There's a good take on this by Casey Muratori - https://www.youtube.com/watch?v=7YpFGkG-u1w
And I agree with him. Things like SOLID and "Clean Code" really are just buzzwords nowadays that don't mean anything.
And I agree with him. Things like SOLID and "Clean Code" really are just buzzwords nowadays that don't mean anything.
I really appreciate his push for simple and efficient, but in reality, the industry has spawned hundred of thousand of software developers these last decades, and collectively we've simulated every possible way of building software. The simple reality is, teams who followed well established patterns and good practices have had more success.
Perhaps. I don't agree with everything he says all the time, however, from my own experience on working on distributed enterprise software I can say that following patterns blindly is an actual problem that impedes a good working solution designed for the specific problem(s) a lot of the time. Devs are pushed by DM's and PO's to have a working product ASAP and what might be a good idea for MVP prototype ends up being a burden down the line because now the entire system is built on top of that decision made in a moment in time without serious thought. Then some time passes and the whole thing crashes down. Then a rewrite happens in the exact same way and the wheel keeps on spinning.
My 0.02c are that I think we should build things more sustainably and expect software to work longer. We should hold ourselves to a higher standard.