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!
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.
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...
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 wrote a json prettifier a couple months ago with just a couple lines of code. I thought it would take a while but ended up taking like 10 minutes.
Just ordered a copy!
That's a shame, I love that book.
When you really want the floor to be lava.
Might need some evidence of this one!
It's my birthday too! Happy bday!
Infinite Jest, especially the sections surrounding the boarding house. Its strange mix of exaggerated reality and absurdness really made me question and rebuild a lot of my ways of thinking.
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.