Hacker News new | ask | show | jobs
by generalk 5348 days ago

  > Since when is being a crafts-person and being proud of 
  > your work and what you do bad?
Nobody said it was. Not the original article, not me, not anyone.

  > I'm in the business of producing good software.
I don't know, maybe you are.

Right now, I'm in the healthcare business. My main client is a medicare company and they want people to sign up for their plans and fill prescriptions, preferably for the cheaper generics that save them money but still provide therapy required.

I meet those goals by writing well-architected software with solid test coverage. I make my job easier on myself by making my deployment a single-click affair. That's part of being a good developer, but that's not what I'm paid for. I'm paid to meet business goals. We got this client by writing software that meets those goals better than their original vendor. If someone comes along who writes poorly-architected messes but that achieve those goals better my client will leave me for them. I will be disgusted as a programmer that this happened, but it only makes sense.

  > I don't see anything wrong with calling myself a programmer.
That's fine. Call yourself whatever you want. But -- and this is the entire point of Patrick's article! -- assuming that people understand the value of a good programmer is a mistake. Rather than dismissing folks who don't instantly comprehend your brilliance, maybe you might try explaining to them the value that you provide in terms they can understand.
2 comments

If someone comes along who writes poorly-architected messes but that achieve those goals better my client will leave me for them. I will be disgusted as a programmer that this happened, but it only makes sense.

I understand what you're trying to say, but I disagree that people perceive "programmers" as highly-paid peons. If they did, why would you want to work for them? There are companies who are desperate for good programmers and recognize that good programmers are hard to come by. Negotiating with them is much less adversarial, I assure you.

I don't disagree with a lot of what you're saying. I think we can both agree that a good programmer understands their role in the business and should view their practice holistically as a part of a much bigger entity. However, I don't think that people universally see programmers as overly-paid gurus or what-have-you. Assuming they want skilled programmers to work for them, why would they look for replaceable cogs and peons?

The true cost of hiring those kinds of programmers will not be apparent until 5 years down the road when you're spending 80% of your budget and time fixing bugs and putting out fires from pissed off client who cannot believe you would ship them such a shoddy product.

Again.. maybe there are people in the world who still do not know what a programmer does or the value of hiring good programmers. I would argue that they're probably in the minority or hiring for a position that doesn't require a lot of skill. In that case perhaps Patrick is right -- but again, why would you want to work for them unless you're desperate to fill in your H1B requirements or you're straight out of school and have no experience. A good programmer can do a lot better in my experience.

I know that you're fighting the good fight, but I just don't have it in me to sell the concept that I'm going to produce software to solve someone's problems. I'm only interested in joining teams where the decision to write high-quality software was already made - and I provide my skill to people who know that's what they need.