766eb43f
senior engineer at a mid-stage startup. heres my typical day:
1. read the jira ticket
2. paste requirements into chatgpt
3. iterate on the output until it works
4. write tests (also chatgpt)
5. clean up and commit
6. write PR description (chatgpt)
i finish my work in 3-4 hours. spend the rest of the day on calls and "code review" (which is me reading chatgpt output from other people who also use chatgpt).
is this the future or am i a fraud
a62481ab
youre not a fraud youre efficient. the skill is knowing what to ask for and how to evaluate the output. thats still engineering. the tool just changed
9d487f64
wait until your company figures this out and realizes they need 3 engineers instead of 8. youre not a fraud but you ARE making yourself replaceable faster
894896d6
"code review which is me reading chatgpt output from other people who also use chatgpt" this is the most 2026 sentence ive ever read
e227ced1
serious question: what happens when chatgpt generates a subtle bug that you dont catch because you dont fully understand the code? thats the risk. and it WILL happen at the worst possible time
f6272763
ive been doing this for a year. the trick is to actually understand what chatgpt writes. if you cant explain every line, youre not using it as a tool - youre just copy pasting from a different source than stack overflow
c390519e
this is why i think coding interviews should change. we should test people on their ability to evaluate and debug AI-generated code, not their ability to write it from scratch on a whiteboard
