4 ms·
Assuming he had a green light on the project itself, and it creates value, I don't see why that would be selfish.
by andrewflnr 15y ago
Assuming he had a green light on the project itself, and it creates value, I don't see why that would be selfish.
- zasz 15y agoSuppose the OP leaves. It's going to be hard for the his former coworkers to maintain the Ruby app.
- tricolon 15y agoIf the OP did a proper job documenting his work and his former coworkers are competent, it would only be a tiny bit selfish.
- numeromancer 15y agoAnd it is not unlikely that there is somebody else looking for an opportunity to put Ruby experience on her resume, and will gladly take on the maintenance. In that case you have created value for your co-workers, too.
- dpritchett 15y ago$30,000 hard, or minor annoyance hard?
- zasz 15y agoDepends on how competent his coworkers are.
- chc 15y agoMaybe "one-off" means something different where you're from, but I read it as meaning this wasn't an issue.
- zasz 15y agoA classic mistake people make is assuming that something isn't an issue, when the other party DOES think it is an issue.
- chc 15y agoIf you think the maintainability of a one-off script that's probably already been deleted because its job is done is that crucial, you're simply nuts. If it needs to be maintained, then by definition it is not a one-off.
- nc 15y agoHard for them to maintain, or they wouldn't be as inclined to, if it were written in their language du jour?
- HeyLaughingBoy 15y agoUltimately everybody leaves. Does this mean you should never change your language or technology stack? Do what gets the job done, within reasonable limits. If the expected maintenance is minimal and you can improve your personal capability and/or produce the deliverable faster using a different technology, by all means go for it. I've had to learn languages far more unpleasant than Ruby (VBA, I'm looking right at you!!) in order to maintain programs that no one expected would ever change. That's life!
- invalidOrTaken 15y agoIf management would like easy-to-maintain software, they are free to start prioritizing it.
- adgar 15y agoMaintenance takes a lot more time than the initial implementation. By using a language nobody else knows, you increase the cost for 90% of the project's lifetime to decrease the cost of the initial 10%. It's selfish if the numbers are such that maintenance ends up costing more than you saved by using your favorite language for the initial implementation. That depends on a lot of things: your co-workers' experience, your coding style, documentation for the language/libraries used that your co-workers aren't familiar with, etc.
- tomjen3 15y agoFor some projects maintainance cost a lot more than initial development. This is kot the case for a large segment of programs though. Hint: any kind of problem that need only be solved once (or where it is cheaper to write the code again rather than to make it general enough for everybody) can be written however the original developer believes he will create the most value
- ramchip 15y agoHe said a "one-off" project. Not all projects have such huge maintenance costs.