DEV Community

Cover image for The Secrets behind highly effective programmers

The Secrets behind highly effective programmers

Abdullah Alhariri on October 31, 2021

Being a programmer requires much more than the simple act of sitting at a computer looking for solutions through Stack Overflow. To be a programmer...
Collapse
 
mtrantalainen profile image
Mikko Rantalainen

Good article, but let's be honest, 7 hours per day for screen time is not nearly enough for most software developers.

I've been doing some bodyweight training and it has saved me from shoulder and neck pain that I used to have. Sometimes I find myself being "in the zone" for 5 hours straight but then I feel like doing some pull ups and archer push ups or pistol squats for a few minutes to get my body to work, too. The good part with body weight exercises is that you don't need equipment (I do have a pull up bar a couple of meters from my workstation, though, and it helps to avoid procrastinating pull ups because I can do 5-10 on my way when I go to bathroom or get something to eat).

Collapse
 
thomasvanholder profile image
thomasvanholder

Exactly! Staying in the zone with a break every hour seems contradictory for me. Once you are in it, it’s so easy to keep going.

What helps me is to do stay physically health is to do some non-coding activities after work, like go for a run or long-walk.

Collapse
 
dpereira profile image
Diego Pereira • Edited

If you can't break down the work you are doing in 1h-2h chunks, you probably haven't thought out an overall plan and shouldn't be coding away like crazy anyway.

Being "in the zone" for more than 1h, at most 2h, means you are just lost without an actual plan on where you are going and how to get there.

Thread Thread
 
mtrantalainen profile image
Mikko Rantalainen

I would say that it depends. There are tasks that are straightforward but simply need more code than you can type in 1-2 h. Recent example for me was porting existing code to a new backend architecture. I had automated tests with 100% coverage so it was easy to see any problems and I was constantly aware of the failing parts of the code.

Thread Thread
 
dpereira profile image
Diego Pereira • Edited

I wouldn't use "straightforward" then. And if it is not, it probably could be broken down in smaller chunks.

Collapse
 
piyush181 profile image
Piyush Raj

Very well said, I completely agree

Collapse
 
abdullahalhariri profile image
Abdullah Alhariri

thank you

Collapse
 
awohletz profile image
Ayron Wohletz

I will add that getting good sleep is crucial for any kind of mental work. If I don't sleep well then it's hard to concentrate the whole next day.

Collapse
 
imasterzed profile image
ImasterZed

Hey man, Your article was awesome!
I translated it to my language and shared it with your name and added a link to this page, and again, Thank you very much

virgool.io/@MasterZed/%D8%B1%D8%A7...

Collapse
 
abdullahalhariri profile image
Abdullah Alhariri

The article looks awesome, thank you 🌹

Collapse
 
shadid12 profile image
Shadid Haque

Could not agree more. Hats off

Collapse
 
abdullahalhariri profile image
Abdullah Alhariri

thank you

Collapse
 
ashleyjsheridan profile image
Ashley Sheridan

I think the "showing off" part can depend on your and their level. Code that is hard to read isn't immediately someone showing off, it might be that it's following a standard for that framework/language that might not be very obvious to someone new to it. I feel that way when I'm learning a new language, and come across something that's very particular to that language that looks unusual.

The exception is regular expressions. I think most people who use them are showing off :P

Collapse
 
virtualmachine profile image
ByteCodeProcessor

Nice article. Especially the one on spaghetti code. I would have to work on the "asking others for help" part. 11/10 article

Collapse
 
abdullahalhariri profile image
Abdullah Alhariri

thank you

Collapse
 
gtobar profile image
Guillermo Tobar

I agree with you, thanks for writing the post.

Collapse
 
33nano profile image
Manyong'oments

Nice article and definitely highlights some great points, especially the point of taking care of ones own system.

Collapse
 
abdullahalhariri profile image
Abdullah Alhariri

thank you

Collapse
 
joycelee11 profile image
Joyce Lee • Edited

Know when to ask for help

This! Couldn't agree more. Know when and how to ask for help sounds easy, but I've found it really takes practice to get good at.

Collapse
 
yashiroquy profile image
UMR

me working as a developer for 1 year and get varicose vein.

Collapse
 
worldtok4u profile image
Emmanuel David

I doff cap for u on the case of asking others for help. I find it difficult as most of my colleagues are not always around for that.

Collapse
 
chautien profile image
Chau Tien

thank you for article

Collapse
 
viral7chauhan profile image
Viral Chauhan

Great article, Programmers should focus on physical/mental health for more productivity.