DEV Community

Discussion on: Programmers who only code at work

Collapse
 
xtrasmal profile image
Xander

TLDR: I have several experiences.

I have a reputation of having a very disrupted work/life balance. One could argue that there is no balance and my live is spent behind a computer, with occasional dancing and partying of course :) But my main focus is writing code or just making stuff that I just can't keep inside. I have pain in my left thumb, from making that SHIFT key go down every minute. My shoulders are tense and my knee sometimes hurts like I am 80 years old. That is retarded, but it is not as bad as I paint it with words. SO I WILL PREVAIL!

To come back to to what you are asking... I have seen them.... on the workfloor.... ... ... ... .. .... ..
..... (heavy breathing)...THEM!! AAAaaaaah the horror.

Only kidding of course :) I had good and bad experiences with 9 to 5 programmers.

The regular: I had colleagues who did frontend stuff. Learned some at school and when applying for the job they knew some Angular 1. The did what was expected and we finished sprints. Their code gradually improved, because that is natural.. I hope. At some point you get organised or lost, so trying to get a little structure is helpful. Kicking some design patterns into view and it looks daunting at first, if the colleagues are human and reasonable, they will form their own opinions and it will improve their code.
They went home at 5 and came back in the morning. No stress. This is how most developers live I think. It is just a job, like being a fireman/woman, toiletcleaner, whatever. And it probably is a very good way to think about your work.

The good: One colleague was really open for whatever. I worked hard and was really good. He did not read or play every evening, but once in a while he needed to pick up something in his free time. But in general, he learned and worked at the job. I liked that. Very straight forward and a good problem solver. He liked structured code and did not drink the Kool Aid. He was een independent thinker and not a cargo-culter. I personally like these kind of colleagues. Pretty balanced.

The sad: Another colleague worked at this office for his entire professional career. He thought himself all knowing. He never picked up new things and everything he wrote was just to fix it quick. Cowboy code. The cowboy kicks in the door of the bar, shoots holes in the ceiling, drinks all the booze and takes all the girls. It was horrible. He was the authority in the company, so he put his VETO on everything he did not know.. and that was a lot. So we could not have nice things. Aaargh what a devil.

We need different types of people, because that makes the world a fun and crazy place to be.
Originators, rebels, stubborn cows, slackers, ploughers, regulars etc. Keep it up folks.

It is all fine, except...

Never become the sad or become the passionate developer who forgot that life happens offline.

Everybody in the technical workforce(doctors, dentists, hackers, deepsea drillers, car mechanics, etc) need to keep their knowledge up to date. Do this how you see fit, but make sure that when you move from job to job, that you are still relevant. Be as relevant and useful for your boss/field-of-work at 20 as well when you are 60 years old. You will need to work until you retire.. or marry a rich woman/man.
Stay relevant.. and if you want to freak out on books and techniques.. well go for it and become the teacher or 10x developer people talk about.

10x means that you can make the people around you 10x better.
Don't write all the code yourself. Hero's are bad for the team. You, the passionate one, writes enough code already. Use the things you learned from your passion and help those who can not spend as much time as you become mofo elite h4x0rs :D