Timeline for Is it okay to use a language that isn't supported by your company for some tasks?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 7, 2011 at 17:56 | history | edited | Vector | CC BY-SA 3.0 |
added 4 characters in body
|
| Sep 7, 2011 at 16:18 | comment | added | Vector | @Thomas Owens - granted - that's included in what I said 'potentially impacts the work of others'. | |
| Sep 7, 2011 at 16:13 | comment | added | Thomas Owens♦ | And if someone else needs to do the same or similar task later (which is very likely, in my experiences)? They have to reinvent the wheel. It's one thing to have a throwaway prototype work for solving a problem or learning a library or framework. It's another to spend time developing a tool to do a task and then just discarding it. The types of tools that the question is referring to are for tasks that potentially have to be done multiple times, and if other people do those tasks, they waste time by not having a tool to assist them (or needing to develop such a tool). | |
| Sep 7, 2011 at 16:03 | comment | added | Vector | @Thomas Owens - there are often one-time tasks - once they're done, they're done - or your own hacks and tests that you do in the course of development to get through something sticky - again, once they're done, they're done - effectively disposable. | |
| Sep 7, 2011 at 15:44 | comment | added | Nate C-K | If during the time you were at that job it increased your own personal productivity, then the company has already gotten value from that script and it was not a waste, regardless of whether it gets reused later by someone else. | |
| Sep 7, 2011 at 14:22 | comment | added | Thomas Owens♦ | How do you know if it's for you or for others? At work, you can get reassigned or you could quit. Anything that you produce at work (in most cases) isn't yours, but it belongs to the company or the customer. If they can't understand or maintain it, the time lost is the time you spent developing it plus the time it takes someone else to understand it (and perhaps develop a new solution). Everything produced at work should be treated as something for someone else. | |
| Sep 7, 2011 at 14:18 | history | edited | Vector | CC BY-SA 3.0 |
added 12 characters in body
|
| Sep 5, 2011 at 20:45 | history | answered | Vector | CC BY-SA 3.0 |