Timeline for What to do with a not well organized application?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 19, 2011 at 21:43 | comment | added | cthulhu | The one step at a time is always good. Concentrate on one improvement at a time, and finish it from front to back. Most importantly - /don't tell management/. They don't need to know, it's not their problem or their pride and quality of work on the line, it's all yours. | |
| Aug 16, 2011 at 9:00 | comment | added | nillls | @domanokz If it's during work hours, no. If it's in in your spare time, no. ;) During work hours you should do what is asked of you - you don't have the mandate to choose the tasks you seem fit (yet). If you do it in your spare time, stop. Some will argue that it's a learning experience, but way too many hours have been spent working for free in this profession - if you want to learn, do something for yourself. | |
| Aug 16, 2011 at 8:51 | comment | added | Raynos | @domanokz your welcome to re-write it as a prototype in a stack your highly skilled with and can just get it done. Then show of the prototype and recommend based on real facts (time, test coverage, prototype) that it can be rewritten and that's it's a financial gain. | |
| Aug 16, 2011 at 8:48 | comment | added | kazinix | Thanks! That's exactly what I'm doing now. I'm just afraid it would take a lifetime to do that. Actually I'm rewriting it without telling my boss, is that okay? I think I'm just wasting my time. | |
| Aug 16, 2011 at 8:42 | history | answered | nillls | CC BY-SA 3.0 |