News for hackers. Stuff that matters.

A comment on What software engineers can learn from the rapid collapse of Fast. Parent comment

Re:What software engineers can learn from the rapid collapse... by mwcampbell on Thursday April 07, 2022 @05:27PM (#30950546)
Perhaps one problem with the current backlash against over-complicated infrastructure is that for some of us, doing everything in one process on one machine using a local embedded database is its own form of playing with nifty toys.
[ Parent | on HN ]
Re:What software engineers can learn from the rapid collapse... by bryanrasmussen on Thursday April 07, 2022 @06:23PM (#30951059)
yeah, I guess, I'm not going to get too specific here but I do think it would be nifty if I didn't go through a couple 10 minute periods every day where I have to basically shut everything down run a number of scripts, then restart individual processes that are problematic, to be able to work again.

Note that this basically works 99% of the time now and is part of a learning process that had the whole thing taking 2 - 5 hours every day for several weeks, down to 2 hours a day for several weeks after that, and now down to the nearly inescapable 20 - 40 minutes a day I have now.

Yeah, not doing that would be my own form of playing with nifty toys.

[ Parent | on HN ]
Re:What software engineers can learn from the rapid collapse... by collinmanderson on Friday April 15, 2022 @08:17PM (#31047626)
Wow. I would find it super annoying to be interrupted twice a day to do a 10min task. Can’t you try to narrow down the underlying bug? Or somehow automate the restart?
[ Parent | on HN ]