<?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 Omri Gazitt on Medium]]></title>
        <description><![CDATA[Stories by Omri Gazitt on Medium]]></description>
        <link>https://medium.com/@omrigazitt?source=rss-aa297bd6572a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*akvrx_Djq9Upd4-0FbBQXg.jpeg</url>
            <title>Stories by Omri Gazitt on Medium</title>
            <link>https://medium.com/@omrigazitt?source=rss-aa297bd6572a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:11:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@omrigazitt/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[Tesla, one month in: the good, the bad, and the ugly]]></title>
            <link>https://medium.com/@omrigazitt/tesla-one-month-in-the-good-the-bad-and-the-ugly-95b83c46e5f5?source=rss-aa297bd6572a------2</link>
            <guid isPermaLink="false">https://medium.com/p/95b83c46e5f5</guid>
            <category><![CDATA[tesla]]></category>
            <category><![CDATA[self-driving-cars]]></category>
            <dc:creator><![CDATA[Omri Gazitt]]></dc:creator>
            <pubDate>Wed, 18 Apr 2018 04:54:02 GMT</pubDate>
            <atom:updated>2018-04-18T04:54:02.206Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3yuMVgro1WAqmX9ZW2dyPQ.png" /></figure><h3>The good</h3><p>One month in, I can say that my Model S is the best car I’ve ever owned, by far. It is an absolute joy to drive — incredibly smooth, quiet, and fast. Great handling, effortless cornering, silky suspension, insane torque. As a driving machine, it combines the best of my previous sports cars (Z28, Boxster, BMW 330ci, Audi S5) without any of the negatives (the rough suspension and poor fuel efficiency). My wife has heard me say “I love my Tesla” every day since I got it. And I hear her say the same thing, since we got her a Model X on the same day, becoming a full-on electric vehicle family :)</p><p>First — the obvious benefit of an EV: not ever having to stop at a gas station again is liberating. I plug the car every night into the wall charger, and at 72A and 45 miles of range charged per hour, the car is fully charged within an hour based on my daily driving patterns. As for longer trips, driving the 200 miles from Portland to Seattle required one stop at the supercharging station in Centralia (about half-way), and in the time it took for a Starbucks break (around 20–30min), the car was charged enough to make the rest of the trip: the 400A DC superchargers will charge the car at an astonishing 340 miles of range per hour.</p><p>Link many new vehicles, the Tesla has a built-in LTE radio and GPS, which help “light up” the standard amenities. For example, the HomeLink garage door opening system is tied into the GPS and map, so that when I get within 50 feet of my garage door, it automatically opens, and when I drive off, it automatically closes behind me. That LTE connectivity also means the maps app is completely self-sufficient, and the car can stream music with no reliance on third-party accounts or my iPhone for wireless service.</p><p>Much has been said about the driver-assist features — sometimes mischaracterized as “self-driving”. On the aforementioned trip from Portland to Seattle, I used the adaptive cruise control and the (beta) auto-steering feature. The experience was <em>transformative. </em>It felt like the car was driving itself for 98% of that trip. The adaptive cruise control kept the car driving under 80mph, slowing it down automatically when traffic got heavier, and speeding back up when traffic flowed smoothly. More impressively, over the three hour trip, the auto-steering kept me centered in my lane <em>better than I could have done as a human driver. </em>The other 2% of the time, I had to take action as a human — for example, when a lane split into two, I had to take over the steering— which I anticipated well in advance. As long as the driver understands that they are in control of the overall driving experience, and those features are thought of as <em>assisting</em> the driver as opposed to providing an autonomic driving experience, the driver-assist features remove much of the drudgery that leads to distracted driving. Overall I felt like the driving experience on a long road-trip was far safer while utilizing auto-steering and adaptive cruise control than without those features.</p><p>Last but not least, the Tesla is a software platform… with all of the good that comes with that fact. Over-the-air upgrades make the car better over time than when you bought it. As I mentioned before, maps and music are seamlessly integrated into the driving experience. Best of all, the Tesla has the first voice-input interface that I’ve ever found delightful: from “play Minus the Bear” to “drive home” to “call Sheri”, the car picks up the context from the keyword and does the right thing.</p><h3>The bad</h3><p>Unfortunately, the Tesla is a software platform… with all of the bad that comes with that fact. In the first few days, bluetooth stopped working. Tesla Service sent an over-the-air update to fix it, but it didn’t. They sent another update, which fixed the bluetooth issue, but broke the adaptive cruise control (!) Think about this for a second. A whole subsystem stops working because of a bad firmware update. Leaves you wondering — what other subsystems could fail with no warning? And indeed, I have heard experiences from other Tesla owners where the car just stopped driving in the middle of the freeway. That’s a scary thing — the last thing you want as a driver is for your brakes to “bluescreen”. In the end, I had to take the car into the service department and have them manually install a new firmware update, which cleared up all my issues… but it still left me concerned about the software platform reliability.</p><p>Another issue is that the range of my Model S 100D is advertised at around 315 miles on a full charge, but the car never charges over 90% (285-290 miles). Driving patterns greatly affect the actual range, and my 40 miles per day reduce the driving range by about 60 miles, so my effective range is less than 2/3 of the theoretical range. On the road trip, the math was slightly better, but definitely nowhere close to the supposed driving range at the start of the trip. Overall, I’m really happy that I took the advice of other owners and went with the largest battery I could get — I suspect that the 75D is closer to the LEAF in terms of effective range, and that would simply not work for our family.</p><h3>The ugly</h3><p>Tesla as a company is both wonderful and terrible. The experience with the sales associate was great — she was super-helpful, informative, and clearly passionate about the company, the mission, and the product. By contrast, some of the back-end processes are opaque, bewildering, and infuriating. I scheduled an electrician to upgrade our house to 320A service, put in a new panel, and install the Tesla-recommended wall charger, which increases charging speed from 30 miles of range per hour to 45mph. I ordered the wall-charger about 3 weeks before the electrician appointment, and the process was a complete black hole. No order tracking information. No answer from the email address of the online orders department. No phone number to call. Even the sales associate and her manager didn’t have a way of contacting the department aside from the same email address I had. After two weeks of total silence, I finally got an email that gave me a FedEx tracking number… for a package that went to Miami. After another week of radio silence, the wall charger came in… a day after the electrician appointment, frustrating both me and everyone at the local Bellevue store.</p><p>Even within the local store, there was no real coordination between the sales department and the delivery specialists. It was great being able to get an online quote for my trade-ins, but there was no way for the sales associate to communicate information to the delivery folks, and the latter had wrong trade-in information for both vehicles in their systems — making it clear that the customer-facing and back-end systems were disconnected and working off of different databases.</p><p>Overall, it was hard to believe that the same company that makes marvels of automotive technology could be so inconsistent and at times incompetent at some of the “basic blocking and tackling” of order fulfillment.</p><h3>In summary</h3><p>I love my Tesla. It is an absolutely wonderful car… <em>when it works the way it should.</em> Extrapolating from my first three weeks of ownership, the software platform reliability feels more like a computer than a car. Assuming Tesla continues to improve the reliability of the software platform, this may not just be the best car I’ve ever owned, but the last car I’ll ever own.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95b83c46e5f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I would have fired him too]]></title>
            <link>https://medium.com/@omrigazitt/i-would-have-fired-him-too-c3e4bdfaa5d5?source=rss-aa297bd6572a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3e4bdfaa5d5</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <dc:creator><![CDATA[Omri Gazitt]]></dc:creator>
            <pubDate>Thu, 10 Aug 2017 05:01:13 GMT</pubDate>
            <atom:updated>2017-08-10T05:01:13.640Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the last week, the tech world has been vibrating around a 10-page internal missive by a Google employee describing how the gender gap in tech should be attributed to biological differences between the genders that make women less suitable for technical or leadership work. This offensive and vacuous argument is wrapped in a “sandwich” of warning against the dangers of succumbing to a “lean-left monoculture”, and expressing frustration at being silenced and shamed for his political / ideological beliefs. Reading through the memo, it’s clear that the author’s true purpose is to divide and inflame as opposed to invite a genuine conversation about diversity and inclusion.</p><p>While any individual has the right to express their own views, it’s equally true that any company has the right to define a value system that clarifies what it believes in and stands for. When an employee’s “free speech” clearly breaches that value system by wrongly stereotyping women, offending a great many of its employees, and inviting withering criticism from the broader tech community, it’s crystal-clear that this employee has done real harm to the company and is not a fit for its culture.</p><p>I would have fired him too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3e4bdfaa5d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Joining Puppet]]></title>
            <link>https://medium.com/@omrigazitt/on-joining-puppet-241862b4ba11?source=rss-aa297bd6572a------2</link>
            <guid isPermaLink="false">https://medium.com/p/241862b4ba11</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[puppet]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Omri Gazitt]]></dc:creator>
            <pubDate>Wed, 08 Feb 2017 05:53:13 GMT</pubDate>
            <atom:updated>2017-02-08T05:53:13.726Z</atom:updated>
            <content:encoded><![CDATA[<p>The next stage of my professional journey starts next week — I’m excited to be joining Puppet!</p><p>Over the last 10 years, while working on distributed platforms at Microsoft (.NET App Server and Azure) and HP (Helion), every Enterprise we served was grappling with the ever-increasing complexity in managing large heterogenous IT footprints. The growing move to public clouds only exacerbates this complexity, bringing at least one more order of magnitude to the number of resources an Enterprise has to manage, making tools like Puppet even more essential.</p><p>Puppet is an iconic company in our industry, and has helped its customers tackle and tame this complexity over the last dozen years, becoming one of the most admired and successful companies in the continuous configuration automation space. But Puppet’s potential is not only to streamline operations, but also help unlock an organization’s development agility by decreasing the cycle time of evolving ideas into deployments, something I care deeply about.</p><p>I am humbled and excited to be leading a fantastic product and engineering team and working alongside a great executive team, and look forward to helping our customers acquire the tools and processes to transform their development and operations capabilities into business value that fuels their competitive advantage.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=241862b4ba11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Accountability]]></title>
            <link>https://medium.com/@omrigazitt/on-accountability-531780d67942?source=rss-aa297bd6572a------2</link>
            <guid isPermaLink="false">https://medium.com/p/531780d67942</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[accountability]]></category>
            <dc:creator><![CDATA[Omri Gazitt]]></dc:creator>
            <pubDate>Mon, 19 Sep 2016 04:16:43 GMT</pubDate>
            <atom:updated>2016-09-19T04:16:43.526Z</atom:updated>
            <content:encoded><![CDATA[<p>During the summer after my freshman year as a computer science student, the local medical school hired me to create a challenging program for one of their courses. A few weeks later, I realized that I was “in over my skis” and couldn’t deliver what I had signed up for. I kept trying different solutions over many weeks, telling the professors that the program was “right around the corner”, but ultimately had to admit that I couldn’t fix the issues. While I got to keep the money they paid me (which I desperately needed to fund next year’s tuition), the bitter taste of failure stayed with me for a while. I vowed that in the future I would make every effort to only sign up for what I could deliver, and then deliver what I promise.</p><p>A couple of years later, during my final summer internship with a telecommunications company, I signed up to create another challenging program. My boss was out for the entire summer on medical leave, and I was completely left to my own devices. This time, I spent many long nights and weekends at work while all the other interns were out partying, even though I wasn’t reporting to anyone and in theory could have collected my salary just for showing up to work every day. By the end of the summer I was able to deliver everything I promised, including lengthy documentation of what I had created. Weeks later, when I had already moved on to a full-time job at a startup, that boss called me, praised my work as first-rate, and offered me a full-time job (which I gratefully but politely declined). Even though I had gained no material benefit from working hard, that feeling of success was a greater reward than I could have possibly imagined.</p><p>The difference between these two early-career experiences sums up my conception of personal accountability: sign up for what you can deliver, and deliver what you promise. When the chips are down, and <strong>especially </strong>when the odds of success are low and the remuneration for delivering is nebulous, people who exhibit personal accountability will plow ahead rather than find excuses for why they can’t get it done. During those times where it feels like whatever you do doesn’t matter, <em>personal accountability matters most</em>.</p><p>As a manager, I’ve often heard the call to “hold employees accountable”. When people use this phrase, they often mean “this employee made a mistake, and they should get rebuked or fired as a result”. As a leader, I have a different interpretation of holding my staff accountable. In my experience, the most common failures are <em>lack of follow-through</em> and <em>errors in judgment</em>. Failure is endemic in all endeavors — if we don’t fail, we’re not trying hard enough. To me, holding someone accountable for failure means being satisfied that they have genuinely embraced that failure as a source of learning: that is, they will improve their follow-through in the future; and their judgment will improve as a result of the wisdom they’ve gained. Of course, as a manager, sometimes one has to make the difficult decision to part ways with an employee. For me, that is almost never due to a mistake they’ve made, but rather because that employee has consistently failed to show the personal accountability that is required to learn and grow from mistakes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=531780d67942" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>