If you consider yourself a fan of Elegant Objects paradigm, don't hesitate to add your name and the name of your project to this hall of fame! :) Instructions are at the bottom of the page.

As I told you earlier, I'm one of the organizers of a new SPLASH workshop, called Beyond Code: No Code (BCNC). The submission deadline has just been extended for a few days. You still have a chance to submit your paper there. All papers will be published in ACM Digital Library. If you have something relevant to NoCode trend, don't hesitate and submit right away!

A new post on my blog about Prestructors.

I just released a new ZIP archive with Java classes from 1000 open source GitHub repositories and 15 metrics measured on them, here (692Mb). This dataset can be used for research and analysis of Java code on a large scale. There is still not enough metrics, though. Would be great if you can help and develop more of them, here is the list of issues that need help.

Let me remind you about the chat groups where you can meet me:

* @elegantobjects on object-oriented programming and EO
* @zerocracy on remote work and freelancing via Zerocracy
* @polystat_org on EOLANG, 𝜑-calculus, and Polystat
* @bloghacks on tech blogging and software engineering
* @zold_io on Zold cryptocurrency
* @painofoop об ООП по-русски
* @szdne о политике по-русски

You are welcome to join all of them.

In the next four months I'll be presenting a series of 16 lectures in Innopolis University, for the 3rd year of BSc, on-site. The topic is "Software Systems Design" (OOP, UML, requirements, design patterns, formal models, testing). I will record all of them and publish on my YouTube channel (don't hesitate to subscribe right away, to not miss them).

I'm planning to interview Jeff Atwood, the co-founder of StackOverflow and #1 software blogger in the world: codinghorror. What would you ask him?

M174: Your personal goals must be much more important for you than your project and your team's ones. Of course, the team will try to make you sell your soul to them, but you must not forget about your long-term objectives. Watch it.

New post on my blog: Logging in Unit Tests, a Bad Practice

M175: Say you are an architect, and your customer or a product owner asks you to explain your technical decisions, you may immediately jump into explanations. Don't do that. There must be a clearly drawn line between your territory of responsibility and authority and theirs. They define requirements for the product you develop, you make technical decisions according to the requirements. You don't need to explain anything. Watch it full on YouTube.

Hey, we are making a lecture about formal semantics in programming languages. It starts right now, in Zoom. Join in! (in English)

Here is the video (just uploaded): https://www.youtube.com/watch/v2ztCZIpQ-3E

Just published a new Shift-M/48 podcast interview with Jeff Atwood, the co-founder of StackOverflow.

Just published the first lecture on software design, at Innopolis University, for 3rd BSc year: 73 minutes (in English).

The second season of Narcos: Mexico is even better than the first one. Less about shooting, more about management of a crew.

Хорошая новость: мы наконец созрели для продолжения наших Object Thinking митапов в Москве, посвященных объектно-ориентированному программированию в его "правильном" элегантном виде. Следующий пройдет 30-го сентября в арт-кафе Creative Diaspora (три минуты от метро Чистые Пруды), начало в 19:00. Регистрация обязательна, здесь. Как и в прошлые разы, будет вкусный ужин, но количество мест ограничено, регистрируйтесь поскорее.

Будет два доклада: Эмиль Фаталиев о том как избавиться от DTO в Spring Framework (30 минут, по-русски) и Егор Бугаенко о том, как сделать DTO не такими вредными (30 минут, in English).

Today at 8pm (Moscow time) you can ask me any questions you want in this live YouTube video. We did it once, a few month ago. We'll do it again today and will try to do it regularly from now on.

A new Sunday Twitter poll for you.

M176: Very often, as far as I can tell, programmers are not willing to participate in digital discussions (tickets, chats, boards) because they are afraid of bullying: their decisions may and will be criticized without any predefined rules. The solution is simple: make sure your team has a structured process of decision making, with explicit roles and permissions. Watch it.

The second lecture (out of 16) from my course about software design was published just now.

We just published our first interview with an author of emerging open source project, here. We will continue recording such interviews, if you your feedback will be positive. Thanks to Ilya Sher for telling us about his NGS project.