
this. coding is the least important part of being a good software engineer. any AI model in 2025 can write the code better than what you are writing. you gotta do more than that
dopefaith_
2.1K posts

@dopefaith1
CS undergrad Powered by caffeine & curiosity https://t.co/sYNYdPEosa

this. coding is the least important part of being a good software engineer. any AI model in 2025 can write the code better than what you are writing. you gotta do more than that


I’ve never fully understood the way people “rank” developers. I often hear terms like “mid”, “cracked”, “10x dev”, but on what metrics people quantity these for a typical software job? In domains like chess, competitive programming, or olympiads, we have clear, objective metrics to measure skill. But in developer role I don't know what parameters we have. Sure, in cutting-edge research like optimizing attention mechanisms in LLMs an exceptional (“cracked”) researcher can have a visible, outsized impact. But in most day-to-day developer roles, what will the cracked dev do different from the avg? A better metric for everyday developer roles is being “reliable.” Someone you can trust to own their tech, step up during incidents, and consistently ship on time



we’ve signed Zero Data Retention agreements with all providers for Go all models now follow a zero-retention policy your data is not used for training

