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

Can you elaborate on what you mean?

Reusable missiles. Reusable claims of missiles being fired…

I mean... their stock is up more than 1,000% since 2014. Anyone who has been there for a few years should have multiple refreshers that have grown significantly in value.

They literally don't. Data is their moat; selling it would be counter to their financial success.

Well not in bulk to its advertisement competitors as you seem to suggest. But as a different revenue stream, data collectors sell the collected information. Don't be naive, of course they do, first customer are governments.

You think not being allowed to write any code manually is the norm?

> "You shouldn't be manually writing any code".

Can someone explain how this mentality could possibly be rational? It sounds completely asinine to me, and I use AI quite a bit for my job.

In fact, the team at my work that seems to be 100% AI writes the worst code, follows no standards, and doesn't seem faster at all than teams that are simply AI-augmented.


> The JS ecosystem is really, really complicated, so any non-trivial app is going to use multiple bundlers, node runtimes, native runtimes, etc, etc, etc.

This statement makes very little sense to me. I've worked on several of what are likely the largest JS monorepos in the world, and they all define a specific version of a specific runtime and package manager you should be using.


I've been seeing this sentiment since I got into professional software development nearly 20 years ago.

I'm one ban away from a permaban thanks to the Navy Seal copypasta

Dishonest people.

Why would a self-described "AI Engineer" be any more capable of building that sort of functionality over any other backend engineer, especially one who is familiar with agent-assisted development?

Because building on top of LLMs is really tricky. You need to understand things like writing evals, configuring agentic loops, creating and iterating on system prompts, designing tools that work well with LLMs.

It's a speciality, just like being a payments engineer who integrates with systems like Stripe is a speciality.

Being familiar with agent-assisted development helps a little bit because at least you understand prompts, but there's a whole lot more to building software on top of LLMs than that.

Any engineer can get familiar with these things of course, just like any engineer can figure out what it takes to work on payment systems.


  > It's a speciality, just like being a payments engineer who integrates with systems like Stripe is a speciality.
At $PREV_JOB, we had physical Point-of-Sales systems as well as a mobile app, and provided multi-merchant marketplace functionality with things like disbursement reports and support for multiple bank accounts for vendors.

I had to migrate all of this from Braintree to Stripe. It probably encompasses the most complex payment system I've worked on in my career.

But that's not a job title, it's just part of "make the app work"


At my $PREV_JOB we would have called you a payments engineer for that.

I don't think AI Engineer is an exclusive job title. If anything, coding agents are pushing us all to become generalists much more so than before.


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

Search: