Tom Sharp (@t_sharp) header
Tom Sharp (@t_sharp) profile picture

building brightplace: https://nitter.gq/t.co/o57MI7li9B AI | DevOps | Infra

NYC
Joined July 2017
Photo by Tom Sharp (@t_sharp)
Replying to @MansiCodez
Agreed. I wrote about this today: tomsharp.substack.com/p/in-d…
2
16
Replying to @kritikakodes
yup. Wrote about that recently here. tomsharp.substack.com/p/in-d…
5
Tom Sharp retweeted
Sorry to say but: Vibe coding didn't kill software engineering, it just made bad engineering easier to hide.
38
3
47
2,143
I expect AI to change the job substantially, including how much code engineers write themselves. But if implementation becomes cheaper, being able to decide what’s worth implementing and evaluate the result seems pretty valuable to me.
1
1
It involves figuring out what should be built, questioning the requirements, and understanding how decisions affect the systems around it. Making implementation faster doesn’t remove the need for that judgment.
1
1
Building an app with a simple backend is a different challenge from building a complex production system with strict requirements around reliability, security, and latency. Software engineering is still a discipline learned over years through theory and experience.
1
3
I keep seeing people on X declare that software engineering is dead, usually alongside some vibe-coded app. I don’t think prompting an agent to build an app in a weekend means it’s the end of software engineering.
2
7
Replying to @the_varunrana
I think coffee shops are great for 2-3 hours of deep work. I still don't know how people work from one all day.
1
7
Replying to @Shwinnabego
completely agree. most people will never want to build their own anything regardless of how easy it is. engineers are engineers for a reason - they enjoy spending time learning and building
13
Replying to @ybouane
Restaurants don’t have entire departments of 6 figure salary employees with huge benefit packages. And as everyone else mentioned, margins are slim and many don’t make it. Very different industry from software
1
1
195
Replying to @sandislonjsak
the first part (design) is what separates engineers from vibe coders. I assume most people are trusting part 3 to agents regardless of skill level
1
18
Serious question. Are we going to need engineering docs in the future? If the code is the source of truth and we can understand the code much faster with agents, what purpose do the docs serve?
7
Replying to @the_varunrana
The fact so many companies even still use JIRA is mind boggling to me
2
48
Replying to @builtwithrubel
maybe not programming. but software engineering is more than just writing code. for those who want to go a layer deeper, learning code is still worthwhile. just like in the past SWEs wanting to go a layer deeper learned about hardware
237
Replying to @moiiikaaa
no. try asking your friends who don't work in tech how they would build an api from scratch
Replying to @YashHustle_22
it already writes faster and the code quality is probably on-par or better than most engineers. the issue is design thinking and architecture
41
Replying to @samueljmcd
yes but also it should be updating weekly if not daily 😄
1
1
80
Replying to @thorstenball
agree on most of this. I’ve seen the “we won’t have bugs we’ll just have ‘you asked for the wrong thing’” already with models like Astra
27