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

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

Software devs in general seem to have a hard time with balance. No comments or too many comments. Not enough abstraction or too much, overly rigid or loose coding standards, overoptimizing or underoptimizing. To be fair it is difficult to get there.

You can read without using your inner voice if you practice. It supposedly lets you read a lot faster, though I have my doubts about how well you retain the information. One way to do it is to think “lalalala” while reading something!

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.

Interesting, yeah. I inherited a Blazor project though and have nothing positive to say about it really. Some of it is probably implementation, but it’s a shining example of how much better it is to choose the right tool for the job, rather than reinventing the wheel. For a while I was joking about setting the whole project “ablazor” until we finally decided to go back to a React/C# ASP.NET stack. If you’re thinking of using Blazor still, though, I think two fun things to look into are “linting issues with Blazor” and “Blazor slow”. I’ve heard people praise it, but they tend to be those who consider themselves backend devs that occasionally get stuck making frontends.

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

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.