Programming to business: how do we do IT?
How business tasks bring programmers out of the shadows and why it turned out that communication is the strength of IT.
There is such an idiom in English – «it's not rocket science». We also say in such cases – «this is not the higher mathematics». It means: «Hey, it's easy!». Not abstruse, not too hard - accessible and understandable.

Our goal is this: customers should understand everything that we do for their business using programming. Our work should not be a «riddle» for them, they need to know what they are paying for.
Therefore, we confidently say: programming is not rocket science for them and for us. It's simple: just the best way to solve business problems with the help of our skills and knowledge.
How it was done before?
Even 10-15 years ago, developers were busy with tasks related completely to the specifics of programming. For example, develop messaging or mail service, create a blog or forum. There were specialists who were engaged in writing databases, organizing storage of information, etc.

Such tasks are related to infrastructure. The real benefit from these decisions the user usually cannot «touch» - but without them it is impossible to run any project.

So, 10-15 years ago, it was possible to say that programming is really «rocket science»: the development took place on the technology level, and the customer did not understand a word.

Fact: In India was widespread the practice of evaluating the work of a programmer by the amount of code written by him: the more lines - the better the specialist works and, therefore, the higher is paid. Smart developers specifically lengthened their code as much as they can, thus creating another idiom - the «Hindu code».
How does it work today?
Today programming is something «more terrible» than rocket science. It has one goal - to make the rocket fly, and for programmers the business poses many incredibly diverse tasks. Like if each of them is a rocket-maker, an exorcist, a vocalist, has a driver's license for BelAZ, a black belt for judo, a Siberian fishing cup, a scientific degree of economist and can bake tasty cookies. Well, sometimes cookies are not needed.
Now the focus is shifting: databases, messaging systems, libraries, frameworks, platforms and much more instruments have already been «invented», it works and solves, literally, all the infrastructure tasks. Moreover, the whole system is now so developed that if the programmer tries to implement something anew, then surely his «handmade» will turn out to be of lower quality.
This is the basis of our working manifesto: programming itself is not as valuable as solving problems with programming.
Therefore, the focus is gradually shifting from infrastructure problems to business problems, the solution of which is necessary for specific users. The programmer's mission today is not just to write code, but to compile a project from existing solutions and tools that will meet the needs of the business.
How is our work organized?
And while programmers are still taught to «write code», the professional sphere requires few other skills from them, the main one of which is communication. For example, everyone now is talking about the philosophy of Agile. According to science, this is a family of «flexible» approaches to software development. In fact, this is programming based on the adequacy of the approach to work, the human relationship between the developer and the client, and well-functioning communication at all levels.
The stereotype of «bearded wild programmers», who code while sitting in a distant cave, goes into oblivion. On the contrary, the business community is actively adopting the experience and technology of work (for example, the same agile) from the IT business. It turned out that these «introverts» build communication with the client so that they have something to learn.
- Today the task of effective communication with the customer is not the prerogative of the project manager alone. If this mission is entrusted only to PM, he will become a bottleneck, and even if he has only a few people on the project, he will not be able to discuss everything with the customer for them. Now we are faced with the problem of speeding up the production process. To solve it, it is necessary that the communication goes directly. The fact is that PM physically can't penetrate deeply into all the details of the product, some moments are available only to the developer. And if he is not motivated to give feedback to the customer - the project will suffer. A programmer now can't act according to the principle «I was told - I wrote code». Previously, feedback from developers was often ignored, programmers were told: «Write code, the rest is none of your business». And now everyone starting to listen to them, effective communication is considered as one of the main sources of production acceleration.

Eugene Tyumentsev
CEO, «Hello World! Technologies»
According to modern requirements, the programmer needs to develop not only his hard skills - professional skills only, but also soft skills, which include responsibility, courtesy, the ability to listen, speak and negotiate. The accents are shifting, the profession of a programmer is being transformed - and, in fact, the demand from them is no longer: «writes code - and that's enough». The question is whether he solves the problem or not.
We in «Hello World! Technologies» not only write and talk about it, but also follow our manifesto and respond to modern requests of the business environment. And with the example of our cases we show how we can, using knowledge in programming, solve the problems of business.