lennivelkant

For the right jobs, it's a good tool.

This isn't the right job.

Sounds like they did the lookups by hand actually

cries in data analyst

Did you know our company is over a thousand years old, possibly even two? Recent dives into our digital archives have unearthed invoice records dated to the year 1021, though we're also investigating the validity of one dated to 215.

Whoever decided to make dates a manual entry text field without validation should be forced to write SQL by hand, without syntax highlighting, autocompletion, syntax checks, reference or looking up stuff, querying a database with no schema or data dictionary.

Well, it's ""This"", not "This", so I'd say it's fine.

I share your hope. I'm just offering the caveat that it might not go as quickly and smoothly as you expect (unless I'm reading your comments wrong - do correct me!)

It's my perpetual gripe with many of those open tools that I love ideologically, but practically find lacking in some respects, typically UI/UX (including the pre-experience of the decision whether to use them). I don't have all the skills or knowledge to fix the issues that bother me, as it's often far eaiser to know what's wrong than how to fix it.

I understand and endorse the philosophy that it's unfair to demand things of volunteers already donating their time and skills to the public, but it creates some interdisciplinary problems. Even if capable UX designers were to tackle the issue and propose solutions or improvements, they might not all have the skills to actually implement them, so they'd have to rely on developers to indulge their requests.
And from my own experience, devs tend to prioritise function over form, because techy people are often adept enough at navigating less-polished interfaces. Creating a pretty frontend takes away time from creating stuff I'd find useful.

I don't know if there's an easy solution. The intersection between "People that can approach software from the perspective of a non-tech user", "People that are willing to approach techy Software" and "People that are tech-savy enough to be able to fix the usability issues" is probably very small.

It's so big that it can take a lot of bleeding before it dies. It doesn't help that there is no significant enough consensus yet on an alternative.

It seems like some people are flocking to bsky, probably because it has better visibility and seems more accessible than Mastodon ("What's an instance? How do I pick?"). Others are heading to Threads just because it's there already.

If enough people move to some other platform to generate a critical mass, they'll pull others too. Until then, inertia will keep X rolling a good while to come.

I prefer Mastodon to what is ultimately still a for-profit corporation ("public benefit" notwithstanding), but both are better than Twatter.

The value of distributed redundancy

For the elites: conserve their hierarchy and the structures that enable the gradual accumulation of power in the hands of the few.

For the rest: conserve their place in the hierarchy and the comfort of the familiar.

Hourly wages for school teachers? I'm worried I might know the response, but does prep work outside school hours, in breaks etc. count as hours worked?

Linux in general and Arch in particular are kinda laissez-faire in that they'll allow you to shoot yourself in the foot. Some distros may put barriers in your way, others practically hand you the gun, but at the end of the day, the gun is freely available and it's your own foot that you're shooting.