Are you a staff level engineer that has dozens of other engineers banging away at code projects you help define?

Try to write a design doc before you implement something (which people find they need to do for LLMs to work at all anyway). You’ll find that you spend much less time actually writing code.

Write proper API documentation laying out the assumptions and intent, generate some good API docs, write a design and architecture document (which people find they need for LLMs to work at all anyway). You’ll find that you spend a lot less time reading code.

	▲	dkersten an hour ago \| parent [-]
		> which people find they need to do for LLMs to work at all anyway Everything we have to do for AI to function well, would help humans to function better too. If you take the things for AI, but do then for humans instead, that human will easily 2x or more, and someone will actually understand the code that gets written.

▲

bborud an hour ago | parent | prev | next [-]

It has varied over the years but it isn't actually relevant since I am talking about when I write software.

Writing code just isn't what takes time.

	▲	QuercusMax an hour ago \| parent [-]
		Getting the code into a state where it actually does what you want takes time - but a lot of that is research, testing, experimentation, documentation, etc. Those can be faster with AI assistance but you still need to bang on it enough to make sure it works right.

▲

kakacik 34 minutes ago | parent | prev [-]

I am not, yet actual coding is miniscule part of workflow. The rest is cca un-automable by any llm - politics, meetings, discussions, brainstorming, organizing testing teams, stakeholders and so on.

This is how big corporations look like, not some SV startups.