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'm searching for a small, compact team where I can have an impact. I'm actively looking because the company I work for is laying off.
> My workflow has changed since adopting async programming. I now work on four or five tasks simultaneously: one complex problem synchronously and three or four in the background.
Someone, please, try to convince me why this is a positive thing.
Perhaps the background tasks are ones with obvious solutions? I use Claude code to write boilerplate terraform for me as I know what it should look like and I often don't want to write it myself as it is not novel or exciting. I could see the argument that I batch a couple of these out to AI, focus on something more complicated, and then come back later to essentially code review them or make necessary adjustments.
One thing is reversing a linked list during a white board interview.
Another write a simple JOIN between two tables.
Come on guys, working on backend applications and not having a clue about writing simple SQL statements, even for extracting some data from a database feels...awkward
With NOSQL becoming more ubiquitous (for better or worse), it's not unfathomable that someone simply never had an opportunity to do something as simple write a join between two tables. Someone replied to my comment and taught me how in 5 lines of code. I read it and I'm like, oh that makes sense. Cool. I won't remember it exactly but I understand it. I wouldn't hold it against a front-end developer who's only ever worked with Vue to understand what happens when a React node rerenders.
My point is that there are acceptable levels of abstraction in all parts of software. Some companies will have different tolerances for understanding of that abstraction. Maybe they want a front-end dev to understand the CSS generated from tailwind. Or maybe they want them to know exactly what happens when a React node is rerendered. Or maybe the company doesn't care as long as the person is demonstrably productive and efficient at building stuff. What some consider basic knowledge can be considered irrelevant to others. Whether or not that has lasting consequences is to be seen, but that just brings us full circle back to the original problem at hand (is it good that people can vibe code something and not understand the code it generates)
And that's fine, it's your choice.
But everything, driven by multiple forces (from hype, to marketing, to real progress, to early adopters) is pointing to that future.
Yes, another web3, crypto and nft "inevitable" futures. Just give Sama a couple more trillion and AGI is juuuust behind the corner.
It's a fact models aren't getting as cost efficient nor better with the same rate that the costs increases of training and running them. It's also a fact that they are so unprofitable that Anthropic feels like they gotta rug-pull your Claude tokens (https://news.ycombinator.com/item?id=44598254#44602695) without telling you, let's just ignore those facts and fanboy with wide-closed about that future.
A future framed as "inevitable" by a bunch of people whose job/wealth depends on framing it as such. Nah, hard pass.
It’s not. It’s like I used to play baseball professionally and now I’m a coach or GM building teams and yielding results. It’s a different set of skills. I’m working mostly in idea space and seeing my ideas come to life with a faster feedback loop and the toil is mostly gone
I also think that mental clarity comes from a lean, blank sheet of paper, instead of a useless pile of accumulated knowledge.
I'm still familiar with the act of deleting, which is liberatory: destroying drawings, writings, trashing things from the past, pictures, and deleting graffiti.
I don't want to be productive, I don't care about being able to access a thought from 7 years ago to do...what? I don't want to summarize, I don't want a stupid LLM to dictate my knowledge. I'm a human being, I change, I forget, I can fail, I'll die, and that's it.
I'm a senior software engineer with 14 years of experience; I'm searching for a small, compact team where I can have an impact. I'm actively looking because the company I work for is laying off.
reply