The library hadn’t had any updates in 2 years before this. Clearly it wasn’t maintained. If you’re a user and bothered by this super edge case “vulnerability”, fork it and take on the responsibility yourself.

Again, you’re putting words in my mouth. I’m done engaging with you as I don’t think you’re conversing in good faith.

No one said anything is beneath senior employees.

It’s a lost opportunity when you, a staff engineer, spend your time doing something that a junior engineer could do – instead of doing a task a junior engineer can’t do.

It’s faulty, short-sighted logic though. If every company trained juniors, only for them to jump ship in two years, there’d be a pool of trained juniors to hire from. Yes you wouldn’t get your investment out of that particular person, but you’d be hiring someone else’s investment.

Beyond that, there’s work that is better suited to more junior employees because it’s literally a waste of the senior employees’ skills.

Too many industries are shitting on entry level employees now… They’re easy targets for layoffs and easy targets for AI, apparently. Now they’re already complaining about the lack of quality talent.

The Great Resignation is effectively over. We’re now in the Great Talent Stagnation, where employers’ biggest concern is the lack of qualified applicants

If you don’t invest in the next set of entry-level employees, you won’t have the next set of qualified employees.

Strong names are great, but (sometimes) mentioning the type of variable in the name is redundant.

“Monday”.length is working JavaScript and does equal 6. No print command afaik though.

100%

I program – yet I’ve been asked to fix a camera and Apple Maps.

They mean jank:

jan·ky adjective, informal adjective: jank

of extremely poor or unreliable quality.
"the software is pretty janky"

The things that make me a good programmer:

1. I read error messages
2. I put those errors in Google
3. I read the results that come up

Even among my peers, that gives me a leg up apparently.

While we resourced mozilla.social heavily to pursue this ambitious idea,

How many people do you need to administer a Mastodon instance? I’m pretty sure infosec.exchange is like one dude.

The go community is strongly opinionated in unique ways. For example, using libraries is generally frowned upon. You either use something included in the language itself (standard library) or copy/paste the code you wrote in another project. There’s also advocacy for shorter variable names which generally seems counter to the normal “write descriptive variable name” mantra.

All in all, I hope the ideas / opinions came from a good place and then some people took them as black & white rules. But they also come off as one or two people’s pet peeves who got to build a language around them.

I’m going to have to print out the Go version for all future “it’s idiomatic” and “but the community!” debates at work

Just add them. You’re a developer and automated testing is one of our tools. A woodworker wouldn’t ask permission to sand.

These people don’t even read their own literature. The Catholic church’s ban on alchemy is about falsely claiming something is a valuable metal in order to pay for debts. It has nothing to do with the occult – the ban was because it’s a sin to lie / cheat / steal. A saint is even on record saying that alchemical gold is ok if the end if product is real gold.

With that context, of course God doesn’t give a shit if you use SQLAlchemy as long as you aren’t using it to defraud people. If you were defrauding people, it wouldn’t matter what tool you used.

.

I use Firefox full time but I’m bummed at the number of sites that break in odd ways when not using Chrome. As an engineer, I understand how appealing it is to only have to test in one browser, but this monopoly is the result.

Turnstile was announced over a year ago.

Sending passwords via email Will compromise any passwords sent via email.

100%. But that is a different problem and a different attack vector than storing passwords in plain text for authentication. When reporting security issues, it’s important to be precise.

DHH is a contrarian. Any benefits of the cloud he might get are overridden by the fact that he needs to be different (and blog about it).

See his stances on Typescript, workplace inclusion, TDD, etc.

I too want my query results in an object, but thankfully libraries like sqlx for golang can do this without the extra overhead of an ORM. You give them a select query and they spit out hydrated objects.

As far as multiple DBs go, you can accomplish the same thing as long as you write ANSI standard SQL queries.

I’ve used ORMs heavily in the past and might still for a quick project or for the “command” side of a CQRS app. But I’ve seen too much bad performance once people move away from CRUD operations to reports via an ORM.