I too have forgotten to memset my structs in c++ tensorflow after prototyping in python.

I don’t think either is actually true. I know many programmers who can fix a problem once the bug is identified but wouldn’t be able to find it themselves nor would they be able to determine if a bug is exploitable without significant coaching.

Exploit finding is a specific skill set that requires thinking about multiple levels of abstraction simultaneously (or intentionally methodically). I have found that most programmers simply don’t do this.

I think the definition of “good” comes into play here, because the vast majority of programmers need to dependably discover solutions to problems that other people find. Ingenuity and multilevel abstract thinking are not critically important and many of these engineers who reliably fix problems without hand holding are good engineers in my book.

I suppose that it could be argued that finding the source of a bug from a bug report requires detective skills, but even this is mostly guided inspection with modern tooling.

Maybe it depends on how or when you signed up. I never gave a cell number and I can use 3.5.

It depends on what you are trying to do… There are many tunnel / reverse proxy routing services like https://www.cloudflare.com/products/tunnel/

Here’s a list https://github.com/anderspitman/awesome-tunneling

You can also get a super cheap vps, do some ssh reverse tunnel magic and go along with your day.

I didn’t say JavaScript… and I certainly wouldn’t choose TS for a personal project because I personally feel that its organization is terrible but I would choose TS over vanilla js for work projects because it does produce better group work and is easier to maintain long term because of the structure imposed on it.

Some people think better with typing information explicitly written out. Some people don’t. In my opinion it is a creativity thing. Some people like to make art that is photo realistic, some people like to make abstract art.

I understand both viewpoints. In my free time I vastly prefer late bound, dynamically types languages with robust reflection engineers built into their interpreters. For work, I heavily prefer late bound, strictly typed with reflection optional or minimal.

Different people think differently.

Hey, I marked only one jira with “Works as intended” for only one of the big reports related to it, thank you very much.

I was headed in the wrong direction for weeks

Oh boy. This comic brings back the horror of leftpad being removed from npm and how it felt like half the internet fell apart.

We have been doing some new pair work processes to expand group capabilities (and to train up some juniors) so I am happy to report that I got to share this with two whole people.

Documentation? 🤣😭

That’s part of why it took so long. Every day I thought I was done a new person would be added to the review and they would identify a security and/or use case edge case.

😅 Mine ended up being only like 50 lines or so total. Complex, pervasive, data coupling with security concerns and my own ignorance were the primary drivers for the time taken on this one.

One of my favorites is the fast inverse square solution.

It’s like Fermat’s Little theorem: meh, this is easy fuck you.

The rest of the world: what in the ever loving fuck is going on here? How in the… Jesus Christ… How did you?!? What is this black magic??? What part of your soul did you sell for this?

And yet, somehow there is still a bug in the datetime implementation.

Self documenting code is infinitely more valuable than comments because then code spreads with it’s use, whereas the comments stay behind.

I got roasted at my company when I first joined because my naming conventions are a little extra. That lasted for about 2 months before people started to see the difference in legibility as the code started to change.

One of the things I tell my juniors is, “this isn’t the 80s. There isn’t an 80 character line limit. The computer doesn’t benefit from your short variable names. I should be able to read most lines of code as a single non-compound sentence in English with only minor tweaks and the English sentence should be what is happening in most of those lines of code.”

Sadly only the compiler will know the true value of my constexpr forLove;

Perl, no wait you said without arcane syntax…

Java doesn’t have to declare every error at every level… Go is significantly more tedious and verbose than any other common language (for errors). I found it leads to less specific errors and errors handled at weird levels in the stack.

Exceptions don’t exists and ask errors must be handled at every level. It’s infuriating.