Right, you do have to understand that either way, if you put something on the public internet, it is gone.

I don’t want a company to sell my data, making money off of me, then having the audacity to ask me for MORE money on top (nitro). It feels gross.

I don’t mind sharing bits of myself online otherwise.

The owners of federated instances can also just start selling your data too at any point. And as you said, advertisers will also just scrape public data trivially. Basically, the internet and world is a terrible place.

But Discord has cultivated a queer membership by serving a different need than those platforms: privacy.

Yeah, gonna stop reading right there. Discord is absolutely selling your data. Nothing against inclusivity features though.

Discord became ubiquitous because it works well, and is free. Take VC money, run at loss, get tons of users, enshittify, die because something better becomes good enough. It’s just another one of those speed runs, which will happen over and over again until the end of humanity.

I enjoy it, started playing recently! All the fun for me is in trying to find good loadouts completely on my own. I don’t want to watch some YouTuber show me the absolute maxed out best loadout, because that’s the entertainment to me. Progress is slow, I still haven’t cleared the game lol, but when I do, I know it will be my own choices that got me there. No shame in researching how to win if that’s your thing, I just love diving into games like this blind.

The JetBrains AI plugin wants to be activated so badly, but legal says we can only use GitHub copilot. The copilot plugin is really good so I don’t mind, but we all know the data is going to OpenAI regardless of the plugin. Data sovereignty will only be achieved by running these services locally.

This right here. Get good at navigating code of questionable quality that you didn’t write. If you can’t do it, start questioning your tools, and mastery of those tools. For the big boy jobs, you should be working with existing code much more than writing new code. Learn to get excited by tweaking existing systems with a few well placed, well researched changes, instead of being The Asshole that adds a new abstraction wart.

To me, a corporation cannot maintain quality code because requirements are ill defined, and there is no “done” state. With those two conditions present, unable to be changed, it’s not possible to form a coherent codebase. Those who try will make things worse, because their abstractions won’t fit in a year or two.

This is exactly the “messy code” people then leave behind. Bad code can come about for other reasons too, of course, but this is one of the more annoying reasons, because someone wrote it with self-righteousness, as if they were the only people to truly SEE the problem. Sigh.

It’s fine, this is how enterprise works. You can learn to navigate and make a living from it. You MUST internalize and accept that it is NOT the same as maintaining code for an open source library or whatever people think it’s going to be.

You have to listen to your heart, at least once in your career, to learn that grass on the other side is covered in just as much dog shit as it is over here.

deleted by creator

Isn’t it that horrid ugly fucking foot

Read… instructions? I love teaching people that git very often prints out what you should do next.

git: “to continue, resolve conflicts, add files, and run rebase —continue”
dev: …time to search stack overflow

All that said… just use lazygit. It does help to know CLI git first to put things in context, but if you do, no need to punish yourself every day by not using a UI.

fzf? https://github.com/junegunn/fzf

Out of the box, would only help searching shell commands that have been run, so for files, things like “vim file.txt”, which is obviously not usually how files are edited (you’d use the file browser in a text editor or IDE)

However if you find a way to list all files on your system by modified time, you can pipe it to fzf for a slick fuzzy find search.

Maybe ag would work here too: https://github.com/ggreer/the_silver_searcher

This song always gets turned up when it comes on, so good

Debugger good for microscopic surgery, log stream good for real time macro view. Both perspectives needed.

Aw gee guys we are soooo sowwyyyy that we hurt your feefees

deleted by creator

YAML comes with its own unique pains in the ass https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell

These things actually matter, come up often enough to actually be annoying, and are a bit difficult to explain and learn into people. You’re basically fine if you just string quote everything that you can, but nobody does that.

MULTI-TRACK DRIFTING!! Which also kills the other lever guy, bonus!

These would actually make for a very hilarious tournament of sorts…

Would be funnier if it was just “JS” on the right, because obviously HTML and CSS are involved too, but JS is where all hell breaks loose

The encryption: base64 encoding