Ask HN: Why aren't you coding?
231–240 of 316 posts
Re: Ask HN: Why aren't you coding?
#232Mentally spent, in the back of my mind I have this feeling like "why aren't you accomplishing something" but I just literally can't. I can't even watch tv or something I'm just in a bad mood in general today idk what to do, kill time till I fall asleep. Wake up with a fresh brain and then do the hardest thing first. In the end... it is just passing time... I guess I'm lucky I at least have a job that pays... what I b…
Re: Ask HN: Why aren't you coding?
#233Re: Ask HN: Why aren't you coding?
#234My shoulder, shoulder blade, and elbow hurt. Overworked and under exercised. :-/
Re: Ask HN: Why aren't you coding?
#235Not late enough yet. I only code productively between the hours of 10 pm and 4 am. If the baby sleeps. Morning coding time is spent fighting with my inner manager about how to present last night’s work at standup. Afternoon coding time is spent in a stupor wondering why the coffee has no effect anymore.
Re: Ask HN: Why aren't you coding?
#236Earlier quoted context omitted.
> For the same reason our job's don't stop when we go home (or turn off slack) either, we are essentially paid to think and our brains do not care about the arbitrary thresholds set by 9-5. Speak for yourself. Some of us have been there, burnt out and had to rebuild our relationship with work in a healthy manner. I think no matter what you do, if it is thought work and you don't find a wat to turn it off, you are doi…
It's a good point, but, to be fair to parent commenter, they may have meant something different. I think they may be referring to the phenomenon of walking away and having the solution "come to you" while doing something else. It took me a while to appreciate this, but simply walking away is often the fastest way for me to solve a hard problem. There I am, lying in bed, or cooking, or whatever, and BOOM the solution…
Re: Ask HN: Why aren't you coding?
#237007 films
Re: Ask HN: Why aren't you coding?
#238Earlier quoted context omitted.
You aren’t writing up UX requirements. You’re writing system designs. If you’ve never had to write down and get feedback on a system design that is entirely okay, but as you work on projects of increasing complexity and scope, it becomes more and more important to plan before you write. The prototypes you’re describing are primarily useful for UX iteration, not system design.
A short system design doc with a working prototype is vastly superior to a 50 page design doc with no code. Think of it as the scale model of the house in the original example. It’s a way for sake holder to see and feel what they’re going to get.
Re: Ask HN: Why aren't you coding?
#239Re: Ask HN: Why aren't you coding?
#240You're imposing your own incorrect assumptions about what developers are paid to do.