cotalks.dev

Yegor Bugayenko

YouTube: @yegor256

| |

Videos (484)

SQM 3/24: Cognitive Complexity by G. Ann Campbell

SQM 2/24: Cyclomatic Complexity by Thomas J. McCabe

SQM 1/24: Lines of Code

PMBA 2/10: Scope Management

PMBA 1/10: Integration Management

The Pain of OOP, Lecture #4: Setters and object mutability

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

Черно-Белое Айти

The Pain of OOP, Lecture #3: Getters and naked data

The Pain of OOP, Lecture #2: Static methods and attributes are evil

The Pain of OOP, Lecture #1 (again): Algorithms hurt object thinking

PPA 10/10: Code Analysis With Machine Learning

PPA 9/10: Model Checking

PPA 8/10: Symbolic Execution

EQSP 16/20: Первые признаки высокого качества в SE

PPA 7/10: Data Flow Analysis

PPA 6/10: Ingredients of Program Analysis

PPA 5/10: Abstract Machines

EQSP 15/20: Тестирование второго порядка

PPA 4/10: Formal Semantics

PPA 3/10: Contextual Analysis

EQSP 14/20: Нефукциональные требования и их тестирование

PPA 2/10: Syntax Analysis

PPA 1/10: Formal Grammars

EQSP 13/20: Несколько примеров интеграционных тестов

EQSP 12/20: Философия автоматизированных тестов

Object Thinking Meetup #8: Yegor Bugayenko / Исключения как контейнеры для данных

Object Thinking

Object Thinking Meetup #8: Maxim Trunnikov / БезУсловное ООП

Object Thinking

EQSP 11/20: Автоматизация изменений в базе данных, с помощью Liquibase

EQSP 10/20: Почему Continuous Integration не работает и как работать должен

EQSP 9/20: Несколько советов по использованию Maven

И2: Стартапы, IPO, Инвестиции, Капитализм, Труд и Воля

EQSP 19-20/20: Discipline of software development

EQSP 17-18/20: Quality of software project documentation

EQSP 16/20: Coverage Control, Mutation Testing

EQSP 15/20: Stress, Load, Performance, End-to-End Testing, BDD

EQSP 7-8/20: Автоматизация сборки на примере Makefile

EQSP 14/20: Integration Testing

EQSP 13/20: Principles of automated testing (both unit and integration)

EQSP 5-6/20: Управление зависимостями на примере Maven, Bundler, и Npm

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

Черно-Белое Айти

EQSP 9/20: Some Recipes Against Dependency Hell

EQSP 10/20: Semantic Versioning of Artifacts

EQSP 12/20: Releasing Changes to Databases

EQSP 11/20: Releasing Applications as Artifacts

Object Thinking #7: Yegor Bugayenko / Immutability + Generics

Object Thinking

Object Thinking Meetup #7: Nikolay Kudasov / Algebraic Data Types (алгебраические типы данных)

Object Thinking

EQSP 4/20: Making Custom GitHub Actions, by Example

EQSP 2/20: XCOP and Customizing Checkstyle

EQSP 3/20: CI and DevOps with GitHub Actions

EQSP 1/20: Why Style Checking is Mandatory?

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

Черно-Белое Айти

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

M198: It's impossible to be a software expert with an empty GitHub account

M197: The worst demotivation for A-players is their equal appreciation with C-players

Готовы ли мы к роботам, а они к нам?

Ты уже сделал своего робота?

M196: Maintaining a creative spirit in an enterprise is hard, but possible

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

Черно-Белое Айти

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

M194: Keep a balance between work for money and investments into yourself

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

Лекция перед учащимися 7-11 классов IT лицея КФУ

M192: Find a way to structure your opinion after each interview of a new candidate

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

Черно-Белое Айти

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

M190: Make sure the bugs you report explain the simplest possible scenarios

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

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

Черно-Белое Айти

M188: I don't think ML will ever be able to write code

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

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

Черно-Белое Айти

Shift-M/51: Michael Kay about XSLT, XML, and software business

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

M185: CTO has to write code and delegate management to PMs

M184: Keep your best programmers from maintenance mode

SIMBA: Simplified Management by Artifacts (at Merge Conf)

M183: Start making a software product from configuring its build pipeline

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

Черно-Белое Айти

M182: Open source products are made by young and hungry

M181: How do you manage under-performers? You ignore them.

M180: Pre-commit Hook is a wrong idea

M179: Calibrated Achievement Points (CAP) to measure R&D productivity

SSD 16/16: Future of Software Design

SSD 15/16: Coupling & Cohesion and Other Metrics

SSD 14/16: Test Patterns and Anti-Patterns

SSD 13/16: Test-Driven Development

SSD 11/16: Microservices and RESTful APIs

SSD 12/16: Serverless Design in Cloud

Object Thinking Meetup #6: Yegor Bugaenko / Veil Objects

Object Thinking Meetup #6: Emil Fataliev / Spring Web MVC without DTO

Object Thinking

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

Черно-Белое Айти

M178: Try to focus your team on artifacts and their delivery status

SSD 10/16: Continuous Delivery

SSD 9/16: IDEF, SQL, NoSQL

KaiCode #2: pip-license-checker by @pilosus

M177: Auto-formatters do more harm than good for programmers

SSD 8/16: Unified Modeling Language (UML)

A conversation with Innopolis University students about OOP, open source, and career development

Shift-M/49: Greg Young about Software Design

SSD 7/16: XML vs JSON

SSD 6/16: Patterns, Anti-Patterns, and Refactoring

SSD 5/16: Object Thinking and DDD

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

Черно-Белое Айти

SSD 4/16: Object-Oriented Analysis & Design

SSD 3/16: Rational Unified Process vs. Agile

KaiCode #1: ngs-lang/ngs by @ilyash

SSD 2/16: Requirements Engineering

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

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

SSD 1/16: README vs. IEEE

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

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

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

Черно-Белое Айти

Shift-M/47: Bjarne Stroustrup on the future of programming

M173: The inspiration for coding comes from personal projects

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

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

Черно-Белое Айти

Lecture on Unit Testing in Innopolis University

M171: submit your research to ICCQ Student Research Competition

M170: recruiters may do a better job if listen to us programmers

M169: Before you write a good text make sure you like how it looks

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

Черно-Белое Айти

M168: a professional software engineer may also be a scientist/researcher

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

M166: Challenging tasks and objective appraisal is what keeps top performers in the team

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

Черно-Белое Айти

Shift-M/46: Fair Management with Pim de Morree

Encapsulation Is Dead, Let's Use Distance of Coupling Instead (Webinar #55)

M165: Contribute to the community if you want to do "good"

F1: Future of Software, Programming, Work Remotely, etc.

M164: Fixed-Price contracts are much worse than Time&Material

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

Черно-Белое Айти

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

Новая Хронология, "Тайна египетских зодиаков" (5-я серия из 24-х)

Новая Хронология

Новая Хронология, "В каком веке жил Христос" (9-я серия из 24-х)

Новая Хронология

Новая Хронология, "Забытый Иерусалим" (10-я серия из 24-х)

Новая Хронология

Новая Хронология, "Символы Древнего Рима" (24-я серия из 24-х)

Новая Хронология

Новая Хронология, "Этруски — это русские" (23-я серия из 24-х)

Новая Хронология

Новая Хронология, "Солдаты Империи" (22-я серия из 24-х)

Новая Хронология

Новая Хронология, "Реформация" (21-я серия из 24-х)

Новая Хронология

Новая Хронология, "Радзивиловская летопись" (20-я серия из 24-х)

Новая Хронология

Новая Хронология, "Как писали русскую историю" (19-я серия из 24-х)

Новая Хронология

Новая Хронология, "Первые Романовы" (18-я серия из 24-х)

Новая Хронология

Новая Хронология, "Смута" (17-я серия из 24-х)

Новая Хронология

Новая Хронология, "Куликово поле" (7-я серия из 24-х)

Новая Хронология

Новая Хронология, "Русь Орда" (8-я серия из 24-х)

Новая Хронология

Новая Хронология, "Иван Грозный" (16-я серия из 24-х)

Новая Хронология

Новая Хронология, "Истину можно вычислить" (3-я серия из 24-х)

Новая Хронология

Новая Хронология, "Алхимия пирамид" (4-я серия из 24-х)

Новая Хронология

Новая Хронология, "Господин Великий Новгород" (6-я серия из 24-х)

Новая Хронология

Новая Хронология, "Три великие фальшивки" (15-я серия из 24-х)

Новая Хронология

Новая Хронология, "Поделки и подделки" (14-я серия из 24-х)

Новая Хронология

Новая Хронология, "Фальсификация письменной истории" (13-я серия из 24-х)

Новая Хронология

Новая Хронология, "Реконструкция истории" (12-я серия из 24-х)

Новая Хронология

Новая Хронология, "Московский Кремль" (11-я серия из 24-х)

Новая Хронология

Новая Хронология, "На чем основана история" (2-я серия из 24-х)

Новая Хронология

Новая Хронология, "Знаем ли мы свою историю" (1-я серия из 24-х)

Новая Хронология

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

Черно-Белое Айти

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

Черно-Белое Айти

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

Черно-Белое Айти

RAII in Java (Webinar #52)

Fat and Skinny Design (Webinar #51)

The Pain of OOP, Lecture #1: Algorithms

Why Static Methods Are Evil?

Object Thinking

Mikhail Yakushin: Constants Have no Place in OOP

Object Thinking

Sergey Kapralov: DI Containers vs. Objects

Object Thinking

Object Thinking Meetup #5 (live streaming recorded)

Object Thinking

Object Thinking Meetup #4 (live streaming recorded)

Object Thinking

Object Thinking Meetup #3 (live streaming recorded)

Object Thinking

Andrey Valyaev: Don't Write Test Methods

Object Thinking

Guseyn Ismayylov: Declarative Unit Testing in NodeJS

Object Thinking

От Java к ООП (митап в Краснодаре)

TDD upside down or how to cut corners (in Russian with English subtitles)

Software Testing Philosophy (in Russian)

How I didn't get a job at Amazon (in Russian with English subtitles)

Typical Mistakes of Startups (in Russian with English subtitles)

Object-Oriented Mistakes in OpenJDK (part 1)

Object-Oriented Mistakes in OpenJDK (part 2)

PayPal demonstrates what a "side-effect of mutability" means, in their Ruby SDK

Don't let your methods change their behavior depending on incoming boolean flags!

Don't make assumptions in your code, they only hurt your clients

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

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

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

M6: Keeping all source code in a single monolithic repository is a terrible idea!

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

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

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

M13: A message without a context is unprofessional and very annoying for the listener; don't do it!

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

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

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

M36: Protect yourself against stupid managers—become their good friend!

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

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

M44: Why do you think you are a senior developer? Who says so? Think again.

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

M41: Six steps to a better speaking English for a software developer

M52: Three-branches release model: Master-Candidate-Live

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

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

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

M54: Make sure you control your programmers and do it explicitly and openly

M55: The programming language you choose must match your project business objectives

M64: You want your programmers to be your enemies? Pay them monthly.

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

M57: Tech startups fail mostly because of software development incompetence

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

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

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

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

M69: Write tutorials instead of training and teaching

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

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

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

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

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

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

M76: Learn Rational Unified Process to understand SDLC better

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

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

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

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

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

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

M81: How to make your GitHub repo popular? Eight things to pay attention to.

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

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

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

M86: The README file must be the only provider of product specification

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

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

M89: Deliver your trust continuously, not discrete

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

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

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

M156: Competition doesn't contradict with collaboration

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

M95: Only lazy and immature programmers are afraid of penalties and punishment

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

M100: Tech audits help you identify the gaps between your codebase and industry standards

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

M97: Let your followers be your best censors helping you think more logical

M154: Proper competition prevents cheating in a software team

M101: Every non-standard design decision you make is a maintainability risk

M103: Large software companies will have to work with freelancers, b/c they will have no choice

M105: Open source developers inevitably have better soft and tech skills

M106: Very soon all important software projects will open their sources

M104: Refactoring without a ticket means stealing project resources

M107: Make your GitHub project look attractive and contributors will come

M108: Your job is to prepare your open source project for the future community

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

M110: Professional developers enjoy being punished by static analyzers

M111: Use open source projects to beat the boresome of the office work

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

M113: Your coding should be a social activity and GitHub is your social network

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

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

M117: Breaking responsibility down is the responsibility of a manager/architect

M115: Going along with large open source projects is a perfect strategy for newbies

M116: Which license to use for an open source product?

M119: How to be a jack of all trades and not hate it?

M118: Deploy your ready-to-use open source artifacts into immutable repositories

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

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

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

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

M123: One README should be enough for any open source project

M124: Put your talent away and learn new skills when working in an enterprise

M126: Use open source projects to build yourself a support group

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

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

M129: Niche narrow-skilled developers will earn more than others

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

M130: The root cause of most software problems is the chaos in the code

M133: How much do you care about open source nature of your project?

M132: Your pet projects are the best contribution to your resume

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

M158: Eliminating team conflicts leads to less collaboration, not more

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

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

M138: Morning stand-ups are nothing else but guilt-triggers

M136: Any software product has an unlimited number of bugs

M139: It seems that better programmers write more lines of code

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

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

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

M143: Daily reports are a perfect guilt-triggering instrument for a lazy team

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

M146: Collaboration and teamwork are highly overrated in software teams

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

M145: Internal competition is what your team needs to achieve results

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

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

M150: Competition is good, while badly chosen tools and rules may be dangerous

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

M152: There is no management without personal responsibility

M153: How managers in self-managing orgs judge your performance?

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

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

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

M162: When punishment is justified in a software team?

M99: Don't punish your team for technical mistakes, use audit results to prevent future troubles

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

M92: We in Zerocracy use Boost Factor to help architect motivate programmers

Week 19.02: Ruby bugs, Exchange Rate, Ruby SDK, Bitcointalk, Zerocracy plans

Week 19.05: Zold queue overflow, educational videos, fund raising

Week 19.03: Memory leakage is gone, Fin model explained, New clients coming

Week 19.01: Master nodes, GC, Memory leakage, and Fin Model

Week 19.09: Mobile API, Callback API, First attack, General Ledger

Week 19.07: New projects, 2% fee, Blockchain, Rebase, Migrate, Bitcointalk

How to run individual tests in BundlesTest

Week 19.12: Zold security, PayPal, crypto future of Zerocracy, plans

Week 19.17: Tech Events, First Refund, Bitcoin adapter, Alterdice

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

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

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

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

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

M12: Freelancers are not full-timers working from home; they are a totally different breed.

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

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

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

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

M20: Reporting bugs and deciding whether they should be fixed are two separate activities!

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

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

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

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

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

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

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

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

M32: Micromanagement happens when tasks are big and motivation is not explicit

M34: Testing and Quality Assurance (QA) are two entirely different things!

M33: You don't need to be loyal to your employers, use them for your own good!

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

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

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

M42: Make sure your software is deployable from the first day!

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

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

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

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

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

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

M59: How to not get frustrated when dealing with freelancers and microtasking?

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

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

M62: Five steps to migrate from traditional management to microtasking

M63: The growth of Zold rate is direct marketing expenses of Zerocracy

What's wrong with global variables? (Webinar #36)

What is Wrong About NULL in OOP? (webinar #3)

Objects vs. Static Methods (webinar #1)

Don't Create Objects That End With -ER (webinar #5)

Immutable Objects vs. Common Sense (webinar #2)

Why Getters-and-Setters Is An Anti-Pattern? (webinar #4)

Daily Stand-Up Meetings Are Evil (webinar #11)

Unit Testing vs Debugging (webinar #26)

Takes, Java Web Framework, Intro (webinar #12)

A Few Thoughts About Constructors in OOP (webinar #7)

What's Wrong About Utility Classes? (webinar #6)

What Fake Objects Are For? (webinar #8)

Who is a Software Architect? (webinar #13)

Dependency Injection Container is a Bad Idea (webinar #9)

How to Cut Corners and Stay Cool (webinar #15)

Why ORM is an Anti-Pattern? (webinar #10)

Java Annotations Are a Big Mistake (webinar #14)

Printers Instead of Getters in OOP (webinar #18)

Smart Classes and Functionality-Poor Interfaces (webinar #16)

The Philosophy of Bugs (webinar #17)

Micro-management vs. micro-tasking (webinar #25)

Who Is a Project Manager? (webinar #19)

Gradients of Immutability (webinar #20)

Naked Data in OOP (webinar #22)

How to Deal With Conflicts in a Software Team (Webinar #21)

Inheritance vs. Subtyping (webinar #24)

Puzzle Driven Development (webinar #23)

Veil Objects to Replace DTOs (Webinar #50)

Xembly, an imperative language for XML manipulations (webinar #46)

Object-Oriented Java Web App from Scratch in One Hour: ThreeCopies.com (Webinar #28)

Why Private Static Literals are Evil? (Webinar #48)

Aspect Oriented Programming: Pros and Cons (Webinar #47)

Cactoos 0.12 polishing and releasing (webinar #27)

How Much Immutability Is Enough (webinar #45)

How to win $4096 in the next year Quality Award? (webinar #29)

A practical example of making an object-oriented HTTP server in Java (webinar #42)

What Is Cohesion in OOP? (Webinar #49)

Lazy Loading via Java Lambda (Webinar #30)

Decorating Envelopes in OOP (webinar #31)

Synchronized Decorators for Thread-Safety (Webinar #32)

The Alternative to Fluent Interfaces in Java (webinar #33)

Names of objects, methods and variables in OOP (Webinar #37)

How to Get Rid of the NEW Operator (Webinar #34)

When do you validate your objects? (Webinar #35)

Parsing Objects vs Parsers (Webinar #38)

A practical example of ORM-free persistence layer (Webinar #39)

The Power of Decorators (webinar #40)

How many RETURN statements is enough? (Webinar #41)

Best Practices of Exception Throwing (Webinar #53)

How EOLANG Was Made and How to Make a DSL with ANTLR4 (Webinar #54)

Барух Садогурский и Егор Бугаенко на Joker 2018

Baruch Sadogursky and I talking about Java and OOP (in Russian, with English subtitles)

Interview with David West (part 1)

Interview with David West (part 2)

David M. West on management, education, motivation and politics

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

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

Four factors of success (in Russian with English subtitles)

Зачем программистам искусственный интеллект?

How AI can help us, programmers?

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

ORM is offensive (in Russian with English subtitles)

Object Oriented Lies (in Russian with English subtitles)

How Immutability Helps in OOP (in Russian with English subtitles)

ORM is a perfect anti-pattern

OOP is dead? Not yet! (in Russian with English subtitles)

Java vs OOP (in Russian with English subtitles)

ORM is an Offensive Anti-Pattern

Java Annotations Are Evil (in Russian with English subtitles)

Utility Classes Are Killing Us (in Russian with English subtitles)

What's Wrong With Object-Oriented Programming?

Object-Oriented Flavor for JUnit Tests

Java Annotations Are a Bad Idea

How Anemic Objects Kill OOP

Java vs OOP (JavaDay Kyiv)

How to Inject Less?

Magic Numbers Are Not Evil. Large Scope Is.

Q4: How to make sure programmers write documentation? (by Iulian Margeloiu)

Q3: How to enforce more formal communications in a team? (by Andriy Kryvtsun)

Q2: What to do if the client doesn't want to pay for quality? (by Kartikey Tanna)

Q1: How to increase the accuracy of QA planning? (by Vladislav Voinov)

How Much Do You Cost?

Who Manages Who? (in Russian with English subtitles)

eXtremely Distributed Software Development, at DevTernity

How Much Immutability Is Enough?

Need Robust Software? Make It Fragile

How Do You Talk To Your Microservice?

XDSD: management without meetings

Chat Bots are the new UI

Chat Bots vs UI

Meetings Help Us and Kill Our Projects

Meetings-free Programming

Software Outsourcing, 10 Years Ahead (in Russian with English subtitles)

How Teamed.io Manages Programmers (in Russian with English subtitles)

Blame the Project

Seven Sins of a Software Project

Continuous Integration May Have Negative Effects

Meetings Or Discipline

Pre-flight Build Pitfalls

Microservices as Chat Bots

Need It Robust? Make It Fragile!

Deployment Scripts Are Dead. Meet Rultor.

Micromanagement (in Russian with English subtitles)

Don't Be Overexcited About Amsterdam (in Russian with English subtitles)

Problems with Chat Bots (as Micro Services)

Chat Bot Architecture

Eight Maturity Levels of Continuous Integration

Practical Example of AOP with AspectJ (in Russian with English subtitles)

Trial by Combat for OOP Honor (in Russian with English subtitles)

Practical Example of a One-Click Release

Seven Sins of a Software Project

Who Is a Software Architect?

How Do You Know When Your Product is Ready to be Shipped?

Management without managers (in Russian with English subtitles)

Seven Enemies of Our Motivation (in Russian with English subtitles)

Get Rid of Experts (in Russian with English subtitles)

Four Best Practices of Time Wasting

How to Avoid Outsourcing Disaster

Quantity vs. Quality (in Russian)

Make Customers Trust You

How to be Honest and Keep a Client?

PostgreSQL + Liquibase + Docker + Maven + Java

How we decide how much to pay programmers?

Zold: Life Without Blockchain (in Russian)

Quality vs. Quantity (in Russian)

Who Cares About Quality? (in Russian)

Experts vs Expertise

How True Experts Manage Their Expertise (in Russian)

The Future of Blockchain (discussion panel, in Russian)

Testing and Testers