HN user

lolsal

1,430 karma
Posts0
Comments725
View on HN
No posts found.

Sincerely asking - how does this solve the problem? I could generate a bunch of dog-shit and then sign it and publish it. Even with user attestation services provided by Apple, Google, et. al - couldn't I even automate generating a bunch of AI junk and signing it?

FYI this list wasn’t “everyone said every one of these things.”

Also, the “only real devs touch the real world” attitude is pretty sad. Not everyone wants to write guidance systems or heart monitoring firmware.

not sure if it is a data cable, also.

I may get accused of being an Apple fan for this, but this is why I dread USB-C. My lightening cables always charge and have data. Having to care about this is a pain.

I wonder how this is affecting what you consider knowledge going forward. This strikes me as students using google to answer homework questions and forgoing the actual “learning” part.

I think I feel the same way. I think it has to do with someone like this going to jail sounds like justice, but it doesn’t really help any of the people he screwed over.

Sort of like when one of the government agencies issued a huge fine to a company that wronged users. Will I ever see a dollar of that? It’s punitive consequences, but not justice.

I agree whole-heartedly. I’ve wasted many hours in security committee meetings. But then a CVE was discovered and we were able to respond in minutes. Earned our compensation 10x over with that preparedness, even if a lot of being prepared looked like downtime.

I appreciate the source, but averages don’t really mean much in the real world.

I’ll tell my neighbors they should get an EV even though they can’t charge it at home and have commutes in areas where there aren’t super chargers yet, but on average they should be just fine, and let you know what they say, if you’d like.

So far we’re talking about refueling logistics, but a huge chunk of all the other uses of a vehicle preclude EVs as well.

I feel like I have a mild case of schadenfreude for all of these Tesla mental gymnastics. All of this is one of the reason I am absolutely not an early adopter of technology. I am looking forward to when EVs are equitable range, quick charging and ubiquitous fueling stations comparable to gas guzzlers. I never have to think about things like whether or not it is cold, I’m going up hills, or any of this other stuff. I just drive and when my tank gets low I pull into a gas station and fill up in a few minutes and move on with my day. The only time I have budgeted my gas on a trip is through long expanses of desert driving where stations are far apart.

These are not mental trade offs I’m willing to make. I owe a debt to the early adopters who sacrifice their sanity for alpha/beta testing this kind of tech. A solemn and respectful nod from me to those that have lost their lives due to this technology.

Don't be clever 3 years ago

The only time being clever has helped me has been putting out a fire in production, to stop the bleeding, and to buy us time for implementing a better fix in the next release.

Being clever during feature development is a red flag to me. I’m a huge fan of the YAGNI principle.

I like the idea of a /now page, but it’s not for me, at least not in public.

I do something similar with journaling; I’m constantly journaling on a single note in the Apple Notes app. I consider it a sort of short-lived RAM for my life. Todos, thoughts, goals. I delete aggressively.

I use a private Trello board for longer-lives objectives and priorities to help keep me focused on 1yr+ long objectives.

If you say so.

You won’t be able to change my mind with an empty quip - people can and do learn by being surprised; and other folks learn differently. I’m not sure there’s much room for debate about that, but if it makes you feel good, spend the energy.

Writing new code with no existing constraints or requirements isn’t some masterful feat of engineering, usually.

Working in an existing code base, on a team with multiple features going in, gathering requirements from stakeholders and negotiating deliverables on a timeline while refactoring is happening, libraries being upgraded and CVEs being fixed - navigating all of that while being a useful, compassionate team member - that’s priceless on a team.

The dashes serve humans eyeballing uuids, not computers. You can remove the uuid in your language of choice and I’m confident it will be able to parse.

How are uuids pointless?

Hexadecimal is much more human friendly than say, binary.

I’ve been using uuids for over a decade and didn’t realize there were fixed bits in version 4. I learned something and am thankful it was posted here. Much more interesting than a lot of other submissions.