Hey, I released debate, a new LaTeX package, which helps you organize a discussion between reviewers right inside your document:

\documentclass{article}
\usepackage{debate}
\begin{document}
I think apples are tastier
  \debate[Jeff]{I don't think it's true!}
  \debate[Anna]{It is indeed true!}
than pears!
\end{document}

This should be very convenient when a few people are working with the document, for example in Overleaf. The discussion will be visible (marked with red color) and can easily be removed everywhere in the document with the package option: \usepackage[hide]{debate}.

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

N10: Новый выпуск черно-белого айти. Здесь.

Сегодня вечером, в 19:00 по адресу Мясницкая 24/7, стр. 3 (метро Чистые Пруды) мы проводим наш очередной Object Thinking митап. После перерыва в полтора года мы решили продолжить! Два доклада (Эмиль Фаталиев и Егор Бугаенко), вкусный ужин, книги и футболки с кактусом в подарок, и общение с сотней фанатов и хейтеров ООП. Вход свободный, нужно лишь зарегистрироваться здесь.

After two years delay, I just released a new version of Qulice, an aggregator of style checkers for Java (Checkstyle + PMD + SpotBugs) shipped as Maven, Gradle, and Ant plugin. This style checker is used in all Java projects I work with. I highly recommend you do the same. This new version 0.19.0 is compatible with Java 17 (just checked).

By the way, there are 200 issues in the backlog. Maybe you can help fix some of them?

And, yeah, one more thing. Don't forget to give it a GitHub star, if you use it and/or like it!

Оба видео с докладов на нашем шестом митапе (Object Thinking, Moscow, 30 September 2021) опубликованы: Emil Fataliev (32 мин) и Yegor Bugayenko (37 мин). Оба доклада были о паттерне Data Transfer Object (DTO) и его порочной сущности.

English subtitles are coming.

The 11th lecture (out of 16) from Innopolis University is published, about microservices and RESTful APIs.

The 12th lecture (out of 16) from Innopolis University is published, about serverless design in cloud.

The 13th lecture (out of 16) from Innopolis is published, about test-driven development.

The 14th lecture lecture (out of 16) is published, about test patterns and anti-patterns.

I will speak at Merge conference in Innopolis, on the 13th of Nov. My talk will be about SIMBA, the management framework we use in a few R&D projects of ours. If you want to attend, I have a promo code for you, to get a 15% discount.

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.