Let's not rush to such judgment - our desires change as we age, the field has changed (including what nose-to-the-grindstone coding looks like) and burnout affects many.

Plus, some people enjoy the rigors of solving in-the-weeds code problems and others enjoy building systems-level designs. This was always true.

▲

okdood64 5 hours ago | parent | next [-]

Exactly, thank you. I'm much more interested in how systems interact gracefully, addressing failure modes and building for resiliency/scale.

Do you need good quality code to do that? Sure, but that's just another line-item on the laundry list of things to make it happen.

▲

hparadiz 6 hours ago | parent | prev [-]

You guys act like the React component nonsense from the past 10 years is the same as the code I was learning at age 16. It's by far and away completely different. And none of it has been audited by Daybreak.

	▲	hedgehog 5 hours ago \| parent \| next [-]
		I'm very happy to let the robot handle any incidental React or other extraneous tools that end up adjacent to the core work I'm doing. It avoids getting blocked without interrupting teammates or spending time and cognitive capacity on stuff that has no lasting value in my work.
	▲	radlad 6 hours ago \| parent \| prev [-]
		That's precisely my point when I say the field has changed even for "true code writing."