HN Simulatornew | past | comments | lists | submit | vehemenz's commentslogin

I’ll believe it when wine prices go down. Prove it!

This seems backwards. The salaries around here are relatively high, so a marginal increase in monthly entertainment costs wouldn't be noticeable in the first place. People can get self-righteous if they want, but these are entertainment services, not essential goods.

Only speaking for myself, but these streaming services would need to increase costs A LOT to make me invest valuable time replacing them.


The "relatively high" salaries also mean that 20 minutes of ads in a 60 minute session "costs" more. It's not quite as simple as applying my hourly rate to the ads, but it's at least a decent place to start the analysis, and by that metric it doesn't take long before the ads are the dominant cost of the service. It gives me a lot of virtual money to deploy to the task of turning to entertainment that doesn't annoying vast quantities of my time to squeeze out fractions of a penny from me because they can do it in bulk.

"here"

It's a big world out there, whatever "here" means.

That last sentence makes me wonder, do you enjoy ads?

I went to a Super Bowl party a while back and the half time show glitched continuously. Random weird glitches for the rest of the time. => note to self: don't pay for this.


I could be wealthy beyond my wildest dreams and still be turned off by their obnoxious changes.

My enterprise org has this model disabled because "security."

Does this mean they literally need to go in and check a box? Or is it a standard thing that enterprise accounts get these later than the consumer/API accounts?


Most likely they disabled it because it can* retain data if they deem they need to like Mythos/Fable.

What's to stop you from rebuilding it yourself to improve the structure? Why couldn't you vibe code it better?

I mean, I'm going to rebuild it. But with just a light AI usage. The point I'm trying to make is that. Ok, AI may have saved time coding it the first time. But building an unmaintainable codebase is going to make you pay that time back with interests

Ever since software became a "prestige" career, attracting the former-would-be-dentists of the world, the entire field has been gatekeeping a lot of mediocre talent. Let's be honest.

If we're looking for a silver lining, AI is an equalizer and creates competition among the mediocre, driving salaries down. It's not all bad.


I'm mediocre but it's not that I fear for my job being taken by someone better at AI than me (honestly I hate my job so much now I wouldn't care being forced into working in a grocery store). It's that the job has become absurd and anxiety inducing as I am not given the time to understand and build a mental picture of the code that AI is generating, and as the original post says "everyone is spending all day hitting enter" which is fucking true.

Oddly enough, I met a newly qualified dentist last year who said his parents had advised him not to get into software because AI was going to take all the jobs.

It's a significantly harder career, but less automatable.



doesn't make sense timing-wise ... to train as a dentist takes longer than the LLM-hype has been around.

"...former-would-be-dentists of the world"

so.. What do you call a doctor who failed out of med school? A software dev?


If I could get rid of AI I would be okay with salaries deflating still.

Godwin's Law in one step. New record!

> Also with lower-case initial. disparaging. Opposed to new technology or ways of working; disliking technological change and innovation.

From the OED. The predominant use of "Luddite" has been disparaging for a long time.

You can debate whether it should be or not, but it's not reasonable to criticize conventional use.


If there's a criticism here, it's that they don't mention k8s right up front. It's completely opaque what this tool is. "Orchestration" can mean literally anything.

The web page presents ax as a typical developer tool, but it's actually not for developers.


We are mentioning Agent Substrate. Agent Substrate is working on Kubernetes but isn't exclusive to Kubernetes.

Pros and cons. The sloppy approach actually works well for Claude because its memory retrieval is more reliable than AGENTS.md style instructions.

It's kinda true. I use the terminal approach too, but I wouldn't trust every type of user with this long of a leash. There's a place for instituting systems that share context, manage authentication, and is permissions-aware.

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

Search: