4 ms·
> the stack always grows to the point that a dev can no longer test it on their own machine So the solution here is to not have that kind of "stack". I mean,
by arp242 2y ago
> the stack always grows to the point that a dev can no longer test it on their own machine
So the solution here is to not have that kind of "stack".
I mean, if it's all so big and complex that it can't be run on a laptop then you almost certainly got a lot of problems regardless. What typically happens is tons of interconnected services without clear abstractions or interfaces, and no one really understands this spaghetti mess, and people just keep piling crap on top of it.
This leads to all sorts of problems. Everywhere I've seen this happen they had real problems running stuff in production too, because it was a complex spaghetti mess. The abstracted "easy" dev-env (in whatever form that came) is then also incredibly complex, finicky, and brittle. Never mind running tests, which is typically even worse. It's not uncommon for it all to be broken for every other new person who joins because changes somewhere broke the setup steps which are only run for new people. Everyone else is afraid to do anything with their machine "because it now works'.
There are some exceptions where you really need a big beefy machine for a dev env and tests, maybe, but they're few and far between.
- fragmede 2y ago> So the solution here is to not have that kind of "stack". Reminds me of my favorites debugging technique. It's super fast: Don't write any bugs!
- vinnymac 2y agoCode is a liability. Not writing code is one of the best things a developer can do on any particular day, aside of course from deleting it ;)
- halfcat 2y agoQuite an effective approach: https://github.com/kelseyhightower/nocode https://github.com/kelseyhightower/nocode
- arp242 2y agoWhat a boring trite reply. All of this is analogous to badly written spaghetti code. And yes, you can absolutely avoid all of this if you know what you're doing.
- Tainnor 2y agoNot trite at all. Bad code and bad architectures are a reality. You can fix them in theory, but that takes a lot of time and needs to be done incrementally. In the meantime, you have to live with the problem at hand.
- justinclift 2y agoThat kind of mess sounds super dangerous from a production perspective too. With things that messy it's fairly likely there would be dependency loops or problems (thundering herd, etc) trying to get things going from a cold start. ie after a complete outage or similar for whatever reason