Was wondering, if female Canada geese look different from males,and apparently they’re just slightly smaller, but Wikipedia has some excellent info nonetheless:
The honk refers to the call of the male Canada goose, whilst the hrink call refers to the female goose. The calls are similar but the hrink is shorter and higher pitched than the honk of males.
Yeah, I imagine that they did try. But it’s not just the intentionally misleading announcement post, they also have 5(?) different subscription tiers, which get different changes from this. And one of the subscription tiers is actually called “Pro+”, so that does not mean “Pro and more expensive tiers” like I wondered. And they have this ridiculous intermediate currency to make things even more confusing.
Their offering itself is overly complex and confusing…
This image showed up in my feed as pure black and I thought that’s the shitpost, that it’s just all censored. 🫠
Man, they couldn’t have communicated this more confusingly, if they tried.
Which is a crime, by the way, when you sell it together with a product you hold a monopoly for: https://en.wikipedia.org/wiki/Tying_(commerce)
So, did they use AI tools to type “LGTM” 400 times or nah?
But yeah, I also find that frustrating. Management just looks at terrible metrics like PRs closed or lines of code produced.
It’s not even novel that you can produce terrible code very quickly. Decades ago, our industry learned that it isn’t worth it, because you suffer for it later. Now the game is altered slightly and management demands that we throw all these learnings out the window.
Well, base prices stay the same. They seem to just be billing more per usage on top of that…
Personally, I found it worth playing around with. I cared less than I thought where I had to move my eyeballs to, once I didn’t have to make the decision anymore.
And automatic tiling can also enable workflows that just don’t make sense with manual tiling, for example master-stack-layout where basically one window takes up half the screen and the other windows share the other half, and then you swap out which one’s the big window as you see fit.
But I also wouldn’t have written all that, if I didn’t have a way that you can easily try it out: You can add automatic tiling into KDE Plasma via Kwinscripts. Personally, I’m using Krohnkite: https://store.kde.org/p/2144146
(Easiest to install by going through the System Settings…)
Thought it said “She run off with a porch thief”. Would’ve been a very different story…
I live in the year 2026, I’m pretty sure, and this still made so little sense to me, that I assumed they meant “hacking a water fountain” as in hitting it with an axe.
Retirement is more of a synchronized event, because folks generally retire around the same age…
I find a gameplay goal more important than a story goal. Sandbox games like Luanti are tricky for me, because I need to decide what to do with no real reason to do anything. But if a roguelike tells me “There’s an artifact at the bottom of this dungeon. Good luck!”, that’s already more story motivation than I need, because the gameplay goal is straightforward.
I also find lots of story motivations terrible to begin with, though, when it’s basically “You’re the hero! Go save the world!” and then the gameplay is just genocide. I don’t care, if we’re violencing pixels, but specifically the attempt to justify this violence, is almost always distasteful.
I think, lots of players would like to communicate with game devs, but you’re rarely told how to do so…
Yeah. Perhaps also somewhat of a subverted expectations thing. The dog is portrayed as not even understanding pointing, but as soon as food is involved, it understands the transaction 1 cane = 1 bone very quickly.
If there’s no reason to hold the feature code back (i.e. its integration doesn’t break anything), then it’s much easier for development to ship the feature and disable it with a feature flag. Otherwise, you have two versions of the code, which means changes need to be integrated in both versions, which is largely just pointless busywork.
For what it’s worth, when we say we do TDD in my team, we write a singular test case that fails, then we implement the production code until the test case works. Then maybe do a bit of refactoring to make it all work nicely together, and only then you start with the next test case.
Writing swathes of unit tests upfront sounds absolutely mad to me, for the reason you state. But also because you do need an API to test against. You can’t write a unit test in complete isolation, pretty much by definition. You can often do so for integration tests, but you definitely don’t want to put all test cases into integration tests, as that increases complexity massively…
I mean, even then, they could increase the price per token, if they want to hand out fewer tokens for the price paid.
They could make this work like a prepaid SIM card, where you charge it with e.g. $10 and then you can use it until the $10 are used up.
Instead, they make it work like in-game currencies in scammy free-to-play games. Except that they didn’t choose a confusing conversion rate, for some reason…