August 5, 2009 at 05:05Manager, designer and programmer ... when nobody cares
So, pent.
The essence of the text.
In the chain of client - manager - designer - programmer, anyone can nakosyachit, and the sooner this happens, the more difficult it is to fix in the future. At the same time, it is important to note that let someone else be to blame for this chain, but it is up to programmers to fix everything, from which they usually do not feel much pleasure. And everything gets really bad when in this chain, in fact, nobody cares about the result.
And it needs to be fixed. Urgently. Poke your nose, do not be offended, through tears, but fix it.
A little more essence.
We have a small company or a freelance chain, as for example in my case. I usually make widgets and small flash sites. I am writing about what I know and what has already been said many times. There are a lot of people like me, and we all often encounter the described problems. Somewhere the chain is different and their problems, I do not touch them here.
Actually, the text.
What does it matter to spit? Everyone wants to eat, so the work will be done, but made to just be behind. So all mediocre sites are obtained that, although the client likes them, are still squalor and at the same time entail a lot of hemorrhoids in the future. It is sad when their creators are not ashamed of such creations.
It's funny, but even working together for several years, people often do not really know what and how their colleagues are doing. They don’t need it. They do not care. Hence all the problems. It’s easier to give a couple of examples than to try to abstractly describe the situation.
There is a manager, he tells the client what he needs, he agrees. The project seems to be simple. A small description is made, some additional materials are being collected. But the manager is not very familiar with the programming kitchen, he is too lazy to give a damn. Therefore, the designer and the programmer come not only with incomplete data, but with incorrect and with a bunch of places that are "understandable." The manager does not think about the fact that he is a very significant link in the whole chain, because his jambs will be overgrown with jambs like a snowball, and programmers will have to fix it. And it does not matter who and when messed up.The programmer's task is to translate the verbal description of the program into code that does something as close as possible to this description. At the same time, very much can depend on the small nuances of the description, for example, the selected application architecture, which then will be very expensive to change.
So, the manager does not know how I (the programmer) work and vaguely represents what I need. You ask what for he is so necessary? Well, here they are with us in most cases. Passing the description to the designer, he himself misses a bunch of key points, and the designer, in turn, misses a bunch of important things. Because, he, too, is not particularly up to date on program matters, the main thing for him is to sketch pictures, and after us at least a flood.
Often people who can make a beautiful picture are not at all capable of creating beautiful yet functional designs. After all, his work should later be translated into the interface. Here, the skill of the designer, or rather its absence, is fully visible. Often, he does not even think that in addition to a beautiful picture and its source in the PSD (which, I must say, will be read by an outsider, and a bunch of layers of Layer 1, Layer 2, Layer 543 will not please him at all) the programmer will need a bunch of things. For example, button states, rendered invisible animated parts, etc. How many times have I had to finish such garbage. And funny, it was faster than asking the designer to draw the missing details. While he reads the letter, he goes for lunch, finds time somewhere in the evening, and sends the result tomorrow afternoon. But,
It can be seen here that the designer does not know what the programmer needs, and the manager, in turn, does not tell the designer about this, because he is too lazy or he himself does not know. The designer, of course, draws only what was requested, and not half a pixel anymore.
Ask where was the programmer at the beginning? Why didn't he say exactly what he needed? Very, very often, the programmer generally finds out what to do when they send the finished design and a small description to it. Is it wrong with you? Then we will come to you (8 This is not the point.
I’m trying to express the main idea with this text - people don’t know and people don’t give a damn. Often I do not care, but I am the last link. Often I’m too lazy, I do things with hacks based on documentation and design, then it turns out that “I had a different mind” and replace these hacks with a normal implementation, rewriting half the code along the way because of such “intuitive things”.
You have to poke your nose!
I have to! Nose! Through the tears. Despite resentment. Incidentally, I came across comrades who were insulted by my claims. With comrades who are so stubbornly not corrected that I would not do. This problem is very important. She is the root of many misfortunes. When the boss sits in the office and thinks what kind of garbage, everyone seems to be working and doing their job, but it turns out shit, he does not know that his employees do not care about work and the others.
A positive example.
But not everything is so sad. I have worked in a heap of such chains in my life. And there were very positive chains. Managers who knew the kitchen, designers who sent chopped transparent pictures with all the necessary states, animations and descriptions. There were also in my memory ideal projects that customers themselves often spoiled, but more on that another time.
It is pleasant to work with such people, the mood of professionalism and non-spitting is conveyed along the chain.
Question.
How to fight?
The last time I told the girl the designer in polite form what was needed and how to ... She was offended and burst into tears.
After an hour of chat yesterday, today, all participants again behave as before and nothing changes.
How to change the situation radically?
The programmer does not have to control the entire process just to get all the materials he needs. Then he becomes a manager, and at the same time retains his programmatic responsibilities and deadlines. Information is required from the programmer about the possibility and timing. When people do not know what and how you are doing, it is terribly difficult to work with them, but in the end it is me who turns out to be the extreme ...
The essence of the text.
In the chain of client - manager - designer - programmer, anyone can nakosyachit, and the sooner this happens, the more difficult it is to fix in the future. At the same time, it is important to note that let someone else be to blame for this chain, but it is up to programmers to fix everything, from which they usually do not feel much pleasure. And everything gets really bad when in this chain, in fact, nobody cares about the result.
And it needs to be fixed. Urgently. Poke your nose, do not be offended, through tears, but fix it.
A little more essence.
We have a small company or a freelance chain, as for example in my case. I usually make widgets and small flash sites. I am writing about what I know and what has already been said many times. There are a lot of people like me, and we all often encounter the described problems. Somewhere the chain is different and their problems, I do not touch them here.
Actually, the text.
What does it matter to spit? Everyone wants to eat, so the work will be done, but made to just be behind. So all mediocre sites are obtained that, although the client likes them, are still squalor and at the same time entail a lot of hemorrhoids in the future. It is sad when their creators are not ashamed of such creations.
It's funny, but even working together for several years, people often do not really know what and how their colleagues are doing. They don’t need it. They do not care. Hence all the problems. It’s easier to give a couple of examples than to try to abstractly describe the situation.
There is a manager, he tells the client what he needs, he agrees. The project seems to be simple. A small description is made, some additional materials are being collected. But the manager is not very familiar with the programming kitchen, he is too lazy to give a damn. Therefore, the designer and the programmer come not only with incomplete data, but with incorrect and with a bunch of places that are "understandable." The manager does not think about the fact that he is a very significant link in the whole chain, because his jambs will be overgrown with jambs like a snowball, and programmers will have to fix it. And it does not matter who and when messed up.The programmer's task is to translate the verbal description of the program into code that does something as close as possible to this description. At the same time, very much can depend on the small nuances of the description, for example, the selected application architecture, which then will be very expensive to change.
So, the manager does not know how I (the programmer) work and vaguely represents what I need. You ask what for he is so necessary? Well, here they are with us in most cases. Passing the description to the designer, he himself misses a bunch of key points, and the designer, in turn, misses a bunch of important things. Because, he, too, is not particularly up to date on program matters, the main thing for him is to sketch pictures, and after us at least a flood.
Often people who can make a beautiful picture are not at all capable of creating beautiful yet functional designs. After all, his work should later be translated into the interface. Here, the skill of the designer, or rather its absence, is fully visible. Often, he does not even think that in addition to a beautiful picture and its source in the PSD (which, I must say, will be read by an outsider, and a bunch of layers of Layer 1, Layer 2, Layer 543 will not please him at all) the programmer will need a bunch of things. For example, button states, rendered invisible animated parts, etc. How many times have I had to finish such garbage. And funny, it was faster than asking the designer to draw the missing details. While he reads the letter, he goes for lunch, finds time somewhere in the evening, and sends the result tomorrow afternoon. But,
It can be seen here that the designer does not know what the programmer needs, and the manager, in turn, does not tell the designer about this, because he is too lazy or he himself does not know. The designer, of course, draws only what was requested, and not half a pixel anymore.
Ask where was the programmer at the beginning? Why didn't he say exactly what he needed? Very, very often, the programmer generally finds out what to do when they send the finished design and a small description to it. Is it wrong with you? Then we will come to you (8 This is not the point.
I’m trying to express the main idea with this text - people don’t know and people don’t give a damn. Often I do not care, but I am the last link. Often I’m too lazy, I do things with hacks based on documentation and design, then it turns out that “I had a different mind” and replace these hacks with a normal implementation, rewriting half the code along the way because of such “intuitive things”.
You have to poke your nose!
I have to! Nose! Through the tears. Despite resentment. Incidentally, I came across comrades who were insulted by my claims. With comrades who are so stubbornly not corrected that I would not do. This problem is very important. She is the root of many misfortunes. When the boss sits in the office and thinks what kind of garbage, everyone seems to be working and doing their job, but it turns out shit, he does not know that his employees do not care about work and the others.
A positive example.
But not everything is so sad. I have worked in a heap of such chains in my life. And there were very positive chains. Managers who knew the kitchen, designers who sent chopped transparent pictures with all the necessary states, animations and descriptions. There were also in my memory ideal projects that customers themselves often spoiled, but more on that another time.
It is pleasant to work with such people, the mood of professionalism and non-spitting is conveyed along the chain.
Question.
How to fight?
The last time I told the girl the designer in polite form what was needed and how to ... She was offended and burst into tears.
After an hour of chat yesterday, today, all participants again behave as before and nothing changes.
How to change the situation radically?
The programmer does not have to control the entire process just to get all the materials he needs. Then he becomes a manager, and at the same time retains his programmatic responsibilities and deadlines. Information is required from the programmer about the possibility and timing. When people do not know what and how you are doing, it is terribly difficult to work with them, but in the end it is me who turns out to be the extreme ...