Pride or lack thereof

I’m really fed up with people that take no pride in their work. People that are satisfied with being the weakest link in the chain.

How differently was I raised that I actually give a shit about my work? I don’t remember being taught lessons by my parents on giving a shit. Hell, my childhood wasn’t all that great.

Now, I don’t expect everyone to work the hours I do – I know I’m partly insane and partly stupid for giving so much of myself to work. But have some fucking pride! If I were a dev, and I let code go out that on first, basic run by qa was COMPLETELY NON-FUNCTIONAL I’d personally be ashamed! I would do my best to never let that happen again! Am I off the chain here??

Advertisements

Posted on February 10, 2013, in Uncategorized. Bookmark the permalink. 4 Comments.

  1. I agree, and it’s extremely frustrating. I find there are always people who just want to work the minimum hours for the money.I find that a good relationship with devs (where I can get/make it) helps me request more from them (such as working builds). Usually I try to ensure they know that I am a support role for them and try to ask if there’s anything they need from me first. If I can’t get better quality builds out of that then I take it up the chain as a testability issue and get the higher-ups to enforce it if they think it’s important enough.

  2. Do you think people really want to be like that ? Wouldn’t most people prefer to be involved in their work and to have pride in it ? Rather than ask why they dont ( or you could ask them and find out why – have you ? ) question the system that has got people in a state that they don’t seem to careIf you are working long hours ( sounds like you are ) and maybe if you dont get recognition for it then you’ll end up burned out, cynical and disillusioned. Then people will start asking why you have no pride in your work…Was the dev ashamed when they found out it didn’t work ? what pressure were they under ? did it work on their machine ? why didn’t it work on your env – was it a blatant bug, misconfiguration, bad code merge ?

  3. This particular dev attempts to always take the lazy way out. When a bug comes back to them that feature x they just fixed a bug in doesn’t work at all, they seem to take it in stride – no shame. This particular dev told me that he is giving me job security. Jokingly, for sure, but still. He has said he feels it is QA’s job to find every bug, and that dev shouldn’t have to do any testing at all.This person works the minimum hours, pushes out code and doesn’t even check if it will work on a very basic level. Sure, our process is bad – they build, it goes to QA. No automated unit tests, no automated regressions (something I’m working on). It’s build and go home, without seeing if it will work.For the case that I mention at the end of my post, the first basic smoke test showed that his bug fix broke the feature entirely, in all cases – it was completely unusable. A cursory test on his part would have caught it. But! That’s what QA is for! He’s doing me a favor by keeping me employed, giving me something to do!As to your first questions, Phil, I would hope that most people wouldn’t want to be like that. However, this person seems to be. I haven’t asked him why he doesn’t seem to care – I’m not sure how I’d word it without sounding bitchy, honestly. He gives pushback to every issue, and tries to implement the "easy" fix rather than the right one. I think the root of the issue is that there’s no accountability, and when he is a continual offender (not doing the unit testing he’s asked to, not implementing a feature as he was told to but the easier way), nothing is done about it except making him fix it. I think most people would get the hint, but there’s nothing making sure he does. *shrug*

  4. re: phil…question the system that has got people in a state that they don’t seem to careYou’d also have to question why a system that creates those people also creates many people who do. I think the answer is that when you show some respect and humanity to your employees you also give some leeway for people who are just working for money to do even less for what they get. I only speak from personal experience and observation. Perhaps the system should be questioned as to how allowing unchecked work to get through is deemed okay? I illustrated to people who matter the cost to the company when this happens, and I illustrated to the devs that I can’t be efficient for them if it does, and how it affects my work. We agreed, as a team, that devs would check their work before sending it to me and I would do a broader smoke (or smoke-like) test session on reciept for quick feedback.Was the dev ashamed when they found out it didn’t work ? what pressure were they under ? did it work on their machine ? why didn’t it work on your env – was it a blatant bug, misconfiguration, bad code merge ?This questioning is important, and I agree strongly with the thrust of it. I always try to blame myself before I blame others, and I do look at circumstances surrounding a problem to stop me from judging too harshly. I do, however, look at attitudes to the work and whether something is done for the company and the project and the team or for themselves. The balance should be right.re: HilarySomething that I found that helped was to point out that their job was to turn desires and documents into a working product and my job was to explore the complexity of the system they create to find hidden problems they don’t have the time/focus to handle to provide them with useful feedback. If you need to breed a culture of accountability it may be helpful to calculate the cost of these errors. I had a section in a presentation (at which my boss was present) pointing out why finding bugs is a bad thing. The cost of lost time in back and forths and a bit of this: http://www.developsense.com/presentations/FindingBugsVersusCoverage.pdf

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: