Live data from Hacker News

It’s Never Going to Be Perfect, So Just Get It Done

nytimes.com

41–50 of 135 posts

Re: It’s Never Going to Be Perfect, So Just Get It Done

#41
The problem with the headline is that if you think ‘it’ isn’t good enough, then ‘just getting ‘it’ done’ will send you into a vicious loop that will spin out of control as the pressure to over-achieve builds up.

You really have to reframe your view of ‘enoughness’ in a more positive light, so instead of something being perfect (not enough until then), it’s finding a way to see what is good enough for the time being, that allows you to move on. Then you can go and do what you need (or do nothing if what you have is adequate) and take the weight off your shoulders.

The startup lingo for this is MVP. There’s no getting it done with that until you’ve reduced the scope of ‘it’.

Re: It’s Never Going to Be Perfect, So Just Get It Done

#42
There are several kinds of procrastination, so it's impossible to generalize.

Some projects require very large time commitment to get right, reworking several times, etc. Some others reach a diminishing return stage very quickly and continued effort is wasted. You definitely shouldn't just take whatever you have in front of you and just rush it until it's barely workable.

The critical skill is to be able to judge without anxiety and with some precision how much additional time is going to improve the outcome, and what is the rough global value (to you) of this improvement. Some projects have long ramps of effort and refinement, some are just not worth the time and can arrive at a good enough stage very quickly.

I think the best advice I could come up with is that if you're having this sort of problem, recognize it, try to deal with the anxiety and get a perspective on the risks vs benefits, and improve. If possible find an environment/hobby /side occupation where you have to make a ton of such decisions to get a lot of practice. College/personal projects tend to be pretty sparse and give a lot of room for failure and delaying I guess.

For me it's been a very slow, progressive realization that I'll never get things I wanted done by just leaving them to an arbitrary later date, or obsessing too much over details. In nothing vs something, something wins.

Re: It’s Never Going to Be Perfect, So Just Get It Done

#43
I had the same negative reaction to the title that other commenters had, and of course I was thinking about software. But then I opened the article and saw a picture of a canvas and my mind shifted to music.

I know lots of people who love to write music or want to write music but can never get anything done because of a feeling that it has to be perfect. I have always embraced an aesthetic of rough imperfection in my music and (I suppose) as a result I have record over 30 albums and EPs. Sure, lots of that music is, well, cringe-worthy, but there are some gems in there that wouldn't exist if I let perfectionism get in the way of _production_.

Re: It’s Never Going to Be Perfect, So Just Get It Done

#44

Earlier quoted context omitted.

"Mediate" and "journal" are two specific solutions. The general answer is "figure out what's stopping you from getting something done and take steps to mitigate or reduce it."

I've found that I'm generally more productive and happier when I both meditate and journal, but I can't say which way causality flows

>I can't say which way causality flows

In my personal experience, it flows both ways. It's a positive feedback loop. When I'm productive, I'm happier, even if being productive means meditating or practicing mindfulness (as long as the dread that comes with "wasting time" is not there, all good), and when I'm happier, I can be more productive. The hard part, for me, was getting the loop started, pushing the rock down the mountain, so to say, getting past the first hurdles of procrastination. What helped me was getting professional help and medicine, but I was a pretty bad case.

An analogy I have used to describe this to family before was an internal combustion engine. Normally, once you get an engine started and keep supplying it with fuel, it'll keep generating everything else it needs to keep running. But it still needs a battery and a starter motor to get it running in the first place. Sometimes just getting it running is good enough, and most engines start with one crank, but other times, something is not quite right and it takes a couple of cranks and maybe some starter fluid to get it started. Even once you get it started, maybe the alternator is faulty, so until you get that fixed, you have to keep supplying electricity some other way to keep it running.

Re: It’s Never Going to Be Perfect, So Just Get It Done

#45
post #14
post #13

Earlier quoted context omitted.

The part I’ve always had trouble with is you need a certain amount of polish before the idea is acceptable. The quality of delivery heavily influences people’s perceptions. So this is a very fine balance.

Quality is local optimization, Market Fit is global optimization. As the saying goes, if you're not embarrassed by v1 you waited too long to launch.

[deleted]

Re: It’s Never Going to Be Perfect, So Just Get It Done

#46
post #36

Earlier quoted context omitted.

> pretend-work I pretend I'm live streaming my programming session, it seems to cause some switch to flip in my brain and seems to help. Maybe I should actually live stream? But I probably wouldn't have real viewers, and don't know how to fit multiple monitors into a stream.

I'm convinced that the majority of the value from pair programming (literally sitting next to each other, not "virtual" pair programming) comes from the fear of looking like a lazy idiot in front of the other programmer.

^that + usually when you pair program, you try to explain your thought process and reasons behind the decisions you make to another person, and in doing so, you actually end up delivering. And learning the material through explaining it to others is a very effective and very known technique, so that makes sense.

Re: It’s Never Going to Be Perfect, So Just Get It Done

#47
post #13
post #10

Earlier quoted context omitted.

Perfectionism is great when you know exactly what the customer wants (like a custom made shoe). It wastes too much time when you're experimenting to find out what the market wants.

The part I’ve always had trouble with is you need a certain amount of polish before the idea is acceptable. The quality of delivery heavily influences people’s perceptions. So this is a very fine balance.

One of the recent entrepreneurial posts here mentioned a question like "do your users know how much they are suffering for lack of your product right now?" and I think that related to polish.

If you have a machine that cures baldness you don't need polish. The knobs can be any color you want and give the user little electric shocks it doesn't matter. Nothing like this exists and potential users really know they want it.

Re: It’s Never Going to Be Perfect, So Just Get It Done

#48
post #9

At least in software "getting it done" is only half the problem. The real problem is knowing how to find a balance between good enough and catastrophic long term consequences. It's a balance between tactics and strategy. The approach is different in other disciplines such as artistic creation where blind confidence in what you are doing is a better long term strategy and we give a lot more importance to tactics. The…

This comment speaks to me. I'm in a weird point at my job where I'm right at the tail end of supporting this legacy app I've worked on for years, and a brand new app my team will be building from scratch. It's pretty surreal, because I've been dealing with many of the negative long term effects of decisions that were made for this app years ago, meanwhile I'm about to have to make a whole host of similar new decision…

I'm sure you learned a lot about the problem from maintaining the legacy app.

There is some intuition that develops over the years, but honestly the only reliable way I've found of knowing how to properly solve a problem is solving it multiple times.

Re: It’s Never Going to Be Perfect, So Just Get It Done

#49
post #47
post #13

Earlier quoted context omitted.

The part I’ve always had trouble with is you need a certain amount of polish before the idea is acceptable. The quality of delivery heavily influences people’s perceptions. So this is a very fine balance.

One of the recent entrepreneurial posts here mentioned a question like "do your users know how much they are suffering for lack of your product right now?" and I think that related to polish. If you have a machine that cures baldness you don't need polish. The knobs can be any color you want and give the user little electric shocks it doesn't matter. Nothing like this exists and potential users really know they want…

Consider a hypothetical low quality situation with this product.

A guy running up to you on the street offering yellow colored baldness pills in a baggie. Sure they might work, but you’re not going to be the one to find out. The inventor, after many failed sales, may erroneously conclude there's no market for this product.

Re: It’s Never Going to Be Perfect, So Just Get It Done

#50

I had the same negative reaction to the title that other commenters had, and of course I was thinking about software. But then I opened the article and saw a picture of a canvas and my mind shifted to music. I know lots of people who love to write music or want to write music but can never get anything done because of a feeling that it has to be perfect. I have always embraced an aesthetic of rough imperfection in my…

For artistic creation I always come back to this anecdote from the book "Art and Fear":

"The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality.

His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: fifty pound of pots rated an “A”, forty pounds a “B”, and so on. Those being graded on “quality”, however, needed to produce only one pot – albeit a perfect one – to get an “A”.

Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity. It seems that while the “quantity” group was busily churning out piles of work – and learning from their mistakes – the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay."

Post reply on HN