4 Hour Work Week Pdf Download Free
Agalia Valcin
Ferriss developed the ideas present in The 4-Hour Workweek (4HWW) while working 14-hour days at his sports nutrition supplement company, BrainQUICKEN.[3] Frustrated by the overwork and lack of free time, Ferriss took a 3-week sabbatical to Europe. During that time and continued travels throughout Europe, Asia, and South America, Ferriss developed a streamlined system of checking email once per day and outsourcing small daily tasks to virtual assistants.[4] His personal escape from a workaholic lifestyle was the genesis of the book.[5]
The format of The 4-Hour Workweek took shape during a series of lectures Ferriss delivered on high-tech entrepreneurship at Princeton University, his alma mater.[6] The lectures (and book) described Ferriss's own experiences in company automation and lifestyle development.[6]
The New York Times noted that Ferriss spends far more than 4 hours per week in blogging and self-promotion, which Ferriss describes as "evangelizing."[7] USA Today commented: "If it all sounds too good to be true, maybe it is. Or maybe not. Clearly, selective ignorance, farming out chores and applying the 80/20 principle have paid off for Ferriss."[8] Wired praised the book's ideas for remote work and its pre-retirement advice, but faulted it for "formulaic writing" and that "nearly every idea [is] taken to an extreme. No sense of work being anything more than a paycheck".[9] Some reviewers noted that the book was quite lengthy and hard to read.[10] Leslie Garner of The Telegraph noted that the book had a "punchy writing style" and that Ferriss had "struck a chord with his critique of workers' slavish devotion to corporations."[11] Meagan Day of Jacobin criticized the book for advising readers to "become a fake expert."[12] Jimmy Wales, cofounder of Wikipedia, said that he secretly moved to Buenos Aires, Argentina for a month after reading the book.[13]
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
Early Agile practices included a 40-Hour Work Week to improve productivity and sustainability. By setting some basic boundaries that were more human-centered, the goal was to create a better place to do great work.
It was easy to see that adding more hours didn't help productivity very much. Instead, working long hours easily lead to work-life imbalance, burn out, and in many cases, lower performance (because people got sloppy with their time, lost focus, lost momentum, etc.)
So, out went the 40-Hour time budget to spend wisely, and instead it became a focus on how to survive longer days. (It's kind of like the advice of, "Don't spend too much money." vs. "Here's a $100, spend it smart.")
Instead of perpetual fire-fighting, they are more deliberate about planning and strategy and they anticipate their customers and the market (through empathy and staying connected to customers.)
To make it worse, when I joined Microsoft, I was surrounded by passionate people who also worked well beyond a forty hour work week. I was in the zone. Not just that, I was spending my time in my passion, so I never burned out.
My second taste that this was a problem was when I joined patterns & practices. After my first few projects, my manager told me I needed to find a way to work a maximum of 40 hours and produce the same or better results.
This also had an amazing set of by-products, including achieving work-life balance for all team members, helping people spend more time in their passion and strengths, reducing downstream risk and surprises, and keeping the energy strong across the team in a more durable way.
It also helped us improve our daily, weekly, and monthly rhythms of results while improving our team practices and procedures. We basically moved up the effectiveness stack and it got faster each time we had to build a new team.
Start with yourself, then help other people. Focus on finding more effective ways to do things, focusing on the vital few things that matter the most, playing to your strengths, and improving your energy. Know what counts and be able to put your finger on it.
In this case, overtime is paid (per FLSA) after 53 hours in a week, meaning the salary is compensation for the first 53 hours every week. Yet, they use a higher number to divide by (56), which results in a lower hourly rate.
Not a labor lawyer, but I believe if the employer (State) and the labor representative (2881) agree to it then it is allowed. My guess is that if 2881 had ever said no in a contract (thus immediately enacting a 53 EDWC clock), then the state would take away/not agree to certain other benefits/raises that were granted in past contracts.
However I agree that this anachronism of years past should have been done away 20+ years ago. Back in the dot com boom I was arguing this should be the number one priority. If 2881 ever wanted to start bargaining on an equal basis in regards to all other 56 hours/week fire departments, they needed to get their calcs in line with them, otherwise it makes comparisons very difficult.
The 66 hour work week is the dumbest thing ever. You will still get held on you will lose $1000 a month not to mention that is pers able income that 12,000 a year pay cut for getting 12 days off a year not worth it. There are alot of other things at effect this do your home work kids before you wish for this.
RE: Loss of Money
I understand members concern about reduction in PERSable income. Couple observations. Anyone can be a sceptic (sometimes its healthy), but it is also healthy to base your views on observable facts.
To add to this, even if there were to be a GSI to offset the loss of PERSable income, inflation continues in the background, so, to me, keeping the same PERSable income as last year equates to an effective cut equal to 4% or whatever inflation has been over the last year.
It seems like each bargaining session begins with the mentality that in order to gain something, we have to give something up. I disagree with this approach and feel like beginning with this as the basis sets the stage for it to be acceptable to give, give, give. There is so much that has been given back or foregone over the decades that has led us to where we are today.
Last week I set out to see how many hours of programming work I could do in one week on CodeCombat, our multiplayer programming game for learning how to code. I clocked in at 120.75 hours. Here's the epic time-lapse video I generated from Telepath (watch in 1440p if you can):
I usually sleep for 8.5 hours a night. I thought that for this week I could be tricky, starting at 04:00 and sleeping later and later so I'd only have to sleep six times for maybe eight hours a pop. Not only did it totally work, but my wake times didn't advance as fast as my bedtimes, so I only lost 6.38 hours per day to sleep.
I thought this would make me tired and unable to concentrate on difficult programming, but energy and focus were actually really good except for one hour early Sunday night. I blame it on epic Viking metal and other super-energizing music, plus maybe the seven bars of 90% dark chocolate I ate. I had one or two cups of tea but no other caffeine, and I woke without an alarm every morning.
I hadn't realized I how much more I enjoy coding when I don't have to answer emails for a week. (Note the unread emails climb to 402 by the end.) Even fixing bugs, supporting Internet Explorer, and struggling with algorithms I don't understand are all fun when I know I'm going to win--that I'll solve the thing before anything can distract me. And listening to music is one of my favorite things, so having a week filled with just code and music? Wonderful!
Normally, I work a focused-but-relaxed 60 hours in a week. I doubled that last week, but I feel like I was perhaps three times as productive. I could keep the problems in my head without cache eviction due to memory pressure. (I mean, there wasn't anything else to think about.) With ever-deepening focus, I felt unstoppable. It was like getting 4.5 40-hour weeks' worth of work done in one.
Most nights last week I programmed in my dreams, with vivid Tetris effect one night of doing CSS tweaks. (One night I had a nightmare of watching a YouTube video and then panicking upon realizing I wasn't working.) Being that deep into my CoffeeScript, I found myself writing terser and terser code, since why do in five lines what you can obviously do in one? But as I coded, I didn't realize until too late that "obvious" is different between just-spent-120-hours-coding me and just-went-skateboarding me, let alone people are not me and may not even know CoffeeScript if you can believe that. Here's an example from spell_view.coffee:
I don't even want to show you what the old code was, because it was uglier than a cowbear. But it was three times this long and did half as much. To me, this new code is luscious. But can a sane coder really understand this? Where are all the commas and braces and parentheses clarifying the operator and method call and array precedence?
I had the idea to do this week a few months ago, but I wanted to wait until I could buy a freshly updated MacBook Pro to do it, since the old one was three years old and, though capable, pretty slow. After the laptop upgrade, I was surprised by how much more I wanted to work. The simple friction of slow builds and poor CodeCombat level simulation performance had been weighing down my enjoyment and efficiency this whole time. I'm never waiting three years to upgrade my gear again.
Man barely moves for a week, staring at patterns of light on a flat object and trying to make the patterns change. Every 2-4 hours, a stimulus is presented and he records how happy he is. He eats and sleeps as fast as he can so he can go back to looking at the lights.
c80f0f1006