For a long time I tried, but one day I just decided to focus on the hobbies I care the most about. I dumped a lot of time into software for my career, then kept up with bass guitar practice and dirt biking. All the other hobbies are things I might pick up if I have a surplus of time, but I've accepted that I'll never go that deep into them.
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.
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.
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 don't speak C, but isn't this an extreme simplification of the issue? I thought memory could be abused in an almost infinite number of subtle ways outside of allocating it wrong. For example, improperly sanitized string inputs. I feel like if it were this easy, it would have been done decades ago.
Nothing wrong with being an EMT who does all those things as hobbies, unless the capitalist pigs to whom you sell your hours demand more than their fair share...
I've had many other jobs and few experiences in them have been as humbling as programming. My favorite is trying everything to fix an issue then realizing the problem is that you're pointing at the wrong database or running the wrong branch.
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.
I often interact with people who don't like something but haven't used it before, so I'm definitely going to steal your term "informed dislike" to distinguish between those cases and ones that are legit gripes.
I unironically use this one all the time, because it captures both sentimental and practical value for me. I just compare the thing itself with the joy of having that much more clean empty space.
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.
Yeah! I think I still have the exact same tastes as when I was a kid. I always wanted a dirt bike and now I have one, and I always wanted a fast computer with a good sound system, which I now keep relatively up to date. Maybe my kid self would be disappointed that I don't have a fast car though!
Suddenly I need to order a lot of explosives...