I got pulled over and the cop found a 1/2 gram of pot in my car (a very small amount), which ended up with me having to do community service and take regular drug tests. I was working as a line cook at the time, but being forced to stop smoking weed gave me the push to finally apply for an entry level manufacturing position at a local company who does drug tests. Years later I still work there, but as a software engineer, and attending online college. I wouldn't quite say I'm grateful about the ass backwards drug laws and invasive drug screening, but I really can't argue that my current situation is a lot better than it was back then. Without that event, I might still be working random entry level jobs.
The Navidson Record from House of Leaves, although it's questionable whether it is supposed to actually exist within the narrative.
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
I've been rewatching Aqua Teen Hunger Force and Space Ghost, and they hold up (if they were ever funny for you to begin with)!
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 all look like it's just a matter of time till they shred the side of your torso or take a finger.
They probably got stuff done, just not the things you left half implemented code for...
I hit the "wake on lan" icon on my phone, since my computer is in a different room from my monitor and the usb doesn't work for waking it up directly. But if I could, left ctrl all day!
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.