Is it 13? I bet it’s 13. Bloody thing keeps making trouble.

An individual would risk corporate lawyers lobbing suits at them they don’t have nearly enough resources to fight. In that way, it’s much like other forms of activism: individual actions are easily singled out and retaliated against.

If a ton of people were to do so, however, they might have an impact. Either the registrar would have to take steps to limit who can submit them, which might conflict with some laws, or they’d invest a great deal of resources trying to sort out the legit ones. Trying to single out people for retaliation is hard when there’s enough of them. In this way, too, it is like other forms of activism:

There is strength in numbers. There is power in unity.

If, hypothetically, someone were to coordinate such actions in the style of a crowdsources DDoS, and they could get enough participants, they might get away with it.

I’m thankful I don’t do software dev (I did two years as a working student, that was enough), but working in Data Engineering / Analytics* doesn’t make things better. I’ll overengineer the database, ETL and reporting, define a dozen measures I’ll never use, prepare a dozen ways to slice and view the data I’ll never look at and build a whole data warehouse I’ll never look at.

Eventually I remember that it exists, realise that I’ve answered all my questions by directly querying the database, except for “What am I running out of?”, which I answer by looking in the cabinet because I never update my inventory anyway.

*I don’t even know where the line is anymore and how much of my responsibilities is on either side of it

“6 for the beer, 9 for the longdrink, 4.20 for the water… That’s a total of 694.20 please.”

He uses a pencil, paper and a mechanical calculator to tally up the bill, which I absolutely understand when your career is in IT.

When the alternative is either having to search, evaluate, compare, select and configure an application for that purpose that you’re never quite happy with, or to scope, design, develop, test, deploy, maintain, eternally find things you wish you’d done better, refactor, realise you’re spending your free time on doing more of your job, regret your life choices, resolve to only make this last improvement and then call it good enough, renege on that promise to yourself a week later, burn out, curse that damn app for ruining your hobby…

…yeah, using the most trivial low-tech solution possible does look rather sensible.

My new data structure:

Given a heuristic for determining data quality, it homogenises the quality of its contents. Data you write to it has pieces exchanged with other entries depending on its quality. The lower the quality, the higher the rate of exchange.

If you put only perfect data, nothing is exchanged. Put high quality, you’ll mostly get high quality too, but probably with some errors. Put in garbage, it starts poisoning the rest of the data. Garbage in, garbage out.

“Why would you want that”, you ask? Wrong question, buddy - how about “Do you want to be left behind when this new data quality management technology takes off?” And if that doesn’t convince you, let me dig around my buzzword budget to see if I can throw some “Make Investors Drool And Swoon”-skills your way to convince you I’ll turn your crap data into gold.

I think it’s a symptom of the age-old issue of missing QA: Without solid QA you have no figures on how often your human solutions get things wrong, how often your AI does and how it stacks up.

ActiveSheet? Please no

As long as nobody starts, not playing is the easiest way to avoid defeat. But if one player plays, the rest must follow or lose. And as long as either keeps playing, neither can stop. That is the tragedy of war: Easy to start, hard to end, until the fire runs out of fuel and only ruin is left.

The only way to truly win in war is to never fight.

If you have a choice, that is.

I love þat you’re trying to bring ðe þ and ð (back) into English.

To be fair, seeing a complex equation simplify down to a concise result is kinda hot 😳

I find myself repeating some version this sentiment every now end then: There are good reasons to hate (whoever the conversation is about), but this ain’t one. We don’t need to grasp at straws when there are solid branches.

Bribe them with snacks. Source: Am IT. Have been bribed with snacks. You can bet that user got priority treatment from that day on.

I recently went and replayed the DLCs of AC3 and Odyssey, which I’d quit for various reasons. Particularly in the case of Odyssey, Open World Fatigue played a role: I couldn’t be arsed to explore everything anymore, but neither could I bear to leave anything open.

I decided to just go for the missions, to not worry about over optimising my choices, to not worry about cleaning out every little question mark and chest and finishing every location. I finished them, enjoyed my time and found new freedom in not having to draw out the maximum amount of game time for my money.

I’ve twice now gotten a position without prior knowledge of the tools in question. I think a lot is just taking a gamble on your ability to learn as you go - which clearly worked out in your case.

I had my start with Python, albeit as a kid and I didn’t actually understand too much about the principles at the time. Still, I think that was a good place to start learning about the concepts of instructions and variables.

I learned more about the ideas underpinning it all later, and most of my understanding came when actually working in software development on a live and in-development codebase. I think that’s a good progression: start small, then learn some theory just so you’ve heard the terms once, then try to make sense of actual code using that.

Edit: definitely work on some goal though. Don’t code in a vacuum, think of something small you want to achieve and learn to do that.

Ooh that’s a good one

Me no word good 😄
Nah, you’ve got a point, my brain is just fried these days. I definitely need a vacation.

I was supporting your point. I forget that comments are seen as counterargument by default.

But you’re right, my comment would have been more useful in reply to the other person.