4 ms·
Anyone remember the unlimited number of "build Twitter/blog/todo list in 15 minutes using Ruby on Rails" tutorials? It's great that we've got it down to 2 minu
by PheonixPharts 3y ago
Anyone remember the unlimited number of "build Twitter/blog/todo list in 15 minutes using Ruby on Rails" tutorials?
It's great that we've got it down to 2 minutes.
However anyone who has worked in a rails shop has experienced that somehow that initial set up seems to make everything else down the line get a bit more time consuming.
In fact, I would posit that there might be an inverse correlation between how quickly you can get a blog up using framework X (including an LLM) and the long term scalability of that project as you start adding features and engineers.
Legacy rails apps can be terrifying, I can only image the horrors that will be legacy LLM apps if they can even manage the structural cohesion to become legacy apps.
- lolinder 3y agoYes! And the cause is the same in both cases: magic. The more magic is involved in getting everything set up, the less well you understand the system you just built, and the harder it will be to do what you need to after the initial scaffolding. Wiring up the initial boiler plate is tedious but gives you a complete picture of the system.
- adventured 3y agoFear not, future LLMs will be tasked to fixing historical LLM apps. Circular LLM employment program.
- pqdbr 3y agoI have the exact opposite impression: legacy Rails apps are usually a pleasure to work with if the developers followed the most basic framework conventions. It's called "on Rails" for a reason.
- deleted 3y ago[deleted]