BougieBirdie

That’s why they call it the graveyard shift

This bird is getting ready to kick him in the dick.

They’ve been given a lemon and they’re choosing violence.

So if the average nap is four seconds, the average period of wakefulness is five seconds.

What a life.

Weirdly, I thought years. Like these were elves or something.

I’ve been playing too much D&D, I need to spend some time in the real world.

A lot of the criticism comes with AI results being wrong a lot of the time, while sounding convincingly correct. In software, things that appear to be correct but are subtly wrong leads to errors that can be difficult to decipher.

Imagine that your AI was trained on StackOverflow results. It learns from the questions as well as the answers, but the questions will often include snippets of code that just don’t work.

The workflow of using AI resembles something like the relationship between a junior and senior developer. The junior/AI generates code from a spec/prompt, and then the senior/prompter inspects the code for errors. If we remove the junior from the equation to replace with AI, then entry level developer jobs are slashed, and at the same time people aren’t getting the experience required to get to the senior level.

Generally speaking, programmers like to program (many do it just for fun), and many dislike review. AI removes the programming from the equation in favour of review.

Another argument would be that if I generate code that I have to take time to review and figure out what might be wrong with it, it might just be quicker and easier to write it correctly the first time

Business often doesn’t understand these subtleties. There’s a ton of money being shovelled into AI right now. Not only for developing new models, but for marketing AI as a solution to business problems. A greedy executive that’s only looking at the bottom line and doesn’t understand the solution might be eager to implement AI in order to cut jobs. Everyone suffers when jobs are eliminated this way, and the product rarely improves.

It’s always fun when a relative admits they don’t care about your child’s safety.

My guy stopped growing them and raised turtles instead,

I wish my resume looked that good.

The kill command allows you to specify which type of kill signal you want to send. -9 sends signal 9 or SIGKILL, and we’re sending it to pid 1.

That would force kill systemd, which I just have to assume will send your computer to a crashing halt.

The echo command is writing "c" to a file at /proc/sysrq-trigger which I don’t really know how it works but this suggests you’ll “crash the system without first unmounting file systems or syncing disks attached to the system.”

I haven’t installed fuck so I’m not sure how that works

A hammer is beginner friendly, but learning to use a hammer doesn’t necessarily mean you’re ready to build a house with it.

Well, I’m not a psychologist, so I suppose my interpretation might not be correct - the irony mounts.

But from the graphs you shared, it looks to me like the only people who underestimated themselves were the top performers. And from what I know firsthand with imposter syndrome, a competent person underestimates themselves.

I used hyperbole for effect, so I don’t think that if you believe you have zero competence in something because you actually have zero competence means that you’re secretly good at something. If you know nothing about plumbing, don’t try to install a toilet.

But if you’re working in the software factory then you don’t actually have zero competence, you probably have formal education and some experience. Having that feeling that you might not be good enough is a sign that you’re on the right track.

I felt like that early in my career. I used to think that being a rockstar developer was a good thing, and I’d be happy to describe myself as one.

The thing is, a lot of rockstars are really just churning out heaps of unmaintainable code. They think they have a high degree of proficiency, they’re confident in their competence, but there’s a disconnect between what they think and what they produce.

It can be a sign of personal improvement to question yourself when you think you’re doing great. We owe it to ourselves to ask ourselves critically if we can be doing better. Because if we don’t, and we just assume we’re awesome, then we’ll happily churn out sub-awesome cruft.

The insidious thing is that self-criticism leads to self-doubt, and imposter syndrome can be quite paralyzing. But if you learn to control your criticism instead of allowing your criticism to control you, you can achieve higher heights than rockstardom.

Based on what I know of Imposter Syndrome and the Dunning-Kruger effect, it seems you’re at your most competent when you feel like you’re at your least.

So if you’re feeling badly because you feel like you don’t know enough to do your job, take some time to remind yourself that other people who appear to be confident have no idea what they’re doing.

It’s fake-it-till-you-make-it all the way down.

I’m definitely writing useless git commit messages

For work, I at least include the Jira ticket id

For personal stuff, it’s sweeping features stuffed into one commit that barely describes what was changed