Learn to write code (HTML5, JavaScript, Python, CSS3, PHP, SQL) from an ancient nerd: school.studioweb.com/store/

#1 Concentrate on fundamentals #2 Learn on a need to know basis #3 Faster write time is more important than fast run time #4 Open is better than closed with regards to all tech #5 Market forces are always greater than tech/nerd advantages #6 Don't jump on 1st generation technology for production project #7 Simple code is superior code #8 Code should be self-describing #9 Code should be fine-grained #10 Don't marry a language or framework

Tip 8 bonus = set your preferences to auto code-fold method bodies when opening a file. This way when you open (someone else's) project you instantly see a neat overview of all the methods in every file. This helps me so much, especially in React.

Rule #11 - If you do something more than twice then automate it. That applies to both your code (write a function, procedure or object to encapsulate the requirement) and also your general business life (develop a system to reduce repetetive manual effort).

This video is a great relief for someone who's feeling overwhelmed by learning. Thank you!

Thank you Stef, your videos are always inspiring and helpful! Keep it up!

Been watching your channel for almost 2 years. Thank you for mentoring me.

Such refreshing to see a knowledgeable IT teacher, contrary to those wannabe KZfaqr teachers that take more effort into acting like a clown than to teach something useful.

I respect people who are older than me in the field as a software developer with a mere small 3 years experience hearing Stefan lay his wisdom upon us is amazing. I wish though it is more detailed please. This is my 4th video from Stefan that I watched but I feel like I want more .

I work in IT and the need-to-nerd principle is spot on. 75% of the time I know absolutely nothing about what I'm getting myself into because technology changes so fast or we take on a new product or technology. I'll usually just research a bit to learn about it, then learn and look at documentation as I work through everything. No one knows everything, and the person who acts like they do is always avoided when it comes to questions. Either they're bullshitting the answer or giving misinformation.

Excellent - 100% with you. I would add the classic : Data is King. The data structure should be so clear that the code just flows from it. Data first, then code around it. Merci.

I can't believe his videos has only average %1 of dislikes. This is the reason why I watched one of his videos and got addicted to the channel...

Thanks for all you do Stef! Much appreciated

There is an aura of authenticity about Stef; albeit he still has to make a living.

Thanks for the video Stefan. I'm already 4.20x better than I was before and I haven't seen the whole thing yet. On the road to getting 10.69 times better

Can not agree more! Delivering great insights again. One thing I would like to hear more about is rule nr 3 "Faster write time is more important than faster runtime". I think that is a very interesting topic to discuss further.

The realest programming adviser out there, no doubt!

The best teacher! Super easy to watch and learn from! Really impressed! Thank Stefan! Wish I could have found your channel sooner would have saved some money ! Cheers

Great video, some points I already figured out on my own, others only just got me thinking

Great advice. Whenever you're about to violate one of these rules, stop and think for a moment if the benefit you're after is worth losing the benefit of sticking to the rule. In most cases, it's not.

Yeah nice. I have been programming on and off since 1984, beginning with Assembly, Basic, C etc. There has been a ramp up in the last few years, so these videos are very important to someone like me. #1 Concentrate on fundamentals eg know what the Fencepost problem is.

Not only do you give great info with your videos Stefan, but I also give you credit because of that Joe Cool shirt. One of the coolest characters of all time. 👍🏼

That's pretty cool, thanks Stefan!!

@03:50 Two really good examples of closed tech which the industry got tired of is 1) Symbian vs Android and 2) Adobe Flash. Both of these were a massive problem due to private companies not giving a public API. Symbian was the only way to program for a mobile phone in the early 2000s but was considered a black art, back then Nokia was the dominant mobile phone manufacturer. The most common way to develop games for Symbian was JavaME. Android is maintained by Goole and was open from the start and this completely changed the terrain in mobile phone programming. Today is the most popular choice among other ones like Xamarin and Swift/ObjectiveC but these two are geared mostly towards Windows and Apple mobile operating systems respectively. As for Adobe Flash it was created by Macromedia (remember Shockwave Flash?), which was later bought by Adobe and remained private and closed. Flash applications were wonderful to look at but the technology was completely closed. Some of you may recall that it was Apple who decided to block it completely on iMac laptops due to slow performance issues (so they claimed). That was a heavy blow on Flash. It managed to carry on for a few more years but you don't hear much of it today, instead you have HTML5 and the likes of that to create animations for the web.

It's crazy that this isn't his most viewed video -- this is certainly his best.

I appreciate your every content extremely this one. Thank you for being a good mentor not only in programming but in real life. Salute

As someone just entering into the industry, I really appreciate the pragmatic knowledge shared.

These are all things I learned in first year of programming classes! And now that i am retired, I use Visual Basic because it is very easy to code in, and I don't have to care what anyone else thinks :)

Very valid advice, thanks!

You just saved my 20 years of learning. I will definitely build upon this 12 rules. Thnx Stefan

Great advice! I am starting to learn how to code and after going through your programming rules I feel more free to go with the flow and choose the best technology that's required for my current project or job.

Cool vid. Thanks, Stef!

Amazing advice! Thanks!

Really appreciate you sharing your knowledge in this way. Thank you.

Really solid advice! Thank you!

Stef I'd really like more breakdown of those rules! P.S. This is one of the better (if not the best) video you've made so far on your channel so far!

#5 is the most important to me. I look around and see where the well paying jobs are in my area and that's my favorite language / framework.

Fantastic, loved every point !

Thank you Stefan, your videos are helping a great deal in this torrid journey of learning to code! thank you.

The cat can read my code, even when I can't. But then it never tells me!

Thanks S. :) very useful advices.

thanks Mr. Mischook ...you're putting me on the right track

thank you so much stefan I wrote them down on a paper and put it in front of my desk

In general, I agree with you, but I just wanna point out something about nr 3. Nowadays run speed is also becoming important if you wanna go serverless. If you write the same functionality in 2 diff languages, then the one that runs faster wins when going serverless because you need fast startup and fast response times to reduce costs.

Loved the video. very short and clean. would like to watch more detailed videos about rule 7 to 9. also please put up a video about web interface design...

#0 Don’t Marry Ruby on Rails

Yeah, I totally agree with your list stef. Especially number 1 and honestly, it made me become better I can catch up immediately now.

Yes Stefan do more videos going into the details of each rule please

I like that you just go through the list. Most other YouTutubers take so long to get through a list; you knocked two out in the first minute!

#11 watch every Stefan Mischook's Videos on youtube.

Hi Stef. Priceless video. If only post secondary educational institutions taught these 10 rules, the experience would actually be worth it. Please go into detail for each of these concepts. I hope you make a 10 part playlist of videos where you take a deep dive into each one of these rules.

Some serious wisdom here. Thanks Stefan

Not marrying language is easier than not marrying framework... With all abstraction and magic, sometimes we just feel uncomfortable using another framework even on same language

Thank you for this video, helped alot 👍🏼👍🏼

I totally agree. Fundamentals are the key!

Good information - very practical and at times, even pragmatic. A few of the points are about simplicity being a strength, and that's a major principle in my software engineering philosophy. Other points are about avoiding becoming a software dinosaur or chaining yourself to the Titanic by committing to staying with a language or framework that is heading for the recycling bin.

More details would be very helpful. Love ur vids!

My new favorite code channel besides my own

thanks Stef , i liked your video waiting for the detailed video

Excellent list - 4 will anger some relics who grew up in the 70's and 80's. Use the power to your advantage instead of obsessing over gaining milliseconds of speed out of the code execution; the code will be cleaner as a result because no weird tricks are being done.

guys you need like this vid . kind of bundler for programming.

Thank you very much for sharing, I like your advise a lot I have given you two thumbs up!

solid advice, thank you

Great advice- especially 10

super stuff....love from zambia!!!

Great video sir! thank u.

Your rules work for most developers, but not all. It's all about the balance, and since most devs tend to stay on the other side of the equation (like focus too much on runtime speed), your rules work for them. To perfect the rules, you need to point out the balance point, like how simple is the best, so if someone tries to write more simple code than that balance point, then it is wrong

thanks for your advice, Sir

As a young Web Dev, I think you give really good advices.

Just found out your channel, thanks for the valuable info

Thanks for the list

When you are talking about writing clean code or fine grained code, could you maybe show an example here and there. This would be helpful for us newbies. In any event, great video, thanks for your advice!

really great rules every programmer should learn before writing single line of code 👨‍💻

Hey Stef...as always, great video and a timely topic. As such, I wanted to ask a quick question: I have heard for years from you about "learning the fundamentals" (your first rule).... can you go into a bit more detail just WHAT exactly are the fundamentals of any programming language, since they vary so much? Thanks for your help in this!

Excellent suggestions! Although at an emotional level I feel that some things should be different, but hey, it's hard to change the world.

Great job ! Stefy .. am getting involved in becoming a code writter

These are golden advices 👍🏻

Thanks Stefan!

Thanks for sharing!

I WISH I watched this when it first came out! Golden! So many truths I found out after a lot of hurt!

Great video 👍

So good, I had to share it on Linkedin.

Got to rule 2 and went back to programming ;) Thanks uncle Stef

Tools and technology matter a lot. With full stack coding where you use more than one language, try coding with the 'best' language with an IDE that sucks and you will find out.

Great ten rules!!!

Love your handwriting, Stef.

Hi. Great video. Just discoverd you today and wanted to know if you elaborated on these points in another video because I would love to hear what you have to say about the first one as I'm trying to become a programer. Thank you.

Yep 👍, let’s do more details. Good video.

I like your rules.Simple to understand and apply. Nothing super-genious-made-to-impress stuff. Make more rules,books and courses...

3 years later... These rules are timeless🙌🏻

I love your Big picture opinion on the technology thing thanks

The best yt channel in the industry. I like all of your videos and advices.

welp time for me to refactor function orderAPizzaAndGetAMicrophone() {...}. Great video btw

Hey, I use Delphi (or FPC/Lazarus) when a client wants a Windows GUI App where runtime performance matters. Doesn't have bad write time performance either. But libraries are lacking etc. This is for clients who only care about what a program does, not what I used to write it.

Almost agree with you in all cases except for your emphasizing on speed in programming. It is important to complete a project as soon as possible but it is not as important as developing an efficient program. I really like your videos, really useful, tnx.

This video is great!

Much Love Stefan

I actually wrote this down and glued it to my wall

I agree with #5 but also remember, you don't need fifteen jobs, you need one, make sure it's one you like. I work with an exotic tech stack and wouldn't trade it for anything.

Very informative;