News for hackers. Stuff that matters.
Re:"Don't f***ing trim the copy" by kevinburke on Friday July 06, 2012 @01:38AM (#4206473)
Sure, but the OP's main problem was that he didn't communicate his opinions back to the person who'd worked so long on the copy.
Re:"Don't f***ing trim the copy" by josephcooney on Friday July 06, 2012 @02:15AM (#4206599)
I don't think they should need to. You set up a situation where we can't touch the home-page without consulting Mike, or we can't change that data access code without talking to Sue about it. Do stuff. Make mistakes. Iterate.
Re:"Don't f***ing trim the copy" by jklp on Friday July 06, 2012 @03:08AM (#4206705)
I disagree. If your team is senior enough, I think it is very important to give people delegated areas of responsibility. I've found people start to take pride in their work when this happens, because they know the buck now stops at them, and any outcome (positive or negative) is their own doing.

If you have everyone putting fingers in everyone else's work, why would you want to spend a week working on something when you know someone could just come in and undo it on a whim?

In saying that, it doesn't mean people shouldn't take feedback, though eventually, you'll have to start trusting your team to make decisions for the business. As a founder, you can't go around making every decision for your company, it doesn't scale that way.

Re:"Don't f***ing trim the copy" by josephcooney on Friday July 06, 2012 @03:31AM (#4206759)
At a certain size, maybe, but for a 2-week seat-of-your-pants getting ready to pitch to VCs sprint I don't think delegated areas of responsibility, or exclusive ownership is warranted or healthy. I think if you go and stomp over someone elses good work you need to be responsible for that, but I think you need a team/organisation where you have that freedom. By the downvotes it looks like I'm the odd one out here. Whatever.
Re:"Don't f***ing trim the copy" by wpietri on Friday July 06, 2012 @07:59AM (#4207358)
I think you can still iterate and stay in touch. Indeed, I think that's the best way to iterate.

The problem wasn't the copy changes. It was not demonstrating sufficient respect for the other person's work. If he had emailed the colleague with a note as he started tinkering ("Great work on the landing pages; I'm going to see if I can tighten the prose up a bit.") and then sent her the diffs, there shouldn't have been any upset.