The Q&A from "Where Bad Code Comes From" is now available on YouTube:https://youtu.be/cOcaj_cRBvE
-
-
Replying to @cmuratori
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.
1 reply 0 retweets 0 likes -
Replying to @MartinTittensor
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.
1 reply 1 retweet 4 likes -
Replying to @cmuratori @MartinTittensor
The parts of SOLID I disagree with are the S, the O, the L, the I, and the D :) In general I think it is mostly focused on completely incorrect ideas that are at best tangential to the actual ideas you want, at worst opposite to them.
1 reply 2 retweets 5 likes -
Replying to @cmuratori @MartinTittensor
For a better set of "rules of thumb" for library design than SOLID please see my API design lecture here:https://www.youtube.com/watch?v=ZQ5_u8Lgvyk …
3 replies 0 retweets 8 likes
In certain instances there are narrow slices of SOLID that I could warp into the correct ideas, but most of the time the SOLID concepts are just wrong.
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.