The ability to hold laweyers accountable not a panacea. In this instance most competent lawyers are going to still give conflicting good advice and charge for it.
Because truly the answer boils down to "it depends" and many people will take it many different ways and not be "wrong". Publishing anonymously is a good choice, publishing publically and complying with a removal order is a good choice, not publishing is a good choice.
"Good" here being somewhat sound in that it likely wont cause the person publishing a huge life changing issue.
That’s what I meant. There should be error bars to reflect uncertainty of the inherent data, but they should wait until all the data that could change things comes in rather than using projections which always drastically change
> If the error bars are large, that is important information to know.
The data is available. If it were important to the causal reader, however, then those casual readers would have already demanded its presence. But they don't care. What difference does it make to Hilary Homemaker? She just wants to get to say "Did you hear about the bad economic news?" when gossiping with her friends.
Those who need to understand the uncertainty will already be looking at more than a news headline anyway.
What decisions are so important and time sensitive they depend on these numbers right after a month is over? And also we at one point were making decisions without these numbers yet the quality of the decision making isn’t clearly improved.
A few months of extra no data won’t impact the stock investments if no one has that data. Startup funding is similarly not so time sensitive.
As for businesses hiring, they should hire based on their own growth. Using an external signal that itself gets adjusted drastically is similarly problematic; I don’t hire because I think no one else is hiring and the numbers get majorly adjusted up. Similarly I hire a bunch of people and it turns out no one else hired.
No one benefits from faster numbers that are majorly shifted in a few months anyway. You wouldn’t make any different decision if no one had the numbers. The only thing you’re doing differently is when the numbers come out your gambling whether or not you think the true number will be revised in some major way in a few months. That’s not helpful for the economy writ large.
I thought about this as well. The dsytopian world I think will exist in the future where the Waymo is priced higher and people will want to take it more, over a cheaper Uber. Precisely because the human driver is removed from the equation.
So yes, I think they will be able to turn a profit by charging more for the experience. Which is a humanless car.
So, uh, you don't really tip your Uber drivers much then do you?
Right now, Tuesday 3pm, Waymo will cost me 13.76 cross town. UberX 10.95, Lyft 11.95. If I don't tip Lyft/Uber they'll be cheaper but I definitely don't tip the Waymo.
This article to me also implies that there are some potential issues with large Spec based development flows, which I haven't been able to pin down lately.
Specifically, having agent implementation drift from the Spec.
I have run into the same problem, and started calling the phenomenon vision drift.
I noticed that the issue tracker I built was well suited to address this problem, as it handles board time-travel. So a simple command like ":replay 4h" gives you a clear overview of how the workflow has evolved over time, and you can checkout previous states at will.
Drift is huge between any large spec and agent implementations.
I've done a ton of testing and the model doesn't matter, fable or sol still miss a ton of detail and drift.
I'm building http://engine.build which closes the gap and makes sure the implementation matches the spec.
It's not the same as the satisfaction you get when solving complex problems with code yourself but writing clear specs and thinking through the problem is still very satisfying to me.
I agree. I am not sure why they dont "just" wait until all the releases are ready before publishing and give a 14 day "deadline to publish" instead of a potential security vulnerability.
I understand wanting to get things out ASAP. but two weeks is not the end of the world to wait as a consumer of professional software packages.
Because truly the answer boils down to "it depends" and many people will take it many different ways and not be "wrong". Publishing anonymously is a good choice, publishing publically and complying with a removal order is a good choice, not publishing is a good choice.
"Good" here being somewhat sound in that it likely wont cause the person publishing a huge life changing issue.
reply