Slashdot Mirror


Do You Like Your Job?

G-shock asks: "I've worked for the government (NASA), large public companies, and small startups as a software engineer. They all have something in common. It seems like management at this company is just winging it. I find myself putting all my energy, both mental and emotional, into a project only to be disappointed by decisions made by management. I really feel like management at my current employer is disconnected from what is actually going on. They manage a project, but not the people. They also seem to lack any real vision. Direction is constantly changing and proper time is not given to engineer these changes correctly. This leads to mandated quick and dirty solutions that end up being maintained with great pain for long periods of time. All this leads to me feeling cynical about the work I'm doing. What I want to know is, how can I feel good about the work I'm doing if I don't have confidence in my management? How many of you are happy with your management? Why? Why not? What can I do about this? Thanks in advance for your insight." Considering that this seems to be a common problem in technology companies, and seeing as we have been producing software for basically half a century, do you think that managing software projects is a different beast than the management of anything else? How many of you have had this problem in your career and what did you do to adjust?

6 of 1,115 comments (clear)

  1. Ex-programmers make the best managers by Tigris666 · · Score: 5, Interesting

    because they understand what is needed.

    When I started at my current job, I was not sure what to expect, being under the assumption that management knows nothing. But later finding out that most of the management here has done some programming before. In fact one of the main managers was the only programmer here when the business started up.

    I believe this makes for the best workplace as a programmer because everyone above you knows how you are feeling. What to expect from you. What is hard/easy etc.

    Atleast that's my view on it anyways.

    --
    Kids, you tried your best and you failed miserably. The lesson is, never try. -- Homer J. Simpson
  2. Simple solution, work for yourself by NewtonsLaw · · Score: 5, Interesting

    I've been working for myself since 1989.

    I always found it incredibly difficult to suffer the incompetence of "managers" who, more often than not, get paid far too much money to do far too little work -- at least that's what I thought.

    Since becoming self-employed however, I have a much greater respect for the time, effort and skill required to "manage" a business.

    In fact, I've deliberately kept my own operations small whenever possible so as to avoid getting caught in the inevitable drift towards management that occurs when you start expanding and employing others. I'd rather remain down and dirty at the coalface.

    One unfortunate side-effect of being self-employed in a fast-moving and highly competitive industry is that you can find yourself working 12-14 hours a day, 7 days a week.

    I haven't had a vacation for over a decade and most years Christmas passed by almost without me noticing.

    This type of thing is okay when you're young and you can survive on 4 hours sleep a night with a constant diet of Coke and pizza -- but I'm knocking on 50 now and it's getting bloody hard.

    Sometimes I dream of retiring to become just another employee. Let someone else worry about paying my salary, keeping the overdraft topped up and filing endless government forms -- I'll just pop in for 8-9 hours a day and go fishing on the weekends.

    If you're thinking of bitching about management, don't forget the old saying "never judge a man until you've walked a mile in his shoes."

    There are some real asshole managers out there -- but then again, there are also some real asshole employees.

    If you're really ticked off -- break away and start your own corporation.

  3. Re:What is your real job? by Jeremi · · Score: 5, Interesting
    One of the best things about my company (and probably the #1 reason I'm still with them) is that they let me release some of my code as open source. This has several nice benefits:
    1. I get to use the same code for my own 'side projects', and will get to use it even after I leave the company. I'll never have to rewrite it! :^)
    2. Having the public see my code encourages me to keep it in tip-top shape, as a matter of pride
    3. The code now functions as a public resume for my skills (better than a resume, because it is actual proof, not just my say-so)
    4. Other people help me debug :^)


    I realize this post mostly just reiterates the parent post, but from the opposite directions.... but I have to say, I'm very happy with the situation.

    --


    I don't care if it's 90,000 hectares. That lake was not my doing.
  4. Re:What is your real job? by infiniti99 · · Score: 5, Interesting

    It all depends on how much money you need, if you need more than $4 a month you better keep your day job.

    Very true. However, I wrote under the assumption that you could just get another job, not that you would run for the hills and code like a hermit. Even a lesser paying job would suffice.. I guess it would depend on what quality of living you are shooting for. Even my friend who works at a gas station makes enough to pay rent. Just because my night job is free software does not mean my day job has to be programming. Hmm, I wonder how many people actually hold non-software jobs, but do free software in their spare time? Sounds like fun.

    I've thought about just quitting my day job and working at the nearby Chili's restaurant. It would be a lot more social than the boring office, and I need to get out anyway. Not to mention there are lots of cute girls there too. :) I could handle it, I think.

    -Justin

  5. Re:Job Board Sites are dead by Squeeze+Truck · · Score: 5, Interesting

    Just as a side note, Japan has a nation-wide government run job database called Hello Work.
    I know in the US "government-run" is synonymous with "piece of crap." Not so in this case. It is detailed and very very comprehensive.

    Basically, it works like this: You find a job via the website or using the touchscreen terminals in the Hello Work offices, then print out the jobs you're interested in (up to five per day).
    You then take the printouts to the office and give them to the people who work there, who then call the company for you and set up an interview with two of the companies you're interested in. Then they give you a card with your info and the company's info on it.
    After the interview, you give the card to the company. The neat part is, if the company doesn't want you, they have to give a good reason why not. This is to help fight job discrimination (especially against women and people over 50).

    I got my current job this way. It's a very pleasant experience, not degrading at all the way I remember it being in the US.

    One company tried to turn me down flat for an interview because I was non-Japanese. The wonderful public servant who was trying to set up the interview for me (Mr. Ikejiri, God bless his soul) actually got angry with the guy and browbeat them into meeting with me. Of course I didn't take that job, but it was cool having someone in your corner.

    --

    "Reactionaries must be deprived of the right to voice their opinions; only the people have that right." - Mao

  6. Programmers can be managers from hell. by igomaniac · · Score: 5, Interesting
    My previous manager was once a programmer (a very bad programmer, I guess). This lead to him
    1. being totally lacking in people-skills.
    2. Thinking he could do every piece of code better than me.
    3. When I disagreed with him on point 2, he would call meetings with the other programmers to 'teach me how to do things'. These meetings tended to be three programmers spending three hours convincing him he was wrong to start with.
    4. He would check out my code when I wasn't looking and 'optimize' it -- that is making it run slower and introduce subtle bugs that I would spend days tracking down.
    5. Finally, when I pointed out his inadequacies as a manager, he got all vengeful and removed all resources from my project, hoping to kill it and get me fired.
    6. When the project succeeded anyway, he took all credit for it.
    7. Now tell me again that programmers make good managers, and I will laugh in your general direction. The best managers I've had knew nothing about programming, but they knew how to ask the right questions (when will it be done, what do you need to do it faster, how can I help you achieve your goals) and leave the programming to the experts.

    --

    The interactive way to Go -- http://www.playgo.to/iwtg/en/