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.
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 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.
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…
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!
This is the book that started it all for me 5 years ago. Now I’m a software engineer!
That’s a shame, I love that book.
It helps people relax and feel good, basically. In a similar vein, there’s no informational content in a sitcom and yet they continue to be made. Some people enjoy crocheting or playing guitar hero, even though they might not be learning much from them. Personally I like a good blend of entertainment and education, but I also don’t really try to justify to myself why I might enjoy one person’s videos over another’s, it might even come down to the voice or some other entirely subjective factor really.
Idk, I don’t see a problem with saying a new language is unintuitive. For example, in js I still consider the horrible type coercion and the “fix” with the triple-equals very unintuitive indeed. On the flip side, when learning C# I found the multiple ways of making comparisons to be pretty intuitive, and not footguns.
Nothing like trying to make sense of code you come across and all the function parameters have unhelpful names, are not primitive types, and have no type information whatsoever. Then you get to crawl through the entire thing to make sense of it.
Might need some evidence of this one!
I did, I was in high school at the time and I had just discovered Firefox. I remember it was a while before it was possible to have nested replies. Before Digg I think I just used StumbleUpon. Good times!
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.