Suggestion for Konquerer developers and delivering "stripped" releases

[Michael S. Mikowski]

Hey Phillip:

I for one am sick of your arrogant self promotion here.  You /can't/ write 
programs that do not crash, because you /can't/ control your execution 
environment. Unless, of course, you are working on programs with lower 
complexity and far less distribution than KDE.

I can't believe anyone in this century designs /any/ program with paper.  
That's like using drafting boards instead of CAD for mechanical design (I 
used to design cars with CAD.  They never crashed.  At least, not when driven 
in unknown environments :).  

If you are using paper for design, you are wasting your time and your 
employer's money.  Worse, you are compromising the quality, features, and 
timeliness of your products.  Try some UML modeling or design charting tools 
that can live with the project.

Get some humility.  Lose some narcissism and arrogance.  Learn to use some 
modern design tools.  And, finally, please be constructive.  KDE does need 
good feedback on its projects and intelligent bug reports.

Otherwise, STFU.

Cheers,

Mike

On Thursday 09 November 2006 13:36, Philipp Hülsdunk wrote:
> on a paper first; It will created many advantages:
> * On paper you are not thinking on programming-language specific things.
> This causes you to concentrate more on the programm instead of the
> programming-language.
> * On paper you can overview your concept better. In the source code it is
> more difficult.
> If I write software I do this, My programms then do not crash.
>
> Another suggestion is that you should comment your code better so that
> other developers can understand the code better.

-- 
Michael S. Mikowski
Software Engineering Manager
ValueClick Search
ValueClick Inc.
818.575.4587