Thanks so much for the explanation. As they say, when a measure becomes a target it stops being a good measure.

Relevant XKCD for good measure.

How can these businesses keep running? Storing and distributing documents isn’t exactly the most technically challenging product to build. I’m not in the field though so I’m absolutely certain I’m missing a lot of the nuances here. Can you shed some light on why you think nobody new comes along to our compete these folks?

There would definitely be a lot more art permanently lost.

// This function calculates applicable discounts given a customer's loyalty status
// STOP BEFORE SEASON 8 DEXTER PLEASE 
fun calculateDiscountRate(loyalty: LoyaltyStatus): Set<Discount> {
    // No seriously you can hide out at my place if you need to just please don't let them do it 
...

Why arrest them and then have to go through such a troublesome legal process that might not even result in a conviction?

It’s too late, we can’t contain it

Wow, it’s really hard to imagine the deep societal harm done by these five people. And you do have to imagine it because it doesn’t exist.

Outlook

Outlook (New)

Outlook (Newer)

Outlook (Newest)

Outlook (Newest final)

Outlook (Newest final V2)

That’s right! It goes in the square hole

I don’t know how to React to this.

Write down any NaN advantages of JavaScript

Yes I believe they dragged it to the wastebasket

As an aside, I fucking hate that I can’t uninstall this shit on my work Mac. I use another media player and when it’s open the media keys work fine but if I forget to open and and hit play that cursed thing just looms on the screen to remind me that I can’t get rid of it.

I believe the idea is to potentially induce a brief nasal snort possibly accompanied by a slight upward curling of the lips in those casually scrolling by. In other words, it’s a joke, being posted on a joke community.

Same here, unless it’s a small PR then I like to nitpick 👍

Yeah it is but the doc can write you a script for that.

Do you have CSS as well? I heard if you get one you probably have the other.

Peter screwed up again, dammit. We can’t afford to have any more outages or we’ll miss all our SLAs!

I think it’s pretty useful, be interested to hear your hangups with it though because it’s definitely not perfect.

If something goes wrong and I have a stack trace, that plus the type of exception will almost always be enough for me to figure out what’s wrong at least as a starting point. I’ve worked mostly with JVM languages in my career though so maybe I just don’t know how bad it actually is.

It’s a meme to say “can’t you just” at my workplace

The best code editor is the one that you enjoy using, because you’re going to be using it a lot.

This seems like a generic type of problem that could happen to anyone. Hopefully we can learn from this and avoid appending it to our already large grid of problems.

Then a year or two later you quit/get fired/move to a new team and that code is underpinning a business critical task. Everyone responsible for the code is scared to do any major refactoring because of how important it is but it seems to be working ok. Hopefully they’ll have time for a big refactor next quarter when they can afford to take some time and manage the associated risk.

Seems legit to me typeof 🎈=== "spaceship" is probably true in JavaScript after all

But can’t you just…

If you aren’t getting seg faults, are you really living?

Let’s do it for real then

In case of

Git commit

Git push origin main --force

Fire

Fortunately it doesn’t seem too deep, it’s really difficult to learn under pressure

One interesting thing I read was that commenting code can be considered a code smell. It doesn’t mean it’s bad, it just means if you find yourself having to do it you should ask yourself if there’s a better way to write the code so the comment isn’t needed. Mostly you can but sometimes you can’t.

API docs are also an exception imo especially if they are used to generate public facing documentation for someone who may not want to read your code.

Agree with you though, generally people should be able to understand what’s going on by reading your code and tests.

Well yes, you’re going to need a lot of buckets to create a lake

Very true and completely agree with your post. I didn’t mean a test in the exam sense more like a COVID test in terms of test design.

I actually think in some ways it’s a good thing to overlook the technical side to a degree as well because technical skills are generally a lot easier to teach than the people skills. Assuming the fundamentals are there at least.

An interview is just a test. Like any tests there are false positives and false negatives. There is a trade off between having more false positives/negatives and generally when it comes to hiring, a false positive is much more expensive than a false negative so many interview processes will end up rejecting good developers.

An interview can’t tell the company whether or not you are a good developer or a bad one. It can only say you can demonstrate certain skills to a certain level under interview conditions which means you are pretty likely to be a good developer.

It’s tough when you get rejections but because of the above factors, unfortunately it’s not enough to be a good developer to pass interviews a lot of the time. You also have to be good at interviewing. The good news is like any skill it can be practiced and if you’re already a good developer it shouldn’t really take much effort to become good at interviewing but it does require practice.

That’s my take anyway. Keep your head up, practice interviewing and you’ll be alright.

But they do tho…

Source: almost every developer I’ve worked with was once entry level

Not exactly programming but recently discovered Logseq and I’m absolutely loving it. Been using it for work but I kinda want to start using it for personal stuff too.

What a coincidence

What was your first girlfriend like?

error: IndexOutOfBoundsException

My perception of which side of the Dunning Kruger effect I’m on is in some kind of quantum superposition.

Completely agree, transactions are amazing for this kind of thing. In a previous team we also had a policy of always pairing if you need to do any db surgery in prod so you have a second pair of eyes + rubber duck to explain what you’re doing.