Latest / // TODO: Переписать — IT без бигтеха и успешного успеха / // TODO: Быть инженером
Transcript
- Artem: Hi! This is Tutu. I'm Artyom. Alex: You were so you were so intonationally good, I couldn't handle Artem: What Alex: It's you know, the with the Gypsy. Artem: Ilya and Sanya, yes. Alex: I'll try not to laugh. Artem: ⁓ Okay. Alex: So, this is Kom, let's record more ⁓ you'll yeah. Artem: So... Hi! This is Tutu to podcast about IT, how it lives outside of LinkedIn. My name is Artem, I Python developer. In recent years, I have been writing backends and various IA integrations in one outsource company. Every day I deal with such stories as the one you just heard. It seems that I spend time on convincing business not to anything crazy than to write the code itself. Alex? Alex: Hi everyone, my is Alex, I'm also a Python developer, I backends, integrations, and I often encounter strange things in IT. And now I to start passing sub-sets I pass several sub-sets and I got a pretty good statistics. and I have many interesting stories to tell you Artem: Clear. Let me you the story of the origin of this podcast and what is the idea it. The is quite simple and it was quite a ago. Alex and I have been writing to each discussing IT Mostly discussing work, how difficult it is some vacancies on this rather difficult labor And I thought, if we are about voice actors, why can't we talk about it on a Because it's something that can be interesting for other people. And that's it all happened. Plus, we noticed that in Russian-speaking IT content There are different podcasts about IT, we are not the first here. But these podcasts are usually little different. For example, these some technical podcasts where some industry From Yandex, Tinkova. general, some cool guys who are technically forged. Definitely not ordinary developers. Or these are kind of videos about the usual. and this is a tutorial video where you learn something by watching this video and practicing And in the middle is what we are to do now. 90 % of developers are ordinary developers. They work in ordinary companies, not in big tech companies. And these companies, as a rule, are no super cool processes. There no Cuber, no DDPractic and so on. And our goal is to tell the vision. from side, from side of usual developers about how we see IT and if you are interested, if you also enter in this percentage of then please watch this podcast and maybe you will yourself and you will be interested Alex: Yes, right. On the hand, big companies, industry on the hand, there motivational videos, how to enter in 3 months, and on. we are standing somewhere in the now and want to show our current realities Artem: Yes, that's right. Alex, you just touched on a rather interesting topic, how to get IT, and this whole story. Actually, it's worth talking about saying what to expect from this podcast, why it can be interesting and what it will be from other podcasts. Let's start with what this podcast. Alex: We don't have to do an interview with industry we don't need to network bank and so on. Artem: that We like to invite you, but our podcast is a little different. We want to ordinary people, ordinary developers, our roots, fact, work like bees in these 90 % companies, not in Big Tech, who don't go to conferences, maybe just sometimes watch YouTube conferences and so on. Alex: In Artem: Just bees, workers. This our audience. We are going to these people to our podcast and show how their work Alex: I think we will release some stuff like Domain Driven Design, like DDD, some strong technical stuff, like shower stuff, because there are other podcasts, books, resources, We will talk more freely here. Artem: Yeah. About DDD, actually, story is quite interesting. We had a time when Alex was interested in DDD, because he often goes for interviews and, accordingly, knows a about how the current rental Therefore, Alex can lot about DDD, both bad and good, but our goal is to simplify it Perhaps we will discuss DDD, but such a more ironic approach because as a in such companies where we work DDD is not needed at Alex: Well, let's say so, well, you can say so, yes, principle, plus or minus, plus or minus, yes, normally, probably, let's Artem: No more Lopez. Yes, we like argue on this topic, that DDD is needed or not needed, cool or not cool, in which companies it is it worth using for or not. In general, is possible that we will some topics from IT, including DDD. Although I think that now DDD is more relevant with the arrival of AI, what is happening with the agent and so on. But we Alex: Yes, tests are important here, of course. Let's the hype about AI, fear about AI and so on. We will talk about how we live with this AI in the current time. Artem: Yes, is clear that we will talk about AI. We live in such a time that impossible not to talk about AI. But we will talk about AI quite soberly and we will tell that AI will replace all developers because no, will not replace. We will tell the truth that is in our companies. Alex: Yes, that's right. will talk about the real story, some working moments, interviews, and what we discuss in the messages. It will interesting. Artem: Yes, task is not to that everything is bad now, is just terrible, difficult to job and so on. general, this is enough. Our task is to sober enough and objectively approach the evaluation of the situation and just share the experience that we and also guests, actually the same developers as we are, so that they also share their thoughts. That we this way Let's see how the industry like. Alex: Yeah, Artem: Okay, let me tell you Time of great stories. So that you understand what our manifesto what our podcast is what we mean when we say that we most ordinary developers and most likely 90 % of developers work in similar conditions us. My story is quite interesting. It's because it seems like it combines several aspects But let's in order. I work in outsourced company and one of the I'm working now, need to use API Pixels. Pixels are basically stocks, photos, videos, as far I know, but mostly it's just photos. Some photographers upload their cool photos there and these photos can be used. You can just to the Pixels see how it all looks, but they also have a of and you can get pictures according to specified parameters. Actually, actively use this Pixels But there is one problem. The that all back-end What is this problem? This problem is called rate limit. We have a certain limit to the number of requests that we can send to pixels. The limitations are quite severe in Pixels and in fact it is impossible to make load testing without breaking this rate limit. ⁓ We had situation when we needed two different keys for the QA environment and for production environment. ⁓ This is a big challenge, because you need to convince the company to provide these two keys. That is, need to two accounts and make two api keys. There is a problem. Because at that moment, key was only one. In ⁓ Pixels, you can create only one key, in general, one key for one account. So we had to create two keys. This first problem. The second problem is have a limit. It is to load tests and using only one key. This is a very bad practice. We cannot throw it on both QA on the prod. We need to divide it. I asked the management to several times that would nice for us to make two keys. there is such a thing as a bass factor and it would to this API key an official account of To this does exist. We do have an official account company, which linked to services, including API keys and so on. Some developer, like Vasya, can create account in the current time to use this api key, put it everywhere and then this Vasya will disappear and, accordingly, will have a problem, that is, we will be to access this account. Unfortunately, we company like this, so that you understand the problem, that is, everything happens badly, but the problem with api key itself was different and the story itself is a little different. In order to access to pixels and do everything right, need to two accounts, two api keys and, most importantly, need to the limit because the rate limit is too severe in pixels. I have repeatedly asked the management to do this and in order to remove the rate limit, just to just write to Pixels and explain what you need it how you use this service and so on there is a special instruction that you just follow send a letter, send a request and as a it's not difficult to it but, but, so that you understand every time I spoke and understood this problem in I was basically just ignored it's not important, we'll figure it later and so on. So bad. But I tried anyway, pushed, pushed and finally the manager came up a solution. solution to this problem. Alex, what you think Alex: and I remember this decision. You better ⁓ Artem: Well, okay, ask you, course, if we had a guest, we would ask. Alex already what decision my manager with. The brilliant was that instead of writing in pixels and for there, so that we have a rate limit, we will make our own service, which will simply rob pixels, take these pictures. Alex: Hahaha Artem: parse them, them in S3 and accordingly we thus collect a puzzle of these pictures we will have problems with rate limit because they will be well stored in our service on our S3 and everything will very cool and fun. That's that's the solution. Alex: Why use a ready-made solution if you can do your own Artem: It it would seem. By the is a leader, who was once an engineer. That is, he is also ex-developer. It is already clear that several years he has been in development at all, person has completely gone into business. But this kind of decision comes to people's And here, in fact, situation is quite interesting. That is, if you evaluate this idea ... you can divide it into three parts. Technically, it's a week of a separate infrastructure, need update this infrastructure, need to synchronize it. The legal problem is that Pixels has Terms of Service, and stealing Pixels is not a very good idea. Thus, we will simply Terms of Service. Alex: So he actually suggested to the service, right? Artem: Yes, I think he doesn't know what Terms of Service is and that there is a Terms of Service He just suggested this idea, like, let's do it this But in fact, yes, is such a legal problem. But business-wise, would seem that manager should also think from point of view of right? But from point view of business, what kind problem do have that this solution is simply useless. Globally, business doesn't need it at Why should create a service? Why should spend resources, time, infrastructure on If it's just a small local problem that needs to by writing a 5-minute letter to Pixels and that's And we'll of this red limit. Alex: So, without any code, without any can't write letter. Instead, can write a code. Artem: Absolutely. Yes, is, here is work for work. And this is such an approach of a That is, seems but after working quite a long time in such companies, I understand that in general it is a base already. But we even later. Actually, you interested how I solved this problem. I it, of course, by own As I said, I've the manager many not only the manager, but also project manager to close the question. But I was to do my service solve the technical Okay. I understand that this the to I'm a developer, not just that. I have solve business not just write code. And here I did it quite wisely. I just took everything on myself. I didn't ask to create accounts and so on, because I understand that it a lot of time until they are duplicated and create accounts. Until it all turns around, it's too much time. As a result, I made two accounts myself. I wrote in pixels. I followed the instructions and asked the frontender to make these small We took it from Pixels and named it Photography. These small, neat bottles. Everything very beautiful and neat. It not the user interface, but the user experience. Everything is very beautiful, laconic and great. I meet the of Pixels. I recorded demo video. and provided all these data to Pixels. In several iterations, literally, we two iterations, and they provided me with a new API key, which has absolutely no limits They said that they could provide not only one key, but general, okay. Now we a situation in the end that we have this one key absolutely without limits and there is a key with a Naturally, the without limits, I put on the Prod. production environment. But one with limits I left on QA. But in end, gave me what I can do load testing without problems, what has already been done. And secondly, it gave me the opportunity to sleep at night, because we now have no such limit and everything will be cool. I know that all this will work well. What do think, Alex? Alex: I think it's a interesting There are a lot of talking about architecture, code and so on. I haven't seen a podcast where they this kind of It's communication with business. It's very important. service from scratch, lot of and effort to spend on it, can take it and actually by communication with external providers or by communication with with stakeholders, if they are course in the contract if they normal and understand the problem, can solve much less effort and general completely, actually solve it, here Artem: Yes, everything is like that. The it seems quite indicative for our podcast, that is, this manifesto that we are promoting here. This situation says that developers often have follow what business But... If you blindly trust business and just follow what business then most likely you will get some kind of unreal monster that you don't need at And here it seems to very important to be exactly a developer, engineer and have opportunity to influence the business That is, need to fight that you you need to code sometimes. You can the problem much easier. I think it's different from a good developer, a good engineer, from a bad engineer. Because you can solve the in different ways. But you still to about what is profitable and what not. In this case, it's much more profitable to write pixels, solve the problem in few iterations, in 20 minutes. minutes than to this huge service and then still support it Alex: Yes, this case, without a line of and sometimes it seems to that need to delete the code, is, solve the problem Yes, course, you absolutely need to talk but of course would be good if these business also They listen to what engineers say. It would be great. Artem: Yeah, in general, write in the comments how this story is developing you. mean, have you any cases when the business man said to do what you don't need do all and you solved this problem How absurd it to you when the general manager, although from an engineering background in the past, offers such a solution? I how much you think it's normal? How much does fit into our concept that 90 % of companies are like this, that is, we work in this? This is not some big tech, probably in some big tech, although I think that big tech also fits, most likely, such stories, but yes, yes, but they have everything little cooler and on a scale than we have, most likely there a huge project, and then it turned out that no needs more that. Alex: I'm there some Artem: So, please, the comments, it will very interesting to how much it is reflected in your Meanwhile, we have a lot of great stories to This time we have a very cool story from Alex about how people are having interviews in 2026. Alex? Alex: How people are for new job in 2026 As I said before I at market now, what are the possibilities and I regularly have interviews, 2-3 times a week. I a case in a small educational platform. There were lot of stages. It all started with a communication with HR. The was strange. It was built in There greetings, but it's good. But not the There is a shortness, but it's okay. But I noticed a... How to I just read a from HR and she immediately wrote that she to make a with HR to screencall. I was little surprised and little nervous. Then we started to chat with to schedule a screencall. and it happened that one HR screencall, which is 30-45 minutes was for several days. On the first day, not exactly, the first part of this two-day HR screencall was... What's so special about HR? I late, everything is clear. I put our meeting and said that we had planned for this time, and Aichars was sorry. There another meeting, I couldn't come, etc. We discussed the first part of our HR screencall. HR said that they needed to run because we will the next meeting. I said, okay, okay. We agreed on second part the next day. Artem: some problems ⁓ Alex: The next day met and talked about out lot of interesting details about the about the stages in this company. They are for a super-mega-puper developer with 10 years of experience. Yes, 10 years. Artem: wow 10 10 plus years this is generally straight interesting interesting how many people in general fit under these 10 plus years Alex: This is a very good question, don't know what the 2 % of developers Artem: Yes, But if we your experience and mine, then maybe we will apply for this vacancy Alex: Da da da da da. To be HR understood how strange and huge is the process in the and that she wanted to the hiring process, to shorten the of the specialist. That's what Again, of stages, HR, technical, then screening, then life coding, system design, final with Timledome, final with CEO. There were more than five stages. Artem: You Wait, are off Google or what? Alex: So it's not Google, but Google. And then they didn't Artem: Yes, it happens. Maybe someone has 10 plus years of and who has passed. On the hand, the is now maybe by pushing such requirements, company feels that they can do What do think? Your experience, from side the person who has had a lot of conversations in recent times, what do think? Alex: 100 % Yes, a lot of things Of course, is the market of now in 2026, because there are lot of reductions, economic crises and on, and the AI boom, which also pours oil into fire. So the company has a huge choice among candidates, and they, respectively, They for the best specialist to close the vacancy. It is clear. ⁓ Yes, think so. course, it's a kind of employer and the company a very large selection of specialists, such multi-stage hiring I am an hire and Neuronka is hiring Neuronka, talking to Neuronka in the initial process when communication takes place. Yes, it's there. Artem: I think that should give a credit for that it's not for all companies. It's of thank God. It's an exception to the rules. So, most companies have more real requirements. Right, Vitya? Alex: Of course, it was a very extreme case. I a big selection of companies where I talked. In general, from a point view, companies are adequate, without any questions. are tech-sobies, with the life-coding is some kind final with the CTO, CEO In general, yes, in general, companies ... Plus or minus is ok. But again, emphasizing the current situation of labor we get some extreme cases. Artem: Yes, it's very interesting. I think that both of our stories show the story about the most common company. It's not about Google, not about Big Tech. The industry is in a transition stage. First you are here, this stage, then you in Big Tech, then then you are according to Big Tech start to some kind startup. And what if there is Big Tech? What if 90 % of people stay here, they stay at this step before Big Tech and are constantly in such conditions? Maybe it's okay? What do think? We easy questions. Alex: Yeah, well... If most of the stay in this niche, say, 90 % of this what can say? they stay, let's And I think that in such companies, as if ... It would be to of stages with some of those sabers, but not something so big-tastic, without any ups and downs, so Artem: I about the interview, it's that. I'm talking about the concept itself. That general, these two, our case they are about the fact that... most the work in these companies before I started working IT I thought that is something cool, complex, not very clear you build processes, is clear, are project managers, Agile, Sprints, DDD, Kubernetes very very smart words and you will be spinning but in fact When I came to IT maybe I was so lucky, but I realized that it's completely different. Everything different, everything different. the people with whom I talked, for all this time, for my entire career, developer, engineer, I realized that most people work in such conditions. Most people don't work in Big Tech. We often watch podcasts. with cool dudes who know example, podcast with Nikita Sobolev. Nikita is cool guy, I lot of respect for his videos. He lot for the community, for the botanists. But this is a unique person, a genius who is good at it. I think that most developers, if you to be objective, We are such an developers. It would be interesting to look at the situation from point view of regular person who works in the most regular companies, not in big tech companies, not open source, not being a star. That's it. What do you Alex? Alex: Yes, agree that for such cut, most developers... Indeed, have such extremes. There is open source, you said, there is a big tech company like Fanga. But most developers... Well, I don't think is anything wrong with being applied developer. We basically solve the problems of business with help of and so on. We more in the platform. Yes, many developers, think they are software engineers, developers. It would be interesting to talk to such people, make podcasts for such people, discuss the problems of this cohort. of Artem: Yes, Is okay? Actually, there a lot to discuss here and we will probably do in future podcasts. general, we have enough interesting First, if you ask very actively, we will tell you why our podcast is called To Do. It has a pretty interesting story So the to like and write comments. we definitely talk it. And of want, as I said earlier, to some news of Python with invited guests, because in principle we are in Python as a language, but we not limited to Python. That is, we generally about IT. We want to everything related to IT. This is about NIME and about AI. Today we didn't touch AI at there is a abyss where you can dive and not dive. Only Liniva does talk now. Therefore, naturally, will discuss AI and how we AI ourselves, and how best to do this for the application developer. Also we will invite some interesting guests to Not stars, but just interesting guests from the most ordinary companies. And ask them questions about how they work, how different the processes from ours, if they these processes, how they are from the and so on. Alex: Yes, right. It would to talk to Artem: necessarily, following podcasts wait if you liked this podcast please write about it how much do you think this topic is relevant that what we show the cut of the most ordinary workers and how much you think this is promising format If there are many it will very good and we will be glad to make such content for you, also for ourselves. We use this podcast to speak because sometimes we really want to do it. Sometimes there is not enough from what is happening. It happens. Alex: Yes, that's right. Artem: But in general, we are for positive, that is, we are for looking at everything positively, optimistically and trying to think about the Because in general, our industry is quite interesting, for whom this is not secret. A sea of new opportunities and of course we want to opportunities, on podcasts and discuss them. Therefore, be to subscribe to channel, like, write comments, tell us how you this podcast. how do you like this topic, what should be improved and so on. Any criticism will be applied. Also, understand that Alex and are this first time, as we have said, we not some stars, we are just the most ordinary developers and beekeepers who work, do not work in big tech and so on. That is, we are just doing this first time, so you should also take this That's today, and see you in the next podcast Alex: Ha Artem: Thank you. Alex: See you thanks!