This has been such a great read. I was feeling something along those lines but couldn’t quite articulate why. This article does a great job of making sense of the issue with the new design direction at Apple on macOS tonsky.me/blog/tahoe-i...
This has been such a great read. I was feeling something along those lines but couldn’t quite articulate why. This article does a great job of making sense of the issue with the new design direction at Apple on macOS tonsky.me/blog/tahoe-i...
Yessssssss, I remember dreaming about this feature ~10 years ago when we started using it for the content property. CSS is getting more powerful! ✨
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).
recently, whenever the team needs to make a non-trivial design decision for any of the systems we develop, I advocate for writing a design doc that outlines the context of the change, the proposed solution and at least one alternative solution we’ve consciously discarded.
I bought an iPad recently and tried coding on the go with cloud development environments. Not the ultimate computer (yet), but it can work well enough for super light travel and light work.
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 think I’ve found a valid use case to integrate some AI into saraos.tech. It wasn’t something I was explicitly looking for, but it came to mind while thinking about how to make a specific feature more useful. More details coming soon!
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! 🙏
I'll be attending BilboStack in a couple of weeks, which also makes for a perfect excuse to visit Bilbao for the weekend :-)))
Who else is gonna be there?
The internationalization APIs (Intl) in browsers and Node.js are so good! Yesterday I added language-sensitive string comparison in just a couple of minutes and have been relying on the date format APIs for years.
developer.mozilla.org/en-US/docs/W...
You know we’ve reached a decent level of civilization when you can wear noise-canceling headphones, shutting off one of your natural senses, without worrying that something (or someone) will attack you.
I’m about to upgrade a four-year-old project to eslint@9. Any experiences on how painful it will be? Hoping the ecosystem has had enough time to catch up with the new configuration format 🙏
Unsolicited product review: I recently bought the Nothing Ear (a) earbuds and I couldn't be happier with them. The noise cancellation works great & the sound quality is very good. Currently on sale on Amazon (Spain)!
Over the past few days, I’ve been working to make @saraos.tech friendlier with social media links beyond X or websites. Organizers can now add up to five links, with automatic recognition for the most popular ones (and support for more coming soon!)
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!
I’m on the hunt for a new office chair, and before I start browsing like crazy… do you have one you’re particularly happy with?
Okay, it seems like a good time to add support for links to other social accounts such as this beautiful one 🦋 into @saraos.tech 😌
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
Working in the JavaScript/TypeScript/Node ecosystem for a few years has reinforced my belief in the importance of not coupling too tightly to third-party libraries outside your control. The Node ecosystem is far more fragile and fragmented than, say, Ruby (Rails)
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 💖
I hope I can find some time to write about a few things I've learned over the last few days about JavaScript proxies, Prisma, and Jest/Vitest environments.
yesterday, I migrated over 600 tests (unit tests, component tests, integration tests) from jest to vitest, unblocking the issues related to upgrading packages to their ESM versions and simplifying the overall test infrastructure. Truly a drop-in replacement for jest! ❤️
my main questions today are about how to provide a consistent ux, given that there will be at least 3 different areas that need proper translation: logged-out experiences (landing pages, blog), the application itself (taking user-preferred language settings into account), and transactional emails
hey 👋 are you folks familiar with any good resources about i18n in a web app? I have a good understanding of what's required, but I usually enjoy reading in-depth posts on topics (book recommendations are also welcome!)