141–150 of 436 posts
Earlier quoted context omitted.
Youtube wasn't launched by Google, it was purchased.
Youtube launched 1 year and 8 months before being acquired by google.... It's largely semantics to say that what Youtube is today, isn't a direct result of Google's ownership for nearly 20 years now....
It’s not right at the top of the list only because the current customer base is made up entirely of a small number of friendly triallists who are known and trusted and not likely to go rogue.
It’s sort of mind blowing that Google would release an AI powered feature to who knows how many millions of people with, apparently, no prompt injection mitigations in place and no interest in adding them.
We think pretty hard about the corners we choose to cut at our early stage, and the trade-offs we’re making in doing so, but I still occasionally worry that we’ve cut a corner we shouldn’t have. It seems I’m somewhat less of a cowboy than I’m sometimes concerned I may be.
Earlier quoted context omitted.
objective systems become gamified subjective systems become politicized pick your poison
I'll pick small company, thank you.
Earlier quoted context omitted.
I disagree with this pretty strongly. If you’re not going to take responsibility for your bugs I don’t want to work with you. Don’t make other people QA your work; if you’re not able to figure out how to do that yourself while you work you’re legitimately bad at your job. Once you leave an employer obviously you have no obligation to fix bugs in IP you don’t own or anything.
I think it's reasonable to have a culture where you're encouraged to consult the IC who wrote the code even after they've moved on to other projects. But I don't think they should be responsible for fixing the bugs. And I don't mean this to excuse the bad code written by ICs. I just think it's not sustainable from the POV of the org itself to depend so heavily on individuals, especially ones who aren't familiar with…
Earlier quoted context omitted.
I really feel like this genre of comment should fall under this "don't" from the HN guidelines: > Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting. You're willingly disabling a part of web atandards.
The web really doesn't, and shouldn't, depend on these things. I use a JavaScript whitelisting tool, so that I can allow JavaScript on pages where it's merited, when the trust for that functionality has been earned. Nowadays it's used for things that have been possible in plain HTML for decades. In this case, text has been added to HTML that causes otherwise visible text not to display, presumably so that it can fade…
(I also allowlist javascript. Regardless of your philosophical standpoint, many websites do break. If you don’t want “smacks me in the face multiple times a day” then stop allowlisting javascript.)
Earlier quoted context omitted.
Youtube wasn't launched by Google, it was purchased.
Youtube launched 1 year and 8 months before being acquired by google.... It's largely semantics to say that what Youtube is today, isn't a direct result of Google's ownership for nearly 20 years now....
- ads every now and then
- addictive shorts no one needs
- suggested videos nobody asked for
- geo ban of videos
I recently left Google having worked on a number of projects with various YouTube teams. I think I can explain why it's being handled this way by YouTube. This is a fairly nuanced/involved issue, so the task of classifying the bug likely made it's way to one of the engineers responsible for the implementation of this feature. That engineer has already launched this project, and filed it away under their GRAD (perform…