If I was hired to start a new tech startup tomorrow, web + mobile app, this would be my stack:
- Rails 8 monolith
- PostgreSQL
- AWS hosting
- Creatine gummies
- Cloudflare
- Sidekiq
- Jbuilder for JSON templates
- ViewComponents + Slim in the FE
- Dart SASS written in BEM
Ruby is such a weird language!
It’s like, everyone was able to be super productive and build incredible things with it for about twenty years, but then suddenly it needed static typing! 🤔💭
Just learned that Ray Peat died a few days ago.
Very few people made a bigger impact on my understanding of the world than he did—particularly around topics such as health and nutrition.
What a terrible thing to lose such a unique thinker.
#raypeat
How to you handle changes made to the database schema when your queries are all standalone?
e.g. someone adds archived_at to users, and now you have archived users showing up in places they shouldn’t
It’s possible to write Ruby for years and not properly understand OOP.
Once you understand that OOP is about deciding which object is the best receiver of this message, rather than deciding which message to send this object, you understand that MESSAGES (not objects) are the
Tomorrow I’m going to stand in front of a room full of Rails devs and tell them that `attr_accessor` is one of the most dangerous things you can use in your codebase, from a code design perspective.
Wish me luck?