arborint wrote:It is fairly well designed, organized and coded, and it's improving
Relative to what exactly? You personal experience I would guess. In which case, I don't think your understanding where I am coming from. Most projects I have worked on are like SugarCRM. If your not in need of more experience working on projects like that, maybe you need to spend more time...cause I tell you what. 10 years of workign with globals, more than acceptable code duplication, horrible comments, poor file structures, etc...
While I wouldn't say it's left me winded...it's certainly left me tired of the same old thing, when my spidey-sense tells me it could be better.
You missed my point when I said I consider myself to be the best of the best. It' more about not letting deliberate errors ocurr than boosting thy ego.
Here is how I see it: Complacency is a real killer (especially when your a pilot - the path I originally persued in life). Confident people are allowed to fail. Complacency sneaks up and murphys law bites you in the a$$. Sometimes it's a lesson learned, othertimes, you become the lesson. Cocky people can't fail!!! Their pride constantly reminds them of the fact everyone is waiting to watch them fall.
I bark like I'm the best, because it reminds me to always be my best. I realize to error is human, but it doesn't mean I have to accept making errors or mistakes which I know are avoidable. The statistic goes like: 80% of aircraft related accidents are pilot/human error. Meaning, it could have been avoided. In programming, 100% of errors are human error - meaning they could all be avoided (unrealistic perhaps). If your average developer spends 50% of his/her time fixing mistakes they made because they jumped the gun a little to soon, then I'll be damn sure that I only spend 25% of my time doing the same thing.
Maybe I'm just competitive (no secret there)...but it's usually people who want to win that do. I can't remember ever watching the olympics and hearing an athlete say:
"Man that was a great race and I didn't even really want to win".
Take from that what you will, the whole point of this disscussion was to see if anyone shared the same passion/experiences as I have about software development and possibly had the desire to at least make a serious effort to make things better. Infact not just slightly better, but way better.
In the T&D forums I have seen you expose the evils of GLOBALS and other bad design techniques countless times (infact you've even influenced my choices in the when I thought you were right) and yet here you are challenging everything I say like you incorporate these practices in your own designs and are defending your own bad choices...what gives?
Do you follow OOP practices and principles like OCP? Do you not utilize dependecy injection as required? Do you not favour composition over inheritence most of the time? Do you not follow your very own advice you preech in the forums??? The fact is, if I presented the code in SugarCRM on the forums and asked for opinions, you'd be all over it like hotcakes.
You've really spun me 360 here. You are one of the few I figured might agree with me on the amount of poor quality software currently availble (from the developer perspective anyways). Maybe your defending my accusations, because you have some sense of humility that I don't share. I can appreciate that...being humble and all. The fact is, humility is not a one way street. You are not supposed to just be humble around humble people, but retain that humble opinion around cocky people as well. Otherwise your not humble or cocky, but in my opinion, confused.
While you are right in saying SugarCRM is useful (I use it in-house it's why i used it as an example cause I know it well) that was not the point of this disscussion. I thought I made that clear in the original post. In such a competitive market, I need an edge. If I can match a product feature for feature, but I do better, faster, safer & cheaper on every level of software development, the idea is, the software will sell itself.
patrikG: I get the idea behind RERO. Really I do - it's not rocket science.
Your either missing my point or trying to make yourself believe, I am so ignorant as to not see the benefits to RERO. My point was, most projects use it as a crutch. Just get the code released and the community will find and maybe fix bugs.
That is that complacency effect I spoke of above. It's pure laziness most of the time. While I am sure there are some projects who nail it right on...those are the minority, not the majority.
I'll give you a tip. When your selling something to a potential client, the last thing you want to do is hilite the benefits of your competitors products and focus on the negatives of your own - which is what you seem to expect I should have done. I focused on the fact that most software is indeed rushed (SugarCRM initial release took only 3 months) and happened to use SourceForge as an example, because *most* of the projects on there are incomplete, of poor quality or total failures.
Was I supposed to focus on the handful of projects which implement RERO successfully? I would have, had I been promoting them...but I was selling something completely different and in this case, the open source alternative is of poor quality...case in point.
Cheers
