yegor256 podcast

yegor256 podcast

By Yegor BugayenkoTechnology
Download on the App Store

yegor256 podcast episodes

  • M97: Let your followers be your best censors helping you think more logical
    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
    6 min
  • M96: Freelancers are a pain, but they are your only hope if you want the quality to go up
    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
    7 min
  • M95: Only lazy and immature programmers are afraid of penalties and punishment
    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
    7 min
  • M94: It is impossible to make a full-timer deliver results, unless they want it
    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
    7 min
  • M93: To become a good programmer you have to find a project that rejects your mistakes
    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
    6 min
  • M92: We in Zerocracy use Boost Factor to help architect motivate programmers
    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
    6 min
  • M91: Full-timers want to look smart, freelancers want to deliver results
    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
    5 min
  • M89: Deliver your trust continuously, not discrete
    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
    6 min
  • M90: RUP is a framework, Agile is a philosophy; just like Zerocracy and XDSD
    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.
    8 min
  • M88: If you are working on a prototype for longer than two weeks, you are doing it wrong
    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
    6 min

About yegor256 podcast

From the publisher's feed

Software developer at Huawei, founder of Zerocracy, author of Elegant Objects, creator of Zold

More shows like yegor256 podcast

Moscow Python: подкаст о Python на русском by MoscowPython

Moscow Python: подкаст о Python на русском

5 Listeners