gabrieledarrigo

Location: Milan, Italy

Remote: Yes

Willing to relocate: No

Technologies: Node.js, TypeScript, React, PostgreSQL, MongoDB, Redis, Google Cloud Platform, AI agentic development.

Résumé/CV: https://www.linkedin.com/in/gdarrigo/

Email: darrigo.g@gmail.com

I'm a senior software engineer with 14 years of experience; I have worked with small teams and enterprises, and I have successfully contributed to the success of many products.

I would love to work with a small, compact team on an interesting product and/or challenging engineering problems.

Please get in touch!

> because the diff is cheap and the “why” vanishes when the session ends.

But why should I use a tool like Entire, if the "why" is usually tracked somewhere else, in a ticket under the form of user or business requirements?

Once the specs are clear, and the intent is fixed or validated, the resulting code is just an implementation detail, and it can follow a continous merge approach as long as it doesn't drift away.

> Let your agents loop until evals are green

Exactly what I'm saying: if you think about it, it's just the job of a CI.

If for the "why" you mean why an engineer choose that approach, I'm not interested into digging in their own prompt with the agent: to rebuild a mental model, I can just ask another agent.

Another one: I'm also very skeptical on the "Join the rebellion" punchline. Rebellion against who, exactly? Nothing in the AI narrative has the flavour of something built from the bottom, against an established power; I would say it's the opposite.

I'll suggest something more streamlined, and banal: "Try it now!", or "Join the alternative"

As a side note, the text styled with Noe Text in a bold weight is quite unreadable. I would use 100 instead, which makes the text more pleasant to digest.

Location: Milan, Italy

Remote: Yes

Willing to relocate: No

Technologies: Node.js, TypeScript, React, PostgreSQL, MongoDB, Redis, Google Cloud Platform, AI agentic development.

Résumé/CV: https://www.linkedin.com/in/gdarrigo/

Email: darrigo.g@gmail.com

I'm a senior software engineer with 14 years of experience; I have worked with small teams and enterprises, and I have successfully contributed to the success of many products. I would love to work with a small, compact team on an interesting product, having an impact on my daily work. Please get in touch!

> he was asking me how to do a 60 to 80-hour week

It's simple: just don't do it.

> Not just servers in Europe. A European company

Come on, even the claim is sloppified! It's not this, it's that!

Location: Milan, Italy Remote: Yes Willing to relocate: No

Technologies: Node.js, TypeScript, React, PostgreSQL, MongoDB, Redis, Google Cloud Platform, AI tools.

Résumé/CV: https://www.linkedin.com/in/gdarrigo/

Email: darrigo.g@gmail.com

I'm a senior software engineer with 14 years of experience; I worked with small teams and enterprises, and I successfully contributed to the success of many products. I would love to work with a small, compact team on an interesting product, having an impact on my daily job. Please get in touch!

Location: Milan, Italy Remote: Yes

Willing to relocate: No

Technologies: Node.js, Typescript, React, PostgreSQL, MongoDB, Redis, Google Cloud Platform, AI tools.

Résumé/CV: https://www.linkedin.com/in/gdarrigo/

Email: darrigo.g@gmail.com

I'm a senior software engineer with 14 years of experience; I worked with small teams and enterprises, and I successfully contributed to the success of many products. Hire me if you want to onboard a passionate team player who is used to wearing many hats, colleague.

PS: Please don't spam me with your recruitment platform; contact me only if you are directly searching for a senior software engineer position.

> Looking at the countless repetitive posts on HN, it shows what HN programmers are afraid of. They're afraid of the destruction of their overall meta-methodology.

I think this already happened. What's hard to swallow for us is the countless years spent studying, researching, and investing our time to be the best possible professionals in a very demanding, skill-intensive industry.

Now that software development is starting to be industrialized, I think it's fair to react with fear and uncertainty.

Yep, we are trying to find new strategies and methodologies to still stay relevant, but I think they'll become obsolete soon once the technology reaches a maturity point for full automation and the industrialization of the development process.

What it will look like, I don't know (I have a few guesses), but what I know is that I'll struggle a lot, in the middle of my forties, to reskill myself, especially considering a country of no opportunities like Italy.

> In that sense, I think the recent post from Jane Street is more like a new solution.

Can you please share it?

"Questions are never indiscreet. Answers sometimes are."

> Why, I wonder.

By something that is going to replace my job by writing better code and shipping more features at a fraction of the cost, without asking for vacation? I don't know, boss; I'm also trying to understand why I'm tired.

> Code (and specs) are going to fade into obscurity

I'm always skeptical when I read absolute statements like this.

Especially about specs. They drive and document how the software should work, behave, and under which conditions. In the same moment you write a prompt in natural language, you are writing a spec.

Why should they disappear?

For the same reasoning, we could no longer need books or manuals or documents (is it valuable to keep around that doc about F-22 specs?).

Bah.

Personally my take on the entire affair is quite negative, whatever Jarred or Simonw says about it.

I think Bun owned by Anthropic and the entire rewrite with AI is not the real point (even if it's quite interesting, though).

My take is that Jarred, and Bun,didn't demonstrate a serious, adult approach, from "this is my branch, you are overreacting" message to just proceeding with a 1mil+ PR merged in less than month.

The communication is the issue, and it was handled very badly, in a way that impacted trust and divisions.

Was it so difficult to adopt the approach that the TS team adopted for 7.0?

I highly respect Antirez, and as an Italian fellow programmer, for me, he's like a legend!

Although reading this article makes me quite sad; I consider myself an average, mediocre programmer, but I enjoy writing code since it's a way to build the mental model of a problem and to solve it iteratively.

I obviously use agents and all the new fancy tools, but if a great programmer like Antirez says that it's over, I think I'm not so faithful about my future as an engineer.

Location: Milan, Italy

Remote: Yes

Willing to relocate: No

Technologies: Node.js, Typescript, React, PostgreSQL, MongoDB, Redis, Google Cloud Platform,

Résumé/CV: https://www.linkedin.com/in/gdarrigo/

Email: darrigo.g@gmail.com

I'm a senior software engineer with 14 years of experience; I worked with small teams and enterprises, and I successfully contributed to the success of many products. Hire me if you want to onboard a passionate, team player, used to wearing many hats, colleague.

Was this page human-written, or AI-generated?

> AI didn’t come for a job title. AI came for a task type

I just stopped reading here. It's frustrating how so many people can't simply write an article, a document, or a ticket.

Just use your words, come on!

> You don't need a body, you need electrical signals your brain interprets as body.

As I was saying, your brain is literally part of your body. It's a living organ of your body that receives those inputs, as you say, from the rest of your body.

> And in principle you don't even need a brain, you could replace that with some matrix multiplication or transistors that do the same stuff.

I completely disagree here, and that's why guessing that a bunch of matrix multiplications are coscient and have self awareness of their own experience while running in a CPU seems quite hilarious to me.

But hey, that's just my opinion.

> AI that can build itself would be a major development in the history of technology—one that could bring enormous good for the world

I really can't stand these guys anymore...

> Easy, you don't have subjective experiences because you have body in the first place. You have them because some signals come in from your nerves, which your brain turns into a world model.

Bro, I think we discarded this idea from Platone and Cartesio a while ago...

Your brain is your body.

Your mind is not detached from it, and you can't feel anything, and so have a subjective experience, without it. Neither, your mind, or "soul" could survive to the physical death of your body.

So...I mean...

> Yeah, it's kind of mind boggling that Ted Chiang (of all people!) can't imagine intelligence without a body. and the whole thing just begs a lot of questions.

How can you have a subjective experience without a body?

That's the point, in my opinion: your physical/chemical state (body) in a given moment is then translated into the higher abstraction of the emotion. An emotion that *you* feel, because you are self aware of what's happening.

How can you be self aware without feeling? And how do you feel, without a body?

> The body itself has little effect on the mind other than the inputs from nerves and chemical and hormonal changes.

"Little"...

> I actually enjoy the collaborative programming process, and was pair programming with folks before the term was coined

Yep, the same here, I'm a long pair programming enjoyer, but I'd like to raise that collaboration is usually meant with a human being in the context of pp, and prompting and agent to execute a task is nothing like that.

> but if someone defects to a longer work week they tend to get ahead at work. Thus we all do it and thus we all lose.

A four-day-a-week worker here.

I don't know what you exactly mean, but my personal experience is exactly the opposite. I worked for a startup as a founding engineer, just 4d/w (the CTO was crazily open-minded), and I was never so productive. Doesn't matter that the others were working 5 days, pushing more; it was my responsibility to keep up, and it worked pretty well.

Same now, working for a company with the same arrangement.

And no one is or was "losing."

I'll admit that I found the entire story quite hilarious...maybe a plot for next Guy Ritchie movie?

> the engineers who can solve them will be among the scarcest and most valuable talent in the market.

Reduce the work force of 30%. I don't know, dude, you didn't convince me.

Location: Milan, Italy Remote: Yes

Willing to relocate: No

Technologies: Node.js, Typescript, React, PostgreSQL, MongoDB, Redis, Google Cloud Platform

Résumé/CV: https://www.linkedin.com/in/gdarrigo/

Email: darrigo.g@gmail.com

I'm a senior software engineer with 14 years of experience; I worked with small teams and enterprises, and I successfully contributed to the success of many products, Hire me if you want to onboard a passionate, team player, used to wear many hats, colleague.

> Does nobody else laugh that a company supposedly worth more than almost anything else at the moment, is basically hacking around a load of text files telling their trillion dollar wonder machine it absolutely must stop talking to customers about goblins, gremlins and ogres?

Honestly, when I was reading the article, I couldn't stop laughing. This is quite hilarious!

> You can hire many minimum wage workers who are generally intelligent who dont even go to that level.

That's pretty rude to say, at minimum.

Location: Milan, Italy

Remote: Yes

Willing to relocate: No

Technologies: Node.js, Typescript, React, PostgreSQL, MongoDB, Redis, Google Cloud Platform,

Résumé/CV: https://www.linkedin.com/in/gdarrigo/

Email: darrigo.g@gmail.com

I'm a senior software engineer with 14 years of experience; I worked with small teams and enterprises, and I successfully contributed to the success of many products, Hire me if you want to onboard a passionate, team player, used to wear hmany hats, colleague.