The BEST code is code YOU yourself can understand 6 months later, and don't have to ask "what was I thinking?"
Readability and lack of redundancy is what I consider to be clean code
"Dave might be holding the internet together, but one day Dave is gonna quit… and then we’ll all suffer."-stolen from chat gpt
I learned to write clean code the hard way after having to refactor my own code that was 6 months old due to a change in requirements. So yeah, unless your team is in XGH mode, it's a good idea to spend a little extra time to make sure the quality is there.
I like to structure code like a tree. The trunk and branches are usually very clean and efficient, with priority to efficiency, but the leaves are just chaos incarnate, since they are the "end points". Sure you could make them clean and it's nice if they are, but you wouldn't get anything from it.
Writing readable/maintainable code is a skill you can develop to the point where it costs little if any time to do, and I encourage my juniors to do so.
I am the only dev where I work. My code gets messy because I don't have the time to make it clean while juggling other responsibilities. Some of the projects have grown so far out of scope and I've learned so much that I really need to rebuild them from the ground up, but management wants their sudden idea completed a week before they even thought of it so I just slap some more lines in there and cross my fingers.
Because people think a code can be either bad or clean. Believe me there is no limit on how bad code is. Like you said real skill is to know when enough is enough to make things as clean in deadline.
Me remembering I just put a comment "Temporary implementation" in my code today and thinking right after that that I might probably never touch it again, this video confirms it.
Preparing for interviews, ive realised that clean code is more about design principles and solid principles. Its not about having nice variable names or a lot of comments.
I'm so focused on writing clean code that I always use semantic HTML tags like main, nav, section, footer, p, etc. It makes the code much easier to read and avoids the typical nested div hell.
There is the type of technical debt that makes you cringe for 5 minutes. And then there is the technical debt where you take 4 weeks to ship a feature instead of 4 days.
This is the most accurate description of programming ever made
What does if it's an internal or external feature affect maintainability. Clean code isn't about the current deadline. It's about the next deadline. They won't care if your code is clean, but they will care when you're stuck on some bug and late a week.
all I see is spaghetti
Why this video is a SCAM
1:41 it's getting shipped on the titanic
Slow and clean, or quick and dirty? Why not do it like 10x developers and combine the best of both worlds: slow and dirty
There is some truth to this but some people will take the wrong message from it. If you're newer to engineering, find an experienced person you can trust to help you balance quality vs placating the non-technical folks.
@codehead01