@searls interesting. Thank you for sharing. I’ve been using the tagline “full cycle” on my resume for awhile. full-breadth might be even better, semantically at least. And for me it’d be slightly aspirational, whereas I’m kinda bored with “full cycle”

@searls very well-put! I don’t think this applies to folks waaaaay down in the technical stack, though. AI still feels very far off from being able to handle the complexity of those tasks. But for product-focused engineering I totally agree.

@searls This is an odd distinction; in 30+ years of doing professional software development I’ve never observed this kind of split. Everyone has a mix of both capabilities & interests. Some may be *excluded* from participating one or the other due to organizational quirks, but this feels like a false distinction.

Also, if you believe you are “scorching through” your backlog with some AI tool, you’re probably fooling yourself & everyone who’s counting your judgement & expertise.