As someone who works with typescript daily, you’re not wrong. It’s an extremely overcomplicated glorified linter that tries and mostly succeeds in catching basic type errors. But it also provides false confidence when you concoct something that shows no errors but doesn’t behave how you expect.

At least until it gets direct dom manipulation and multithreading…

I had one of those that was grandma-owned but the transmission shit the bed within 5k miles. What a pos.

I understood what he was talking about instantly… but only because I did the same thing with the brake when I was a kid.

I had a viscous reaction, if ya know what I mean.

3Blue1Brown on youtube has amazingly good visual explanations for various math concepts. Helped me out a lot when I was having trouble with calculus. It doesn’t help specifically with memorizing theorems or anything, but provides a good conceptual framework to start with. https://www.youtube.com/c/3blue1brown

There’s nothing quite like the unique pain of navigating an unfamiliar codebase that treats abstraction as free and lines of code in one place as expensive. It’s like reading a book with only one sentence per page, how are you supposed to understand the full context of anything??

They probably got stuff done, just not the things you left half implemented code for…

Maybe the word “audit” is incorrect? If they didn’t provide you any guidelines, I’d definitely recommend asking. But it’s possible they’re just looking for your perspective on best practices and possible improvement ideas, more like a general code review.

If you’re not being sarcastic, why limit yourself to only one thing? If you’re working on some amazing UI with tons of CSS animations and a full audiovisual experience, and it takes intimate knowledge of everything frontend, I guess it would make sense. But if you’re just making internal CRUD apps, I don’t see a reason why a given domain is special enough to have its own job title.

I think it’s a complement. We’re not in the dark ages anymore where you had to be intimately familiar with each target platform and have different people who each know everything about their little part of the stack. Nowadays it’s feasible for one person to be productive in devops, database, backend, frontend, etc. because so many people have gone to great effort to get us there. I personally get a lot of enjoyment out of being able to stand up an app by myself without necessarily needing to work with six other teams. That way we can have an actual vision for an overall user experience rather than getting caught up in compatibilities and discussions of ever changing best practices.

Depending on the software, you still get to think about garbage collection!

I’m pretty sure you could buy one of those with a straight six, I bet they’re even more of a dog!

I have basically the same story, except it was one of my actual friends on Steam asking me to rate their CS:GO team. I fell for it since I was trying to be nice, and luckily changed my password before they could turn around and use my account for the same thing.

Just an anecdote, but I’ve definitely eaten those bad boys after several months. I’ve never been led astray by just checking for mold and giving it a sniff.

I’ve already left, but seeing them marching towards an IPO makes me even happier with my decision. I just fear that the mountains of helpful troubleshooting and advice on Reddit will be locked away forever soon, while the rest of the web falls to SEO and AI-generated nonsense text…

E plumbus unum

I use Vscode with markdown preview, with a git repo. The only downside is that Windows incessantly wants to group instances of an application, so it’s hard to keep my notes separate from my coding stuff.

Just ordered a copy!

This is the book that started it all for me 5 years ago. Now I'm a software engineer!