I used to think this, until I tried it. Now I see that it effectively removes all the tedium while still letting you have whatever level of creative control you want over the output.

Just imagine that instead of having to work off of an amorphous draft in your head, it really creates the draft right in front of you in actual code. You can still shape and craft and refine it just the same, but now you have tons more working memory free to use for the actually meaningful parts of the problem.

And, you're way less burdened by analysis paralysis. Instead of running in circles thinking about how you want to implement something, you can just try it both ways. There's no sunk cost of picking the wrong approach because it's practically instantaneous.

▲

layer8 a day ago | parent [-]

I’m getting the impression that developers vary substantially in what they consider tedium, or meaningful.

	▲	shawnz a day ago \| parent \| next [-]
		Sure, and that goes even for myself. Like for example, on some projects maybe I'll be more interested in exploring a particular architectural choice than actually focusing on the details of the feature. It ultimately doesn't matter, the point is that you can choose where to spend your attention, instead of being forced to always go through all the motions even for things that are just irrelevant boilerplate
	▲	Groxx a day ago \| parent \| prev [-]
		Shockingly, software developers are people, and are as varied as people are elsewhere. Particularly since it became (relatively) mainstream.