For me, if I can make a kickass testing system that people love so much that they actually build features with it and it’s not an afterthought, then maintenance becomes much easier. It’s often called test driven development but I’ve rarely seen it done in such a way that the dev ex is good enough for it to work.

But say you have that. Then you have great profiling. At that point you can measure correctness and performance. Then implementation becomes less of a focal point. And that makes it a lot easier to concede coding to ai

▲

NotGMan 7 hours ago | parent [-]

This will probably be how things will work in future: devs will shift to specifying features which will be validate through tests.

The AI will then be middle layer that will iterate until tests pass.

Layer 1: Specs (Humans)

Layer 2: Code (AI mostly)

Layer 3: Tests (AI + human checks).

▲

visarga 4 hours ago | parent | next [-]

Yes, that is how I see it too. What I would add is - intent testing - collect user messages, and check them against executed work from time to time. Every ask must be implemented and tested, every code must be justified by a user message.

▲

jplusequalt 6 hours ago | parent | prev [-]

What a boring fucking future.

	▲	bluefirebrand 2 hours ago \| parent \| next [-]
		No kidding. AI does all the interesting problem solving and humans... Write tests. The most boring activity on the planet
	▲	3 hours ago \| parent \| prev [-]
		[deleted]