Hacker News new | past | comments | ask | show | jobs | submit login

Perhaps the methods used to achieve the results or the context in which they were achieved aren't relevant from one position to another? Maybe the methods would reveal a momentary success that happens to be unsustainable?

I feel like your angle here is frustratingly assumptive in the same way as the other response below.

Having seen it twice now, maybe what I'm saying looks just like the symptoms of some "process not results" types you two have seen before, but it couldn't be further from my intent or work in practice.




Your good intentions aren't relevant. This thread is critiquing a marketing message. I'm sure you're great at what you do, but the strategy of producing volumes of well-groomed data about your process will work against you with many managers, and isn't expected by any managers.


You keep referencing things I made no mention of "mentality that carefully-documented work is a substitute for results", "set out to achieve a result and receive instead a detailed log of steps that failed to produce it", "the strategy of producing volumes of well-groomed data".

I don't see how you managed to fantasize all that from my suggestion about the potential utility of an easy, concise way to share what I'm working on and how with someone.

"That's bad idea." - Fine. "No one cares." - Cool. "Don't try to hide your failure to produce results behind a pretty status chart." - What the fuck are you talking about?

That's where the topic of intent came from, you keep baking it into your judgments.

By this point in the tangent I thought the interesting topic was why you seem to think that the work or method behind a specific result is irrelevant?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: