Cleaner Code: 3 Ways You Can Write Cleaner Code 

People who say coding isn’t an art form are just salty they can’t do it themselves

Really great video! I appreciate that you not only gave clear and concise information, you also referenced places we could learn more about these concepts. Then you put the actual links in the description. Thank you!!

Excellent! This tutorial shows clear maturity and professionalism! Every beginner should trust this guy! And we can all learn here, or reinforce what we may have learned already.

Well finally a video where I can watch from the starting till the end without even getting bored for a second I hope this continues for all your videos.

Back in 2005, I wrote code as a contractor for a company that transmitted a set of data to an external server. It was okay, written in C# 1.2. A couple of years later, I was hired back by the same company for some other projects. The manager had been replaced and the new guy was complaining about my original code, saying that it was unmaintainable and every time someone touched it, it broke. They wanted it re-written in C# 2.0. Not only did I just do an in-place upgrade to the .EXE file, I added new features that weren't available in 1.2. I re-compiled and had it up and running within a couple of hours. I went back to that manager and told him that every person who said my code was unmaintainable should be fired on the spot because my code was clean and _EASILY_ maintainable. I have no idea who he had that "touched" it, but if they broke it, it was because of their lack of skill, not my code.

Good editing skills, keep it up. Thanks for all those shorts about open source projects too :)

Really love your videos. You deserve way more subscribers. Best of luck

I started really loving your content. Thank you for all these I learned many things from you. I have a small request can you please make some short videos on how to create efficient database architecture for both SQL and Non-SQL databases.

Coding is an art form, but it's also a rigorous engineering discipline. All the fundamentals - encapsulation, defined interfaces, modularity, resilience, reusability, error-checking, exceptions, etc - are pure engineering. Building on those engineering fundamentals is where pure art can be created.

I loved watching your video. Those are some good lessons learned.

I'm just starting to learn to code and your channel is a goldmine, there's so much to learn. thanks a bunch!

great best guard clauses

Quality content man... Loved this

I love the second advice, will go read about it right now

Thank u so much is amazing!

here after one year and u r 340k subs, u deserve a lot Lewis all the support.

keep up the good work man I really appreciate your videos 🙏

Watching the video right now. I'm a beginner, and the guard clauses was very needed! Thank you

Amazing and clear one !

Short, focused and really helpful

Thanks for the good tips and sources. Keep them coming. 🙂

Dude, Guard clauses have made my life so much easier. Great Video!

Very very very useful.

100% on the spot. Recommended.

This is an awesome video... I have issues with hard to read code for projects...

good stuff! I'm a Game Dev, was kinda spooked when you called me out at Guard Clauses 😅 but I've been implementing them for a while, thanks for letting me know what they're called

Really great video. Helped a lot. Please make more of the longer type videos :).

Your videos are absolutely amazing, informative, helpful and so entertaining as well. I can't thank you enough!

I like guard clauses, but 4:18 broke the logic of the original code.

Wow…extreme helpfull

Thanks for waiting everyone! Let me know what you think :) More frequent videos coming now that I am back from vacation 🌴

Also if you have any advice on coding for a 2nd year student I'd be glad to hear from you.. thanks

As always, helpful video

0:25 Love it. LOL

Love your editing style! Keep make videos!

Thanks, this video helps me out.

I have found a really great channel. It feels like found a mentor.

Great video, Make a playlist on SOLID Principles in detail.

The guard tests (or functions) implement the "fail fast" principle. If the parameters are wrong fail as quickly as possible. But beware of complex "check everything" guard functions that could take a toll on performance. If performance is really an issue, you have to find the right balance by separating "safe" internal functions and public APIs that need extra security. Generally speaking any time or effort skipped on design will be spent tenfold on debugging. If code looks messy it is because your thinking is ... messy or at least cluttered.

ty

Thank you for the video. I think the length is perfect. It is a little Snack for in between and it is deep enough to improve your skills. The shorts are Unfortunately to short und of course not deep enough.

Amazing Video About Improving to Code!!

Awesome video. Learnt a lot. Specifically the guard clauses

Which compilers we choose like something looks stylish i use turbo c++ but it's looks like any games to my mom think I'm paying game 😂

I like using cases/matches in python to make if statments readable

Great production value on this one. Best dev channel on RU-vid!

Thats funny. I just came from a video here which told me to remove these guard clauses

Lovely

Is "def send_email(to_email, email): email.send(to_email)" a good example of clean code? Because it's still somewhat confusing to me. I would use different words for (email) address and (email) message but, on the other hand, I don't know the rules of clean code. Maybe we need to limit the number of words we introduce?

when the class has more than 1 arg(or few smaller args) in kotlin then i always use the named arguments

When nesting code, I find it very helpful to put a Number as a Comment for each bracket. Then it's easy to tell when the code within a set of brackets begins and ends. Example: { //10 lines of code here ; { //20 more lines of code here; } //20 { //30 lots of code here; } //30 } //10

One complaint: Some clips are so short that I had to literally pause just to get the joke . Overall, Love it. subscribed

3:02 what is inversion control?

4:25 this code doesn't do the same thing though, you never send the email notification in this version

Where's the discord?

If you have to write more than 3 of statements just use switch or a map

I like to leave some mystery and ambiguity in my code that way when it breaks (and it will!) I’m the only person who can fix it…more money for me 🤑!!!

if you have a clarifying comment, is a great sign, that you could do some simple function extraction with a meaningful name.

What looks clean imo depends in large part on the size of your monitor and structure of your IDE sections ... I have no clue how people do serious programming on laptops. I see people screen sharing and I'm at a loss

There was a brilliant joke on How I Met Your Mother that I keep coming back to. Characters X and Y faced a tough decision, and their happy and exciting conclusion was "do you know who can take care of it? Future X and Y! YEAH!" Of course, at some future point they were like "damn X and Y from the past! Those guys are THE WORST". Well, that's the mindframe my team seems to be in when they produce code, with the exception that, instead of blaming themselves and learn from it when shit hits the fan, they USE how messed up things are to justify their lazy and shortsighted ways to produce MORE unmaintainable and buggy code. They'd watch this video and say "yeah, I wish our applications were like that, but at this point there's nothing that can be done... Now let me resume the making of our next set of bugs".

solid, cyclomativ complexity, coding guidelines = everything you need to know

Yeah, I almost never use comments but I think I split my code into smaller functions a bit too much.

hi lewis, i wish that i had a feedback on your content, so i might be able to help you and (thank you) but, your contents are already amazing, and the only way you can improve, is to keep making contents ❤‍🔥❤‍🔥❤‍🔥

Him: “I’ll use Python and JavaScript” Also him: uses PHP

You said 40 thousand subscribers? More like 400 thousand.

Hey uncle Bob. F CleanCode™ and DRY.

If you use guard clauses, maybe it makes your code easier to read, but it certainly makes the code less performant. I'm not going to write a detailed explanation as to why because it requires understanding how branch prediction actually works. But like it or not, if/else will, in the majority of cases out perform using if statements to eliminate conditions. Every branch taken costs you a least a cycle and every if statement is going to end up as a branch instruction, or if you're lucky, maybe the compiler will make your code branchless, but good luck with that. Okay, so what's a few cycles here and there, eh? We're all friends here. Well, run that routine using those extra few cycles a few million times and now it's orders of magnitude slower. So whilst it may seem good to eliminate a few conditions right out of the gate, don't think of it as a panacea to solve your coding woes. Although that being said, breaking things down into smaller and smaller functions is a much MUCH worse idea, as all those stack frames have to be built and it's not free! Finally, DON'T if possible use exceptions either. That's another classic way to make your code run like dog shit. Treat an exception like it's name suggests, an Exception. An error is not an exception, an I/O failure is not an exception etc. etc.

1. comment what would otherwise be a "why would anyone do this?" 2. simpler is always better, minimize the number of things one has to keep in mind to understand the code 3. make sure test cycles are quick 4. forget all explicit principles

5:03 this goes against java

no matter how clean your code is, there's always that one nit-picky PR reviewer that literally complains about small nothings

I would have chosen if ((age > 18) && (isActive === false)) { renew(); } because it is simple and doesn't warrant 7 lines of code. I haven't seen many situations though someone needs to be 19 years old for something...

2:21 "int elapsedHoursInDays" That is not a good variable name. I don't even know what that's supposed to mean. Is it counting hours or days? And since it's an int, it obviously can't be counting partial days.

I don't comment, so my code is the ugly 😸

Why not give short names to variables and use a separate text file to explain those variable names? Because of that, your code would be clearer and faster to process?

Your clean code does a totally different thing :/

The thing is: if you are only coding in Python and JS, you don't even know the word "efficiency"

40k subsribers? More like 50

There’s no such thing as “self-documenting” code. If anyone tells you their code is self-documenting, feel free to laugh at them.

Good video. Just a one i observed. Your refactoring with the guard clauses left out the "member.sendEmailNotification()" part, so it can only "member.renew()". One way to fix this is to put the "member.isLifeTimeMember()" as the last guard, with member.sendEmailNotification()" in the true part of the check followed by return;

Really great video.

i just yk make it super unreadable

Lewis can't code