Comment The problem is... (Score 1) 495
not the coder, but the company. Or at least that's my experience.
So many organizations still persist in viewing technology as a black hole of expense and yet, expect miracles to pop out of it with minimal investment.
Then when code or systems go live with screwy results, the bitch fest begins that morphs into a witch hunt on "who to blame for this error that's costing us money."
Rolling back to the beginning, if the company would:
- Entrust those hired to do the job to do their job
- Hire a TEAM to make the project effective and less costly (even if a temp hire from a external org)
- Manage the business and projects therein properly (no draconian deadlines and unobtainable goals)
- Invest in the proper tools to allow teamwork & quality to prosper
- Require accountability and teamwork to promote employee & product development
Looking at my current employer as an example, we have no reliable & functioning source control (and the developers typically code directly against live servers - no better test than a live one right?), no QA tools or test processing cycle, and no team or project management. The coders want to do the right thing, which is admirable - but they need better tools to deliver the goods. Takes money to invest on the infrastructure. Management isn't willing to go there as it requires money.
It's miserable, but when I look out into the market place this is not an uncommon story.
Organizations expect IT to deliver and all too often people want to take on the challenge only to realize they are effectively an army of one, ill equipped to do the right thing and forced/expected to deliver. In our environment, if coders could rely on teams equipped with decent tools, the review would be easy & effective. And our products would reach the market faster with better results... But instead, they write & review their own work.