Timeline for Desktop to Web - How to deal with user-interactive workflows
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2014 at 9:33 | comment | added | maple_shaft♦ | @OlivierH Rewriting complex software is well... a complex undertaking. If you detail out the high level tasks and provide high level estimates you might be able to use that as leverage to convince your boss to hire more people. | |
| Jul 17, 2014 at 8:58 | comment | added | OlivierH | Yep, that's exactly what i thought in the first place, your solution is quite the same as the splitting i talked about in my question. Unfortunately, this would be too much work too. Imagine thousand of workflows like the one you took as example, on average more complicated than that. Some could have 10 or 20 intermediate states : it would be a huge work, and there would be an high probability that we introduce lots of bugs. | |
| Jul 17, 2014 at 8:28 | history | answered | k3b | CC BY-SA 3.0 |