1–10 of 52 posts
I don't know what an acceptable level of programming productivity is; I just feel as if I am 5-6 times slower than when I started.
Should I commit seppuku (this feels like the most honorable thing)? Should I renegotiate to take long unpaid breaks (this should revitalize me)? Am I panicking too much (I always panic too much)?
If you are asking this all seriously, then yes, you are panicking too much. Calm down.
Talk with a superior candidly about the situation. Taking breaks is not going to solve things if it is the project you don't like. Something about what you are working on/with is what needs to change.
How about a new project, a new job or find a way to make this project interesting (i.e. use a new approach, a new language, switch tasks with someone else working on the same project). Anything!
Is your career progressing? Have you accomplished anything in the last year that you'll put on your resume? Yes? Good, continue. No? Consider other options.
Is the project proceeding? How does your manager feel about your work? Good? Maybe it's a perception problem on your part. Anxious? Perhaps you're not being applied well and should be moved to a different project within or without the company.
Things checked out OK so far, but you're still not happy? Perhaps you should consider trying to flip your role in the company to something that would be more beneficial to both you and the company.
My productivity plummets during certain phases of projects. If you're feeling that way perhaps you just need to get past a milestone onto a better or more interesting task.
Don't panic about it! Some corporate structures can withstand an almost malicious amount of unproductive behavior; in fact, managing the spectrum of productivity is in large part what corporate management is about. That said, don't abuse it -- long term it will definitely hurt you more than them -- but think of it as productivity insurance while you figure out how you can succeed.
Here's what you need to remember: the difference between a professional and an amateur is that a professional comes and in and delivers work they'll stand behind all the time, whether it's fun or not. You are always going to work harder and faster when things are fun. Things are not always going to be fun. If you're a pro, you're going to keep going regardless.
Obligatory essay (not that they've set the world on fire either, but the sentiment is good): http://www.joelonsoftware.com/articles/fog0000000339.html (Fire and Motion).
Best of luck.
This happens to everybody. I think I've commented on it here before: a lot of nascent entrepreneurs here appear to be working under the delusion that they'll redline at their peak productivity levels throughout the lifetime of their startup. Here's what you need to remember: the difference between a professional and an amateur is that a professional comes and in and delivers work they'll stand behind all the time, wh…
Somehow I always thought that no-one else had this problem. Seriously.
I hope I can finally give up my youthful arrogance. I always believed that when people spoke about getting experience they meant learning more about writing software (and how I scoffed at that). But it's just as much, if not more, about learning how not to turn around and run away.
That doesn't mean quitting immediately (and potentially jumping into another bad situation).
Rather, start making inquiries (either internally, at other companies, or start your own) and see what else you could be working on.
Just don't accept the idea that "work/life sucks, get used to it" as that's the surest way towards becoming a drone.