Coding Skills NO ONE Will Teach You

Welcome back to another video on my channel! In this video I am going to be sharing with you some coding skills that nobody can teach you! What I mean by that is these are going to be things that you can't learn from a book or a YouTube video. These are things that require hundreds if not thousands of hours of practice and that you have to build over a career of coding. Please enjoy the video!

⭐️ Timestamps ⭐️
00:00 | Overview
01:08 | Sponsor
02:00 | Domain Knowledge
04:49 | Programming Habits
07:22 | Software & Tools Efficiency
09:57 | Debugging & Obscure Problem Solving
12:09 | Conclusion

◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️

◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️

⭐️ Tags ⭐️
- Tech With Tim
- Coding Skills
- Things People Don't Teach You
- Good Coding Skills
- Programming Skills

⭐️ Hashtags ⭐️
#TechWithTim #CodingSkills

[TechWithTim]

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

[YossiZinger]

I can't stress enough how important it is to create readable code. I've known extremely talented programmers who could write an entire service as a one-liner with all those nifty inline operators. When they moved on, and someone else took over their code, it was a disaster.

[ChessQuickies]

Title: *Coding tips no one will teach you*
Tim: *Teaches us those coding tips*
Thanks, great video

[ohwow]

Also learning how to learn efficiently. It's something no one teaches you and you have to work on it and get good at it.

[TheDavidlloydjones]

2:11 "Domain knowledge": knowing about the real world in some area you're interested in; e.g. Microsoft's own products for people who work at MS; real estate if you're in real estate... In Tim's case, Python knowledge gathered while using it.
4:53: Programming habits. "subconscious" skills. E.g. giving good names to variables. Having consistent style. Writing tests.
7:25: Software tools and efficiency. Use of IDEs, libraries, version control, command line usage, knowledge of frameworks and modules.
9:57: Debugging and obscure problem solving: Time believes there are a class of bugs connected with cross platform frameworks. The skill? Being aware that some bugs will not conform to usual paths, perhaps.
Coda: Have faith: it's going to get better.

[mmkamalraj]

Ask for help is one important skill Programmers lack. Depending on stackoverflow, books and youtube vids are fine. After that ask your friends, colleagues and those around you too. TWT has been really inspiring, and info rich. Keep up the great work.

[CornishMiner]

Choosing great variable names isn't always easy but it is SO worth it. If done well, the code just comments itself.

[kittipongpiyawanno]

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.

[MrBonesbr]

In my view, "domaing knowledge" is to know about the market specifics of what you're working on. For example, I work in a Real Estate Fintech Startup, so the domain knowledge here is knowing about Real Estate market specifics. I actually think that, in some cases, it is better to have a Junior programmer with Domain Knowledge over a Senior programmer with no knowledge of the market the company is in

[dovedozen]

"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.

[fusionsid]

bro be turning into linus tech tips with that smooth sponsor transition

[joey]

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.

[davidskaggs]

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.

[sherlock_]

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.

[codexed-i]

I have 10 years. Started coding with 7

[CallousCoder]

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.

[CallousCoder]

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.

[CallousCoder]

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.

[becolex]

Love the video, great idea to become better programmer. My habit is giving 5 lines of space separating classes, statements, functions and adding a comment if needed it makes it easy for me to read and jump around

[CallousCoder]

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 😅