Meetings — look at the itinerary, and if it isn't relevant, say "no".
Technical Debt (Fix it later) — remove technical debt as soon as possible. The only person to blame for technical debt existing and lingering is ourselves (the developers).
Code Reviews — imo, are practically worthless. If you want to do code reviews (because you like doing them, like I actually do), do them informally and after-the-fact of the check-in. Any issues found can be fixed later. Don't have code reviews block the process. But if you want real code reviews, the only options are either paired programming or mob programming — for continuous code reviews. Anything less than that is just gloss code reviews finding nits (curly brace placement and indentation) and typos.
Micromanagement (Lack of Autonomy) — push back on micromanagement. If that doesn't work, then vote with your feet.
Burnout — mix it up. The only person that can make that change happen, is you. If you don't be your own advocate for what you work on, then no one will advocate on your behalf.
Poor Documentation — find bad documentation? Fix it! Find out of date documentation? Update it! Find no longer relevant documentation? Archive it! Find fluff documentation? Delete it! From documentation in the code, to architectural documentation, to API documentation, to system requirements, to end-user documentation, to technology white papers, to product life-cycle documents, to production documents, to process documents.
Unrealistic Deadlines — who made those deadlines? Did you make them? Where they unrealistic to begin with? Well stop doing that! Did someone else make them? Then educate them.
I've never found pair programming to be that great. Too often I'm running through some logic in my head and then the person I am working with, will say "hey what about this", and it throws me off.
And nothing is really stopping them from nitpicking during the pair programming process, they can still say "hey add a new line there".
I do kind of like the idea of just "fixing" nit picks in the review process. If the reviewer sees a typo or a style thing, just append a commit onto the PR and have it merged in.
My latest pair programming were amazing. It depends on how you see and do It.
As a Mid-level I had three jobs, with juniors and with our senior.
With senior level, one was building the backend logics and callbacks on a Kafka consumer environment while another was working on Rails integration and data manipulation sent and received by kafka. We build all together, with little talks between one code and another. Was very prodductive.
With our juniors, I usually allow them do build the whole frontend structure while I build the APIs and backend validations ( Rails, either ). Side by side, without overestimulate or 'build the code' for the juniors, but helping on his doubts. I guess this is, actually, what pair programming is about. And it is freaking amazing for Code Review, Application Testing and validating Bussiness Logics. It all become more approachable and usefull for team.
Pair programming is like programming with a rubber duck. Except the duck talks.
I've done pair programming in short stretches (1-4 weeks), about a dozen times. Those few times were good experiences. The continuous code review in realtime was a huge secondary benefit.
Very often it is not possible to fix technical debt because some choice cannot be made yet, or because all developers are overloaded with other work by their manager. I don't think it is fair to always blame it on the developers.
As for code reviews, I find it very valuable to have other colleagues look at my work. Very often they will see things that I missed, or someone will know of a particular way to solve a problem more efficiently.
I once asked my non-technical manager how I would recover lost files that were not yet in production. His suggestion was to be more careful about what I deleted...
I moved on fairly quickly after that.
I feel like tools can help to address these issues but also important is the culture change needed to even recognize there's a problem worth fixing. I feel that's often the biggest challenge.
How would you go about making a case for better documentation for example? Say to someone who believes gut feeling and asking so and so for help is a better approach?
Born in 1961 and live in Hamburg. Software developer for 40 years. Current project: myway SQL Manager for MySQL and MariaDB in PHP, Javascript and SQL.
Bei einem meiner Jobs war tatsächlich das mental anstrengendste: Nicht bei den Meetings (Monologen) einzuschlafen. Fast so anstrengend, wie sich dann durch einen Fremdcode zu wühlen, der nach den dort festgelegten Konventionen erstellt wurde und in dem jeder Variablenname aus einem Roman bestand.
Senior Full-Stack Software Engineer with over 6 years of progressive experience in the full software development lifecycle. I specialize in building secure, scalable multi-tenant web platforms .
It starts by saying 'no' but explain why you say no. For instance a meeting that you're invited to but you know you will only be a listener. You can probably decline. With introducing technical debt you should say no when you know it will cost al lot of effort to fix later. If they insist ask for an email confirming that they want to introduce the technical debt so that you are covered and decisions have a paper trail. These two will already help a lot to gain productivity. (25+ years of dev experience)
Great post! There are so many day-to-day activities that might be necessary and helpful, but by not managing them correctly they can really affect our productivity and overall performance
Hi, I’m Kudzai — a passionate African tech builder, full-stack developer, and digital problem-solver.
I create modern applications that make life easier for real people.
I'm a skilled Content Writer and Digital Marketer who blends creativity with strategy to craft engaging content and drive successful marketing campaigns. I'm a photographer by hobby.
Hmm ideally you want to catch such a cowboy before they make the pull request though. In my opinion code reviews should be a way to collaborate and not a means to catch unwanted behavior. Unwanted behavior should be prevented by using linters, or in the case of your redux cowboy, during work planning...
We're a place where coders share, stay up-to-date and grow their careers.
I've never found pair programming to be that great. Too often I'm running through some logic in my head and then the person I am working with, will say "hey what about this", and it throws me off.
And nothing is really stopping them from nitpicking during the pair programming process, they can still say "hey add a new line there".
I do kind of like the idea of just "fixing" nit picks in the review process. If the reviewer sees a typo or a style thing, just append a commit onto the PR and have it merged in.
My latest pair programming were amazing. It depends on how you see and do It.
As a Mid-level I had three jobs, with juniors and with our senior.
With senior level, one was building the backend logics and callbacks on a Kafka consumer environment while another was working on Rails integration and data manipulation sent and received by kafka. We build all together, with little talks between one code and another. Was very prodductive.
With our juniors, I usually allow them do build the whole frontend structure while I build the APIs and backend validations ( Rails, either ). Side by side, without overestimulate or 'build the code' for the juniors, but helping on his doubts. I guess this is, actually, what pair programming is about. And it is freaking amazing for Code Review, Application Testing and validating Bussiness Logics. It all become more approachable and usefull for team.
Pair programming is like programming with a rubber duck. Except the duck talks.
I've done pair programming in short stretches (1-4 weeks), about a dozen times. Those few times were good experiences. The continuous code review in realtime was a huge secondary benefit.
You have a point
Very often it is not possible to fix technical debt because some choice cannot be made yet, or because all developers are overloaded with other work by their manager. I don't think it is fair to always blame it on the developers.
As for code reviews, I find it very valuable to have other colleagues look at my work. Very often they will see things that I missed, or someone will know of a particular way to solve a problem more efficiently.
Could add poor tooling to the list. I work at a company that doesn't even have source control, on top of most things you mentioned.
I once asked my non-technical manager how I would recover lost files that were not yet in production. His suggestion was to be more careful about what I deleted...
I moved on fairly quickly after that.
That's a also a valid issue.
I feel like tools can help to address these issues but also important is the culture change needed to even recognize there's a problem worth fixing. I feel that's often the biggest challenge.
How would you go about making a case for better documentation for example? Say to someone who believes gut feeling and asking so and so for help is a better approach?
Bei einem meiner Jobs war tatsächlich das mental anstrengendste: Nicht bei den Meetings (Monologen) einzuschlafen. Fast so anstrengend, wie sich dann durch einen Fremdcode zu wühlen, der nach den dort festgelegten Konventionen erstellt wurde und in dem jeder Variablenname aus einem Roman bestand.
Thanks for sharing
How do you overcome a lack of productivity?
It starts by saying 'no' but explain why you say no. For instance a meeting that you're invited to but you know you will only be a listener. You can probably decline. With introducing technical debt you should say no when you know it will cost al lot of effort to fix later. If they insist ask for an email confirming that they want to introduce the technical debt so that you are covered and decisions have a paper trail. These two will already help a lot to gain productivity. (25+ years of dev experience)
Good idea to avoid those situations. Everybody should learn to say "No".
Great post! There are so many day-to-day activities that might be necessary and helpful, but by not managing them correctly they can really affect our productivity and overall performance
Absolutely! It's remarkable how the little things that we might even ignore or not considered them as unproducitve can hinder our productivity.
This is a great list! Can I add just one thing?
Thanks a lot!
Good to know information's, Thank you.
I need to add missing leadership and resulting unclear requirements.
Hmm ideally you want to catch such a cowboy before they make the pull request though. In my opinion code reviews should be a way to collaborate and not a means to catch unwanted behavior. Unwanted behavior should be prevented by using linters, or in the case of your redux cowboy, during work planning...