But not for long and most of the code reviewers begin to curse at .. "What were you thinking as you do not know the pattern for the problem?" Or "Why do you have this code written down here that could be much better there need to be." And so on and so forth.
Anyone who looks at someone else's code, something has to be criticized. In the very best this is true even when you reflect yourself. (Incidentally, under girl developer described very nice)
I wonder if the so needs to be.
Customize these views together somehow? I think so, but who knows or defines the boundaries of creativity and standardization? Is it even shifts in these boundaries, that is sometimes more or less creativity or standardization? It depends on the solution? Can we consider software development as a production process, which have also kept creativity and standards collection? If so, what? Can be derived from these processes and look to the future?
All these questions I asked myself recently. I thought that this issue is no longer relevant would be for me where I can but for I had completed 10 years ago,
Customize creativity and standardization together?
What a question, of course, go together. First, because almost all materials are in art produced by any standards. Look for. But the artist does not care, but also uses the material and creates art. Well, the comparison is a little bit. So I'm looking for what I use instead of standard I now betterrule because Norm is a very final word in Germany.
So where contact artist in creative processes rules? Very simple. A sculptor will always ensure that it works well balanced, so the material is not destroyed, before his work is finished. It will operate under the simple rule not to give too much force on the chisel or gouge.
A graphic designer turned the pen on the page, a thin and maintain the broad peak to a thick line. To this rule he is not around.
Yes, and for software development, there is now also a good easy to learn rules that the creativity of the individual is not in the way. Here you can get a picture of it.
Where are the limits?
now what are the limits? Determine the creators of solutions themselves first, by the solution itself and secondly by the technology and architecture, processes and planning, and creativity and the organization. Briefly defines the anatomy of the solution Limits.
Is that good? I am currently of the view that this means too much freedom, which can lead to high friction losses. I will continue to monitor.
software development process?
we are about, imagine that Germany is an innovative leader in the automotive industry. If not difficult for us. Now we face a development department once before in this industry. There's a lot of well-paid people are in an office and suddenly invent a super duper Einparkhilfssystem bang and bright, every car that goes on in that second off the line, equipped with this innovation. Also nonsense. As is naturally a highly focused, innovative, and behind before groaning standards process. And each R & D engineer claims that he is creative in his work. Wow, I want to see in the software production Sun
So, I maintain that software should be created as a product in a production process. Since the end of each has something like this, customer and developer. I would like to compare in a later blog Scrum and Kanban with each other.
Software as a process is that about it?
If it can be produced even the solution itself as a product so successful, why should not it be possible that the solution is formulated themselves how such a process. Because we imagine we want a successful model can be applied several times.order to support this statement I have a little search in the history for similar statements and I at various literary and find Internet references (simply 'Software as a Factory' Enter Google, really good review here). This subject has therefore wise people already employed. It looks therefore like this, it is necessary to join or make a better analogy between traditional manufacturing and software process.
In the next blog so it will more precisely to this analogy. EBC 2.0 is an excellent approach to realize this, the classical component models, it gets it too, but it's a little more complicated.
January