When is it acceptable for a team leader to encourage “hard-code everything for now, and then maybe we’ll fix it later”? What about when the rest your team is fine with it? What then?
Hack now, refactor later.
I hope the real world isn’t like this.
2 Responses
Josh
February 8th, 2008 at 6:38 pm
Don’t get your hopes up…it won’t be THIS bad but it’s not going to be a paradise by any means.
If nothing else, if you expect to see attitude/skills like this, you could be pleasantly surprised?
No, this wasn’t very “uplifting”.
Rex
March 1st, 2008 at 12:27 am
From what I’ve noticed, most of the people see what they’re doing as a job and not as a way to improve their programming skills.
If you go into a project without wanting to learn anything new, and decide to hack it together because, “that’s what we did in the last miserable project…” then you’re going to get frustrated with your job and hate life.
If you go into a new project thinking of it as a clean slate, a new chance to apply what you’ve learned in past projects, then you’ll find that the more projects you work on, the easier they become.
The problem is everyone on the team has to be on the same page about this.
Why not be the code snob that says “no, we’re not going to hack this together” and tells people the best way to do things?
And… I’ll end my rant here…