| ??? 12/23/11 09:43 Read: times |
#185189 - Speed, quality, cost Responding to: ???'s previous message |
It's the old project management dilemma - the powers that be want it cheap, they want it fast and they want it good. Now decide which two do you really want!
Most software bloat comes about when quality (i.e. speed and resource efficiency) are sacrificed for development speed. Unresponsive applications can have faster hardware thrown at them (i.e. trade off against cost) but not many products justify a lot of effort being thrown at an attack on software bloat. This is particularly relevant when applications or technology are evolving rapidly, where you have to run very fast just to stand still. |
| Topic | Author | Date |
| Wirth's law Does it apply to embedded systems? | 01/01/70 00:00 | |
| Same for embedded | 01/01/70 00:00 | |
| It's possible, but ... | 01/01/70 00:00 | |
| That obviously depends on priorities and focus | 01/01/70 00:00 | |
| Still Java | 01/01/70 00:00 | |
| embedded categories vs "ease of programming" | 01/01/70 00:00 | |
| No question about it, but doesn't that also contain risks? | 01/01/70 00:00 | |
| Speed, quality, cost | 01/01/70 00:00 | |
| I think they have to choose which one of the three ... | 01/01/70 00:00 | |
| Its time for me to get on my soapbox | 01/01/70 00:00 | |
passing knowledge | 01/01/70 00:00 | |
| Software Bloat - or Feature Bloat? | 01/01/70 00:00 |