HN user

twodave

3,082 karma

Dave here, interested in most things tech, work as a software developer/architect on a variety of projects and tech stacks.

I also maintain https://naprun.dev, an HTTP test automation framework.

Contact: my username at gmail

Posts12
Comments1,151
View on HN

For years I always felt if I got a human on the other end I could understand that a company valued me as a customer enough to provide fantastic support. I could still understand the trade-off if I called and got someone barely-understandable, as long as they can still solve my issue. AI support agents tend to just make up reasons they can’t help you or you’re holding it wrong, or they are only able to do things the UI already allows, so they are actually of negative value to me.

Yes, the game is over, the corps have won. Where the Internet used to be a forum for creativity, it's now a weapon of influence. Where we used to have an anonymous (or at least pseudonymous) playground, we are now monitored more than anywhere else. Where we used to be able to genuinely connect, everything is now artificial and manufactured. And where we once had control, we are now the product.

For sure. I've taken to using a similar method over the last couple of years as I've increased miles and needed to take steps (ha) to take better care of my feet over longer distances. I wouldn't recommend this setup for more active sports with lots of change of direction, but for steady plodding it provides a very consistent and dependable stride for a lot of miles.

I tried writing a similar comment. Yours is much clearer. This 100%. As a runner I used to have to re-tie multiple times per run. I corrected my mistake with this same fix probably a decade ago and haven’t had a loose shoelace since.

Runner here. I found some time ago that starting out the classic shoelace tie right-hand dominant and finishing it left-hand dominant results in a very stable knot. Lacing them high enough to keep the ends short helps too. It has been thousands of miles since my last loose shoelace.

I wouldn’t say it serves no purpose. It is useful when rewrites are tolerable and loss of history is not. It’s the default when using tools like jj, because the expected workflow wraps git in a way that force pushes are frequent and expected, but blowing away someone else’s work by mistake is not.

For smaller shops (by small I mean <1,000 employees) this isn't even tenable. We (engineering team of about 10 people) mitigate what we can via tooling and cooldown periods/minimum release age. This will work as long as these malicious packages remain reasonably detectable. I think that's the proper balance, because we can adjust the # of days we are willing to risk against the SOTA of detection tooling.

I have said the same for a while. And I also think there is an increasing trend of clueless CEOs trying to replace expensive developers with AI token spend. We are still waiting on the long tail of consequences from those decisions, but I suspect it is going to look like a lot of perfectly financially viable companies turning into dumpster fires. Followed by opportunities as their clients churn.

No, I think the company has plenty of responsibility. I just think it is more likely as someone who has been part of many engineering orgs that this is a latent bug affecting some people than some intentional change of policy.

Personifying Google in this way is not realistic. The search team alone at Google is made of thousands of people who are all working on different things with an over-arching mission of making the web MORE accessible, not less. Any release from any of those people could have created a side effect of this kind. Is there a chance it was an intentional policy implementation? Sure. But the odds are heavily against it.

It's possible, in the short term, but eventually the only oil flowing thru the Strait of Hormuz will be Iranian oil, and perhaps not even that. Give countries enough time and they'll rather invest in building a way around Iran than giving them money for passage thru international waters.

I used to think heat/exercise was my only trigger. Then I got ahold of some of some HDR-enabled emojis and immediately started seeing auras everywhere haha. Didn’t take long to get rid of those. I didn’t get one from this article, but it felt like I was about to. So maybe not migraine-triggering but definitely anxiety-triggering :)