Live data from Hacker News

Work for only 3 hours a day, but everyday

plumshell.com

31–40 of 146 posts

Re: Work for only 3 hours a day, but everyday

#31
It reads like someone who isn't doing much of realtime support. This works great for projects that haven't been unveiled or even ones that require little ongoing maintenance like a game. But if I worked 3 hours a day, my clients would crucify me.

Sadly, it isn't always possible.

Re: Work for only 3 hours a day, but everyday

#32
post #19

Earlier quoted context omitted.

On a serious note, this is a terrible habbit. SO code is questionably licenced.

Any questions about the license not answered by this? http://meta.stackexchange.com/questions/271080/the-mit-licen...

I don't think that answers anything. Just because some anonymous poster put code online doesn't make it usable under the MIT license no matter what the ToS of the website says. The poster may have copied that code from a GPL code base...

Re: Work for only 3 hours a day, but everyday

#33

As a freelancer, I understand where some of the comments "As a freelancer this won't work" are coming from. However, the last year I've flipped my freelancing model where I offer a more productized service with a clearly defined scope and set price. Instead of doing design work for $XXX/h, I'll deliver A,B,C within Timeframe Y, for Price $XXXX. With clearly defined services, I've actually been working for the last 12…

That's interesting, what do you do exactly? Designer? Developer? :)

Re: Work for only 3 hours a day, but everyday

#34
post #13

Earlier quoted context omitted.

On the topic of work environment: in one job I worked at, we had the Internet machines completely separated from the work machines. If you needed to check something you had to physically walk over to the Internet desk. Great for focussing on the task at hand without distraction, and considering carefully what information you need.

"Air gapping". https://en.wikipedia.org/wiki/Air_gap_(networking) It's common practice in classified environments, as a necessary security precaution. But it's a true productivity killer imho. Better to just install an extension that blocks twitter/facebook etc, than completely cripple your ability to search for technical information as you need it. Also - good luck installing tools and plugins when you have to start…

After the initial period of adaptation, I found it actually increased productivity. Perhaps it was just preventing already-established bad habits that arise from having the internet constantly available.

Re: Work for only 3 hours a day, but everyday

#35

If I told you that every car needed 8 gallons of gas to drive 100 miles, you'd point out I was wrong - so many different makes and models, not to mention variables from tire pressure to driving style. Yet for the potentially even more complex range that is different people, it amazes me that so much of the advice is didactic - we all need 8 hours sleep, 8 glasses of water, and 8 hours of work with breaks is optimal.…

This reminds me of 7 minute abs:

https://m.youtube.com/watch?v=JB2di69FmhE

Re: Work for only 3 hours a day, but everyday

#36
post #13

Earlier quoted context omitted.

On the topic of work environment: in one job I worked at, we had the Internet machines completely separated from the work machines. If you needed to check something you had to physically walk over to the Internet desk. Great for focussing on the task at hand without distraction, and considering carefully what information you need.

"Air gapping". https://en.wikipedia.org/wiki/Air_gap_(networking) It's common practice in classified environments, as a necessary security precaution. But it's a true productivity killer imho. Better to just install an extension that blocks twitter/facebook etc, than completely cripple your ability to search for technical information as you need it. Also - good luck installing tools and plugins when you have to start…

> Better to just install an extension that blocks twitter/facebook etc, than completely cripple your ability to search for technical information as you need it.

With godoc, man pages, info pages, a local copy of the Common Lisp Hyperspec and Usenet, what more does one need?

Re: Work for only 3 hours a day, but everyday

#37
post #25
post #24

So no going out for drinks where you might have a hangover the next day?

If you really want alcohol, why waste the next day with hangover when you can just drink one or two drinks and be well?

Getting drunk is part of the point. There's no gain in pretending it's not.

Re: Work for only 3 hours a day, but everyday

#38

As a freelancer, I understand where some of the comments "As a freelancer this won't work" are coming from. However, the last year I've flipped my freelancing model where I offer a more productized service with a clearly defined scope and set price. Instead of doing design work for $XXX/h, I'll deliver A,B,C within Timeframe Y, for Price $XXXX. With clearly defined services, I've actually been working for the last 12…

That's interesting, what do you do exactly? Designer? Developer? :)

I'm both, but offer a couple of productized design services. I'm actually right now in the process to figure out if if I'm able to replicate the same model for some dev services. Curious to find out.

Re: Work for only 3 hours a day, but everyday

#39
I have experienced a similar thing while freelancing or design and web development. I used to work 16 hours some days and less hours others, but then sometimes I would need to work and found it hard to kick it into gear.

I think creativity is like a well, and when you do creative work its like drawing that water out. If you use too much water one day, the well runs dry. You have to wait for the goundwater to fill it up again.

Not only did I begin viewing creativity as a limited resource I create and have access to over time, but I noticed that some activities, like reading about science, listening to music, and walking around town actually increase the rate at which the well fills up.

So now I have made it a daily habit of doing things that inspire me, and I also daily draw from the well like the author said - but Im more careful not to creatively 'overdo it' and leave myself unable to be creative the next day.

Viewing it this way has helped a lot, for all the same benefits the author listed. Im in a rhythm where I dont feel I need a break on the weekend, I just still have energy.

Re: Work for only 3 hours a day, but everyday

#40
I agree with this article mostly, although 3 hours a day might be too little to make good progress with work for some people.

This article reminded me of my previous workplace (about 7 years ago) where my manager discouraged engineers from working for more than 6 hours a day. He recommended 4 hours of work per day and requested us not to exceed more than 6 hours of work per day. He believed working for less number of hours a day would lead to higher code quality, less mistakes and more robust software.

Although, he never went around the floor ensuring that engineers do not exceed 6 hours of work a day, and some engineers did exceed 6 hours a day, however, in my opinion, his team was the most motivated team on the floor.

Post reply on HN