Great cheat sheet, but has a really poor quality, even when I download it. It may be problem on my side. The original on mastonon has good image quality.
Because at the same time plasma succeded kwin and dolphin konqueror, the kool naming scheme became optional. The snipping tool used to be Ksnapshot, which was at least obvious naming in what it did.
Does Merkuro mean something in another language? Like Krita means Crayon in…Swedish? Norwegian? Scandahoovian? And for some reason they didn’t call it Krayon?
Squashing is easy too, though no, there isn’t a “squash all” option, unless you’re working in a feature branch and check out master and git merge --squash branch: graphite.dev/guides/git-merge-squash
I’m sure there’s a way to commit to another branch without having it checked out, but that just sounds like a recipe for trouble.
And I have no idea how you’d manage to not have different ssh keys per user. You shouldn’t be reusing keys across accounts to begin with.
Maybe we could do like a take-a-gun/leave-a-gun kinda thing at the front door to schools to help those who can’t afford one. After the metal detectors of course.
Gun is gun, everybody gets to choose their own flavor (although those who choose small guns will be bullied by those with larger guns, thats just the natural order)
Children should be given guns and sent individually in the same forest on a moonless night. Let them figure out for themselves which course of action maximizes the likelihood of a good outcome and minimizes that of a bad one for them when they hear another kid between hiding, calling out and shooting.
I have a head full of stuff that hasn’t had time to be documented, and being a single point of knowledge isn’t job security, it’s a major risk.
My code gets documented. But so much infrastructure is just held in my head as senior SysAdmin. Wherever possible I just have a ride-along “up-skilling” (works like a RAID mirror for my brain).
I came across this early in my career in networking. I ended up having to support another technicians customer(we primarily managed our own workloads) and he did not use the tools(vault) we had to manage the network equipment credentials, so I always had to call him and ask him what the password is and why he doesn’t update it in the vault(it frequently changed) … After bothering him enough about it he said it was job security.
This was a 45k entry level job that he was years into. Why someone would want job security at the bottom part of the totem pole is beyond me, but that is where I mostly came across tribalistic tendencies(I worked in a lot of small/medium sized companies before getting a big break)
If I look up those people on LinkedIn, they’re exactly where they were or in another lateral position. They don’t tend to make it very far.
Someone should do this joke but with a pogo stick jumping in place instead of driving and a ridiculous amount of time such that they end up in the expanded sun at the end.
lemmy.ml
Active