Wondering whether “best practices” has wrecked SW engineering
At this point I've seen this kind of feedback one too many so, given that I'm just a click away from giving the whole current SW dev party the middle finger and do something more productive with my life, I'd just want to see if I'm alone in feeling that:
1. cargo-culting (uncle Bob et all) has poisoned the field to the point of destroying even unrelated paradigms (at this point I won't be impressed if someone tries to apply SOLID to Elixir)
2. SW eng roles are gatekeeped (this was a take home test) by evangelists of a certain type that make sure that things will keep being done in that way.
3. That way being the way Java ecosystem made sure that nobody with a creative vein and a slight aversion to authorities and bureaucracy would ever set foot in it again. Consistently delivering overengineered BS that build nice CVs and careers and leave companies with unmaintainable overengineered messes.
4. There is yet a shred of actual damned scientific evidence that all this 90s and 00s "best practices" actually lead to better SW. There has been no double blind experiment to measure whether the SOLID principles actually work or their best use is to insure a fat paycheck for evangelists and build CVs. For the record I conside most of SOLID and a lot of DPs just self-indulging rules conjured out of thin air. A case of an academic trying (and succeeding) to impose his hugely impractical views on the real world. Shit that looks good on paper but is actually offering little value and a lot of times is akin to splitting hair.
Anyway. Bye and thanks for the fish.
I think I deserve much more than munching on canned BS by this world's uncles and their minions.