-
Developer Book Syndrome
A colleague of mine once stated that creativity is rare in technical people I had my doubts at the time as I’m fairly creative and often build unorthodox solutions tailor made to the problem but the longer I’m in the industry the more I agree.
The biggest symptom of this is something I called book syndrome. This is where famous author xyz ( eg Lowly , Fowler etc etc ) writes a strategy in a book and people use it in completely in inappropriate circumstances. When challenged on the solution they use the authority of...
-
Is software theory relevant
I just realized my main objection to heavy theoretical based development stems not from poor theory but in appropriate use.
I think it comes down to the original premise that 90% of a softwares lifetime budget is in maintenance . While this is certainly true for large scale mainframe applications or software vender apps ( eg IE , Word etc) it is not for the majority of small apps used today. I have seen many of these applications not change for 90% of their lifetime and when replaced they are replaced by the latest and greatest language /technology.
Here is...
-
POS or SOA Lite TODO
I think Service Orientation has gone the way of J2EE/ EJB and needs to be pulled back like was done with POJO.
I propose POS Plain old Services or POSA for Plain old services architecture.
Rules.
1) There is only one rule and that is KISS.
-
Agility vs Planning
Pretty nice discussion about the book Balancing Agility and Discipline
http://www.reliablesoftware.com/DasBlog/default,month,2007-05.aspx
Im think if you have too much agility you will not get a very good ROI from your investment ( though everybody maybe happy except for the person who pays the bills)
-
Are projects getting more successful
Im curious at the increase rate of sucess in a number of surveys such as the later CHAOS surveys. Looking in the detail however it appears that projects after peaking in 2000 the amount of time overrun and the amount of features completed have dropped dramatically in the vast majority of projects. Not sure what it means but to me it DOESNT mean software development is getting better if features are getting dropped and there are increasing time blow outs.
Things that come to mind
Standards for success and projects have increasing amounts of over estimation to prevent...
-
Architecting for the team
One of the major differences between the oft and bad used example of building Architecture and Software architecture is people. When you build a building people know how to pour the concrete and a few specialized roles are imported electricians etc but with software we are expected to know all. If you have been writing Windows Forms apps for years if the new project is a web app it is expected that you know write a web application , the only exception seems to be with languages people seem to except a C# programmer cant write VB or Java -...