Head to the project or wide open in the studio

    On Facebook, I often discussed where it is more comfortable to work in a studio or on a project. I tried both there and there. I’ll tell you a little about my vision on this subject. The first serious typesetting work began precisely with the studio. As a rule, at the beginning you don’t really find fault. Therefore, I literally went to the first place where a coder-intern was needed. In those moments, circumstances did not soar, I just wanted to make up, and of course, to gain experience. And just a fierce desire to join the development environment. The fighting spirit was from the very start. Frankly, rushing for several years on the rise.

    The first euphoria ended and I went in search of a more comfortable environment. For me it was not important what kind of company it would be. The main thing is that there is a layout, and all other conditions should be at least a little adequate with a slight hint of perspectives. Again, literally after a couple of interviews, I got to the project. Actually, that's why I want to make a meaningful comparison.

    After the transition to one project, I did not feel particularly comfortable. It’s not that something infuriated me, it’s just that the brain has not yet been reorganized into design tasks. About half a year later, normal awareness came about how to develop harmoniously within the project framework. Here are a few nuances in working on a project:


    There is no client factor. I think there are no comments. One wild delight. As if he got rid of the persecution mania. Those who worked not in the most expensive studios, probably know firsthand about the pressure from the customer. Sometimes it looks like a dictatorship that overwhelms the whole working spirit.


    A bit of code. I can judge the front-end (HTML, CSS, JS). But this is something that has to be fought and a couple pushed into a dead end. On sub-projects there is code written about five years ago. Of course, then no one heard about the NSA and the modular layout system. Therefore, everything is wired to the cascade. Plus, all this had a hand in more than one workbench. The picture is not for the tender psyche. So refactoring is inevitable. In recent projects, we introduce an excellent thing MCSS and a simple, but more deliberate system. This brings more logic to layout. It allows you to get used to the team and develop a single style.


    After the studio, the hierarchy of managing people and dependence on other departments are a little annoying. In most cases not related to development. Conversations with them on business, the thing is not the most pleasant. But with those who talk cool in the topic, sometimes you can even get a fresh understanding (in those moments when they are not talked about by the manager, but by the developer). But we will assume that this compensation is for the lack of direct customers. However, the "Manager" is more a diagnosis than a role. Sometimes it seems they are in their fantasies, representing in their arsenal an army of developers on doping, sawing his project of "world importance". Well, let's give them a discount. Surely this obsession with the result is not out of bad intentions.


    Raise the bar. I don’t know how in Moscow. I’ll tell you about Peter. If you don’t work in a cool agency like Nimax Design or SoftFacade with solid clients, the growth ceiling will crush in about a year. The customers are the same; it’s not very practical to practice the new technology. Since it is expensive. If the design can be sold, then in practice the layout for the customer of the “full package” is some kind of internal process that is not quite clear to them. And which they don’t really want to delve into. On progressive projects, this should be given increased attention, since this is the most vulnerable part when scaling it. Here, to lose several thousand visitors, because of the "traveled" layout on any device, is much more critical than losing a couple of people at the promok, which are targeted at most advertising and design agencies.

    Bet on the future

    Studios usually rely on speed. If the projects are small, then there is no time left for licking the code. In the case of the project should work for the future. Think over the architecture, comb the styles and think about scaling soon. There is an opportunity to clean up a bit and polish your code-style.


    Perhaps this is due to more difficult tasks on the project compared to the bulk of typical studio tasks, but the skill level of specialists and the level of the general team are at a qualitatively high level. Of course, everything is relative. But I am doing a rather private comparison. Plus, one of the reasons is a larger team both in general and on individual tasks. Managers have a full arsenal for assault. In fairness, I’ll say that for all the time I have met only a couple of sensible managers who are able to carefully allocate power. I don’t want to offend the tough guys, but usually it’s a balance between burnt deadlines and attempts to tighten up one’s managerial incompetence. I will say without a doubt that the main team is gorgeous and to be a part of it is just high.

    In general, if you readjust to the desired wave, then working on the project is really cool. I can not say that I am completely satisfied with everything in its place. But I think everything is progressing for the better, and if not, then this is a good opportunity to transform thinking in the right direction. The main thing is not to drive yourself into slavery and not to forget about the ambitions that can be realized within the company. And as a rule, correctly oriented work is most useful to both parties.

    Also popular now: