Design to last
Myths, MythBusting and Facts Print E-mail
Written by Daniel Leiderman-Gueller   
Thursday, 30 October 2008 00:00
Watching the TV series Mythbusting, I came to a realization that many times I was guided by myths generated without any basic facts or actual validation of the myth. This can happen due to repeating outdated information, using wrong methodologies, or simple ignorance.

Since these myths actually hinder the development of the system, one of the tasks of a system engineer is to ascertain the validity of the myth and remove unnecessary barriers.

Last Updated on Saturday, 10 January 2009 13:30
Read more... [Myths, MythBusting and Facts]
 
The name of this site Print E-mail
Written by Daniel Leiderman-Gueller   
Tuesday, 28 October 2008 00:00
The name of this site is related to the way I look at how to solve problems. Problems are part of the universe, as defined by the 3rd law of thermodynamics: the entropy increases - always. Thus problems will be part of the world because they are the chaos that surrounds the order men tries to bring into the world.
My personal view it that each problem solving must be tackled as something to be creatively solved by understanding the fundamental problems.
The fundamental problems can be categorized in several issues:
  • lack of communication
  • lack of information
  • real technical obstacle
Last Updated on Tuesday, 21 April 2009 09:48
Read more... [The name of this site]
 
WaterFall – real life problems Print E-mail
Written by Daniel Leiderman-Gueller   
Saturday, 18 October 2008 00:00
WaterFall - real life problems

Waterfall is a method for software development process devised in the 1970's. This model has been used by many companies and is used in the company I work as well. This method is very simple and assumes that each step is done sequentially and fully.

Waterfall in theory can work if:
1.      Complete information is available
2.      Requirements are constant
3.      Finish design before implementation
4.      Implementation will not change design
5.      There is enough time to finish design before implementation
6.      Perfect communication of design
Last Updated on Saturday, 10 January 2009 13:23
Read more... [WaterFall – real life problems]
 
Open Source makes better programs Print E-mail
Written by Daniel Leiderman-Gueller   
Thursday, 16 October 2008 00:00
Commercial software is created to make money; this money comes for increased sales to upgrading or new customers. In order to create software to be sold to other customers, two options are available:
  1. simplify existing capabilities
  2. add new capabilities


The first option creates a product that it's easy to use and has the distinct benefit of having easier learning curve and can be explored to suit the capabilities of the user. The second option creates bloated software that can do anything, but its very hard to learn and to use.

A very good example of a program going the second direction is "Paint Shop Pro"

This post explains how he software gets bloated and how it has lost its appeal.


In the open source world, the reasons are different. Software is written to suit a need, to fulfill the requirements of users. If something is actually needed it can be written by the user who needs it.

If the decisions taken by the developer are not acceptable by the community, then the community can make a decision and branch the source to a different product. See the funpidgin / Carrier situation.


In my opinion, for software that does not need customization to a customer, open source solution will make a more viable product. Commercial software will need to evolve and be leaner.

For solutions that require tailoring for a customer, as SAP, open source is still in its infancy because each customer requires a lot of functionality modifications.


In the end, open source products will be much more efficient and with less bloat.

Last Updated on Saturday, 10 January 2009 13:17
 
<< Start < Prev 11 12 13 14 15 16 17 18 19 Next > End >>

Page 15 of 19