Hi! Thanks for the comment. Indeed, some, if not most, are using LLMs in their daily activities. They have access to GitHub copilot, and there were pilots with other tools like Claude Code, recently.
Generally speaking, these folks are empowered to make their lives better and more productive through LLMs. There are a few things to consider, though:
1. It’s not the same a brand new codebase vs a big, existing one. Context management helps, but you also need to invest a lot on it. Especially legacy projects. Bear in mind that producing code is part of the job of a Software Engineer but not the biggest chunk, especially in legacy apps. Observability, setting up good cloud infrastructure, etc is still there. I think there’s also room to improve it with LLMs but we must also acknowledge we’re in the early days, although it does not seem so.
2. When you work for a bigCo, there are tempos. Approvals, budget, licenses… All of this makes the adoption of these tools a bit slower than wanted.
3. Finally, there’s a cultural change. A lot of great SWE, even on HN, despise the idea of having someone writing code for them. “It’s bad code”, etc. We need, as an industry, to make sure we get the most out of the available tools, and be proficient with them. So, this is a more cultural/people’s problems. And these are harder than vibe coding.
I’ve spent the past three years "vibe coding" with LLMs, building side projects I wouldn’t have had time to ship otherwise. Along the way, I’ve learned how to structure context for ChatGPT, utilize PRDs to minimize rework, and address areas of weakness, such as testing.
It doesn’t feel like "magic" anymore, but it does feel like a real productivity boost. Wrote up the reflections + shipped projects in this blog post.
Adevinta | Barcelona, Spain or Remote (GMT +- 4h) | Full time
Site Reliability Engineer @ Common Platform Runtime (CPR) | 40.000-70.000€/year + bonus and other perks | We offer relocation and visa, if needed.
CPR operates a managed multi-cluster, multi-tenant Kubernetes runtime. We run thousands of containers for teams across Adevinta.
We think that running containers in a K8s cluster isn’t cool. Do you know what’s cool? Running them in multiple clusters and being able to resist cluster failure.
Do you want to know more about how we do it? Let’s talk [1]
---
Adevinta [2] began its journey as a standalone company in 2019, as a global online classifieds specialist, operating digital marketplaces in 11 countries. We provide technology-based services to connect buyers with sellers and to facilitate transactions, from job offers to real estate, cars, consumer goods and more.
Our portfolio includes more than 30 digital products and websites, attracting 1.3 billion average monthly visits.
During 2020, Adevinta agreed to buy eBay Classifieds Group [3] to become the largest pure-play online classifieds company in the world.
Generally speaking, these folks are empowered to make their lives better and more productive through LLMs. There are a few things to consider, though:
1. It’s not the same a brand new codebase vs a big, existing one. Context management helps, but you also need to invest a lot on it. Especially legacy projects. Bear in mind that producing code is part of the job of a Software Engineer but not the biggest chunk, especially in legacy apps. Observability, setting up good cloud infrastructure, etc is still there. I think there’s also room to improve it with LLMs but we must also acknowledge we’re in the early days, although it does not seem so.
2. When you work for a bigCo, there are tempos. Approvals, budget, licenses… All of this makes the adoption of these tools a bit slower than wanted.
3. Finally, there’s a cultural change. A lot of great SWE, even on HN, despise the idea of having someone writing code for them. “It’s bad code”, etc. We need, as an industry, to make sure we get the most out of the available tools, and be proficient with them. So, this is a more cultural/people’s problems. And these are harder than vibe coding.