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 -
Replying to @cmuratori @MartinTittensor
I'm enjoying all your content these past weeks. In this lecture you seem somewhat aligned with SOLID on the importance of avoiding coupling. When you criticize ReadFile bundling reading file w/ interpreting it into an object it kind of makes me think of Single responsibility
1 reply 0 retweets 0 likes -
I think if you saw what the average web developer puts out before learning SOLID principles you might self immolate.
1 reply 0 retweets 0 likes -
But I also see SOLID being over-applied to great detriment. I want to take more away from your lectures for my work in web dev but I find it hard to map a lot of the concepts back to that space. I found the WARMED concept more portable than the principles in this lecture.
1 reply 0 retweets 0 likes -
Replying to @gordon_cassie @MartinTittensor
WARMED was just my attempt to say "this is what everything should come back to", so hopefully it is applicable everywhere. The API design lecture was specifically to a game development audience, so it doesn't include the necessary explanation for people used to web.
1 reply 0 retweets 3 likes -
Web is a particularly bad architecture in general, so I think in order to really talk about good API design principles, you first have to explain all the ways that the general architecture of the web obscures good API design in the first place, etc.
2 replies 0 retweets 2 likes
But the concepts from the lecture would still apply.
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.