All my switches are unicellular and ceiling fans and lights are their fan hubs as well. Over a hundred devices and it generally just works.
69 karma · joined April 10, 2012
All my switches are unicellular and ceiling fans and lights are their fan hubs as well. Over a hundred devices and it generally just works.
Note: I’m not forming an opinion on it or saying to use or not use it, was simply curious because I hadn’t heard of it.
Then when it wrapped up very nicely I felt like I was bad at my job. "Wait, how did they fix it so fast!?!" (hyperbole here but it was sort of a gut punch)
However, the core tenets were valid from a general approach. My fear when reading was the potential to go overboard. We have all met over-zealous scrum masters. Same could be applied to a lot of the stuff they were essentially transferring from manufacturing to development and more specifically devops.
Given the recent debacle with the airpower lack of a launch date I can't help but not really trust that this is going to come out in the fall...much less "what" is coming in the fall.
Not saying that the employees are to blame but I'm sure there's plenty of good ideas out there that just don't have the right people trying to implement it.
Or that's such a small amount that it really doesn't contribute.
Really just wondering what that number is.
It seems very un-Amazon of them. They clearly have the metrics to track this so I'm shocked they aren't diverting or doing something to fix the problem, whether that's incentivizing slower shipping or using other carriers (I realize the carrier deals they have are very complex and affect a whole load of other data points).
It's just odd to me that consistently the Amazon delivery service is what is being used and that it's consistently bad/delayed/etc.
The last one that was delayed was delayed for 2 days. I contacted chat and apparently it was because they couldn't get into the mailroom and were waiting on delivery instructions.
I don't know from whom, because I was never contacted.
Poor performance isn’t typically a “bad thing” in this sense. For instance, if someone went and pissed in the coffee pot, they would be fired. If a big group of people were simply told to not come in anymore it’s laid off. Tesla specifically said this wasn’t laying people off so I’m not sure how that works.
I don’t know if there’s any legal or contractual grounds for one or the other but I’d guess it would matter what state you’re in.
I know for a lot of states collecting unemployment benefits does require some sort of reason for termination that is related to the above distinction.
I didn't get the feeling that was the Sun business model, but I didn't follow it super closely.
There are clearly scientific ideas that we take as simple truths now that will be disproved in the future. They are clearly going to be a little more nuanced than planetary motion but it's great to see how the scientific community has and will evolve.
Trust me, I've had similar things happen. I don't know how there can be security auditors who don't even understand how password encryption works but I've had to explain it a few times. It's awful.
In all honesty, if you have a well designed system it's pretty good at what it does. I've used it without any issues on small personal projects and it was great at what it did. Although getting it to work with Postgres is needlessly "complicated". Not complicated per-say but not as easy as it just working with SQL Server.
What happens when you take a legacy system and move over to .Net and try to use EF on a poorly architectured data model? Chaos.
"Oh you want to search for orders that have these attributes that are stored in a bit-encoded string field that is only joined from 3 different tables?"