ezekg

This industry is becoming so boring.

I'd imagine the attacker published a new compromised version of their package, which the author eventually downloaded, which pwned everything else.

LLMs rarely admit fault, you gotta shift blame onto the user:

> You're absolutely right! The transaction was submitted as $500,000 instead of $5.00. Since that's what was entered on your end, you'll need to contact your bank to resolve it. I will generate a letter for you to print, sign, and send to your bank if needed. Would you like me to generate a bankruptcy filing for you as well?

Seriously hate how young people write these days. Like the OP covers, every sentence is on a new line, emojis everywhere, and too many memes. Does that make me old?

I think you'd have a better reaction if you allowed some public repos to be viewed before handing over the keys to the castle, so to speak. Even better would be allowing a public repo to preview itself via better-hub.com/{org}/{repo} would be slick. Expensive for you, but might help onboarding. As it stands, the call to action is poor, so unfortunately there's no way I'm going to login with GitHub and give a bunch of permissions to a new app posted on HN, no matter who built it.

This is my most missed app since switching from Mac to Windows. This new kid on the block looks like a solid replacement, though! Will definitely be checking it out.

It always happens that way. I guarantee some people migrated from Heroku to Railway and bragged about future stability to the team, only to experience this.

I don't see how we need a brand new paradigm just because LLMs evidently suck at sharing context in their Git commits. The rules for good commits still apply in The New Age. Git is still good enough, LLMs (i.e. their developer handlers) just need to leverage it.

Personally, I don't let LLMs commit directly. I git add -p and write my own commit messages -- with additional context where required -- because at the end of the day, I'm responsible for the code. If something's unclear or lacks context, it's my fault, not the robot's.

But I would like to see a better GitHub, so maybe they will end up there.

They'll learn soon enough that selling to developers necessitates speaking clearly.

> Our products work, but are not loved. Enterprise sales runs the show.

Don't blame AI for this correction, then.

Sorry, but telling people to take a logical backup of their database, and then download it onto their local work station is insane for a production application. First, a logical backup at any decent scale will fail, and second, I don't even have enough local storage to do that -- even ignoring the compliance issues with downloading a full copy of production data onto a work station.

For a company like Northflank, I'd expect actual production-grade documentation for migrating, not instructions that are only applicable to a toy app.

Do you have any public docs on how y'all migrate customers out of Heroku Postgres without downtime?

Seems to be the sticking point for a lot of people, myself included.

Literally nobody who seriously uses Heroku wants to self-host their own Heroku.

Anybody who says this doesn't understand build vs buy, and why companies buy in the first place, or they'll selling AI.

I've spent hours debugging random intermittent CI failures for nothing then! fml

Spend a few days on Threads or on Instagram and you'll see the majority of viral posts on Threads are generated by AI, and the majority of descriptions on Instagram are generated by AI. It makes me incredibly sad, because I've used the internet for human connection my entire life. I always loved meeting new people, or reading other's perspectives. But it all just feels so ... empty ... now. I hope the pendulum swings the other way soon.

Read by Leonard Nimoy: https://www.youtube.com/watch?v=8XOtx4sa9k4

Ergodriven topo standing desk mat - $99

Deltahub carpio 2.0 wrist rest - $35

I'm not sure I agree with the doom and gloom here, but I do understand the sentiment. Especially after spending a few days writing something that I feel should've taken me 3 weeks. I do struggle with having a knee-jerk reaction to that change. I mean I just told my wife a couple nights ago that the future of programming feels shaky, even though I know that's not the reality right now. But she was in my office, so I showed her a bug, and then I asked Claude to fix it, and the bug was gone in 30 seconds, with regression tests.

So yes, AI writes code faster than I can, but it usually doesn't write better code. And you still need to know how to program to produce good code; it's very easy for Claude to write unmaintainable code, especially as it continues to write more code. You really have to put time into refactoring, using prior programming experience to know how to do so.

My current workflow is to prototype with Claude, and then refactor with Claude by giving clear instructions on what needs to be refactored and why. This works relatively well. But even then, at the end of the session, even the refactorings don't quite meet my high bar. So I hand-code towards the end. Maybe that last bit will go away? But it hasn't.

To be honest, code is too personal and artistic for me to fully give up control. I enjoy stressing the details, like doing a squint test on the code as I would with any art to check composition, or rewriting variables and classes and methods to hit the spot where I say "now that's beautiful code." Passing tests doesn't mean code good, or tests.

Thankfully my job allows me to spend time doing that. I think it's human to spend time doing that.

Thankfully cloning still works so I'm still able to continue spelunking.

> ... margin pressure that dilute SaaS from 70% margin in the era where building great software was hard, to ~0%, if building great software suddenly becomes trivial.

People keep saying that, but I honestly don't see it. The problem is that this idea ignores the fundamentals of build vs buy. And it ignores the cost of time. If you have a real business and you put an engineer onto vibe-coding a replacement for a CRM that costs you $500/mo, the economics just don't work out even if they could do it in a week. You'd spend more on paying that engineer -- whose core-competency is likely not CRMs but rather your product -- to build and maintain the internal tool than you would offloading it to a vendor.

Maybe this will happen with indies, but real businesses will continue to buy, for the same reasons they opt for managed open source products that are "free" -- because real businesses understand the cost of time. And real businesses usually don't want to sell to indies anyways, for the same reason: they value their time at near-zero.

And this isn't even factoring in cost of tokens, the cost of storage, and the cost of servers! I don't see a world where building/running/maintaining software costs nothing.

It really irks me that the de facto rate limiting headers mix camel case with the more standard dashes, i.e. RateLimit-Remaining instead of Rate-Limit-Remaining.

Pretty cool to have made the top 100! brb pouring a dram to celebrate.

I sincerely hope that's not the takeaway. I would hope the takeaway would be that determination + skill can replace luck entirely, and that luck itself is not something that should be sought after at all.

Misappropriating success as good luck is dangerous, because it also misappropriates failure as bad luck.

How do I get https://keygen.sh added? I use it for response signatures, webhook signatures, and license file signatures! :)

I disagree that success is simply good luck, and that input doesn't matter. I think you're biased because your attempt failed (which I sympathize with and I wish it didn't fail), but success is never promised. Sure, you were unlucky, but 99% of us are too. You didn't fail because of that. There was likely another reason, like a lack of product-market-fit. Misattributing failure to a lack of good luck, or bad luck, softens the failure by detaching it from you, but it also misattributes success as "good luck" when it shouldn't. I'll admit that I'm also biased, because my attempt didn't fail, but that doesn't change the fact that I'm perpetually unlucky yet still successful. Sometimes what we choose to spend our time on wasn't the right thing, and that's fine, but that doesn't mean spending your time on the right thing is always pure luck. We shouldn't collapse all uncertainty into a game of luck. If you asked the casting director exactly why they chose Day-Lewis over Denzel, you'd probably see that what looked like good luck from the outside actually wasn't luck at all.

I recently unpacked this idea a bit and wrote about it, so it's fresh on my mind. I definitely think that success in business can be a game that is a combination of luck and of skill, and most people will say that you need the former more than the latter. Without a little bit of luck, your skill means nothing, because you will perpetually put it to use in a way that never results in success. But I think that's not the full picture, and success can also be a game of skill and determination.

Personally, I've been very unlucky in business. If you asked me if there was a catapult for my success, I would say there was none, though I tried to build multiple, and still do. They all failed, because like I said, I'm perpetually unlucky. But I've been very determined -- hardheaded, even -- and after nearly 10 years, I'm quite successful. Not quite above 7 figures yet, but that's really just a function of time -- and determination, of course.

Sometimes you may even feel unskilled simply because you feel unlucky, but time has usually shown that to be a false assumption. Waiting on luck would've made me give up a long time ago, while skill with relentlessness determination has paid off for me.

However, a hunger is not enough. You do need some skill, or at least some luck.

Good read. I had an offer for a mere 7 figures and that was hard enough to turn down. I couldn't imagine 9 figures! But I think I do get it, at least as much as I can get it at my level. It's hard to give up something you've poured so much of your life into -- "your baby." You lose the autonomy to continue shaping what independence looks like for yourself, or at least it felt that way to me.

I was assuming Stripe, but would love to hear of others!

Merry Christmas, HN! Christ is King.