re: Those silly mistakes we all make VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Ah, the nightmare of a misspelled constructor. It's there, it's just pretending it's a regular method. Cheeky. And hard to track down. 😡 What are ...

These days I work mostly in Go, but even in languages with constructors I struggled with them enough that I now recognize a misspelled one sooner.

Programming has helped me discover that I truly never learned "I before E except after C". I'm always misspelling the BadgeAchievement model in the dev.to codebase.

As a Canadian I occasionally have hangups with keywords like color. Phil, you probably feel this too.

That's why we have postcss-spiffing.

body {
  background-colour: grey !please;
}

Top Tip!

Rename the BadgeAchievement model to BadgeAcheivement and never have this problem again!

I'm sure there are things like this in the code already 😭

Unrelated, but my last job had a referrals-based business model, so you can imagine the referrals table in their database was the most important table with indexes on almost every other table in the database.

It was spelled referalls, and every table apparently has its own convention of whether to name their column referall_id or referral_id 🤦‍♂️

I once fixed a misspelling in a codebase without realizing that the name was coming from an external API's response so my correction broke everything. Misspellings that you can't fix are very frustrating.

@yechielk At least that's just in one app and not the Referer header supported in every web browser and server in the world.

Come to think of it, I bet the Referer header has caused multiple spelling confusions leading to things like this.

@halldjack Oh no! You must have thought you were fixing a bug instead of causing it. That's the worst!

Yes! Someone pointed out the referer header to me once, and I instantly felt better for the poor developer who created that referalls table...

code of conduct - report abuse