i think its more nuanced than "is" or "isn't." an architect does't pour the concrete. the gap between me or claude comes down to the architectural decisions. ta

i think its more nuanced than "is" or "isn't." an architect does't pour the concrete. the gap between me or claude comes down to the architectural decisions. take a large functional spec in jira for example, any developer can pick up a ticket, but they aren't steering the product. i have zero issue with claude or anyone doing mundane dev tasks to pull off a product im trying to make. but i guess if you want to say you typed every byte, thats a personal preference. i guess i agree if your one shot prompting software, sure, you're still making but not really coding. i see claude as my agentic pair programmer not "the" developer and most of my software is archicted by me and written the way i would. one thing i like to do is point it at my code bases so it can pick up on my stylistic choices.