Why Developers Get Fired
jammag writes "Other coders get canned — but never you, right? From a developer who's now a manager (and who admits to being fired himself) comes the inside story on how the Big Ax might sneak up on you. To prevent it, he recommends some strategic bragging, keeping a CYA (Cover Your ...) folder to document your efforts, and making sure that your talent isn't frittered away so much that even your most mediocre colleagues look good. "
However, some people truly have their heads buried in the sand (or their code).
Yes, imagine the shock and horror that you would see on people's faces if I spent my time doing what I'm getting paid to do: develop code. Yes, I'm young. No, I've never been fired but I've been "hired then unhired" out of college because of a poor job environment in the locale of my origin. No matter, plenty of jobs were out there for me.
Spiegel claims he's fired people. I wonder how he would have chosen people if he saw through an employee's thinly veiled attempts to make himself look better? Or if he knew that employee spent time trying to cover his or her own ass instead of -- you know -- just get work done? These points aren't addressed in the blog.
So for those of you reading this, I will offer you an alternative to what the blog suggests. I imagine most developers (even agile developers) have a system for tracking completed requirements and also for fixing reported errors/bugs. If you spend your time chewing up those outstanding items and forget about all this near-Machiavellian bullshit manipulation Spiegel is proposing then you've got nothing to worry about. If your manager wants to fire you, just pull up the numbers if he or she hasn't already and show them. You can't fire a developer that's leading in resolutions and completed requirements. It's that simple. Skip the drama and get to work.
My work here is dung.
I'm a former programmer, now a manager. Recently, we had to cut some dead wood. I went through all my employees and asked myself, "Would I hire this person?" (I didn't hire any of them in the first place). In many cases, the answer was no. Either they shouldn't have been hired in the first place (previous manager was borderline incompetent), they didn't work out as well as expected, or they had attitude/personal problems that outweighed their contributions.
I got laid off in 2002 specifically because I was vocal and did my best to try and make for a better work environment. The problem was that management was TOO political. The parent poster is 100% accurate. After that I learned, never to be vocal. Give simple opinions and never give negative feedback, or try not to do so.
Too true. I work at an IT consulting firm and my boss pretty much told me flat out that I'm going to be in some serious shit if I don't start dragging my feet to bill clients more hours. Apparently I'm too productive and don't over bill. I called my boss to ask him a question about a task I was going for a client one day - 10 minute phone call (maybe 6 minutes of it being the task at hand) and he bills the client for an hour for "assisting me". Now I'm just waiting for the economy to pick up so I can get a new job.
"The tree of liberty must be refreshed from time to time with the blood of patriots and tyrants." ~Thomas Jefferson
Good article generally and good advice. But for a US audience.
"For those who donâ(TM)t see it coming".....here in New Zealand would earn the employer a death sentence in Employment court (well, a large settlement anyway).
NZ law states broadly 2 key points: That there is a relationship of good faith between employer and employee, and that both parties act in a fair way.
examples from both sides:
For the employer:
- Theft by an employee is grounds is grounds for instant dismissal
- A drop in income that requires a restructuring process when some employees might be shed.
For the employee:
- A drop of productivity can be due to various reasons. The employer must determine what those reason are. And instigate a prodedure policy known by both parties. The No.1 rule is "no surprises" to the employee.
- Numerous instances of Case Law indicate the employer must act to prove in a fair way they are right(they are the ones with the resources). For example , allowing one employee to arrive late but then enforce it on another first time late person would show lack of process and earn punitive penalties in employment court.
In post Patriot Act America, the library books scan you.
I am simply amazed at the level of vitriol and naivete displayed in these posts. The article basically boils down to "you are your own best advocate." Of course management's perception of your performance is what keeps you employed when the economy is tough. Duh. The article says to back up your arrogance with facts and not to let your own perception of your value lull you into a false sense of security. Doesn't seem very evil or unethical to me!
My question is why do good developers, that are talented get laid off?
Only 'flamers' flame!
Does slashdot hate my posts?
India is way too expensive. How you can possibly compete by making software in India? You should really consider moving development to east Asia.
“Common sense is not so common.” — Voltaire
No, it's not fair today. In fact, in most states employment is "at will", which means among other things that if you aren't a member of a protected class of people (and often if you are a member of a protected class) you can be fired for any reason at any time. And therein lies a large part of the problem.
Cops and teachers both have a very significant tool to protect themselves that developers as a rule lack: a union. Yes, I know, a lot of folks think of union regs as pile of bureaucratic BS, and unions as a bunch of corrupt jackasses (sometimes true), but the simple fact is that unions are very frequently a big net benefit to their members. Unions, for instance, are a primary defense that cops and teachers have against unpaid mandatory overtime.
Nurses right now are protected by the low supply and high demand, much like developers were about 15 years ago.
I am officially gone from
When you're employed, try living below your means and saving the surplus. Amazing how much less of a panic losing your job is when you have $10-20K socked away in a bank account. Now you have several months cushion to search for another job; you don't have to leap at the first thing that turns up, no matter how bad. You don't have to panic, and you don't have to live in fear at your current job that you might get laid-off unexpectedly.
Seriously, it's too useful to have a cash reserve for emergencies. Start a savings account.
---dragoness