Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rezonant
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
49 ms
·
631.
▲
by
rezonant
3y ago
line of business
632.
▲
by
rezonant
3y ago
> In software engineering you can test things in something on the order of seconds to minutes. Functions have fixed contracts which can be unit tested. I think this only applies to a certain subset of software engineering, the one that r
633.
▲
by
rezonant
3y ago
On the other hand, Ooh, looks like this Furby has learned the English words "new", "nuclear", "facility" and "Ohio"! /s
634.
▲
by
rezonant
3y ago
It's the straw that broke the camel's back, at least for all the lamenting of Google here on HN lately.
635.
▲
by
rezonant
3y ago
Larry Page (the cofounder) took over after Eric Schmidt. And that was a long, long time ago. Read up on the History section of Google's wikipedia page for more ancient history.
636.
▲
by
rezonant
3y ago
Google is far from an engineering led company today. It is the same product management situation as at any other company. That engineering led vision for the company is what produced their early successes. Their later failures aren't b
637.
▲
by
rezonant
3y ago
- Post resulting article on your spam blog - The circle continues
638.
▲
by
rezonant
3y ago
That's not what open source itself means, no. Open source means everyone gets source, not only customers. What you are referring to is often labelled shared source. For instance, Microsoft offers the Windows source code to some custome
639.
▲
by
rezonant
3y ago
> The Waymo passenger answered and there was much giggling. She kept saying she didn't know what to do. I said just leave it in the car. I inferred that you discussed this with the person, since you indicated you talked to them via
640.
▲
by
rezonant
3y ago
Moving the phone from the place it was left with consent of the owner is not theft. And it's not that crazy to leave lost property with a nearby business (presumably a trusted one)- sure they could say no but then you could just find
641.
▲
by
rezonant
3y ago
Sounds like their intricate build process is in service of their business model. Pretty crappy thing to do.
642.
▲
by
rezonant
3y ago
Chromium and its components like libwebrtc are extremely difficult to build correctly.
643.
▲
by
rezonant
3y ago
I think this sort of verification being available is exceedingly rare, especially for builds that statically link dependencies.
644.
▲
by
rezonant
3y ago
This was an incredible read! I'm diving into my own hobbyist IoT project and it was super interesting to see how this spelunk turned out. The extra bits about NetThings exploits are the icing on the cake!
645.
▲
by
rezonant
3y ago
I'll go further, what kind of monster inconveniences the whole process by changing the order after the fact??
646.
▲
by
rezonant
3y ago
Yep, this is my intention. Good product is made via collaboration between the people writing the stories and determining the overall experience and the engineers that make it happen.
647.
▲
by
rezonant
3y ago
OK let me share more detail. My personal account has 2 payment profiles, one that is individual and one that is an Organization type with just my name which has a Public Merchant section. The second one clearly came from some kind of long r
648.
▲
by
rezonant
3y ago
Oof that's true I forgot about MapQuest.
649.
▲
by
rezonant
3y ago
Features are not product design.
650.
▲
by
rezonant
3y ago
Search was a product designed by two engineers. Maps from 2005 was a very sleek product, but at the time there were no competitors on the web, and now Maps is so ubiquitous, and requires such an insane data investment, that we'll proba
651.
▲
by
rezonant
3y ago
Oops, should've been M&A (mergers and acquisitions)
652.
▲
by
rezonant
3y ago
We should all endeavor to emulate it if we can.
653.
▲
by
rezonant
3y ago
> If Big Tech really are metaphorically comparable to the big dinosaurs, then I don't want to think about what it would take for them to go down. In an absolute sense, probably nothing can, short of society ending cataclysm. In a sh
654.
▲
by
rezonant
3y ago
Perhaps DNA is too strong a word, because it would seem to imply that change is impossible. It's more that Google executed the changes badly, after the "PM shift" as we're calling it happened, they continued to fail to s
655.
▲
by
rezonant
3y ago
Absolutely. And don't get me started on how M&A has created an absolute monster of technical debt that stares you in the face as a user. Many might disagree, because the trillion dollar veneer Google can throw at things obscures it
656.
▲
by
rezonant
3y ago
Yes, but Google as a business felt like they could do no wrong, like they were the best at everything, and failed to see that they threw the baby out with the bathwater while trying to chase product categories that weren't in their DNA
657.
▲
by
rezonant
3y ago
Your theory doesn't match the timeline. Under the engineering first strategy, Google became the juggernaut it is today, with products like Gmail, Maps, Street View and of course Search. Unfortunately, the approach doesn't work for
658.
▲
by
rezonant
3y ago
Which is actually supported already with App specific Passwords...
659.
▲
by
rezonant
3y ago
App specific passwords will continue to work, and will work fine if your native app does not support the usual OAuth flow.
660.
▲
by
rezonant
3y ago
Yes indeed they mention how to opt out of quantization directly in Chrome if you'd like (at your own risk) using the Devtools.
More ›