Reading up on Rails

Yep. Except: 1. This was about important internal tools. The team was stuck in some architecture nightmare of their own doing (writing it in rails but headless, with graphql api, and a SPA react app, constantly needing frontend engineers for changes). I call this kind of thing 'cosplaying an enterprise production app'. All that complexity was in the way and using straight rails was perfect in that case. 2. I make calls like this all the time. Usually someone on the team asks me to. They see what needs to happen but don’t want to be the bad guy. I’m happy to just make the call if I agree with the premise. Saves enormous amounts of meetings and change management etc. Sometimes this is jokingly referred to as Founder-mode-as-a-service here. 3. For ten years I’ve also run an internal podcast called Context, where I revisit decisions like these and explain the reasoning so everyone can learn from them. This is helpful to give people all the variables that were considered and why this was the choice made given the information available at the time. I want to teach how to make such decisions effectively without needing me. Sunk cost fallacy is a problem. 4. Any notions that Shopify is succcessful despite of me doing this, instead of because of it, will have a hard time making their argument come together I think 😄 the part of 'two weeks later tobi learns about...' is nonsese and the pivot of that project up there happens one of the more successful examples of interventions. But getting the company to work effectively with great architecture and low technical debt baggage into the right direction is literally the job, so guilty as charged I suppose. But there are always cope stories floating around like this because they are more fun, than saying 'somehow we needed tobi to stop doing silly architecture astronautics'. I can totally see that.

@tobi

it says a lot that the creators of three of the most iconic web frameworks: django (@simonw), flask (@mitsuhiko) and rails (@dhh) were so AI pilled so early

@trq212

Stop building Foxconn factories for your agents

@garrytan

In light of all the heroku drama, here are 3 services I use or have used extensively over the past few years for hosting/deploy/server stuff.@Railway — This to me is the spiritual successor to Heroku. Arguably does the best job at distilling eye-gouging sysadmin stuff down into…

@Shpigford

The beauty of opinionated open source software, like Rails or Omarchy, is that the initial experience can be carefully designed AND still offer the user infinite freedom to tailor it thereafter. It's your framework, it's your OS, it's your computer. https://t.co/b05Lb7yr4X

@dhh

CSRF token headaches in Rails will be a thing of the past thanks to Rosa. She first tested the solution based on Sec-Fetch-Site header in Fizzy (1), and then upstreamed to Rails (2) 🎉(1) https://t.co/jWVDhgCPZQ(2) https://t.co/yfCDyWR1Ko

@jorgemanru