Re:What a programmer does for a living
by Locke1689 on Monday March 07, 2011 @06:47AM
(#2296827)
It can actually hurt if you're really good at or really like programming because it can sometimes lead to unnecessary programming. A common example of this is writing a small script to automate something that would have actually taken less time to just perform manually the one or two times you have to do it.
[ Parent
| on HN ]
Agreed, except you need the wisdom to know when you truly will never ever have to do that task again (nor anyone else) vs when you think you only need to do it once. There's value in having something scripted that you end up needing to come back to months later. I also know I would have preferred setup steps to be scripted on projects I've taken over, vs apparently just hand-entering SQL.
Re:What a programmer does for a living
by JonnieCache on Monday March 07, 2011 @09:51AM
(#2297252)
This is why you put the script on github and blog about it, that way there's a chance the script could save millions of times the amount of time it took to write.
But then you run a risk of not automating things you should have automated, which is already much more common.
On the other hand, if you have to do it one or two times a month, you should write a script. It prevents future mistakes on your part, and makes the task a lot easier to hand off to someone else, because you're guaranteed to record all the necessary steps.