drgath

That sounds amazing. Off-by-one disasters, time conversion problems, imperial instead of metric messups. Halt and Catch Fire & Mr Robot were great. We need more like that, and less like CSI:Cyber.

Have we yet deviated from FDIC rules? I don’t think so, even with what Yellen says. My limited understanding of the situation is that the assets to cover everything is there, they’re just tied up in long-term treasuries.

From the FDIC’s site:

> As of December 31, 2022, Silicon Valley Bank had approximately $209.0 billion in total assets and about $175.4 billion in total deposits.

For simplicities sake, let’s just assume 100% of the assets are actually there, but it’ll just take varying years for everything to mature. So, what’s next? FDIC finds a buyer for the assets, perhaps a private bank or a a pseudo-government body who has the ability to wait till maturity, and in the meantime, everyone gets all their deposits. That’s not a “bailout”, and is following the rules.

ctrl+f “yql” and landed here. Was an amazing service for its time. Could even execute server-side JS in its engine (Rhino). Certainly the only E4X environment I ever coded in.

Asking someone to spend $400+ just to upgrade equipment in order to support a service that doesn’t work well on the original equipment you sold them, takes some guts.

In 15 years as a professional software engineer, I’ve never worked somewhere that wasn’t heavily using IRC, Hipchat, or Slack. The conversations are identical, the only thing that has changed is the service being used. As previous poster alluded to, your complaints aren’t a Slack issue, it’s a co-worker issue.

To the same degree? I disagree there. I would never expect a full-stack engineer to be more proficient at front-end when compared to a FE specialist. You are expected to know some, but not to the same degree. That’s the reason they are specialists, in comparison.

They’re about to IPO. Doesn’t mean they’re profitable, but it does mean their finances are healthy enough that they can be publicly traded.

> Being overworked is an excellent reason to hire. It shows that you are about to lose your team due to burn-out or extended sick leave.

I took the original comment to imply that when employees are overworked, it is due to a failure in planning to assure a project is adaquately staffed from the beginning. That is when you should hire, not because you just began to notice you failed to plan appropriately.

Sure, if someone is being overworked, hire to spread the load (if new person can ramp-up fast enough). But don’t put your employees in that position to begin with, because some of them won’t return to full productivity, even after you resolve the problem. Overwork for any duration comes at a cost.