🎶 Sometimes SE is not coding but orchestration
Recently, I've rolled out a "small" but important project our team was working on. We have decommissioned the old registration UI and enabled a new registration UI for 100% of our customers.
There were some peculiarities to this. The old registration was available on route
This project does not require lots of coding, but it requires a lot of coordination. Let me share the tools and practices that helped me to plan it and release it without major issues.
🖼 Mural board. I love collaborative whiteboard tools. You can add any content there — text, images, link this to each other or to the outside sources.
I gathered lots of information about the old and new registration to the board. How do people get to it? Which links are there? How can we map the old links to the new links? How is the old registration setup from the infrastructure level? How is the new one? I put everything to one place.
👥 Interview. I talked to all parties that are related to the registration — the application team, marketing, and sales. I showed them what we know on the Mural and together we have added missing information. We have identified what shall continue to work and for which reason. This way I ensured that all stakeholders are aware of what is happening and are aligned with the process.
📝 Rollout plan. Together with the platform team member, we have brainstormed and visualised the rollout plan. What was important for me, that each step is small and reversible. We have created two stickers for each step: what do we do and what is the effect of that step.
During the rollout I was marking each step as completed to maintain consistency and transparency.
🗣 Communication. Registration is quite important at our company, because otherwise customers can not start using our service. Therefore, it was important to inform everyone about what is going on, how this affects them and when it is done. I have communicated important steps in our public slack channel, so all stakeholders are informed and confident that we know what we are doing.
🎉 Celebration. After the rollout was performed and initial monitoring confirmed that everything is fine (registrations are coming). It is time to celebrate. We were able to decommission a relatively old front-end project, which was difficult to maintain within the last years. Also, we reduced the amount of services that our team shall maintain. In our department, we have a public slack channel where we share the great things we did. So I posted a wrap-up message there and we celebrated!
Celebrating small wins is a great practice, on the job or in our private lives. Do not waste an opportunity to release dopamine as a group.
🔮 Plan the future. A major part of the job is done. But we do not want to keep these redirects forever. So I have planned the meeting with the stakeholders to agree to start using new registration URLs only. This way, after some time, we will be able to reduce complexity even more.
▪️ Orchestration is also an important part of the role of Senior+ engineers. Small, but confident steps, will eventually bring you to the result.
Recently, I've rolled out a "small" but important project our team was working on. We have decommissioned the old registration UI and enabled a new registration UI for 100% of our customers.
There were some peculiarities to this. The old registration was available on route
X, the new one on route Y (because we were A/B testing them for some time). And we had to move the new one to the route Y* and decommission the old one. At the same time — the links to the old registration should continue to work because we have thousands of them on the internet, in the customer mail, and hardcoded in the old application versions.This project does not require lots of coding, but it requires a lot of coordination. Let me share the tools and practices that helped me to plan it and release it without major issues.
🖼 Mural board. I love collaborative whiteboard tools. You can add any content there — text, images, link this to each other or to the outside sources.
I gathered lots of information about the old and new registration to the board. How do people get to it? Which links are there? How can we map the old links to the new links? How is the old registration setup from the infrastructure level? How is the new one? I put everything to one place.
👥 Interview. I talked to all parties that are related to the registration — the application team, marketing, and sales. I showed them what we know on the Mural and together we have added missing information. We have identified what shall continue to work and for which reason. This way I ensured that all stakeholders are aware of what is happening and are aligned with the process.
📝 Rollout plan. Together with the platform team member, we have brainstormed and visualised the rollout plan. What was important for me, that each step is small and reversible. We have created two stickers for each step: what do we do and what is the effect of that step.
During the rollout I was marking each step as completed to maintain consistency and transparency.
🗣 Communication. Registration is quite important at our company, because otherwise customers can not start using our service. Therefore, it was important to inform everyone about what is going on, how this affects them and when it is done. I have communicated important steps in our public slack channel, so all stakeholders are informed and confident that we know what we are doing.
🎉 Celebration. After the rollout was performed and initial monitoring confirmed that everything is fine (registrations are coming). It is time to celebrate. We were able to decommission a relatively old front-end project, which was difficult to maintain within the last years. Also, we reduced the amount of services that our team shall maintain. In our department, we have a public slack channel where we share the great things we did. So I posted a wrap-up message there and we celebrated!
Celebrating small wins is a great practice, on the job or in our private lives. Do not waste an opportunity to release dopamine as a group.
🔮 Plan the future. A major part of the job is done. But we do not want to keep these redirects forever. So I have planned the meeting with the stakeholders to agree to start using new registration URLs only. This way, after some time, we will be able to reduce complexity even more.
▪️ Orchestration is also an important part of the role of Senior+ engineers. Small, but confident steps, will eventually bring you to the result.
👍8❤1
🎧 AI podcast to save your day
Yesterday I stumbled upon some insane AI application that was released 1 month ago (quite outdated by nowadays assessment, isn't it?). What impressed me is that it a) works, b) is free.
You do not need to wait further, I'm talking about NotebookLM.
This tool allows you to upload documents and different kinds of information to the notebook and then chat with it. But this is not new. What is new — it allows you to generate a podcast based on this information!
There are things you need to know:
1. You can upload documents in any language (I tried 🇺🇦), but it will generate podcasts in English.
2. There is only one setup — two hosts: one man and one woman.
3. The podcast is called "Deep dive". The hosts talk about the information you provided and add some other context from the large body of information that was used to teach that LLM. But they focus on the provided content.
4. When there is more content or known external references, the length of the podcast will be about 15 minutes. If there is less — up to 5 minutes.
🛟 Why is this helpful? I see two use cases:
1. In this fun form, you can study documents that you otherwise find boring. Human brains are wired to hear stories, not lists of facts. This "podcast" way will make it much easier for you to understand the gist of the document.
2. For people who are used to consuming information by listening, this instrument just helps to convert one format to another (+ more entertaining one). The quality of voices and their emotions during the talk are already on a high level.
As an example, just listen to the 3 minutes podcast about my write up "Sometimes SE is not coding but orchestration". From my perspective, it catches the sense of the post quite good. What do you think?
Feel free to share your generates podcasts in the comments.
Yesterday I stumbled upon some insane AI application that was released 1 month ago (quite outdated by nowadays assessment, isn't it?). What impressed me is that it a) works, b) is free.
You do not need to wait further, I'm talking about NotebookLM.
This tool allows you to upload documents and different kinds of information to the notebook and then chat with it. But this is not new. What is new — it allows you to generate a podcast based on this information!
There are things you need to know:
1. You can upload documents in any language (I tried 🇺🇦), but it will generate podcasts in English.
2. There is only one setup — two hosts: one man and one woman.
3. The podcast is called "Deep dive". The hosts talk about the information you provided and add some other context from the large body of information that was used to teach that LLM. But they focus on the provided content.
4. When there is more content or known external references, the length of the podcast will be about 15 minutes. If there is less — up to 5 minutes.
🛟 Why is this helpful? I see two use cases:
1. In this fun form, you can study documents that you otherwise find boring. Human brains are wired to hear stories, not lists of facts. This "podcast" way will make it much easier for you to understand the gist of the document.
2. For people who are used to consuming information by listening, this instrument just helps to convert one format to another (+ more entertaining one). The quality of voices and their emotions during the talk are already on a high level.
As an example, just listen to the 3 minutes podcast about my write up "Sometimes SE is not coding but orchestration". From my perspective, it catches the sense of the post quite good. What do you think?
Feel free to share your generates podcasts in the comments.
❤6
Good day 🎄,
The end of the year is coming and we look forward to giving and receiving presents. My suggestion — let's create 🎁 a present together. The present for AFU. Let's gather some money and purchase vehicles!
🚘 Vehicles at the front mean quick evacuation of soldiers, transportation of medical supplies and mobility of fire groups, and they are also consumables that are always needed
🫡 That is why I am joining the @tazyky.ua fundraising for 5 vehicles for the AFU
🎯 My goal: 10 000 UAH
Total goal: 1 000 000 UAH
🔗 Link to the bank:
https://send.monobank.ua/jar/5AJFedKK87
💳 Card number:
🅿️ PayPal:
https://www.paypal.com/paypalme/PavloPoliakov
🤝 Join our team by writing to @tazyky.ua
P.S.: all supporting banks and donors participate in the prize draw
The end of the year is coming and we look forward to giving and receiving presents. My suggestion — let's create 🎁 a present together. The present for AFU. Let's gather some money and purchase vehicles!
🚘 Vehicles at the front mean quick evacuation of soldiers, transportation of medical supplies and mobility of fire groups, and they are also consumables that are always needed
🫡 That is why I am joining the @tazyky.ua fundraising for 5 vehicles for the AFU
🎯 My goal: 10 000 UAH
Total goal: 1 000 000 UAH
🔗 Link to the bank:
https://send.monobank.ua/jar/5AJFedKK87
💳 Card number:
4441111128142290🅿️ PayPal:
https://www.paypal.com/paypalme/PavloPoliakov
🤝 Join our team by writing to @tazyky.ua
P.S.: all supporting banks and donors participate in the prize draw
send.monobank.ua
Безпечний переказ коштів
Надсилайте безкоштовно та безпечно кошти
👍4❤1
Hi people,
Fun story. Several times I've shared my PayPal here. And each time right away I receive a phishing mail about my PayPal shortly afterwards. (Image in the first comment ).
I have two variants:
1. There is somebody in the channel who is against fundraising and wants to hack me
2. Telegram groups are monitored by phishing bots
Either way there is only one right way to deal with it — donate.
So far we've gathered
🔗 Link to the bank:
https://send.monobank.ua/jar/5AJFedKK87
💳 Card number:
🅿️ PayPal:
https://www.paypal.com/paypalme/PavloPoliakov
You are the best 💙💛
Fun story. Several times I've shared my PayPal here. And each time right away I receive a phishing mail about my PayPal shortly afterwards. (
I have two variants:
1. There is somebody in the channel who is against fundraising and wants to hack me
2. Telegram groups are monitored by phishing bots
Either way there is only one right way to deal with it — donate.
So far we've gathered
8140 UAH and 60 EUR. Let's make sure we have 10.000 UAH in the jar. 🔗 Link to the bank:
https://send.monobank.ua/jar/5AJFedKK87
💳 Card number:
4441111128142290🅿️ PayPal:
https://www.paypal.com/paypalme/PavloPoliakov
You are the best 💙💛
send.monobank.ua
Безпечний переказ коштів
Надсилайте безкоштовно та безпечно кошти
👍8❤1
🗓 The 12 weeks year
Last years I understood that I have a problem with long-term vision and long-term planning. At the beginning of the year I started to work on the new pet project —
I feel comfortable when I need to distribute my tasks within the week or bring any current issue to the decent state. But how to make sure that these achievements add up and together create a better future for myself and my family, that I dedicate time to the things that are important to me in the long term?
The new year is coming soon and I want to try out a new process — 📙 The 12 week year. I just finished listening to this book and want to summarise it for you.
💡The main gist of the book is simple. Year is too long. Many things may happen within this timeframe, and you will not feel time pressure. So why to plan for the year? Let's focus on the upcoming 12 weeks. And for the next iteration, you can plan again. I like this concept.
Ok, accept that we plan for the next 12 weeks only is quite simple. But how to plan? There are five main stages of the process.
1️⃣ Create a vision. Write down your long-term vision for yourself. Who do you want to be? What do you want to achieve? What does it mean for you? Write it down. Create a mid-term vision — where do you want to be within a 3-5 year period? Write it down as well.
Get emotionally attached to that vision. It must be something which drives you. This would be the reason why you will execute your plan.
2️⃣ Plan. Select one or two goals for the next 12 weeks. These goals shall just bring you closer to the vision. You won't achieve it in 12 weeks (if you do — try to be more ambitious the next time), but if you reach them, you will be closer to your vision. Small, but confident steps.
Now think of the tactics — how can you reach those goals in 12 weeks? Create a more detailed plan with the tasks for each week.
3️⃣ Control. You gave a promise to yourself, you promised that at least for these 12 weeks you would commit towards working on the set goals, and you have a plan. Make sure that you stick to the plan and work. Nothing more, you cannot guarantee that you will achieve your goals, but you can guarantee that you will execute.
4️⃣ Measurement and assessment. At the beginning of each week measure which percentage of the plan you've executed the last week? What went good and what went bad? What can be adjusted to make this week better?
5️⃣ Time management. Everyone has 24h per day. We need to use them wisely, so we do have time to work on our 12-week plan. In the book they suggest dedicating at least 3 hours where nothing interrupts you and you can work on your strategic goal heads down.
And that's mainly it. Plan, commit to 12 weeks, execute, and on 13th week you have a free week. Week where you celebrate and plan another 12 week year.
▪️ I'm going to try that out and see if it solves my issue with the long-term planning. The thing that inspires me is creating and writing down a ✨ vision ✨, the fact that you need to plan for 12 weeks only and that this will allow me to give myself permission to work only on several goals at the same time.
Last years I understood that I have a problem with long-term vision and long-term planning. At the beginning of the year I started to work on the new pet project —
1to100, but did not finish it 📉 it just faded away, because of different priorities.I feel comfortable when I need to distribute my tasks within the week or bring any current issue to the decent state. But how to make sure that these achievements add up and together create a better future for myself and my family, that I dedicate time to the things that are important to me in the long term?
The new year is coming soon and I want to try out a new process — 📙 The 12 week year. I just finished listening to this book and want to summarise it for you.
💡The main gist of the book is simple. Year is too long. Many things may happen within this timeframe, and you will not feel time pressure. So why to plan for the year? Let's focus on the upcoming 12 weeks. And for the next iteration, you can plan again. I like this concept.
Ok, accept that we plan for the next 12 weeks only is quite simple. But how to plan? There are five main stages of the process.
1️⃣ Create a vision. Write down your long-term vision for yourself. Who do you want to be? What do you want to achieve? What does it mean for you? Write it down. Create a mid-term vision — where do you want to be within a 3-5 year period? Write it down as well.
Get emotionally attached to that vision. It must be something which drives you. This would be the reason why you will execute your plan.
2️⃣ Plan. Select one or two goals for the next 12 weeks. These goals shall just bring you closer to the vision. You won't achieve it in 12 weeks (if you do — try to be more ambitious the next time), but if you reach them, you will be closer to your vision. Small, but confident steps.
Now think of the tactics — how can you reach those goals in 12 weeks? Create a more detailed plan with the tasks for each week.
3️⃣ Control. You gave a promise to yourself, you promised that at least for these 12 weeks you would commit towards working on the set goals, and you have a plan. Make sure that you stick to the plan and work. Nothing more, you cannot guarantee that you will achieve your goals, but you can guarantee that you will execute.
4️⃣ Measurement and assessment. At the beginning of each week measure which percentage of the plan you've executed the last week? What went good and what went bad? What can be adjusted to make this week better?
5️⃣ Time management. Everyone has 24h per day. We need to use them wisely, so we do have time to work on our 12-week plan. In the book they suggest dedicating at least 3 hours where nothing interrupts you and you can work on your strategic goal heads down.
And that's mainly it. Plan, commit to 12 weeks, execute, and on 13th week you have a free week. Week where you celebrate and plan another 12 week year.
▪️ I'm going to try that out and see if it solves my issue with the long-term planning. The thing that inspires me is creating and writing down a ✨ vision ✨, the fact that you need to plan for 12 weeks only and that this will allow me to give myself permission to work only on several goals at the same time.
👍13❤5
⚡️ Flash news for all GitLab users
Start your year the right way. 💡 TIL that you can go to
That's it. Your future self says "thank you", now they do not need to see
Reducing the cognitive load is one of the best things we can do for ourselves and our team. Let's rock in 2025 🤘.
Start your year the right way. 💡 TIL that you can go to
Preferences (click on your avatar, then Preferences) there you can find Time preferences and uncheck Use relative times. Press Save.That's it. Your future self says "thank you", now they do not need to see
3 weeks ago and try to convert that to the exact date. Now gitlab directly shows 18 Dec 2024.Reducing the cognitive load is one of the best things we can do for ourselves and our team. Let's rock in 2025 🤘.
👍16❤9
🤖 Try it: Trae
The day before yesterday, ByteDance, the one that stands behind TikTok and CapCut (and what else?), announced a release of the new AI IDE — Trae.
Trae can be considered as a direct competitor of Cursor and less direct but still a competitor of your
I tried Trae a little the same day and was astonished even before it got to AI. I just opened one of our
It was pure
The company behind the product is indeed controversial, and I was surprised that they released such product. We have a tendency to think that TikTok steals our data, and now they suddenly release an IDE. Are they also going to "steal" our code? Most likely the correct question is — are they going to use our code to teach their AI? These questions have no answer. But I still suggest to trying Trae with one of your own projects.
The day before yesterday, ByteDance, the one that stands behind TikTok and CapCut (and what else?), announced a release of the new AI IDE — Trae.
Trae can be considered as a direct competitor of Cursor and less direct but still a competitor of your
IDE + continue.dev. Under the hood, Trae is still based on VS Code, as others, but you do not need to install any addons, and the default configuration looks promising and visually nice 💅.I tried Trae a little the same day and was astonished even before it got to AI. I just opened one of our
JavaScript projects using this IDE and saw that there is a "Testing" tab. IDE defaults allowed it to find the tests in our project, and immediately, without any additional configuration, I was able to run them one be one from IDE and even run 🐛 debug! It was pure
Spring + IntelliJ experience, where things just work from project to project. I have never seen this working by default in the JavaScript projects, where the setup of the project is almost always different.The company behind the product is indeed controversial, and I was surprised that they released such product. We have a tendency to think that TikTok steals our data, and now they suddenly release an IDE. Are they also going to "steal" our code? Most likely the correct question is — are they going to use our code to teach their AI? These questions have no answer. But I still suggest to trying Trae with one of your own projects.
👍10❤1
👋 Шановні друзі, я до вас з саморекламою. Я повернувся у великий інстаграм та перейменував мій минулий
Буду писати на теми про технічне лідерство, знімати reels, ділитися своїм життям у сторіз.
Будь ласка розгляньте пропозицію підписатися та продивитись мій перший рілз до кінця, щоб інстаграм зробив мене зіркою 🙏
https://www.instagram.com/pavlopoliakov
gooddevknows тех аккаунт на pavlopoliakov і буду тепер вести його українською. Буду писати на теми про технічне лідерство, знімати reels, ділитися своїм життям у сторіз.
Будь ласка розгляньте пропозицію підписатися та продивитись мій перший рілз до кінця, щоб інстаграм зробив мене зіркою 🙏
https://www.instagram.com/pavlopoliakov
👍44👎7❤3
🗓 The 12-Week Year: 6-Week Update
When you remember, at the end of last year, I shared the idea of the 12-week year and committed to trying it out. Today, my 7th week started, and I want to share my experience about the process.
First, I did an exercise and formulated my ✨ vision ✨. What I want to achieve in general and what I want to achieve in the mid-term. That was nice and indeed allowed me to fantasize about how my life will look if I do everything I have planned 📈.
Then, I chose topics that will bring me closer to my vision. For the first 12 weeks, I chose to — improve my 🇩🇪 German speaking and start developing my Instagram account. Those are strategic goals. Then, I chose tactics — how will I try to achieve that?
Let’s abandon specifics, but I can tell you that indeed, in these 6 weeks, I have done more than I did toward these goals the whole last year (because last year I was mostly dreaming about it and not doing it).
✅ What I did so far
* I practice German regularly (5 times a week I do the Üben app, 1 time — a 30-minute talk with a native).
* I released 5 episodes of a podcast in German, "6 Minuten Wöchentlich". This way, I practice writing, and then I check it against ChatGPT and learn from my mistakes.
* I relaunched my Instagram in Ukrainian (+ polished my profile there).
* Shot and edited 7 reels and 3 posts (already got 20+ subscribers from reels only).
* I kind of created a content plan (not a plan, but a list with ideas to pick from).
✚ What I achieved besides
* I feel I am more confident in sporadic German conversations.
* I learned how to work with sound using Audacity; I can edit my podcast myself.
* I learned how to edit videos using CapCut. I already used that for work once.
* I am learning how to create more engaging reels.
* Recently, I added some health tactics to the weeks — drink more water and meditate for 5 minutes, 5 times a week.
💡 Other insights
* I now know that any tasks, even small tasks, still mean you need to dedicate time to them. Shoot and edit a reel? 1.5h. Write and edit text for a 6-minute podcast? 1h. Record and edit a podcast? 1h.
* I think for the next 12 weeks, I will also add work-related goals. Anyhow, I work 8h a day. Why not structure my progress there and celebrate achievements?
* It’s useful to reflect on the past week (I do it on Monday) and write down what you can improve this week, changing your weekly plan a little. For example — split tasks into smaller ones (create a reel scenario, shoot a reel, edit a reel).
* Yes, it’s difficult to combine all these new tasks with regular work and life. But having them recorded, knowing that I want to set a checkmark there, makes me do them 💪.
* It’s fine to NOT do everything that was planned. It’s more important to reflect on why and adjust for the future.
👍 I’m going to continue, and let’s see what I will achieve in the next 6 weeks. So far, I’m happy about this experiment. When you want to bring more strategy to your life, I would encourage you to try this framework out.
When you remember, at the end of last year, I shared the idea of the 12-week year and committed to trying it out. Today, my 7th week started, and I want to share my experience about the process.
First, I did an exercise and formulated my ✨ vision ✨. What I want to achieve in general and what I want to achieve in the mid-term. That was nice and indeed allowed me to fantasize about how my life will look if I do everything I have planned 📈.
Then, I chose topics that will bring me closer to my vision. For the first 12 weeks, I chose to — improve my 🇩🇪 German speaking and start developing my Instagram account. Those are strategic goals. Then, I chose tactics — how will I try to achieve that?
Let’s abandon specifics, but I can tell you that indeed, in these 6 weeks, I have done more than I did toward these goals the whole last year (because last year I was mostly dreaming about it and not doing it).
✅ What I did so far
* I practice German regularly (5 times a week I do the Üben app, 1 time — a 30-minute talk with a native).
* I released 5 episodes of a podcast in German, "6 Minuten Wöchentlich". This way, I practice writing, and then I check it against ChatGPT and learn from my mistakes.
* I relaunched my Instagram in Ukrainian (+ polished my profile there).
* Shot and edited 7 reels and 3 posts (already got 20+ subscribers from reels only).
* I kind of created a content plan (not a plan, but a list with ideas to pick from).
✚ What I achieved besides
* I feel I am more confident in sporadic German conversations.
* I learned how to work with sound using Audacity; I can edit my podcast myself.
* I learned how to edit videos using CapCut. I already used that for work once.
* I am learning how to create more engaging reels.
* Recently, I added some health tactics to the weeks — drink more water and meditate for 5 minutes, 5 times a week.
💡 Other insights
* I now know that any tasks, even small tasks, still mean you need to dedicate time to them. Shoot and edit a reel? 1.5h. Write and edit text for a 6-minute podcast? 1h. Record and edit a podcast? 1h.
* I think for the next 12 weeks, I will also add work-related goals. Anyhow, I work 8h a day. Why not structure my progress there and celebrate achievements?
* It’s useful to reflect on the past week (I do it on Monday) and write down what you can improve this week, changing your weekly plan a little. For example — split tasks into smaller ones (create a reel scenario, shoot a reel, edit a reel).
* Yes, it’s difficult to combine all these new tasks with regular work and life. But having them recorded, knowing that I want to set a checkmark there, makes me do them 💪.
* It’s fine to NOT do everything that was planned. It’s more important to reflect on why and adjust for the future.
👍 I’m going to continue, and let’s see what I will achieve in the next 6 weeks. So far, I’m happy about this experiment. When you want to bring more strategy to your life, I would encourage you to try this framework out.
Telegram
Good dev knows
🗓 The 12 weeks year
Last years I understood that I have a problem with long-term vision and long-term planning. At the beginning of the year I started to work on the new pet project — 1to100, but did not finish it 📉 it just faded away, because of different…
Last years I understood that I have a problem with long-term vision and long-term planning. At the beginning of the year I started to work on the new pet project — 1to100, but did not finish it 📉 it just faded away, because of different…
1👍8❤3
Good day,
At first, I planned to write a regular post to build some credibility before running an ad. However, I was informed that all early bird tickets are already gone.
So, I’ll start by promoting the 3rd batch of my “Crash Course: Tech Leadership”, which I run in collaboration with fwdays.
The Tech Leadership Crash Course is a 3-day event, with each day dedicated to a key topic:
1️⃣ Leadership
2️⃣ Hard skills
3️⃣ Soft skills
Throughout the course, we explore and practice everything that will help you become a great tech lead. This means understanding how to support the business, empower your team, and feel confident in your role. More information on the couse page.
What’s new in the 3rd batch?
* Limited to 25 participants for a more interactive experience.
* ⭐️ New topic added: “Measuring Architecture” – because you can’t improve what you don’t measure, right? You’ll learn how to assess whether your architecture is maintainable and beneficial or if it’s time for a change.
As a member of this channel, you can use the promo code
The course language is 🇺🇦.
I will still post a regular post later.
At first, I planned to write a regular post to build some credibility before running an ad. However, I was informed that all early bird tickets are already gone.
So, I’ll start by promoting the 3rd batch of my “Crash Course: Tech Leadership”, which I run in collaboration with fwdays.
The Tech Leadership Crash Course is a 3-day event, with each day dedicated to a key topic:
1️⃣ Leadership
2️⃣ Hard skills
3️⃣ Soft skills
Throughout the course, we explore and practice everything that will help you become a great tech lead. This means understanding how to support the business, empower your team, and feel confident in your role. More information on the couse page.
What’s new in the 3rd batch?
* Limited to 25 participants for a more interactive experience.
* ⭐️ New topic added: “Measuring Architecture” – because you can’t improve what you don’t measure, right? You’ll learn how to assess whether your architecture is maintainable and beneficial or if it’s time for a change.
As a member of this channel, you can use the promo code
GOODDEVKNOWS for a 20% discount (while it’s still available). Hope to see some of you there!The course language is 🇺🇦.
Fwdays
Crash Course: Технічне лідерство
Курс для технічних лідерів: навички, архітектура, софт скіли.
👍8
⚙️Tech Leadership: Boosting your visibility
One of my favourite topics in the tech leadership scope is visibility. How would other people know that you are good enough to trust you, to agree with your promotion, to help you to implement your ideas? Visibility is not just about being seen, but about creating value and sharing insights that can help the team and the company grow. Recently, I stumbled upon two tools that I used and liked. I want to share them with you and you can share them within your company and increase your ✨visibility.
1️⃣ Promptfoo
When working with LLM I had an open question. How people test their AI integrations or chat bost? How do they chose which prompt is better? Can this be automated?
Promptfoo is a fantastic tool for testing and securing your LLM apps. It allows you to:
* Compare different prompts and models side by side.
* Evaluate outputs for accuracy, safety, and relevance.
* Automate testing to catch issues before they hit production.
Why it’s great for ✨ visibility: By using Promptfoo, you can demonstrate your commitment to quality and security in AI-driven projects. It’s a tangible way to show your team and stakeholders that you’re on top of the latest tools to mitigate risks and improve outcomes.
2️⃣ Racing Bars
Data storytelling is a superpower in tech leadership, and Racing Bars makes it easy to create engaging, dynamic charts. This library generates racing bar charts (you know, those cool animated charts that show rankings over time) based on your data. Check out the demo here.
Originally I found this service https://livingcharts.com/, which may generate cool looking video based on your data. But it's under the question if you can share your comany's sensitive data with a random service on the internet (better not).
The usage of the library is quite simple, the result is impressive. For example, you can build a chart how customers of your business were adding up throughout the years. Then share it with the company.
Why it’s great for ✨ visibility: Whether you’re presenting project progress, team performance, or market trends, Racing Bars can help you visualize data in a way that captures attention and makes complex information easy to understand. It’s a small investment in presentation skills that can have a big impact on how your insights are perceived.
❤️ I would love to hear if you used any of these tools.
One of my favourite topics in the tech leadership scope is visibility. How would other people know that you are good enough to trust you, to agree with your promotion, to help you to implement your ideas? Visibility is not just about being seen, but about creating value and sharing insights that can help the team and the company grow. Recently, I stumbled upon two tools that I used and liked. I want to share them with you and you can share them within your company and increase your ✨visibility.
1️⃣ Promptfoo
When working with LLM I had an open question. How people test their AI integrations or chat bost? How do they chose which prompt is better? Can this be automated?
Promptfoo is a fantastic tool for testing and securing your LLM apps. It allows you to:
* Compare different prompts and models side by side.
* Evaluate outputs for accuracy, safety, and relevance.
* Automate testing to catch issues before they hit production.
Why it’s great for ✨ visibility: By using Promptfoo, you can demonstrate your commitment to quality and security in AI-driven projects. It’s a tangible way to show your team and stakeholders that you’re on top of the latest tools to mitigate risks and improve outcomes.
2️⃣ Racing Bars
Data storytelling is a superpower in tech leadership, and Racing Bars makes it easy to create engaging, dynamic charts. This library generates racing bar charts (you know, those cool animated charts that show rankings over time) based on your data. Check out the demo here.
Originally I found this service https://livingcharts.com/, which may generate cool looking video based on your data. But it's under the question if you can share your comany's sensitive data with a random service on the internet (better not).
The usage of the library is quite simple, the result is impressive. For example, you can build a chart how customers of your business were adding up throughout the years. Then share it with the company.
Why it’s great for ✨ visibility: Whether you’re presenting project progress, team performance, or market trends, Racing Bars can help you visualize data in a way that captures attention and makes complex information easy to understand. It’s a small investment in presentation skills that can have a big impact on how your insights are perceived.
❤️ I would love to hear if you used any of these tools.
👍13
🤖 AI Hackathon, part 1
The week before last, we had two on-site days for the AI hackathon at Free2move. I organized the event and also participated in it. I’d like to share my learnings and insights. The story is quite long, so there will be two posts.
💡 Idea
At the end of last year, we had a working group investigating how we could enable our engineers to use AI in their daily work. We ended up making the following toolset available to everyone: continue.dev +
After some time, I ran a quick Slack poll and discovered that only 8 developers had tried it. Not cool 📉.
From another angle, I understand that generative AI and modern AI development aren’t just about chat interfaces — you can also use AI directly from code and integrate it into the product. That’s the part I found really exciting.
So I thought: what if we announce an AI hackathon to encourage people to explore AI? I brought the idea to the Director of Engineering, and he liked it. But he also had his own vision for the event.
A week later, this Director of Engineering resigned 🙃 which didn’t make the implementation any easier.
🏋️ Making It Possible
At the beginning of this year, I picked up the idea again. Before going to management, I decided to check if there was any traction. I asked people to submit ideas: where could we apply AI at Free2move? We received 21 ideas from 15 people.
With that information, I went to the new Director of Engineering. He liked it too. We agreed on the high-level format: a 1-month hackathon, where people work asynchronously for 3 weeks and spend 2 days in the office.
The DoE asked me to confirm with the business unit director that it was okay for people to dedicate time to the hackathon, since this meant they wouldn’t be working on business-priority topics during that time. I did that.
There was a general feeling that no one was against the idea, but also no one really wanted to drive it. I understood it would mostly be on me.
🤖 Hackathon
Finally, I announced that the hackathon would happen and shared the format. I asked people to join a new Slack channel and got 61 participants.
For the first event, I asked people to pitch their ideas and look for teammates. We ended up with 5 ideas. To my surprise, there weren’t many people willing to join teams. We ended up with one team of 5 and four teams of 1.
Over the next few weeks, we had two support sessions for hackathon activities:
1️⃣ In the first session, a member of the platform team and I prepared a service template that could be deployed to our platform and use AWS Bedrock. I showcased a simple Slack bot that could generate an image based on a Slack message. I reminded everyone that even a Slack bot with AI counted as a valid hackathon idea.
2️⃣ In the second session, I showcased promptfoo — a tool to test prompts and chat bots. I introduced the idea of testing AI outputs systematically.
Then came the 2 on-site days. I tried to lure people to the office with 🍕free lunch. Four people accepted, but only two (including me) actually came.
Tomorrow I will continue, sharing the results of the hackathon and what I have learned. Stay tuned.
The week before last, we had two on-site days for the AI hackathon at Free2move. I organized the event and also participated in it. I’d like to share my learnings and insights. The story is quite long, so there will be two posts.
💡 Idea
At the end of last year, we had a working group investigating how we could enable our engineers to use AI in their daily work. We ended up making the following toolset available to everyone: continue.dev +
AWS Bedrock. This way, engineers have access to a code assistant and chat right in the IDE of their choice.After some time, I ran a quick Slack poll and discovered that only 8 developers had tried it. Not cool 📉.
From another angle, I understand that generative AI and modern AI development aren’t just about chat interfaces — you can also use AI directly from code and integrate it into the product. That’s the part I found really exciting.
So I thought: what if we announce an AI hackathon to encourage people to explore AI? I brought the idea to the Director of Engineering, and he liked it. But he also had his own vision for the event.
A week later, this Director of Engineering resigned 🙃 which didn’t make the implementation any easier.
🏋️ Making It Possible
At the beginning of this year, I picked up the idea again. Before going to management, I decided to check if there was any traction. I asked people to submit ideas: where could we apply AI at Free2move? We received 21 ideas from 15 people.
With that information, I went to the new Director of Engineering. He liked it too. We agreed on the high-level format: a 1-month hackathon, where people work asynchronously for 3 weeks and spend 2 days in the office.
The DoE asked me to confirm with the business unit director that it was okay for people to dedicate time to the hackathon, since this meant they wouldn’t be working on business-priority topics during that time. I did that.
There was a general feeling that no one was against the idea, but also no one really wanted to drive it. I understood it would mostly be on me.
🤖 Hackathon
Finally, I announced that the hackathon would happen and shared the format. I asked people to join a new Slack channel and got 61 participants.
For the first event, I asked people to pitch their ideas and look for teammates. We ended up with 5 ideas. To my surprise, there weren’t many people willing to join teams. We ended up with one team of 5 and four teams of 1.
Over the next few weeks, we had two support sessions for hackathon activities:
1️⃣ In the first session, a member of the platform team and I prepared a service template that could be deployed to our platform and use AWS Bedrock. I showcased a simple Slack bot that could generate an image based on a Slack message. I reminded everyone that even a Slack bot with AI counted as a valid hackathon idea.
2️⃣ In the second session, I showcased promptfoo — a tool to test prompts and chat bots. I introduced the idea of testing AI outputs systematically.
Then came the 2 on-site days. I tried to lure people to the office with 🍕free lunch. Four people accepted, but only two (including me) actually came.
Tomorrow I will continue, sharing the results of the hackathon and what I have learned. Stay tuned.
👍8🎉1
🤖 AI Hackathon, part 2
Let's continue where we left. The hackathon had two on-site days. We are at the office.
🏢 At the office
We had two productive days. I worked remotely with my team, and we even continued working into the evening, handling some deployments at
I remember when I was 20+, I participated in an overnight hackathon. Now, I can’t imagine myself doing that 🙂 It’s better to sleep at night. But one of our teammates worked through the night to push our project a bit further.
🏆 Results
At the end of the 2nd in-office day we had our DEMO event. I invited our management and with the help of one proactive manager we were able to gather the jury and agree on the small prize for the participant.
I was afraid that from the 5 ideas which started the journey only 2 or 3 will finish. To my surprise we had 5 demos. Even people who I thought did not work on the stuff shared their progress and working demos.
It was a 🌟 success. Our CEO was also present on the demo and seeing the result he decided to upgrade the prize pool and give our a prize to every participant. Which was great and motivating.
People appreciated my effort and I got many congratulations on organising this event from A to Z.
✍️ What have I learned
1. It's not correct to assume that most of the people as as much fascinated with AI capabilities as you are :) It's fine that other people may not want to engage with new technologies, but just do their work. You need to motivate them.
2. When you have good idea and nobody is against it, it still does not mean that they actively support it. You need to keep pushing, when you want it happen. I appreciate our management in the support they provided.
3. Different things motivate different people. I was definitely charged as an organiser. But the rest of people might be less charged and it is fine. I appreciate that they still worked on the topic, learned something, and shared it outside.
4. Not everyone is sharing their progress. I only knew that 2 teams (including one where I was present) are working ont he idea. In fact 5 teams were working.
5. It was draining but still fun and useful. Both for me and for the company. We have tested some concepts, learned new technologies and showcased their application for our product. This helps us to be competitive.
I encourage everyone to push their companies at least to explore the AI opportunities. When you have any questions about the event, please, ask in the comments.
Let's continue where we left. The hackathon had two on-site days. We are at the office.
🏢 At the office
We had two productive days. I worked remotely with my team, and we even continued working into the evening, handling some deployments at
23:00 while integrating the LLM response as a stream. I remember when I was 20+, I participated in an overnight hackathon. Now, I can’t imagine myself doing that 🙂 It’s better to sleep at night. But one of our teammates worked through the night to push our project a bit further.
🏆 Results
At the end of the 2nd in-office day we had our DEMO event. I invited our management and with the help of one proactive manager we were able to gather the jury and agree on the small prize for the participant.
I was afraid that from the 5 ideas which started the journey only 2 or 3 will finish. To my surprise we had 5 demos. Even people who I thought did not work on the stuff shared their progress and working demos.
It was a 🌟 success. Our CEO was also present on the demo and seeing the result he decided to upgrade the prize pool and give our a prize to every participant. Which was great and motivating.
People appreciated my effort and I got many congratulations on organising this event from A to Z.
✍️ What have I learned
1. It's not correct to assume that most of the people as as much fascinated with AI capabilities as you are :) It's fine that other people may not want to engage with new technologies, but just do their work. You need to motivate them.
2. When you have good idea and nobody is against it, it still does not mean that they actively support it. You need to keep pushing, when you want it happen. I appreciate our management in the support they provided.
3. Different things motivate different people. I was definitely charged as an organiser. But the rest of people might be less charged and it is fine. I appreciate that they still worked on the topic, learned something, and shared it outside.
4. Not everyone is sharing their progress. I only knew that 2 teams (including one where I was present) are working ont he idea. In fact 5 teams were working.
5. It was draining but still fun and useful. Both for me and for the company. We have tested some concepts, learned new technologies and showcased their application for our product. This helps us to be competitive.
I encourage everyone to push their companies at least to explore the AI opportunities. When you have any questions about the event, please, ask in the comments.
👍4❤1🎉1
Уже наступного тижня стартує другий потік мого краш-курсу з технічного лідерства. Для читачів мого каналу — спеціальна пропозиція: за кодом
🦸 Є сумніви, що ви можете бути хорошим технічним лідером? Стаються напади синдрому самозванця? А хто взагалі ці "хороші лідери"?
💚 Це не проблема. Лідерство — це лише навичка, якій можна навчитися.
Запрошуємо на триденний краш-курс із технічного лідерства!
👉 Реєстрація та деталі: https://fwdays.com/event/tech-lead-course-2?code=GOODDEVKNOWS
📅 Дати: 10, 12 та 14 квітня
🔥 Залишилося 7 місць!
🔍 Краш-курс — це три великі модулі: Бути лідером, Hard skills, Soft skills.
Ми розглянемо:
✅ Що таке технічне лідерство і як стати хорошим лідером.
✅ Як створювати архітектуру, що вирішує задачі бізнесу.
✅ Як вимірювати архітектуру і бути впевненим, що ви рухаєтеся в правильному напрямку.
✅ Як пояснювати технічні речі так, щоб вас розуміли.
✅ Як проводити мітинги ефективно і приймати на них рішення.
🗣 Що кажуть минулі учасники:
Буде цікаво та користно!
GOODDEVKNOWS ви ще два дні можете отримати знижку 20%. Потім — лише 15%. Долучайтеся 🙌.🦸 Є сумніви, що ви можете бути хорошим технічним лідером? Стаються напади синдрому самозванця? А хто взагалі ці "хороші лідери"?
💚 Це не проблема. Лідерство — це лише навичка, якій можна навчитися.
Запрошуємо на триденний краш-курс із технічного лідерства!
👉 Реєстрація та деталі: https://fwdays.com/event/tech-lead-course-2?code=GOODDEVKNOWS
📅 Дати: 10, 12 та 14 квітня
🔥 Залишилося 7 місць!
🔍 Краш-курс — це три великі модулі: Бути лідером, Hard skills, Soft skills.
Ми розглянемо:
✅ Що таке технічне лідерство і як стати хорошим лідером.
✅ Як створювати архітектуру, що вирішує задачі бізнесу.
✅ Як вимірювати архітектуру і бути впевненим, що ви рухаєтеся в правильному напрямку.
✅ Як пояснювати технічні речі так, щоб вас розуміли.
✅ Як проводити мітинги ефективно і приймати на них рішення.
🗣 Що кажуть минулі учасники:
* Дуже багато корисної інформації за стислий термін курсу. Курс дуже концентрований.
* Структурування, виділені основні теми; цікаві практичні задачі; робота в команді над hard skills.
* Багато завдань. Теми, про які я не знав, що вони існують, а вони є важливими.
* Нова інформація + вижимки з цікавих робіт.
* Теорія поєднувалася з практикою; продуманий план лекцій. Є що пропрацювати та прочитати.
Буде цікаво та користно!
👍7❤1
📅 12 Week Year. Closure.
I want to finish my story about the first iteration of the 12 Week Year. I completed it on the 30th of March and then took a three-week pause. Now I’m in the 2nd week of my 2nd iteration.
Main conclusion: I can confidently confirm that during the active 12 weeks, I accomplished more than I did in the previous year for the chosen topics. The methodology works, and I will continue to use it.
At the beginning, I chose two goals: 🇩🇪 improve my spoken German and develop my 🖼 Instagram account. Along the way, I added 🧘 health. Let’s see what I achieved during these weeks.
🇩🇪 Improve spoken German
- Completed 60 lessons in the Üben app
- 11 lessons on italki, which is 6 hours and 30 minutes
- 10 podcasts of 6 minutes each
- At least 7,000 words written for podcast noscripts
- Read the first book in German
- 2,000 words of article retellings
🖼 Instagram development
- Revived the account
- Published 18 Reels
- 1 Reel went “viral”
- Published 3 posts
- Gained 555 followers
- Learned how to edit videos
- Learned how to add subnoscripts
- Create better content now
🧘 Health
- 40 liters of water (8 weeks, 5 days a week)
- 200 minutes of meditation
To me, this is a lot! And what I like about this methodology is that it’s as simple as “checking the checkboxes.” There is a week, there are checkboxes that you have planned, and you just need to take actions so you can check them off. I use this Notion template to manage it.
🔑 My key learnings
1. It works!
2. Taking small steps toward the goal is enough. It gives a sense of progress.
3. Every action takes time—more time than you expect when you imagine it. You need to account for that.
4. Integrate your work goals into the plan. You work 8 hours a day anyway, so why not add structure to it?
5. The plan is not set in stone. You can change and adapt your weekly checkboxes, but stick to the goal.
6. Just start
I know some people have already been inspired by the idea of the 12 Week Year methodology from my posts. I hope more people join ✨
I want to finish my story about the first iteration of the 12 Week Year. I completed it on the 30th of March and then took a three-week pause. Now I’m in the 2nd week of my 2nd iteration.
Main conclusion: I can confidently confirm that during the active 12 weeks, I accomplished more than I did in the previous year for the chosen topics. The methodology works, and I will continue to use it.
At the beginning, I chose two goals: 🇩🇪 improve my spoken German and develop my 🖼 Instagram account. Along the way, I added 🧘 health. Let’s see what I achieved during these weeks.
🇩🇪 Improve spoken German
- Completed 60 lessons in the Üben app
- 11 lessons on italki, which is 6 hours and 30 minutes
- 10 podcasts of 6 minutes each
- At least 7,000 words written for podcast noscripts
- Read the first book in German
- 2,000 words of article retellings
🖼 Instagram development
- Revived the account
- Published 18 Reels
- 1 Reel went “viral”
- Published 3 posts
- Gained 555 followers
- Learned how to edit videos
- Learned how to add subnoscripts
- Create better content now
🧘 Health
- 40 liters of water (8 weeks, 5 days a week)
- 200 minutes of meditation
To me, this is a lot! And what I like about this methodology is that it’s as simple as “checking the checkboxes.” There is a week, there are checkboxes that you have planned, and you just need to take actions so you can check them off. I use this Notion template to manage it.
🔑 My key learnings
1. It works!
2. Taking small steps toward the goal is enough. It gives a sense of progress.
3. Every action takes time—more time than you expect when you imagine it. You need to account for that.
4. Integrate your work goals into the plan. You work 8 hours a day anyway, so why not add structure to it?
5. The plan is not set in stone. You can change and adapt your weekly checkboxes, but stick to the goal.
6. Just start
I know some people have already been inspired by the idea of the 12 Week Year methodology from my posts. I hope more people join ✨
👍11🎉3
🤖 Trying out Codex
Several days ago, OpenAI introduced Codex, a cloud-based software engineering agent.
Today, I realized that I have access to it and decided to look around.
I connected it to my open-source repo https://github.com/PavelPolyakov/fastify-blipp. When you connect the repository, Codex creates an environment for it and runs some "default" tasks against the repo.
Among the first "default" tasks, which started the execution automatically (smart), there was:
* 🐛 Find an important place, find a bug, and fix it
🧐 My experience:
1️⃣ Codex found something and drafted the code change (🖼 #1 in the comments)
2️⃣ But it was not able to run tests; it shared the error that
3️⃣ I asked it to fix it
4️⃣ 1+ minute of public thinking and executing bash commands. It suggested changing the test command (🖼 #2 in the comments)
5️⃣ I asked why it removed
6️⃣ 1+ minute of public thinking and executing bash commands. It said that it did not remove anything and cross-env is in place (it was a lie). It suggested installing dependencies before the test run.
7️⃣ I asked to install dependencies and run tests
8️⃣ 1+ minute... it said that the test run still fails
👩⚖️ Overall observations:
* It's a good start for the product; things feel well thought out
* I like that they stream the model's "thinking," and it's possible to follow it, but you may also ask yourself, WTF are you doing?
* When the model "thinks," it feels like you have no impact (maybe I can get used to it)
* It was also looking for an
* I had no expectations and haven’t learned any specific way of working with the engineering agent so far (other than a "simple" chat). So, I consider my experience relevant.
Overall, it still looks like a loop where the model is executed with some context, and that model has access to the "tools". Pretty much like this.
Have you tried it? Feel free to share your experience.
Several days ago, OpenAI introduced Codex, a cloud-based software engineering agent.
Today, I realized that I have access to it and decided to look around.
I connected it to my open-source repo https://github.com/PavelPolyakov/fastify-blipp. When you connect the repository, Codex creates an environment for it and runs some "default" tasks against the repo.
Among the first "default" tasks, which started the execution automatically (smart), there was:
* 🐛 Find an important place, find a bug, and fix it
🧐 My experience:
1️⃣ Codex found something and drafted the code change (🖼 #1 in the comments)
2️⃣ But it was not able to run tests; it shared the error that
cross-env is missing3️⃣ I asked it to fix it
4️⃣ 1+ minute of public thinking and executing bash commands. It suggested changing the test command (🖼 #2 in the comments)
5️⃣ I asked why it removed
cross-env6️⃣ 1+ minute of public thinking and executing bash commands. It said that it did not remove anything and cross-env is in place (it was a lie). It suggested installing dependencies before the test run.
7️⃣ I asked to install dependencies and run tests
8️⃣ 1+ minute... it said that the test run still fails
👩⚖️ Overall observations:
* It's a good start for the product; things feel well thought out
* I like that they stream the model's "thinking," and it's possible to follow it, but you may also ask yourself, WTF are you doing?
* When the model "thinks," it feels like you have no impact (maybe I can get used to it)
* It was also looking for an
AGENTS.md file to read instructions for the coding agent. If I would have it, I guess it would have been beneficial.* I had no expectations and haven’t learned any specific way of working with the engineering agent so far (other than a "simple" chat). So, I consider my experience relevant.
Overall, it still looks like a loop where the model is executed with some context, and that model has access to the "tools". Pretty much like this.
Have you tried it? Feel free to share your experience.
Openai
Introducing Codex
Introducing Codex: a cloud-based software engineering agent that can work on many tasks in parallel, powered by codex-1. With Codex, developers can simultaneously deploy multiple agents to independently handle coding tasks such as writing features, answering…
👍4
Hi friends,
The war in 🇺🇦 Ukraine is still ongoing — it has been nearly 1200 days since the full-scale invasion began in 2022.
Despite various headlines and political statements like Trump’s “let’s see in two weeks,” peace still feels far away.
The Armed Forces of Ukraine continue to bravely defend not only their homeland, but also the rest of 🇪🇺 Europe from further aggression.
And they need our help — specifically, they need vehicles.
I've joined a fundraising campaign organized by my friend’s volunteer group tazyky.ua.
This incredible team has already delivered over 500 vehicles to the Ukrainian Armed Forces.
Their current goal is to raise 1.2 million UAH (about 25,000 EUR) to purchase more vehicles for the front lines. My personal goal is to contribute 10,000 UAH (about 210 EUR).
I invite you to donate any amount that feels right for you — every contribution brings us one step closer to peace in Europe 🙏.
Donate here:
💸 PayPal: https://www.paypal.com/paypalme/PavloPoliakov
💳 Monobank jar: https://send.monobank.ua/jar/36KZTp5qP6
Why vehicles?
They’re essential for rapid logistics, delivering ammunition, evacuating the wounded, and saving lives. But they’re also expendable — constantly in demand and often destroyed in action.
Thank you for standing with Ukraine. 💙💛
The war in 🇺🇦 Ukraine is still ongoing — it has been nearly 1200 days since the full-scale invasion began in 2022.
Despite various headlines and political statements like Trump’s “let’s see in two weeks,” peace still feels far away.
The Armed Forces of Ukraine continue to bravely defend not only their homeland, but also the rest of 🇪🇺 Europe from further aggression.
And they need our help — specifically, they need vehicles.
I've joined a fundraising campaign organized by my friend’s volunteer group tazyky.ua.
This incredible team has already delivered over 500 vehicles to the Ukrainian Armed Forces.
Their current goal is to raise 1.2 million UAH (about 25,000 EUR) to purchase more vehicles for the front lines. My personal goal is to contribute 10,000 UAH (about 210 EUR).
I invite you to donate any amount that feels right for you — every contribution brings us one step closer to peace in Europe 🙏.
Donate here:
💸 PayPal: https://www.paypal.com/paypalme/PavloPoliakov
💳 Monobank jar: https://send.monobank.ua/jar/36KZTp5qP6
Why vehicles?
They’re essential for rapid logistics, delivering ammunition, evacuating the wounded, and saving lives. But they’re also expendable — constantly in demand and often destroyed in action.
Thank you for standing with Ukraine. 💙💛
PayPal.Me
Pay Pavlo Poliakov using PayPal.Me
Go to PayPal.Me/PavloPoliakov and enter the amount. It's safer and more secure. Don't have a PayPal account? No problem.
❤25👎14👍11
Hi everyone,
Thank you for your contributions — we’ve raised
Running fundraisers is tough these days; everyone is tired in their own way.
But just like with tech leadership and staying true to our personal and company goals, we must accept that there is no finish line.
The path is the answer.
Let’s stay committed to our path of contributing to a fair outcome for Ukraine.
Please donate your part — let’s make it happen 🙌.
Donate here:
💸 PayPal: https://www.paypal.com/paypalme/PavloPoliakov
💳 Monobank jar: https://send.monobank.ua/jar/36KZTp5qP6
Thank you for standing with Ukraine. 💙💛
Thank you for your contributions — we’ve raised
7,650 UAH out of our 10,000 UAH goal.Running fundraisers is tough these days; everyone is tired in their own way.
But just like with tech leadership and staying true to our personal and company goals, we must accept that there is no finish line.
The path is the answer.
Let’s stay committed to our path of contributing to a fair outcome for Ukraine.
Please donate your part — let’s make it happen 🙌.
Donate here:
💸 PayPal: https://www.paypal.com/paypalme/PavloPoliakov
💳 Monobank jar: https://send.monobank.ua/jar/36KZTp5qP6
Thank you for standing with Ukraine. 💙💛
PayPal.Me
Pay Pavlo Poliakov using PayPal.Me
Go to PayPal.Me/PavloPoliakov and enter the amount. It's safer and more secure. Don't have a PayPal account? No problem.
❤15👎3