deploy595

Chaotic Exploration Phase in EventStorming

Chaotic Exploration is the first and most energetic phase of an EventStorming workshop. The goal is to get all domain events out of people's heads and onto the wall as fast as possible — without filtering, ordering, or debating.

Setup

• A long wall covered with butcher paper (or a wide whiteboard)
• Orange sticky notes (for domain events)
• Markers for every participant
• No laptops, no chairs — everyone stands

deploy595

Great, I now have a clear picture of the pattern across your Jobs. Here's my analysis.

---

Yes, you are doing it right

Your understanding is accurate. Looking across the Jobs in your project, they all follow the same template:

1. Accept primitive IDs (not Eloquent models) as constructor arguments — serializable for the queue.
2. Guard — re-fetch the entity from DB; if it's gone, log and bail out early.

deploy595

AI в разработке ПО: опыт российских компаний

Дата исследования: 25 февраля 2026 Формат: по компаниям — как, результаты, выводы, планы, подводные камни.

---

Контекст: масштабы внедрения в России

По исследованию State of DevOps Russia 2024, 44% российских компаний уже используют AI для разработки и тестирования ПО, 47% отметили положительный эффект на эффективность работы.

deploy595

\033[XXm
30 black             90 gray
31 red 		         91 bright red
32 green             92 bright green
33 yellow            93 bright yellow
34 blue              94 bright blue
35 magenta           95 bright magenta
36 cyan              96 bright cyan
37 white             97 bright white

deploy595

Install, start and enable:

  apt install firewalld
  systemctl start firewalld 
  systemctl enable firewalld

Make sure the file /etc/docker/daemon.json does not contain this line. If it does, delete/comment it. If the file is missing, it is OK, you can skip the step:

{

deploy595

# Two SQL queries. One built using ActiveRecord, the other - manually assembled.
# Both return the same result.
# Each table has 500 thousand and a million records respectively (Ticket has many Messages).
# The first query works 10 times slower.
#

# 1) Active Record
# 130 rows retrieved starting from 1 in 645 ms (execution: 635 ms, fetching: 10 ms)
# 130 rows retrieved starting from 1 in 623 ms (execution: 611 ms, fetching: 12 ms)
# 130 rows retrieved starting from 1 in 640 ms (execution: 631 ms, fetching: 9 ms)