I dunno. You still have to test, but in my experience if I noticed unreliability during high load I could just tell Claude "I noticed unreliability during high load" and it would easily have set up a high load benchmark, discovered this broadcast channel issue and fixed it.

It definitely improves the results if you do think but I don't think "you still have to think" is a safe space that's going to save us from unemployment.

▲

B56c 3 hours ago | parent | next [-]

Author is saying that some decisions aren't as obvious as "my code should be reliable under high load". Some decisions are tradeoffs that require you to have domain/technical expertise to answer.

	▲	skydhash 2 hours ago \| parent [-]
		And some do require design thinking. Like sndio or alsa, drm, caddy, … With no domain expertise and technical knowledge, a lot of software are out of scope.

▲

catlifeonmars 2 hours ago | parent | prev [-]

> It definitely improves the results if you do think but I don't think "you still have to think" is a safe space that's going to save us from unemployment.

Who said anything about saving people from unemployment?

> I noticed unreliability during high load

This is pretty ambiguous. You still need to provide more context, such as which failure modes you are trying to benchmark.