The 15th lecture (out of 16) is published, about coupling, cohesion, and some other metrics of software design.

New post on my blog: Calibrated Achievement Points (CAP). It's an answer we found to a very challenging question: How can you measure productivity of an R&D team? We give every member of the team an opportunity to earn points by making achievements and presenting them to the team. Read the blog post, it explains the details.

As you probably know, during the last few months I gave 16 lectures about Software Systems Design to 3rd year BSc students of Innopolis University (Russia). All lectures were recorded (some of them not with the highest possible quality of sound, unfortunately) and published on YouTube in this channel. The slides you see on the screen were made with LaTeX, their PDF versions are here, the sources are here (feel free to use for your own lectures).

It was a very interesting experience for me. I was doing this for the first time (I had single lectures before, but not a full course). The main lesson I've learned: it's a very hard job — being a teacher. Coding is much easier :)

M179: 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. Watch it.

17 years ago David West in his book Object Thinking coined the term objectionary, which he suggested to make a factory and a dictionary of all objects. Just recently we implemented his idea, at objectionary.com. No surprise, all our objects are EO objects. Here is a summary of the entire development-and-deployment pipeline for this new centralized curated repository of objects: Objectionary: Dictionary and Factory for EO Objects

Two open source projects, which we develop for the last few years, need Java developers: Artipie and EO. It's a part-time and fully remote type of work: you don't need to be at any meetings and you will never visit the office. Moreover, you will be paid fixed-price only for the tasks you finish, in the best traditions of XDSD. We expect you to be an expert in Java and familiar with open source development culture (we will check your GitHub and StackOverflow profiles). Text me directly, if you are ready to try: @yegor256.

We just published a webinar about EO, conducted by a team at HSE University, who is helping us develop this new experimental programming language. Watch it: 37 minutes.

M180: 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. Watch it.

I finished a small library eo-files, consisting of EO objects for Input/Output. It is deployed to Objectionary and can be used as simple as this:

[] > app
  memory > mem
  copied > @
    as-input.
      file "/tmp/test.txt"
    memory-as-output
      mem
    1024

This snippet reads the content of a file into memory. There are other objects, that help making directories, reading/writing files, deleting them, etc.

Let me remind you, here is what you can do if you believe in better object-oriented programming and Elegant Objects in particular:

- Add your name to the fan list at elegantobjects.org
- Join @polystat_org chat
- Join @elegantobjects and @painofoop chats
- Buy Object Thinking book
- Buy Elegant Objects books (vol.1 and vol.2)
- Contribute to eo and polystat (give them GitHub stars!)

The objective is to demonstrate that OOP could be a much better programming paradigm than what we have with Java or C++. We are also looking for volunteers in our R&D projects: text me if you need a good research topic for your MSc/PhD study.

A new Sunday Twitter poll for you.

M181: 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. Watch it.

M182: 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. Watch it.

Can someone please endorse me on arXiv for "cs.PL" category? My code is: UEAAY6

I Don't Feel at Home in This World Anymore (2017) — a pretty good comedy with an idea. I've enjoyed watching. Also maybe because I love Melanie Lynskey from Two and a Half Men (my favorite sitcom).

Next Friday, I will be speaking at EngX Z-Day 2021 (online). First time will share an event with Uncle Bob. Don't miss it. It's free, but you have to register.

Новые новости черно-белого айти: https://youtu.be/NLNVkvnrr3Q

M183: 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. Watch it.

Good Time (2017) by Benny Safdie (also playing the retarded brother) is probably the most intense criminal movies I've seen recently. You won't stop watching it.

A new post on my blog: https://www.yegor256.com/2021/12/01/teaching.html