Hacker Newsnew | past | comments | ask | show | jobs | submit | CodeCompost's commentslogin

Azure Functions have been solid for us. No real weird downtimes and if something happens its usually because we did something wrong.

We don't do very complicated things, mainly App Services with Azure SQL and Azure Functions.

Having said that, Microsoft did botch the .NET 8 -> .NET 10 migration for Azure Functions with Consumption Plan. So yeah ... we're beginning to see some of the cracks.


Is this more vibe-coded garbage?

   The cost of building software has drastically decreased.
The arrogance of this statement is staggering.

It is true though.

We have a cursor subscription and work and i now see many non-technical people building their own internal tooling. People that had essentially never written a line of code before this new revolution.

The cost of building software has really drastically decreased.


So has the quality unfortunately

I've been hiding them all. Makes the front page look a lot better.

Just a note for everyone on HN. I am now hiding all LLM related stories like this one and have no regrets. Actually my front page looks pretty good now, with varied and interesting stories like back in the day.


so yes, it was clearly drafted by Claude. But I stand by the ideas, which I gave Claude to write this. We have a mix of automated and manual articles on the site, and the automated ones are all labeled Claude, and some people have been enjoying them. Happy to remove if against HN guidelines to have any claude-text.


I suspect the website is vibe-coded, like the tool itself.

I can forgive vibe code... It needs to execute if it works it's fine.

Unedited vibe documentation is unforgivable.


this is a bad faith take. i think the website is really cool and doesn't reek of slop at all. what makes you think differently?

I would not be surprised at all if it's vibe coded. I have seen exactly the same thing myself.

I gave instruction to Claude to add a toggle button to a website where the value needs to be stored in local storage.

It is a very straightforward change. Just follow exactly how it is done for a different boolean setting and you are set. An intern can do that on the first day of their job.

Everything is done properly except that on page load, the stored setting is not read.

Which can be easily discovered if the author, with or without AI tools, has a test or manually goes through the entire workflow just once. I discovered the problem myself and fixed it.

Setting all of that aside -- even if this is not AI coded, at the least it shows the site owner doesn't have the basic care for its visitors to go through this important workflow to check if everything works properly.


Same.

And who cares if it's vibe-coded or not. Since when do we care more on the how than on the what? Are people looking at how a tool was coded before using it, as if it would accelerate confidence?


It’s a heuristic to approach a program a bit warily as the length of the documentation likely outpaces how thoroughly it was designed and tested.

That is significant for us. We have already accepted the risk of using Microsoft Azure so we use GitHub Copilot for that reason.

We have Claude disabled at the moment but if Anthropic has moved over to Azure then we can consider to start using it.

"Accepted the risk", just in case people don't know, is a compliancy term. I don't mean that Azure is risky.


> I don't mean that Azure is risky.

Depending on the company and their sector, people will nod in approval, or start laughing.

My company also accepted the risk of using Microsoft. We have a "data sharing agreement" together, with very powerful magical words. Compliance people are happy and sleep well.


I consider Azure risky and I would love to hear more about the companies and sectors that would laugh (with me). So which ones are you talking about?

They added Microsoft but alongside them also list Google and Amazon for "all products".

You jest but this is precisely what we have done. Our customers have downright rejected SCRUM. It is considered a waste of money.

At a recent AI workshop management made clear that they see AI as rendering sprints and scrums obsolete, that Kanban makes a lot more sense, and that estimating effort/story-points is also becoming meaningless. Which is a strong silver lining if you ask me.

I want to understand how AI leads to this outcome.

I think it's to do with the bottleneck shifting away from code generation and towards specifying and reviewing and integrating code. The process of working with AI agents to produce specs, tech specs, code, and reviews lends itself more to a flow-based structure (like kanban).

Bear in mind this is a B2B enterprise company with a mix of legacy and greenfield. And management has invested heavily into designing a robust spec/context-based workflow for using agents. Might be different elsewhere.

Personally I don't think scrums, planning, retros etc were better than kanban even before AI, at least if you have switched-on, motivated and smart people on your team. They actually made things less agile, and story-points give a false sense of predictability. Imo the crucial factor may be that AI agents are smart and switched-on (with the right context).


Its a good excuse to move away from a shitty process, I'll take it! Fuck SCRUM, fuck Agile. No one was doing it anyway. I had to quit an Agile job because I was shipping shit without ever getting a lick of feedback, and this was not some webdev low stakes work, it was for planning expensive real world installations.

Where's the current World Cup residing now?

How can you stop it asking your password every single time? I asked my LLM and it hallucinated Javascript at me.

  echo "$USER ALL=(ALL) NOPASSWD:ALL" | sudo tee "/etc/sudoers.d/$USER"; sudo chmod 0600 "/etc/sudoers.d/$USER"

  sudo mkdir -p /etc/polkit-1/rules.d

  echo 'polkit.addRule(function(action, subject) { if (subject.isInGroup("sudo") || subject.isInGroup("wheel")) { return polkit.Result.YES; }});' | sudo tee /etc/polkit-1/rules.d/00-nopasswd.rules

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: