While I worked at Google I once searched for "//this should never happen" in the code base.
It was in there.
A lot.
707 karma · joined April 10, 2013
twitter.com/danciruli (dead) @danciruli@hachyderm.io
It was in there.
A lot.
Once you learn woodwoorking, you're going to be good at it (until you lose strength, flexibility in your fingers, etc).
In our industry, to 'stay at the same place,' you continually have to learn new technologies, new concepts, etc.
One thing that amazed me about babies was how early they understand line drawings. Long before a baby can talk, it knows what a dog is (and can imitate a dog sound), and can also identify a dog in a photo, in a realistic drawing, and in a very simple line drawing.
It seems so easy, but in reality those things all look so very, very different. And after 6ish months, babies have mastered that recognition.
I meant it's not normal to start selling a feature in 2016 and delivering it in beta seven years later.
According to the linked article: "Ms. Izurieta departed the Company on October 1, 2022. The Company initiated discussions with Ms. Izurieta about a transition from the Chief Risk Officer position in early 2022. Accordingly, the Company and Ms. Izurieta entered into a separation (without cause) agreement pursuant to which she ceased serving in her role as Chief Risk Officer as of April 29, 2022 and moved into a non-executive role focused on certain transition-related duties until October 1, 2022."
Typically (in the past) both client and server have been VMs or containers.
Client side it can do things like automatic retries, routing decisions and fault injection (among others). It's super useful.
What this adds is the ability to deploy it as a client in more places...a couple of billion more places!
If they want to try to be appealing to, say, 7/7ths of the developers out there, they might want to do something different.
What if someone had a code of conduct that was clearly about people treating each other well...but started it with "First, you must acknowledge that there is no God." Or "First you must acknowledge that Mohammad is God's messenger." Or "First you must accept the mitzvot as binding." Or "Brahman is Truth and Reality."
None of these is promoting inclusion.
That said: I'm an observer here. I haven't chosen to participate or not participate in the SQLite community because of this. I simply think it's a strange place to promote one's religion, and it doesn't surprise me that non-Christians might find it unwelcoming.
Assuming I end up generating 8 MWh per year, I'll use that number along with an expected lifetime of, say, 20 years. So: lifetime production of 160 MWh, and my system (after incentives) was something around $18K.
$18,000 / 160,000 kWh = $0.11 / kWh.
If my system lasts 25 years, that goes down to 9 cents per kWh.
(note: I think I have a 10 year loan but will likely pay it off way earlier than that, but it wouldn't factor into this calculation other than interest)
So if they eliminate all of the accidents that are caused that way, but increase the number of garden-gnome related accidents...wouldn't that be worthwhile?
Another, less flippant way to say it: yes, we can imagine scenarios in which the number of accidents will increase. But what is the relative frequency of those types of accidents compared to run-of-the-mill rear-end, red-light run, lane change due to inattentiveness?
But of course, there's no way they actually said it that way.
Right? Right??
Calling for a cab was extremely unreliable here. You could easily wait for an hour (because any driver coming to pick you up could, without ill effect for him/herself, stop to pick somebody up on the street). Some cabs took credit cards, some didn't. Some claimed to take credit cards but then "the machine was broken" so you had to pay cash.
Uber improved on every single aspect of the customer experience. And they did it while offering lower prices for the consumer.
However: to me, they haven't proven it's a viable, long term model. I highly doubt that they are paying their drivers enough to cover the cost of wear and tear on the cars (many/most of the drivers I see with Uber and Lyft are doing it full time, so they are crazy if they aren't factoring in the cost of the car and maintenance as part of their cost). And AFAIK neither company has proven they can make money.
So: this industry was due for a shakeup.
But it needs to be done by a company without rampant management problems, and it still needs to prove that there is a viable, long term business model that works for the company, the drivers and the consumers.
[edit: and, yes -- long term, there won't be drivers in these cars. But Uber has to find a way to survive until then, and I don't believe they can burn cash that long]
You opened the "spreadsheet", which hid Excel itself and showed a form. You filled it out, clicked Send and it used your local Outlook client to email a copy of itself to your boss, who then opened it and was presented with another form for approval, etc, up through finance and finally to the person who wrote the check.
It was amazingly ugly and fragile, and of course, there was no way for anyone to see the state of the system (because the 'state' was distributed among the entire workforce's Exchange inboxes!).
Want to know the status of your check request? No problem, simply call everyone who might have been in the approval chain and ask them to search their inboxes. Hope you find the most current person!
(updated to correct the name of the software)
A Cloud Spanner “node” isn't a physical machine, per se. It is an allocation of compute capacity and disk access throughput on a set of machines with access to the storage API.
(disclosure: I work at Google Cloud but not on Spanner)
Out of curiosity, what format did your infotainment system for serialization?
I remember when, as a kid, if you answered the phone and it was a long distance call for mom or dad, we would run to get them yelling "Long distance! Long distance!"
Every second was precious.
Check [0] if you, like me, hadn't.