jdalton

No different than most practices now. PM write a ticket, dev codes it, PRs it, then someone else reviews it. Not a bad practice. Sometimes a fresh set of eyes really helps.

The UI experience will eventually die off. Even AI doesn't know what an agentic experience is (yet), but give it a year ;)

I agree. I think that's why we need to use AI as an assistant, not a replacement..but most companies want replacements.

Would you consider yourself one?

Is that philosophy course via college?

The challenge is many struggle with giving context. In tech we were always told to "dumb it down" but in a world driven by context people need to "smart it up."

I feel there will be room for PhD level roles like you mentioned, but it would seem that over-time they become HITL by regulation...not knowledge.

In a world where AI will always be smarter than us, what's the point of getting a degree? Should we just focus on learning to work with AI?

I coined the term "agenticist" to describe this mindset shift. It's not about technical skills (I'm no ML expert), but about treating AI as a thinking partner rather than a productivity tool.

But I'm curious what HN thinks. Are we just rebranding existing practices? Or is there something fundamentally different about approaching problems with AI as a collaborator from the start?

Four things I've noticed agenticists do differently:

- They ask "what's the agentic approach?" before defaulting to traditional solutions - They focus on emergence over control (letting conversations evolve rather than scripting everything) - They treat AI failures as thinking opportunities, not bugs - They bring AI into strategy discussions, not just execution

The controversial part: I think this mindset matters more than knowing how to fine-tune models or write perfect prompts.

What do you think – is "agenticist" a useful distinction, or just consultant BS?

And if you work this way, what would you call it?

I've worked with business rules teams. They're great at establishing the yes and no, but never the why.

I've updated the readme...

I've added the url to the YT livestream in the readme file.

I could see about making the initial one more difficult or let the user pick a difficulty level.

I love the wordle-like approach idea!!!

Thank you so much!

I'm going to hook a backend up to have AI generate patterns.

I like the idea of positive and negative matching :)

Thank you for this feedback.

Yesterday I did have a marketing copy where we provided a sample, but people were copying it then leaving the site :p

I like item #4 a lot!

That's been corrected. Saw this come across the log about 13 minutes ago.

(Context: I'm a top rated freelancer on UpWork that's been using the platform for a year)

Ivan, one of the main reasons you're encountering those types of clients is that your hourly rate is competitive with other freelancers in other parts of the world that will do the same job for $3/hr.

Here's my advise for you:

1) Increase your rate to around $50/hr. Trust me there are plenty of clients that are willing to pay higher rates. 2) Don't bid on every project that comes along. Only focus on projects that you really want to be a part of. 3) If you don't have a portfolio then build some demo sites where you can showcase your work. Given that you like building scrapers you should be a simple web service that does exactly that. 4) Only take hourly jobs OR fixed rate jobs where the client provides a clear, documented scope document that you both can agree to. 5) Don't be afraid to say no. The biggest issue with freelancers in other parts of the world is that they say yes to every single thing....don't be that guy. Clients will respect you more for it. 6) Don't hand the source code over until you have been paid. 7) Stand your ground anytime a client challenges your rate. You're a professional and not a cheap commodity.

Great things never came from comfort zones. If you want to reach your goal of financial freedom you're going to have to put yourself back out there.

The company I work for still uses an AS/400. I hate it.