What I’m using

Hardware

I’m into the Apple ecosystem. My main machine is a MacBook Air with an Apple chip. This is often enough for my development needs on the side, and the portability of this laptop is a plus. When I need to work even more lightweight (because I’m traveling or working on the go), I use an iPad Pro 11-inch with an Apple chip. I’ve found this machine to be super capable of handling most work (with, of course, a few compromises in developer ergonomics).

When I need to do some coding on the go with the iPad, I use GitHub Codespaces. Again, the ergonomics are far from those of a desktop machine (window management is something that doesn’t work as well on iPadOS, even with the latest updates), but it’s good enough to let me get the work done. Another drawback of coding on the iPad is that I need an internet connection, so it’s not the best option if you’re planning to work while flying or from places with limited connectivity.

While I’m on my desktop, I use a Jarvis standing desk from Fully and I switch between sitting and standing regularly. I have other peripherals from Logitech (the MX line) and elgato (mic, key light), and I’ve repurposed an old Sony mirrorless camera as my main webcam (I use an elgato Cam Link to connect it to the laptop).

Dev Tools

For writing code, I use VS Code (because it’s everywhere these days). And since I’m currently working at GitHub, I use GitHub Copilot extensively as my AI companion. Regarding VS Code customization, I’m enjoying the Catppuccin theme (the Mocha variant), and I always work with dark themes (I don’t think I have a solid reason for that, just personal preference).

As for coding fonts, that’s something I’ve experimented with a lot. I spent quite some time using JetBrains Mono, then Dank Mono, and for the past few months, I’ve been a happy user of MonoLisa. I’m by no means a font expert, so the choice often comes down to personal preference for their aesthetics, ligature support, italics, etc.

These days, I typically use the integrated terminal in VS Code for convenience.

Technologies & Frameworks

This is obviously super dependent on the project and the context I’m working in. But my go-to technologies and frameworks these days for any new development are:

• TypeScript: I’m not going to make a long argument for this language. It just works, it’s everywhere, and it has great adoption. I was really into JavaScript back in the day, and the transition to TypeScript just felt natural.
• Next.js: It’s opinionated and quirky sometimes, but I’ve been using it since 2018 in very different projects. It’s well maintained and continuously evolving (which can be a good or a bad thing, depending on how you look at it). The React ecosystem hasn’t yet reached full maturity (we just need to look at the recent movement towards React Server Components), and Next.js is always at the forefront. Beyond being a front-end framework, I’ve also had a great experience using it as a full-stack framework while working on saraos.tech (it’s a monolithic application built on Next.js, handling both front-end and back-end).
• Other tools: These often come and go, but my default testing framework these days is Vitest. And for every front-end project, I use Radix Colors to get a good starting point for designing the color palette (it works well in both light and dark themes and provides clear guidance on when to use each color and shade). Highly recommended (as well as much of the Radix ecosystem).

AI

I use AI tools every day. They’ve become such a fundamental part of my workflow that I decided to create a dedicated page I can update frequently, where I explain how I use AI and which tools and platforms I’m currently using.

Updated on January 2026