The author of the video is apparently referring to Uncle Bob’s first book (Clean code, 2009), which essentially says that “Clean” code is “understandable” code: created with care, thinking about the next reader.
So yeah, the book then goes on for a painful 450 page ramble, opinions, and admittedly arbitrary rules.
But Martin was at least partially aware of this:
> “Clean code is not written by following a set of rules” — quote from the book!
So really, the person in the video failed to apply the Principle of Charity, which is fundamental in critical thinking.
They end up not addressing the interesting claim, and openly attacking a Straw Man.
As for the deeper points implied in the video, they seem –ironically– less fresh:
- Software is slow these days
- Performance matters
- The way you write code impacts performance
- Don't blindly follow rules and generic advice
Groundbreaking!
If anything, the video shows the failures of C++ as a language. Why aren't languages designed to promote maintainability without sacrificing performance? :Rust enters the room:
The more interesting claim that the video's author missed:
> “It is not enough for code to work.” ― quote from the book
Thank you for the kind comment! I've been a bit busy lately but implemented zoom with the mouse wheel today (it's not yet on the live wasm build though).
Don't offer anything new, just mirror their attitude and feelings. If they say their day sucked, you go "that sucks". Then you encourage sharing by asking for more details, and you join them in whatever attitude they have about the things they share.
That's it. Fake it till you become it. If you're sincere, it works from the start.
Yes! If you are interested in doing front-end in Rust using Wasm, checkout Yew : https://github.com/yewstack/yew
The data flow is inspired by React, you’ll feel right at home.
I've seen the videos and went through -most- of the book exercises. This is a beautiful way to teach and think about programming and it continues to fascinate me.
Was used to HDPI screens at home and previous gig. Now at work with Linux and some cheap Dell 24"s: just zoom like 200%, until text is huge. If you only fit 80 cols like god meant to, type will be clear, you can have your monitor further away, improve your posture and eye strain. Code might even get better.
Guess coders care little about typography, like everyone else, mostly out laziness and lack of appreciation.
So yeah, the book then goes on for a painful 450 page ramble, opinions, and admittedly arbitrary rules. But Martin was at least partially aware of this:
> “Clean code is not written by following a set of rules” — quote from the book!
So really, the person in the video failed to apply the Principle of Charity, which is fundamental in critical thinking. They end up not addressing the interesting claim, and openly attacking a Straw Man.
As for the deeper points implied in the video, they seem –ironically– less fresh:
- Software is slow these days - Performance matters - The way you write code impacts performance - Don't blindly follow rules and generic advice
Groundbreaking!
If anything, the video shows the failures of C++ as a language. Why aren't languages designed to promote maintainability without sacrificing performance? :Rust enters the room:
The more interesting claim that the video's author missed:
> “It is not enough for code to work.” ― quote from the book