Coding Skills NO ONE Will Teach You

only do what you love in this life.....the stuff you talked about comes with that.

Good Moto: Go as far as you can see, and when you get there you can see farther...like driving in the fog.

Really amazing

Thanks

Reading Documentation, no one will teach you that and is really important

Great list.

One ‘habit’ I would suggest is to ‘take an empirical view’. Come up with theories. Do experiments. Disprove those theories. Basically, apply the scientific method. So much of programming is about discovery, not invention. Once you have discovered a way that works, a theory that seems correct, you can experiment to find out why, and iterate towards a way that works faster, less memory, less code etc.

That’s why physicists make the best programmers 😉

A second I would consider, somewhat related to the first, is ‘knowing when to stop’. One of my teachers said to me ‘a program is never finished’. You can always spend more time refactoring, tidying up, adding more tests, trying different libraries or versions of libraries, polishing the code; but in a production environment you have to know when to stop - perfection being the enemy of good enough. And not good enough being the enemy of acceptable.

You have to put a limit on your OCD.

A final one for consideration; the right tool for the job. This could be considered under ‘domain knowledge’? Anyways, this was a favourite saying of another of my teachers. They pointed out that using the right tool can be 100 times faster (in dev time) than using the wrong one. Like if you have a hammer, every problem is treated like a nail. It’s always worth hunting around to see if there already exists a tool for your problem. Eg I once had 85 lines of code replaced by one line of (very cunning) sql. It’s a trade off between time spent looking/asking vs time spent coding!

I can’t help but add a further one. Breadth and depth of knowledge. Spend some time getting to know the full stack. Read about, I don’t know, Networks - how do they work? Databases - how do they actually work, web servers? What’s really going on? If a bug leads you down a rabbit hole to some issue with eg DNS settings or port mappings - take a few extra minutes to find out more about them while you are there - rather than just the absolute minimum to fix what you need. You will be better prepared next time!

Thank you for make subtitle 👍

Nice to see you again Tim.
I enjoy your videos for real.
👍

I think I am the worst when it comes to variable names or values...Believe me.

Thank you so much

The video should be blank as no one's supposed to teach these coding skills

My tip : try to understand the principle not the technique and minimize the scope of techniques but use it efficiently.

The reason : Technique and technology will always evolve but principle is always the same.

and you will,.. such a good boy

I think your content is awesome and I am a beginning coder myself in Python and JavaScript. I just finished the Intro to Programming at Udacity but it gave me enough of a foundation to take things on my own from here. I will always watch your content and I would prefer to master a specific programming language but I’m 40 already and have a long way to go so it’s kinda late for me, but I’m going to go all out as best as I can bc I love doing this more than my full time job. Thanks for your content and any tips would be greatly appreciated.

Informative video. I do enjoy the fact that you get straight into your video without waffling, like many others.

I have 10 years. Started coding with 7

"Knowing when to ask for help on a forum" (and when to keep scrounging for information on your own until your question turns into a different question) is huge. The first time I Actually reached the point where I thought "I can't get any further on my own" & had to sit there formulating a Post about it and got all the way through doing that without realizing there was something else I could look up or test that I hadn't noticed before was a weird milestone, but an important one, I think.

I am great at handling IEDs, but man, I just wanna work in IT.

"nobody will teach you"
proceeds to teach

No one else*

None is gonna teach
Teaches

You teach us

Make a video tutorial about Debugging & Obscure Problem Solving, please :)

Linode needs a permanent free tier, for all accounts. All others offer this. Google gives 300usd + a permanent free tier. Amazon gives 12 months free on some services and permanent free in others. Heroku gives a permanent free tier. Vercel gives a permanent free tier. Same goes for others not listed.
But linode has served me numerous ads instead of providing a generous free tier that would get me to try their service when I have the time and opportunity to do so, and with the pace that I feel comfortable with.

As it stands I'm not even going to make an account with them, cause idk if I will have the time or interest to check out their service in the next 2 months....

Quickly debugging and problem solving is both the first and the last level.

Clicks thks video hoping you will teach me the skills no one is going to teach me: skill number 1 being: Not needing others to teach you. dang/;

1. Focus on the problem primarily, technology and methodology secondarily

2. You are coding for a user (human being) not for inanimate object

3. You don't have god-like powers, you could be wrong so always test your code or your assumptions

"Nobody Teach You", Yeah You Just "Teach Me And Others People"

except you

Need to gain your experience am a jnr full Stack web developer and don't feel even quite as ready

Every time I feel demotivated
I watch Tim's video to get motivated.

Make a video on programming habits.

Great stuff and keep it up!

This video is a paradox.

Another thing I recommend is that EVERY programmer puts 2 weeks of their lives reading about basic electronics like how transistors work, How they form into logic gates, how those logic gates form ALU and registers that your code directly works with. Then learn some basic assembly and do 2-3 small projects purely in assembly. Why? Because this will give you an intuitive grasp to what your code is eventually turning into and makes you learn future concepts better.

Hi tim 🙋‍♂️ i am 35 and i think about a New step i Code for 3 month and want to go to a bootcamp for a job. Am i to old for a new beginning ?

😂That is indeed one of the benefits of getting old you know more stuff and what to do with what you know

I have habit of waking up and getting up everyday. IT IS WEIRD

From Egypt: Very very thankful for this golden advises Tim

Domain knowledge is by far the most important. You can’t make proper decisions when you don’t understand the functional processes the business value. With this whole idiocy around corona and now the energy crisis, I’ve been very outspoken. And people waved away (the now proven arguments) that I’m not a virologist or energy provider. Nope but I developed animal group health analysis software with a virologist and epidemiologist as knowledge consultants. We’ve proven and predicted Corona outbreaks in pig groups with our software back in the late 90s. Some we knew Corona viruses are aerosole driven and not large droplets. And I’ve worked in a startup to supply energy to the grid form greenhouse farmers. So I know how the grids simply and demand must be balanced. And when you start to close gas turbines and gas fields that costs would soar and the grid would be deregulated especially with stupid wind turbines that turn when there’s no demand and so not turn when there’s demand.
And I guess that especially as an engineer you have knowledge that is so detailed and specific that you are a domain expert without the necessary PhD.

Programming habits, variables I don’t care for. A trade of an system/assembly programmer. We don’t have a luxury of names you deal with registers as soon as you load a value from a named (variable) memory location into a register, you need to track the register.
But you see that us systems programmers therefore create very nice small and concise functions because otherwise it is/was too hard to track. And we document our code the best.

Tools efficiency is a good one! It you see me edit on vi people blink. And I’m not even the fastest and most skilled. Same with blender I am of the old skool blender used that could only use keyboard shortcuts. I would’ve even know how to scale or translate if they shortcuts S snd G were removed 😅

Debugging and reverse engineering is a skill. In EE college we were drilled into analytical thinking and learning to ask the right questions. You cannot solve an issue if you don’t have the ability to analytical reason through it. One test was that we had a broken TV or Radio we had to fix in 45 minutes. And the last year it was a nand tree of 12 layers simulated on a PC. And after 2 minutes 2 minutes I wrote down: “there’s no way I can possibly know which one failed without actually being able to isolate them and test each one independently! Because it feeds though! I hand in my paper and shortly after my brother in crime (we were both phreakers and crackers in the same crew) laughed and stood up.
We both scored 10 out of 10. And he actually got me seriously interested in electronics. And I was maybe 10-20 seconds before he stood up to hand in the paper. I believe only 7 of the 23 passed that exam.
And I guess my friend and I were so quick because we had spend 3 years reverse engineering PBXs by just dialing and sending tones without any visual feedback. Our hobby had developed a different sort of mindset.

Domain knowledge :
Knowing the nitty and gritty of your domain. It takes 1000 hours to be an expert in it. It can only come by practicing


Programming habits :
- giving good variable name
- consistent styling
- always write a test
- commit after every small feature
- separating codes into different
functional units

Software & tools efficiency :
- IDE
- Git
- framework
- python module
- Command line and
terminal
Debugging and difficult to understand problems.

you're the chubbier version of Tobey Maguire

So much of what you're saying is found in The Pragmatic Programmer (Andy Hunt and Dave Thomas, 2019), and its good to see the same lessons are coming from multiple sources. When you mentioned learning the IDE so you key-code the features rather than reaching for the mouse and menu reminded me of the tome. Yes Tim you are moving to expert status. Good on you, love your channel.

Hardest thing: Debugging chatgpt generated code

What other skills do you think most programmer overlook when just starting out?