𝙲𝚑𝚊𝚒𝚛𝚖𝚊𝚗 𝙼𝚎𝚘𝚠

https://github.com/TheArchitectDev/Architect.Identities

Here’s the package one of our former developers created. It has some advantages and some drawbacks, but overall it’s been quite a treat to work with!

At the company I work at we use UUIDv7 but base63 encoded I believe. This gives you fairly short ids (16 chars iirc, it includes lowercase letters) that are also sortable.

https://hackaday.com/2024/05/03/google-removes-risc-v-support-from-android/

Strange, it’s the exact opposite for me. Moon in dark mode, sun in light mode.

It’s happened in the past and is easier than you might think.

Anti-authoritarian can lead to difficulties in coordination with other teams. I’m not saying it has to, but it can.

Not doing something unethical from a moral standpoint makes you a good person, but not necessarily a good employee. But in the vast majority of cases engineers aren’t presented with morally dubious tasks.

Not doing what you’re told because you think you know better is also anti-authoritarian, and definitely would be considered a bad trait to have for an employee.

Team coordination is now being hostile to employees?

Who do you prefer, someone who:

• Thinks critically about his assignments
• Communicates concerns with his coworkers
• Can intelligently express his reasoning
• Is open to being wrong
• Helps improve a product

Or someone who:

• Thinks critically about his assignments
• Creates alternative designs that they feel are better
• Builds those designs despite this not being instructed
• Creates beautiful software, which ends up incompatible with the other software it needs to work with because they didn’t consider various requirements from other stakeholders
• Causes delays and frustration because their stuff, nice as it is, isn’t to spec and needs to be rebuilt

You can be a brilliant developer and a terrible employee at the same time. If you want to design software as you like it, you should be in the design sessions. And not ignore the hard work those people already did and throw it out without discussion.

Anti-authoritarianism is a bad trait. Critical thinking and standing up for your ideas is not. I frequently question design decisions I have not made myself, because A) there could be something that was overlooked or B) I’m overlooking something and I don’t have a full picture of the scope. Either should be resolved by a quick chat with the designers, not by me ignoring instructions and doing whatever I feel like is best.

Part of being a good developer is also accepting that you might be wrong and your ideas might be bad. That doesn’t mix well with anti-authoritarianism.

It is if you’re the one trying to coordinate multiple product teams and one of them doesn’t build to spec, introduces different behavior in edge cases or declares something to be “not their responsibility”. Anti-authoritarianism is a bad trait to combine with “being wrong”.

Someone who wasn’t present during the design meetings, stakeholder calls, planning sessions etc… can absolutely still have very good input regarding decisions that were made. But they should raise those concerns with whoever made the final designs and discuss them, not decide on their own to deviate from the given instructions. They may not see the full picture and cause a ton of delays that way.

David_Edmundson - KDE Developer

Don’t create a social media hype of something before discussing it with Plasma devs. That’s obviously going to antagonise people, and puts us in an awkward situation afterwards.

Looks like this “vote” is not really official and blindsided the devs a bit.

Given the sheer amount of Steam users, it’s still not a bad increase.

Yes, I’m aware. But with 12 people you can’t simply divvy the groups in threes constantly, because if you weigh and the groups are unequal, then you don’t know in which group the different person is (yet). E.g., weighing ABCD - EFGH can tell you the different person is in IJKL if the groups are even, but if they’re uneven you don’t know in which of the other two groups the different person is.

I mean that not knowing it is part of the question, and the proposed solution doesn’t work without knowing if the person is heavier or lighter.

If you know if the person is heavier or lighter, the question becomes trivial.

You don’t know if the person is lighter or heavier yet.

I’ve tried both but always find myself just opening new windows instead of using split panels. I find it to be more convenient personally.

https://blog.horner.tj/how-to-kinda-download-more-ram/

Already been done.

Try taking a break for a month and see how much you actually remember. In my experience it was depressingly little, and I’m not generally bad with languages at all.

OpenTTD, OpenRCT and OpenRA are all great!

It’s because there’s not enough people in the EU actually using it.

Generally the programmers that visit these kinds of websites, let alone participate in a survey, are the enthusiast programmers who are much more likely to be interested in exploring a new language in the first place.

There’s a considerable potential for a selection bias here. Not that this disproves the survey, but generally these kinds of surveys tend to be a little bit ahead of the curve, so to speak.