Avoid This Common Programming Mistake!

What is something that a lot of programmers do, that is causing their programming output to drop? In this video, I'll explain one of the most common mistakes that programmers make, that results in getting less code written, than you potentially could have written in a given timeframe.

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

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

⭐️ Tags ⭐️
Programming, Programming Mistakes, How To Write Code Faster, Coding Mistakes

⭐️ Hashtags ⭐️
#techwithtim #shorts

[DutchGio]

If I have an issue I always make it in smaller issues, like designing the database, ordering the priorities etc. Helps me a lot.

[rushas]

The thing is that if you're the only software developer in your company that is not directly in the tech industry, you will be given huge tasks and be expected to do everything by yourself from 0 to the end.
The board will not care about the code quality, nor they will care about the robustness. The one and only metric will be the delivery / due date.
So while "jumping straight to the coding" might seem tempting at the beginning, thinking ahead, planing and then starting to code will save you time in the long run. I agree with the OP: if it's a complex project, always think first, prioritize then get in action (coding)

[hollowses]

Personally, i think about how to write something while I'm on a break or not coding, then hyperfocus to write it and get it done as efficiently as i can make it out to be.

[HakeemAlimi]

Absolutely right. Breaking down of problems into sub components and solve them one at a time

[abdullahisiaq]

Thanks a lot for pointing that out, really true

[aymensaadoon]

You’re very right. I’m like that rn. Where I code for 30 min then think about my code for 30 min and I keep switching so it gets boring and I stop all together.

[trentonstarkey]

I’m no real programmer yet, but I’m doing CS50, and what you’ve described here tremendously helps me get through things. Having a separate time to think about design requirements and use pseudo code to get a general workflow really helps eliminate the brain fog during actual coding time.

[henriquev]

And it's not only about programming, it's a useful way of thinking about a lot of things in life

[tanglesites]

Facts! I am learning to get the requirements, user stories, event storming, model design out of the way first. Coding goes faster after that.

[NicBob]

Context switching kills productivity in all aspects of life - it’s also quite tough to overcome. A good to do/ task list that you stick to helps a lot!

[EmilHagbarthRasmussen]

I usually do a high level design. Write a quick version of that. Then redo the design to fix all of the wrong assumptions I had before, and write it proper.
The upfront process isn’t that important for single person productivity, but very important for communicating with your team, designers etc about what you’re trying to build.

[yousufsalalah]

Thanks man, coincidentally I was yesterday looking for the full video and today I got a short from it.

[dpsheals]

I’ve only been coding c and JavaScript a few months after a few weeks of html, and css. And it is easier for me to brainstorm and write out my thoughts and code first before coding it. Thanks for the advice

[zach]

I personally like to jump into the code it helps me get ideas if I just sit down and think about it not a lot comes to me

[Im-mustafa-saeed]

Bro you literally described me, thank you for making me notice the problem

[alexi_space]

That's true, My fastest project I made with requirements, high level process, some db structures on paper, then I broken it down to smaller pieces and I finished within around 3 weeks afterhours from scratch.

And when I do a project without it, then I'am very often get stuck

[tntg]

We used to say in a previous team "2 days of dev saved us 30min of planning" which obviously means the exact opposite when we started coding without taking the time to conceptualize.
That goes for everything you do in life.
Planing should always proceed doing. Otherwise you are up for a bumpy ride

[thethricegreat]

My old Sgt: "Planning and execution don't mix."

[FireChronos]

I saw a technique a while back where you would write out pseudocode to be your comments and then fill it in with actual code. Seems like that could be helpful in this case.

[BenRogersWPG]

When the thinkin/reading guy put his hands on the laptop keyboard, his hands lined up perfectly with the upvote/downvote buttons and I thought it was pretty cool