Slashdot Mirror
Software Exorcism
Mark Burroughs writes "Leave it to a SubGenius preacher to take normally mundane subjects, like software maintenance, and expose the unholy conspiracy behind them. I think the following quote from the introduction sums up the tone of the book nicely: 'Rather than shield your eyes from the sordid realities of the software industry, I am going to dust off my old 8mm films and let you take a good look at the uncensored truth for yourself. You may want to keep a paper bag handy in case you get sick.'" You know you want to read on for the rest of Burrough's review.
Software Exorcism
author
Right Reverend Bill Blunden
pages
351
publisher
Apress
rating
two thumbs up
reviewer
Mark Burroughs
ISBN
1590592344
summary
Tactics for Maintaining Legacy Code
Reverend Blunden's sermons focus on things that the college professors, in their tweedy jackets, will never talk about. As such, this book should be required reading by computer science majors, who often have a number of misconceptions concerning the industry that they are about to enter.
I doubt very highly that your instructors will tell you how to handle all the nasty little things that can occur when humans work in groups: backstabbing, stonewalling, sabotage, etc. The sad truth is that the people who do actually learn about these tactics (under the guise of "organizational behavior") are MBAs, the people who end up being managers. Folks, the deck has been stacked: The MBAs have been given whips, and the CS majors have all been given saddles. It's called animal husbandry; ... now go look up the word "cull."
Glancing at the back cover of the book, Reverend Blunden looks like the type of subversive individual that the ATF would like to have a chat with. As such, he is not one to let the reader leave without a few useful weapons (some of which may be questionable from a legal standpoint ... but hey, business is war). For example, the book tells you construct a paper trail so that even the shiftiest weasel cannot switch sides if it's suddenly convenient. Reverend Blunden even goes so far to refer the reader to a vault purveyor in New York so that evidence can be stored securely at home (hint: it's sure as hell not safe at the office). Don't kid yourself; a solid paper trail can save you during a witch-hunt.
The book also looks at how to deal with legacy code in situations where internal competition has encouraged people to hoard information, or to escape responsibility via promotion (i.e. VPs have been known to develop amnesia about the code they worked on). It explains the forces that cause these shenanigans to occur and then describes how to flush the guilty party out into the open, where their slimy tactics won't work. As before, generating a trail of evidence and possessing a degree of intellectual humility go a long way.
Then there is privacy, an issue that employers will definitely try to skirt. Management types tend to be keen on metrics to measure productivity. In addition, software engineers typically have access to code, or algorithms, that may be considered proprietary secrets. This has led many companies to monitor their engineers in some way or another (i.e. key loggers, remote desktops, sniffers, TEMPEST, etc.). Reverend Blunden provides a couple of easy, but extremely effective, counter tactics that the reader can use to foil this kind of Big Brother antics.
At the end of the day, Reverend Blunden tells it like it is. He hasn't been bought off and he doesn't have an agenda. His only goal is to warn new hires about the various landmines that exist, buried under the polite exterior of the corporate landscape. You may not like what he has to say, but no one ever said that software engineering was a pretty job. If they did, they were telling you a lie. Praise Bob.
Reverend Blunden's sermons focus on things that the college professors, in their tweedy jackets, will never talk about. As such, this book should be required reading by computer science majors, who often have a number of misconceptions concerning the industry that they are about to enter.
I doubt very highly that your instructors will tell you how to handle all the nasty little things that can occur when humans work in groups: backstabbing, stonewalling, sabotage, etc. The sad truth is that the people who do actually learn about these tactics (under the guise of "organizational behavior") are MBAs, the people who end up being managers. Folks, the deck has been stacked: The MBAs have been given whips, and the CS majors have all been given saddles. It's called animal husbandry; ... now go look up the word "cull."
Glancing at the back cover of the book, Reverend Blunden looks like the type of subversive individual that the ATF would like to have a chat with. As such, he is not one to let the reader leave without a few useful weapons (some of which may be questionable from a legal standpoint ... but hey, business is war). For example, the book tells you construct a paper trail so that even the shiftiest weasel cannot switch sides if it's suddenly convenient. Reverend Blunden even goes so far to refer the reader to a vault purveyor in New York so that evidence can be stored securely at home (hint: it's sure as hell not safe at the office). Don't kid yourself; a solid paper trail can save you during a witch-hunt.
The book also looks at how to deal with legacy code in situations where internal competition has encouraged people to hoard information, or to escape responsibility via promotion (i.e. VPs have been known to develop amnesia about the code they worked on). It explains the forces that cause these shenanigans to occur and then describes how to flush the guilty party out into the open, where their slimy tactics won't work. As before, generating a trail of evidence and possessing a degree of intellectual humility go a long way.
Then there is privacy, an issue that employers will definitely try to skirt. Management types tend to be keen on metrics to measure productivity. In addition, software engineers typically have access to code, or algorithms, that may be considered proprietary secrets. This has led many companies to monitor their engineers in some way or another (i.e. key loggers, remote desktops, sniffers, TEMPEST, etc.). Reverend Blunden provides a couple of easy, but extremely effective, counter tactics that the reader can use to foil this kind of Big Brother antics.
At the end of the day, Reverend Blunden tells it like it is. He hasn't been bought off and he doesn't have an agenda. His only goal is to warn new hires about the various landmines that exist, buried under the polite exterior of the corporate landscape. You may not like what he has to say, but no one ever said that software engineering was a pretty job. If they did, they were telling you a lie. Praise Bob.
You can purchase Software Exorcism from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
He hasn't been bought off and he doesn't have an agenda. His only goal is to warn new hires about the various landmines that exist, buried under the polite exterior of the corporate landscape. You may not like what he has to say, but no one ever said that software engineering was a pretty job. If they did, they were telling you a lie.
Ahhh, yes. Another treatise on how The Man is tapdancing on our heads.
Alternatively, we could read books on how to help create environments that are mutually advantageous, supportive positive experiences rather than focusing on heading off to another dreary color washed existence where we hate our bosses and hate our jobs.
Visit Jonesblog and say hello.
I thought the owner was insane, so I just ignored it. It would never surprise me now if I learned that she had spied on me. Of course, maybe that was brought on by the paranoia of reading something that, like this book, promotes paranoia.
Can I bum a sig?
1. Tell the truth. 2. Stay out of other people's business. 3. Do the right thing.
Yes, there are some things that can't be avoided. If you are under attack by someone trying to get ahead or find a scapegoat, you have to defend yourself. But, even in these situations, there are choices.
I always save my last mod point to mod up a good troll. You people are too serious.
Is this really the "corporate landscape" for many software engineers? A job so bad where you feel compelled to check for keyloggers, keep paper trails locked in a home safe, etc.?
Granted, I've not been out of school that long, but every job I've had was in a friendly, cooperative environment w/ good people who wanted to write good software. We don't assign blame, we don't sabotage people's code -- we fix problems we find and give each other help when its needed. But then, I've always worked in scientific computing, so maybe I'm not in the "corporate landscape" as such.
So am I wearing rose-colored glasses and blinding myself to the cut-throat world of commercial software development, or is the author of this book simply over-reacting?
Also, if I were to find myself in a job where I felt a need to take the precautions suggested in this book, I'd be looking for a new job. I can't believe that any company could maintain such a draconian work environment and keep employees.
I now sit back and await all the posts telling me how naive I am. :-)
Maybe not, but having taken a couple of grad courses in Comp-Sci, I can say that the day we all switch from PCs to 5-tuple one-tape Turing Machines I will so be set.
Joking asside, Universities aren't about practical education (barring Medicine and Law...and to some extent Engineering). You don't go to university to learn how to be Bill Gates (god forbid). You go there to learn how things really ought to be. Then again, despite how ideal Universities try to be, research ends up having its fair share of backstabbing and intellectual thievery.
"I doubt very highly that your instructors will tell you how to handle all the nasty little things that can occur when humans work in groups..."
/., dilbert and userfriendly to get the same instructions, but usually we start reading these only after we've learned about this stuff the hard way.
That's the problem right there. Every student getting a degree in computers should take a mandatory class covering office politics, hiring legals, and how to deal with various peers, managers and devil^H^H^H^H^Hmarketing people.
Sure, we can read
they pretend to pay us so we pretend to work. In the UK, developers salaries are cheaper than some hourly rates offered in India with outsouring companies ... but moving along ... it comes down to the fact that good programmers are rarely good at getting on with people.
If you can do your technical stuff well and be a nice person (even better a popular preson), a company will value you and you can rise above office political bullshit.
The books author sounds embittered by the fact that joining the software industry at the height of the tech boom didn't make them as rich as (Kill) Bill. Get over it and get along with people.
"It's not your information. It's information about you" - John Ford, Vice President, Equifax
People go out and learn martial arts to protect themselves just incase. (Well... most of them do) They don't just go out and learn it to take down the next person they meet on the street.
Just because this information is laid out as it is, doesn't mean you should use it just because and cause such a malicious environment.
Remember, it takes everyone to create that happy environment.. but just one person to create that malicious environment. This is for that time when that one guy (or guys if you are really unlucky) is on you and you need to protect yourself.
Here's a short version of what you need to know when you're working for someone.
Do you know the difference between a cost center and a profit center?
A cost center's something the business needs to do but doesn't make any money. Think accounting, or maintaining print servers -- the goal is to make its function as cheap as possible. One attractive way is to offshore it, provided things work out as cheaply as possible.
A profit center makes the business money. Like software development, or whatever it is that the business does: doing a good job will make the company money.
It's always better to work for the profit center.
I think you are confusing "college" with "undergraduate work". In the above paragraph, s/customer/advisor/ and s/software/research/ and you start to get the idea.
--
bachiatari na torisetsu o yome!
Don't kid yourself; a solid paper trail can save you during a witch-hunt.
How cute. The naivete boggles the mind. Now, grow up and realize that there is nothing that can save you during a witch hunt. Even if you document your way out of the frontal attack, you will be noted as a troublemaker (for defending yourself) and be eliminated on the next pretext that they come up with.
When faces with a purge, the best course is to resign yourself to your fate, and take as many others down with you as you can manage.
I've worked for good managers and bad, and for the most part (aside from having one's department deliberately nuked by an idiot top-management team I eventually outlasted - true joy!) I've never had to put up with much in the way of dirty politics. Most of my colleagues have been and are good folks, the rest don't last. That said, I think the following rules will serve you well:
* Document your work and accomplishments and keep hard copies.
* Act so you need not fear your chickens coming home to roost (great stress-reliever, that).
* Be straightforward and honest, even when dealing with fools and slimeballs.
* If you feel the need to keep a few hidden surprises in reserve, make sure it's not inappropriate to keep'em hidden. Then spring'em with a smile.
If all that fails and political crap befalls you, you don't really wanna work there anyway.
"My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
Office politics is when:
- The new and impressive system that you've been coding (with love and tenderness) for the last 3 months gets shelved just before regression test phase is over because some middle manager changed his mind.
A crappy manager can easily undo the work of a thousand first rate coders.
If you stick to coding and don't look around (like an oostrich with it's head on the sand), you will constantly be hit by surprises at work (a lot of them not nice).
Pop your head once in awhile and smell the air - you might just see that out of control freight train coming your way in time to dodge it.