HN user

lpapez

1,649 karma
Posts0
Comments353
View on HN
No posts found.
Cooling in Space 1 month ago

It is a comment on the absurdity of orbital data centers. Mountaintop data centers sound absurd, but are more feasible and efficient than orbital ones in nearly every aspect.

Can't you simply fill that gap on your resume with something made up? "Self employed", "freelancer", "stealth startup", "confidential employer" etc.

How would the companies ever know?

Very cool research and wonderfully written.

I was expecting an ad for their product somewhere towards the end, but it wasn't there!

I do wonder though: why would this company report this vulnerability to Mozilla if their product is fingeprinting?

Isn't it better for the business (albeit unethical) to keep the vulnerability private, to differentiate from the competitors? For example, I don't see many threat actors burning their zero days through responsible disclosure!

so why use PHP at all instead of JS like all the other vibe coders?

Because there is nothing remotely close to Laravel for JS. I don't want to think about auth, job queues, mailing, cache layers, auditing etc. I want an opinionated default from my framework that is thoroughly documented and part of the AI training corpus. Laravel gives that to me.

hype-driven commercial product

single-handedly keeping PHP relevant

While architecture astronauts are clutching pearls, I've built multiple profitable products with Laravel without caring the slighest about the internals, both before and after AI.

PHP was always all about just building stuff while ignoring code quality. Laravel is a natural extension of that approach. Let us live.

Agile just finally embraced that specs are incomplete and can even be wrong because the writer of the spec does not yet really know or understand what they want. So they need working software to show the spec in action and then we can iterate on the results.

I agree, but what you describe is agile, not Agile (capital A).

Agile (capital A) is Scrum (capital S) where you have Backlog Grooming (patent pending) where the team clears any ambiguity to define a spec (ticket).

Deviating from said spec is seen as Scope Creep (gasp) and might lead to complaints during Sprint Review (trademark).

So yes, agile prefers working software over detailed spec. But typical manifestations of Agile (capital A) are exactly the opposite.

The US public discourse is so dehumanized today that anyone who is not "with them" is literally not a human anymore. Even within the country itself "the leftards" are considered an obstacle which can be removed if only enough force is applied.

Sending armed agents at protesters is seen as being the same thing as sending pest control to clear out beaver dams on the creek. Nobody cares what the beavers think, they are not human, they do not have feelings. They are simply a menace to be dealth with.

So if you can sell those MT for $1-5, you're printing money.

The IF is doing a lot of heavy lifting there.

I understood the OP in the context of "human history has not produced sufficiently many tokens to be sent into the machines to make the return of investment possible mathematically".

Maybe the "token production" accelerates, and the need for so much compute realizes, who knows.

Less headcount usually means faster pace - less lines of comminication, less red tape etc.

Or at least that's what many C-level people believe to be true. "We need to move like a startup" is a common mantra repeated by executives, even megacorps like Amazon.

I guess it's true to some degree though, anecdotally as an IC at a tech company, I feel like I could move a lot faster if some people around me removed and replaced by an automation instead.