Jonathan Ballet

18 Followers
77 Following
93 Posts
Site Reliability Engineer at Camunda
Build, break, recycle (not necessarily in that order)
我也是喬納森

The systemd project is under attack by a trolling campaign orchestrated by fascist elements, accusing it of implementing "age verification".

I wrote more about the facts on my blog: https://blog.bofh.it/debian/id_473 .

systemd has not implemented age verification

We played "Kanagawa" last night, it's a very cute game with beautiful artwork and a simple mechanism. The game finishes quickly and is good to finish the evening gently :)

My only grips are the rules which are not super clear at first glance (several small details could have been made clearer regarding the turn order and how certain cards interact with scoring). Also, it's playable with 2 people but is a bit limited ; I think it should be a better experience with 3 or 4 players.

#boardgames

Get started with me & Kestra.io

New job (!!!), so let's learn orchestration with Kestra.io together

DEV Community

Time for a brief review of Daybreak the board game.

This is a collaborative board game for 1–4 players - you win or lose together. It’s by the people behind Pandemic, if you ever played that. In this came, you each lead a different world power in the fight against climate change.

1/5

We played our second game of "Zhanguo: The First Empire" last night. I personally like the theme very much, the game is very cute, but oh god it's tricky to build your engine correctly. Winner got 171 points, I finished with 127 🥲

I will play again, but I still need to understand how to win. Solo mode is well done too! (But check the online solo FAQ at https://boardgamegeek.com/thread/3246284/ first!)
#boardgame

"I’m in charge": called a meeting because they're in charge and they can. The meeting has no objective, no agenda. The meeting exists to reaffirm their ego or allow them to exert power over people by forcing them to show.

"Feedback": management calls everyone into a room and asks for “real, honest feedback and corrective criticism.” Crickets.

"Blamestorming": something has gone wrong and finger pointing ensues instead of working on the issue. Feelings are hurt. People are fired/quit

7/x

"Hide the elephant": a meeting to solve a problem, but no one wants to discuss THE glaring issue at the time, and people actively steer the conversation away if the subject is brought up.

"Gaslightathon": a Q&A session where all bad recent events or actions of the leader sitting there are positively spun, and anyone disagreeing "simply misremembers"

6/x

"Information dump meeting": a meeting where a person provides a lot of detail about some topic; the topic might be very important, but fundamentally, it should have been an email instead

"The pre-game huddle": it happens before some other larger meeting where information is presented. This meeting represents a lack of trust by the one calling it in the preparation done by the other people, and generally has one person drilling everyone else on the information already previously prepared.

4/x

"Bloated working session": originally formed by 2 or 3 people actually doing work and solving a problem, these meetings drag every single person into a room one-by-one or call a large meeting with all the people there because they don't know who all they need

"Just in case": an expression of someone’s belief that a meeting will somehow solve a problem that may exist in the future. When the meeting comes, no one will recall why it exists or what problems we were concerned about

3/x

"Online Postit Confetti": the meeting devolves into the exercise of every feature of the new whiteboard software being used. Bonus points if consultants are involved.

"Rumor mill": mainly gossiping about other people in the company while supposedly doing something else; it wastes time and sucks morale.

"Talk show": this is a meeting where a small set of people 2-5 talk amongst themselves and have a good time while the rest of the organization is meant to sit and listen

2/x