<?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 Geoff Kerr (Vona) on Medium]]></title>
        <description><![CDATA[Stories by Geoff Kerr (Vona) on Medium]]></description>
        <link>https://medium.com/@geoff.aj.kerr?source=rss-8e7f873e4e00------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*T0Rlc40v7uXZnUDp</url>
            <title>Stories by Geoff Kerr (Vona) on Medium</title>
            <link>https://medium.com/@geoff.aj.kerr?source=rss-8e7f873e4e00------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:27:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@geoff.aj.kerr/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[Wanna Coach? Go Suck At Something!]]></title>
            <link>https://medium.com/@geoff.aj.kerr/wanna-coach-go-suck-at-something-4eb489f4fd93?source=rss-8e7f873e4e00------2</link>
            <guid isPermaLink="false">https://medium.com/p/4eb489f4fd93</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Geoff Kerr (Vona)]]></dc:creator>
            <pubDate>Fri, 11 Nov 2022 22:45:05 GMT</pubDate>
            <atom:updated>2023-07-17T21:27:50.159Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/248/0*q-ePc2qnB7qKG1_6" /><figcaption>Sometimes it does not suck to suck…</figcaption></figure><p>There’s a debate about whether performance-oriented individuals should focus on their flaws (so-called growth opportunities), or lean into their strengths. I don’t really know. Like most things human, it is probably an iterative mix that you can’t really prescribe.</p><p>What I can say is that if you want to be a really good coach, you have to understand what it is like to receive difficult feedback But, taking feedback in the same setting in which you give feedback is (in my opinion) a false path. You become conscious of taking feedback as connected to your own performance as a feedback provider. The result is a bit of a show — you graciously accept feedback so that you can reference it when you next give feedback. Most likely, the feedback you receive isn’t all that pointed. After all, if you’re coaching in a particular context, you’re performing well in that context. The whole cycle is insincere.</p><p>I believe the best way to truly understand what it is like to receive feedback is to put yourself in a situation where the feedback you receive is pointed, tough, even harsh. That means doing something you’re not good at. More bluntly — find something you suck at, and get feedback on your performance.</p><p>I use hockey. I learned to skate as an adult (at 40!), and I don’t have a history of playing the game. This year, I signed up for a men’s league that’s above my level of play. My team is a good fun loving group, but they want to win. As part of closing out a game, I took a face-off in our own end — and shot the puck straight at our goalie. Then I lined up in the wrong spot and almost let a winger break free for a shot. A couple of teammates gave me direct, immediate feedback on both plays. No shit sandwiches — just stop playing like shit. Now.</p><p>It didn’t feel good to hear the feedback, even though I knew they were absolutely right. I’m there to learn and get better, but it was humbling and made me feel like crap. As someone who gives feedback every day, it is <strong>critical</strong> that I <strong>understand deeply</strong> what it is like to receive hard feedback. It makes me a better coach.</p><p>So go suck at something. Take your lumps.</p><p><em>Originally published at </em><a href="https://geoffkerrblog.wordpress.com/2022/11/11/wanna-coach-go-suck-at-something/"><em>http://geoffkerrblog.wordpress.com</em></a><em> on November 11, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4eb489f4fd93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Perspective]]></title>
            <link>https://medium.com/@geoff.aj.kerr/perspective-9dc5bb057bae?source=rss-8e7f873e4e00------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dc5bb057bae</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Geoff Kerr (Vona)]]></dc:creator>
            <pubDate>Fri, 13 May 2022 20:17:09 GMT</pubDate>
            <atom:updated>2023-07-17T21:33:56.453Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XDQFYE320Fsou5VHS_kRIg.jpeg" /></figure><p>My wife is a Respiratory Therapist. When we were both young, pre-kids, we worked hard and took vacations at our family cottage. Taking vacation in the 90s was tough — there wasn’t the same respect for rest and renewal as exists today. I tried to get out early, but got pulled into a series of meetings and emergencies that kept me late. Traffic was bad on the way home. We were late, and I was in a foul mood.</p><p>We had all our vacation items packed and laid out on the driveway. My wife was doing final checks in the house. I was firing our items into the car at high velocity, grumbling about how hard my job was. I went to grab a pair of my wife’s shoes, but she suddenly appeared.</p><p>“Stop! Don’t touch those shoes!”</p><p>“Why not?”</p><p>“They are from work today. We had a code. Someone had an aneurism. Those shoes might have brains on them. I’ll got get a plastic bag.”</p><p>Instant perspective shift.</p><p>Absolutely my job at the time was tough — I was taking on more responsibility and trying to balance a number of business demands. But at no time was I ever — NOT EVER — at risk of getting brains on my shoes.</p><p>Perspective is key. It helps you truly understand the appropriate amount of stress and pressure you should feel in any given situation. It also helps you empathize with the lived experience of others. At that moment, with my wife and her shoes, I felt stress drain out of me as my perspective shifted. It was amazing how effective perspective was at pushing back on stress, pressure, and anger.</p><p>I’ve been on the other side of that perspective divide as well. In the early pandemic days, much of the world was locked down and idle. Friends, family and neighbours all mentioned how they were relaxed and bored. There were news pieces on the perspective shift for society, how we would all value work differently, re-evaluate our relationships, etc. But as a manager in FBA at Amazon, my lived experience in the early pandemic was 20 hour work days 7 days a week for the entire spring. It was brutal, and I was exhausted. When I talked to people, I could see their perspective change. I saw what my wife probably saw in me when we were packing for vacation all those years ago. People would stare for a moment while they processed the perspective change. Most of the time they’d change their tone, recognizing that being bored was preferable.</p><p>There were a couple of perspective-shifting events for me this week. First, my 20-year-old son started a new job at a local tech company. We were talking through his onboarding steps when he mentioned that there would be an introduction to the entire company. He was legitimately excited! He felt it would be the highlight of his week — to get introduced to all these new, important people in a company he really loved. In my career, I’ve written dozens of “Welcome Bob/Sue” e-mails. It feels routine. That bit of perspective helped me remember that what might be a mundane task for me is a key turning point for someone else. Put a bit more juice into it, right?</p><p>Later in the same week, I was at our first outdoor company event of the year. It was a great day in general — so many people in the office, great energy. My wife and I were sitting and chatting when a group of young engineers came up to me. They wanted to know if they could introduce themselves to me. I could see that they were a little scared and also excited. Would the CTO talk to us? Would he care about us? I’d forgotten what it is like to work up the courage to talk to a senior person at a company event. Of course I think of myself as approachable. They don’t know that. I’m just a scary old guy with a beard. We had a nice chat about where they live, how they get to work, sports, the party — smalltalk. It was fun. I think they enjoyed it. My wife and I talked about it afterwards — how they were nervous, not sure if I would talk to them. It is easy to forget that other people see gaps and barriers that you don’t believe exist. That perspective is key. I can say “I have an open door, bring me your issues”, but it is meaningless without understanding the perspective of my team.</p><p>There are still perspectives to understand, and trust to earn.</p><p><em>Originally published at </em><a href="https://geoffkerrblog.wordpress.com/2022/05/13/perspective/"><em>http://geoffkerrblog.wordpress.com</em></a><em> on May 13, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dc5bb057bae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fighting that Overwhelmed Feeling]]></title>
            <link>https://medium.com/@geoff.aj.kerr/fighting-that-overwhelmed-feeling-da9ac2870170?source=rss-8e7f873e4e00------2</link>
            <guid isPermaLink="false">https://medium.com/p/da9ac2870170</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Geoff Kerr (Vona)]]></dc:creator>
            <pubDate>Tue, 03 May 2022 20:57:40 GMT</pubDate>
            <atom:updated>2023-07-17T21:37:42.878Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MPOtErM9sQe1ugRDE6Ba6w.jpeg" /></figure><h3>Fighting that Overwhelmed Feeling</h3><p>Where does that overwhelmed feeling come from? It comes from a feeling of loss of control. The fastest way to address it is to take back control over what you do.</p><p>Work-life balance is not possible without work balance. You need to balance what you’re doing with what your team and peers do for you, all at the right priorities. Taking ownership of everything is not balanced.</p><p>What follows is a collection of suggestions and thoughts on fighting that overwhelmed feeling.</p><h3>Scheduling</h3><p>Color your schedule: must attend, should attend, if possible, repeating meetings, personal. The color helps you know at a glance if you’re making the right trade-off. Skipping an “if possible” meeting shouldn’t make you feel bad.</p><p>Use your admin to help. Booking a meeting, finding a room, organizing a lunch, etc — these are not value-adds for your job.</p><p>Flex your schedule. Being in the office just for visibility is nice if you have time. If you don’t, make sure you are leveraging your in-office time optimally. In-office time is for 1:1s, team meetings, relationship building, and efficient information transfers. If you’re in the office but at your desk doing heads-down work, you’re probably making the wrong choice. Use other hours in the day.</p><p>It is easy to lose control over your schedule. If you find your days are full of meetings, be conscious of which ones you are only mechanically attending. If you spend much of your time in a meeting on email, you shouldn’t be in that meeting.</p><p>Be empowered to walk away from meetings after you sense that your presence is not required or adding value to the discussion.</p><p>Do you know what must be delivered this week? Tasks all require attention, but they should be ordered based on due dates and your priorities. It takes planning to know when an item is due.</p><h3>Most Important Tasks</h3><p>Personal takes highest priorities. There are instances where you will have to sacrifice a personal event for a work emergency. There are a limited number of times you can do that without feeling guilty or feeling that your job is unreasonable. Use those times wisely. You’ll feel better.</p><p>Sacrificing personal things has a non-linear impact on how you view your job. Missing kindergarten graduation or your grandmother’s birthday party hurts disproportionately. You amplify the disappointment of your friends and family and direct it at your job. Make sure that the important personal things are immutable.</p><h3>Presence</h3><p>Presence is one of the hardest things to do for busy multi-taskers. To be completely present in a moment, you must context switch and focus. It is common for busy people to be physically present but mentally absent. One of the key multipliers for your effort is being physically and mentally present for everything you do, whether it be work or home life. Practice focus. If you’re meeting with people, put down the phone, shut the laptop. If you’re in a meeting, make eye contact and read body language. For remote meetings, I recommend using video — it forces you to be present in the meeting. (Granted, given WFH and COVID, this isn’t always an option. We understand. )</p><p>If you need to do some heads-down work on a document, book a room, shut the door, and make sure you have an immersive environment that allows you to focus. Use full-screen mode for what you’re working on. If you’re writing a document, use all the screen real estate. You don’t need to also look at your email and messaging — focus on the job you need to do, then move on. Pro tip: for personal events, don’t film it or focus on taking pictures using your phone. Put the phone/camera down and Be There!</p><h3>Multitasking</h3><p>Context switching is a key part of presence. How do you context switch? Think about what it takes for you to move on from the last thing you were doing. If you aren’t done, what do you need to do to allow yourself to move on? I use my book to record key details I can revisit later. That’s not the only technique — sending yourself notes or reminders on your phone is another. Some people can context switch without “offline storage”, but it takes practice. Getting better at context switching starts with being conscious that context switching is a thing.</p><p>A better rule for multitasking is to avoid it entirely. If a task can be done in less than 2–5 minutes, do it immediately. You’ll save interruption time.</p><p>The greatest time drain is interruptions. Think of it in computer terms — stop working; calculate state; store state; switch to the new task; load state; continue working. All of these steps are wasted if you need a few more minutes to finish. Try to work concentrated in chunks of 50 minutes and take a 10 min break after that. Ideally, get up from your desk and walk around — go to a different floor at work, or just to a different room at home if you’re WFH. Even a few minutes outside can be beneficial.</p><p>Above all, turn off desktop alerts and notifications — sound and visual. You should choose when to change tasks. Alerts and notifications take the choice away from you!</p><h3>Delegation and Career Growth</h3><p>Delegation is key. Who is your replacement (or who are your replacements) when you’re on holiday? Now extend that — who would help you if you were away for an extended period? Who would take over for you if you left?</p><p>Delegating tasks means empowering people to do more. If you can delegate every aspect of your job to a team member, you’ve stretched your teammates to do more. This will help them with promotion velocity and guarantees that you have a solid succession plan.</p><p>It is common for people to view their work in terms of a linear increase in hours worked that delivers a benefit. <strong>This is wrong</strong>. To advance in your career, you need to think in terms of multipliers and amplifiers that allow you to scale your work capacity *beyond* the hours available in a day. If you’re working 12 hours a day as a senior engineer, do you think you need to work 14–16 hours to move up to staff? That’s not a promotion, that’s punishment for working hard. Think about getting to that next level by your hours worked and leveraging skills like delegation, schedule optimization, prioritization, automation, planning/organization and presence to multiply your impact.</p><p>The hardest part of a promotion and role transition is to get rid of (a.k.a. transition) the old responsibilities and habits. Most of the habits that made you successful as an X will not necessarily make you a successful Y. Habits are very hard to change but run most of your days (~95%). Keep track for a few weeks of everything that you do and review it on Friday or Sunday.</p><h3>Responsibilities</h3><p>If you do work, you accumulate responsibilities. Most people add new things to their list of things and try to balance. Try to avoid accumulating responsibilities. The fastest way to grow your career is to maintain the right set of responsibilities: taking in only those responsibilities at the right priority level, and letting go of those that have shifted lower on your list. Instead of accumulating, think of the responsibility list as a fixed-length list. If something comes in, something else should go out. This won’t happen easily: it is far harder to remove an old responsibility than it is to take on a new one. But even the act of considering what to drop will force you to adjust the priorities and, eventually, the time spent. Don’t view a dropped or shifted responsibility as a failure. If something fell to the bottom of your list, and someone else picked it up, then we are most likely closer to the overall optimal work assignments. The way to claim victory on a dropped responsibility is to be proactive about it. Identify what you should drop, find an owner, and transition.</p><h3>Daily Routine</h3><p>Make sure you optimize your time as much as you can. That doesn’t mean doing multiple things at the same time. What it means is choosing the best time to do something. If you commute by train, that’s probably the best time for e-mail sorting or reading documents. Some people find mornings are the best time to organize the day/week and prepare for meetings. Some use late evenings to answer email backlog or finish documents. There is no one right answer. The key is to know when you are best at specific tasks.</p><p>Here are some optimizations that might work for you:</p><ul><li>Use Sunday night for schedule pruning. Decide what meetings you need to attend, and which ones you can skip.</li><li>Set up for your day first thing in the morning. Organize your to-do list and have a plan for your day. You won’t always achieve your plan, but you have a better chance of achieving your plan if you make a plan.</li><li>Block your must-attend family events in your work calendar. Do you drop the kids off at school? No problem, book 8–10 every day. Do you have a dentist appointment? Block it out. Do you do volunteering work on Wednesday nights? Block it out. Don’t wait for conflict between your business and personal — reserve space for your personal things.</li><li>If you need to be in a meeting, put yourself on video if you can. It forces you to pay attention. Maintain eye contact as much as you can.</li><li>Take breaks. It is amazing how much renewal one can get from 5 minutes outside.</li><li>Change your routine! Sometimes, you need to work in a different space for an hour or a day.</li><li>Don’t stay in one location all day. Move to different rooms, get outside — whatever makes sense.</li><li>Evening meetings happen. Make sure that you tell your family about them well in advance to avoid disappointment and surprise.</li><li>Be transparent about your commitments. If you’re working at home, publish your daily schedule. Print it out and stick it to your door, or on the fridge.</li></ul><h3>Art of Pushback</h3><p>Pushing back on requests is expected. It demonstrates that you’re conscious of your workload (and your teams), and that you make good decisions based on priorities. Pushing back is a bit of an art. It requires that you have a good read on the requesting party. Some tips:</p><ul><li>Do you understand why you’re receiving the request? You may be at the tail end of someone else’s delegation. You may be the obvious owner. Or you may simply be the most convenient person to receive a request.</li><li>Avoid using zero-sum math to push back on requests. “The time I spend on this will cause a linear delay on project X” is exactly the wrong way to push back on a request. We don’t work in a robotic, arithmetic environment. Not every nanosecond of your day is allocated.</li><li>Phrase your pushback as a clarification — “How should I prioritize this request relative to X?”, “This might conflict with Y, any advice on how to resolve”. Try to push back in a conversational way. Invite the requestor to help you solve the problem.</li></ul><h3>Avoid Creating Work</h3><p>Sometimes we’re in such a hurry to get things off our desk, we don’t resolve them and, in fact, create more work. For example, if you escalate a task in an effort to make something go faster, you may actually slow things down. Sending something up the escalation chain can create the need for more meetings, summary documents, oversight, status reports etc. Only escalate when there is a dispute that cannot be resolved. If you cannot articulate two opposing and unreconciled points of view, then you don’t have an escalation.</p><p>Email is a great way to communicate, but sometimes it spirals out of control. Always read everything in a thread before replying, and reply to the latest relevant e-mail. Email is the best way to review things in text — for example a policy statement. Switch from email to a meeting:</p><ul><li>If there is repetition of questions or clarifications</li><li>If you cannot get a clear agreement or consensus</li><li>If the thread has gone on for more than a day</li><li>If the email chain is 2x the number of participants</li></ul><p>Don’t send emails when you are upset. In organized sports, we have the “24-hour rule”. If something is upsetting, let it sit for 24 hours before you make your issue known. Make sure you monitor your own emotions to understand if you need to invoke the 24-hour rule. Email is tone deaf — angry or even firm comments can come across in a way that creates unintended reactions.</p><p>If you feel the need to rant, do it in an email *with no recipients*, then <strong>delete the email.</strong> Never send.</p><p>What is the purpose of a discussion? What is the right outcome? Is what I’m about to say (or type) helping to close the conversation or move things forward? What’s my motivation for contributing it — to be heard? Am I simply repeating what else has been said?</p><p>Management is largely the art of compromise. You should always be looking for the common path or win/win scenario between the various sides on a particular issue. Taking a stand or “standing up for your team” is tempting, but most often creates unnecessary work. Finding a compromise is not a weakness. Strong pushback to show something to your team can create work, especially if it doesn’t help resolve the issue. Find other ways to stand up for your team.</p><h3>Measurement</h3><p>If you’re serious about improving anything…measure it! If someone feels constantly overwhelmed and they want to reduce it then measure it. Put a reminder in your calendar at the end of every day to rate your overwhelming feelings on a scale of 1 to 10. Put that into excel each day and graph it. Then ask yourself where you want to be in 1 day, 1 week, 1 month etc. Put that expected line in the graph. Then start implementing various suggestions in this doc and from elsewhere and watch your progress. Discard suggestions that don’t work and strengthen up suggestions that do. Once your steady state hits your target point consistently means you’ve developed habits that help keep it there. Discard the graph/tracking and keep doing the habits you’ve formed. Move on to the next thing you want to improve.</p><p><em>Originally published at </em><a href="https://geoffkerrblog.wordpress.com/2022/05/03/fighting-that-overwhelmed-feeling/"><em>http://geoffkerrblog.wordpress.com</em></a><em> on May 3, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da9ac2870170" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identity Traps]]></title>
            <link>https://medium.com/@geoff.aj.kerr/identity-traps-c40e441ae8ce?source=rss-8e7f873e4e00------2</link>
            <guid isPermaLink="false">https://medium.com/p/c40e441ae8ce</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Geoff Kerr (Vona)]]></dc:creator>
            <pubDate>Sat, 08 Jan 2022 01:14:26 GMT</pubDate>
            <atom:updated>2023-07-17T21:50:52.820Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lBVVJJUk4etM7dhk6iQiaQ.jpeg" /><figcaption>Sometimes it is hard to be unique…</figcaption></figure><p>Identity is important. Who you think you are forms the basis for your self-esteem and declared your alignment with your tribe. You belong because of who you think you are. But identity can be a trap. Who you think you are can prevent you from changing and evolving.</p><p>This is especially true for technical people. We have a tendency to form tribes and religions around technologies and processes. That creates a strong need to belong and choose, which in turn encourages odd identities. Ask a Product Manager what they do, and they’ll probably say “I’m a Product Manager”, then tell you about their product, their target market, or problems that drive their passion. Ask a Software Developer what they do, and they might answer “I’m a Rails developer”, or “Python/Django”, or “Mobile — iOS only”, or “Full Stack”, or some other indecipherable nonsense.</p><p>I’m as guilty as the next geek. At different points in time, my identity has been “VIC-20/Commodore 64”, or “6502/68000 but not x86”, or “C/XWindows”, or “OpenLook/Motif”, or “C++/OOD”, or “Java but not EJBs”. None of those identities roll smoothly off the tongue at dinner parties.</p><p>More importantly, none of those identities lasted longer than 10 years. Most lasted just a few years. When I look back on this chain of identities, each one led directly to the next. VIC-20 led to 6502 assembler and a distaste for Intel. The love of low level dropped me squarely in C for a long time, which led to a job working on XWindows. That in turn led to OpenLook/Motif. Dealing with graphics toolkits drove me to Object Oriented Software Development and C++. By 1995 I’d swung from tech to tech like Tarzan on vines, always grabbing the next related thing and clutching it with all my might.</p><p>Java disrupted tech-driven identity for me. By all measures, the beta version of Java was a derivative technology — a paltry subset of C++ with sad graphic capabilities, no access to the OS (by design!), and few libraries. But someone I respect asked me to take a look at Java and consider a role working on toolkits for this new technology. For the first time in my career, I was forced to ignore the pure identity-driving attributes of a technology and consider — in great detail — what problems it could solve. It fundamentally changed my approach to technology, and it shook my identity.</p><p>I worked with Java for a long time, but I was never a Java developer. Language and technology became secondary. I was creating a charting toolkit, then a collecting of graphical widgets, then a profiler, then performance management tools for almost any enterprise technology. I was able to move from problem to problem with greater agility because I no longer defined myself based on a single technology or approach. Even more important, my mindset was broader. I solved problems in a more general form — performance data gathering rather than Java JMX/PMI data gathering, for example. It enabled the creation of better solutions that lasted longer because they were more flexible.</p><p>It is critically important for young developers to switch their mindset away from specific technologies. I’ve been in this game for 40 years, and it <strong>fundamentally</strong> changes every 10 years. Centralized computing gave way to microcomputers and desktops in the late 80s, pushing interoperability in the early 90s. The Internet changed the game, shifting focus away from client/server and proprietary network protocols. By the early 2000s we were all creating back end services to be deployed on dedicated, hosted servers. Virtualization disrupted that game, and everyone wanted to be a VMWare admin. By 2010 the shift to the cloud was on, and the AI winter was ending with ML and big data. By the time we got through that decade, the shift to serverless, alternate data stores and scripting languages was underway. Everything a software developer uses today will be legacy in 5 years and dangerously obsolete in 10.</p><p>Tying your personal identity to a technology or process will limit your ability to solve problems and narrow your career path.</p><p>What could I have done differently? Thinking back to those early days, my bias against x86 formed out of tribalism and kept me from exploring that architecture. In the 80s and 90s, that’s a major missing tool. There were cool problems at interesting companies that were closed to me because of a personal bias. In a similar vein, when I was working on C++/OOD for a workflow system in the early 90s, I was highly focused on Object Oriented as the “right” way to create software. As a result, I worked for months (years?) to replace an existing functional system. It was a colossal waste of time and effort. Instead, I should have focused on approaches to workflow and orchestration. That would have had a lot more legs in the long run. Ultimately there was no meaningful advantage to a workflow system written in C++. In hindsight that sentence sounds ridiculous, but I remember being very passionate about it. Misplaced energy!</p><p><em>Originally published at </em><a href="https://geoffkerrblog.wordpress.com/2022/01/08/identity-traps/"><em>http://geoffkerrblog.wordpress.com</em></a><em> on January 8, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c40e441ae8ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>