What about 1 return and no braces

void SomeFunction(SomeThing s)
{
if (s == null || s.Thing == null) return;
//... more code
}

Just put all your conditions into that 'if' clause. Too many conditions? Use a method to test the conditions and call that method from the 'if' clause Regards GregJF

I still believe that "Good Software Architects will WANT to code", whether they actually get the time to do that is another story. You seem to be arguing that an Software Architect does not need to know how to "code up an enterprise level solution". That I would total disagree with! Enterprise level software applications are too complex to only theorise about their design, without practical long term hands on experience in actually building solution experience. Therein lies the issue and the problem senior non-technical managers face today: having to listen to "software architects" that have never "coded up an enterprise level solution". The lack of University level master degrees (unlike Building Architects) AND an industry that is still more craft than science ( at enterprise business solutions) (not even a software apprenticeship like Masons have) AND the technical complexity that are in enterprise software solutions can only really be counted by the Software Architect having decades of hands on, wide ranging (different business, different industries), in-depth experience. Without that experience, the Software Architect will be relying upon Senior Developers to perform tasks he/she should do or to know answers to issues that he/she should know or lead non-software stakeholders to the correct solution when he/she should convince and lead. I think that a great deal of thought needs to go into this. Also, don't confuse the "Solution Architect" with the Software Architect as they are completely different. The "Solution Architect" deals with the Business Solution, not the Software, Hardware, Networking Solutions. Regards frazGJF

Companies get overwhelmed by the complexity, rather than lose focus. They seem to lose focus when what is really happening is that they are searching for the next "guru" that will give them the "silver bullet" solution. Managers need to be more educated as to what the SDLC is and what the impact is on building software in-house. Normally when companies build software in-house they have moved away from their core business activity into a realm that they really do not understand. (I am not advocating outsourcing, but I am advocating educating senior managers)

Mmmmmmm! Are there any Software Architects here? Software Architect? Well, architects design things. We in the software industry are often compared to those in the building industry, but I think that the software industry is closer to the movie making industry, and the software architect more like the director (who might some times take a role and act!) But what makes a Software Architect? Firstly, a Software Architect must understand the full Software Development Life Cycle(SDLC) AND where in that cycle they operate. Like a movie, each software application has a life cycle. Like a movie, a software application can be used over and over by the end user. Unlike a movie, a software application can be changed in it life cycle and continued to be used by an end user. (although there can be a Director's Cut) To make that happen, players in the SLDC must understand their role as well as the SDLC. So who are these players? There are 5 major players and under each of them are teams of other players. These are: Project Manager: Team of Sub-Project Managers Scrum Master or some other project methodology champion. Business Process Manager: Team of Business Process technicians Team of Business Analysts Software Architects: Software Team Leads Teams of Senior Developers and Developers Quality Assurance Manager: Team of Testers Team of Technical Writers Enterprise Architect: Change Control Team Team of DBAs Team of System Engineers Support Manager Team of software Support staff So now the 5 major players are going have a virtual conversation for the life of the software application. The initial build of the software application will be done in a project, then later it will be Supported and enhanced in patches. The idea for the project will come from a customer, either internal to the organisation or external to the organisation. The Business Process Manager( or members of she/his team) will determine if the idea is feasible for the organisation. If it is, the Project Manager will form a project team. The Project Manager will be interested in three things: How long will it take? How many resources(both human and non-human) will it take? How much will it cost? The Software Architect will need the other players to help answer these questions. Although, the Software Architect won't

Find another job, you are working in a cave

AndyInUK congratulations on obtaining your MBA. Now if you really wish to succeed in IT you ought do a Masters in Information Technology (MInfoTech), but you will find that much harder than your MBA. You could do it part time(about 2 years) Through that process you will be able to find your way. Regards GregJF

GregJF

Yes useless data. Not like us, commenting in this blog thread. No not like us! :-D

GregJF