Live data from Hacker News

I’m a Bad Developer, That’s the Only Reasonable Explanation

medium.com

61–70 of 130 posts

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#61
I got the "you're a bit slow" once. Which was funny, because I was very focused and felt very productive at that time —more than ever before. Plus, some of my code allowed a business expert to contribute directly, which made us even faster.

I have since realised it had nothing to do with my actual performance. It was a people thing.

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#62

I've had similar self-doubt in the past, I considered myself fast but sloppy. I changed my opinion after a workshop on different team roles at my previous job. A lot of it was boring workshop fluff, but I loved the core message: that many personality traits aren't purely positive or negative. Perfectionists are nitpickers. Fast developers are sloppy. Experienced ones overthink stuff. Bleeding-edge evangelists ruin lo…

I consider myself meticulous but slow. My coworker and I often talk about he differences and I always have wish I cared less about certain things and prioritized time more while he likes hat I focus heavily on maintainability and clarity.

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#63
One general piece of advice that stuck with me after reading "Feeling Good: The New Mood Therapy" (a cognitive therapy book) is to refrain from thinking in inherent categories about myself. Thinking "I'm a slow developer" is just depressing and sad - there is nothing much you can do about your inherent flaw. By contrast, thinking "I've done this task slowly" puts you in a problem-solving mood. Something like "Wow, I've actually shipped, that's great! Now, it took me a bit more time than I've anticipated. Does it really matter? If it does, what can I do about it?"

Also, a lot of this is just management trying to put pressure on the devs using methods more appropriate for a kindergarten. I vividly remember my former boss telling me "you are going to put down the team and have a bad conscience if you don't finish this feature on time" (an arbitrary deadline caused by a looming performance review). He was a good boss, but I would have more appreciated an honest "look, I'm trying to get you a raise so finishing this feature by this date is in our mutual interest" without any kind of moralizing shit.

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#64
Most people cut corners. They deliver crap, fast. But when you add the time needed to debug that crap, to refactor it, was it really fast? Of course managers don't track time over the whole life of a feature...

- So it says in your CV that you are quick at math.

- Yes. Yes I am.

- How much is 23 times 14.

- 7!

- That's not even close!

- No. But it was quick!

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#65
The labels of good/bad developer are not useful - just as we try to optimize the perf of our code, we should be focused on optimizing the things we can. For example, figuring out some answers to questions like "How can I get to this conclusion faster on figuring out bugs like this", or "How can I figure out the optimal architecture for this feature faster?" Putting things in front of us that are in our control and actionable is the best we can do.

One has to break the block of being afraid of failure - we all fail at various tasks. The important part is how we respond to this failures.

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#66
post #45

Earlier quoted context omitted.

Is self doubt ever about being bad at something?

Sure, sometimes it is. When I doubt my career skills, I can (usually, eventually) recognize it as insecurity / impostor syndrome / whatever. When I doubt my dancing skills, it's a rational evaluation.

It sounds like what you're doing is accurately assessing your lack of dancing skills, not doubting your dancing ability. A hallmark of self-doubt is the nagging unknown, a questioning, a debate that goes on in one's head as to the real truth of the matter. I'd bet such a debate doesn't exist about your dancing given the rational part you mentioned. If it's actually a correct, accepted, rational evaluation, then what you have is self-fact: I can't dance well; rather than self-doubt: I'm not sure if I can dance well. The rational evaluation part eliminates the doubt once it's accepted, as you've arrived at a rock-solid conclusion.

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#67

I've had similar self-doubt in the past, I considered myself fast but sloppy. I changed my opinion after a workshop on different team roles at my previous job. A lot of it was boring workshop fluff, but I loved the core message: that many personality traits aren't purely positive or negative. Perfectionists are nitpickers. Fast developers are sloppy. Experienced ones overthink stuff. Bleeding-edge evangelists ruin lo…

Often the people judging us as good or bad are idiots that know nothing of what we do.

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#68

I've had similar self-doubt in the past, I considered myself fast but sloppy. I changed my opinion after a workshop on different team roles at my previous job. A lot of it was boring workshop fluff, but I loved the core message: that many personality traits aren't purely positive or negative. Perfectionists are nitpickers. Fast developers are sloppy. Experienced ones overthink stuff. Bleeding-edge evangelists ruin lo…

I consider myself meticulous but slow. My coworker and I often talk about he differences and I always have wish I cared less about certain things and prioritized time more while he likes hat I focus heavily on maintainability and clarity.

If traits have downsides and upsides, we get used to the upside and yearn for solving the downsides. In this yearning, we almost wish to give up our strengths so as to alleviate our weaknesses.

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#69
post #43

Earlier quoted context omitted.

Such bold conclusions from 900 words and a single perspective. Isn't it possible that the author is, in fact, not good at the job?

People who are bad at their jobs usually fall into two categories: a) people who lack the insight to realize it, and thus don't work to fix it b) people who realize it but don't care (for various reasons, some valid some not) If you're agonizing over your job competence and trying to improve but feel you aren't succeeding, then it's vastly more likely that either your job specification is impossible, or you're settin…

I'm really bad at basketball. I have to insight to realize this, and I tried to get better. I really cared about getting better. But at the end of the day, I am not athletic. Sure, I can devote time and energy to improving my basketball skills, but I will never achieve anything beyond 'mediocre'.

There's also a chicken and the egg issue here; perhaps the author really does not enjoy coding and thus is not willing to put in the effort to improve?

Re: I’m a Bad Developer, That’s the Only Reasonable Explanation

#70
I was challenged by my bosses at my last job because they were concerned about overall team productivity (including mine... mainly because I spent some additional time refactoring and creating better testing tools, because those were necessary and coworkers reported them as cool and labor-saving) and they put us in a "bataan death march" mode without a definite ending (...) and I pushed back and said this is bullshit because what these metrics I took say is that we need to be paying down some tech debt, stat.

I ended up leaving. Sometimes, the job is too good for you, and sometimes you are too good for the job.

Post reply on HN