After reflecting on it for a while, staying relevant to me means understanding that our role isn’t just about writing code. It’s about solving business problems through technology and staying adaptable to new tools and trends (yes, I’m talking about AI 😄)

* what "non-trivial" means may vary across different teams!

this not only provides a great space for async technical discussions (as we’re fully distributed across multiple time zones) but also serves as a solid foundation for a future architectural decision record (ADR).

yeah, thank you for recognizing this! ❤️ I fully agree with your conclusion in the article that it’s about staying humble and embracing uncertainty. In my experience, that’s the hardest shift (we’re not taught to admit ‘we don’t know’ in a professional setting…)

On a different topic, I’ve spent the last few weeks replacing css-in-js with CSS Modules. The main reason behind this decision is to facilitate the adoption of the App Router in Next.js, which will help me unblock some features that are already in the works!

I love this article, @eferro.net, and it really aligns with my philosophy on software engineering. What’s frustrating is how counterintuitive these principles can feel to those unfamiliar with them; in my experience, it’s something you only appreciate after trying.

A ver si nos cruzamos por ahí y podemos charlar un ratillo! 🙏

After much browsing this weekend I’ve decided to move forward with the Steelcase Leap chair. This will be my first time spending big bucks on a chair, but after suffering some upper back pain recently it feels like a good investment!

Funny enough, I've switched ORMs in the past, and having that abstraction has proven extremely helpful! Again, probably not something people working in Ruby-land (Rails) have to worry about (has anyone ever abandoned Rails' ActiveRecord?! 😬)

With a few exceptions, you never know when it will be time to switch to a different solution or when a package will be abandoned. I have to remind myself of this every time I'm tempted to use the Prisma client directly from the domain layer for convenience, without adding an extra data access layer

All these pieces helped me reduce the integration test suite runtime for saraos.tech (more than 600 tests, all run serially) to less than a minute, down from almost 7 minutes!

It was yet another reminder of how incredible the open source community is and how fortunate we are to have such a massive source of information at our disposal 💖