Kissaki

5 with reasonable acceptance and use, even advocacy, for up to 1. I don't see a difference between 4 and 5, though.

Reviews should be the norm. Even for simple changes, a simple code change should be simple to review and approve, too. At the same time, some formatting changes or small or minimal changes with high confidence can be pushed to main without review - that'd be just wasted time and effort on the reviewer's side. High urgency can also warrant an immediate push to main, or live hotfixing on prod if possible, with a corresponding PR still open.

What do you mean by government suppression? The government suppressing entities, or you as the authorizing individual?

EU has eIDAS, and Germany has an existing working system. A certified publisher and you with your NFC phone can confirm your age above x without disclosing any other information about your identity. It runs with sophisticated cryptographic negotiation between the three parties. For you as an end user, obviously the government already knows of your existence beforehand and can serve as an authorative entity. The two other parties can then verify their validity to each other through the mutually trusted entity without revealing unnecessary information to any of the parties. Practically, the requesting entity must be certified by the state to confirm their validity and reasonable necessity of what kind of data they plan to request, and the user use their moile phone NFC and an app to read their identity document, and give explicit consent to specific data sharing.

I'm not too familiar with the specifics of what the state can see in this system. It seemed plausible to me that they may not even see that you're authenticating with a specific party or that and what you're sharing. Cryptography ftw.

Requires an account to even look at the Mermaid source of a diagram. :/

It's a tool that adds yet more complexity to our profession. More choice, more cost-benefit-analysis, more risk assessment, more shitty stuff to inherit and fix, more ability for shitty code producers to hide incompetence, more product and data policy analysis, more publisher trustworthyness and safety analysis, more concerns regarding what tooling sends into the cloud and what it can access and do locally, a significant "cheap and fast solution" you will be compared against requiring more communication, explanation, justification, new attack vectors to protect against, …

My team and some others [can] use Copilot at my workplace. I haven't had or seen significant gains. Only very selectively. Some other senior devs I trust are also skeptical/selective. We see the potential opportunities, but they're not new solutions. Some other colleagues are more enthusiastic.

What it does is make me question bad code from review request authors. Whether they missed it, are this unobservant, or incapable, or used AI. Quality, trustworthyness, and diligence are concerns anyway, but now I can't really assess how much care and understanding they actually take, if they're misled, take shortcuts, and how that changes over time - other than asking of course.

I'm not scared for my job. It already changed the field and industry, but not in a net quality productivity gain. And will continue to in one way or another. There are many parts of and surrounding software development that it can't do well.

Participating countries and territories: Angola, Argentina, Austria, Bahrain, Bangladesh, Bolivia, Bosnia and Herzegovina, Botswana Brazil, Brunei, Burkina Faso, Burundi, Cameroon, Colombia, Democratic Rep of Congo, Eritrea, Eswatini, France, Gambia, Georgia, Greece, Guatemala, Guinea, Guinea Bissau, Guyana, Honduras, Iceland, India, Iraq, Ireland, Israel, Japan, Jordan, Kazakhstan, Kenya, Kuwait, Latvia, Lebanon, Lesotho, Liechtenstein, Macao (China), Madagascar, Malaysia, Maldives, Moldova, Mongolia, Niger, Nigeria, North Macedonia, Oman, Pakistan, Palestine, Paraguay, Philippines, Poland, Qatar, Singapore, South Africa, South Sudan, Spain, Sri Lanka, Switzerland, Tanzania, Togo, Türkiye, Uganda, Ukraine, United Arab Emirates, United Kingdom, Venezuela, Zambia, Zimbabwe.

Impressive list of countries participating

Update - 13/03/2026 11:10 UTC - The Lutris creator has restored the Claude attribution, with a comment noting "Since it's such a big fuss, I'm putting the Claude attribution back".

I obviously don't know your environment, but I don't think a manager needs access or knowledge to git to effectively manage teams, hear and understand team member concerns, and to steer guidelines and guardrails.

I appreciate your comment, even when many others downvote it. Honest experiences like this provide context and should always be upvoted in my eyes.

You didn't even make any claims about effectiveness or usefulness. Downvotes like these make me sad and make me feel like this is an unwelcoming community in general, where you can't have open and honest discussions.

Some, maybe many, developers use and want to use AI even without management pushing it.

I'm skeptical and see limited usefulness, but I've also heard seemingly different sentiments from colleagues.

Seems similar to Jupyter/Polyglot Notebooks, but focused on APIs.

For context, I looked Bruno up

Bruno is a Git-friendly and offline-first open-source API client aimed at revolutionizing the status quo represented by tools like Postman and Insomnia.

Voiden lists Bruno on their comparison page as well

if I could stay later when there’s broken things in prod

In general, or on this instance?

Do you have team retrospectives? That's where I would bring it up in my team. Raise my concerns, explore and understand what team consensus is around this topic, around risks, quality, etc.

If the team consensus and/or management consensus is YOLO - then I try to protect myself from personal investment and going beyond contractual obligations. Because I already know what will come and how it will negatively affect me personally.

It's possible a honest discussion with management about goals and risks could lead to clarified guidelines, requirements, and goals. If it doesn't, I'd probably be looking for a better job/environment. Because I'll be miserable if colleagues YOLO, no matter how careful I am personally.