12 ms·
Maker's Schedule, Manager's Schedule (2009)
- jbob2000 9y agoThe problem I have now is; How can I get the manager to read, understand, and respect Maker Schedule? Should I send them this link and then try to explain to them who Paul Graham is and why they should care about him? Should I send them the wikipedia article about Flow[1]? Should I show them the clip from The Social Network about "being in the zone"? [1] https://en.wikipedia.org/wiki/Flow_(psychology) https://en.wikipedia.org/wiki/Flow_(psychology)
- codingdave 9y agoMaybe you should treat both schedules as equally valuable, while acknowledging the different purposes they serve, and respectfully discuss the problem with your manager to collaborate on a solution together. It could be as simple as "Please don't schedule meeting mid-day." When I was a 50% manager / 50% dev, I blocked off 10-2 forever on my calendar for my coding. Whatever you end up with, talk, don't send links -- sending links to articles comes off about as well as sending your fellow devs to LMGTFY.
- brazzledazzle 9y agoThey’ll agree because it’s reasonable and makes sense but the real test will be if they ask if they can book over that big maker block, just this once. And this once. And this project is really important so just this once. It’s like technical debt. No manager is going to disagree that it’s important. But the test is if they ever make time for it or drop the story for something else.
- rumpope 9y agoYes, all these things do help and you can also speak their language - they understand having multiple "back to back" meetings, so you if you schedule meetings with yourself, that you can't miss, and open up your schedule for other times, then you can allow them to book you then.
- jermaustin1 9y agoThis is exactly what I learned after years of developing around meetings. Block your time first. And block your time based on your tasks you have to complete. Sure you can't completely rewrite the billing system from scratch in an hour, but you CAN stub out the new architecture. Then each hour after that you fill in a method. I feel needing 4-9 hour blocks of time means you AREN'T focusing, not that you are "IN THE ZONE"
- maxxxxx 9y agoI can't do anything with some complexity in one hour increments. I need days (or weeks) to immerse myself into the issue to develop a mental model. In my view working in short increments leads to very superficial work.
- deleted 9y ago[deleted]
- annywhey 9y agoI think I know what parent is getting at. I am increasingly able to bypass the "load problem into brain" stage by reducing the problem scope to a subset. When the problem seems potentially quite large, like "greenfield a new system", I look for "seven plus/minus two coherent concepts": while I can't know the whole scope until development begins, I can pick a set of concepts that I can commit to memory(hence, about 7) and search for an optimization of which concepts I'm using that makes each one cohere better with the others, contingent on whatever belief is driving the need for a software solution. This process typically only takes a few hours at most and usually illuminates something really unexpected about the problem space. Selecting for coherence is effective at reducing problem scope since it cuts through unquestioned practices: in a more coherent solution all the answers feed into each other. In my previous methods I would just sit and stare at the problem and sit and stare at techniques until a match of technique to problem came to mind. That's why it took so long - there wasn't a philosophy there, so my thinking could drift in an undirected way for long periods and even get deep into writing code without doing anything effective.
- reggieband 9y agoI find this comic is helpful: https://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt-a-programmer/ https://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt...
- andyidsinga 9y agoI'm sending this to my wife!
- codemac 9y agoTaking notes in a digital lab notebook (i.e. text file) while I'm thinking has sped up the re-inflation period significantly from ~1/2 hour to ~1-5 minutes. I can highly recommend it for folks in very noisy/distracting environments. It also points out how much you struggle to stay focused if you are not continually writing in your notebook.
- wool_gather 9y agoUnfortunately I'm not sure that explains it in any way that a non-maker would get. It's basically missing the last panel, where the dev writes a _new_ bug that costs millions of dollars because of the distraction.
- willholloway 9y agoMaker Time is an alternative time keeping system I designed after being inspired by this essay. http://willholloway.net/makertime.html http://willholloway.net/makertime.html
- codetrotter 9y agoOn mobile it’s just showing the number “751” on the middle of the page, the text “maker time” and a background picture of earth seen from space. Is this how it is supposed to look? If so, what does it do?
- schrodinger 9y agoOn desktop there's a "What is Maker Time" link that provides the following: Your clock has it backwards. Time is infinite, but our time on earth is not. Clocks should count down, not up. Time keeping should be based on meaningful celestial events like the year (one earth rotation around the sun) and the day (one rotation of the earth) Each unit of time should be based on a viable period of work for makers. Maker Time is reset on January 1st each year. The year is divided into 1095 blocks (1098 in leap year). Every 8 hours the count decreases by one.
- nategri 9y agoOldie but a goodie. Play it again, Paul.
- thaumaturgy 9y agoI've had to juggle the two schedules he describes for about a decade now. I haven't been wildly successful, but there are some tactics that seem to make it work okay. - Write code in smaller chunks. This has been a huge change in how I do software. Almost all my code now starts out as an outline in a series of comments: "// do this", "// then do that". I write software "outside-in" now; if I need to slurp a file in one format into a database in another format, I start with the bits that read the file, then add the code that translates/interprets/processes the data in the file, then separately add code that talks to the database, then glue it together. At each step I dump output to the screen. So, I start with a stupidly simple file-dumping program and iterate it until it does the whole job. - Write less code. Find a framework that you get along with, and stick with it. This takes away all the joy of learning new things, but you can still get work done. Develop and nurture your personal code library like you're tending to a garden; your personal code library should be highly modular, and as simple as possible, so that you can use pieces of it as often as possible in your projects, so that it's constantly being improved. Reuse as much as you can from each project. - Do your thinking on the toilet. Or in the shower. Challenging programming often has two separate aspects, the part where you try to understand the problem you want to solve, and the part where you write code to solve it. You don't need to be in front of a computer to do the first part. Likewise, when you're in front of the computer, try not to do the second part -- just sit down and bang out code under those outline comments for as long as your schedule allows. - Keep a notepad nearby. I carry a Remarkable everywhere now. I can sit in a meeting and write things on it and it's a lot less rude than typing on a laptop or my smartphone. People probably figure I'm just taking notes in the meeting, but I can be flowcharting or braining out the next piece of code. A paper notebook works fine for this too. - Aggressively guard what's left of your productivity. My cell phone sits behind me or out of sight; my email tab is closed or on another virtual desktop; headphones are in. Any problems that I regularly encounter in my development environment get time set aside to permanently solve them in a way that's convenient for me. If I find that I need to be able to rapidly switch between different versions of some software, I work and work on my tooling until it's just a short commandline statement to do it. As a recent example, managing unique random passwords for everything was starting to cause a little bit of friction; a few dozen times a day, I had to switch to KeePass, scroll down to or search for the appropriate password, copy it, switch windows, paste. The other day, I wrote "pcp", for "password copy", which takes the title of a password for an argument, opens my KeePass file, locates the password, and copies it to the clipboard. I only touch the KeePass UI now to update the file. - And finally, say no sometimes, or push back a little bit on your boundaries. If you can, find a place to work where you're most productive, whether it's a different office in the same building (so that co-workers aren't popping their heads into your workspace), or from home, or a coffee shop. Make yourself unavailable once in a while so you can get caught up. Take time away so that you're not also fighting off the inevitable fatigue from doing lots of context switching all day long. Avoid getting talked into meetings that are optional where you aren't likely to have much influence.
- karthikb 9y agoI've tried to keep this top of mind for my team. It hasn't been perfect, but: (every 2nd) Mondays - Planning Tuesdays - some meetings for followups, sparingly Wednesdays - NO MEETINGS ALLOWED (screaming intentional) Thursdays - some meetings for followups, sparingly Friday - NO MEETINGS ALLOWED (screaming intentional) Works fairly well. There's a major increase in the amount of work done on W and F. However, going to three days without meetings didn't really help, as the problems we are working on do require lots of whiteboarding and brainstorming sessions between engineers.
- pkaye 9y agoI've found if the teams have mostly senior engineers there is very little need for meetings. In my current situation we just have one meetings per week to discuss status and priorities. Everything else is slack chats and adhoc meetings among individuals as needed. Mostly everyone is in sync on what is the right thing to do or if not, hash it out in a quick discussion.
- haskellandchill 9y agoThat's how I love to work. We are adults and most of our workload is fundamentally adhoc, changing with our business partnerships and market fit. Unfortunately at my current job we squaded up adding extra meeting load anyone who works across squads. With weekly planning meetings and standups for every squad it's rough. Also people treat standups like they are free, why not add more? Well they are not. I have to fight being put on more than one. It's already one more than I would like anyway :)
- maxxxxx 9y agoReading the comments here I find it interesting how management totally ignores feedback from developers. A lot of devs think open offices and endless meetings are a drain on productivity. So you would think the reasonable response would be to address these issues to get as much productivity out of these often highly paid people but instead the top guys often do exactly the opposite. It's a very curious dynamic.
- gk1 9y agoI agree that managers should very mindful of filling their teams' calendars with meetings. But there's not much a manager can do about open offices. They didn't design the building or the floorplan, and they can't change it now. Those decisions are made way above the typical managers' pay grade.
- maxxxxx 9y agoSomeone up the chain made those decisions based on some input. This stuff doesn't come down from the heavens.
- sotojuan 9y agoThey made that decision because it is cheaper, everyone else is doing it, and companies like Facebook "biggest open office plan ever" do it as well.
- doublescoop 9y agoYou know how developers feel their managers never listen to their input before making big decisions that have drastic impact on their day to day work? That happens between managers and executives just as often. As a manager, I have never been consulted about work space beyond a general "how do you want to arrange these desks we bought for you?" kind of way.
- maxxxxx 9y agoMe neither. But I know for sure that someone around VP level or higher could make changes if they actually cared. They shouldn't hide behind facilities policies.
- floodfx 9y agoI wrote an app called MakerSession [1] which was inspired by this essay. MakerSession automatically blocks out time on your (google or microsoft) calendar based on when your day starts/ends and how much time you need to get stuff done... [1]-https://makersession.com https://makersession.com
- padobson 9y agoWorking in the eastern time zone for clients on the west coast has allowed me to find some ways to solve this problem. The time difference is about a "half day", the one PG is describing here. So if I schedule all of my meetings in the afternoon pacific time, I can get a full day of work done before calling into teleconferences. So I wonder if some kind of staggered scheduling, like PG described in the essay, is the answer to this problem.
- bayindirh 9y agoI have been parts of projects which failed just because the manager refused to accept that developers' need uninterrupted time to start and warm-up to achieve full speed in their daily routines. Add micromanagement into this mix, and the environment quickly approaches to real-life-dilbert. Addenda: Obligatory dilbert: http://dilbert.com/strip/2018-04-21 http://dilbert.com/strip/2018-04-21
- SteveJS 9y agoI took this to heart when it was published and ensured I schedule full team meetings that are as short as possible, and either start a day, end a day, or are directly adjacent to lunch. I also ensure there are 2 days of no scheduled meetings. Another thing that helped me as an IC was keeping notes as a habit. It needs to become ingrained enough that it isn't blocking flow to jot a note into OneNote or Evernote. This allows you to 'see' the interruptions later. I'm more of a 'pile' based note taker, so it's a gigantic list of timestamps + notes. If you are getting too many interruptions it also provides highly detailed 'proof' to the person in charge. More recently I realized that getting distracted today is tremendously easier than it was in the past. When I find that is an issue I set a meditation timer to ring a bell every 5 minutes. If I'm not doing what I want to be doing when that bell goes off, I just go back to doing what I planned. At a certain point the bell ringing is just a habit to ensure your attention is in the right place.
- justherefortart 9y agoI took over as IT Director at a company with a small team. Everyone would take their issues to the developer all day long, interrupting his day constantly. So every new "fire" because the latest task. Not surprisingly the hacked together new website (which went live months late and $100s of Ks over budget) was a train wreck. Unreliable and constantly causing errors/issues. The first thing I did was said the only person that can talk to the development team is me. It took about 2 months to get all the software processes in place that were non-existent, to get the entire website working and stable, and to get our task/goal list under control. The cocksucker owner comes to me and says "I want these 4 project you quoted that would take 6 months done in the next 3 months". So I quit (so did their lead developer that was doing 90% of the heavy lifting). IT Management is a mess everywhere I've ever been, just to varying degrees. Maybe this is because most my career has been as a consultant or contractor, but it's really discouraging.
- woqe 9y agoI just finished reading the Phoenix Project, and I wanted to say the beginning of this post read almost exactly like the first 3/4's of the book. https://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/0988262592 https://www.amazon.com/Phoenix-Project-DevOps-Helping-Busine...
- oftenwrong 9y agoThis meets with my experience. I rarely have meetings, and I regularly get solid, 4-hour blocks of productivity. Typically two to three time per week. Those pushes account for most of my work, and my best work. I do not schedule those 4 hour blocks because I would not be able to stick to the schedule. I often have trouble concentrating for even 30 minutes straight. When I hit 4 hours (and my time tracker sends me a notification to celebrate), I am always surprised. I get into the zone, and then I find myself still coding 4 hours later. Every meeting is a chance to miss that enter-the-zone window.
- pavel_lishin 9y agoI'm like this too, and I hate it - because it means I can't reliably get those four hour blocks. Not having a schedule isn't a good thing, it just means that if you're ever in an environment where outside factors become significant (new job, new child), your productivity gets fucked.
- slgeorge 9y agoOne suggestion: change the way you think of a schedule. Book in those 4 hour blocks, calendar gym, calendar leaving the office etc. People tend to start trying to work around the outside of those blocks.
- ericd 9y agoCould you elaborate? I don't quite understand what you're suggesting.
- dredmorbius 9y agoYou have a calendar. Your 4 hour blocks are scheduled. As committments. And cannot be casually preempted.
- pavel_lishin 9y ago
- ccvannorman 9y agoMy mitigation strategy is I book calendar time for entire days to work on stuff. "Want to get coffee on X or Y date?" "Sorry, I'm totally booked those dates -- how about Z date/time?" It makes me seem unavailable/scarce, and allows me to book things on my "manager days". The key is using the calendar to your advantage .. control your own time.
- eddieschod 9y agohttp://calnewport.com/blog/2017/04/05/why-are-maker-schedules-so-rare/ http://calnewport.com/blog/2017/04/05/why-are-maker-schedule...
- dasmoth 9y agoThis is an interesting follow-up to the original example. I quite like the proposals he makes (although with some reservations about the extreme one —- some level of contact with end users is always valuable in my experience) However, relevant to contemporary software (where nearly every project, regardless of scale, seems to need a team...): The exception, of course, is that makers working in teams have ways to communicate within their team. My experience is that “the team” seems to be a disproportionate source of interruptions. If anything, I wonder about a system where a manager acts as a form of message-queue within the team. Pretty much the direct opposite of a lot if contemporary approaches (...scrum...) but perhaps a bigger increase in maker-schedule time than focusing on external interruptions.
- lmilcin 9y agoThe problem with working at the large company is that every manager will see open calendar as an invitation to put in some meetings. For this reason I am booking in my calendar actual working time. Since I am based in Europe and work with people in both US and Asia, I do this smack in the middle of the day so that I can have meetings with APAC in the morning and with US at the end of my working day. I frequently have managers asking me why my calendar is booked so much to which I respond, "why YOUR calendar is booked so much". This of course has to follow with suitable explanation which is more or less based on this essay which I read many years ago.
- voxmatt 9y agoWe started Clockwise to address this problem, and this PG article was a major point of inspiration. (Looking through the comments, that seems to be a trend!) We just launched a private beta of Clockwise for Chrome, which helps automatically put more maker time on your team's calendar. It's free and we'd love everyone's thoughts. Feel free to send me an email if you'd like to hop the line: matt@getclockwise.com https://www.getclockwise.com/product https://www.getclockwise.com/product
- rupertdev 9y agoThis is cool! Too bad my team is trapped in the Outlook world..
- voxmatt 9y agoWe'll get there! Had to start somewhere, and Google Cal is a little more common among early-adopters.
- bmpafa 9y ago> Clockwise for Chrome, powered by AI, Can you share where AI fits in the product? It's not that I'm skeptical of every time a product vaguely alludes to AI in their copy, but... well... I can't think of a way to end that sentence.
- ozim 9y agoMy feeling is it tries to fix people problem with tech. If you have reasonable manager who would respect people time instead of bomb dropping, you don't need the tool. If you have micromanager, you won't get to him with the tool.
- tquinn 9y agoI've run a small distributed team for years, and I've mostly resolved the manager vs maker challenge through a combination of: -desynced collaboration tools -avoiding interruption based tools as much as possible -short & focused bi-weekly meetings at the front or back end of the day It allows the majority of the day for a maker schedule, while allowing for just enough manager time. Also with desynced tools (ex: outstanding support/bug/etc issues in Trello), as long as everyone is checking in at regular internals (say 2x a day) -- things can move through fairly quickly without constant interruptions. For the manager side I use a mix of: -Calendar/Contacts -Evernote -Workflowy -Trello -Slack (at scheduled times, leaving it on all day is horrible idea) For the maker side: -Workflowy -Trello -Pathjet.com (A small tool that I designed for myself which mixes GTD + Kanban + Pomodoro) -Prior to my own tool, I used a Pomodoro timer + Workflowy on my machine -Sometimes I think it's great to get off my machine, and just use a pen+legal pad to do planning/sketching/brainstorming
- mellett68 9y agoI have been keeping one day a week for the manager's schedule- style calls and appointments. The rest of the week is divided in to half-day blocks which from my own experience is the minimum useful time to switch context and complete or work on some task. I'd never read this before but it sums up problems I've had in teams previously with scheduling and especially short-notice "quick" meetings that wreck an afternoon. It also means there's sacred time in my calendar for unbillable stuff, which gives peace of mind rather than thinking "but I could be doing..."
- kristianc 9y agoI read Dan Pink's book "When" recently, and made a conscious effort to schedule all of my meetings in what Pink calls admin time between 1 and 3 in the afternoon. It's a win-win - I can go to the meetings having just been to the gym, and my morning is freed up for making.
- vikasuy42 9y agoCheck out http://try-tempo.com/ http://try-tempo.com/ A few friends and I built this to create more "maker time" for ourselves. It helps you group your calendar events together for the day so that you get longer stretches of time to be creative. Would be honored if you gave it a try!
- lainga 9y agoUnrelated to managers, this is why I have trouble doing work when I'm home from university: "Could you fold the laundry now...?"
- chrisbennet 9y agoThis! That’s why I have an office that isn’t at home. (I’m a consultant/contractor.)
- kyleblarson 9y agoA context switch costs many IQ points and it takes at least an hour to get them back.
- nkozyra 9y agoThis is my number one reason for working at nights outside of normal working hours.
- raleigh_user 9y agoI cofounded a small agency. I really enjoy it. I spend a lot of time away from our team and this is no shot at the amazing team we built. But the time where you're in the zone and able to produce/be creative is imperative to our growth/success. I still have meetings but days where I don't I go on really long runs in the mornings (15 miles or so) and during that time get in a great state of mind. Then 3-4 hours of awesome productivity and the business seems to keep moving forward at a rapid pace.
- josephcooney 9y agoPro tip: Decline meetings, as many as possible.
- brazzledazzle 9y agoI’ve encountered so many people that assume someone has to come to any meeting they’ve invited them to and it never fails to blow me away. I can understand the mindset a bit with managers but it seems to have little to do with title. It always starts with a message or a call asking where I am. When I tell them where they let me know I’m late for a meeting. When I tell them I declined it or I was tentative you can practically hear the gears in their heads grind and seize up. The thought seemingly had, up until that point, never occurred to them to check the attendance on the invite before the meeting starts. “But... I booked it in an open spot on your calendar. Aren’t you available, can you come? Here’s why I need you here...” This is where it becomes clear to me that they’ve never considered populating the meeting with more than a subject and a conference link. They treat an open calendar like you’re some kind of reservation system.
- chrisbennet 9y agoA friend of mine got so sick of the many useless meetings at a company he worked at that he would just started declining any meetings that didn’t have a written agenda. When I schedule a meeting with clients, I send them an email with the questions I’m going to ask them and what I need to learn from the meeting. As a meeting attendee, I don’t want to be asked a question that someone knew they were going to ask before the meeting. I want to hit that meeting with answers so I’m not having to say, “I’ll look into that and tell you at the next meeting.”
- droosevelt 9y agoThis is definitely a great model to strive for. Whenever coworkers try to schedule unnecessary meetings w/ me I send this - https://shoulditbeameeting.com/#/ https://shoulditbeameeting.com/#/
- Cofike 9y agoThis was a major problem at my last company. There were days where meetings weren't an issue but the support channel we had to monitor was. Ugh
- Fzzr 9y agoI regularly send this to people where ever I work. Never stops being relevant.
- blablabla123 9y agoI've tried this at 2 companies, one was even my own startup. It seems like a natural separation but in my experience it alienates the makers from the business. Probably that's not an issue if you just work for the tech that is in use. YMMV but if not, it's not the best idea.