←back to thread

689 points dheerajvs | 1 comments | | HN request time: 0s | source
Show context
noisy_boy ◴[] No.44523098[source]
It is 80/20 again - it gets you 80% of the way in 20% of the time and then you spend 80% of the time to get the rest of the 20% done. And since it always feels like it is almost there, sunk-cost fallacy comes into play as well and you just don't want to give up.

I think an approach that I tried recently is to use it as a friction remover instead of a solution provider. I do the programming but use it to remove pebbles such as that small bit of syntax I forgot, basically to keep up the velocity. However, I don't look at the wholesale code it offers. I think keeping the active thinking cap on results in code I actually understand while avoiding skill atrophy.

replies(9): >>44523200 #>>44523227 #>>44523342 #>>44523381 #>>44523532 #>>44523832 #>>44525241 #>>44528585 #>>44532723 #
emodendroket ◴[] No.44523227[source]
I think it’s most useful when you basically need Stack Overflow on steroids: I basically know what I want to do but I’m not sure how to achieve it using this environment. It can also be helpful for debugging and rubber ducking generally.
replies(4): >>44523343 #>>44523436 #>>44523560 #>>44523787 #
threetonesun ◴[] No.44523343{3}[source]
Absolutely this. For a while I was working with a language I was only partially familiar with, and I'd say "here's how I would do this in [primary language], rewrite it in [new language]" and I'd get a decent piece of code back. A little searching in the project to make sure it was stylistically correct and then done.
replies(1): >>44527167 #
1. emodendroket ◴[] No.44527167{4}[source]
Those kind of tasks are good for it, yeah. “Here’s some JSON. Please generate a Java class I can deserialize it into” is similar.