mfalcon

I think SWEs will still be needed but to do higher level work. The thing is, there will be less SWEs per company.

Obviously I dont know ehat will happen, but my guess is that there will be more small companies highly specialized on specific niches.

If I switch to business mode, I think this is the best time to start a company because you have more leverage in your hands and also because the job market is and is going to be disrupted, at least for a while.

Agree, and for the delivery-riders side, you and some vlose people can start making the deliveries if possible.

I don't know what requires more skills: creating Bitcoin or avoiding getting identified after all these years.

"Just when I thought I was out, they pull me back in"

You have to evaluate the llm responses. https://aunhumano.com/index.php/2025/09/03/on-evaluating-age...

In my opinion, conferences are mostly high noise low signal. My boss went to an "AI conference" last month and all the learnings he shared were things I was advocating already:

- use claude code

- evals are critical

- don't use AI everywhere

I think the conferences are more "work vacations" than work. Maybe they're useful if you think about them this way.

The truth is that no one really knows.

My approach is to "ride the wave", don't resist, just try to use it as an advantage and if not possible, adapt and look where I can keep adding value to the world.

Currently I'm trying to get my own company started because that way I can iterate the product faster using AI and if it goes well I can slowly migrate from coder to manager. I've come to terms that my days as a pure coder are coming to an end but I've been coding for at least 15 years.

Wake me up at Opus 12

Would be nice to use as an interface to interact with Claude Code.

Nice, I'll take a look. I was thinking about building a benchmark similar to the one you described, but first focusing on the negotiation between the store and the product suppliers.

Does your software also handle this type of task?

I was eagerly waiting for a chapter on semantic similarity as I was using Universal Sentence Encoder for paraphrase detection, then LLMs showed up before that chapter :).

I had been working on NLP, NLU mostly, some years before LLMs. I've tried the universal sentence encoder alongside many ML "techniques" in order to understand user intentions and extract entities from text.

The first time I tried chatgpt that was the thing that surprised me most, the way it understood my queries.

I think that the spotlight is on the "generative" side of this technology and we're not giving the query understanding the deserved credit. I'm also not sure we're fully taking advantage of this funcionality.

You can evaluate with your programming language of choice.

Good idea for a follow up post :)

Yes, and these problems are more present in the first iterations, when you are still trying to get a good enough agent behaviour.

I'm still thinking about good ways to mitigate this issue, will share.

Hey fellow hners, OP here. Been working on agents for a while so I started sharing some things.

The idea is to keep updating this post with a few more approaches I'd been using.

I know that the "understanding" is a stretch, but I refer to the Understanding of the NLU that wasn't really understanding either.

I think that the natural language understanding capability of current LLMs is undervalued.

To understand what the user meant before LLM's we had to train several NLP+ML models in order to get something going but in my experience we'll never get close to what LLM's do now.

I remember the first time I tried ChatGPT and I was surprised by how well it understood every input.

I guess it depends on how you use the LLMs. We implemented some workflows where the LLMs were used only for dialogue understanding, then the system response was generated by classic backend code.

That's the way I'd used it, I've built a document with all the requirements and then gave it to CC. But it was not a final document, I had to go back and make some changes after experimenting with the code CC built.

We're using gitlab issue tracker and it's not even close.

I know you tried to hack it the same way as I did.

I think that we will be reviewers too, we have to know if the AI generated artifact does what we want.

The AI doesn't suffer, doesn't struggle, doesn't love, doesn't question itself.

The AI is not like us. The AI only can produce something "nice" with no backstory.

I was asking myself the same question the other day, some basic search thing just didn't work.

I'm doing something similar to the OP but I'm not a CTO but a "manager". Maybe the title is "we're all managers now". The CTO role is bigger than that.

"Outputs are disposable; plans and prompts compound."

I agree with this and it aligns with the general opinion about what is the true value the SWE's bring to the table.

Another argentinian here, nice username! :P

That sounds nice. Sometimes I listen to a really great fragment of a song (the final minutes of Descending from Tool) and I think: "It'd be great to hear songs that have this kind of fragment".

I don't know if that's possible or not, but it'd be much better for me than the recommendations from popular streaming services.

Wow! I was thinking about doing something similar (extracting audio features to find really similar songs) some weeks ago. I love the idea, it'd be great to have something like this to discover music too, but it'll be difficult to discover new music because it won't be present in the collection.