Recent submissions

Comment · 9 days ago
Maybe i missed it in the post, but how are they going to implement it? They mentioned geoIP is insufficient for complying with the block, so if they dont have a way to block only these domains for users in France, how will they block all requests for users in France?

To be clear I dont think they should comply with the block, but i didn't grasp how they're going to block everything if they dont have a way to only block some things.

Comment · 2 months ago
Nothing needed to be "revived" here. The cloud sync stopped working, the device was otherwise fully functional. Author found a more convenient method for accessing files than the cloud sync, anyway.
Comment · 3 months ago
Same in the NY/NJ/PA tri-state. Ahead of the 4th a NY state trooper sits in the parking lot of the Phantom Fireworks in Matamoras, presumably calling in NY plates for their buddy to go pull over.

We just took the back roads home instead of the highway.

Comment · 4 months ago
> ... on my Macbook Max M5 128 GB

Local development for who? How many of y'all are rocking 128GB of memory? Am I reading Apple's site correctly that it's a $10,000 laptop?

Comment · 4 months ago
Piracy isn't stealing regardless of whether or not buying is owning.
Comment · 5 months ago
This kind of behavior is never tolerated in the market. Your revenue is flat; they lay you off. Right away. No trial, no nothing. Your revenue is down, right to layoffs, right away. Revenue grows but less than guidance? Layoffs. Record revenue exceeding guidance? Believe it or not, layoffs.
Comment · 6 months ago
> I have an unhealthy relationship with it.

You really, really do. Please, for your own benefit, take a step back and touch grass, literally. There is so much more to this world than Github of all things.

> Every day, multiple times per day, for over 18 years... During my honeymoon while my wife is still asleep? Yeah, GitHub

This is addiction

Comment · 10 months ago
> Ironically, LLMs are especially good at evaluating documents to assess the degree that an LLM assisted their creation

Is there any evidence for this?

Comment · 10 months ago
Two different numbers, no? The resignation posts specifies 110 customer meetings, the blog post you linked to about meetings during odd hours does not.
Comment · 1 year ago
> Unfollow all of your connections

I hate that this is the only option available. I want to follow my connections, for their own posts, if any. What I don't want is to see everything they like, share, and comment on -- but LinkedIn won't let you turn that part off.

Comment · 1 year ago
Because nginx, as an HTTP server, could answer the query?
Comment · 1 year ago
The ACME provider makes a query to the DNS server to validate the record exists and contains the right "funny string". Parent's question was whether that query is/can be made via DoH.
Comment · 1 year ago
They don't use Godaddy directly. Godaddy is the registry for .us. Zoom's registrar is MarkMonitor, who appear to be at fault for this outage.
Comment · 1 year ago
Wow, that edit is something. Post something inflammatory that will garner engagement, then turn it into your own "I'm hiring" post once it's on the front page.

Quality hack.

Comment · 1 year ago
You can't just be in your codebase and start doin' technical debt like that. 1a. Technical debt is when you... 1b. Okay, wait. Technical debt is when you write code but, like, the kind of code that you know Future You is gonna hate. 1c. Let me try this again.

1c-a. It's when you're coding and you think, "I'll fix this later," but then later turns into never. And now there’s spaghetti code in a project that was supposed to be a sleek pipeline.

1c-b. Like, imagine you're about to refactor something, but you go, "You know what? The deadline's tight, so I’m just gonna... not." That’s technical debt.

1c-b(1). If you're writing code and you think, "Wow, I hope no one sees this commit message," congratulations, you’ve accrued technical debt.

1c-b(2). It’s like leaving a TODO comment, except the TODO becomes, “Oops, it’s been in production for three years.”

1c-b(2)-a. You can write a clever workaround here, but the workaround has to work around the workaround of the workaround from three sprints ago.

1c-b(2)-b. Also, don't forget to include an inline comment that says, "This should be fine for now," which is developer code for “This is the next intern’s problem.”

1c-b(2)-b(i). Fun fact: the "for now" phase lasts forever, and the fix will never be fine.

1c-b(3). Seriously though. Technical debt is when your code does the thing but not in the way anyone would ever want it to. And if your app suddenly catches fire during peak traffic, that’s just the interest being collected.

    Do not do technical debt, please.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton