Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
Oliver Sedlacek
12/23/11 02:43
Read: 324 times

#185189 - Speed, quality, cost
Responding to: Jez Smith'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.

List of 12 messages in thread
Wirth's law Does it apply to embedded systems?      Jez Smith      12/22/11 15:28      
   Same for embedded      Per Westermark      12/22/11 15:49      
      It's possible, but ...      Richard Erlacher      12/22/11 23:59      
         That obviously depends on priorities and focus        Per Westermark      12/23/11 00:35      
            Still Java      JecksonS Ben      12/23/11 01:13      
            embedded categories vs "ease of programming"      Erik Malund      12/23/11 08:08      
            No question about it, but doesn't that also contain risks?      Richard Erlacher      12/23/11 08:43      
   Speed, quality, cost      Oliver Sedlacek      12/23/11 02:43      
      I think they have to choose which one of the three ...      Richard Erlacher      12/23/11 08:46      
         Its time for me to get on my soapbox      Jez Smith      12/23/11 14:25      
            passing knowledge        Mahmood Elnasser      12/24/11 05:59      
   Software Bloat - or Feature Bloat?      Andy Neil      12/24/11 01:54      

Back to Subject List