hi, who? Adriano, João. I build software.

Socials: X / GitHub

What I'm working on

Lead Developer at Nortech.ai - Digitalizing the marine sector


How I work

  • Tools not rules - Prioritize good internal tooling, automate the golden path
  • Measurement over intuition - It's a tradeoff, but I err on the side of measurement
  • Iteration over planning - You (usually) get more information from trying it out and exploring the shape of the problem than from thinking about it.
  • First draft, good draft - I build a rough version of the solution while iterating, then throw it out and write the good one
  • Early adoption - There's a lot of advantage in adopting new technology early

  • Relevant tidbits

  • I'm years old
  • I've been coding professionally for years now
  • I started scripting (JASS) at 11 to make custom wc3 maps
  • Hosted my own WoW private server at 16, modding it to make my friends OP
  • Skipped college to start working at 18.. Debatable decision

  • Current tech choices

    Infra
  • Kubernetes - Built several medium sized clusters
  • AWS ecosystem - My usual cloud of choice. Lock-in conscious
  • Dockerize everything - Not that hard, and makes deployment very flexible
  • Gitlab/github pipelines - I'd rather not though, actively looking for the next evolution in CI/CD
  • Terraform - also CDKTF early adopter
  • Linux - Used several distros (arch btw) as personal work computers, and admined many linux servers
  • Web (base platform, many frameworks, servers)
  • Node.js - many production deployments
  • React - since it showed up
  • Next.js/Vercel - early adopter
  • In the past many a framework was used, including rolling my own for internet explorer 6 (yes...)
  • Dev tooling
  • MacOS - Having a single platform for the team is more important than the linux gains
  • Cursor w/VIM bindings - Best tradeoff of cross team extension building and personal productivity
  • Nix - Setting up all the team envs with nix (ongoing...)
  • Teamwork
  • In person over remote - We're still not there, but VR might tip the scale soon
  • Slack/discord - for remote comms. Discord has better API, slack has better enterprise face value
  • Github - Code hosting
  • Linear - Issue tracking, although usually *just fix it* is a better policy
  • Monorepo - It's really hard to go back once you've worked with a monorepo daily
  • Code syncing - (Graphite - PR Stacking) || (trunk based development - with cutting releases for on prod ci pass)

  • Languages I've used professionally

  • Typescript - since it showed up
  • Rust - low power / high perf, edge computer code - actually in production
  • Python - Barely, but now deployed a few services
  • PHP - Good(debatable) old days
  • Golang - A few production projects, mostly for low-level code
  • Javacript - Many years, but there's barely any reason to write any anymore (except this very website :-)

  • Stuff I've worked on before

  • Nearshoring @ https://mobinteg.com/ - Building in-house products and contract work for customers - 5 yrs
  • Outsourcing @ https://altar.io/ - Building MVPs for companies - 1 yrs
  • Regra - Oldschool portuguese company, not interesting work - 1 yr

  • What I'm not good at

  • Design - I have very little visual memory, internal visualization capabilities, and color awareness
  • Delegating - I prefer to build tools to empower teammates with data and capabilities, rather than delegate
  • Following up - I am not the most organized person, and will frequently lose track of emails and comms. Getting better at this is an explicit goal