<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Zack Bloom on Medium]]></title>
        <description><![CDATA[Stories by Zack Bloom on Medium]]></description>
        <link>https://medium.com/@zackbloom?source=rss-af5af901a9d5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tGmeNYMkvzt1Vfs-.jpeg</url>
            <title>Stories by Zack Bloom on Medium</title>
            <link>https://medium.com/@zackbloom?source=rss-af5af901a9d5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:54:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zackbloom/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Why a Pneumatic Ventilator]]></title>
            <link>https://medium.com/@zackbloom/why-a-pneumatic-ventilator-e324da4a9b0f?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e324da4a9b0f</guid>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Sun, 22 Mar 2020 05:20:58 GMT</pubDate>
            <atom:updated>2020-03-22T05:20:58.998Z</atom:updated>
            <content:encoded><![CDATA[<p>“We knew the world would not be the same. A few people laughed, a few people cried. Most people were silent.”<br>― <strong>J. Robert Oppenheimer</strong></p><p>The pneumatic ventilator designs we are working on are insufficient. They don’t have the level of control of a modern vent. They don’t (yet) do the proper filtration of exhilate, they don’t (yet) support humidification, they don’t (yet) have careful control of the PEEP values required. So why are we pursuing them?</p><h3>Simplicity</h3><p>For most of us, our first imagining of a home-grown ventilator was a large piston or air-bag and electromechanical computerized controls. Unfortunately that image runs into very real supply constraints. It’s possible to buy a dozen or a hundred stepper motors or RaspberryPi’s in my area, but I can’t get or afford a thousand much less a hundred thousand. I know it’s possible to get these items in the United States (for now), but I am not entirely confident of what will be available in Mongolia or Patagonia.</p><p>I can imagine taking our Army or Vortran Ventilator designs, printing 500 or 5000, filling a box or pallet, shipping them to India and believing someone could hook up O2 or air to one end, a patient to the other, and keep them alive; At least for a time, hopefully long enough. I don’t know that I can say the same about many of these more complex designs.</p><p>As much as I believe in the maker ethos, I don’t believe every person or every physician is going to suddenly be a maker. I think a small cohort of builders in the world will create these devices. If the device can be made by a 3D printer or a laser cutter I think each person might be able to make hundreds, if it has to be assembled from many complex parts that number drops precipitously, however good the instructions.</p><h3>We are the worst-case scenario</h3><p>It’s important to understand where we fit in the ecosystem. Right now Tesla and GM are supposedly preparing to build devices. Ventilator manufacturers are doing the same. Many very smart teams within Helpful Engineering are building brilliant things. I am so incredibly thankful that these teams exist because what we build will be not sufficient and not enough, I desperately hope that if a loved one of mine falls ill it is on one of their devices their hopes lie, not ours.</p><p>But our devices are the last line of defense. We are building something very different. We are building a device which doesn’t meet the modern standard of care. A device which virtually everyone will discount and toss because it isn’t what a modern patient in the modern world should have to put up with. But there is a small chance we are about to leave the modern world behind us, and the wonderful devices built by these brilliant people will function well but not for enough people fast enough.</p><p>Let me ask you, will Tesla be sending ventilators to Djibouti? Do they have the ready access to the electronics you need for an alternative design there? How will those people survive? I hope the answer is anything other than our devices. But if the alternative is death, I believe what we are creating might be the solution they need at the scale and simplicity which they can get and use.</p><h3>I leave these to a darkened world with the hopes they are never used</h3><p>Again, I hope that what we are building is utterly unnecessary. I hope everyone with better, more complete plans is right. But I fear their assurity, and I fear the standards of modern medicine will leave thousands behind. For those reasons I believe what we’re doing remains worth pursuing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e324da4a9b0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Become an Engineering Manager]]></title>
            <link>https://medium.com/@zackbloom/how-to-become-an-engineering-manager-c255341f5df7?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c255341f5df7</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Fri, 04 Jan 2019 14:51:30 GMT</pubDate>
            <atom:updated>2019-01-04T14:51:30.811Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I have been asked several times how to make the transition from individual contributor to manager. Rather than answer it for just those asking, I thought I would take a moment to share my thoughts with you!</em></p><p>I decided to be a manager of people for two reasons. One, it seemed a necessary skill if I wished to enable the development of anything more complex than I could build myself. The Saturn V rocket was born out of Wernher von Braun’s ability to lead, not just his ability to calculate delta-v. The second reason for my managerial bent was equally simple: it was really hard. Computers always do what you tell them to, but people… don’t. It is fiendishly hard for someone such as myself to learn how to motivate, develop, and focus people. It’s something I can genuinely believe I will be learning about and struggling with for as long as I’m on this earth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DkezZ7ud1ftlz-V9.jpg" /><figcaption>Werner von Braun standing in front of the Saturn V rocket he helped design.</figcaption></figure><p>It is not, and should not be, for everyone. I know absolutely brilliant principal engineers and it would be a crime to all of humanity if their time spent building was pulled into people management. At the end of the day the future is built by the people who are actually willing to get their hands dirty. Beyond that, a new wave of nomadic entrepreneurs like Pieter Levels have shown it’s possible to build entire companies alone. Coordination consumes a lot of resources, working alone has its advantages.</p><p>Managing and mentoring has a tremendous upside along with its difficulty. There is nothing quite like watching a person grow from a novice to an expert, capable of incredible things. There is also nothing more valuable to an organization than being able to recruit entire teams who can work together to get things done which simply would not have been done without them. It can define the future.</p><h4>Why this is so hard</h4><p>Management is a skill. It requires an understanding of people and a sense of judgement, but also a whole load of nuts-and-bolts judgement learned through experience. Virtually every manager will suffer through the same situations (an underperforming direct report is a classic one) and come out the other side with learnings and a playbook for how to deal with those situations in the future. Similarly, they will pick up useful practices which can be applied to their future teams to make them more successful.</p><p>Unfortunately, these are not skills commonly developed in childhood or school. Being a team lead for a few weeks of your senior project is barely a blink, and it represents the entirety of the leadership experience many of us have entering the workforce. When you are asking to become a manager for the first time you are, therefore, asking for no small favor. Imagine what it would mean to hire a software engineer who had never programmed a day in their lives before they started the job. Imagine how much training, how much mentorship, how much patience, it would take to get them to the point where they could be successful. It would be a tremendous undertaking! Management is no less a skill, and most of us enter it no more prepared.</p><p>Truthfully, the reality of the situation is even worse, as we can tolerate bad programmers more easily than bad managers. Bad managers don’t just waste their own time, they endanger an entire team. The classic adage is “employees don’t quit companies, they quit managers” is true. Your manager is often your gateway in an organization to knowledge and opportunity, if their bad it can make your life miserable. What a risk an organization is taking in allowing someone without experience to try it!</p><h4>How to become a manager</h4><p>Fundamentally organizations don’t make managers, directors do. Directors are generally responsible for managing first-level managers, and it falls to them to make the necessary recommendations which lead to someone getting promoted. At the most basic level, your director (or in a smaller organization VP of Engineering or CTO) needs to decide you would cause more good than harm if you were managing others. It’s that simple, and that hard.</p><p>There is one important caveat: all of this only applies if your organization <em>needs</em> managers. If your technical team isn’t growing it’s possible no more management is required. If your organization is notably flat it’s possible they don’t want more managers, whether they need them or not. It’s also common for organizations to go through phases where they emphasize bringing in experienced external managers to boost their overall maturity, during which it can be hard to get promoted from within.</p><p>The jump to being a manager is a big one. The job is essentially entirely new. There is rarely any meaningful source of training available. Most managers learn their craft on the job through mistakes, and through mentorship. Allowing you to make that leap into a new career takes a great deal of faith on the part of the organization. That makes it very rare for it to come through a career change, few people want to hire a manager who has never done the job before. Generally people must work somewhere for a year or two before they are moved into management. Once that title appears on your resume it becomes possible to at least get the interviews you need to keep it. If you choose to work somewhere which requires X years of experience before making that leap, you might be in for a wait.</p><h4>The Technical Experience Clock</h4><p>Becoming a technical manager requires technical experience. Conventionally, in the tech field, this is considered necessary so you can authoritatively speak on technical topics, and so you can mentor more junior team members. It’s also important as a check on the desire for junior people to immediately move into management. For better or worse it’s generally considered important for people to have, at least, a decent amount of work experience before making that leap.</p><p>Technical knowledge is not the only thing gained through experience. Judgement is, by my definition, the ability to know what the result of a decision will be without having to play it out. It’s the knowledge of what has to be reported up to your boss and what can be kept inside the team. It’s the knowledge of what performance or reliability problems have to be tackled, and what can be deferred. It’s knowing just what to say to a recruiting candidate to get them to want to work at the company.</p><p>Judgement takes experience. It takes making decisions and seeing how they will play out. And that takes time. But your time can be more or less valuable. If you’re in a role like running a startup you get a lot of experience very fast (at least at leading very small teams). If you are in a very narrowly scoped engineering role within a very large company, it might take much more time for you to learn.</p><h4>Pick your company</h4><p>The conventional track within a company is to spend 5+ years as an individual contributor, working your way up until you are ready to move into the management track. This is sometimes a bit unfortunate, as it’s very possible many people who simply don’t excel as individual contributors would make excellent managers. God knows there are many ICs who shouldn’t be managers, why would the reverse not be true? It is very possible there are many people slogging through the promotion track as a programmer while everyone would be much happier if they could move into a more people oriented trajectory.</p><p>In any case, as with all process-related limitations the way to bypass this clock is generally to find somewhere where the game is played fast and loose. That usually means startups. Many tiny startups need ICs much more than they need managers and won’t create the best opportunity for entering management. As they pass through five or ten engineers however it quickly becomes clear that some management is necessary, and an enterprising engineer on that team can earn the mantle. That opportunity remains up through perhaps a hundred engineers when more hierarchy and process begins to be enforced. It also can be very valuable to work for someone who is more instinct than process driven. This is very much a personality trait and can be selected for while you are interviewing. Choose the place where the VP of Engineering calls you, not the place with an ultra established interview process.</p><p>If you are told you need X years of experience before making the transition at that company, it’s likely true. If you are told you don’t, it might still be a fact. Don’t necessarily believe promises made during the interview process, talk to other actual managers who made that transition first. Also be cautious in spelling out your managerial intent in the interview process. It can scare off organizations who will fear you won’t be content working as an individual contributor if you are immediately looking for promotion.</p><h4>Act like a manager</h4><p>You also must act like a manager. That doesn’t mean ordering people about (that’s not what a great manager does), it means being responsible, being accountable for your actions, caring about the people around you, making people want you to be in charge. Be trustworthy, give credit to those around you, stand straight, bring solutions not problems. Appear to prioritize the organization over yourself. When given the choice, act like an adult who acts in the interest of senior leadership, not a child who demands things of them. Don’t be the drunk one at the party or the loud one at the table.</p><p>This attitude can also be evidenced in how you speak. Consider these two comments made to your boss:</p><blockquote>“I don’t like this job, I want to work on the ML platform, I want to move.”</blockquote><blockquote>“I want to work on what’s most important for the organization, what you most need. From my perspective that looks like the ML platform, but tell me where to go and I’m there.”</blockquote><p>They will, very likely, get you the same thing. One is how junior people ask for what they want, the other is how senior people endeavor to give the organization what it needs.</p><p>Always remember that your ultimate goal is to make the Director-like person believe that the organization will be better served by you leading others than the alternative. That also means making other engineers respect you, as they are the very people you will end up leading. That can mean putting their interests first, making sure everyone is heard, supporting people in any way you can, and acting as much like a manager as you can even while you don’t have the role. It’s often said that you get the job after you start doing it, that is no less true here.</p><h4>Cultivate judgement and empathy</h4><p>You can cultivate your judgement. It can be done by thinking and writing about decisions made by yourself and others, and by asking questions to learn how decisions are being made. If you are given an opportunity to work on a project where every decision hasn’t been made yet, don’t just wait to be told what to do, take some time to form your own perspective. For me that usually means writing. By writing I am able to get my thoughts into a form where I can build on them, and even more importantly, edit them. If you don’t like writing, it’s all the more important!</p><p>You can also read books and blog posts on engineering and management (you’re doing it now!), but don’t just consume them, write something based on them. It can be a critique allowing you to get on paper why something felt off to you, or a summary, or an aggregation of many different sources on a topic. As Benjamin Disraeli said: “The best way to become acquainted with a subject is to write about it.”</p><p>You also have the opportunity to absorb all the knowledge of the people around you. Ask questions to the managers in your organization. Build relationships and show them you value their advice. Have a humble learner’s mindset: don’t push to have your opinion heard, instead assume everyone has something to teach you and allow them to. It is always more valuable for you to make someone think they are the smartest person in the world, than for you to make them think you are.</p><p>This idea, that how you make people feel is important, is a critical component of the other thing you need to be successful as a manager: empathy. Empathy isn’t just the ability to sympathize with other people’s problems, it is the ability to understand other people’s perspective; to put yourself in their shoes. If you often think people are ‘crazy’ or ‘nuts’ you likely don’t have very much empathy yet. If you think people are complex, challenged, individuals who are all doing their best however poor that might be, you’re closer to the mark.</p><p>You can build empathy simply by listening to people, asking questions, and learning how they think and why they make the decisions they do. In that listening you must do something very paradoxical: you must turn off that judgement which you spent so much energy to cultivate. Judgement is your perspective, and it is the dire enemy of you being able to understand anyone else’s. You must listen with the attitude that you are not always correct, that everyone has a right to make their own decisions, and you are not god: you have no unique ability to predict the outcome of any of those decisions. You are simply another human with your own perspectives and your own decisions to make.</p><p>The more you cultivate that empathy and understanding the more you will be able to relate to, build relationships with, and predict the behavior of, other people. It can certainly be a challenge, but if it’s not one you are interested in taking on you should not be a manager.</p><h4>Make your goals known</h4><p>You should, at some point, tell your boss your ultimate goal is to be a manager. That doesn’t mean saying ‘Make me a manager’, or ‘If I don’t become a manager I’ll quit’, it means saying “My long-term goal is to move into management. I know I might not be ready for that yet, but can you help me get and stay on the path to get there?” Eliciting help is almost always a great move, and demonstrating you know you have a lot to learn is a wonderful way of showing you have the right attitude for moving into the never-ending challenge that is management.</p><p>You should also solicit the advice and mentorship of other managers in your organization. They made that transition and can give good council, but they also probably talk to the directors in your company more often than you do. You never know when a good word might be made on your behalf. The absolute most important relationship however is between you and your direct manager. This is the person who ultimately will make the critical recommendation, and who will control your access to high-visibility and management-like opportunities leading up to that moment. If you don’t think your manager wants you to succeed, you need to have a direct conversation getting to the bottom of it, and if that doesn’t work, you need to switch teams or jobs. It’s exceptionally hard to succeed with a manager who doesn’t want that for you.</p><p>Ultimately, life is long and most people give up long before they run out of time. The five years you spend wanting to be a manager might be the fond blink of an eye in the scope of the thirty years you spend as one. Learn everything you can, about engineering, and about people. Most importantly, when you become a manager, as I believe you will, please be a good one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c255341f5df7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Isolates are the Future of Cloud Computing]]></title>
            <link>https://medium.com/@zackbloom/isolates-are-the-future-of-cloud-computing-cf7ab91c6142?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf7ab91c6142</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Thu, 18 Oct 2018 03:37:31 GMT</pubDate>
            <atom:updated>2018-10-19T22:48:39.742Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Computing Without Containers</h3><p>I work on a cloud computing platform. Unlike essentially every other cloud computing platform I know, it doesn’t use containers or virtual machines. I think that is the future of Serverless and cloud computing in general, and I’ll try to convince you why.</p><p>(I’m a part of Cloudflare, where we have our <a href="https://www.cloudflare.com/products/cloudflare-workers/">Workers</a> platform, making me incredibly biased. Please discount what I say appropriately in that light, and feel free to leave comments here or on Hacker News where you disagree.)</p><h3>Isolates</h3><p>Almost two years ago we set out to find a way to let people write code on our servers deployed around the world (we had a little over a hundred data centers then, it’s 154 as of this writing). We were dramatically limited in how many features and options we could build in-house and needed a way for customers to be able to build for themselves. We needed a way to run untrusted code securely, with low overhead. It also had to run very very quickly, as we sit in front of ten million sites and process millions and millions of requests per second.</p><p>The Lua we had used previously didn’t run in a sandbox, meaning customers couldn’t write their own code without our supervision. Traditional virtualization and container technologies like Kubernetes would have been exceptionally expensive for everyone involved. Running thousands of Kubernetes pods in a single location would be resource intensive, much less 154. Scaling them would be easier than without a management system, but far from trivial.</p><p>What we ended up settling on was a technology built by the Google Chrome team to power the Javascript engine in that browser, V8: Isolates.</p><p>Isolates are lightweight contexts which group variables with the code allowed to mutate them. Most importantly, a single process can run hundreds or thousands of Isolates, seamlessly switching between them. They make it possible to run untrusted code from many different customers within a single operating-system process. They’re designed to start very quickly (several had to start in your web browser just for you to load this web page), and to not allow one Isolate to access the memory of another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PdicnoJtzaeZDcO2UQcHdg.png" /></figure><p>We pay the overhead of a Javascript runtime once, and then are able to run essentially limitless scripts with almost no individual overhead. Any given Isolate can start around a hundred times faster than I can get a Node process to start on my machine. Even more importantly, they consume an order of magnitude less memory than that process.</p><p>They have all the lovely function-as-a-service ergonomics of getting to just write code and not worry how it runs or scales. Simultaneously, they don’t use a virtual machine or a container, which means you are actually running _closer_ to the metal than any other form of cloud computing I’m aware of. I believe it’s possible with this model to get close to the economics of running code on bare metal, but in an entirely Serverless environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uq3wwohDg_R7u5j4VleBDg.png" /><figcaption>This is not meant to be an ad for Workers, but I do want to show you a chart to reflect just how stark the difference is, to showcase why I believe this is not iterative improvement but an actual paradigm shift. <a href="https://blog.cloudflare.com/serverless-performance-with-cpu-bound-tasks/">Source</a></figcaption></figure><h3>Cold Starts</h3><p>Not everyone fully understands how a traditional Serverless platform like Lambda works. It spins up a containerized process for your code. It isn’t running your code in any environment more lightweight than running Node on your own machines. What it does do is auto-scale those processes (somewhat clumsily). That auto-scaling creates cold-starts.</p><p>A cold-start is what happens when a new copy of your code has to be started on a machine. In the Lambda world this amounts to spinning up a new containerized process, and it can take between 500ms and 10 seconds. This means any requests you get will be left hanging for as much as ten seconds, a terrible user experience. As a Lambda can only process a single request at a time, a new Lambda must be cold-started every time you get an additional concurrent request. This means that laggy request can happen over and over. If your Lambda doesn’t get a request soon enough, it will be shut down and it all starts again. Whenever you deploy new code it all happens again as every Lambda has to be redeployed. This has been correctly cited as a reason Serverless is not all it’s cracked up to be.</p><p>Because we don’t have to start a process, Isolates start in 5ms, a duration which is imperceptible. Isolates similarly scale and deploy just as quickly, entirely eliminating this issue with existing Serverless technologies.</p><h3>Context Switching</h3><p>One of the key features of an operating system is it gives you the ability to run many processes at once. It transparently switches between the various processes which would like to run code at any given time. To accomplish that it does what’s called a ‘context switch’, moving all of the memory required for one process out, and the memory required for the next in.</p><p>That context switch can take as much as 100uS. When multiplied by all the Node, Python or Go processes running on your average Lambda server this creates a heavy overhead which means not all of the CPUs power can actually be devoted to running the customer’s code; it’s spent switching between them.</p><p>As an Isolate-based system runs all of the code in a single process and uses its own mechanisms to ensure safe memory access, there are no context switches.</p><h3>Memory</h3><p>The Node or Python runtimes were meant to be ran by individual people on their own servers. They were never intended to be ran in a multi-tenant environment with thousands of other people’s code and strict memory requirements. A basic Node Lambda running no real code consumes 35 MB of memory. When you can share the runtime between all of the Isolates as we do, that drops to around 3 MB.</p><p>Memory is often the highest cost of running a customer’s code (even higher than the CPU), lowering it by an order of magnitude dramatically changes the economics.</p><p>Fundamentally V8 was designed to be multi-tenant. It was designed to run the code from the many tabs in your browser in isolated environments within a single process. Node and runtimes like it were not, and it shows in the multi-tenant systems which are built atop it.</p><h3>Security</h3><p>Running multiple customer’s code within the same process is something which should, obviously, be done with a careful attention paid to security. I don’t think it would ever have been productive or efficient for us to build that isolation layer ourselves. The amount of testing, fuzzing, penetration testing, and bounties required to end up with something truly secure is astronomical.</p><p>The only reason this was possible at all is the open-source nature of V8, and it’s standing as perhaps the most well security tested piece of software on earth. We also have a few layers of security built on our end, including various protections against timing attacks, but V8 is the real wonder that makes this compute model possible.</p><h3>Billing</h3><p>This is not meant to be a referendum on AWS billing, but it’s worth a quick mention as the economics are interesting. Lambda’s are billed based on how long they run for. That billing is rounded up to the nearest 100ms, meaning people are overpaying for an average of 50ms every execution. Worse, they bill you for the entire time the Lambda is running, even if it’s just waiting for an external request to complete. As external requests can take hundreds or thousands of ms, you can end up paying ridiculous amounts at scale.</p><p>Isolates have such a small memory footprint that we, at least, can afford to only bill you while your code is actually executing.</p><p>In our case, due to the lower overhead, Workers end up being around 3x cheaper per CPU-cycle. A Worker offering 50ms of CPU is $0.50 per million requests, the equivalent Lambda is $1.84 per million.</p><h3>The Network is the Computer</h3><p>Amazon has a product called Lambda@Edge which is deployed to their CDN data centers. I’m sure they’re doing their best with the technology they have to make it compelling, but it’s three times more expensive than traditional Lambda, and it takes 30 minutes to deploy a code change. I don’t think there’s a compelling reason to use it.</p><p>Conversely, as I mentioned, with Isolates we are able to deploy every source file to 154 data centers at better economics than Amazon can do it to one. It might actually be cheaper to run 154 Isolates than a single container, or perhaps Amazon is charging what the market will bear and it’s much higher than their costs. I don’t know Amazon’s economics, I do know we’re very comfortable with ours.</p><p>It long-ago became clear that to have a truly reliable system it must be deployed to more than one place on earth. A Lambda runs in a single availability zone, in a single region, in a single data center.</p><h3>Disadvantages</h3><p>No technology is magical, every transition comes with disadvantages. The biggest is an Isolate-based system can’t run arbitrary compiled code. In a world where you have process-level isolation your Lambda can spin up any binary it might need. In an Isolate universe you have to either write your code in Javascript (we use a lot of TypeScript), or a language which targets WebAssembly like Go or Rust.</p><p>If you can’t recompile your processes, you can’t run them in an Isolate. This might mean Isolate-based Serverless is something which is only for newer, more modern, applications in the immediate future. It also might mean legacy applications get only their most latency-sensitive components moved into an Isolate initially. The community may also find new and better ways to transpile existing applications into WebAssembly, rendering the issue moot.</p><h3>Your Help</h3><p>I would love for you to <a href="https://developers.cloudflare.com/workers/about/">try Workers</a> and let us and the community know what your experience is like. There is still a lot for us to build, we could use your feedback.</p><p>We also need engineers and product managers who think this is interesting and want to take it in new directions. If you’re in San Francisco, Austin, or London, please reach out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf7ab91c6142" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serverless Pricing and Costs: AWS Lambda and Lambda@Edge]]></title>
            <link>https://medium.com/@zackbloom/serverless-pricing-and-costs-aws-lambda-and-lambda-edge-169bfb58db75?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/169bfb58db75</guid>
            <category><![CDATA[lambda]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Wed, 22 Aug 2018 18:15:41 GMT</pubDate>
            <atom:updated>2018-08-22T21:05:21.513Z</atom:updated>
            <content:encoded><![CDATA[<p>(Note: These prices are accurate as of August 2018)</p><p>AWS Lambda has 263 separate billable line items each with their own prices. They have names like “<em>Accelerated InterRegion Inbound using edge locations outside US, Europe or Japan, From EU (Paris) to EU (London)</em>”, and exist for each of the 17 regions it is offered in. All told that is 4,471 separate prices you can be charged for executing Lambda.</p><p>That gets added to the 635,035 prices for EC2 services, 12,261 for Route53, and 15,283 for API Gateway. All told Amazon has over a million separate rates you can be charged for various services. It’s so complex they even have a <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/using-ppslong.html">dedicated API</a> just to expose pricing, which is how I got these numbers (Lambda is not included in the <a href="http://calculator.s3.amazonaws.com/index.html">price calculator</a>).</p><p>Even in the simplest case, the <a href="https://aws.amazon.com/lambda/pricing/">pricing</a> for Lambda is far from simple: A free tier followed by $0.20 per million requests plus $0.00001667 per GB-second of ‘compute time’ used per month plus the cost of the API Gateway ($3.50 per million) you use to translate HTTP requests into Lambda executions. You are also charged for any data transfer done by your Lambda ($0.09 per GB), and any Dynamo DB requests you make from it (I can’t).</p><h3>What is Compute Time?</h3><p>You are charged $0.00001667 per GB-second of compute time your Lambda performs. GB-second is a bit of an odd unit. It could mean the number of seconds you’re using a GB of memory, but it actually means the number of seconds of compute you’ve done, multiplied by the number of GB of memory that compute allocated.</p><p>For people who aren’t comfortable with microcents as a unit of measure I’ve compiled the numbers into a chart which shows how much memory and CPU-time you get for $1–6 per million requests:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NVL8dayD9qzsgji4.png" /></figure><p>Amazon includes a pricing table on their page which excludes the $0.20/million base charge, but I’ve included it in my numbers.</p><p>Of course, a ms of CPU time can mean many different things. A ms of compute on an Apple II represented 3000 clock cycles. On the i7 in my laptop it’s 4 million cycles. In Amazon’s case, they actually scale up the speed of the CPU they provide based on how much <em>memory </em>you allocate. In other words your performance is memory * CPU time where CPU timegets smaller the more memory you use. This CPU boost continues until you have what looks like a full core, after which it grants you a second core which your application may or may not benefit from depending on its composition.</p><p>To compensate for that I’ve adjusted my chart to show how much actual CPU time you’re getting based on the mid-grade server processors we used in our comparison testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jgxAzK1XCA2qlHmt.png" /></figure><p>As you can see from the chart, it doesn’t, from a cost perspective, matter if you elect to run a 1024 MB Lambda for 100ms, or a 128 MB Lambda for 800ms, you get the same amount of compute and pay the same amount. Above 1024 MB though you reach the performance of a full processor core and begin getting the power of a second core (if your application is multithreaded).</p><h3>Rounding</h3><p>CPU time is rounded up to the nearest 100ms, meaning even the simple Lambda which returned the current time we used in our tests cost us $0.41 / million invocations. Of course, your Lambda will rarely execute with a number of ms of CPU that rounds perfectly. Much more commonly you’ll use some odd number of ms which Amazon will round up to calculate how much to charge you. Given that they always round up, that means you will be overpaying by an average of 50ms of CPU for every invocation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MyUwx4ZIuWM3UzhO.png" /></figure><h3>API Gateway</h3><p>AWS Lambda’s can perform a wide variety of tasks within Amazon. We’re interested in their use for building Serverless web applications specifically. For that purpose, a Lambda can’t be used directly, it needs some HTTP server which is willing to translate a request into a call to the Lambda’s invoke API. By far the most common way to do this is with Amazon&#39;s API Gateway product.</p><p>API Gateway is billed at $3.50 per million requests, a price which often exceeds the cost of the Lambda itself. Here is our chart from above adjusted to include API Gateway:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tr1aqtJ-BwOv-aQT.png" /></figure><p>You’ll notice the $1, $2, and $3 lines have disappeared from the chart. The absolute minimum is $3.91 / million requests if your Lambda consumes very little CPU.</p><p>You’ll also have to pay for your traffic, and an additional hourly fee if you wish to use caching.</p><h3>Route 53</h3><p>Amazon’s Route53 DNS service isn’t free. You’ll pay $0.40 per million DNS requests for the first billion. That brings our total minimum cost to $4.31 / million.</p><h3>More Costs</h3><p>Tabulating all the costs can be somewhat exausting. CloudWatch logs are $0.50 per GB. The $0.09 per GB of traffic charges will start to add up.</p><h3>Lambda@Edge</h3><p>Amazon also offers a way of running code through their CDN service, Cloudfront. Both the fixed and variable costs are exactly tripled when compared to Lambda, making them roughly 10x Cloudflare Workers.</p><p>Of course, for HTTPS requests Cloudfront itself costs $1 / million requests and that has to be purchased to use Lambda@Edge. You also pay bandwidth costs which can easily dwarf that price. If your site is 1 MB, you’ll end up paying as much as $85 / million just in Cloudfront bandwidth, $250 / million in regions like South America. Plus an additional $20 / million for requests which have to go back to your origin.</p><p>Here’s what that looks like for just the compute component:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t-f_HcVCgG4tLN5j.png" /></figure><p><em>PS: I work at Cloudflare, where we have a product called </em><a href="https://www.cloudflare.com/products/cloudflare-workers/"><em>Workers</em></a><em>. I won’t shill too much for it here, but you might want to take a look.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=169bfb58db75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Bad Managers Give Feedback]]></title>
            <link>https://medium.com/@zackbloom/how-bad-managers-give-feedback-b8f9bae21ff2?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8f9bae21ff2</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Wed, 15 Mar 2017 21:02:01 GMT</pubDate>
            <atom:updated>2017-03-15T21:02:01.430Z</atom:updated>
            <content:encoded><![CDATA[<p>Giving feedback is the single most fraught part of management. Every instinct we have pushes us towards either not giving it (if you fear conflict) or to give it incorrectly (if you don’t fear conflict enough). There are ways to do it well, but they’re not obvious or intuitive. Like anything worth knowing, they have to be learned.</p><p>Let’s break down the ‘intuitive’ way to give feedback:</p><blockquote>“Chris, your work on the ferry report sucked.”</blockquote><p>A critical component to communication is understanding how your words are received. How would you expect that to be received? My guess is Chris is going to get some combination of defensive, afraid, demoralized or angry. Notice that none of those outcomes resulted in the emotions you are hoping for. You want Chris to get introspective, thankful, motivated and frankly, better at doing ferry reports.</p><p>Of course, there are also many managers who don’t love conflict, and so they give it a bit more like this:</p><blockquote>“[ Quote Left Intentionally Blank ]”</blockquote><p>They won’t say a thing. Instead of helping Chris get better, they might decide Chris shouldn’t work on ferry reports in the future, or that maybe he needs to be reassigned. They might spend countless hours double checking his work, or worse, just doing it themselves, breaking down the fundamental purpose of being a manager. Even worse, Chris isn’t learning or growing, so he’s not happy, and you’ve now constructed a lie which will forever limit your ability to build a real relationship with him.</p><h3>How To Do It Right</h3><p>My model for feedback comes from management consultants Mike Auzenne and Mark Horstman of <a href="https://www.manager-tools.com/">Manager Tools</a>. Their system is the one which I think draws the best compromise between simplicity and effectiveness. Here’s how it works:</p><blockquote>You: “Hey Chris, do you have a minute for some feedback?”</blockquote><blockquote>Chris: “Sure, what’s up?”</blockquote><blockquote>You: “When you send ferry reports with the wrong numbers it makes it hard for us to maintain the trust of the customer.”</blockquote><p>That’s it. Stop talking. You’re done.</p><p>No moral judgements, no value judgements, no (probably wrong) guesses of why Chris is doing what he’s doing. The truth is you don’t know why Chris isn’t double checking things: it might be that he’s not detail oriented, or distracted, or that his cat is sick. You can spend the rest of your life probing and guessing, or you can just trust him to be the best person to figure it out for himself.</p><p>You trust Chris to care about the ‘trust of the customer’, and to take the necessary actions to keep it. He care’s about his job. He want’s to do it well. He is an intelligent human who is willing and able to improve, if he knows how his behavior effects the outcome.</p><p>Not making value judgements is important for several reasons. For one, you don’t actually know what the situation is, whether it was his fault, or that you would have done better. Even more importantly though, you don’t want to raise Chris’ guard and cause him to become defensive. When you start attacking people’s character, that’s exactly what happens.</p><p>This feedback is also fundamentally oriented towards the future which <strong>is the only thing you can change.</strong> The past is the past, the mistake happened, you can’t reverse it. Your goal now is to do what is best for preventing a similar thing from happening again.</p><p>Your goal is to connect cause with effect. This is critical because in a complex business, it can be very hard to connect one person’s behavior (how hard Chris works on reports) to an outcome (how many customers we lose). It might be easy for you to see, as the manager, but nearly impossible for Chris. Conversely, when Chris understands how his behavior relates to the success of the company, he will work harder and smarter.</p><p>Considering another example, let’s say you have an employee, Sam, who is talking over other people in meetings. It is very unlikely Sam knows that he is suppressing the contribution of other people in the room. He probably is just communicating the way that is natural to him. It’s not that he is consciously choosing to do poorly. In fact, doing well is often the single most important thing to any of us, all we want is to perform well.</p><p>Your instinct might be to tell him to “just talk less.” That, at best, is gonna convey that you are an authoritarian manager who makes crazy demands. Remember that Sam doesn’t know what his communication style is resulting in, if he did he wouldn’t do it. Another potential outcome is he clams up in fear of you and stops sharing his opinion at all. But if you can connect Sam’s behavior with the outcome, he will change his behavior, no explicit rewards or punishment required.</p><h3>How Often To Give Feedback</h3><p>Give feedback immediately after an issue occurs. Don’t bottle it up for a quarterly performance review. Once a quarter is simply too infrequent to get feedback, and it is asking a lot for an employee to hear a half dozen different notes all at once and take action. If you’re a manager you need to be devoting time every single day to management, and that gives you time to give feedback each and every day if necessary.</p><p>Even more importantly, every employee should be working on at least one area of their performance or capabilities at all times. A growing person is a happy person, and feedback is critical for growth.</p><p>If you miss an opportunity to give feedback that’s ok! If it’s a serious problem, it will come up again (if it never comes up again, mission accomplished!). The further away your feedback is from the event, the harder it can be to apply, give it quickly, and don’t fret if you miss your chance.</p><p>You also don’t want to wait for a negative behavior to give feedback. Give positive feedback too! You want to reinforce good behavior even more than averting negative. Here’s an example:</p><blockquote>You: “Hey Claire, can I give you some feedback?”</blockquote><blockquote>Claire: “Sure, shoot.”</blockquote><blockquote>You: “When you point out issues with the project planning it keeps the quality of the product high and the schedule on time, great job.”</blockquote><p>Preventing negative behavior is great, but what we really want is uniquely positive behaviors: acts and ideas which we didn’t even expect and which raise the bar throughout the organization. You need to identify when someone is doing something well and let them know.</p><p>For some reason positive feedback seems to take more emotional vulnerability than negative. Maybe it’s a reflection of the idea that anyone can complain about things, but suggesting a solution exposes you to the risk of being wrong. Don’t let this stop you, be vulnerable, when you appreciate something, express it!</p><p>If you don’t seem to find positive things to say about an employee, you’re not trying hard enough. Do what you would do with any other problem: sit down with a piece of paper and brainstorm. Everyone is doing something right, even if it’s just contributing their unique perspective to the team.</p><p>Finally, it’s worth mentioning that positive feedback should often be given publicly, but negative feedback must always be given privately. Our goal is to create good future behaviors, not to shame anyone for a mistake made in the past.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8f9bae21ff2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to Ask at One-on-Ones and How To Kill The Awkwardness]]></title>
            <link>https://medium.com/startup-grind/what-to-ask-at-one-on-ones-and-how-to-kill-the-awkwardness-e4e12592214f?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4e12592214f</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Mon, 13 Mar 2017 21:02:01 GMT</pubDate>
            <atom:updated>2017-03-13T21:02:01.436Z</atom:updated>
            <content:encoded><![CDATA[<p>A <a href="https://medium.com/@zackbloom/youre-doing-one-on-ones-wrong-dfc27f36f204">one-on-one</a> is a meeting between you (a boss) and one of your direct employees. It’s purpose is to allow you to build a relationship which is honest and deep, rather than superficial and procedural. Here are some questions which you can ask to learn about your directs:</p><ul><li>What do you want to get better at?</li><li>How’s your family?</li><li>Is there anything that’s frustrating you?</li><li>Where do you want to be in five years? What skills do you need to develop to make that happen?</li><li>What makes me difficult to work for?</li></ul><p>Many of these questions won’t have immediate answers, particularly if your directs aren’t used to being asked them. If there isn’t an immediate answer, let them think on it and something will come up at the next one-on-one.</p><p>Some of these questions might seem a little personal, and they’re supposed to be. There is a simple trick to make them not awkward though: <strong>share your answer to the question before asking it</strong>. It shouldn’t be more than a sentence or two (this is time for your direct, not you), but opening with something about yourself <strong>will make the awkwardness magically disappear</strong>.</p><p>Personal relationships ratchet, as one side exposes a bit more vulnerability, it allows the other party to expose a bit more themselves. <strong>If you expect your direct to expose everything, and you nothing, you’re conducting an interrogation, not a conversation.</strong> Like most of life, you have to give as much as you expect to receive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4e12592214f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/what-to-ask-at-one-on-ones-and-how-to-kill-the-awkwardness-e4e12592214f">What to Ask at One-on-Ones and How To Kill The Awkwardness</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You’re Doing One-on-Ones Wrong]]></title>
            <link>https://medium.com/@zackbloom/youre-doing-one-on-ones-wrong-dfc27f36f204?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfc27f36f204</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Fri, 10 Mar 2017 21:46:43 GMT</pubDate>
            <atom:updated>2017-03-10T21:46:43.820Z</atom:updated>
            <content:encoded><![CDATA[<p>One-on-ones are a common management tool where you have a (wait for it) one on one meeting with a direct report who works with you. Like many management fundamentals though, <strong>our natural instinct on how to conduct them is dead wrong.</strong></p><h3>Vulnerability</h3><p>The instinct for the new manager, particularly for a new engineering manager, is to use a one-on-one as an opportunity to review the past week’s work. To check on what needs to be done and what has been done and update themselves on where the project stands. This is a very human desire, both because we want to know how things are going, and because this line of communication involves no emotional vulnerability whatsoever.</p><p>Communicating like this allows you to play the very easy role of ‘boss’. You talk about work matters in your work voice wearing your work clothes. This is a great way to reinforce a work-type relationship where you don’t know or care much about your employee: you pay them to do a job and they do it (or don’t). <strong>But you’re not actually mimicking a boss you would want to have, you’re playing the role of a boss from your nightmares, a Bad Boss</strong>. It’s not an environment I would chose to work in, and it’s not a way to get exceptional performance.</p><p>If you want to be a boss worth having you need to develop real, human, relationships. That is the basis for growing your people into more capable workers, for helping them achieve their goals, and for helping them to be not just functional, but happy. How do you build real relationships? You drop the veneer of manager and expose your true self. <strong>You talk about what you’re worried about, what you’re excited for and what is going on in your life. Even more importantly, you ask the same from your direct.</strong></p><h3>The One Rule</h3><p>This takes us to the one rule of one-on-ones: <strong>It’s not a progress report</strong>. Your direct should not be giving a rundown of what they did that week. If you need that information, have them send you an email, set up another meeting, or start running Science Fairs where your people can present what they’ve accomplished. The one-on-one is a place for the direct to talk about things which explicitly don’t get communicated in those settings. Things like, their long-term goals, their happiness and satisfaction, what they’re worried about, what they’re excited for, what’s happening in their life which you may not know.</p><p>The reason the one-on-one is so important and so sacred is because you will never hear these things without one. If some of the more serious issues are coming up during the work day it means things are coming to a head and you needed one-on-ones a long time ago. The most likely course though is they don’t come up. <strong>You will never know why Jim’s performance took a dive this week, or why Claire left (she wasn’t growing), or that Kevin would love to move into a more customer-facing role and was perfect for that Sales Engineering role you ‘can’t hire for’.</strong> You will never know anything about your people beyond the superficial, and that information is exactly what you need to be a great boss.</p><p>Showing up, sitting in your desk chair, answering emails, knowing what your people are doing day to day, those are all the admission price for being a boss. By learning more about your people you begin to make move from acceptable to exceptional. In fact, I would make the bet that once you start doing real one-on-ones, true conversations where you expose parts of yourself and get the same from your people, you will never stop.</p><h3>Using The Information</h3><p>What can you do with this information? You can, for one, avert crises before they become disasters. When you know someone is unhappy, you can work to change that. You can make sure everyone on your team is working with you to cultivate a new skill and improving themselves. You can genuinely say that you know your people, know how they feel, and that they are satisfied and growing.</p><p>You can also show them, through your investment in this process, that you care about them. <strong>You are demonstrating your interest in their success, not just in this moment on this team, but in their career, and their life, as a whole.</strong> That is what it is to be a great boss, and honest and deep one-on-ones are the path.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfc27f36f204" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Making Excuses]]></title>
            <link>https://medium.com/@zackbloom/stop-making-excuses-a4bd09d0aa26?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4bd09d0aa26</guid>
            <category><![CDATA[procrastination]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Fri, 03 Mar 2017 13:58:09 GMT</pubDate>
            <atom:updated>2017-03-03T13:58:09.964Z</atom:updated>
            <content:encoded><![CDATA[<p>The pre-frontal cortex of our brains is an excuse machine. It is where our rational mind sits, quietly observing us fulfill or resist our natural tendencies, and trying to pretend it was all on purpose.</p><p>One of the purposes of this part of our brain is to align our observations with our world view. For example, when you slip and fall, it’s because the ground was icy, not because you’re clumsy, because you know yourself not to be clumsy. Of course, if your self-esteem is not that great, you have a different world view, and that very same slip and fall will become a personal failure of your sense of balance.</p><p>Most of us have, fortunately, not accepted into our world view the idea that we’re lazy or worthless. This means when we don’t get out of bed on time or don’t get to the gym when we should, we need to rationalize and justify. Our prefrontal cortex needs to make an excuse. “I had a long night last night,” or “Today’s a big day, I need the sleep,” or “That damn garbage truck woke me up at 4am,” or any manner of excuses which align our behavior (laziness) with our world view (responsible, hard working, adult). Stop.</p><p>Stop making excuses. We all fail to live up to our expectations every now and then. In fact, if your expectations are high enough, you will fail to live up to them in one way or another regularly. It’s just not possible to fill every hour of every day with productivity, and that’s ok. When you admit that, and accept your weakness, it sets you up to make a better decision next time.</p><p>There is always a reason not to do something, just as there are always great reasons to do it. You will always be able to point to an annoyance, an extra chore, an important presentation, which will give you a justification to not accomplish your goals. But all of that points the blame outward, at all the things you can’t control (like what time the garbage truck runs), instead of at the one thing you can, yourself. At the end of a month, or a year, or a lifetime, all you’ll have to show for it is a whole lot of not-accomplishment. You are fundamentally accountable for achieving what you care about, no matter who or what gets in your way. We are rational, thinking, beings capable of shaping our environments and creating opportunities for ourselves, there are no excuses.</p><p>This can get even more insidious when you are making a decision. When you’re lying in bed deciding if you will get up and go to the gym or hit snooze, how rational are you being? Ask yourself “Am I being objective? or do I really want to come to a specific conclusion here?” If your primitive brain really wants you to pick one of the two outcomes (Sleeeeeeppppp), drop the excuses and accept it: “Damn, this sucks and is not ok, I refuse to justify it, I have to do better, zzzzz.”</p><p>When you have to accept your own laziness to get that last bit of sleep, you will find yourself significantly more likely to get out of bed. In a world without excuses, you will be able to honestly account for your normal human weakness and make decisions which help you to achieve your goal behaviors in the future.</p><p>Excuses can be a hard habit to break. When you next feel yourself justifying something you would like to be true, or are afraid is true, stop. Accept it for what it truly is and that you can, and must, do better next time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4bd09d0aa26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Make Your Team Better]]></title>
            <link>https://medium.com/@zackbloom/the-quickest-way-to-develop-your-people-31baa638e067?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/31baa638e067</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Tue, 14 Feb 2017 16:25:04 GMT</pubDate>
            <atom:updated>2017-03-03T14:01:30.819Z</atom:updated>
            <content:encoded><![CDATA[<p>The general view in business is that moments of increased responsibility are few and far between, synonymous with promotions. This all-or-nothing model of growth is not the best way to run a high-performance team.</p><p><strong>If growth is a key ingredient for happiness, every single member of your organization should be working to improve some dimension of their performance any given moment.</strong> In the high-performance world there is no such thing as a stagnant, happy, employee. This personal improvement requires taking on new challenges, and challenge is often synonymous with responsibility. For example, writing a blog post means you are responsible for how the company is seen by the world. Managing an intern makes you responsible for his or her experience and for the work he or she does. Taking ownership of a part of the product makes you responsible for the ability of your users to get their jobs done.</p><p>New responsibility is not something you take on once every few years. In a high-performance organization your people must always be taking on new small responsibilities as they challenge themselves to grow. To create that environment, you must support their growth by aggressively delegating anything and everything possible as they become ready to take on new challenges. No part of your work should be reserved from this including management itself! If you have an employee who is close to being capable and they have the time and inclination to take on the responsibility, they should be doing it, not you. <strong>That</strong> <strong>aggressive delegation frees you to focus on what your true fundamental responsibility is: their growth.</strong> It makes them capable of doing your job, so you can grow, in turn.</p><p>Granting an employee a new responsibility can be one of the most nerve wracking experiences for a manager however. They’ve never done this before, what if they do it poorly?! What if I could do it better!? The truth is though, once we’ve decided growth is our first and foremost objective, that no longer matters. It’s not a question of who could do it best, it’s a question of what will improve our collective capability the most. The answer to that is generally clear: <strong>it’s the person who has done it the least who stands ready to learn the most</strong>.</p><p>Functionally though, its not fun having inexperienced people doing new jobs. How do we make sure they’re actually learning, not just doing sub-par work? The answer is simple: <strong>no responsibility without accountability</strong>. No one is given a task without understanding the goal and that they are responsible to meet it. Failure can be a valuable learning experience and isn’t necessarily to be feared, but <strong>the one thing we absolutely can’t tolerate is the same mistake made repeatedly</strong>. In other words, failure without learning. This type of failure generally happens when the person making the decision is separated from the result of their decision making.</p><p>They are given an important task in a big project, but it’s never explained what they’re accountable for or what will happen if they deliver late. Possibly due to the lack of that information, they don’t meet their deadlines. The big project misses it’s deadline, bosses grumble, but it’s never really connected back to the actions of our fearless explorer who persists in demanding even more power.</p><p>With accountability, mistakes are productive. Your direct can see how his or her failure led to not yet reaching the goal he or she is accountable for, and can stay focused. Each misstep is a learned lesson, not to be repeated.</p><p>But how do you prevent those mistakes from ever getting made without just telling your direct what to do? Coach with context. Don’t order anyone around, instead explain what you would do and why. If they have a different plan explain how it might go wrong, what the consequences of that are, and then leave them to make <em>their decision.</em> <strong>That ownership, the freedom to make a mistake (or a brilliant innovation), is critical to growth.</strong> I’ve found that people are never more clear thinking and amenable to a good idea than when they are in control.</p><p>Think back to your most valuable learning experiences. They probably happened during your periods of least supervision, when you were free to actually make mistakes. This doesn’t mean you can’t coach and guide. It means <strong>the more control you exert, the less your direct learns</strong>. You have to manage to provide context and guidance, without taking away autonomy to the greatest extent possible. Your control is over how much responsibility you choose to give this person, that’s your job, not to explicitly what they do with it.</p><p>But what if they’re making a horrible mistake? Then <strong>give them more of your time and attention</strong> in the form of coaching. No one willingly makes a mistake. If your direct doesn’t see the consequence of their actions, this is your moment to teach! If, despite your best efforts, they don’t see the cause and effect, your next move is to make sure it is crystal clear upon failure what happened. Get the goals and the potential consequences written down, and if at all possible, let the failure happen. There will be no greater learning experience.</p><p>Of course, it’s also your job to, in the background, work to see that that failure isn’t disastrous. It also may prove that the level of responsibility you granted was too much too fast, but that isn’t my experience. My experience is that as long as your direct is honest and open to being coached, they can be coached. <strong>The amount of responsibility granted translates to how much of your time it will demand, not the potential for success</strong>. And, of course, you have time to do this coaching, your real job, because you’re delegating everything that isn’t, right?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31baa638e067" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Focus on Growing Your People, Let Performance Take Care of Itself]]></title>
            <link>https://medium.com/@zackbloom/leadership-practice-vs-performance-a8bb4c7032c8?source=rss-af5af901a9d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8bb4c7032c8</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Zack Bloom]]></dc:creator>
            <pubDate>Tue, 07 Feb 2017 14:06:48 GMT</pubDate>
            <atom:updated>2017-03-03T13:59:28.225Z</atom:updated>
            <content:encoded><![CDATA[<p>When we think of the business world, very little of the time we spend is devoted to ‘practice’. Perhaps we prepare for a big presentation, and many of us went to school, but the vast majority of the time is considered the performance: actually doing our jobs.</p><p>I think this is incorrect. <strong>Businesses are long-term prospects.</strong> We don’t start a business, grow it, and then give one good talk or write one good paper, and then wrap it all up. There are challenges today, but there are also challenges tomorrow, next week and next year. What is more productive, delivering the better results this moment at the expense of the future, or delivering better results for all time? If you believe at all in investment, you know compounding results are always better.</p><p><strong>The only times of true ‘performance’ are crises.</strong> Moments which could break the business and which must be handled decisively using the best tools we have. The website is down. We’ve had a data breach. The plant is on fire. These moments must be handled as the military handles combat, decisively.</p><p>Most other moments are not combat however. A quickly corrected misstep, a missaid word, would not hose the business. Absolute perfection, even if it were attainable, isn’t required. In that environment, there are countless opportunities to get better at our jobs, rather than just performing them.</p><p>If we can build this culture, we will be improving ourselves and our people every single day, accomplishing what I would say is <strong>the ultimate goal: to build a team of incredible people who can get anything done.</strong> That should be our true goal, to build a team of people who are so terrifyingly competent they can be trusted with any challenge.</p><p>Building an organization which focuses on personal growth also has tremendous recruiting value. What’s easier, to recruit superstars, or to recruit new grads out of college? <strong>If you have a system which can train and develop a new grad, you get to hire them.</strong> This also has a huge impact on diversity. Underrepresented populations remain underrepresented not because they have less potential, but because they have less experience. If your organization knows how to grow people, you can hire based on that potential.</p><p>Potential will always beat current performance in the long run. <strong>If you take someone who is motivated, smart, and has the right goals, that person will most likely accomplish those goals because they’re motivated and smart.</strong> I would rather have that person do that at my organization than elsewhere when they do.</p><p>Fostering personal growth also has a massive impact on retention and employee happiness. <strong>If I had to encode what ‘happiness’ is for a human, it would be having connections to people and getting closer to goals every day. </strong>An organization which helps you get closer to your goals is one you want to work at, and you want to give your best because you know that will translate into even more opportunities. It’s an organization which makes it’s members happier for being in it, not more miserable.</p><p>This is not human development at the cost of performance. There’s a quote by a famous football coach which goes <strong>“The score takes care of itself.”</strong> If you develop the people, winning is inevitable. In general, if you manage to have the best team with the strongest people, it’s not likely you will fail.</p><p>There is a tremendous chasm between beat down employees who rely on a leader to guide them, and empowered employees who grow every day and are able to apply their full mind to the problems they face. One is a company which amplifies the will of one person, the other is a terrifying force of warriors, each owning what their responsible for and improving it every day. <strong>I know which I would rather build.</strong></p><p><strong>Except in times of crisis, the first goal, above even the quality of our product, should be to improve our skills.</strong> That’s an environment where you can delegate confidently, where everyone is growing and learning, and where, paradoxically, the very best products get built.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8bb4c7032c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>