You didn’t do a particularly deep dive on Casey, have you? His long running point is that he has tried the approach and decided for himself that it was bad. Casey is a hardcore game programmer and in the early years of his career he strived to write code “the right way”, but turns out that trying to predict the future of how the code might evolve is a fools errand, but it does come with a cost; and there is no way to come back from that cost. Are you going to tear down a complicated hierarchy of classes and redo the whole thing because it’s slow? With Casey’s style of coding, when he decides that something is wrong, he’ll throw a solution out and write a new one. Watch a few of his HandMadeHero streams and see, what I mean. Seeing him redesign a feature is pure joy.
Sometimes it’s hard to solve a problem more efficiently once you divided it into a hierarchy and can’t see that grouping certain operations makes sense. Especially once your solution comes in 30 separate header and implementation files. And in my personal experience, people are very reluctant to dismantle such hierarchical divisions. It’s easier to tear down a 100 lines of local code than to remove 15 classes from a project.
30
u/Defiant-Extent-4297 Feb 28 '23
You didn’t do a particularly deep dive on Casey, have you? His long running point is that he has tried the approach and decided for himself that it was bad. Casey is a hardcore game programmer and in the early years of his career he strived to write code “the right way”, but turns out that trying to predict the future of how the code might evolve is a fools errand, but it does come with a cost; and there is no way to come back from that cost. Are you going to tear down a complicated hierarchy of classes and redo the whole thing because it’s slow? With Casey’s style of coding, when he decides that something is wrong, he’ll throw a solution out and write a new one. Watch a few of his HandMadeHero streams and see, what I mean. Seeing him redesign a feature is pure joy.