smashface

If AI continues at this trajectory, sure, likely to the picks and shovels.

If AI has a bubble burst, you could see a lot of used hardware flood the market and then companies like WD could have a hard time selling against their previous inventory.

Headline reads like a hot take. Actual recommendation is rather useful. Click-bait used for good.

Basically this.

If companies want people back in the office when they could WFH instead, they're going to have to compensate them, time and costs, for the commute.

Skimmed article mostly.

Could things be better? Sure. But saying we're "wasting" all this time seems a little disingenuous. How much time do people spend maintaining tractor equipment to grow crops? Or really any tools of any trade?

The equipment and tools we use let us be more productive overall with certain tradeoffs.

While that's an interesting question, legacy students likely also have access to better resources outside of the classroom and office hours.

She is literally a walking biohazard. She got her due process, lost, and then ignored the court order. From the article it sounds like she can still refuse treatment but she can't keep being a risk to the public.

Edit: And to your point about "no crime," reckless endangerment is a crime. Defying court orders is a crime.

Where do you get that 50% number? Do you mean 50% of all new code in the industry? That seems beyond extremely unlikely.

My first two internships were at an insurance company. Everyone was busy. Not saying your job wasn't what it was but I can't say it's representative of everything outside Silicon Valley.

We have a project that is basically an internal, stripped down version of CodePen and others like it. All code samples are stored in git.

The main challenge for something like our app is search. Git is good at creating files and managing versions/branches but not good at search files or their content. I'm not a git expert to fully backup that claim but that's been our experience. You can layer on your own search capabilities if you need it but then you might want to start asking if a full DB is better.

Perhaps not depressing but certainly unhelpful. If I'm spend time thinking about other more interesting stuff, I tend to get sucked into those things. Which just means I've got zero focus on stuff I need to get done.

I work on internal UI libraries that we use in our products. We updated our designs maybe 4-ish years ago and we're already getting feedback from customers that our designs look dated.

Unless you paid cash, your bank or credit card company will remember the amount for you. I don't know if most restaurants receipts are going to itemize the bill. But even if most do you can just say you went to one that didn't.

A thought I had recently was to shift from having candidates write code to have them review code. I'm sure it's not an original thought, but it comes with a few advantages. 1. Reading someone else's code is usually harder than writing your own and in most projects you spend more time reading code. You're seeing how they'd handle the more common work. 2. You can still pick how deep you want to go in the interview. Like some of the algo problems where interviewers keep adding new requirements, you can discuss API design, performance trade-offs, other code qualities. 3. You get to see how respectfully they can discuss a future colleague's work and how well they can communicate their own ideas.