3 ms·

I think t-shirt sizing is madness. "How long is a piece of string?" But we've had tickets to create other tickets, because, as you point out, speccing out the

I think t-shirt sizing is madness. "How long is a piece of string?" But we've had tickets to create other tickets, because, as you point out, speccing out the feature (including what does it do and what does it not do) is itself a ton of work In fact I wager that coding is...20%, maybe 25%? of the work that goes into providing value*? So Amdahl's law says having AI optimize that part isn't going to move the needle all that much *it's certainly possible to expend lots more effort coding, but is it coding in the right direction?

bluefirebrand 1y ago
> In fact I wager that coding is...20%, maybe 25%? of the work that goes into providing value Ehh... I've heard this sort of reasoning before and I get where it comes from, but I'm not sure I agree. It feels like "Idea Guy" propaganda to overvalue their contribution. Figuring out what to build doesn't provide real value at all imo. It provides theoretical value. Coding is closer to 100% of the work that actually provides the value Edit: This is why people who actually have skills to build things are made to sign NDAs and Non-competes when hired or before being pitched projects. The ideas people want to keep the value of their idea and undervalue the skill of actually building things
- anonymars 1y ago
  I am in no way saying "the idea guy" is doing 80% of the work, that's probably less than 10% Put another way -- genuine question to which I have only a guess: who does more coding during an average day? A junior developer or a senior developer? Broadly I'd posit the junior developers do a lot more coding, and the more senior you get the more important "English" becomes over any programming language. Maybe I'm in an aberrant bubble. But I doubt it. > This is why people who actually have skills to build things are made to sign NDAs and Non-competes when hired or before being pitched projects. So what I'm getting at is, my version would be: "this is why senior developers code less than junior developers"

bluefirebrand 1y ago

> In fact I wager that coding is...20%, maybe 25%? of the work that goes into providing value Ehh... I've heard this sort of reasoning before and I get where it comes from, but I'm not sure I agree. It feels like "Idea Guy" propaganda to overvalue their contribution. Figuring out what to build doesn't provide real value at all imo. It provides theoretical value. Coding is closer to 100% of the work that actually provides the value Edit: This is why people who actually have skills to build things are made to sign NDAs and Non-competes when hired or before being pitched projects. The ideas people want to keep the value of their idea and undervalue the skill of actually building things

anonymars 1y ago
I am in no way saying "the idea guy" is doing 80% of the work, that's probably less than 10% Put another way -- genuine question to which I have only a guess: who does more coding during an average day? A junior developer or a senior developer? Broadly I'd posit the junior developers do a lot more coding, and the more senior you get the more important "English" becomes over any programming language. Maybe I'm in an aberrant bubble. But I doubt it. > This is why people who actually have skills to build things are made to sign NDAs and Non-competes when hired or before being pitched projects. So what I'm getting at is, my version would be: "this is why senior developers code less than junior developers"