The picture was slow to load for me, and I expected Beanie Babies or some kind of precious metal or BitCoin.
Have you considered turning it into a paint ball arena?
It probably wouldn’t be a good investment, but it would make a great story.
I’m a developer, so my chances are pretty good. But I take your point.
Even if I weren’t, there’s enough software options out there that I don’t have to pick between paying for proprietary software and living with abandonware.
So I think the need for this security is exaggerated.
Of course. I used proprietary software for a long time. Having things I relied on get abandoned got old, but it worked.
I just expect more from most of my software, now.
It’s funny that Ouya’s brand recognition is so infamous that no additional explanation is needed.
I’m happy to pay for software, but I want more than just permission, I want long term security that my investment in the tool will last.
If IntelliJ would open source their oldest versions, I would make my boss buy me a copy of the newest version every year.
And to every other bidder, too, of course.
The comics kind of address this:
Killing the holder of the Infinity Gauntlet usually results in someone equally bad picking it up.
So just killing Thanos often isn’t a complete solution, after the stones have been gathered.
Another tip I haven’t seen yet:
It varies by client, but Markdown generally works, here.
Spoiler tags seem to still be a separate extension from regular Markdown.
Many of us try to be more careful to include ALT Text with images, as it supports both blind users, and anyone whose server is just being slow to load images:
Example of Image with Alt text in Markdown:
Here’s one I haven’t seen mentioned yet: many of us explicitly state our intended tone after our comments, to avoid miscommunication. Particularly in busy threads.
We have some great accessibility outreach communicators here, some of whom have shared how much it helps them or people they know.
Some examples:
Sometimes these are abbreviated, but we often even avoid abbreviation - for general clarity, but probably mainly because we’re always gaining new users who might not recognize the abbreviation.
This is a great point.
There’s also very convenient block mechanisms for rude folks, and a “block and move on” culture for those who don’t keep their communication civil.
I can explain this chart: SO and AI both give me questionably useful example code, but AI isn’t as much of an asshole about it as the average SO user.
The time you “save” in the beginning, you’ll have to use it later to rewrite the code to do what you intended in the first place.
Docker Compose brought “works on my machine” to the cloud.
The issues should be central, but it would be nice for my reputation as a contributor to migrate between instances.
Needs more chains and walls between groups in the top picture. And maybe some ransom notes.
(This is more to try to make you laugh, than useful feedback, sorry. I don’t have a very good idea how to actually include these concepts in a simple diagram.)
That’s a great way to handle it.
I like to pass them the ticket and schedule the next open hour on their calendar for them to teach me how to do it, if they’re a developer. Sometimes they do, because I was genuinely missing something easy. Usually they get to awkwardly discuss why they don’t have it done yet, either.
When the person isn’t even a developer, I’ll explain the usual process between developers, and give them a chance to beg their way out of it.
If they don’t beg off, I schedule them anyway and see if they can actually at least “rubber duck” me through the problem. (Sometimes it even works.)
I’ve had a couple peers discover (or rekindle) their love for development this way. Most just make up a reason not to make the meeting, though.
Don’t feel bad, this place is weird. It’s a good weird. But weird.
ain’t none of us are all that bright.
If I ever get a bumper sticker, to announce my views to the world - you’ve given me the words for it. Thank you.
They worked well for us
Yeah. I used story points successfully for years.
After learning about the above data, I asked my team to trial just counting tickets for velocity, and it also works fine.
The outcomes weren’t noticably different, so now we just don’t spend the couple hours each sprint that estimating story sizes was costing us.
My team was hesitant to give up story point estimation, because they didn’t want to give up the communication with leadership about which stories were XXL.
So we kept using the XXL issue tag, but dropped the rest of the estimation process.
this isn’t Twitter
But this is Mastodon (for some of us).
Lemmy and Mastodon share content, now.
This new nerd Internet is weird, but it’s weird in cool ways.
I would welcome a utility that makes it easy to find donate links for my software packages, based on my Apt, Flatpak, and F-Droid package lists.