The Myth of Clean Code

The Myth of Clean Code


USE COUPON CODE: hallden
To get 32% discount for premium

A lot of beginners might ask the question what is clean code? And how do I write clean code? In this video I try to show that clean code may actually be a myth.

"Clean Code Friday"

Follow me on:

--------------------------------------------------------------------------------------------------------
GEAR:

[berargeorge]

I think a code without bugs is not considered a 'clean code' and is more like 'a code without bugs'. Clean code refers more to formatting for better readability, docs, consistency in naming convention, low cyclomatic complexity, not have duplicate code blocks etc. A code that can be read after 8 months and is still understandable and its purpose is clear...that's a clean code.

[colehanson]

“Print(“Hello1”);” I felt that on a personal level

[mattstirling]

Me: Frustrated with messy code. Open up youtube
Youtube: The Myth of Clean Code, uploaded 1 minute ago.

[foxubis]

everyone gangsta till he starts debugging with "hey"

[paulopimenta]

"Using print statements as the debugging method of choice", can relate 😂

[Mortuus]

- types on laptop
- encounters errors
- google's on phone

[David-yscw]

In addition to what Kalle said, if you're looking to improve your Code, in my humble opinion Clean Code mostly results from:
1. Clean Architecture
2. Test Driven Development
3. Knowing your programming language really well

[imaginarynoise]

I've never met anyone who regards code running perfectly the first time as something to aspire to. Most of the people I've met - including ones who appreciate 'clean' code - are mildly skeptical if they do a large amount of work and it just runs.

[PandaPavilion]

Kalle 1: "So you did write the test?"

Kalle 2:

I'm cracking up

[Ziontastic]

i'm a software engr for almost 14 years and what i learned:
1. do algorithm
2. compile / test per module ( in parts)
3. no hardcoding
4. test every line (unit test)
5. test negative scenarios

[PrinceDVII]

I recently spend a big amount of time reading and watching things about architecture and clean code. In the end, I decided to stick with one thing and the process will teach me how to do it better. It is about enjoying the process instead of being perfect. Thanks for the video, it is timed perfectly for me 😂

[TomGrubbe]

"Where each line is perfectly planned out, so well planned that the first time we run it, it just works. No errors, no flaws first go." I don't think that is anyone's idea of clean code. What's the matter with readable, understandable, extensible, maintainable?

[n.kh.l]

0:53 wait what this is my debugging from the start.

[ivanyang]

This Coding channel has the best cinematography work.

[pawelpiotrgil]

Hi Kalle, awesome video! My recipe for clean code is TDD. It shortens the refactor cycle from refactoring once per working feature (or so) to refactoring once per passing test which is like every minute. It encourages clean design and makes implementation in complex projects way faster (no need to run the project and test your implementation manually each time you add new code or refactor). In addition - when you write tests in order to understand already existing code you get a better understanding of it and contribute to higher test coverage - super useful technique. Mastering it is not easy and takes lots of practice, but we're programmers - we know how to do that.

[corieleclair]

I felt personally attacked when he spoke of using print statements as debug methods.

[webdevlog]

Great video man, love your stuff. I think this is a important concept for every programmer, to not be a perfectionist who gets stuck over small stuff but instead someone who get shit done and also makes it better when time is right! Props brother.

[lemuelpuglisi]

"Writing - refactor - review" method can seems faster because your code will run after the first step. But it introduces technical debt that you have to pay within hours of refactoring, so in the end it will takes from you more time than actually thinking and writing clean code.

[valeriovettoretti]

I think that even if clean code is nearly impossible to create, if you have a really good knowledge of the programming language you are using, you can do it.
But when you are using languages that you dont know 100%, i think its just fine if the programs runs enough smoothly for you.

[bsimpson]

Incredibly helpful, Kalle. Thank you. I haven’t even started yet, but bought my Head First Java LAST NIGHT.
The bits of podcasts at the ends of your videos are a great treat.
And like others have said, your production quality and editing skills are increasing at an astonishing rate!