yegor256 podcast

Video is here: https://youtube.com/live/QlxTNu9IzMs

N25: Linux и JetBrains BAN | WordPress vs. WP Engine | ВК увольняет | Doom в Telegram | Питер Тодд? Oct 30, 2024

Video is here: https://youtu.be/PB5WNqN6HrM

Video is here: https://youtube.com/live/Xlz4dHtZ83k

Video is here: https://www.youtube.com/live/vIG53nxbWMI

Video is here: https://youtube.com/live/Aw5AGYp9QEw

Video is here: https://www.youtube.com/live/j9TGVT_j38w

F40: Дерзкий менеджер | стратегия программиста | KPI архитектора | эра облаков всё? | MVC - это зло? Sep 08, 2024

Video is here: https://www.youtube.com/live/Ebaxo8TnW3s

И27: И. В. Аржанцев | ФКН ВШЭ, ICPC, стартапы, студенты, аспирантура, JetBrains, Yandex, MIT Sep 03, 2024

И27: И. В. Аржанцев | ФКН ВШЭ, ICPC, стартапы, студенты, аспирантура, JetBrains, Yandex, MIT by Yegor Bugayenko

Video is here: https://youtube.com/live/siLfhb-HW74

И26: В. А. Петров | математика, СПбГУ, R&D, наука в Китае, аспирантура не для всех Aug 20, 2024

И26: В. А. Петров | математика, СПбГУ, R&D, наука в Китае, аспирантура не для всех by Yegor Bugayenko

F38: МИФИ или курсы? | офис или Бали? | кодер в Скуфиндуе | стартапер vs. Enterprise | ООП умирает? Aug 16, 2024

Video is here: https://youtube.com/live/BgSb8PT3txA

Video is here: https://youtube.com/live/Z-vZthdBMTs

F36: Блокировка YouTube | C++ в 49 лет | удаленка в Армении | работа в США | тимлидство Aug 02, 2024

Video is here: https://youtube.com/live/_H0isUrZ8l0

F35: Books on Java | Java or Kotlin? | Programmer evaluation | Drive by Daniel Pink Aug 01, 2024

Video is here: https://youtube.com/live/YpGg65a1aWI

N24: Путин запретил тапать хомяка! Цены на печенье? Блокировка YouTube, Санкции, Инклюзивность Jul 23, 2024

Video is here: https://youtu.be/KoGoyeFNgpA

F34: PHP или Python? | удалить Microsoft | Azure + .NET + C#? | CrowdStrike | SberJDK Jul 19, 2024

Video is here: https://youtube.com/live/fSiNDxTyp6M

И24: Н. В. Литвак | математика, искусственный интеллект и перспективы молодежи Jul 19, 2024

Video is here: https://youtu.be/Gp4J2dK0umU

Video is here: https://youtube.com/live/3QOevN0n-WQ

F32: Рен Женфей | PMP Exam Prep | продакт без опыта | стратегия джуна | совет тестерам Jun 14, 2024

Video is here: https://youtube.com/live/s7eIBPA81iA

BB1: Будьте смелее, покажите свое резюме Jun 12, 2024

Video is here: https://youtu.be/af6bidlat6Q

Video is here: https://youtube.com/live/C1WG7SM75eQ

F30: Роберт Мартин vs Кейси Муратори | язык V | Трамп | США vs Китай | работа в Huawei May 31, 2024

Video is here: https://youtube.com/live/8M1wpAdDDOY

И23: А. С. Медведников｜язык V - простой, быстрый, безопасный, скомпилированный, Open Source May 28, 2024

Video is here: https://youtu.be/xMGNlUZQ-6w

И21: А. В. Гасников | ректор Университета Иннополис, школы, ВУЗы, этика ИИ, будущее науки в России May 21, 2024

Video is here: https://youtu.be/KkTkDHp7nd4

И20: Д. К. Завалишин | Фидонет, Фантом ОС, Яндекс, Digital Zone, Управление сложными ИТ проектами May 21, 2024

Video is here: https://youtu.be/F1vpnQ__E8A

И22: Р. Н. Василишин | приключения биомассы, сталинизм, конспирология, солнечный круг - сыроедение May 21, 2024

Video is here: https://youtu.be/YUFX1g_Pejk

F29: Сareer path｜coder or engineer｜remote work | CTO or a startup｜project fails May 18, 2024

Video is here: https://youtube.com/live/7oy91g30DkU

И19: И. В. Оселедец｜AIRI, искусственный интеллект, ChatGPT, H-Index, математика и визы в Европу May 13, 2024

Video is here: https://youtu.be/9cKX1SlkZeI

N22: AI, Vision PRO, Нейролинк, Врач GigaChat, Сэм Альтман, Госкапитализм, Цензура, Навальный, Театр May 13, 2024

Video is here: https://youtu.be/gmVm63hBpPQ

N21: Зарплаты и Увольнения в IT, Аврора, Блокировки, Слово Пацана, Религия и ЛГБТ, Пелевин May 13, 2024

Video is here: https://youtu.be/xOfIFpI2nkQ

N19: Москва-Сити, Цифровой Рубль, Threads, Хакеры и Байкал May 13, 2024

Video is here: https://youtu.be/sSGD6D92JL0

N17: Rust, Зарплаты, Увольнительные Шутки и Биполярный Мир May 13, 2024

Video is here: https://youtu.be/1KxqtLe1kQY

N14: Стартапы, Предприниматели, JetBrains, Илон Маск и Twitter, Оскар и Will Smith, Жириновский May 13, 2024

Video is here: https://youtu.be/hKvWaHFMuLY

N9: Codex, Приватность, Дипфейки, Windows 365, Удаленка May 13, 2024

Video is here: https://youtu.be/weriC7HBuJo

N8: Космический туризм, Рынок труда, AI и кодинг, Русские хакеры May 13, 2024

Video is here: https://youtu.be/XFGqqTSWE_E

N7: Роскомнадзор, Вакцинация, Китай и Биткоин, Новый Chrome, ИИ May 13, 2024

Video is here: https://youtu.be/Fj2Ut5wQpW8

N6: Китайское черное зеркало, NFT токены, New IP, новые языки программирования May 13, 2024

Video is here: https://youtu.be/hEB4_8TfIu8

N5: Роскомнадзор, Китайские хакеры, Google и их офис, Rockstar Games May 13, 2024

Video is here: https://youtu.be/9-qHtEMtvgk

N4: Clubhouse, GameStop, Навальный, Китай, ИИ, Биткоин и Патенты May 13, 2024

Video is here: https://youtu.be/BtpXp4npVQs

F19: Elon Musk sues OpenAI｜Copilot vs. Slaves｜R&D｜DevOps｜Money｜Open Source May 13, 2024

Video is here: https://youtube.com/live/AR8Y8lfHtQU

F27: Data Engineering｜Procrastination｜Code Ahead Principles｜IT revolutionaries May 13, 2024

Video is here: https://www.youtube.com/live/q9fY_uju_Vw

F21: Math and EOLANG｜Management｜Zerocracy｜10K lines of code｜OOP｜Java I R&D｜IT STANDUP May 13, 2024

Video is here: https://www.youtube.com/live/7mh6YHFbt6s

F18: Из сеньера C++ в джуны｜разница senior и middle｜идеи для Open Source May 13, 2024

Video is here: https://www.youtube.com/live/Y-2Gfyj0Dhg

F17: Carlson｜Navalny｜IT in Russia｜Elegant Objects｜discrimination in the US May 13, 2024

Video is here: https://www.youtube.com/live/Qsdrlln6Ru4

F16: Python после 40｜ООП｜гемблинг в стартапах｜Copilot｜из синьера в джуны May 13, 2024

Video is here: https://www.youtube.com/live/dOiiPQiLc24

F15: System Analysts｜GitHub Copilot｜Depression｜Art and Cinema May 13, 2024

Video is here: https://www.youtube.com/live/Es2u-uAMmO8

F14: Карьера｜Увольнения｜ChatGPT｜Марксизм｜Спорт｜Семья May 13, 2024

Video is here: https://www.youtube.com/live/MvcE7JKBvOQ

F13: Programming｜Management｜Career｜ChatGPT and Politics May 13, 2024

Video is here: https://www.youtube.com/live/ZL3MrihGC0I

F12: Взлом Apple｜X｜США vs Китай｜Глупый Начальник｜Умный Архитектор May 13, 2024

Video is here: https://www.youtube.com/live/KU4mURw4JNs

F11: Apple Watch patents｜Recruiters｜Film Making｜OOP May 13, 2024

Video is here: https://www.youtube.com/live/hP40z9VwBxE

F10: Gemini｜Musk & STEM｜Apple GDP｜Образование｜Культура｜Карьера May 13, 2024

Video is here: https://www.youtube.com/live/x-gOa77p0Jc

F9: Meta AI｜Happiness｜Gemini AI｜Disney vs Elon Musk｜Spotify｜Apple May 13, 2024

Video is here: https://www.youtube.com/live/qmvZGTAHx1g

F8: X Antisemitism｜ChatGPT birthday｜Henry Kissinger｜Gaza｜Zerocracy｜XDSD May 13, 2024

Video is here: https://www.youtube.com/live/4-EwFWb4rb4

F7: OpenAI｜Starship｜Binance｜Ukraine｜Future of Russia May 13, 2024

Video is here: https://www.youtube.com/live/Dl1JhD_19JM

F6: Career｜Management｜Remote Work｜Procrastination｜Chinese Clothes May 13, 2024

Video is here: https://www.youtube.com/live/hsW13vBR624

F5: PDD｜Books｜Quality of Code｜Requirements Engineeing｜Career May 13, 2024

Video is here: https://www.youtube.com/live/LQxZ8GXlws4

F4: Team Mgmt｜Career｜Morality｜AI｜Chinese Cars｜After-Life May 13, 2024

Video is here: https://www.youtube.com/live/nT1Bd5VYVj0

И10: Обабков И.Н. | индивидуальные образовательные IT траектории в УрФУ May 12, 2024

Video is here: https://youtu.be/VdTVKggQKv8

И11: Легалов А.И. | автор языка Пифагор современное IT образования в РФ [ВШЭ] May 12, 2024

Video is here: https://youtu.be/TEMIYBrk1Ww

F3: OOP｜Job Market｜Junior Coders｜ChatGPT｜Capitalism｜Palestine ｜Career May 11, 2024

Video is here: https://www.youtube.com/live/7pBD45NvSQk

F2: Remote Work, Zerocracy, Crisis in Europe, Code Ahead, Teaching OOP, etc. May 11, 2024

Video is here: https://www.youtube.com/live/xEk4dFf4bUA

F1: Future of Software, Programming, Work Remotely, etc. May 11, 2024

Video is here: https://www.youtube.com/live/cfD8gApC4P8

F28: Python собеседование｜свобода в сети｜переезд в Европу｜Open Source｜Django May 11, 2024

Video is here: https://youtube.com/live/SdqY8LZU8uw

И9: Ицыксон В.М. | исследования IT научное программирование в ИТМО May 09, 2024

Video is here: https://youtu.be/0uUGCZEvjLk

И12: Себрант А.Ю. | Яндекс, будущее ИИ, стартапы, роботы, БПЛА, дрон vs курьер [eng sub] May 05, 2024

Video is here: https://youtu.be/qF3krHWQz-o

И5: Шалыто А.А. | ИТМО, ICPC, JetBrains, лучший айти стендап в России! [eng sub] Apr 30, 2024

Video is here: https://youtu.be/TlO6lPZrC3g

И13: Недоря А.Е. | Никлаус Вирт, Архитектурное программирование, Компиляторы, Кронос, Тривиль Apr 28, 2024

Video is here: https://youtu.be/FGXws8lrkoI

F26: Как завести девушку? | слить бюджет на дармоедов | тестировщик должен сломать код Apr 27, 2024

Video is here: https://youtube.com/live/MlBXNhUZxPw

Video is here: https://youtube.com/live/NZ5dN37gsw8

И14: Скляров Д.В. | Positive Technologies, кибербезопасность, реверс-инжиниринг, хакеры Apr 21, 2024

Video is here: https://youtu.be/VPQQUEIIQMo

И7: Фоменко А.Т. | Новая Хронология, мировая альтернативная история, критика и разоблачение НХ Apr 18, 2024

Video is here: https://youtu.be/Ijy8_3efUuo

И15: Панов А.А. | Deep Tech, Neiry, КБ-12, стартапы, инвестиции, наука и роль государства Apr 14, 2024

Video is here: https://youtu.be/wKWt9l9Ll4U

Video is here: https://youtube.com/live/2bW1nnSXM50

И8: Носовский Г.В. | Новая Хронология, мировая альтернативная история, критика и разоблачение НХ Apr 11, 2024

Video is here: https://youtu.be/4-9MmyBP7gA

F23: Management | Career | PhD | OOP | Java Apr 10, 2024

Video is here: https://youtube.com/live/FPAHs9-Zsbo

И16: Рыжков Е.А. | PVS-Studio, Static Code Analyzer, AI Analyzer, Legacy Code, Open Source Apr 07, 2024

Video is here: https://youtu.be/hp_hFI1rl9A

F20: Java после 35 | джуны без опыта | оверскил | сдельная зарплата | тайм-менеджмент Apr 01, 2024

Video is here: https://youtube.com/live/7mh6YHFbt6s

F22: Как быть джуну? | из программиста в менеджеры | цель тестировщика | ИИ в Яндексе Mar 31, 2024

Video is here: https://youtube.com/live/_olSJKagmC4

И6: Зуев Е.А. | высшее айти образование в России далеко от идеала! Mar 31, 2024

Video is here: https://youtu.be/g8PEEX-aUWY

И18: Елизаров Р.А. | JetBrains, Kotlin, ICPC, спортивное программирование, Яндекс, ИТМО, Codeforces Mar 29, 2024

Video is here: https://youtu.be/7ohc0Ljyxdc

ITPurpleConf: далеко ли до Стэнфорда? Mar 24, 2024

Report at the IT Purple Conf conference (March 16-17, 2024, Moscow, MIPT). Conference website: https://fpmiconf.ru/ Video is here: https://www.youtube.com/watch?v=VZDBG-BInWo

И4: Яков Файн | не все так однозначно! жесткий диалог айтишников про СВО Mar 24, 2024

Video is here: https://youtu.be/fMwHdedplwU

И17: Райгородский А.М. | ФПМИ МФТИ - убираем потолки, не срывая крышу Mar 23, 2024

Video is here: https://youtu.be/sLysj4IPP54

N20: Наука, Иммиграция, Анонимность, Telegram, Оппозиция Sep 05, 2023

Video is here: https://youtu.be/_o-5-QGD8Lw

N19: Москва-Сити, Цифровой Рубль, Threads, Хакеры и Байкал Jul 31, 2023

Видео здесь: https://youtu.be/sSGD6D92JL0

N18: Удаленка, ChatGPT, Neurolink, Наше ПО и Образование в России Jul 04, 2023

Video is here: https://youtu.be/SdBLL56rZGA

N16: ICPC, ПМЭФ, Эмиграция, Дискриминация, Образование и Пиратство Jul 02, 2022

Video is here: https://youtu.be/W4lcWiIa9QY

M199: Unit tests are the Safety Net that you can't afford to not use Jun 24, 2022

Coding without unit tests similar to building a house without a safety net: you can do this, but your productivity will be extremely low. You will mostly be driven by fear. Can you afford this? Video is here: https://youtu.be/Y0Zx_sdVG48

N15: Русские Хакеры, Agile, Профсоюзы, Безработица, Русский GitHub May 19, 2022

Video is here: https://youtu.be/OWUnLpeAcyA

M193: What is fun and joy for you, being a programmer? May 19, 2022

Video is here: https://youtu.be/5FckPa6aOok

M194: Keep a balance between work for money and investments into yourself May 19, 2022

Video is here: https://youtu.be/SNAULZ4KRak

M195: Static analyzers find bugs in code, but who finds bugs in programmers? May 19, 2022

Video is here: https://youtu.be/JilDO5zqcuc

M192: Find a way to structure your opinion after each interview of a new candidate Apr 18, 2022

When you interview each new candidate, your opinion will most likely be pretty subjective. I suggest you try to find a way to structure it with some generic approach, which you will apply to all interviews. This will help you not miss important information and always have a good explanation for your decisions. The video is here: https://youtu.be/o_S1aSLoh14

M191: When a bug report is not as simple as it can be, don't fix it Apr 11, 2022

The best bug report is the one that represents the simplest possible scenario where the bug shows up. Most bug reports are not like that. I suggest rejecting them and letting their authors simplify them. Blog post: https://www.yegor256.com/2022/03/29/bugs-occam-razor.html The video is here: https://youtu.be/UXu_Uejo0f0

M190: Make sure the bugs you report explain the simplest possible scenarios Apr 04, 2022

When you report a bug, try to make it as simple as it's possible. When you accept a bug, ask the reporter to make it as simple as possible. Somebody has to do this work of minimization of a bug. I suggest this work is done by reporters. Video is here: https://youtu.be/jiEJnLBowHc

M189: How would you decide who deserves to be authors of a published paper? Mar 21, 2022

When you write an academic paper or a patent together with your co-workers, who of them becomes your co-authors? All of them? Some of them? Who decides? In this video I'm asking for your help in defining the formula. The video is here: https://youtu.be/TF8MKOfo3gI

N13: Украина, Санкции, Железный Занавес, Иммиграция Mar 11, 2022

Video is here: https://youtu.be/6RYinocrR0E

M188: I don't think ML will ever be able to write code Feb 21, 2022

AlphaCode recently announced that its ML model can write code as good as an average programmer. I don't think it's writing and I don't believe in this approach we will ever be able to get anything meaningful aside from pure marketing speculations.

Shift-M/53: Adam Tornhill on auto-detecting technical debt hotspots Feb 11, 2022

Adam is a creator of CodeScene.com, a cloud service where you can check the quality of your code and spot places where your technical debt is the largest. He's also the author of "Your Code as a Crime Scene" book. Adam's personal website: https://www.adamtornhill.com Twitter: https://twitter.com/adamtornhill?lang=en The book: https://amzn.to/3AXCPxz

M187: Why did I return a new MacBook Pro 2021 worth $5500 back to Apple? Feb 10, 2022

Two months ago I bought a new MacBook Pro. After a month of waiting, I received it. My frustration was huge. I returned it to Apple and got the money back. Here is why. The video is here: https://youtu.be/JYW25iNTqUE

Shift-M/52: Aino Corry about meetings and retrospectives Jan 28, 2022

Aino Corry is an expert in Agile and specifically in retrospectives: these are special type of meetings a team must conduct by the end of a sprint, a phase, or the entire project. Aino's twitter is here: https://twitter.com/apaipi?lang=en Aino's website: https://metadeveloper.com And the book is here: https://amzn.to/3fREDOQ The video is here: https://youtu.be/ByatpkT2-tI

N12: Анонимизация, Выгорание, Циан и славяне, Сколково и стартапы Jan 22, 2022

Video is here: https://youtu.be/AqfH1ABgx9o

Shift-M/51: Michael Kay about XSLT Jan 18, 2022

Michael Kay is the editor of the W3C XSLT 2.0 and 3.0 language specifications for performing XML transformations and the developer of the Saxon XSLT and XQuery processing software. The video is here: https://youtu.be/2Zt9oJtFKGw

M186: Make sure your CV has something nobody else has and you'll be fine Dec 27, 2021

"How do I become a software architect with a six-figure salary?" is the question I'm being asked very often. I can't say I know the answer but here is the strategy I would recommend to pursue: make sure your profile differs from all others somehow. The video is here: https://youtu.be/mJb-H-8npFk

Shift-M/50: Andy Hunt about tech book publishing Dec 24, 2021

Andy Hunt is a writer of books on software development, co-author of "The Pragmatic Programmer," one of the 17 original authors of the Agile Manifesto, and a founder of "The Pragmatic Bookshelf" publishing agency. The video is here: https://youtu.be/zebqDkVfY-g

M185: CTO has to write code and delegate management to PMs Dec 20, 2021

Chief Technical Officer (CTO) is usually the highest technical position, where usually is a person who doesn't really remember how to write software code. A better setup would be with a CTO who codes every day and delegates management to Project Managers. Video is here: https://youtu.be/b_w85hL2o04

M184: Keep your best programmers from maintenance mode Dec 13, 2021

Developing a software product and maintaining it are two different activities, even though both are very important. Developers and maintainers are people of different types and if you want to keep your best developers in the project, don't allow them to become maintainers. The video is here: https://youtu.be/_BbgpugwpEI

M183: Start making a software product from configuring its build pipeline Nov 29, 2021

Some of us think that the functionality of a product comes first, while the build pipeline (testing, coverage control, static analysis, style checking, deployment) goes next. Moreover, some of us believe that functionality is the foundation of a house, while the build is more like a decoration. I strongly disagree. Video is here: https://youtu.be/TcD6jJKaLcg

N11: Meta, Трамп, Дискриминация, PinePhone, Домогательства, Профсоюз Программистов Nov 27, 2021

Video is here: https://youtu.be/NLNVkvnrr3Q

M182: Open source products are made by young and hungry Nov 22, 2021

When you are young and hungry for attention, you make open source products. They give you appreciation and recognition faster than anything else. When you grow up and become known for the products you created earlier, you lose interest in open source and give space to next-generation attention seekers. Thus, let's appreciate their work to keep new products coming. The video is here: https://youtu.be/eyx69afklkY

M181: How do you manage under-performers? You ignore them. Nov 15, 2021

What do you do with those who don't deliver almost anything except promises? Do you try to motivate them, discipline, organize, find better tasks for them? I suggest a better strategy: just ignore them. This is how you will save your time and energy for those who deserve your attention. This is how you help your team achieve better results. The video is here: https://youtu.be/KvwEKA4Owuc

M180: Pre-commit Hook is a wrong idea Oct 25, 2021

Many programmers love to use pre-commit hooks to run the build and test the code before it gets to the repository. I believe it's a bad idea for two reasons.

M179: Calibrated Achievement Points (CAP) to measure R&D productivity Oct 18, 2021

Most of us believe that it's impossible to measure the productivity of programmers, researchers, software experts, and other "talents". I believe it's possible. Here is a simple framework, which has experimentally proven its effectiveness. Try it out in your team. The blog post is here: https://www.yegor256.com/2021/10/12/calibrated-achievement-points.html The video is here: https://youtu.be/Qii3yrQJdHs

N10: GitHub от Мишустина, iPhone 13, Умные очки, и Линус Торвальдс Sep 29, 2021

Video is here: https://youtu.be/9bRCNcMox4g

M178: Try to focus your team on artifacts and their delivery status Sep 27, 2021

Proper management is not something any team can afford. Here is a simplified framework, which gives you enough control over project affairs and at the same time doesn't bother the team too much. I called it SIMBA since it's a Simplified Management By Artifacts. The blog post is here: https://www.yegor256.com/2021/09/09/simba.html The video is here: https://youtu.be/939ntzufGB0

M177: Auto-formatters do more harm than good for programmers Sep 13, 2021

Using auto-formatters to make your code look nice is a bad idea. Mostly because they won't teach you anything about code quality. Instead, always format your code manually. This is how you learn a lot about quality and good programming practices. The video is here: https://youtu.be/NoBE-WNIVVs

Shift-M/49: Greg Young about Software Design Sep 09, 2021

The video is here: https://youtu.be/JER03qMCmIk

N9: Codex, Приватность, Дипфейки, Windows 365, Удаленка Sep 04, 2021

Видео здесь: https://www.youtube.com/watch?v=weriC7HBuJo

M176: Often digital discussions don't work because there is no decision making process defined Aug 30, 2021

Very often, as far as I can tell, programmers are not willing to participate in digital discussions (tickets, chats, boards) because they are afraid of bullying: their decisions may and will be criticized without any predefined rules. The solution is simple: make sure your team has a structured process of decision making, with explicit roles and permissions.

Shift-M/48: Jeff Atwood about knowledge management in software teams Aug 23, 2021

Jeff Atwood is an American software developer, author, blogger, and entrepreneur. He writes the computer programming blog Coding Horror. He co-founded the computer programming question-and-answer website Stack Overflow and co-founded Stack Exchange, which extends Stack Overflow's question-and-answer model to subjects other than programming. Jeff's blog: https://www.codinghorror.com

M175: When the customer asks you to convince them, just don't Aug 13, 2021

Say you are an architect, and your customer or a product owner asks you to explain your technical decisions, you may immediately jump into explanations. Don't do that. There must be a clearly drawn line between your territory of responsibility and authority and theirs. They define requirements for the product you develop, you make technical decisions according to the requirements. You don't need to explain anything. The video is here: https://youtu.be/WapJducA2NY

M174: Your personal goals go first, team and project goals next Aug 10, 2021

Your personal goals must be much more important for you than your project and your team's ones. Of course, the team will try to make you sell your soul to them, but you must not forget about your long-term objectives. The video is here: https://youtu.be/rR4UFPvAulI

N8: Космический туризм, Рынок труда, AI и кодинг, Русские хакеры Aug 01, 2021

The video is here: https://youtu.be/XFGqqTSWE_E

Shift-M/47: Bjarne Stroustrup on the future of programming Jul 27, 2021

The video is here: https://www.youtube.com/watch?v=ae6nFZn3auQ

M173: The inspiration for coding comes from personal projects Jul 26, 2021

"Where do you find inspiration for coding," I hear very often. The trick is simple: I try not to stay for too long with the same code base. I try to extract sub-module, libraries, or frameworks from the products I work with and make them standalone products. This is fun: making new products. The video is here: https://youtu.be/ygoWsvgXe1c

M172: When requirements are vague, you don't quit, you make your own product Jul 19, 2021

Very often our managers don't know exactly what we have to do. They don't have specific requirements, they don't know how to specify tasks for us. Is it bad? Many people complain and quit. I suggest the opposite strategy: you say and do what you think is important. Make your own requirements. The video is here: https://youtu.be/a_UEkcV9laA

M171: submit your research to ICCQ Student Research Competition Jun 11, 2021

This year we organize a competition for student researchers. If you are a student (MSc, BSc, PhD), you most certainly do some diploma work. When finished, publish your results at ACM/IEEE conference and send us a link. We may give you a reward. The video is here: https://youtu.be/53DCw1QyDRc

M170: recruiters may do a better job if list to us programmers Jun 08, 2021

We all know how annoying are the recruiters who spam us instead of finding the right methods of approaching us carefully. Here is a quick summary of the advice I would give them all. Video is here: https://youtu.be/dlPk1AE2aQk

M169: Before you write a good text make sure you like how it looks May 30, 2021

Every time I start a new book, an article, or a new software project, I spend a lot of time making sure it visually looks nice. Sometimes this process even takes longer than the writing itself. I'm kidding about this, but it's not so far from the truth. Visual representation of data/text is very important. The video is here: https://youtu.be/l4PhrB4AytY

N6: Китайское черное зеркало, NFT токены, New IP, новые языки программирования May 19, 2021

The video is here: https://youtu.be/hEB4_8TfIu8

M168: a professional software engineer may also be a scientist/researcher May 11, 2021

Computer science is not so hard to do. If you are a professional software engineer, you can present your results in an academic way and publish them at one of those computer science conferences. You will get yourself a status of a researcher. This will only help you in your career. The video is here: https://youtu.be/ARwiHvTA4dc

M167: Sometimes you have to be an imposter, either you like it or not Apr 20, 2021

When you deal with a weak and incompetent manager, who is not capable of finding a way to measure people's results objectively, you have to behave like an imposter. If you don't, somebody else will and the manager will think that this guy is the best guy in the team, no matter what are the actual achievements. Read the blog post: https://www.yegor256.com/2021/03/03/imposters-to-win.html The video is here: https://youtu.be/ulrMXmIcC4w

M166: Challenging tasks and objective appraisal is what keeps top performers in the team Mar 29, 2021

You can acquire a new team member by making a better offer. I mean money. But you can't keep them with money. To keep someone in the team, especially if this is a top performer, you need two things: 1) challenging tasks, and 2) objective appraisal. Both of them are only available to good and strong managers. Video is here: https://youtu.be/bRXaMOJMJYk

M165: Contribute to the community if you want to do "good" Mar 17, 2021

Just working for a product, creating a product, and making your customers happy doesn't mean being good. It only means being successful, rich, or effective. It's a pretty selfish strategy. If you consider yourself as a "good" person (whatever it means), you should think about giving something to the community, for free. The video is here: https://youtu.be/TM7RodFnRr4

Shift-M/46: Fair Management with Pim De Morree Mar 17, 2021

Our special guest is Pim de Morree from https://corporate-rebels.com/ More about Pim: https://corporate-rebels.com/rebel/pim Twitter: https://twitter.com/pim_de_morree LinkedIn: https://www.linkedin.com/in/pimdemorree/ The video is here: https://youtu.be/VXbi5TXMsrY

M164: Fixed-Price contracts are much worse than Time&Material Mar 01, 2021

If you outsource part of your software development project to a third-party, you may think that the best type of contract to sign is Fixed-Price: you set the scope, they promise the time and price, they deliver, you check the quality, and you pay. It sounds right, but in reality, it'll be a disaster. Instead, always sign Time&Material contracts: you tell them how much resources you need, they give you a quote per hour, you manage them, they work for you, you pay every month. This is much more effective. The video is here: https://youtu.be/xUALewcix44

M163: If you as a manager don't punish wrong-doing, the team will punish you Feb 17, 2021

It's your job as a manager in a software team — to identify wrong behavior and find ways to punish it. The best manager, of course, will configure the management system so that it will enforce the punishment. Average managers use guilt and emotions as tools for that. Bad managers are scared to even think about punishment. The video is here: https://youtu.be/2lyz-CRGBwk

M161: When punishment is justified in a software team? Feb 11, 2021

Most of us are so scared now of the word "punishment" that all types of mistakes made by programmers remain unnoticed, very often. I believe, there are many types of mistakes that have to be punished. Everybody will win: the project, the people, and our customers. The video is here: https://youtu.be/zJ_PqlMcYcE

M161: It's not the competition that destroys a team, but unfair rules Feb 09, 2021

Many of us believe that competition is not something a software team may need. Moreover, competition may destroy a team killing morale and promoting conflicts. This may happen, but not because the competition is a bad idea, but due to the misconfiguration of its rules. The video is here: https://youtu.be/TyHCjKOFsBo

Shift-M/45: Risk Management with David Hillson, the Risk Doctor Feb 06, 2021

The video is here: https://www.youtube.com/watch?v=L2vUKqEgdys

M160: Traditional top-down planning doesn't work, try better alternative Feb 01, 2021

Traditionally, you tell your team what needs to be done and then force them (or motivate) to do it. You basically try to make your plans their plans. It works sometimes in some industries, but doesn't work with us programmers: we are too spoiled and lazy. I suggest a better planning principle: you let your people decide how many awards they are going to earn and then build your plans on top of their selfish desires. The video is here: https://youtu.be/vaFPNdNaOAY

M159: If your objective is to keep the team intact, competition is not for you Jan 28, 2021

Competition in a team works only if are ready to lose some part of your team, and very soon. If you don't want that to happen and your main objective is to keep the team intact and alive — competition will only do you a bad favor.

N3: Cyberpunk, русские хакеры, Твиттер и Трамп, цензура и ИИ, и Биткоин Jan 22, 2021

Video is here: https://youtu.be/nenmlYhNM50

M157: We must measure productivity, but using the right metrics only Jan 14, 2021

Measuring the productivity of programmers to many of us seems like a dangerous process, which leads to a lack of value delivered. This is true, but only if you use the wrong metrics to do your measurements. Use the right ones and everything will be fine. Video is here: https://www.youtube.com/watch?v=yZcNHZ_FJco

M156: Competition doesn't contradict with collaboration Jan 11, 2021

Many management experts believe that competition kills collaboration and that's why a software team must not encourage their people to compete. Instead, they should collaborate and help each other. I don't see a contradiction here. Moreover, I don't think that a fully altruistic collaboration is at all possible and/or productive. I argue with Allen Holub in this video. The video is here: https://www.youtube.com/watch?v=qRuzYdmgjCg

M155: The best and the only way to reward top talents is recognition through fair competition Dec 28, 2020

It's a well-known "fact": best programmers are 30x times more effective than their average colleagues. How do you reward them? You pay them 30x salaries. Of course, you don't. However, they do deserve such a reward and won't work hard, if you don't give them something of this size. The only replacement of money is recognition, which you can give them only through fair competition. The video is here: https://youtu.be/2bEB3phUXA4

M154: Proper competition prevents cheating in a software team Dec 24, 2020

If there is no competition in your team, everybody will soon be interested in making deals and cheating. The only simple rule that may prevent this from happening: when I win, you lose. If such a rule exists there, your team members will always be interested in achieving more instead of compromising the system. The video is here: https://youtu.be/pgwVAaV0tRw

Shift-M/44: Allen Holub on management, motivation, and estimations Dec 22, 2020

Shift-M podcast: https://www.yegor256.com/shift-m.html Allen Holub personal website: https://holub.com/ Allen's Twitter: https://twitter.com/allenholub Video is here: https://youtu.be/8OKdilyNOIg

M153: How managers in self-managing orgs judge your performance? Dec 21, 2020

I think there is a simple metric we all can use to understand who the minds of managers in teal organizations work. Just count the amount of message they send you every day and you will understand where you are standing compared to others in your team. No sarcasm. The video is here: https://youtu.be/TmAJPeM4UlE

N2: Фейсбук, Биткоин, COVID, Open Source, PHP 8, Дудь и его долина Dec 17, 2020

Video is here: https://youtu.be/ECu4kXLYrD4

M152: There is no management without personal responsibility Dec 14, 2020

A famous book "Reinventing Organizations" suggests a new model of management, where people are not personally responsible for mistakes, but everybody altogether share responsibility and avoid hierarchies. I don't understand how this can work. It can't. Video is here: https://youtu.be/WZlIb5oxDBQ

M151: Don't judge your people, let the market do it much better Dec 10, 2020

If you are a teacher, a mentor, or a team leader, your job is not to give your people the final opinion about their results. This would be a terrible mistake. Instead, you should make sure they work for the market and the market evaluates their performance. Best team leaders know how to do that.

M149: Rewards without quality control will only hurt, but so what? Dec 03, 2020

If we reward programmers for each pull request they merge or for each ticket they submit and we don't control the quality of PRs and tickets, what will happen? Nothing good. They will easily abuse the system and there will be tons of low-quality tickets and PRs (or classes, or lines of code). However, if we do have strong quality control, everything will be just great. Thus, when someone says that paying per line of code will ruin the project I answer: "Only if your project is weak". The video is here: https://youtu.be/JIspFqjRt80

M148: How do you ask your manager to raise your salary? You don't! Dec 01, 2020

Most of us don't feel comfortable asking a manager for a raise. And it's only natural. I suggest you don't do it. Instead, you approach them with a question about the system your company has for promotion and salary increases. Moreover, you don't ask because you need this, but you ask because you care about others. Should work! :) The video is here: https://youtu.be/rvhI6m95Qxo

N1: Удаленка, фриланс, AI, open source, онлайн-обучение, карьера, коронавирус Nov 29, 2020

Video is here: https://youtu.be/5sTTHU0rJL8

M147: The quality of code review(er) can be measured by the frequency of rejections Nov 26, 2020

We do code reviews in order to control the quality of code programmers write. However, the question is: how can we control the quality of the code review process? The only objective metric that comes to my mind is the frequency of rejections. If a reviewer rejects too little, there is something wrong with the process or the reviewer. The video is here: https://youtu.be/fbBotuMol6Q

M146: Collaboration and teamwork are highly overrated in software teams Nov 23, 2020

They say that "collaboration" and "teamwork" are very important in software teams. I don't think so. I think that they are valued where the management and weak and information flow is chaotic. This is where you need collaboration. In perfect teams, people have individual tasks and personal appraisal of results. The video is here: https://youtu.be/7xeQLtDZLYQ

M145: Internal competition is what your team needs to achieve results Nov 19, 2020

The best and the only way to motivate programmers (and not only them) to achieve great results and solve complex problems is the give them fair rules of the game and make sure they compete against each other. The video is here: https://youtu.be/darliiClsjE

Shift-M/43: David West on management, education, motivation and politics Nov 16, 2020

David M. West is a retired professor in computer science, an author of a few books on object-oriented programming and software architecture, and a very interesting person. We recorded this interview on 8th of November. The video is here: https://youtu.be/UaxSDFesUR0

M144: Programmers are lazy, either in a good or a bad way, bu they are Nov 16, 2020

No matter how you put it, we programmers are lazy. Most of us are lazy because incompetent, stupid, and not motivated to do anything at all, while others are lazy because they don't like to do boring work and only enjoy creativity and innovation. In either case, managers must keep this in mind and find methods of dealing with our laziness. The video is here: https://youtu.be/FLZRgyXeZB4

M143: Daily reports are a perfect guilt-triggering instrument for a lazy team Nov 12, 2020

We all hate daily stand-ups for so many reasons. But daily reports is a better tool, which makes the same impact, but with higher precision. I would recommend you use them in your team if you have no other management instruments. The video is here: https://youtu.be/Yj1VFGK9vqc

M142: Your management is perfect only if you can pay everybody by results, not by time Nov 09, 2020

There is only one indicator of a perfect management system in a company or a team. You can pay everybody for the results they deliver, instead of the time they spend? If you can, your management is perfect. If you can't, you still have room for improvement. The video is here: https://youtu.be/2MUK_o9gU3E

M141: Lines of Code is a good metric if your management is perfect, otherwise it will hurt Nov 05, 2020

If you tell your programmers that you measure their performance by the number of lines of code they write, you may have to possible outcomes. First, this will turn your management into bigger chaos if it was chaos before. Second, it will boost performance if your management was strong and transparent before. The video is here: https://youtu.be/9Zen0B0SNwI

M140: Morning stand-ups are evil, use other management instruments instead Nov 02, 2020

Making the entire team standing up every morning and discussing plans, issues, or exchanging information is a perfect way to demonstrate your team that you are an incompetent manager. Instead, use other management instruments to make technical decisions, share information, to plan, and to control progress. The video is here: https://youtu.be/uov3LRJ12Nw

M139: It seems that better programmers write more lines of code Oct 29, 2020

My experience tells me that there is a direct connection between the subjectively experienced performance of a programmer and the number of lines of code he or she produces every day. Believe it or not, the famous Lines of Code (LoC) metric may be used to measure who is the best and the worst in a software team. The video is here: https://youtu.be/33Ym2ArSEjw

M138: Morning stand-ups are nothing else but guilt-triggers Oct 26, 2020

Why do we need morning standups in our Agile software teams? Some say that they help synchronize the team. Others believe that they are to encourage the team to share. There are many other stories, but I disagree with all of them. I think that we need these meetings in order to trigger guilt in our team members. They have to feel bad when they let everybody else down. Standing in the morning in front of everybody is the perfect moment to feel it. The blog post about this: https://www.yegor256.com/2019/09/03/injection-of-guilt.html Also, read this one: https://www.yegor256.com/2015/01/08/morning-standup-meetings.html The video is here: https://youtu.be/ues5Dks37zI

M137: Don't ask your programmers to estimate, tell them how much you have Oct 22, 2020

Asking your programmers to estimate how much time or money a software product would cost is a mistake. They don't know and can't now. They can spend all your money and still deliver an incomplete product. Because the product is never complete. Instead, tell them how much you have. They will do their best to deliver the most they can within the limitations. The video is here: https://youtu.be/lgScAwsYWCc

M136: Any software product has an unlimited number of bugs Oct 19, 2020

No matter how big or good is your software, it has an unlimited number of bugs, especially if we remember that maintainability bugs also are very important for the overall quality of a product. This is my talk at TestCon: https://www.youtube.com/watch?v=aYXuK2do6FA The blog post you may want to read: https://www.yegor256.com/2017/05/23/unlimited-number-of-bugs.html The video is here: https://youtu.be/ZdHCrsQsoMI

M135: Don't ask for approval, educate them so that they make the decision themselves Oct 15, 2020

If and when you want to convince your management to approve your idea, don't go there directly with a cold proposal asking for an answer. Instead, make a series of educational presentations, in order to help them understand the idea and agree with it. Then, they will come back to you and ask you to implement it. They may even forget who was the author. But the goal will be achieved. The video is here: https://youtu.be/9ym5u4en0Tc

M134: Don't blame the situation for the mess in the code, it's only your fault Oct 12, 2020

If the code is messy and dirty, blaming the situation is not correct. No matter what were the restrictions (both time, scope, and cost), your responsibility as a programmer is to deliver the code up to the quality expectations of the project. If you can't do that, you should inform the project beforehand. But don't blame the customer later. The video is here: https://youtu.be/WKX8CUPuYvo

M132: Your pet projects are the best contribution to your resume Oct 05, 2020

No matter how many big companies you worked for, your future employer will still pay more attention to your personal projects, especially open source. Well, provided the employer is savvy enough. Your personal code is much more valuable than the big name of some Facebook you have in your CV. They are just job places, but your code is something you managed to created. So, don't waste time and start your own pet projects now. The video is here: https://youtu.be/_ga2tP3wZbI

M131: Be aware of conflict-of-interest concerns when you open source while being employed Sep 28, 2020

When you work for a company and at the same time do open source development, you most certainly have a conflict of interest. The open-source is mostly for your own benefit, while the company expects you to give all your results to it. How will answer the questions when they ask you when your product is popular? The video is here: https://youtu.be/TW4uxuiHjCw

M130: The root cause of most software problems is the chaos in the code Sep 24, 2020

Solving software problems in most cases is not about finding the right algorithms or optimizing the effectiveness of existing ones. It's about cleaning up the mess left by other programmers and by ourselves. The video is here: https://youtu.be/kPmbRkSWYnY

M129: Niche narrow-skilled developers will earn more than others Sep 21, 2020

"Jacks of all trader" were appreciated and valued in the past when computers were young. Now the situation is different: you either are a niche specialist and you make good money, or you know everything and your income is below average. This situation will only get worse for those who don't want to dive deeper into a specific tech domain. The video is here: https://youtu.be/-WpBUrOxoDI

M128: Don't quit failing projects, quit those that fail you Sep 14, 2020

I often hear programmers complaining about projects they work in: customers are not happy, the market doesn't like us, nobody wants our product, etc. They not only complain, but they also quit. This is ridiculous. You don't need your product to be successful, you need your project to give you everything you need to be successful, personally. And this includes freedom and open source. The video is here: https://youtu.be/wQwZPOzN2gI

M127: The ability to explain a problem so that it's understood is the most important soft skill Sep 10, 2020

Most of us programmers are good at writing code, but very bad in reporting bugs so that other programmers understand what is wrong and help us resolve issues. This is a very important "soft" skill. You can train it in open source projects, where nobody will listen to you unless you explain yourself very clearly and professionally. Take some open source project and try to submit bugs to them. You will see the reaction. The video is here: https://youtu.be/Hrk_Jorc5z4

M126: Use open source projects to build yourself a support group Sep 07, 2020

One of the most complex tasks while working in a team of software engineers is how to convince them that you are right and your technical decisions are correct. No matter how smart you are, you will have problems with this. In order to win in those fights, you need a support group: people who agree with you and will vote for your decisions. Open source projects may give you such a support group. The video is here: https://youtu.be/DA9pK_yNLtc

Выступление перед студентами ВШЭ Sep 04, 2020

1-го сентября 2020 года мне повезло выступить перед 200+ студентами Факультета Компьютерных Наук (ФКН) Высшей Школы Экономики (ВШЭ) в Москве, по случаю начала нового учебного года. Видео здесь: https://youtu.be/Ly9u_ZAZFCk

M125: When you contribute to your project altruistically, you are killing it Sep 03, 2020

You may think that being altruist and give your project and your team more than taking back is the right thing to do. It's not true. To the contrary, if you are being selfish and always make sure that the team is giving you back the same amount of value you are giving to it—you are doing the right thing and improving the management system in your company. The video is here: https://youtu.be/A59xGYb-aGY

M124: Put your talent away and learn new skills when working in an enterprise Aug 31, 2020

Being a talented programmer, in my opinion, means having an innate intolerance to mess. It means a permanent desire to structure and organize the code you are working on. This may be a great advantage if you are in a small project or a startup. However, if you join an enterprise, this will be your disadvantage, which may only hurt you and the people around you. Instead, you will have to learn new skills and acquire new talent for yourself: the ability to put up with mess around you. The blog post about talent is here: https://www.yegor256.com/2019/12/31/talented-programmers.html The video is here: https://youtu.be/8Ls88a_Y5iY

M123: One README should be enough for any open source project Aug 27, 2020

Some of us believe that a good open source project (or some of them) must have extensive and big documentation, in multiple Wiki pages or Markdown files. I don't believe in this. I believe that any project must be able to fit its documentation into a single README. If you can't fit it all into it, you are doing something wrong. The video is here: https://youtu.be/Qxvk9z0tEP8

M122: Don't help them, instead use their free contribution to improve the product Aug 24, 2020

When someone comes to your product and asks questions about how it works, why it doesn't work, or simply complains about its problems: don't help them right away. Instead, fix the product while they are waiting "on the line," show them a new version of it, and ask to provide feedback again. This is how you use them as free testers and make your product become better. The video is here: https://youtu.be/tI6rGQIevxU

M121: Don't be frustrated by the enterprise chaos around you, conquer it! Aug 20, 2020

No matter what kind of enterprise you are working in, you won't like what's happening around you: chaos, lack of control, lack of logic, and so on. Don't expect them to improve. Instead, find a place for yourself and make changes there. Be the leader of the changes and earn yourself karma points. The video is here: https://youtu.be/SuAM9J2cTDo

M120: Don't wait for your manager to tell you what to do, do what you think is right (open source) Aug 17, 2020

Most managers are incompetent, lazy, and stupid. If you expect them to tell you what to do, you will have a lot of frustration. Because they don't know and they don't want to know. The solution is simple: start planning everything yourself and show them your plans. In most cases, they will be happy to leave you alone and let you do what you want. If it will be open-source, you will have a double win. The video is here: https://youtu.be/CmUzNPqCF4s

M118: Deploy your ready-to-use open source artifacts into immutable repositories Aug 10, 2020

Having a good source code repo in GitHub is not enough if you want your users to trust you and use your product. They expect you to deploy it somewhere where you can't delete it. Maven Central is a good example of such storage. If your binary artifacts are not there, your users will have serious concerns about whether to use your libraries or not. The video is here: https://youtu.be/iFx2-U8fsrE

M117: Breaking responsibility down is the responsibility of a manager/architect Aug 06, 2020

When they say that we are working for a big goal and that's why we don't use fine-grained metrics, be aware: you are dealing with an incompetent manager or an architect. Their job is to decompose larger tasks into smaller pieces, instead of feeding us stories about "Big Goals". The video is here: https://youtu.be/kPTKT3jOG7c

M116: Which license to use for an open source product? Aug 03, 2020

Do you still wonder what is the best license to use for your new open-source product? GPL, BSD, Apache? Stop thinking about this. It doesn't matter. Just use the most simple one: MIT. The video is here: https://youtu.be/vBOg8_nGDls

M115: Going along with large open source projects is a perfect strategy for newbies Jul 30, 2020

There are three strategies to get into open source when you are just starting. They didn't work for me. There is the fourth one, which I would suggest you try. I didn't try it myself, but I'm sure it's much more effective than the first three. The video is here: https://youtu.be/IeoYXstRvzw

M114: The performance of programmers can be measured, with the right metrics Jul 27, 2020

Most of us think that the programmers' performance can't be measured. We can't, they say, put a number on a person. I believe, we can and must. Just like any other job, software development has to be measured. The question is which metrics to use in order to do this objectively and effectively. In one of my recent blog posts, I suggested a number of metrics, which can be used individually or all together. Try to apply them for yourself and see what happens. This is the blog post about this: https://www.yegor256.com/2020/06/23/individual-performance-metrics.html The video is here: https://youtu.be/jjeW1hTtRh0

M112: Put as much as possible on GitHub, no matter what it is Jul 20, 2020

GitHub is the place you should keep your code at, no matter how perfect or complete it is. Small scripts, short documentation pages, some notes, simple documents: they all may be there, they all may be interesting for your followers. Don't wait until you have a complete library to open source, start smaller. The video is here: https://youtu.be/xFXW5j2x7XI

M111: Use open source projects to beat the boresome of the office work Jul 16, 2020

We all work with some legacy and boring code. In most cases we can't decide what to work with, since this is what the business is paying for. Making small open source projects may become a great solution to deal with the boresome of the legacy: make them on your own and be the architect there, and have fun! The video is here: https://youtu.be/qJxDV1TrEGE

M110: Professional developers enjoy being punished by static analyzers Jul 13, 2020

A static analyzer is not a "nice" tool generating fancy statistics, which you can show to your boss and get back to work. A static analyzer is supposed to be a punisher for you for the mistakes you make. The video is here: https://youtu.be/7rtQ4yQVAK0

M109: Open your sources piece by piece, not all at once Jul 09, 2020

If you have a good product to open source, don't do it in one go. Instead, take pieces out of it and open them slowly. This is how you buy your freedom from your organization and learn how to do open source, avoiding big mistakes. The video is here: https://youtu.be/VuJNBXPnRy8

M108: Your job is to prepare your open source project for the future community Jul 06, 2020

Your main goal as a creator of an open-source project is to prepare it for the users and contributors who will come after you. You will not stay with your project forever. You may not even stay with is for a few years. You don't want the project to die, do you? Just make it look attractive for future users and it will live forever. The video is here: https://youtu.be/kV5j4Uysivo

M107: Make your GitHub project look attractive and contributors will come Jul 02, 2020

The product you develop is very important. But the way you format and present your repository on GitHub is equally (or even more) important. This is how you attract contributors: by making your project look well-organized on GitHub. The video is here: https://youtu.be/elOkw1OYd_U

M106: Very soon all important software projects will open their sources Jun 29, 2020

It is inevitable: open source is how we will be developing software in the future. Nobody will pay for software, but only for services around it. You have to join this new market as soon as possible. The video is here: https://youtu.be/JBdtSAJjFaU

M105: Open source developers inevitably have better soft and tech skills Jun 23, 2020

Open source projects are the best places for training programmers and helping them grow their soft and tech skills. If you want to convince your management to allow you to work in an open-source, use this argument: your skills will only grow if your code is open. The video is here: https://youtu.be/D12gi1x6Cdw

Shift-M/42: self-development with Venkat Subramaniam Dec 10, 2019

Venkat Subramaniam is a famous software expert, a regular speaker at software conferences, a book writer, and a software architect/programmer. He shares his views about self-development.

M104: Refactoring without a ticket means stealing project resources Nov 11, 2019

When you see the code that needs improvements you, as a good programmer, fix it because you don't want the bad quality to stay in your project. However, this good intent only harms the project. When you work in a team, you are not allowed to do what is not approved by the project. Every time you see an opportunity for refactoring, make a ticket and let the project decide when and who will do it. The video is here: https://youtu.be/PkmVF64mZNo

M102: Zerocracy may look like utopia for you now, but eventually you will be there Jul 12, 2019

Very often, those who read about Zerocracy and watch my videos, ask me whether I believe that the management model we are promoting, is applicable to real projects. They sometimes call it utopian and unrealistic. I suggest you look at it as a picture of an ideal software world, which may become your world if you try to apply it to your work, piece by piece. Try harder! :) The video is here: https://youtu.be/cIq-pSFswUI

M100: Tech audits help you identify the gaps between your code base and industry standads Jul 08, 2019

Independent technical reviews, which you may get in Zerocracy, won't help you find bugs in your software, this is what testers are for. They will help you understand how far your code base from the industry standards applicable to your tech stack. Most teams tend to do things in their own special way, which is a huge threat to maintainability. Don't wait until it's too late, start now. The video is here: https://youtu.be/jzMZaC54nbc

M98: If you think that your team is doing fine, you are a bad manager Jun 28, 2019

Most CTOs and project managers I'm talking to believe that their teams "are doing fine" and don't need any audits. This means only one thing: they are incompetent managers. Professional managers know that "doing fine" now doesn't mean that the team doesn't have hidden and currently invisible defects, which will cost a lot, in the future. The job of a professional manager is to regularly identify problems, technical debt, risks, and threats. Zerocracy provides exactly this service, remotely. The video is here: https://youtu.be/GlBf5-g4nGk

M97: Let your followers be your best censors helping you think more logical Jun 26, 2019

There are many reasons why people are being active in social networks, like Twitter, Instagram, Facebook, or Telegram channels. Some of them even have their own blogs or YouTube channels, like me. Some of them are having fun, but my primary objective of doing this and publishing my ideas online is that this activity helps me structure my thinking and make it more logical. I have thousands of censors constantly looking at what I'm saying and writing. You should do the same if you want to grow: start publishing your thoughts and see how many people follow you and read. If the number will grow, you have ideas. If not, well... The video is here: https://youtu.be/CJ6oYeLGdmo

M96: Freelancers are a pain, but they are your only hope if you want the quality to go up Jun 24, 2019

Most companies suffer from the legacy code they inherit from software teams that disband or programmers just quick. Companies have to do something with the software and they can't throw it away. Most of them hire full-timers to support the code, maintain, and hope that they will improve it. This won't happen. Full-timers are not interested in doing that and they won't. If you want your code base to become better you need people who are interested in going into conflict with the code base and the status quo. Freelancers are your only option. The full video is here: https://youtu.be/0gnDmr_H2Ks

M95: Only lazy and immature programmers are afraid of penalties and punishment Jun 20, 2019

Very often I hear managers saying that if you even try to punish programmers for their mistakes they will quit and you will have no team. This may only happen to junior or lazy programmers. Professional software engineers are interested in being challenged and rewards+punishment is what constitutes a challenge. And the challenge is what motivates us, technical people, to work. The video is here: https://youtu.be/PlvoXBgwooY

M94: It is impossible to make a full-timer deliver results, unless they want it Jun 20, 2019

Our bosses what us to be productive, effective, and deliver results. However, the question is whether they can make us do it or not. When they hire us as full-timers and pay us for a full month of our time in the office, they can't do anything to force us to work. They can only rely on our desire to be "good soldiers." For some people, this may work, but true professionals are always smarter than their bosses and know how to look busy while doing something else. This will never be the case with people who are paid by the result. Want to try to hire a team of freelancers in Zerocracy? Fill this form out: https://www.zerocracy.com/rfp The full video is here: https://youtu.be/salVaSqJwb8

M93: To become a good programmer you have to find a project that rejects your mistakes Jun 17, 2019

Junior programmers usually don't know where to start in order to practice, learn how to code, and work with professionals. They can't find the right project to contribute to. I'm suggesting you find a project, which is ready to reject your mistakes, no matter what. We have such projects, which are owned and managed by our best programmers, in Zerocracy. Join our Telegram chat and ask, there will be plenty of offers. The chat is here: https://t.me/zerocracy The video is here: https://youtu.be/dCn53X1I2R0

M92: We in Zerocracy use Boost Factor to help architect motivate programmers Jun 12, 2019

Sometimes we have tasks in our projects, which nobody wants to complete. They are difficult or impossible to decompose, or simply too complex. What do we do in order to motivate our programmers to work with those tasks? We use Boost Factor, which is a multiplier of a micro budget. In other words, we use money in order to motivate programmers. We believe that professional programmers are motivated by money and know how to demand more when more work is required. The video is here: https://youtu.be/nvXu_Yl5Y_w

M91: Full-timers want to look smart, freelancers want to deliver results Jun 11, 2019

Most full-timers are afraid of showing their bosses that they find help at StackOverflow, because their managers expect them to be smart and know everything about the technologies they work with. Who would want to pay a full monthly salary to someone who constantly seeks help at StackOverflow, right? This is not the case with freelancers, on the other hand. Those who are paid by result are not required to be smart. They need to be productive and effective contributors. Who do you want to be? The video is here: https://youtu.be/_4pk5GNUySg

M89: Deliver your trust continuously, not discrete May 31, 2019

Most companies and managers believe that they have to check people before they let them get into the team, through a number of very complex interviews. After that, they trust their programmers and hope they will be motivated and committed enough to deliver the best results. Agile also suggests the same. I strongly disagree. We must not deliver our trust only once when we hire someone. We must continuously inform programmers about their performance and trust them as much as they deliver, every day. The video is here: https://youtu.be/KPbKqTXfZwA

M90: RUP is a framework, Agile is a philosophy; just like Zerocracy and XDSD May 31, 2019

I often hear a question: what is better, Agile or RUP? This question doesn't make a lot of sense since Rational Unified Process (RUP) is a framework with a large set of artifacts, processes, roles, and procedures; while Agile is a short list of philosophical points. I would actually strongly recommend you study RUP to understand software development (or even get certified). XDSD is our philosophy and Zerocracy is a framework.

M88: If you are working on a prototype for longer than two weeks, you are doing it wrong May 28, 2019

Technical debt is a huge problem, when it is, well ... huge. What usually happens is this: we start a project, we work on its "prototype," we wait until it is fully ready, and then we start thinking about unit tests, continuous integration, and build automation. But it is too late because the product already is too big. The problem is that we hold the product in the prototype mode for too long. I believe that two weeks is the maximum a prototype should take. After that, it's a normal product, not a proof-of-concept anymore. The video is here: https://youtu.be/4MP3xXGrpCY

M87: If you are afraid of being replaced, you are not a good programmer May 27, 2019

Most programmers feel uncomfortable realizing that their employer may replace them one day. To make this event less likely to happen they do many things in order to make themselves unreplaceable. One of those things is unmaintainable source code, which nobody else will be able to understand if its author is fired. I think that this mindset is not only toxic but also very typical for unprofessional engineers. If you are professional enough, the market always has something to offer you and you always know what is the next step for you, after this team gets rid of you or you decide to quit. If you feel scared, just look into the future and start checking opportunities. The video is here: https://youtu.be/yRm97umW4vE

M86: The README file must be the only provider of product specification May 22, 2019

I think that any repository, be it open source or proprietary, must have a single README file, which must include everything a new contributor needs to know about it: the product statement, the vision, the list of features and non-functional requirements, the list of technical decisions, which are important to know. Unfortunately, this file is very often forgotten, especially in non-OSS products. If you don't have it now, it's never too late to create it, and make it right. The video is here: https://youtu.be/1zCH0xBiCP4

M85: The source code is just a part of a software project, not the biggest one May 20, 2019

We started reviewing software projects of other companies, just a few weeks ago and our first finding is that programmers don't pay attention to anything aside from the code they write. They don't have build automation, unit testing, static analysis, continuous integration, test coverage control, database versioning, and many other things which are supposed to keep the code together. It seems that this is happening because of the lack of knowledge and experience. The video is here: https://youtu.be/keGVpncTn4Q

M84: Don't chase your team members, make them chase you May 16, 2019

The job of a good project manager is to organize the team the way that every team member wants to contribute and is ready to go through all possible obstacles and barriers, in order to make sure their results are accepted by the project. If the project manager has to chase programmers, ask them, beg them, and pull results from them, it is a bad project manager and the project is mis-configured. The video is here: https://youtu.be/4j4Kddo5Xgw

M83: Strong opinions loosely held is not a problem, the absence of an architect is May 13, 2019

A software team where everybody expresses their opinions loudly and strongly, always being ready to admit that "I was wrong," is not able to produce anything serious. This is what I read in one blog post recently. And I do agree with this. However, I disagree with the solution suggested in the blog post. The author suggests programmers be more humble and skeptical, which I believe will only lead to more compromises. We know that compromises are bad for quality. My solution is to have a formally assigned architect, who makes all final technical decisions.

M82: Is it possible to open the entire source code base and still make business? Definitely. May 10, 2019

When I start talking about 100% open source business model, most people wonder how is it possible to give away the entire source code base and still remain profitable, money wise. I think that any modern digital business has three components of success: the source code, the database, and the community of users, programmers, clients, and so on. If you make your source code fully open, you will only help your other two components (data and community) to grow. In Zerocracy and all our satellite projects, we rely on this business model. We open the code and invest in the community. The video is here: https://youtu.be/4-7fth8Iku8

M81: How to make your GitHub repo popular? Eight things to pay attention to. May 08, 2019

Do you want to be known in the open source world? If you don't, don't watch this video. If you do, there are eight things you should pay attention to when making a new GitHub repo: 1) make it small, 2) don't depend on other libraries, 3) make your README sexy, 4) write up a complete documentation, 5) ask everybody around to give you GitHub stars, 6) release it, 7) configure continuous integration, 8) communicate with your users via issues and pull requests. You can see how I do it in my libraries, in my GitHub account: https://github.com/yegor256 The video is here: https://youtu.be/vhOg-7uPbvA

M80: Every two weeks you should hire a new auditor to review your software project May 06, 2019

Very often software project sponsors complain about the low quality of their programmers. They also say that changing the team doesn't really help. They believe that it's possible to hire the "right" people and everything will be great. This is a myth. Instead of expecting your people to be great, you should control their results, by auditing it with an external expert. I'm suggesting you find such an expert in our Telegram chat: https://t.me/zerocracy. There are almost 400 people, most of whom are true experts. Pay them by the hour and you will be impressed by the changes you will see in your project. The chat is here: https://t.me/zerocracy The blog post is here: https://www.yegor256.com/2017/11/21/trust-pay-lose.html The blog post about technical reviews is here: https://www.yegor256.com/2014/12/18/independent-technical-reviews.html Here a blog post about questions such an auditor must answer: https://www.yegor256.com/2019/04/02/software-project-review-checklist.html The video is here: https://youtu.be/TxYi7J0vKC8

M79: Make as many open source libraries as possible, eventually one of them will become a success May 03, 2019

I created a simple Ruby library just about two weeks ago: https://github.com/yegor256/iri. I already have more than 60 GitHub stars there. How did I do that? I just published it where I usually publish my open source libraries. There is no secret. I just create them, publish and then some of them (!) become popular. You should do the same. Every time you see an opportunity to make a small piece of code open -- do it. And make them small. The smaller your open source products the easier they are to use and the higher the chance that they will be popular. The video is here: https://youtu.be/jeflGHMpfDc

M78: Programmers are not your property, don't invest in them! May 02, 2019

Most companies and project managers feel proud of spending a lot of money for finding programmers, training them, getting them on board. They tell me very often that programmers are their valuable assets and they don't want to lose them since they invested so much into them. That's a terrible approach, which is only disrespectful to us programmers. We are not your property or your assets. We want to be equal partners with your team. Change your attitude before it's too late. The video is here: https://youtu.be/UFfJCRhLCZ0

M77: Lines-of-Code don't show anything meaningful, but Hits-of-Code are pretty accurate May 01, 2019

It is a well-known fact that Lines of Code (LoC) is a very inaccurate metric for a software developer. It doesn't demonstrate anything and can't be used to measure the progress of a programmer or a number of efforts the programmer puts into the source code. However, there is another metric called Hits-of-Code (or Code Churn), which is calculated differently and perfectly indicates how much time or efforts the repository required to be created. There is a command line tool of mine, which can help you calculate HoC in your repo. There is also a hosted web service, to do the same. The video is here: https://youtu.be/hTs_R0dFoFM

M76: Learn Rational Unified Process to understand SDLC better Apr 29, 2019

Most programmers think that writing code is enough to be useful for a software project. It's not true, especially now, when projects are becoming smaller and teams are more distributed. A modern programmer must understand all the processes and phases of a software development lifecycle. The best way to learn them all, if you ask me, is to study the Rational Unified Process (RUP). The video is here: https://youtu.be/Af0E8Bn8qcw

M75: Your presence in social networks is important for your career as a software architect Apr 22, 2019

Most people ask me why exactly I think it's important for a software developer or an architect to be a blogger and stay active on Twitter, for example. I believe, and most recent practical cases prove that a well-connected and "visible" software architect would bring a lot more value to a project than someone who just knows how to write code. The video is here: https://youtu.be/l-bM2XyhlkQ

M74: If your project doesn't have a formal Risk List, you are doing management wrong Apr 18, 2019

Risk Driven Development is a powerful concept, which may help you prevent many bad things in your project. Unfortunately, many teams don't know how to do it right. I'm going to publish an online tool for that soon, which will be used by Zerocracy and for anyone since it will be free and open source. The book by Rita Mulcahy: http://amzn.to/266pAYB (you must read it!) Zerocracy is here: https://www.zerocracy.com The video is here: https://youtu.be/WlI6IZ6M7vY

M73: It is your job, as an architect, to convert client's requirements into tickets Apr 16, 2019

Microtasking, in order to work properly, requires a certain amount of discipline. First of all, all tasks and communications about them have to happen in tickets. However, our customers are far from being disciplined enough to use tickets for every requirement they have. Instead, they make phone calls, chat with us online, and send emails. I believe that is the responsibility of an architect to make sure each request that is coming from a client turns into a ticket. If you, as an architect, don't do that, you are doing a very bad favor to the project.

M72: Zold, like any other young cryptocurrency, needs master nodes to survive Apr 15, 2019

Very often our investors and users ask us why Zold has master nodes, even though it claims to be decentralized and anonymous. I answer that I can't imagine a serious cryptocurrency without a certain amount artificially created master nodes, which help it survive when it is still young. Without them, it will be possible to destroy us easily, just by a majority of hardware, which is not that expensive, while we are young and small. The video is here: https://youtu.be/kNqKLCWFzbY

M71: Motivating programmers by equity or profit sharing is a bad idea, it doesn't work Apr 12, 2019

Many startup founders think that by sharing equity with programmers or giving them annual bonuses according to the overall result of the company, they can motivate them to work better. This is a wrong idea because programmers can't control those things. They can control the quality of their code, the speed of its delivery, their unit tests, their build pipeline, and other technical things. By rewarding them for things they don't control, the business only demonstrates that it doesn't understand what it is doing. The video is here: https://youtu.be/MyBbtwKgc9k

M69: Write tutorials instead of training and teaching Apr 10, 2019

Every time someone comes to me for a piece of information, I ask myself: "Why? Isn't this information available in our documentation?" And if the answer is "No," I try to improve the documentation, to make that piece of information visible and accessible, to avoid future requests of the same kind. You should do the same. Don't train anybody, don't teach anybody. Instead, write tutorials. Help yourself and your project. The video is here: https://youtu.be/QzU2Fbr3xuI

M70: A software team without conflicts can't produce anything of a good quality Apr 09, 2019

Very often my readers complain about me saying that programmers must be in conflict with testers, or code reviewers in conflict with programmers, and so on. They claim that a good software team must have everybody going along and share the same set of objectives. They say that we should work "together," not against each other. I strongly disagree with that. I believe that good management means organizing conflicts and giving people explicit rules for resolving them. That's how quality can be achieved. The video is here: https://youtu.be/DUWiy7fvVzk

M68: Is it necessary to be a full-timer first, in order to become a freelancer? Yes, why not! Apr 09, 2019

Being a freelancer and charging $100 per hour, switching projects every few months and living in Bali, sounds like a dream for many programmers. But the question is, how to get there? Where can one get experience and training? Does it seem that the only way to learn to programme is to work somewhere as a full-timer? Yes, why not. Most of you will remain full-timers, but some of you will become freelancers. Those two categories will co-exist on the market. The video is here: https://youtu.be/sJRM4VWkzSM

M67: The future of software development has no offices and no companies, only projects Apr 08, 2019

Building teams that were supposed to stay together for many years, was a good strategy, many years ago. Not anymore. The reality of the modern software development market demands us to work with remote programmers, who in most cases will be individual contractors or freelancers. They will not be emotionally attached to the team or to the company. They will be looking for the most interesting projects on the market and will quit the moment they will realize that your project is not the one they fit well with. That's why, if you want your business to be ahead of the market, you should start learning how to work with freelancers and how to manage projects. Instead of building teams. The video is here: https://youtu.be/5GfGXhzQb4Y

M66: If you will manage programmers the way Google does it, you will lose Apr 05, 2019

The current situation on the software development market it terrible: programmers are spoiled by large salaries and very high demand. They know that their managers can't really do anything with them, can't make them work faster or better, can't fire them, and can't enforce any discipline. Large companies, like Google or Facebook, have the luxury of buying 10 times more programmers than they really need, that's how they solve their productivity problems. However, if you don't have that amount of money, you must not manage your programmers the way Google does it. You need a better management formula. Which one? Microtasking from Zerocracy is one of the options. Use it or invent your own one, but don't copy Google. The video is here: https://youtu.be/XQQoaBZEs38

M65: If you need to learn the code around your microtask, don't do it! Create a new ticket. Apr 04, 2019

When a microtask arrives to you, very often you may need some additional information, which is not specified in the task description. Your first intent would be to go and find that information, even if it's not available. This would be a mistake. You should not spend your time, which is a valuable project resource, on something the management hasn't approved yet. You should create a new ticket/task and ask for additional information. It will be provided and you will be able to continue your main task. The video is here: https://youtu.be/XYXNOOH8q3M

M64: You want your programmers to be your enemies? Pay them monthly. Apr 02, 2019

Most managers and business owners believe that programmers are interested in their ideas, in their business, in their vision. They expect programmers to work because they share a global vision. In reality, it doesn't work that way. Programmers work for their own profit and care about their own personal results. If the business fails to align its objects with personal objectives of its programmers, it will get enemies, not friends. The video is here: https://youtu.be/TvvSQq_c4X8

M63: The growth of Zold rate is direct marketing expenses of Zerocracy Mar 29, 2019

The business model of Zerocracy by definition requires a pretty big amount of venture capital in order to connect many programmers with many customers and make them attractive to each other. In order to attract VC money, we have to demonstrate them the traction on the market. Zold is going to help us achieve exactly that, by collecting micro-investments from you and showing bigger money people that the market is interested in us. Help us make Zerocracy bigger, invest in Zold! The video is here: https://youtu.be/sbONYCd5iUI

M62: Five steps to migrate from traditional management to microtasking Mar 28, 2019

Microtasking is a great method of managing programmers, but it's very difficult or almost impossible to switch to this new model of work from traditional full-time management. There is a list of five simple steps I would recommend you making with your team if you want to get yourself ready for microtasking in a few months or a few years. First, make sure the use GitHub. Second, make them report their weekly results in a list of completed tasks. Third, make sure their code gets into the repository via pull requests and only after code reviews. Fourth, invite external reviewers and let them submit their ideas only through tickets. Fifth, let them work remotely, from home. The video is here: https://youtu.be/0mOn9MvuMzU

M61: What do you do when a client says that everything is wrong and has to be done from scratch? Mar 27, 2019

What do you do as a customer, when you realize the your architect is totally wrong and the architecture is flawed and you have to start from scratch? Most likely, you got aware of that from one of your friends of the experts you invited to the project. What's next? Replace the architect? Start from scratch? Or continue working with the existing team? My recommendation: never start from scratch. The video is here: https://youtu.be/RWV6f90eHek

M60: Ask a software team for a quote only to check whether they refuse to provide it Mar 26, 2019

How much would it cost to create a Twitter clone? You won't believe how often I hear this or similar questions. There is no such thing as a realistic estimate of a software price if we are talking about a more or less big product. It starts with a few thousand dollars and ends with a few billion if the product becomes successful on the market. Those who tell you that to develop your app would cost, say, $100,000 are just trying to fool you or they don't understand what they are talking about. The video is here: https://youtu.be/j5uXrY2gttA

M59: How to not get frustrated when dealing with freelancers and microtasking? Mar 25, 2019

A team of freelancers working in a microtasking mode is not focused on your business objectives, by definition. They are doing what they are willing to do, randomly covering the entire scope of the product's functionality. This is why so many customers get frustrated when they experience this for the first time. In order to avoid this frustration, you should do something, to align technical goals with your business objectives and focus the team on tickets, which are important. The video is here: https://youtu.be/w3HwEtFU2wo

M58: Don't expect UI/UX people to work in microtasking mode, they are too creative for that Mar 22, 2019

Very often customers of Zerocracy ask me whether we can find them some good UI/UX designers, who will make sure their application looks great and can work together with programmers. We can't do that because UI people are too artistic and their work has no explicit borders. It's better to find them somewhere else, make sure they are managed and disciplined somehow differently and let programmers integrate their code with their creativity, somehow. How exactly you do that, depends on many technical factors. The video is here: https://youtu.be/dzepTbcQkgU

M57: Tech startups fail mostly because of software development incompetence Mar 21, 2019

Why do startups fail? Conflicts between investors and founders, marketing issues, lack of customer development, not enough money, etc. I believe that all those issues are secondary. The primary cause of problems is the inability to manage programmers right and make sure they deliver what they promise to deliver. Everything else happens as a consequence of the technical incompetence of the software team. The video is here: https://youtu.be/AwN4emJT0n4

M56: Don't expect your architect to be an expert in your tech stack, that's what developers are for Mar 20, 2019

Very often our customers in Zerocracy expect software architects to be very knowledgeable in the tech stack they are going to use in their projects. Even though it doesn't hurt, but this is not what software architects are for. An architect is not going to be the knowledge provider in the project, instead, he or she has to know where to find the right experts, how to engage them, how to motivate them, and how to deal with the information flow they provide and programmers work with. Soft skill is what differ an architect from a regular programmer. The full video is here: https://youtu.be/_XPonwxsXGI

M55: The programming language you choose must match your project business objectives Mar 19, 2019

Many customers, who pay for software development, think that some programming languages are fast, while others are slow and when they need a great/fast/awesome application, they need to use the language some other team has been using before and managed to create some other great application. This is the wrong approach. Instead, when you choose the language pay attention to how it matches your business objectives. Whether your project is going to be alive for a month or a few years, how big will be your team, how much money do you have to hire experts, how disciplined is your management style, etc. Almost any language can create a fast application, but not any language is suitable for disciplined management. The full video is here: https://youtu.be/Pz256gcyuHs

M54: Make sure you control your programmers and do it explicitly and openly Mar 18, 2019

I've heard it very often that people don't like the word "control" being applied to a group of programmers. They find it abusive, offensive, and de-motivating. I absolutely disagree with this. Control is abusive only if it's implicit, hidden, and not obvious. However, if the rules of work are well defined, accepted by everybody and applied strictly, just like those laws we all know in civil life, control is not abusive at all. The video is here: https://youtu.be/ezE0hRH9BnQ

M53: What do I think about Agile? It's a recipe for disaster, if you are a project sponsor. Mar 15, 2019

Agile, as a software development methodology, was invented by programmers and for programmers, to make things easier for them and to get a perfect excuse when things go south. In Agile the management is not in charge anymore, can't control things, can't really predict anything, and can't blame programmers for mistakes. If you are a programmer, Agile is your perfect shield against most of the problems in the office. If you are a project sponsor, it's your ticket to failure. The full video is here: https://youtu.be/OOAMNOso46g

M52: Three-branches release model: Master, Release Candidate, Live Mar 14, 2019

In order to isolate your production from the "dirty" master branch, I'm suggesting to use a simple release/delivery model. First, you let everybody commit to the "master" branch, of course, after they pass all unit/integration tests and the entire merge pipeline. Then, you create a candidate branch, which you deploy to the staging environment and let your testers break it as much as they can. Then, when it becomes obvious that testers can't find anything critical there, you the "candidate" branch into the "live" branch and deploy to production, via the deployment pipeline. You may have a number of release candidates, staying in testing simultaneously. This model proved its validity in many projects I've been doing over the last years. If you tried it and there were problems, please let me know in the comments.

M51: Don't hide error stacktraces, make end-users part of your quality control instead! Mar 12, 2019

Most big websites I work with don't show their error details when something goes wrong. Here is an example: my account with Amazon is in trouble and I see nothing except the "We are sorry" message from them. Instead, I believe, would be much better to show me much more technical information and make me part of the development process. That's what we do in our projects: making our technical defects as much visible for end-users as possible, in order to make them fixed faster. The video is here: https://youtu.be/t1locjBAXYY

M50: Testing is the process of confirming that the software has defects (JPoint talk rehearsing) Mar 11, 2019

The biggest problem of modern software testing is that neither testers, nor programmers, or their managers understand the role of a software tester. A tester is not someone who confirms that the software works as intended. Instead, a tester is the one who confirms that the software has bugs and who knows how to discover them and document. I will be speaking in JPoint in a month, exactly with this topic. Here is a short rehearsal of my presentation for them. I'm interested in your comments, criticism and suggestions. The video is here: https://www.youtube.com/watch?v=D5RtdHicCXE

M49: Zold is an experimental non-Blockchain cryptocurrency, made by Zerocracy Mar 07, 2019

There are many cryptocurrencies on the market, while 99.9% of them are based on the Blockchain architecture, with some modifications. About a year ago we decided to try to create our own solution, which would be a true alternative to Blockchain. It seems that we managed to achieve what we planned and now it's the right time for you to join us and convert your bitcoins to zolds. This is how you will help Zerocracy and will make yourself a profit. The video is here: https://www.youtube.com/watch?v=5A9uBwMow0M

M48: If you depend on your programmers, you are a bad architect! Mar 06, 2019

If I would need to create software for a nuclear power station, who I would work with: freelancers or full-time employees? Of course, the first intent is to get a team of full-timers who we can "trust" and who will care about the business, will be committed to it and will feel personal responsibility. However, this is a very wrong idea. The business will eventually suffer because of lost control. In order to stay in charge of the quality the business should work with people who care mostly about themselves. Freelancers are exactly that type of people. If you manage to deal with them and keep them under control, your business will be strong and successful. The full video is here: https://www.youtube.com/watch?v=12SEpsOH7CE

M47: What is the difference between Zerocracy and Upwork? We are not competitors! Mar 05, 2019

Very often this question is asked: how Zerocracy can be compared with Upwork and similar platforms for freelancers. Long story short, we are not competitors and can't be compared directly. Upwork provides unmanaged teams of freelancers, while Zerocracy turn them into managed teams. You may and should find freelancers in Upwork and then come to Zerocracy and let your team work under the management of our AI and according to our policy of work. Hope this helps. The full video is here: https://www.youtube.com/watch?v=A6AC2Tgyhzs

M46: Freelancers and full-times are like oil and water, don't mix them, they are not friends Mar 04, 2019

When your objective is to put programmers together in one office and make them look like hard working slaves, spending the money of your investors, you definitely need full-timers, with good salaries and benefits. However, if you need to achieve results, and you know how to manage programmers, you need freelancers, who work for results, for money, and for themselves. You don't mix those two categories, they are absolutely different. And you don't apply the same selection criteria to those two groups. The video is here: https://www.youtube.com/watch?v=hDsy-D5zaVs

M45: Freelancers and full-timers have very different resumes, don't expect them to look similar Mar 01, 2019

Changing jobs frequently is usually considered to be a sin for a professional programmer. Recruiters don't like that and to leave just a few places in the resume, to look more "loyal." However, this is not true for freelancers, who by definition change projects frequently. That's why their resumes have to look very different and recruiters and project managers have to be ready to read them differently. The full video is here: https://www.youtube.com/watch?v=31xOLs-DqTo

M44: What do you think you are a senior developer? Who says so? Think again. Feb 28, 2019

Being a senior developer doesn't mean getting a large salary or being appreciated in the office. It means belonging to an elite group of developers who know how to do certain things and can do them. If you want to be senior, think again about open source contribution, about StackOverflow participation, about conferences and certifications. Without that, you are just yet another programmer, one of a million. The full video is here: https://youtu.be/Y_IUzt-Oyww

M43: Technical interviews are pointless, pay attention to these five things instead! Feb 27, 2019

Most software teams interview programmers before getting them on board. Later they get surprised how was it possible to hire someone who doesn't understand programming. Those so-called "fake interviews" would not exist if we would let the market vouch for programmers, instead of us relying on the information we manage to collect at those Skype calls. We, in Zerocracy, pay attention to five things that are important: 1) GitHub reputation, 2) Stackoverflow history, 3) certifications, 3) conferences, 4) blogging experience. Once a programmer has all of those, we know that he/she is senior enough for us. The full video is here: https://www.youtube.com/watch?v=gVs9NKSlOVc

M42: Make sure your software is deployable from the first day! Feb 25, 2019

The first thing you should worry about when you start a software project is how your product can be delivered to end-users in an automated way. Right after you managed to create a skeleton and make it "work on your laptop," start configuring the deployment pipeline. Only after it's done, demonstrate your product to your testers, partners, investors, customers, etc. Don't tell them that your product is in GitHub and if they want they can check it out themselves. This is very unprofessional. Make sure they can touch the product where its end-users will see it when it's fully ready for the market launch. The full video is here: https://www.youtube.com/watch?v=p-Hv-TC0JHc

M41: Six steps to a better speaking English for a software developer Feb 22, 2019

I'm being asked about English speaking skills very often, that's why this video. You want to improve? Here is hot-list: 1) read English books; 2) watch movies in English, with subtitles; 3) find someone to chat with online, not about work; 4) go to the United States of America and stay there for a few months; 5) make lectures or presentations in English; 6) write in English, like blog post or anything that someone else will have to read. This is what helps me to practice and not to be afraid of speaking English. The full video is here: https://www.youtube.com/watch?v=6de0RNdIIFk

M40: To achieve quality you should numberize your Plan-Do-Check-Act cycle and its participants Feb 21, 2019

Quality management, if I understand PMBOK and ISO-9001 correctly, is all about the Plan-Do-Check-Act cycle, where we 1) plan what quality objectives are important for us and how they can be numbered, 2) let the team produce the results, 3) collect the numbers, and 4) compare them with our expectations and take corrective and preventive actions. In order to make this all happen, you need to turn your human resources in numbers. How do you do that in your software team, depends on many factors. But software business is the easiest one for that: most of our activities are easy to measure. The entire video is here: https://www.youtube.com/watch?v=euEOroFEHWM

M39: Meeting are evil and must be replaced by a disciplined process of decision making Feb 19, 2019

Meetings are a great solution for lazy, immature, stupid, and non-professional software developers, architects, and their managers. The more you grow, the more professional you become, the bigger will be your frustration from those meetings. What is the alternative? How can we make technical decisions without sitting together in a room and talking? The alternative is a strict and disciplined process of decision making, which has to be based on ... guess what ... microtasking. The full video is here: https://www.youtube.com/watch?v=KUUzUb9arNg

M38: Request-for-Proposal (RfP) is how the matchmaking process works in Zerocracy Feb 18, 2019

When you are ready to delegate your software project to Zerocracy, you will need an architect, who will guide you through the bootstrap steps, will understand the requirements, will build the team of freelancers, and will supervise it, with the help of Zerocrat, our AI-powered chatbot. To find that architect you have to submit a Request-for-Proposal (RfP), which will be "purchased" by one of the most active and reputable programmers and you will get a chance to discuss your project with him or her. Then, if you both like each other, the project will start and you will be the Product Owner and requirements provider. If not, you will have to try again or ask help in our Telegram chat. The full video is here: https://www.youtube.com/watch?v=QsxwHdKoWEI

M37: It's only your fault if the requirements you are working with are not clear enough! Feb 15, 2019

It happens very often: the requirements we have to work with are not clear. Customers, requirements providers, product owners, managers, architects, and other programmers are simply too lazy to specify them right and they just drop those feature requests and bugs on our heads. We have to deal with them. The most enthusiastic of us dive into those unclear problem descriptions and attempt to clear things our on their our, attempt "to figure it out themselves." This is a very unprofessional behavior. Instead, you should always try to push back those requirements providers and make sure the requirements you work with are unambiguous, clear, and easy to understand. The full video is here: https://www.youtube.com/watch?v=z59jkRAeBDg

M36: Protect yourself against stupid managers—become their good friend! Feb 14, 2019

You remember my recommendations for a programmer if the management is weak and stupid, right? Don't be loyal. Instead, use their resources for your own good. But what do you do if you are the architect and the tech lead of the project? In that case, the situation is more complicated, but it's solvable. You just need to be more careful, here is how. The full video is here: https://www.youtube.com/watch?v=_Y2lZsRLwlk

M35: A transition from office slavery to pay-by-result model is very expensive Feb 13, 2019

Very often startup founders and CTOs are asking me how and whether it's possible to transition from traditional full-time management to pay-by-result and microtasking, which we practice in Zerocracy. My answer is that it's possible but expensive. It will take time, money, and nerves. Here is a short summary of why it will be so difficult and why you should use Zerocracy instead. The full video is here: https://www.youtube.com/watch?v=dAgRUtR3LQg

M31: What do you do with junior programmers who can't write good code? You train them. Feb 12, 2019

Multitasking is something only senior developers can deal with, because it's stressful, results-focused, and demands a lot of skills, which junior developers simply don't have. However, the question is: What those junior developers should do? How they can contribute to the project? There is a number of possible ways. The full video is here: https://www.youtube.com/watch?v=6OHfh36zLsk

M34: Testing and Quality Assurance (QA) are two entirely different things! Feb 12, 2019

I know so many testers who think that they are QA engineers. They are so wrong that I decided to record a video about that. Testing is about breaking the software and finding bugs. QA is about watching the entire software development process and improving its quality indicators. They are two absolutely different activities. The full video is here: https://www.youtube.com/watch?v=hp4PL0AJAVo

M33: No don't need to be loyal to your employers, use them for your own good! Feb 11, 2019

Proper management is very rare, happens only in some companies. Others are treating people like office slaves, expecting them to do stay in the office instead of delivering results. What do you do when you happen to be hired by such a company? How do you change it? How can you improve your team and motivate your management to shift to better management practices, like microtasking, paying by result, etc? You can't! And you shouldn't even try. The full video is here: https://www.youtube.com/watch?v=Op3EIwhMxrg

M32: Micromanagement happens when tasks are big and motivation is not explicit Feb 08, 2019

Do you know what micromanagement is? It's when your manager is telling you exactly what you have to do right now in order to achieve the results he or she wants. The micromanager doesn't trust you and that's why wants and needs to control every step you make. It's annoying and unproductive, but it's inevitable unless you have small tasks and a transparent and unambiguous system of rewards and punishment. The full video is here: https://youtu.be/0Jte_LGR5Zk

M30: Pay equality and smaller pay gap mean only one thing: the management is weak Feb 06, 2019

The average salary of american workers is growing 1% every year, while the paygap between similar jobs is decreasing. What do I think about this trend? Does it sound like people are getting more every year and it's good? Not at all. This trend is completely against what Zerocracy is fighting for: unequal pay for unequal contribution. We want to work with free people, who get what they deserve because of their work, not because of their place in the company. Meritocracy is yet another name for the movement we are leading now in the industry of software development. The full video is here: https://www.youtube.com/watch?v=mKZOuJ7AAas

M29: Instead of finding the right architect, find a way to manage the architect right Feb 05, 2019

In order to do the project right, you need the right person, right? Wrong! This type of thinking doesn't help at all and only leads to failures. It's the management that needs to be "right," not its people. Watch this morning video about this problem: https://www.youtube.com/watch?v=SSZnloEHeOk

M28: Microtasking works only if you can decompose tasks, PDD helps you do exactly that Feb 04, 2019

Microtasking is a great management method, provided you can break your larger scope into smaller micro-tasks. Who should do this decomposition and how much time will work by itself will take? This question I hear very often when we start talking about paying-by-results and microtasking. We've spent a few years to find the answer and the methodology invented was called Puzzle Driven Development, here is how it works (the full video is there): https://www.youtube.com/watch?v=LmSaC_OjIbQ

M27: Microtasking enables more accurate and precise estimates of a software project's future Feb 01, 2019

You know how much I love microtasking and paying-by-result, but you may wonder how can we estimate the future of our projects if we deal with very small pieces of work. I made an attempt to explain it in the video. Long story short, microtasks not only make estimation easier for computers, but ensure much higher accuracy and preciseness of the result. The full video is here: https://www.youtube.com/watch?v=1rmZN3r5SWg

M26: Don't be afraid of your programmers, just get ready to fight when they get rich on your idea Jan 31, 2019

How do you protect your business ideas from potential theft by your own programmers? Do you sign NDAs? Do you hire only those who won't steal? Well, I believe you should do the opposite. Don't be scared of theft, just be prepared to prove that the idea was originally yours and share their success, when and if they get it. The full video is here: https://www.youtube.com/watch?v=H56jeG_Xi64

M25: Dear investors, Zerocracy is not an on-demand software shop, think bigger! Jan 30, 2019

I've got a meeting with a potential investor a few days ago, which asked me to help him develop some software, in order to prove that Zerocracy is an investable business. I refused and here is the explanation of my logic. The full video is here: https://www.youtube.com/watch?v=F3eRSRt-zDY

M24: Artificial Intelligence is not a thinking machine, but a powerful calculator Jan 29, 2019

We claim that Zerocracy is an AI bot that is capable of managing people better than a human being. But very often I hear questions: How is it possible to make a computer so smart? Is AI so powerful already? In this morning video I ask you a question: Do you know what AI is? What exactly is happening in that "thinking" machines? Do they really "think" as you expect them to? No, they don't. Just like Zerocracy chatbot doesn't really think, but only does what its algorithms are designed to do. There are no thinking machines in the world, as of yet. And they won't show up in the near future. The full video is here: https://www.youtube.com/watch?v=XBZcVHc0LNE

M23: Senior developers are the best, but the most difficult to manage, and the most dagnerous Jan 28, 2019

If you need to demonstrate your investors that your software team is working hard on something great, you need a group of junior developers — they are easy to manage and are afraid of going into conflicts. On the other hand, if you need to develop a great product, you need senior developers. However, they are difficult to manage because they prefer to work for themselves, not for you and your project. Will you be able to manage them? The full video is here: https://www.youtube.com/watch?v=SdrtZIW5JtY

M22: Both full-time hiring and outsourcing will lead your project to failure, Zerocracy won't. Jan 25, 2019

I was asked to explain what Zerocracy is doing exactly, but a potential client of ours. Here is what I managed to create, in just 15 minutes (I wanted to do five, but didn't manage). The bottom line is that full-time hiring and outsourcing are two great recipes for disaster, for a young startup. To the contrary, Zerocracy is a life saver. The full video is here: https://www.youtube.com/watch?v=GozQCUH2D0I

M21: Junior developers are not a good fit for microtasking, they simply can't keep up. Jan 24, 2019

Very often I hear people saying that microtasking is only suitable for junior developers, who are ready to work like "coding monkeys", while professional senior programmers can't do that. That's a mistake. Junior developer simply can't do microtasking, because it's stressful and complex. It's something that only experienced programmers can do right and make money out of it. The video is here: https://www.youtube.com/watch?v=1pHUx-ISrS8

M20: Reporting bugs and deciding whether they should be fixed are two separate acticitives! Jan 23, 2019

The video is here: https://www.youtube.com/watch?v=F3bjFXFRsI8

M19: Want to pay-by-result? You have to do microtasking first, otherwise nothing will work. Jan 22, 2019

The video is here: https://www.youtube.com/watch?v=tHeXxLdGqqI

M18: Writing unit tests or not is not the decision project makes, it's your professional choice Jan 21, 2019

The video is here: https://www.youtube.com/watch?v=MF0xMjyKdKk

M17: Algorithm-driven mining doesn't make a cryptocurrency more democratic, but less transparent Jan 18, 2019

The video is here: https://www.youtube.com/watch?v=77pWgn_JVRk

M16: You either report bugs or implement features. You can't do any of that? You are out. Jan 17, 2019

The video is here: https://www.youtube.com/watch?v=_ppWQCCT8zE

M1: Your enthusiasm may only harm the project if you can't deliver it incrementally Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=gMJNz9AWbQE

M2: We must fully trust the architect, but regularly review the decisions he or she is making Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=PYq05UAwzNk

M3: Zerocracy is not applicable unless motivation is changed from pay-per-time to pay-per-result Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=CZ_Bhg4vW58

M4: A full decentralization is a myth, since the source code inevitably is under someone's control Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=8Lr0cFhwE6M

M5: Professional programmers always need a second opinion, to make sure their code is good enough Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=9tC7p2UTLsU

M6: Keeping all source code in a single monolithic repository is a terrible idea! Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=zljJpADEf_E

M7: Don't be afraid to ask difficult qtns before you get into a partnership, or get ready to lose Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=RNRaVmbWZXI

M8: Since most tech editors have no idea what they are doing, ignore them Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=2oAW9LmYJI4

M9: Every time you see an opportunity to open source a piece of code, do it! Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=3SZ6Zvci4O0

M10: How do you enforce TDD in a team? Put your gang together first. Then use it as a leverage. Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=kY7UYCiMG6s

M11: Freelance means freedom, but it also means poverty; this will change, thanks to Zerocracy! Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=6CPOHvyyY2I

M12: Freelancers are not full-timers working from home; they are a totally different breed Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=1OFgf8XYI2A

M13: A Message Without A Context Is Unprofessional And Very Annoying For The Listener; Don't Do It! Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=fVMml2vpP-Y

M14: The revolution of zero-trust decentralized stms is coming, but it's not only about Blockchain! Jan 16, 2019

The video is here: https://www.youtube.com/watch?v=48mtB40sKhs

M15: Large software projects mean bad projects, don't be proud of them! Jan 16, 2019

Video is here: https://www.youtube.com/edit?video_referrer=watch&video_id=IqnbG826Oyc

Shift-M/41: Focus and accountability with Gordon Tredgold Jan 04, 2019

More details here: https://www.yegor256.com/shift-m/2019/41.html

Shift-M/40: Soft skills with Anne Loehr Dec 19, 2018

More details: https://www.yegor256.com/shift-m/2018/40.html

Shift-M/39: Product Management with Melissa Perri Nov 20, 2018

More details here: https://www.yegor256.com/shift-m/2018/39.html

Shift-M/38: Herd instinct with Jennifer Britton Oct 08, 2018

More details here: https://www.yegor256.com/shift-m/2018/38.html

Shift-M/37: Zen project management with Mike Clayton Oct 01, 2018

More details here: https://www.yegor256.com/shift-m/2018/37.html

Shift-M/36: 70/70 or how to make a business deal Sep 17, 2018

More details here: https://www.yegor256.com/shift-m/2018/36.html

Shift-M/35: Bullying, discussion with Suzanne Lucas Sep 03, 2018

More details: https://www.yegor256.com/shift-m/2018/35.html

Shift-M/34: Respect in software teams with Todd Williams Aug 27, 2018

More details here: https://www.yegor256.com/shift-m/2018/34.html

Shift-M/33: Metrics in project management with Shoaib Ahmed Aug 13, 2018

More details here: https://www.yegor256.com/shift-m/2018/33.html

Shift-M/32: How to deal with project failures with Andy Jordan Aug 06, 2018

More details here: https://www.yegor256.com/shift-m/2018/32.html

Shift-M/31: Waterfall, Agile and self-awareness with Lisa Sieverts Jul 30, 2018

More details here: https://www.yegor256.com/shift-m/2018/31.html

Shift-M/30: change management with Erik van Hurck Jul 23, 2018

More details here: www.yegor256.com/shift-m/2018/30.html

Shift-M/29: Team dynamics in modern IT companies Jul 17, 2018

More details here: https://www.yegor256.com/shift-m/2018/29.html

Shift-M/28: How to be critical and lazy May 21, 2018

Post comments here: https://www.yegor256.com/shift-m/2018/28.html

Shift-M/27: TDD philosophy with GeePaw Hill Apr 30, 2018

See http://www.yegor256.com/shift-m/2018/27.html

Shift-M/26: software testing with James Bach Apr 23, 2018

More details:http://www.yegor256.com/shift-m/2018/26.html

Shift-M/25: Risk management with Ricardo Vargas Apr 16, 2018

2 April 2018; please post your comments here: www.yegor256.com/shift-m/2018/25.html

Shift-M/24: Mandatory skills of a software architect Apr 02, 2018

2 April 2018; please post your comments here: www.yegor256.com/shift-m/2018/24.html

Shift-M/23: No estimates Mar 19, 2018

18 March 2018; please post your comments here: www.yegor256.com/shift-m/2018/23.html

Shift-M/22: How to be honest with a client? Mar 05, 2018

4 March 2018; please post your comments here: www.yegor256.com/shift-m/2018/22.html

Shift-M/21: Sociotech skills in software development Feb 05, 2018

4 February 2018; please post your comments here: www.yegor256.com/shift-m/2018/21.html

Shift-M/20: Vincent Birlouez about PMBOK and project managers Dec 25, 2017

3 November 2017; please post your comments here: www.yegor256.com/shift-m/2017/20.html

Shift-M/19: Typical mistakes we make in bug tracking Dec 18, 2017

18 December 2017; please post your comments here: www.yegor256.com/shift-m/2017/19.html

Shift-M/18: Henrik Mårtensson about HR troubles Dec 11, 2017

3 November 2017; please post your comments here: www.yegor256.com/shift-m/2017/18.html

Shift-M/17: When micro-tasking doesn't work? Dec 04, 2017

5 December 2017; please post your comments here: www.yegor256.com/shift-m/2017/17.html

Shift-M/16: Jose Barato on Indian Outsourcing and Catalonia issues Nov 27, 2017

30 October 2017; please post your comments here: www.yegor256.com/shift-m/2017/16.html

Shift-M/15: How not to trust programmers right Nov 20, 2017

20 November 2017; please post your comments here: www.yegor256.com/shift-m/2017/15.html

Shift-M/14: Bart Vermijlen about Sociocracy, Gamestorming and Agile Nov 13, 2017

24 October 2017; please post your comments here: www.yegor256.com/shift-m/2017/14.html

Shift-M/13: What is the difference between Quality Assurance and Testing? Nov 06, 2017

6 November 2017; please post your comments here: www.yegor256.com/shift-m/2017/13.html

Shift-M/12: Bert Heymans about their LeanCoffee meetup Oct 30, 2017

17 October 2017; please post your comments here: www.yegor256.com/shift-m/2017/12.html

Shift-M/11: How to do stakeholders management right? Oct 24, 2017

20 October 2017; please post your comments here: www.yegor256.com/shift-m/2017/11.html

Shift-M/10: Johanna Rothman about hiring issues Oct 16, 2017

11 October 2017; please post your comments here: www.yegor256.com/shift-m/2017/10.html

Shift-M/9: Padding vs. Risk Management Oct 08, 2017

9 October 2017; please post your comments here: www.yegor256.com/shift-m/2017/9.html

Shift-M/8: How to pay programmers less? Aug 28, 2017

28 August 2017; please post your comments here: www.yegor256.com/shift-m/2017/8.html

Shift-M/7: Hugo Messer about distributed management Aug 10, 2017

10 August 2017; please post your comments here: www.yegor256.com/shift-m/2017/7.html

Shift-M/6: Susanne Madsen about leadership Jul 24, 2017

24 July 2017; please post your comments here: www.yegor256.com/shift-m/2017/6.html

Shift-M/5: Inclusive Management and Diversity Jul 17, 2017

17 July 2017; please post your comments here: www.yegor256.com/shift-m/2017/5.html

Shift-M/4: Yakov Fain about his management philosophy Jun 26, 2017

26 June 2017; please post your comments here: www.yegor256.com/podcast/2017/4.html

Shift-M/3: How to Handle Underperformers on a Team Jun 19, 2017

19 June 2017; please post your comments here: http://www.yegor256.com/podcast/2017/3.html

Make Customers Trust You Jun 17, 2017

BDMSummit 2017; 17 June 2017; Kiev, Ukraine; video is here: https://youtu.be/oiNI2jF46h0

How to be Honest and Keep a Client? Jun 13, 2017

PMCon 2017; 11 June 2017; Kharkiv, Ukraine; video is here: https://www.youtube.com/watch?v=Rip_04Bv3Jk

Shift-M/2: What's Wrong With Project Management Conferences? Jun 12, 2017

12 June 2017; please post your comments here: http://www.yegor256.com/podcast/2017/2.html

Shift-M/1: Why Distributed Teams Fail? Jun 06, 2017

5 June 2017; please post your comments here: http://www.yegor256.com/podcast/2017/1.html

How Much Do You Cost? May 27, 2017

JEEConf 2017; Kyiv, Ukraine; 26 May 2017; video is here: https://www.youtube.com/watch?v=GS45LzE3LPQ

How to Avoid Outsourcing Disaster May 27, 2017

Kyiv Outsourcing Forum 2017; Kyiv, Ukraine; 26 May 2017; video is here: https://www.youtube.com/watch?v=DLk_5BmgTVk

What's Wrong With Object-Oriented Programming? May 18, 2017

RigaDevDays 2017; 15 May 2017; Riga, Latvia; video is here: https://www.youtube.com/watch?v=K_QEOtYVQ7A

Four Best Methods of Time Wasting Mar 31, 2017

DevOn Summit 2017; Delft, The Netherlands; 30 March 2017; video is here: https://www.youtube.com/watch?v=MSBf2RftCKo

How to Deal with Conflicts in a Software Team (Webinar #21) Feb 09, 2017

Video is here: https://www.youtube.com/watch?v=GWLpAZqvqSc

eXtremely Distributed Software Development Dec 21, 2016

DevTernity 2016; Riga, Latvia; 1 December 2016; video is here: https://www.youtube.com/watch?v=7EytYc7K5JA

Who Is a Project Manager? Dec 07, 2016

Webinar #19; 7 December 2016; video is here: https://www.youtube.com/watch?v=zaKTNK8g2-M

Who Is a Software Architect? Nov 22, 2016

BuildStuff Kiev 2016; Kiev, Ukraine; 22 November 2016; video is here: https://www.youtube.com/watch?v=R1lA7pN60xg

How Do You Know When Your Product is Ready to be Shipped? Nov 18, 2016

Build Stuff 2016; Vilnius, Lithuania; 18 November 2016; video is here: https://youtu.be/wd-SA1HVmLg

Keep Your Servers in GitHub Nov 17, 2016

TopConf Tallinn 2016; Tallinn, Estonia; 17 November 2016; video is here: https://www.youtube.com/watch?v=mq4bsnKK0qs

Seven Sins of a Software Project Nov 16, 2016

TopConf Tallinn 2016; Tallinn, Estonia; 16 November 2016

XDSD: How Extreme is Your Team Nov 15, 2016

XPDays Kiev, 2016; Kiev, Ukraine; 12 November 2016. Video is here: https://www.youtube.com/watch?v=tCr9dtGdi2c

Java vs OOP (JavaDay Kyiv 2016) Oct 15, 2016

Java vs OOP (JavaDay Kyiv 2016) by Yegor Bugayenko

Who is a Software Architect? (webinar #13) Sep 26, 2016

Software architect is responsible for failures. Software is powerful enough to make and overrule any decision. But that's not it. We will also talk about delegation of responsibility and micromanagement.

Continuous Integration May Have Negative Effects Sep 17, 2016

WebIT.Festival; Sofia, Bulgaria; 20 April 2016. Original blog post is here: http://www.yegor256.com/2014/10/08/continuous-integration-is-dead.html

Meetings or Discipline (NTPM conference in Gdyna, Poland) Sep 12, 2016

New Trends in Project Management (NTPM); Gdyna, Poland; 26 April 2016

How to Cut Corners and Stay Cool (webinar #15) Sep 10, 2016

We discussed how to turn chaos into a disciplined software development. The discussion will be based on these articles: http://www.yegor256.com/2015/01/15/how-to-cut-corners.html and http://www.yegor256.com/2015/02/16/it-is-not-a-school.html

Printers Instead of Getters in OOP (webinar #18) Sep 07, 2016

Getters are evil in OOP, but what is the alternative? Printers is the way to go. The discussion is based on this article: http://www.yegor256.com/2016/04/05/printers-instead-of-getters.html Video is here: https://www.youtube.com/watch?v=_Q0cNykXB04

The Philosophy of Bugs (webinar #17) Sep 05, 2016

We discussed what bugs were for, how they must be understood by the management, how many of them we should expect to find and what is in general the right philosophy of bug tracking.

Interview with David West (part 2) Sep 03, 2016

Interview with David West, the author of "Object Thinking" book.

Interview with David West (part 1) Sep 03, 2016

Interview with David West

Our TOPPODCAST Picks

Follow Us

Stay Connected

Related Podcasts

Links

Stay Connected