353 karma · joined April 18, 2013
• Someone with a lot of money wants to get U.S. residency.
• They set up or work with a shell company that “hires” them under the H-1B program.
• That company uses part of their payment to win the visa auction.
• Once in the U.S., the “employee” does whatever they want — the job is just window dressing.
This is essentially what’s happened in other visa categories when money alone becomes the main filter.
Based on the photos, they measured this as the distance from the surface of the edge to the surface they were dropping it onto.
But for the vertical egg drop, the center of mass is several millimeters higher than for the horizontal drop, a pretty significant difference when you're only dropping 10mm at the most.
Maybe I'm missing something, but based on how they set up the experiment, maybe they're not measuring how resistant the egg is in certain positions, but instead just measuring that higher potential energy is more likely to break an egg?
> San Francisco formally adopted demand-based pricing for curb parking in 2017.
> The result was a rare win for San Francisco governance: We know from pilot areas that implementing demand-based pricing reduced congestion and parking citations while speeding up transit and increasing overall sales tax revenue. The program is now widely regarded as a model for parking management.
The SFpark program was by all accounts a huge success, and the areas where it was implemented feel a lot better off - you can actually find parking when you need it, and traffic isn't as bad there. I would love to see it put in place in the Sunset and Richmond - those areas are almost entirely free parking, and have the worst parking in the city.
RMSE of proposed rounding to closest is 17.5 seconds.
The new method is roughly 17 seconds more accurate on average.
Does this reduced error make a significant difference? Probably not. There are very annoying practical issues with this proposal though.
Rounding down makes it clear what minute has already passed. If your clock says 3:00, you know the current time is definitely some point after 3:00. If something needs to happen at 3:00, and your clock says 3:00, it is time to start.
With this proposed method, 3:00 could mean anywhere from 2:29:30 to 3:00:30. When do you start? Do you start as soon as your clock says 3:00? Then you're starting 30 seconds early. Do you wait until your clock says 3:01? Then you're starting 30 seconds late.
And how do you set a clock that uses this scheme? If I want to set the clock to 3:00, do I wait until 2:59:30 and then set the clock to 3:00?
The headaches that arise from this scheme are not worth the trivial error reduction.
Sonic focuses their fiber services only in areas that are most profitable to install fiber. As far as I know, they only install fiber on telephone poles that have free space, in areas that are high density. The cheapest install option for the highest possible revenue. I live right next to an area that has Sonic fiber, but there's no telephone poles, and an install would require an expensive underground installation. As a result, my area isn't even on their roadmap for future development.
If you're outside the areas covered by their fiber service, Sonic feels it's still perfect fine to charge $50/mo for a 50 mbps asymmetrical DSL connection.
Even assuming all your developers are magically given a solid understanding of the new code, all remaining velocity will be entirely consumed by bugs and incidents. No more feature development will occur.
You could try to grow to outrun the code debt you've just acquired - but that's what literally every start up tries to do, and less than 10% succeed.
The most likely outcome is that the company would enjoy a one-time massive feature feast before slowly dying over the course of 5-10 years or so.
Great if you're a founder looking for a quick exit or some other position that is super focused on short term growth, I suppose.
Of course modern architecture is just going to look bland, generic, and low quality compared to old architecture - there's only about 10% the effort put into it.
Creating an unsustainable pension system solves nothing. The only real solution is to root out the causes of unsustainable cost of living and address them. But doing that is far more difficult than just giving out "free" money, and gets almost no recognition from voters.
Any system that intentionally pays out significantly more than people pay in is going to have sustainability problems.
It's so bad with the California pension systems that they're facing immenant collapse, despite being in an economy with the highest growth rate in human history.
Not a lot of civilian uses require anywhere near that speed or accuracy.
It's a lot harder to justify grossly inaccurate geographic data as not hurting civilian uses.
Like, if the problem you notice is 7,500 pound vehicles designed to kill pedestrians, isn't the logical solution to anyone with a functioning brain to propose restricting those vehicles? What kind of lead paint eating logic does it take to conclude that the best solution is to get rid of bike helmets?
Don't waste your time playing political games and undermining incompetent management trying to "fix" massive organizational rot from the bottom up. Your reward is going to be negligible at best relative to your effort, and it's more likely you'll be punished instead. Go start your own company, or work for a small company where you can make a massive and positive difference - and get massively rewarded for it.
I have a suspicion that you're not putting the source for the specific versions of glibc and Linux you used into every one of your projects.