3 ms·

I'm curious about the "high throughput" part of your comment. Does that mean rapid development? Lots of lines written? or what? I find the older I get, the slo

I'm curious about the "high throughput" part of your comment. Does that mean rapid development? Lots of lines written? or what? I find the older I get, the slower I produce code. I spend more time thinking about the solution than coding the solution. This tends to frustrate my employers, who follow the "move fast and break things" philosophy. They think I shouldn't have to think about it, just do it. So, I guess what I'm asking is, in your opinion, is my slowing down a problem? Or an advantage?

MacsHeadroom 13y ago
It's a problem if you want to be on a team, especially one that does rapid development-- which is most/increasingly more of them from what I can tell. Freelancing might suite someone like you very well though. The best freelancers write solid software at the pace that works for them.
- bandushrew 13y ago
  " team, especially one that does rapid development-" sorry, what? any team that thinks "rapid development" actually means writing code more quickly is a team composed of idiots - I think I must be misunderstanding you?
bermanoid 13y ago
If your code ends up coming out the other end with fewer defects and ends up costing the company less overall than when similar tasks are done by your peers, then document that and present it to your bosses. If it's incurring a similar bug load and just gets done slower, that's a problem and they're right to be upset. I've seen both cases before, even from very experienced people, so it's very specific to the situation.