71–80 of 144 posts
"Personally I cannot listen to technical podcasts while I develop software" What? I've never known anybody that could do that! Anyone that can do that meaningfully must be some kind of savant.
"Personally I cannot listen to technical podcasts while I develop software" What? I've never known anybody that could do that! Anyone that can do that meaningfully must be some kind of savant.
I can't listen to anything with words I understand. Podcasts would be ridiculous.
Fuck breaks. I hate them. Stay strong.
At id software they said if you wanted to see something, make it happen on a screen.
Earlier quoted context omitted.
I have to agree with this. You're either writing assembly code yourself, or you're using code that was invented by someone else (and even the assembly code will have been invented by someone!). If using libraries/frameworks is something you do consistently, you can absolutely reach a state of deep work while working with them. Libraries should help keep the flow going at a high level by keeping one from being bogged…
I think you're confusing using a library you've already been using (in which case I agree) and introducing a new library. Most people engaging in NIH aren't removing a library that is already being used in your build process. They're deciding it's easier to implement URL processing (spoilers: it's not) than to use a library that already exists. The exception to that is when the existing library turns out to be a dump…
I don't know how I could function without them actually.
Earlier quoted context omitted.
> blue light that damages your vision Can anyone explain to me how looking at a computer screen is not several times less harmful than spending time outside from a lifetime-blue-light-exposure perspective? The sky is blue and natural light has a blue component in probably about the same proportion as white light from a screen. Maybe I'm wrong — and I'd like to find out if I am — but this whole blue light scare really…
The light & vision story is still being discovered. "How is the idea of "outdoor time" used for myopia control? One of the big surprises of recent research is the importance of how increased time spent outdoors helps in preventing myopia. At the present time it appears that 14 hours a week or more outdoors are significantly effective in reducing myopia progression." http://www.myopiaprevention.org/outdoor_time.html
We need to restrict the amount of hours we spend in front of computers per day and take weekends completely off. There are so many downsides: blue light that damages your vision, lack of exercise, depression and other disorders, missing out on social life, etc. There is a direct relation between productivity and having a life put together. Not taking care of ourselves (programmers) could have lead to disaster: mental…
I've been making an active effort to avoid using my computer at home. 40 hours a week of sitting in front of one is plenty. That's not to say my alternatives are exactly healthier, sitting in front of a computer is probably better for you than drinking pints at the pub.
"Personally I cannot listen to technical podcasts while I develop software" What? I've never known anybody that could do that! Anyone that can do that meaningfully must be some kind of savant.
Upside is that when I'm doing things that don't require high concentration that are kinda boring and easy I get to listen to the podcast while I do it. A faily large chunk of programming is me on autopilot writing things where I know exactly what to do so a podcast isn't a big deal.