You're viewing a single thread.
Single responsibility principal and dependency injection are your friends.
The problem is that so is the junior dev they hired to do the two seniors' jobs who left for less inhuman pay.
Code problems are usually people problems.
Also makes it easier to put spaghetti back onto the right track
You reminded me of a guy who’s always banging on about how Elm combs the spaghetti in your source code for you and the meatballs and sauce are only mixed in at compile time. He says object oriented programming is like threading the pasta through the meatballs which is OK before anything’s cooked but after that it gets too soft and entangled and the spaghetti won’t thread through so you start again rather than refactor. It was a compelling image and got me curious.
I used it for the second rewrite of a side project WebApp a couple of years ago, and I it felt like I had to do everything from scratch by hand all the time at first, but I have to admit that maintenance has been an absolute dream compared with the old codebase. New features, changed functionality, it’s always good and you don’t need to reunderstand everything because it’s all so separated and I told him he was right. It writes the css for you and I kid you not, I did not miss that flakey nonsense one bit.
Our boss is shit scared of anything even a little bit different, though, so he noped out hard when he saw the syntax and got all shouty about all the whitespace and arrows on the big branching statements before launching into a sermon about how you can’t have a corporate look and feel unless you use css. I lost quite a lot of respect for him that day.
Our code at work is so like the bottom picture. You have absolutely no idea whether you just filled someone's underpass when you build another bridge over the top and sometimes you just have to kill the whole branch you've been working on because adding a f*ing overhead sign collapsed seven other things and no matter what you try, you can't undo whatever it was that collapsed. I swear, one day we're going to find that someone accidentally nuked twelve routes six months ago and there's nothing anyone can do about it any more.
I'm not familiar with Elm, but I wish you good luck praying that codebase stays functional
The side project is safe from managerial interference. At work though, nothing is functional. Well, boss always claims we're combining the best of the functional programming world and the best of the object oriented world and the best of the agile world, but what he means is we can have as many buzzwords as he's heard at conferences as long as we're prepared to ignore the actual principles and do it the way we always did it. Give him is due, he is not an unreasonable man and will actually support you and listen to sense, but he's absolutely not interested in fundamental change.
Edit: Oops replying to wrong person sorry.