Hi @cmuratori, big fan but this bashing of "clean" code doesn't match my experience. I work on a legacy code base and it's the stuff which doesn't try to code to interfaces, or follow any of the SOLID principles which is the "bad" code. (1)
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
By bad I mean that it's inflexible, hard to understand, resists extension, is buggy and so on. These principles aren't the product of some fever dream, they did come from an effort to make writing software more disciplined. (2)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Maybe it's just that our definitions of "bad" don't align too well. Maybe writing software which much evolve for 20+ years is a different beast entirely. Could you explain which of the SOLID principles (for example) leads to bad code? Thanks for reading, appreciate your work.
-
I do write 20+ year codebases - the last codebase that I shipped as a library is still in use today. I designed it in 2000 (http://www.radgametools.com/granny.html ) and the API remains essentially the same to this day.
- Show replies
New conversation -
-
-
I love this thumbnail
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.