cotalks.dev
Login
Yegor Bugayenko
YouTube:
link
all (484)
|
events (12)
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, Инвестиции, Капитализм, Труд и Воля
Interviews
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
Good morning
M198: It's impossible to be a software expert with an empty GitHub account
Good morning
M197: The worst demotivation for A-players is their equal appreciation with C-players
Good morning
Готовы ли мы к роботам, а они к нам?
Conferences
Ты уже сделал своего робота?
Conferences
M196: Maintaining a creative spirit in an enterprise is hard, but possible
Good morning
N15: Русские Хакеры, Agile, Профсоюзы, Безработица, Русский GitHub
Черно-Белое Айти
M195: Static analyzers find bugs in code, but who finds bugs in programmers?
Good morning
M194: Keep a balance between work for money and investments into yourself
Good morning
M193: What is fun and joy for you, being a programmer?
Good morning
Лекция перед учащимися 7-11 классов IT лицея КФУ
Lectures
M192: Find a way to structure your opinion after each interview of a new candidate
Good morning
N14: Стартапы, Предприниматели, JetBrains, Илон Маск и Twitter, Оскар и Will Smith, Жириновский
Черно-Белое Айти
M191: When a bug report is not as simple as it can be, don't fix it
Good morning
M190: Make sure the bugs you report explain the simplest possible scenarios
Good morning
M189: How would you decide who deserves to be authors of a published paper?
Good morning
N13: Украина, Санкции, Железный Занавес, Иммиграция
Черно-Белое Айти
M188: I don't think ML will ever be able to write code
Good morning
M187: Why did I return a new MacBook Pro 2021 worth $5500 back to Apple?
Good morning
N12: Анонимизация, Выгорание, Циан и славяне, Сколково и стартапы
Черно-Белое Айти
Shift-M/51: Michael Kay about XSLT, XML, and software business
Interviews
M186: Make sure your CV has something nobody else has and you'll be fine
Good morning
M185: CTO has to write code and delegate management to PMs
Good morning
M184: Keep your best programmers from maintenance mode
Good morning
SIMBA: Simplified Management by Artifacts (at Merge Conf)
Conferences
M183: Start making a software product from configuring its build pipeline
Good morning
N11: Meta, Трамп, Дискриминация, PinePhone, Домогательства, Профсоюз Программистов
Черно-Белое Айти
M182: Open source products are made by young and hungry
Good morning
M181: How do you manage under-performers? You ignore them.
Good morning
M180: Pre-commit Hook is a wrong idea
Good morning
M179: Calibrated Achievement Points (CAP) to measure R&D productivity
Good morning
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
Good morning
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
Good morning
SSD 8/16: Unified Modeling Language (UML)
A conversation with Innopolis University students about OOP, open source, and career development
Shift-M
Shift-M/49: Greg Young about Software Design
Interviews
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
Good morning
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
Good morning
M174: Your personal goals go first, team and project goals next
Good morning
N8: Космический туризм, Рынок труда, AI и кодинг, Русские хакеры
Черно-Белое Айти
Shift-M/47: Bjarne Stroustrup on the future of programming
Interviews
M173: The inspiration for coding comes from personal projects
Good morning
M172: When requirements are vague, you don't quit, you make your own product
Good morning
N7: Роскомнадзор, Вакцинация, Китай и Биткоин, Новый Chrome, ИИ
Черно-Белое Айти
Lecture on Unit Testing in Innopolis University
Lectures
M171: submit your research to ICCQ Student Research Competition
Good morning
M170: recruiters may do a better job if listen to us programmers
Good morning
M169: Before you write a good text make sure you like how it looks
Good morning
N6: Китайское черное зеркало, NFT токены, New IP, новые языки программирования
Черно-Белое Айти
M168: a professional software engineer may also be a scientist/researcher
Good morning
M167: Sometimes you have to be an imposter, either you like it or not
Good morning
M166: Challenging tasks and objective appraisal is what keeps top performers in the team
Good morning
N5: Роскомнадзор, Китайские хакеры, Google и их офис, Rockstar Games
Черно-Белое Айти
Shift-M/46: Fair Management with Pim de Morree
Interviews
Encapsulation Is Dead, Let's Use Distance of Coupling Instead (Webinar #55)
Webinars
M165: Contribute to the community if you want to do "good"
Good morning
F1: Future of Software, Programming, Work Remotely, etc.
M164: Fixed-Price contracts are much worse than Time&Material
Good morning
N4: Clubhouse, GameStop, Навальный, Китай, ИИ, Биткоин и Патенты
Черно-Белое Айти
M163: If you as a manager don't punish wrong-doing, the team will punish you
Good morning
Новая Хронология, "Тайна египетских зодиаков" (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)
Webinars
Fat and Skinny Design (Webinar #51)
Webinars
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 к ООП (митап в Краснодаре)
Meetups
TDD upside down or how to cut corners (in Russian with English subtitles)
Meetups
Software Testing Philosophy (in Russian)
Meetups
How I didn't get a job at Amazon (in Russian with English subtitles)
Meetups
Typical Mistakes of Startups (in Russian with English subtitles)
Meetups
Object-Oriented Mistakes in OpenJDK (part 1)
Meetups
Object-Oriented Mistakes in OpenJDK (part 2)
Meetups
PayPal demonstrates what a "side-effect of mutability" means, in their Ruby SDK
Live Coding
Don't let your methods change their behavior depending on incoming boolean flags!
Live Coding
Don't make assumptions in your code, they only hurt your clients
Live Coding
M1: Your enthusiasm may only harm the project if you can't deliver it incrementally
Good morning
M4: A full decentralization is a myth, since the source code inevitably is under someone's control
Good morning
M8: Since most tech editors have no idea what they are doing, ignore them
Good morning
M6: Keeping all source code in a single monolithic repository is a terrible idea!
Good morning
M7: Don't be afraid to ask difficult qstns before you get into a partnership, or get ready to lose
Good morning
M9: Every time you see an opportunity to open source a piece of code, do it!
Good morning
M10: How do you enforce TDD in a team? Put your gang together first. Then use it as a leverage.
Good morning
M13: A message without a context is unprofessional and very annoying for the listener; don't do it!
Good morning
M18: Writing unit tests or not is not the decision project makes, it's your professional choice
Good morning
M26: Don't be afraid of your programmers, just get ready to fight when they get rich on your idea
Good morning
M31: What do you do with junior programmers who can't write good code? You train them.
Good morning
M36: Protect yourself against stupid managers—become their good friend!
Good morning
M38: Request-for-Proposal (RfP) is how the matchmaking process works in Zerocracy
Good morning
M40: To achieve quality you should numberize your Plan-Do-Check-Act cycle and its participants
Good morning
M44: Why do you think you are a senior developer? Who says so? Think again.
Good morning
M43: Technical interviews are pointless, pay attention to these five things instead!
Good morning
M41: Six steps to a better speaking English for a software developer
Good morning
M52: Three-branches release model: Master-Candidate-Live
Good morning
M47: What is the difference between Zerocracy and Upwork? We are not competitors!
Good morning
M50: Testing is the process of confirming that the software has defects (JPoint talk rehearsing)
Good morning
M51: Don't hide error stacktraces, make end-users part of your quality control instead!
Good morning
M54: Make sure you control your programmers and do it explicitly and openly
Good morning
M55: The programming language you choose must match your project business objectives
Good morning
M64: You want your programmers to be your enemies? Pay them monthly.
Good morning
M58: Don't expect UI/UX people to work in microtasking mode, they are too creative for that
Good morning
M57: Tech startups fail mostly because of software development incompetence
Good morning
M65: If you need to learn the code around your microtask, don't do it! Create a new ticket.
Good morning
M67: The future of software development has no offices and no companies, only projects
Good morning
M66: If you will manage programmers the way Google does it, you will lose
Good morning
M68: Is it necessary to be a full-timer first, in order to become a freelancer? Yes, why not!
Good morning
M69: Write tutorials instead of training and teaching
Good morning
M70: A software team without conflicts can't produce anything of a good quality
Good morning
M71: Motivating programmers by equity or profit sharing is a bad idea, it doesn't work
Good morning
M72: Zold, like any other young cryptocurrency, needs master nodes to survive
Good morning
M73: It is your job, as an architect, to convert client's requirements into tickets
Good morning
M74: If your project doesn't have a formal Risk List, you are doing management wrong
Good morning
M78: Programmers are not your property, don't invest in them!
Good morning
M76: Learn Rational Unified Process to understand SDLC better
Good morning
M75: Your presence in social networks is important for your career as a software architect
Good morning
M155: The best and the only way to reward top talents is recognition through fair competition
Good morning
M77: Lines-of-Code don't show anything meaningful, but Hits-of-Code are pretty accurate
Good morning
M80: Every two weeks you should hire a new auditor to review your software project
Good morning
M82: Is it possible to open the entire source code base and still make business? Definitely.
Good morning
M79: Make as many open source libraries as possible, eventually one of them will become a success
Good morning
M81: How to make your GitHub repo popular? Eight things to pay attention to.
Good morning
M84: Don't chase your team members, make them chase you
Good morning
M83: Strong opinions loosely held is not a problem, the absence of an architect is
Good morning
M85: The source code is just a part of a software project, not the biggest one
Good morning
M86: The README file must be the only provider of product specification
Good morning
M91: Full-timers want to look smart, freelancers want to deliver results
Good morning
M88: If you are working on a prototype for longer than two weeks, you are doing it wrong
Good morning
M89: Deliver your trust continuously, not discrete
Good morning
M90: RUP is a framework, Agile is a philosophy; just like Zerocracy and XDSD
Good morning
M93: To become a good programmer you have to find a project that rejects your mistakes
Good morning
M94: It is impossible to make a full-timer deliver results, unless they want it
Good morning
M156: Competition doesn't contradict with collaboration
Good morning
M98: If you think that your team is doing fine, you are a bad manager
Good morning
M95: Only lazy and immature programmers are afraid of penalties and punishment
Good morning
M96: Freelancers are a pain, but they are your only hope if you want the quality to go up
Good morning
M100: Tech audits help you identify the gaps between your codebase and industry standards
Good morning
M102: Zerocracy may look like utopia for you now, but eventually you will be there
Good morning
M97: Let your followers be your best censors helping you think more logical
Good morning
M154: Proper competition prevents cheating in a software team
Good morning
M101: Every non-standard design decision you make is a maintainability risk
Good morning
M103: Large software companies will have to work with freelancers, b/c they will have no choice
Good morning
M105: Open source developers inevitably have better soft and tech skills
Good morning
M106: Very soon all important software projects will open their sources
Good morning
M104: Refactoring without a ticket means stealing project resources
Good morning
M107: Make your GitHub project look attractive and contributors will come
Good morning
M108: Your job is to prepare your open source project for the future community
Good morning
M109: Open your sources piece by piece, not all at once
Good morning
M110: Professional developers enjoy being punished by static analyzers
Good morning
M111: Use open source projects to beat the boresome of the office work
Good morning
M157: We must measure productivity, but using the right metrics only
Good morning
M113: Your coding should be a social activity and GitHub is your social network
Good morning
M112: Put as much as possible on GitHub, no matter what it is
Good morning
M114: The performance of programmers can be measured, with the right metrics
Good morning
M117: Breaking responsibility down is the responsibility of a manager/architect
Good morning
M115: Going along with large open source projects is a perfect strategy for newbies
Good morning
M116: Which license to use for an open source product?
Good morning
M119: How to be a jack of all trades and not hate it?
Good morning
M118: Deploy your ready-to-use open source artifacts into immutable repositories
Good morning
M121: Don't be frustrated by the enterprise chaos around you, conquer it!
Good morning
M120: Don't wait for your manager to tell you what to do, do what you think is right (open source)
Good morning
M122: Don't help them, instead use their free contribution to improve the product
Good morning
M125: When you contribute to your project altruistically, you are killing it
Good morning
M123: One README should be enough for any open source project
Good morning
M124: Put your talent away and learn new skills when working in an enterprise
Good morning
M126: Use open source projects to build yourself a support group
Good morning
M127: The ability to explain a problem so that it's understood is the most important soft skill
Good morning
M128: Don't quit failing projects, quit those that fail you
Good morning
M129: Niche narrow-skilled developers will earn more than others
Good morning
M131: Be aware of conflict-of-interest concerns when you open source while being employed
Good morning
M130: The root cause of most software problems is the chaos in the code
Good morning
M133: How much do you care about open source nature of your project?
Good morning
M132: Your pet projects are the best contribution to your resume
Good morning
M134: Don't blame the situation for the mess in the code, it's only your fault
Good morning
M158: Eliminating team conflicts leads to less collaboration, not more
Good morning
M137: Don't ask your programmers to estimate, tell them how much you have
Good morning
M135: Don't ask for approval, educate them so that they make the decision themselves
Good morning
M138: Morning stand-ups are nothing else but guilt-triggers
Good morning
M136: Any software product has an unlimited number of bugs
Good morning
M139: It seems that better programmers write more lines of code
Good morning
M140: Morning stand-ups are evil, use other management instruments instead
Good morning
M144: Programmers are lazy, either in a good or a bad way, bu they are
Good morning
M141: Lines of Code is a good metric if your management is perfect, otherwise it will hurt
Good morning
M143: Daily reports are a perfect guilt-triggering instrument for a lazy team
Good morning
M142: Your management is perfect only if you can pay everybody by results, not by time
Good morning
M146: Collaboration and teamwork are highly overrated in software teams
Good morning
M147: The quality of code review(er) can be measured by the frequency of rejections
Good morning
M145: Internal competition is what your team needs to achieve results
Good morning
M148: How do you ask your manager to raise your salary? You don't!
Good morning
M149: Rewards without quality control will only hurt, but so what?
Good morning
M150: Competition is good, while badly chosen tools and rules may be dangerous
Good morning
M151: Don't judge your people, let the market do it much better
Good morning
M152: There is no management without personal responsibility
Good morning
M153: How managers in self-managing orgs judge your performance?
Good morning
M159: If your objective is to keep the team intact, competition is not for you
Good morning
M160: Traditional top-down planning doesn't work, try better alternative
Good morning
M161: It's not the competition that destroys a team, but unfair rules
Good morning
M162: When punishment is justified in a software team?
Good morning
M99: Don't punish your team for technical mistakes, use audit results to prevent future troubles
Good morning
M87: If you are afraid of being replaced, you are not a good programmer
Good morning
M92: We in Zerocracy use Boost Factor to help architect motivate programmers
Good morning
Week 19.02: Ruby bugs, Exchange Rate, Ruby SDK, Bitcointalk, Zerocracy plans
Week 19.05: Zold queue overflow, educational videos, fund raising
Zerocracy
Week 19.03: Memory leakage is gone, Fin model explained, New clients coming
#NoMeetings
Zerocracy
Week 19.01: Master nodes, GC, Memory leakage, and Fin Model
#NoAltruism
Zerocracy
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
Zerocracy
#NoSalaries
Zerocracy
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)
Webinars
What is Wrong About NULL in OOP? (webinar #3)
Webinars
Objects vs. Static Methods (webinar #1)
Webinars
Don't Create Objects That End With -ER (webinar #5)
Webinars
Immutable Objects vs. Common Sense (webinar #2)
Webinars
Why Getters-and-Setters Is An Anti-Pattern? (webinar #4)
Webinars
Daily Stand-Up Meetings Are Evil (webinar #11)
Webinars
Unit Testing vs Debugging (webinar #26)
Webinars
Takes, Java Web Framework, Intro (webinar #12)
Webinars
A Few Thoughts About Constructors in OOP (webinar #7)
Webinars
What's Wrong About Utility Classes? (webinar #6)
Webinars
What Fake Objects Are For? (webinar #8)
Webinars
Who is a Software Architect? (webinar #13)
Webinars
Dependency Injection Container is a Bad Idea (webinar #9)
Webinars
How to Cut Corners and Stay Cool (webinar #15)
Webinars
Why ORM is an Anti-Pattern? (webinar #10)
Webinars
Java Annotations Are a Big Mistake (webinar #14)
Webinars
Printers Instead of Getters in OOP (webinar #18)
Webinars
Smart Classes and Functionality-Poor Interfaces (webinar #16)
Webinars
The Philosophy of Bugs (webinar #17)
Webinars
Micro-management vs. micro-tasking (webinar #25)
Webinars
Who Is a Project Manager? (webinar #19)
Webinars
Gradients of Immutability (webinar #20)
Webinars
Naked Data in OOP (webinar #22)
Webinars
How to Deal With Conflicts in a Software Team (Webinar #21)
Webinars
Inheritance vs. Subtyping (webinar #24)
Webinars
Puzzle Driven Development (webinar #23)
Webinars
Veil Objects to Replace DTOs (Webinar #50)
Webinars
Xembly, an imperative language for XML manipulations (webinar #46)
Webinars
Object-Oriented Java Web App from Scratch in One Hour: ThreeCopies.com (Webinar #28)
Webinars
Why Private Static Literals are Evil? (Webinar #48)
Webinars
Aspect Oriented Programming: Pros and Cons (Webinar #47)
Webinars
Cactoos 0.12 polishing and releasing (webinar #27)
Webinars
How Much Immutability Is Enough (webinar #45)
Webinars
How to win $4096 in the next year Quality Award? (webinar #29)
Webinars
A practical example of making an object-oriented HTTP server in Java (webinar #42)
Webinars
What Is Cohesion in OOP? (Webinar #49)
Webinars
Lazy Loading via Java Lambda (Webinar #30)
Webinars
Decorating Envelopes in OOP (webinar #31)
Webinars
Synchronized Decorators for Thread-Safety (Webinar #32)
Webinars
The Alternative to Fluent Interfaces in Java (webinar #33)
Webinars
Names of objects, methods and variables in OOP (Webinar #37)
Webinars
How to Get Rid of the NEW Operator (Webinar #34)
Webinars
When do you validate your objects? (Webinar #35)
Webinars
Parsing Objects vs Parsers (Webinar #38)
Webinars
A practical example of ORM-free persistence layer (Webinar #39)
Webinars
The Power of Decorators (webinar #40)
Webinars
How many RETURN statements is enough? (Webinar #41)
Webinars
Best Practices of Exception Throwing (Webinar #53)
Webinars
How EOLANG Was Made and How to Make a DSL with ANTLR4 (Webinar #54)
Webinars
Барух Садогурский и Егор Бугаенко на Joker 2018
Interviews
Baruch Sadogursky and I talking about Java and OOP (in Russian, with English subtitles)
Interviews
Interview with David West (part 1)
Interviews
Interview with David West (part 2)
Interviews
David M. West on management, education, motivation and politics
Interviews
Shift-M/44: Allen Holub on management, motivation, and estimations
Interviews
Shift-M/45: Risk Management with David Hillson, the Risk Doctor
Interviews
Four factors of success (in Russian with English subtitles)
Lectures
Зачем программистам искусственный интеллект?
Lectures
How AI can help us, programmers?
Lectures
Выступление перед студентами ВШЭ
Lectures
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)
Shift-M
Q3: How to enforce more formal communications in a team? (by Andriy Kryvtsun)
Shift-M
Q2: What to do if the client doesn't want to pay for quality? (by Kartikey Tanna)
Shift-M
Q1: How to increase the accuracy of QA planning? (by Vladislav Voinov)
Shift-M
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
Conferences
How Do You Talk To Your Microservice?
Conferences
XDSD: management without meetings
Conferences
Chat Bots are the new UI
Conferences
Chat Bots vs UI
Conferences
Meetings Help Us and Kill Our Projects
Conferences
Meetings-free Programming
Conferences
Software Outsourcing, 10 Years Ahead (in Russian with English subtitles)
Conferences
How Teamed.io Manages Programmers (in Russian with English subtitles)
Conferences
Blame the Project
Conferences
Seven Sins of a Software Project
Conferences
Continuous Integration May Have Negative Effects
Conferences
Meetings Or Discipline
Conferences
Pre-flight Build Pitfalls
Conferences
Microservices as Chat Bots
Conferences
Need It Robust? Make It Fragile!
Conferences
Deployment Scripts Are Dead. Meet Rultor.
Conferences
Micromanagement (in Russian with English subtitles)
Conferences
Don't Be Overexcited About Amsterdam (in Russian with English subtitles)
Conferences
Problems with Chat Bots (as Micro Services)
Conferences
Chat Bot Architecture
Conferences
Eight Maturity Levels of Continuous Integration
Conferences
Practical Example of AOP with AspectJ (in Russian with English subtitles)
Conferences
Trial by Combat for OOP Honor (in Russian with English subtitles)
Conferences
Practical Example of a One-Click Release
Conferences
Seven Sins of a Software Project
Conferences
Who Is a Software Architect?
Conferences
How Do You Know When Your Product is Ready to be Shipped?
Conferences
Management without managers (in Russian with English subtitles)
Conferences
Seven Enemies of Our Motivation (in Russian with English subtitles)
Conferences
Get Rid of Experts (in Russian with English subtitles)
Conferences
Four Best Practices of Time Wasting
Conferences
How to Avoid Outsourcing Disaster
Conferences
Quantity vs. Quality (in Russian)
Conferences
Make Customers Trust You
Conferences
How to be Honest and Keep a Client?
Conferences
PostgreSQL + Liquibase + Docker + Maven + Java
Conferences
How we decide how much to pay programmers?
Conferences
Zold: Life Without Blockchain (in Russian)
Conferences
Quality vs. Quantity (in Russian)
Conferences
Who Cares About Quality? (in Russian)
Conferences
Experts vs Expertise
Conferences
How True Experts Manage Their Expertise (in Russian)
Conferences
The Future of Blockchain (discussion panel, in Russian)
Conferences
Testing and Testers
Conferences