In this post I am going to try to illustrate in a funny way the reality of developer’s life.
This post is a translation of another post written in Spanish.
When you upload something to production environment:
When you find a problem solution without searching in Google:
When you close your IDE without saving the code:
When you try to fix a bug at 3AM:
When your regular expression returns what you expect it:
When my boss reported me that the module I have been working will never be used:
When I show to my boss that I have fixed a bug:
When I upload a code without tests and it works as expected:
When marketing folks show to developers what they have sold:
The first time you apply a CSS to a web page:
When the sysadmin gives you root access:
When you run your script the first time after several hours working on it:
When you go on weekend and everyone else are at office trying to fix all issues:
When your boss finds someone to fix a critical bug:
When you receive an extra paid if project ends before deadline:
When something that had worked on Friday and on Monday did not work:
When you develop without specifications:
When boss tells me that ‘tests are for those who doesn’t know how to code’:
Have you ever life one of these experiences? I hope so, if not maybe you are not a real developer
This guide will introduce you to the world of Software Architecture!
This 162 page guide will cover topics within the field of software architecture including: software architecture as a solution balancing the concerns of different stakeholders, quality assurance, methods to describe and evaluate architectures, the influence of architecture on reuse, and the life cycle of a system and its architecture. This guide concludes with a comparison between the professions of software architect and software engineer.