This is also true. But once that happened, it was a sort of expectation and often necessity. People couldn't outsource as much hard work to machines, built by someone else far away from their farms
Nothing fundamentally changed about frameworks. No need to reconsider every single practice because of AI. I think frameworks actually keep agents in check because they're trained on huge set of conventions.
I vibe coded a few of projects in vanilla JS and they eventually became mess, but with a framework they'd at least be structured mess
"This printer is for collecting and research purposes only. Note that certain 3D-printed objects are forbidden by the law. If you notice any of these objects growing inside your 3D printer, power it off IMMEDIATELY"
Reminds me of those prohibition era alcohol kits that basically came down to "whatever you do, do not put this yeast in that mixture" and "should that happen, under no circumstances should you let it sit in a dark cabinet"
I use it all the time to SSH into my workstation and check on long-running tasks, code, etc.
- Using vim/neovim is way better than I'd expect on a phone keyboard, because you can move around faster with less keypresses.
- My terminal sessions are wrapped in tmux, so switching between devices is seamless (tmux panes resize without any problems to match your device dimensions/aspect ratio as soon as you interact with the terminal - nothing ever breaks). You can do the pinch gesture to change the text size, depending on what you need to see at the moment.
- Both devices are using tailscale, so all I need is cellular data connection. For low quality network coverage I use mosh, which makes the session truly unkillable and makes sure it will recover when the connection comes back, albeit I ran into some annoying limitations with text scrollback.
With the recent development of agents, it becomes even more effective, since I can just open up claude session, type the prompt and have the agent do the heavy-lifting (mostly writing large chunks of code). This greatly compresses the amount of text you'd have to type and makes phone-only coding more viable than ever.
In Rails at least,aside from being used for background processing, redis gives you more goodies. You can store temporary state for tasks that require coordination between multiple nodes without race conditions, cache things to take some load off your DB, etc.
Besides, DB has higher likehood of failing you if you reach certain throughputs
One of reasons is because more hands were needed to deal with the difficulty
reply