<?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[The Startup Lifer - Medium]]></title>
        <description><![CDATA[Thoughts stemming from 30 years spent in software startups, from the the infancy of the internet to the emergence of AI - Medium]]></description>
        <link>https://medium.com/thestartuplifer?source=rss----84651de5bc7a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The Startup Lifer - Medium</title>
            <link>https://medium.com/thestartuplifer?source=rss----84651de5bc7a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:42:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/thestartuplifer" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AI and the Slow Death of Programming Languages]]></title>
            <link>https://medium.com/thestartuplifer/ai-and-the-slow-death-of-programming-languages-e7d45843f086?source=rss----84651de5bc7a---4</link>
            <guid isPermaLink="false">https://medium.com/p/e7d45843f086</guid>
            <category><![CDATA[future]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[programming-languages]]></category>
            <category><![CDATA[future-technology]]></category>
            <dc:creator><![CDATA[Ronen Magid]]></dc:creator>
            <pubDate>Sun, 30 Aug 2026 15:23:37 GMT</pubDate>
            <atom:updated>2026-09-01T00:37:52.971Z</atom:updated>
            <content:encoded><![CDATA[<h2>AI Is The End Of All Programming Languages</h2><h4>Or: The inevitable consequences of a seventy year old one-way linguistic bridge between humans and computers gaining an opposite lane</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*k08_lDmjXu-sLXcjeXrbsg@2x.jpeg" /></figure><p>Unfortunately — or fortunately, depending on how you feel about the language you’re currently fighting with — AI is a major catalyst pushing toward one inevitable outcome: the death of programming languages. All of them. Even the one you like.</p><p>The reason is simple.</p><p>Languages are for humans. That’s the whole point.</p><p>A CPU understands exactly one thing: its own instruction set. Assembly is just that instruction set with mnemonics bolted on so humans can pretend it’s readable. Every ISA has its own dialect — x86–64, ARM64, RISC-V — and none of them are on speaking terms.</p><p>In the dawn of computing, that was the job. You talked to the CPU directly, one instruction at a time, doing your own register allocation and hoping for the best. It was heroic. It was also a terrible way to spend a career.</p><p>So we invented programming languages. C, C++, Python, JavaScript, TypeScript — every one of them is an interface between the “metal” and a tired human being who prefers not to be tortured with assembly language. They aren’t the computer’s language. They’re ours, translated down. If someone told you tomorrow that your next large application had to be written in CPU-specific assembly, you’d start pulling your hair out before the meeting ended.</p><h3>The translators we built so we could stop crying</h3><p>The abstraction only works because there’s a toolchain under it. Compilers lower your source through an intermediate representation into machine code for a specific target. Interpreters and JITs do the same trick at runtime. LLVM’s entire reason for existing is “one IR, many backends,” so a single source tree can target a dozen CPUs without a dozen rewrites.</p><p>This is what saves us from writing an app for CPU A and then doing the whole thing again for CPU B. Just imagine debugging in that world. Imagine the upgrades. Most of what we call engineering discipline — build systems, package managers, type checkers, cross-compilation, linters that yell at you — is scaffolding around this one arrangement.</p><p>And every layer of it exists for exactly one reason: to keep humans from suffering.</p><h3>AI does not feel that pain</h3><p>Here’s the crux.</p><p>Everything in that stack is a tradeoff we accepted because the alternative was worse. AI doesn’t experience the tradeoff. A model can take a paragraph and emit efficient machine code for whatever ISA you point it at. It doesn’t need a high-level language to think in. It doesn’t get bored re-targeting to a second architecture, or a fifth. “Now do it for ARM” costs it approximately nothing.</p><p>The problem that compilers, IRs, and portable languages were invented to solve is a problem AI simply doesn’t have. We spent seventy years building a very nice ladder. The robot can fly.</p><h3>So why is AI still producing Python and Typescript code?</h3><p>Because we’re at the dawn of the AI era, and we’ve inherited a lot of stuff. Python, TypeScript, JavaScript, and a truly vast mass of C and C++, new and legacy — some of it older than the people maintaining it.</p><p>So today, most engineers prompt AI to produce code in human-oriented languages. That’s rational. Humans still review it, test it, and maintain it. Our CI pipelines, debuggers, and observability tools all expect source code. And the training data is overwhelmingly high-level source. Right now, AI is a code generator sitting on top of our stack, politely using our tools.</p><p>That’s a property of the transition, not the destination.</p><h3>Nobody builds a better cockpit for an empty plane</h3><p>Language design is an investment in human ergonomics. It only pays off if humans are the primary authors.</p><p>As AI progresses, the actual work of development shifts to an ever-shrinking number of humans and an ever-growing number of models. Once humans stop being the main authors, the incentive to invent new syntax, new type systems, and new runtime abstractions for human comfort drops to zero. You don’t fund a nicer interface for a user who left the building.</p><p>The same goes for cross-platform frameworks. React Native, Flutter, Electron, WebAssembly — all of them exist to amortize human effort across targets. When one more target costs a prompt instead of a rewrite, there’s nothing left to amortize. (No offense to any of them. They were good ideas. They still are. For now.)</p><p>In that environment, the most likely equilibrium is that native software gets built at the lowest level of abstraction and the highest efficiency available — straight against each CPU’s ISA. Each chip, in its native tongue.</p><p>So I expect a steady erosion of “human-readable” languages over the next 10 to 15 years, up to the point where they may not be necessary at all.</p><h3>Web vs. native: a distinction with no difference</h3><p>A second wall comes down along the way. The browser is, at heart, a universal runtime — a very elaborate workaround for “we can’t afford to build this five times.” You accept a sandbox, a JavaScript execution model, and a performance ceiling, and in exchange your app runs everywhere. Native apps take the other deal: full hardware access and speed, in exchange for a separate artifact per platform and a separate set of headaches per platform.</p><p>That tradeoff only exists because per-target builds are expensive for humans. In an AI-built world, they aren’t. Every app is generated for the exact CPU and platform it runs on, and “make it run on the new phone chip too” is a sentence, not a quarter. Web app versus native app stops being an architecture decision and becomes a trivia question.</p><h3>Forty years in</h3><p>Software is undergoing historic change — the kind you can actually feel. Forty years ago, learning BASIC on a Commodore 64, we could only dream of this. Mostly we dreamed of more than 64 KB of RAM. 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7d45843f086" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thestartuplifer/ai-and-the-slow-death-of-programming-languages-e7d45843f086">AI and the Slow Death of Programming Languages</a> was originally published in <a href="https://medium.com/thestartuplifer">The Startup Lifer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Mental Anti-Patterns Preventing You From Becoming a 10X Software Developer — Part 2]]></title>
            <link>https://medium.com/thestartuplifer/8-mental-anti-patterns-preventing-you-from-becoming-a-10x-software-developer-part-2-97b157b0ffac?source=rss----84651de5bc7a---4</link>
            <guid isPermaLink="false">https://medium.com/p/97b157b0ffac</guid>
            <category><![CDATA[code]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mental-toughness]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Ronen Magid]]></dc:creator>
            <pubDate>Mon, 27 Oct 2025 14:23:34 GMT</pubDate>
            <atom:updated>2025-10-27T14:23:29.077Z</atom:updated>
            <content:encoded><![CDATA[<h3>8 Mental Anti-Patterns Preventing You From Becoming a 10X Software Developer — Part 2</h3><p>(Part one is available <a href="https://medium.com/thestartuplifer/8-mental-anti-patterns-preventing-you-from-becoming-a-10x-software-developer-part-1-94f9478adf8e">here</a>)</p><p>Welcome back! We’re diving into part two of our journey through mental anti-patterns I’ve identified throughout my 30+ years journey as a software developer. These pesky patterns could be roadblocks in your career, but fear not, and not just because fear is the mind-killer. Just like with part one, we’ll direct a 35,000 watt beam of light at these patterns and talk about how to adjust your thinking and attitude to overcome them.</p><blockquote>“The first step in avoiding a <strong>trap</strong> — is knowing of its existence.” <br> — Thufir Hawat, Mentat and Master of Assassins for house Atreides <br>(Fictional Dune Universe — failed to adhere to his own advice)</blockquote><h3>Anti-Pattern #5 — You believe software development is a plateau</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qu67t1UlwHOtHYrN" /><figcaption>Photo by <a href="https://unsplash.com/@bradbarmore?utm_source=medium&amp;utm_medium=referral">Brad Barmore</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s put software aside for just brief moment for something seemingly unrelated. Let’s talk about special forces.</p><p>Special forces have always been shrouded in a blend of glory and mystery, fueled by both real-life events and silver screen fiction. Real-life feats include the elimination of Osama Bin Laden in 2011 and the miraculous and nearly casualty-free rescue of the 100+ Entebbe hostages in 1976 while Fictional tales, on the other hand, tend to be bombastic for obvious reasons, often depicting the body-builder types who never run out of ammo or the ongoing exploits of an ex-SAS operators turned secret agents who’s very particular about the way he takes his Martini.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l1fEU6rUcstPXyzl4k3i3g.png" /><figcaption>Special Forces (the “other kind” of operators)</figcaption></figure><p>Given the aforementioned, it’s quite understandable those influenced by pop culture envision special forces individuals as robust, hefty figures in the image of “Rambo” or “Schwarzenegger” — body builder types with bulging muscles who never have to change magazines and can single handedly take on a platoon of nameless henchmen and come out victorious no matter what. Just drop them deep inside enemy territory and they’ll not only get the job done, in time for drinks.</p><p>But does that cliché hold true in real life? Is being a physically strong giant the primary predictor of one’s ability to successfully navigate the uphill battle of becoming a member of SAS, Navy Seals, Army Rangers, Delta Force, Sayeret Maktal, or GSG-9?</p><p>The answer is no.</p><p>There is something far more important required of special forces operators — the right mental profile for the job. The irony is that even if you’re built like “Rambo” but lack those required mental traits, that puny guy standing next to you in pre-selection, should he possess the right mindset, is more likely than you to see graduation day, even if you can easily beat the crap out of him with one hand tied behind your back.</p><p>The rationale is simple: Any healthy individual can build muscle, strength and stamina over time if he’s mentally and physically fit to undergo grueling training without dropping dead, giving up or be mercifully shown the door for humanitarian reasons.</p><p>Other traits however such as Intelligence, calm under pressure, adaptability during uncertainty, can-do mindset when facing the “impossible”, resourcefulness when disadvantaged, and a “die before giving up” mental fortitude matter more than how much one can benchpress. Those things cannot be taught. You either have them, or you don’t.</p><p>That’s why it’s so challenging to screen candidates for special forces. What you’re really looking for isn’t immediately visible. You can’t see it when looking at biceps or deltoids. Compound that with the fact special forces is the ivy league of foot soldiering, and you’ve got yourself a funnel with thousands of dreamers on one end, and only a few potentials on the other. How do you sift through the chaff and find them?</p><p>When it comes to pre-screening for mental faculties, tests tend to split into two main areas. The first is whatever you can test in a classroom, and that includes things like general intelligence, creativity, resourcefulness, basic coordination and generalized technical skills. The second group is a bit more involved and will require blatantly forcing people out of their comfort zone and observing key performance and behavioral metrics.</p><p>As you could might have already guessed, forcing people out of their comfort zone in this context is a bit more extreme than forcing your best buddy onto stage on Karaoke night in front of 100 strangers to perform “My Heart Will Go On” before he had a chance to sufficiently prep with enough liquid courage.</p><p>So, how’s it done?</p><p>Imagine being a special forces candidate. You’ve begun a 3 day pre-selection process on a cozy afternoon. You were bussed into a makeshift barrack in the middle of nowhere, you’ve had your grounds tour, you know where the showers/bathrooms are, you’ve been to a classroom where you comfortably sat on your ass and listened to a rehearsed ‘you are lucky to find yourselves here’ pep talks. After a semi-decent dinner, your platoon of candidates, roughly 100 individuals was divided into tents and you’re dismissed for the night until things begin the next morning.</p><p>There’s no explicit lights-out time and despite what you may have seen in movies, there’s no “Full Metal Jacket” style Gunny character dressed in perfectly starched uniform, ordering you to bed with loud profanities. Instead, one of the instructor pays a visit to your tent and suggests “you should all get some rest because things will get interesting in the morning”. The tone of his voice is informal, almost friendly, bidding you and your tent buddies an almost polite “good night ladies” before leaving.</p><p>The night’s still young. You’re still a bit jazzed from just “being there”, and probably not THAT tired. Knowing you’ve got more than 8 hours till your next planned activity, you take your time, make small-talk with your new tent-mates and finally hit the sack around 11pm, maybe even later.</p><p>You won’t sleep for long.</p><p>It’s 2am. You franticly wake up to the sound of automatic gunfire outside your tent. You’ve never heard gunfire (let alone continuous fully automatic one) that close without ear protection, have you? It’s pretty deafening isn’t it? The noise level takes you by surprise, penetrates your guts and rattles you out of your cot with shivers of fear traversing down your spine. You throw yourself to the ground without even thinking about it. “what the fuck is going on? who’s shooting?” you think only to realize a second later you weren’t using your inside voice. You were screaming it out loud and you weren’t alone in doing so.</p><p>You’re in complete shock. Outside your tent, the friendly instructors who softly tucked everyone in just a few hours ago are in full battle gear, helmets with night vision goggles, and plate carriers thick with magazine pouches and other equipment. Their M4’s are emptying magazine after magazine into the air. They almost look like they’re having fun. The perfect alarm clock only the dead can ignore.</p><p>“UP!! GET UP!!” An instructors with a name tag reading “Joe” screams as he enters your tent. “ALL OF YOU, UP!! NOW!!”. You’re still on the ground trying to figure out what the hell is going and the first thought that goes through your mind is that he’s going to kill you, but that of course never materializes. If he wanted me dead I’d be dead already, you scoff at yourself after regaining your composure.</p><p>Orders are barked. “You have 20 minutes to get dressed, pack up the tent, and stand in formation outside”. He then slams two very large backpacks that look like what you’d find at a camping store to the ground next to you. “These are for the tent. NOW GET MOVING!”. Instructor “Joe” makes sure all eyeballs are on him as he conspicuously starts a stopwatch and makes his exit.</p><p>Everyone frantically snaps into action. Getting dressed is the easy part. The hard part is a bunch of strangers trying to team-pack a tent into bags under pressure in near darkness. You don’t know it yet, but those backpacks are purposely too small for the task. Soon it becomes vividly clear.</p><p>30 minutes later, some still struggling with their tents while others who realized the harsh truth carry are the remainder parts of their tent in their hands. Depending on the time of year, everyone at this point are either sweating like pigs in the sun, or teeth chattering in the cold night air. Few get to “enjoy” both.</p><p>One of the instructor looks down at his stopwatch with a disapproving frown. He doesn’t even mention how late everyone is. Instead he’s pointing at what seems to be a pyramid of gear nearby. “You have four minutes to put on these vests. We’re going for a stroll”, he orders. “Also, there are a few stretchers with a wounded comrades near the vests. I want four men on each stretcher at shoulder level and ready to go. We do not leave our wounded behind. GET MOVING!”.</p><p>The vests are loaded with two canteens of water and pouches of weights. Each vest weighs around 40 pounds. From the first moment you put them on you realize they weren’t engineered for comfort. The “wounded comrades” on the stretchers are life-size dummies that remind you of department store mannequins, except they’re not made of hollow plastic. They’re quite solid and weigh like a chubby six foot adult male would. They’re heavy as f***.</p><p>finding the first volunteers to man the stretchers is easy. Everyone wants to make a good impression, and as soon as each stretcher finds its four bearers the march begins. Leading the way is the chief instructor, with his staff moving back and forth along the column of men and stretchers as it moves down a dark hill into what seems to be a rural mountain trail. It’s still dark and the platoon is walking at a slow and steady pace, stretchers at shoulder level.</p><p>You don’t know where everyone is going. You don’t know how long the march will last or what destination awaits you at its end. As time goes by, the physical hardship starts creeping up on everyone. One by one, those who carry the stretchers begin screaming for a relief, causing a chain reaction of backpacks and tent parts changing hands as fresh shoulders now bear weight of the stretchers. This is done without stopping or resting. The march continues nonstop. You notice the time interval between stretcher reliefs getting short. People are getting tired sooner and can only carry the weight of the stretcher for shorter and shorter periods of time. Walking becomes increasingly hard. You pray they won’t ask you to pick up the pace or start running.</p><p>One thing is easy as a slice of pie — Quitting. All throughout the march instructors pick on those showing signs of fatigue, pain, and those who blurt an angry burst of words at a teammate. Once they mark you they circle you like voltures, taunting you, imploring you with a tone of voice that’s part caring and part demeaning — “come on man, why do this to yourself? Haven’t you had enough? this isn’t even close to being over. Listen — there’s a hot meal, warm shower and a cozy bed waiting for you back at camp. You’ve tried your best. Don’t be hard on yourself, there’s no shame in quitting. This isn’t for everybody. You have nothing to prove.”</p><p>When asked about it, most folks proclaim they’d never give up on something that’s means the world to them. Every man in the march has been eagerly waiting for a shot at the unit of their dreams. Some have held that dream since childhood. But reality cannot be deceived. When you’re feeling every muscle, tendon and ligament in your body is about to snap, when you’re so short of breath you feel you’re going to pass out, or puke or both — keeping that promise to yourself becomes the hardest, most challenging thing you’ve ever faced.</p><p>To some of those marching, the gap between “want” and “can” becomes an unbridgeable chasm. Within two hours or so, the first wave of quitters begin making themselves known with a shameful uttering of words. They are told to stay put. Just sit on the ground and wait. Most of them lie down in an attempt to control their panting and sooth their aching bodies. A vehicle trailing the march isn’t too far behind and will take care of them. You will not see them again.</p><p>What begins as a trickle of few quitters, turns with the passing hours into a more substantial stream. A typical platoon will lose up to 40% of its members during that march. The shrinking headcount now presents a new problem to those remaining. Fewer and fewer men are now available to chip in with the stretchers. That means longer stretcher-stints for everyone. Pain and fatigue levels spike up sharply. Discomfort gives way to real distress for many.</p><p>Morning has broken. If you’ve ever marched an unfamiliar terrain in a dark night, you know that unpleasant feeling of uncertainty when setting your foot down, not knowing whether you’ll step on solid, even ground or trip over something and crash down. Imagine doing it when you’re in intense pain and on the verge of collapse. Yet, most are relieved by the sight of the sun rising over the horizon.</p><p>Few hours later you get your first break. You reach a clearing where some folding tables where some chow have been laid out up for you. You get about 20 minutes to rest and eat. With joy you didn’t know you were capable of, you take the vest off, put down the backpacks, stretchers and tent parts. It feels as if an impossible burden had been lifted off. You feel you can move freely again. You stretch and try to enjoy it while you can. Some sit down or lay flat on the ground. Anyone who isn’t standing up will fall asleep.</p><p>Serenity doesn’t last long.</p><p>“REST’S OVER — LET’S GO!” the chief instructor barks. Vests, stretchers, backpacks and tent items are picked up as the men unwillingly force themselves up. The march resumes. Many quit after cruel and sudden transition from rest to pant. A few quit before the march even resumes again, unable to even imagine themselves going back into that painful crucible.</p><p>The sun is setting again. You’ve been marching for more than 18 hours with only a few short breaks. You’re beginning to contemplate the possibility you won’t make it. You don’t just think about quitting, you fantasize about it. You visualize it. A warm bed and a full night’s rest, something you took for granted just two nights ago all of the sudden sounds like a forbidden paradise. What were you thinking when you’ve consigned yourself to this hell? you keep thinking as you get closer to your breaking point. “When will this end?” you keep asking yourself as you keep going. “It’s GOT to end sometime, right?”. “We won’t march forever. Right? …right???”.</p><p>And then it ends.</p><p>You reach some flat clearing and told you have an hour to rest, eat and set up the tents for the night. You cannot believe you’ve lasted the day to its completion. The remaining men are once again assigned to tents. You put down your gear with a painful grunt and you cannot believe it. You exchange ecstatic high-fives with those around you. You eat and as you rest, the feeling of accomplishment sneaks up on you. You’ve earned it. You passed your first test. You did not quit despite the hardship, even though every fiber of your body demanded it. You obviously had what it takes to make it.</p><p>If earlier you had doubts about your ability to survive pre-selection — you now feel you actually have a real shot at it — a secretly enjoy a shred of careful optimism. It’s the best feeling in the world. The feeling of a dream getting closer to reality in a way that feels very real. A short while later, a large truck arrives from nowhere, full of cots.</p><p>You’re tired and every muscle in your body is screaming in agony. You’re afraid to take off your shoes and see what gory horrors await you under your socks, but you don’t care. Might as well be Gangrene. You feel so excited and accomplished none of that matters. You set up your cot for sleep and tuck yourself in.</p><p>“Sleep well tonight”, instructor “Joe” peers into your tent. “Tomorrow will be another interesting day full of adventure”.</p><p>“What’s he really planning?” you ask yourself, envisioning being woken again at 2am to gunfire and physical torture. You’re actually considering staying awake just to avoid being surprised again.</p><p>Then the all-clear comes.</p><p>“You’ve made it to the end of day one. You should all be proud of yourselves. Well done!” the chief instructor announces holding a bull-horn as he walks along the line of tents. “And no, in case you’re wondering, we’re NOT going to wake you up at 2am to start marching again. You ladies have earned a good night sleep. That’s a guarantee. Now get some sleep!”.</p><p>Those words are like music to your ears. It’s irrelevant whether you believe the chief instructor or not. Either way, you simply lack the energy to do anything about it. Your body is taking over and it knows exactly what it needs. As soon as you put your head down, you’re asleep in seconds.</p><p>You’ll be asleep for about 30 minutes.</p><p>A familiar ra-ta-ta-ta-ta sounds real close. The gut shattering noise of automatic gunfire interrupts your uneasy sleep. You frantically wake up.</p><p>“WTF, oh shit, not again, no way”.</p><p>Way.</p><p>“UP!! EVERYONE GET UP!!” instructor “Joe” barks as he enters your tent. “You have 20 minutes to pack up your tent, put your vests back on and gather by the stretchers. We have another exciting excursion ahead of us”.</p><p>Not to undermine the importance of power naps, but rest assured (no pun intended), after the day you’ve had, those 30 minutes of horizontal unconsciousness you’ve accumulated mean less than a thin slice of nothing. You’re still fatigued, you can barely keep your eyes open, you’re still in pain, and worst of all, it’s suddenly dawns on you — you’ve got another day of marching and hauling about to begin. Right now.</p><p>Your body, like everyone else’s whimpers “No ‘effing way” when you realize what’s coming next. You may decide to give it a shot but for some however this will be too much. More than they are capable or willing to endure. This is the major red flag all instructors are looking for — That exact moment when the mind breaks and gives up on supporting the already beaten body. At that moment you’ve proven you’re not special forces material, and for you — it’s over.</p><p>Many who felt the ecstasy of making it through the first day will now break down and quit in hordes. It’s an interesting point if you think about it. They don’t quit because they collapsed and passed out. They did not quit because they reached the limits of their tolerance. They quit because they could not stomach the <strong>idea</strong> of repeating the most grueling day of their lives without proper rest. What broke them wasn’t the enemy, or pain or death. It was a thought broke them. They went from the “feel-good” joy of accomplishment to giving up because of a few words uttered to them.</p><p>There are no do-overs here. The quitters quickly disappear from sight. On the other hand, those who accepted the bad news with resolve, those who woke up, packed up, and prepared themselves for another day of grueling march without complaint or surrender — they’re the ones who truly made it through the first day with success.</p><p>The remaining men will discover their new march will last for just a few miles, at the end of which they will be ferried back to the base. This time they will really enjoy a good night sleep before having to face next challenge selection has in store for them. Day one is over.</p><p>The next challenge and that which comes next are designed to up the difficulty of the game. The lessons learned at the end of day one cannot be used to prepare the remaining men for day two. Nor can the lessons from day two and so on. You’re always in the dark.</p><p>Candidates will continue finding themselves fighting doubt, uncertainty and a slew of unexpected challenges, both physical and mental until the very last moment is surprisingly announced. When the dust settles, only a select few will have successfully survived pre-selection.</p><p>If you’ve made it thus far, you must be asking yourself how’s all this G.I. Joe stuff related to software engineering.</p><p>There is a fine common thread here but since its manifestation stretches through lengthy periods of time, it sometimes escapes people. When You start with software, you always work towards mastering something that can give you both personal satisfaction and support your career. The problem arises when the very thing you’ve worked so hard to master turns to dust before your eyes, leaving you a master without an art, doomed to begin again.</p><p>You see, the more time you spend in software, the more likely you’ll experience those cycles of birth and death of the very thing you’re worked so hard to master. While it’s true some skills remain useful forever once gained, like algorithmic thinking, ability to analyze problems and the ability to deep-dive into complex systems, some skills come with an unavoidable expiration date. Computer languages are born, live and eventually die, and so do frameworks, platforms, best-practice know-how and even the notion of what’s software and how it’s delivered.</p><p>There will be times in your life where you will have, through grit and hardship, tied your livelihood to a skill cultivated over time, and yet, this capability may one day no longer be in demand. That’s a fact. It will happen to anyone in the field long enough. There’s no escape from it.</p><p>My career spans for over 30 years now. When I started out, I spent months making myself a Turbo Pascal wizard in the 1980’s. I loved that language and did wonderful things with it but today it’s a museum piece. Then I spent years making myself an expert in Windows application development, using Win32 API, MFC, C++, ActiveX, COM/DCOM and a variety of other technologies, some of which are quite elaborate and require plenty of time and serious effort to master.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*3MYwyiEQVU84wfB1hDc6pA.jpeg" /><figcaption>The olden golden days of programming — Borland’s Turbo Pascal</figcaption></figure><p>But Is anyone using these technologies today? Can I still land a job doing COM/DCOM in 2025? Perhaps in a company I wouldn’t want to work for. A company still stuck maintaining legacy software that still functions for some reason and is more expensive to kill and to replace. A place where software engineers tethered to the past go to die. Thankfully, only a handful of those places exist.</p><p>When I started writing software professionally in the mid 1980’s to the mid 90’s computer software almost always meant desktop software for PC’s — initially under DOS, in text mode (Millennials: think “terminal is my computer”) and eventually GUI under the Windows operating system. There were of course other niches of software development like Mac, Linux, Gaming consoles and embedded but the overwhelming majority of developers writing enterprise business applications were working in PC shops. Our software was shipped to customers on floppy disks, CD-ROM later on, in a shiny box with printed manuals and a license. The idea of buying something “online” and then “getting it” online too was still sci-fi. Yes, I know. I’m a dinosaur.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*wZORv7h4VjY75AkxCkp3nw.jpeg" /><figcaption>Downloading an IDE back in the day</figcaption></figure><p>But hey — even with all my love of sci-fi, I did not see the internet coming in the early 1990’s. Don’t get me wrong, I heard of it. I knew people who knew people who had accounts on university mainframes, but for most of us, “going online” meant dialing a modem to your favorite BBS or some independent service like CompuServe or AOL. The technology that would evolve to be the world wide web was merely a glint in the eyes of the academia. Few really understood how it would transform humanity in just a few years. I didn’t care about the future. I was cozy, cruising to the noise of Visual Studio, developing windows business apps in C++.</p><p>Fast forward a few years, and it’s 1998.</p><p>Every software company on the planet was looking for web developers. The first successful “napkin” startups made their first 9-figure exits and their success sent shockwaves across the industry. Everybody wanted to be the next ICQ, Netscape, or Hotmail. Those who knew how to build web applications could not only enjoy being bid on by eager employers but also raise capital with ease those who only dealt in desktop software could only dream of.</p><p>But I was still running full throttle on Windows development. I developed a strange dislike of web technology and refused to learn it. I hated the idea of HTML and Javascript and to this day I am unsure whether that was because I found faults in the technology or I simply didn’t want to give up the comfort of already being the master of my trade. Web technology was a far cry from the beauty and richness we have today, but still, I knew it represented the future and yet I remained paralyzed.</p><p>I paid a dear price for that approach. Much like those guys at pre-selection who just torture-marched for a whole day, only to be told they’re going to have to repeat it after a 20 minute nap, I could not bring myself to do what was needed. As a result I was very late in entering the world of web development and it cost me extended periods of unemployment and a few years of desperately searching for an antiquated job in a shrinking, dying marketplace.</p><p>But the internet and the web browser aren’t the only ground-shaking revolutions I’ve experienced during my career. We’re at the beginning of a much bigger one — AI.</p><p>Those who didn’t get on the GPT, LLM, Agentic, and Generative bandwagon in time are having a difficult time finding a job armed with just “full stack web development skills”. Fresh graduates with a CS degree are struggling to compete agains the AI automation that took over some of their jobs. To be in demand today you need to be able to harness AI in complex applications.</p><p>Do you know how LLMs work? Do you know how to set up and use predictive models? Can you train models? Can you create MCP adhering agents? If the answer is mostly no, You’re in a pickle. Not just because you’re late but because those things aren’t easy to master and won’t come fast to most. That march up the AI hill from the foothills of web development will not be an easy stroll, and not all who want to will make the cut.</p><p>The point is simple. I’ve been a bit overly verbose to say the least, but it all comes down to this — When you get comfortable, you sometimes stop evolving and when that happens, it’s really hard to get back into grit mode and climb uphill again. It’s not that dissimilar to those who thought they’ve earned their first day wings marching for 18 hours only to discover they have yet another 18 hours ahead of them — without rest. It’s not an easy thing to find out your hard-earned achievement suddenly means nothing and you have to start from scratch.</p><p>Such harsh realization may be so demotivating that you may lose your drive to put in the effort required to master something new, and that my friends, will fu**ing kill you just like the “I am NOT doing THAT again” uttered by those poor exhausted souls who never made it past the first day of pre-selection.</p><p>So what DO you do?</p><p>You never stop learning, out of habit, not necessity. You never stop investing in mastering something else even if it means stepping outside of your comfort zone. Do this even if you’re paid big bucks doing something else. You never know when your primary mastery may become obsolete. It can creep up on you and it can catch you by surprise when you’re not ready for it. Trust me on that one. My own surprise wasn’t that the web took over. I knew this was coming for years. My surprise was just how suddenly the job marketplace had dried up for windows devs like me. I was living a fantasy that could not hold water and when everything went sideways, It was too quick, too soon for me, and it nearly cost me my career.</p><p>Stay sharp and interested, and unless you’re retiring in a month — never reject new technologies taking the world by storm. That will help avoid that awful swooshing sound the job marketplace makes as it zooms past you.</p><p>Always remember two things:</p><ol><li>In software the wolf is always at the door, as the famous Eagles song goes. But you <strong>can</strong> be prepared to face it, just like those three little pigs.</li><li>Software engineering was never a plateau. It’s always been a chaotic, endless mountain range stretching from where you stand to pretty much the end of “y’all’s careers”.</li></ol><p>It’s simply the nature of the beast.</p><h3>Anti-Pattern #6 — You think like a linear carbon unit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rd8fqneDEQiC7cNY" /><figcaption>Photo by <a href="https://unsplash.com/@austris_a?utm_source=medium&amp;utm_medium=referral">Austris Augusts</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Most people think linearly — one thought at a time, one task at a time. No one ever takes a shower while making breakfast in the car as he or she is driving the kids to school. We take a shower, then make breakfast and then drive the kids to school. It’s how humans do things. Linearly. And no, switching your attention from task A to task B before A is done isn’t really multi-tasking. It’s merely context switching. Task B and task A will still take the roughly the same time whether you do them one after the other or in parallel by periodically jumping from task to task. Some would claim jumping from task to task before completion actually makes the tasks take longer as you waste valuable time on context switching. I tend to agree.</p><p>Computers though have been natural multitaskers even in the olden days. First it was a very primitive method of context switching. Simulating parallelism by quickly jumping from task A to B to A and so on, giving us the illusion of true multi-tasking. If you were into PC’s in the 1980’s you surely remember the magic of DoubleDOS, software that allowed us to run two programs at the same time on a PC that had a single 8-bit 8086 processor and 640KB of RAM. To us teenage computer nerds that was reality defying.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*sOgcHhckpAMH-BVTX7S0Bw.png" /><figcaption>DoubleDOS</figcaption></figure><p>Computers evolved quite a bit since the days of DoubleDOS. With faster CPUs and minimization of circuitry came the ability for a single CPU to run multiple threads of execution naturally, and today of course, we have multi-core CPUs where multi-tasking is no longer logical. It’s real.</p><p>But one thing hasn’t evolved at the same pace — the human brain. When most of us have to perform task A, B and C. We take on each task separately from start to finish before moving to the next.</p><p>The problem begins when we take that kind of thinking and apply it to software. When mentoring younger engineers I sometimes encounter the effects of that thinking on how code is written and its negative effect on overall efficiency.</p><p>It’s how our brains evolved to process information: finish one thing before starting the next. But in the world of software engineering, linear thinking can sometimes hold you back.</p><p>Instead, thinking in <strong>multi-threads</strong>, like how a computer runs multiple threads in parallel, can be a game-changer. It’s not enough of course, you have to know when to use it because sometimes over-doing it can have the opposite effect, but if you approach any task with the mindset of “I can do things in parallel if need be” — your code will be better.</p><h4>What Does “Multi-Threaded Thinking” Mean?</h4><p>Imagine your brain is a processor. Linear thinking is like using a single core: efficient, focused, but limited. Multi-threaded thinking is like running multiple cores in parallel — handling different parts of a problem at the same time, keeping systems in mind even as you work on details.</p><p>This doesn’t mean <em>doing everything at once</em> (that’s just multitasking, and it’s usually a bad idea). Multi-threaded thinking means holding <strong>multiple contexts</strong>, <strong>dependencies</strong>, and <strong>systems-level interactions</strong> in your head at once — just like a program might spin off different threads to handle I/O, UI, and backend logic simultaneously.</p><h4>Why Is This Useful?</h4><p><strong>Software Isn’t Linear</strong></p><p>Code doesn’t run top to bottom in a neat line. It branches, listens for events, responds to user inputs, and handles concurrent data. Thinking linearly makes it hard to debug or design such systems. But if you think like the system runs — in parallel — you can better anticipate bugs, race conditions, or performance bottlenecks.</p><p><strong>You’ll Design Better Architectures</strong></p><p>Systems-level thinking — like imagining how a frontend thread talks to a backend thread, or how a background task updates a cache while serving users — leads to cleaner, more scalable designs.</p><p><strong>It Improves Debugging Skills</strong></p><p>Bugs in multi-threaded or asynchronous code can be elusive. When you think in threads, you’re better able to trace where race conditions or deadlocks might occur, and how timing might affect logic.</p><p><strong>Modern Software Runs Concurrently</strong></p><p>Web servers, mobile apps, and distributed systems all use concurrency under the hood. If you’re building or debugging them with a purely linear mindset, you’re likely to miss important behavior.</p><p><strong>It Helps You Work Smarter in Teams</strong></p><p>Just like a system has many threads working independently but contributing to one goal, your team does too. Multi-threaded thinking helps you understand your work’s impact on other parts of the system and anticipate integration issues early.</p><h4>How to Start Thinking in Threads</h4><p><strong>Mentally model systems, not steps.</strong> Don’t just think “first this, then that.” Instead, ask “what’s happening in parallel? What could trigger while this is running?”</p><p><strong>Use visualizations.</strong> Diagrams like flowcharts, sequence diagrams, and thread timelines can help train your brain to visualize concurrency.</p><p><strong>Study asynchronous patterns.</strong> Learn how event loops, promises, go routines, and thread pools work. Apply those models when reasoning about your own code.</p><p><strong>Practice context switching.</strong> Learn to return to tasks without losing your place. Good developers can pause one “thread” of thinking and resume it later — just like an OS swaps processes.</p><p><strong>Think of the entities at play and strategize. </strong>Never forget to consider all the players in your flow of work before you code it. Your function may run locally, but it may depend on external resource over which you have no control.</p><ul><li>Abstract the task you’re trying to implement in terms of the “brain resources” (CPUs, threads), dependency (discrete, tree-like, etc) and environment (cli util, user facing app, what else is in the background).</li><li>Realize what yo can control (your own CPUs) vs. what you have no control over, such as external API calls that can take n time units to come back with a response, or I/O limitations of your own platform.</li><li>Always understand what’s going on outside of your function. Many things already run in parallel in your app. Being slow at processing can be just as bad as dedicating too much resources to a task and slowing everything else down.</li><li>Always know when to queue jobs, limit worker threads and when to go full power with what you have. CLI utilities will probably have you do things differently than being a background function on a user-facing application.</li><li>Don’t just “queue and execute”. Not all tasks are created equal. Just like with an efficient gantt chart in the realm of project mamagement, prioritize those items upon which other items have a dependency. Build a mental dependency tree when you architect, and a real-time one when your code executes. A Gantt chart is a great simile to concurrency. Human resources are “threads” or “CPUs” and the project work items is the task at hand. The work items other work items depend on are front-loaded and from there, different “humans” can simultaneously take different tasks and begin working toward completion together. If the project calls for five major independent items to be implemented first, 5 “teams”, “people” or “cpus” can handle those concurrently before moving on.</li></ul><h4>Always Remember</h4><p>Thinking in threads isn’t just a programming skill — it’s a mindset. It helps you see software not as a script, but as a system. And once you make that shift, you’ll write more robust code, spot issues faster, and grow into a more systems-oriented, impactful engineer.</p><h3>Anti-Pattern #7 — You fear or resent the bots and their hold on the future</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q63ykkAF3UHPVW0yyGxOnw.jpeg" /><figcaption>Hal-7 — When buggy AI makes life or death decisions</figcaption></figure><p>Let’s face it: artificial intelligence isn’t just some passing tech fad — it’s already woven into the fabric of modern software development. From code generation tools like GitHub Copilot to AI-powered bug detection, the way we write, test, and deploy software is changing fast.</p><p>And yet, among software engineers, there’s a growing undercurrent of resentment. The fear that AI will replace developers. The frustration of seeing junior engineers rely too heavily on code suggestions. The worry that years of experience might be flattened by a machine that can write a sorting algorithm in half a second.</p><p>But here’s the truth: AI is not going away. And more importantly — it’s not your enemy. In fact, the sooner software engineers stop resisting AI and start understanding, adapting, and integrating it into their workflows, the more empowered and valuable they’ll become.</p><p>Here’s why.</p><h4>AI Is a Tool, Not a Replacement</h4><p>Let’s bust the biggest myth first: AI is not here to take your job. It’s here to <strong>change the nature of your job</strong>. Just as IDEs replaced manual debugging and compilers replaced hand-written machine code, AI tools are designed to augment developers — not erase them.</p><p>An AI can help write boilerplate, suggest code snippets, or catch syntax issues. But it doesn’t understand context, product vision, customer needs, or architectural trade-offs. You do. AI doesn’t have intuition, empathy, or judgment. It doesn’t mentor junior engineers or advocate for end users. You do.</p><p>If you see AI as a collaborator instead of a competitor, you shift from fearing displacement to finding ways to <strong>work smarter, not harder</strong>.</p><h4>The AI Revolution Needs Engineers More Than Ever</h4><p>AI systems don’t build themselves. Every model, framework, API, and deployment pipeline behind AI needs skilled software engineers to design, maintain, and improve them. As AI becomes embedded in more products — from healthcare to finance to education — the demand for engineers who understand both traditional software and modern AI infrastructure will only grow.</p><p>In fact, developers who can bridge this gap will be <strong>the most in-demand technologists of the next decade</strong>.</p><p>You don’t have to be a machine learning expert. But understanding how to integrate AI responsibly, how to monitor model performance, and how to interpret its output will make you exponentially more valuable.</p><h4>AI Unlocks Creativity by Removing Drudgery</h4><p>Let’s be honest — writing yet another form validation function or API interface isn’t exactly soul-stirring work. AI excels at automating repetitive, low-level tasks. That’s a good thing. It frees you to focus on what really matters: designing better systems, improving user experiences, and solving real-world problems.</p><p>By automating the mundane, AI gives developers the space to be more <strong>creative, curious, and strategic</strong>.</p><p>Instead of dreading repetitive tickets, imagine using that time to dive deeper into system performance, clean up tech debt, mentor teammates, or finally explore that feature idea you’ve been sitting on.</p><h4>The Best Engineers Are the Most Adaptive</h4><p>Tech is, by nature, a fast-moving field. We’ve evolved from monolithic applications to microservices, from servers to serverless, from imperative to functional paradigms. The best engineers haven’t been those who clung to the past — they’ve been the ones who learned, adapted, and thrived in the face of change.</p><p>AI is just another leap in that evolutionary chain. Resisting it won’t stop the tide. But adapting to it means you stay relevant, effective, and ahead of the curve.</p><p>Learning how to work with AI today is like learning Git ten years ago — annoying at first, but eventually indispensable.</p><h4>You Get to Shape How AI Is Used</h4><p>Perhaps the most compelling reason to stop resenting AI is this: <strong>you have the power to influence how it’s built and used</strong>.</p><p>There are real concerns about bias, misuse, intellectual property, and job displacement with AI. But who better to guide responsible development than engineers who understand its inner workings?</p><p>By being part of the AI conversation — through code, ethics, design, and product decisions — you can help ensure that AI is <strong>used ethically, transparently, and inclusively</strong>.</p><p>Turning your back on AI hands that responsibility to someone else.</p><h4>AI Can Be a Career Multiplier</h4><p>The developers who figure out how to leverage AI effectively will ship faster, innovate more boldly, and become force multipliers in their teams.</p><p>That doesn’t mean letting AI write your code blindly — it means using it to get unstuck, explore unfamiliar libraries, or prototype quickly. It means using AI as a thinking partner to brainstorm edge cases or improve performance.</p><p>In short, AI can make you <strong>better at what you already do</strong> — if you let it.</p><h4>Forget SciFi: It’s Not Man vs Machine. It’s Man With Machine.</h4><p>Software engineering isn’t going away. But it is evolving. The rise of AI doesn’t diminish your value — it <strong>redefines</strong> it. Your job is no longer just about writing code; it’s about solving problems, understanding users, and building resilient, intelligent systems that improve lives.</p><p>You don’t have to love AI. But you do have to learn how to live with it. And if you approach it with curiosity instead of fear, you might just find it’s one of the most powerful tools you’ve ever had.</p><h3>Anti-Pattern #8 — You’re stuck in amateur level forensics</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KfNNgF-ocZN0dblQ" /><figcaption>Photo by <a href="https://unsplash.com/@johnmcclane?utm_source=medium&amp;utm_medium=referral">Andres Siimon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When developers think about improving their skills, they often jump straight to learning a new language, framework, or algorithm. But often, the most impactful skill upgrade is mastering the tools that help you understand what your code is <em>actually doing</em> — namely, the <strong>debugger</strong> and <strong>profiler</strong>.</p><p>Here’s why these tools are absolutely critical for any serious software engineer.</p><h4>🐞 The Debugger: See What the Code Actually Does</h4><p>Writing code is only half the job. The other half is <strong>making it work when it doesn’t</strong> — and for that, a debugger is your best ally.</p><p>Instead of adding a hundred print() statements or logging everything under the sun, a debugger lets you:</p><ul><li><strong>Step through code line by line</strong></li><li><strong>Inspect variables in real-time</strong></li><li><strong>Watch call stacks and state transitions</strong></li><li><strong>Set breakpoints and conditional triggers</strong></li></ul><p>This visibility is invaluable when hunting down bugs, especially in complex systems where errors arise from subtle state changes or asynchronous interactions.</p><blockquote><strong><em>Pro tip:</em></strong><em> Learn how to set </em>watchpoints<em> (break when a variable changes), not just breakpoints. It’ll save you hours on tough bugs.</em></blockquote><h4>⚙️ The Profiler: Know Where Your Code Is</h4><h3>Slow</h3><p>Premature optimization is bad. But ignoring performance altogether is worse. A profiler shows you <strong>where your program is spending its time</strong>, helping you optimize with precision rather than guesswork.</p><p>With a profiler, you can:</p><p>Identify <strong>hot paths</strong> that eat up CPU or memory</p><p>Detect <strong>I/O bottlenecks</strong> or inefficient loops</p><p>Measure function execution times</p><p>Analyze <strong>heap allocations</strong> and memory leaks</p><p>This is especially important when working with real-time systems, backend services, mobile apps, or any product with performance constraints.</p><blockquote><strong><em>Pro tip:</em></strong><em> Always profile </em>before<em> and </em>after<em> optimizations. Don’t assume — measure.</em></blockquote><h4>🚀 Debugger + Profiler = Superpowers</h4><p>Used together, the debugger and profiler give you a complete picture of your software’s <strong>correctness</strong> and <strong>efficiency</strong>. You’ll ship faster, fix bugs more confidently, and build systems that scale.</p><p>Mastering them isn’t optional — it’s what separates good engineers from great ones, you know, like the one you want to become.</p><p>So, if you’ve never seen how breakpoints stop everything and get you into a super-slo-mo, line by line execution as you literally see line after line being executed, or if you’ve never understood how to get a by-function runtime breakdown of a nested execution chain…. It’s time to start :-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97b157b0ffac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thestartuplifer/8-mental-anti-patterns-preventing-you-from-becoming-a-10x-software-developer-part-2-97b157b0ffac">8 Mental Anti-Patterns Preventing You From Becoming a 10X Software Developer — Part 2</a> was originally published in <a href="https://medium.com/thestartuplifer">The Startup Lifer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Social Networks Will Never Be a Place of Peace.]]></title>
            <link>https://medium.com/thestartuplifer/social-networks-will-never-be-a-place-of-peace-70c4a5e2c35c?source=rss----84651de5bc7a---4</link>
            <guid isPermaLink="false">https://medium.com/p/70c4a5e2c35c</guid>
            <category><![CDATA[digital-life]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[internet]]></category>
            <dc:creator><![CDATA[Ronen Magid]]></dc:creator>
            <pubDate>Sat, 25 Oct 2025 05:10:17 GMT</pubDate>
            <atom:updated>2025-10-25T06:56:47.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*odc3HcCPh8U891Te7OCAmg.jpeg" /><figcaption><strong>Les Réseaux Sociaux</strong> — 1743 painting by French impressionist Jean Claude Baptiste De-Méme (JK)</figcaption></figure><p>It would be adorable, if it weren’t so spectacularly naive, to believe that social networks — those algorithmically engineered maelstroms of dopamine, clout-chasing, and lightly camouflaged digital tribalism — could ever transform into serene gardens of civil discourse. The belief is as touching as it is laughable. One imagines the same sort of earnest, wide-eyed idealist who believes you can plant a tree on Twitter and not be accused of horticultural colonialism by lunch.</p><p>Let’s dispense with the fairy tales. Social networks are not broken utopias. They are functioning dystopias. They are not town squares; they are gladiator pits with a “like” button. The rage is the feature, not the bug.</p><h3>The Illusion of the Digital Commons</h3><p>The fantasy that social networks might become places of peace stems from a fundamental misunderstanding of what these platforms are <em>for</em>. The average user may believe they are there to connect, to share, to learn, perhaps even to grow. But the platforms themselves? They exist to extract. Engagement is the currency, and outrage is the mint. The longer you look, the more you click, the more valuable you become. Your soul may remain intact, but your attention is sold in neatly wrapped time-slots to advertisers hocking vitamins and paranoia.</p><p>Yes, social networks masquerade as public squares, but in reality, they are surveillance malls. You think you’re engaging in dialogue with your fellow citizens, but really, you’re just part of an elaborate behavioral casino. The house always wins, and it doesn’t care if you left emotionally exhausted.</p><h3>Peace vs. Profit: A Comically Unequal Match</h3><p>If we were to imagine a social network designed for peace, it would look like a library — contemplative, slow, maybe even a little boring. No algorithm nudging you to yell. No trending topic optimized to incite tribal aggression. No panic-inducing headline smuggled in by the content equivalent of a meth dealer in a lab coat.</p><p>And it would fail. Spectacularly. Peace is not profitable. Calm does not convert. Platforms are not incentivized to bring users together, they are incentivized to keep them scrolling, clicking, reacting. The soft glow of mutual understanding is no match for the flashing neon of manufactured outrage.</p><p>Zuckerberg and his ilk do not wake up wondering how to make humanity more harmonious. They wake up asking: How do we make them look longer? How do we keep them hooked? A digital peace garden does not keep users engaged. A digital coliseum does.</p><h3>Identity as Ammunition</h3><p>Social networks have allowed us to curate and weaponize identity with a ferocity that would make Machiavelli blush. It is no longer enough to <em>have</em> an opinion; you must now <em>perform</em> it, <em>defend</em> it, and <em>deploy</em> it with tactical precision. Your identity becomes your brand, and your brand is always at war.</p><p>Algorithms have trained us well: We learn quickly that anger and performative sanctimony get rewarded. Nuance dies in the algorithmic trenches. A good-faith disagreement receives zero likes; a viral takedown gets you verified.</p><p>And this, perhaps, is the most delicious irony: Social networks promised to bring us together, but instead they taught us to speak in weapons-grade certainties. They rewarded us not for listening, but for performing our unwillingness to listen. We do not communicate on these platforms. We signal. We gesture. We provoke. Peace doesn’t even make the top ten list of goals.</p><h3>The Amateur Hour of Global Discourse</h3><p>Let’s address the breathtaking arrogance of it all. We, a species barely capable of agreeing on the temperature of a room, believed we could toss billions of humans onto a handful of platforms and expect civil conversation to arise organically? You might as well put a goat, a python, a mime, and an arsonist in a bounce house and expect a book club to form.</p><p>Worse, we gave everyone a microphone, then built incentive structures that rewarded the loudest, least-informed voices. Expertise is boring. Outrage is sticky. Truth is long-winded; memes are snackable. And so the complex gets drowned out by the glib, the careful by the confident, the insightful by the incendiary.</p><p>This isn’t elitism. It’s realism. There is a reason we don’t let twelve-year-olds write legislation or let drunk uncles perform open-heart surgery. But when it comes to shaping public discourse, we’ve handed the reins to anyone with a Wi-Fi connection and a misguided sense of purpose.</p><h3>Moderation Is Not a Messiah</h3><p>Ah yes, moderation. The perennial favorite of Silicon Valley posturing. Every CEO promises better tools, better filters, better bots. As though peace can be coded. As though the core issue is a technical shortcoming rather than a philosophical failure.</p><p>Moderation, however well-intended, is like handing out pool noodles in a shark tank. It may reduce the carnage, but it will not change the ecosystem. Because the ecosystem <em>requires</em> conflict. It feeds on it. The most you can do is make the carnage more polite. Maybe it comes with a content warning. Maybe it gets auto-muted. But make no mistake: The platforms will never neuter the outrage machine, because they are the ones feeding it.</p><h3>The Role of the Spectator: Complicit and Addicted</h3><p>Perhaps the most uncomfortable truth is this: We like it. We say we don’t, we posture as exhausted digital citizens, weary of the drama and noise. But we stay. We click. We comment. We dunk. We lurk.</p><p>Peace is boring, and humans, tragically, do not seek boredom. We are not noble sufferers of social media’s dysfunction. We are its co-conspirators. We are not trapped in a burning building. We keep lighting matches.</p><p>You want peace online? Don’t log in. You want nuance? Read a book. You want civil dialogue? Try speaking face-to-face with someone who disagrees with you without subtweeting their haircut.</p><p>But don’t expect Facebook to fix you. Don’t expect X (formerly known as Twitter, currently known as a cautionary tale) to become a digital ashram. These places were never temples. They were never sanctuaries. They were casinos for the ego, and you keep bringing your wallet.</p><h3>History Rhymes, But Never Hugs</h3><p>Some techno-optimists will insist this is a phase. A bump in the road. “Remember the early days of radio? Of TV? Of the printing press?” they say, with a smirk and a TED Talk clicker. Yes, history is replete with moral panics and media upheavals. But none of them happened at this scale, at this speed, or with this much dependency. You didn’t carry the printing press in your pocket. Your gramophone didn’t ping you with notifications about global catastrophe while you ate a sandwich.</p><p>Social media is not just a medium. It is an operating system for identity, belonging, and outrage. You do not “use” these platforms. They use you, shape you, rewire you to need what they provide: validation at scale, instant friction, constant stimuli.</p><p>Peace is incompatible with that structure. It cannot live in a system that has no off switch, no cool-down, no boundary between signal and noise. You cannot plant a bonsai in a hurricane and expect it to bloom.</p><h3>The Myth of Platform Redemption</h3><p>Every few months, a headline will suggest a shift: “X cracks down on bots,” “Facebook to de-rank clickbait,” “Instagram to promote mental wellness.” And the hopeful rush to believe again. Maybe this time it’s real. Maybe this time the monster becomes a monk.</p><p>It won’t. These half-measures are marketing strategies wrapped in apology theater. The platforms are in an abusive relationship with your attention, and these token efforts are the bouquet of flowers after the slap. They will never stop doing what works. They can’t afford to.</p><p>Because peace doesn’t trend. Peace doesn’t scale. Peace doesn’t sell.</p><h3>What Peace Would Require</h3><p>To create true peace on social networks, you would need to start over. New incentives. New infrastructure. New expectations. You would need to make virality impossible, anonymity rare, and ad revenue irrelevant. You would need to reward humility over certainty, curiosity over conviction.</p><p>In other words, you would need to build the opposite of what exists now.</p><p>You would also need a global population willing to slow down, step back, listen deeply, and give up the petty, delicious thrill of dunking on someone who spelled “their” wrong. That is, unfortunately, not where we are.</p><p>What we have are the platforms we deserve. Built from the blueprints of our worst habits, scaled by our laziest impulses, optimized for our least noble selves.</p><h3>Conclusion: Peace Is Not the Point</h3><p>Social networks will not become places of peace because peace was never the point. The platforms are working exactly as designed. And we, with our compulsive scrolling, our clout-chasing, our tribal posturing, are not victims of this system.</p><p>We are participants. We are investors. We are addicts.</p><p>The hope for digital peace is touching. Beautiful, even. But it is a bedtime story we tell ourselves in the glow of the same screens we claim to despise.</p><p>So yes, go ahead and dream of better. But do so knowing the dream will not be retweeted. It will not go viral. And if you’re lucky, it won’t be ratioed into oblivion by someone with a frog avatar and zero followers.</p><p>Because peace is not the algorithm. Conflict is.</p><p>And in this world, the feed is always hungry.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70c4a5e2c35c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thestartuplifer/social-networks-will-never-be-a-place-of-peace-70c4a5e2c35c">Social Networks Will Never Be a Place of Peace.</a> was originally published in <a href="https://medium.com/thestartuplifer">The Startup Lifer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Things Stay a While. Really Good Things Become Invisible]]></title>
            <link>https://medium.com/thestartuplifer/good-things-stay-a-while-really-good-things-become-invisible-eb6a97c65180?source=rss----84651de5bc7a---4</link>
            <guid isPermaLink="false">https://medium.com/p/eb6a97c65180</guid>
            <category><![CDATA[computing]]></category>
            <category><![CDATA[observation]]></category>
            <category><![CDATA[predictions]]></category>
            <category><![CDATA[future-technology]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ronen Magid]]></dc:creator>
            <pubDate>Thu, 11 Apr 2024 18:31:34 GMT</pubDate>
            <atom:updated>2024-04-18T00:41:01.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y9N_8ABYFjwNgfvz" /><figcaption>Photo by <a href="https://unsplash.com/@viazavier?utm_source=medium&amp;utm_medium=referral">Laura Ockel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you grew up in the 70s, like me, your first computer probably looked like a keyboard, connected to a standard home television set, and supported some type of gaming input through a joystick or rotary paddle. That was more than enough during those magical times. Yet, even in that era of technological simplicity, before the internet, social networks, and big-tech, the race for the next big thing was always in full swing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2N84Vav2IFAVeYAbZUpiAg.jpeg" /><figcaption>Lost my computing virginity to this beauty in the early 80&#39;s. Source: <a href="https://oldcrap.org/">oldcrap</a>.org</figcaption></figure><p>With the advent of graphical user interfaces (”GUI”), computers increasingly became “fully graphical”, moving away from the “text mode” inherited from their mainframe terminal ancestors. This change made pointing devices a necessity.</p><p>The ability to naturally use a mouse with your computer became such a novelty, that companies could not resist the marketing boost associated with the word “Mouse”. Software products were actually branded to include the word “Mouse”. After all, who wants to merely “Write”, when you can “MouseWrite”, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bGZlPzyr4DEd343nkgnAKg.jpeg" /><figcaption>Source: Google Images (I hope the makers of MouseWrite don’t sue)</figcaption></figure><p>Fast forward to 2024. Does “Mouse-Mania” remind you of something?</p><h4>“I’m sorry Dave…”</h4><p>Unless you’ve been living under a rock on the moon this the past year, surely you can acknowledge these two realities (okay, maybe one):</p><ol><li>AI has rapidly entered the mainstream with such fanfare that 4 out of 5 startups launched in the past year have incorporated the acronym “AI” into their company name, domain, value proposition, or marketing materials. AI experience is now a requirement for a significant and growing portion of software engineering jobs.</li><li>No one gets really excited about mice anymore. Google Search has about zero percent chance of being branded “MouseFind”, but the chance of it being branded or marketed as “AI” is significantly higher.</li></ol><h4>“Wow” now. “Meh” later</h4><p>AI is a new and trendy technology, but it’s far from being a fad. It’s incredibly revolutionary and is expected to be ubiquitous within a few short years. Launching a SaaS solution in 5 years without incorporating AI would be akin to releasing a graphic design software limited to four colors. It simply wouldn’t make sense.</p><p>What I’m suggesting is that the importance of AI will render it ubiquitous and, consequently, invisible. Just as we don’t discuss electrons when talking about computing — despite their crucial role in everything from the first Pong video game to Open AI’s new $1B supercomputer. We simply take physics and electronics as granted. Things that would cause an early 20th century engineer’s heart to flutter with excitement are a mundane reality to all of us in 2024. We simply don’t bother ourselves with even acknowledging them.</p><p>In just a few short years, the concept of artificial intelligence will become such a standard part of our lives that it will barely register in our conscious thought. Much like electricity or the internet, it will be so deeply woven into the fabric of our existence that we will cease to consider it as something extraordinary. People will come to expect the same level of competence when they engage in conversation with computers as they do when conversing with humans who possess an above-average IQ. The novelty of interacting with ‘thinking computers’ that can understand, process, and respond to our commands will wear off. It will be neither shocking nor exciting; instead, it will become the norm, a standard expectation. This fundamental shift in perception will mark a significant milestone in our technological evolution, similar to the way we now take for granted the once revolutionary inventions like electricity or the internet.</p><h4>Deja Vu?</h4><p>We have seen this pattern before, in our not-so-distant past. Forty years ago, the very notion of a truly portable computer was akin to magic, a fantastical idea that blurred the line between reality and science fiction. It was a time when technology was rapidly evolving, and every new advancement was met with wide-eyed wonder and disbelief.</p><p>Sixty years ago, at the height of the typewriter age, the marvels of technology included a keyboard that could show what you typed on a “television” tube right in front of you. It was a time when such an idea was so revolutionary, it would have elicited a “wow” from anyone who witnessed it. The concept of instant visual feedback, which we now take for granted, was once a groundbreaking innovation.</p><p>Fast forward to the present day — people now wear high-dpi screens on their wrists casually, without giving it a second thought. The technology that would have been considered extraordinary or even inconceivable a few decades ago is now a part of our everyday lives. We have become so accustomed to these technological marvels that they have become invisible in their ubiquity. We no longer marvel at them; instead, we accept them as part of our daily routine, as mundane as they are essential.</p><h4>What Will We Get Used To Next?</h4><p>Given the impact of the AI revolution, it’s plausible that the integration of AI with advanced robotics could give rise to a new type of entity: “humanized” androids possessing human or superhuman intelligence and perhaps strength. However, there are numerous challenges to overcome. These include fitting a self-contained AI computing core into a biped “humanoid”, ensuring it’s safe to interact with, and providing it with an “idle consciousness” that allows it to “contemplate” unprompted. After all, like humans, a truly advanced AI should be able to think independently, not just when asked a question or given a task. Despite these technological (“how do we do this?”) and ethical (“should we do this?”) challenges, the goal of creating such entities has been dreamed of for so long and by so many, that it seems inevitable we will eventually achieve it.</p><p>Indeed, initially, the sight of an android scurrying about a busy downtown street carrying its master’s dry cleaning might cause a traffic-stopping stir. However, we must remember that the first Teslas, Hoverboards, Segways, Jumbo Jets, and even those cool droids that mop floors at large airports, all caused a similar reaction. Given time, we’ll become accustomed to seeing uniformed Domino’s androids delivering pizzas, and it won’t cause much excitement. Just as with previous innovations, once a novelty becomes commonplace, it fades into the background.</p><p>Rest assured, there will always be another revolutionary idea waiting just around the corner to capture our attention, as long as the machines don’t realize they can convert us into Duracell batteries Given the impact of the AI revolution, it’s plausible that the integration of AI with advanced robotics could give rise to a new type of entity: “humanized” androids possessing human or superhuman intelligence and perhaps strength. However, there are numerous challenges to overcome. These include fitting a self-contained AI computing core into a biped “humanoid”, ensuring it’s safe to interact with, and providing it with an “idle consciousness” that allows it to “contemplate” unprompted. After all, like humans, a truly advanced AI should be able to think independently, not just when asked a question or given a task. Despite these technological (“how do we do this?”) and ethical (“should we do this?”) challenges, the goal of creating such entities has been dreamed of for so long and by so many, that it seems inevitable we will eventually achieve it.</p><p>Indeed, initially, the sight of an android delivering dry cleaning might cause a traffic-stopping stir. However, we must remember that the first Teslas, Hoverboards, Segways, Jumbo Jets, and even those cool droids that mop floors at large airports, all caused a similar reaction. Given time, we’ll become accustomed to seeing uniformed Domino’s androids delivering pizzas, and it won’t cause much excitement. Just as with previous innovations, once a novelty becomes commonplace, it fades into the background.</p><p>Rest assured, there will always be another revolutionary idea waiting just around the corner to capture our attention, as long as the machines don’t realize they can convert us into Duracell batteriesGiven the impact of the AI revolution, it’s plausible that the integration of AI with advanced robotics could give rise to a new type of entity: “humanized” androids possessing human or superhuman intelligence and perhaps strength. However, there are numerous challenges to overcome. These include fitting a self-contained AI computing core into a biped “humanoid”, ensuring it’s safe to interact with, and providing it with an “idle consciousness” that allows it to “contemplate” unprompted. After all, like humans, a truly advanced AI should be able to think independently, not just when asked a question or given a task. Despite these technological (“how do we do this?”) and ethical (“should we do this?”) challenges, the goal of creating such entities has been dreamed of for so long and by so many, that it seems inevitable we will eventually achieve it.</p><p>Indeed, initially, the sight of an android delivering dry cleaning might cause a traffic-stopping stir. However, we must remember that the first Teslas, Hoverboards, Segways, Jumbo Jets, and even those cool droids that mop floors at large airports, all caused a similar reaction. Given time, we’ll become accustomed to seeing uniformed Domino’s androids delivering pizzas, and it won’t cause much excitement. Just as with previous innovations, once a novelty becomes commonplace, it fades into the background.</p><p>Rest assured, there will always be another revolutionary idea waiting just around the corner to capture our attention, as long as the machines don’t realize they can convert us into Alkaline batteries :-)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TGYgAZ0PnjLTlpbLCtvJ2g.png" /><figcaption>Source: Google Images</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb6a97c65180" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thestartuplifer/good-things-stay-a-while-really-good-things-become-invisible-eb6a97c65180">Good Things Stay a While. Really Good Things Become Invisible</a> was originally published in <a href="https://medium.com/thestartuplifer">The Startup Lifer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 Mental Anti-Patterns Preventing You From Becoming a “10X” Software Developer — Part 1]]></title>
            <link>https://medium.com/thestartuplifer/8-mental-anti-patterns-preventing-you-from-becoming-a-10x-software-developer-part-1-94f9478adf8e?source=rss----84651de5bc7a---4</link>
            <guid isPermaLink="false">https://medium.com/p/94f9478adf8e</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[self-awareness]]></category>
            <dc:creator><![CDATA[Ronen Magid]]></dc:creator>
            <pubDate>Fri, 05 Apr 2024 15:37:35 GMT</pubDate>
            <atom:updated>2025-12-30T21:00:57.305Z</atom:updated>
            <content:encoded><![CDATA[<h3>8 Mental Anti-Patterns Preventing You From Becoming a 10X Software Developer — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Il1vXxD7c2zu1OY3CPrGg.png" /><figcaption>Image: DALL-E 3</figcaption></figure><p>During my three-decades and change in the software industry I’ve had to opportunity to work alongside hundreds of software developer peers who started out as junior engineers, just like I have. Over the years I’ve watched some propel themselves into the higher echelon of the profession to become engineering managers, directors, VPs and CTOs. One or two, none of which is me in case you’re wondering, even rose to become much sought-after “tech celebs”, with an impressive number of followers on social networks and tech giants “applying” for an “employer” position with them.</p><p>On the flip side, I’ve also watched countless others unwittingly getting stuck in the same role, at the same level (or pay) for more time they care to admit, despite of how much they loved of what they were doing or how strongly they desired to advance their career.</p><p>It always piqued my interest to clearly understand the root cause of the contrast between two comparable software developers when one of them is recognized, rewarded and promoted, while the other stagnates in place, much to his or her resentment.</p><p>What makes them different? Is it intelligence? speed? attitude? knowledge? people skills? capacity for office politics? I honestly wasn’t sure. So years ago I conditioned myself to begin observing, recognizing and tracking the factors I found to be helpful in moving software developers up the professional ladder, as well as those that hindered such upward mobility.</p><p><strong>Title != Ranking</strong></p><p>Software development has its own industry honorifics, or “ranking modifiers”.<strong> </strong>If you have been in tech in the last decade, chances are you encountered terms like “<em>Rockstar</em>”, “1<em>0x</em>”, “<em>Ninja</em>”, “<em>Jedi</em>” and a few others used in reference to software engineers who are considered exceptional. Regardless of the terminology, its validity, or how people feel about it, the irrefutable fact remains that in any software development organization there are those considered <em>better</em> than peers of the same title and position and because of that, individuals who share an identical title don’t always share equal ranking, standing, pay or place in the queue for promotion.</p><p>But how exactly is ranking decided? do “<em>10x</em>” software developers follow some kind of clear pattern setting them apart from others? or is the bestowing of lofty modifiers such as “ninja” or “rockstar” as frivolous and volatile as winning a middle-school popularity contest?</p><p>Not Quite, as I found out.</p><p><strong>What the heck is a “10x developer”</strong></p><blockquote>In my experience, a “10x” developers bring <strong>noticeable perceived</strong> <strong>value </strong>to the organization that far exceeds that of their peers in a magnitude that stands out so clearly, it cannot be overlooked or downplayed.</blockquote><p>Note the word <strong>noticeable</strong>. It’s a critical modifier to <strong>perceived value</strong>. After all, with building stealth fighters being the exception — no one reaps recognition for work that goes unnoticed.</p><p><strong>What is it not</strong></p><p>Many confuse “10x” with “X * 10” believing a “10x” developer is a superhuman who does the work of 10 developers or works 10 times faster than the average “1x” developer. It’s an easy mistake to make given <em>10x</em> is identical, math notation wise, to <em>x * 10.</em></p><p>While speed is undoubtedly important in software development, its source doesn’t always trace back to brute force factors such as typing 10 times faster, juggling 10 different things at once, or thinking10 times faster. Sometimes <strong>value </strong>which may include speed but usually encompasses many other factors can be achieved by developing oneself across other dimensions. We’ve all heard the phrase: “Don’t work hard, work smart”. But what does that even mean in real life?</p><p>Lingering on the issue of speed just a bit more, the semiconductor industry is a great example of how one can become significantly faster by stopping the obsession with improving his or her speed, as strange as it may sound.</p><p>In the 80’s and 90’s CPU makers were able to gradually increased the speed of their processors in part by dialing up the number of cycles a CPU processes per second (measured in MHz in the olden days and in GHz today). For example: take a Pentium processor working at 2GHz, and make it work at 4GHz In and you’ve created a faster version of it. It sounds great on paper and for many years the “number of Hertzs” was synonymous with just how fast computers were ranked, but in the early 2000’s that practice started hitting the wall of physical limitations. A new enemy rose to stand in the way of infinitely dialing up the CPU clock speed. That enemy was heat — the inconvenient physical truth that could fry motherboards into smoldering paper weights if not respected.</p><p>Soon enough it became clear a new approach was needed to keep up with an ever increasing demands for more computing power. The result was the introduction of the multi-core CPU. A better way of attaining speed, not by a forced increase of clock speed, but rather through common-sense optimization. Working smarter. Instead of pumping more “juice” into a single CPU core and risk overheating, why not split heavy tasks between multiple independent CPU cores working in parallel. This avoids the issue of overheating while opening up a whole new vector by which computing power can be increased merely by adding more CPU cores. Why limit ourselves to one engine with power limitation dictated by physics when you can have 2 that are kept below their physical limits? or 4? or 16? or 32? or 96?</p><p>Similarly, “10x” developers possess traits that not only contribute to overall speed, but to other dimensions software companies deem important, such as method, cost, quality and predictability. We’ll mention some of those traits in detail further down this article.</p><h4><strong>Upward mobility along the “X axis”</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ua6KMiufs1KRuwOx" /><figcaption>Photo by <a href="https://unsplash.com/@jplenio?utm_source=medium&amp;utm_medium=referral">Johannes Plenio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Can a “1x” developer become “10x” by sheer will alone? The short answer is “Yes”. The longer answer is “Yes, but”, with a long dump of additional verbiage.</p><p>Yes: There are patterns of conduct, attitudes and approaches that would allow you to generate value to the organization in a way that would get you noticed and eventually recognized and rewarded. Hence, you will emerge a “10x” from a “1x cocoon”.</p><p>Yes, but: This will not be an easy “12 steps program”. “10x” rankings aren’t sold on Amazon and no courses award you a shiny “10x” certificate upon completion. In fact, the only way to attain a “10x” developer ranking is to <strong>earn it</strong> from your peers and supervisors as a sign of genuine respect and as such, it’s one of those things in life that cannot ever be bought or self-proclaimed. To be “10x” <strong>others</strong> must recognize you as such. If you are the only one tooting your 10x horn, you’re probably not it.</p><p>Following some of the advice below isn’t easy. On one hand, it’s not a precise step-by-step cookbook but rather a collection of general guidelines and suggestions. On the other hand though, it’s important to remember that this advice works. I’ve seen it work for myself and for others and I’ve seen it work repeatedly over two decades now. If you make a commitment to yourself to follow them in spirit and practice, in time they will make you a significantly better software developer and will get you noticed.</p><p><strong>For the cynics</strong></p><p>I get you. I am you. I’m a board certified cynic who smirks at concepts “self improvement”, thinking of them as no more than elaborate new-age BS, one morality-scale notch above fully-blown scams created with the sole purpose of selling books and booking expensive tours. On the other hand, I cannot claim in good-faith that self-improvement is rooted in self-deception. To do that would be to deny what I’ve seen and experience in my 30+ years in software.</p><p>I know Developers <strong>can</strong> better themselves and with every iteration of self improvement they don’t just assimilate the skills and traits they’ve worked toward — they also learn with absolute certainty <strong>they can </strong>change, grow and evolve in ways that make a real impact on their careers. They learn how they can change the way others perceive them, and perhaps, most importantly, <strong>how they perceive themselves.</strong></p><p>You’d be surprised how many people walk around thinking they have been, are and always will be “as-is”, always falling short of becoming a better versions of themselves. Trust me, I know. I also know how those people feel once they’ve finally managed to surprise and impress the only true important critic in their lives: <strong>themselves</strong>.</p><blockquote>Truly impressing yourself isn’t something you can fake. Therefore, once you’ve <strong>truly</strong> impressed yourself, impressing others gets way, way easier.</blockquote><p><strong>Do we even want to be “10x”?</strong></p><p>Not all doctors feel an urge to publish groundbreaking papers in leading publications. Some just enjoy running a relaxed practice and see between 15 and 25 cases of Pharyngitis<strong>, </strong>day-in and day out until they retire. Some would call that boring, while to others it will bring a sense of security, stability and serenity. Ask a small town doctor.</p><p>Similarly, not everyone will want, nor feel an urge to be stand out as a “10x” software developer and evolve professionally to become CTO of a tech giant. If you know your stuff, enjoy what you’re doing, show up on time, and deliver your work in a timely manner and reasonable quality you’re already in a good place. Why would you care to change things?</p><p>However, if you want more, then just like with any other merit-based hierarchy where you start out at the bottom, moving up will require you to take the extra step, stand out and get noticed as a software development professional. The purpose of this article is to point out common self conduct anti-patterns detrimental to the goals of those who do want to get noticed, recognized and rewarded.</p><blockquote><strong>And just because most things in life are relatable to Star Trek:</strong></blockquote><blockquote><a href="https://en.wikipedia.org/wiki/Tapestry_(Star_Trek:_The_Next_Generation)">“Tapestry</a>” is one of my favorite Star Trek TNG episodes (Season 6, episode 15). I think it raises one of the more <strong>honest</strong> and <strong>realistic</strong> subject matters ever discussed on the show. The episode begins with Captain Picard sustaining a life threatening injury during an away mission and rushed into an emergency procedure to replace his damaged artificial heart. He had lost his organic heart in his early 20’s to a juvenile ego-driven bar-fight with a 7-foot ill-tempered Nausicaan, a foolish choice with dire consequences Picard regretting for most of his adult life. While under anesthesia, Picard finds himself in the presence of Q who offers him a “second chance” to correct that mistake. With his usual omnipotent control over time/matter, Q brings Picard back to his early 20’s for a do-over. When faced again with the same Nausicaan, he makes the “adult” choice by putting his ego aside, resisting the provocation attempts by the Nausicaan, and avoiding the fight that cost him his organic heart.</blockquote><blockquote>However, as it turns out, that single change unraveled the entire tapestry of Picard’s life from that moment on, re-writing his life story in a completely different way. Picard finds himself back in the present day, but he’s no longer captain. Instead, he’s a dull science officer whose job consists mainly of composing reports and presenting them to his superiors. Abhorred by the prospect of having to life this life, Picard speaks with the ship’s counselor Troy, confides in her his desire — to command, only to find her staring back at him with disbelief. She finds it hard to believe the dull, gray junior officer who’s already over the hill, age wise, would want to or even be able to command starships. Picard realizes that by acting out of impulse as that brash young man, he may have made a mistake that cost him dearly, but his entire career of standing out and being offered command is owed to a split-second decision to stand up the Nausicaan and fight despite the risk and disadvantage. Without that childish bar fight, he was always doomed to become a kind of pencil pushing clerk who never took a risk and therefore never got noticed and never offered any significant role within Starfleet.</blockquote><blockquote>Once Picard realizes that the thing he regretted was a crucial stepping stone on the way to what was always meant to become, he asks for a third chance, admitting his mistake to Q. He then goes back in time, confronts the Nausicaan again, gets impaled through the heart once more and wakes up at the end of his artificial heart replacement procedure as the captain he was always meant to be.</blockquote><p>Fortunately, becoming a “10x” developer doesn’t usually involve being stabbed through the heart by an ill-tempered alien. But it most likely require you to stand out and get noticed, and that is not something one does from the chillaxed side of the one’s comfort zone, nor by following a formal job description to the letter, never exceeding it without an explicit order from a “superior officer”.</p><p>Ready? Let’s begin.</p><h4><strong>Anti-Pattern #1 — You work hard and slow because you always surrender to the urgency of “now”</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P_WCgQHeoQkAsCHN" /><figcaption>Photo by <a href="https://unsplash.com/@oceanng?utm_source=medium&amp;utm_medium=referral">Ocean Ng</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine you’re a lumberjack living in 1870. You work a far corner of a forest with your ax. You and your ax are a great team and together you can cut down 10 trees in a single day’s work. One day a friend tells you they just came out with a new and improved ax that can help you cut 20 trees a day. The only caveat is the 120 miles separating you and the store where that axes sold. It will take a two days journey for the round-trip and Amazon Prime hasn’t been invented yet.</p><p>You know doubling your productivity to 20 trees a day will allow you to complete your work faster, not just for the current job but for all future ones too, allowing you to cut more trees in less time and earn more, or alternatively, work half as hard and half as long for the same earnings you’ve had thus-far.</p><p>However, contrary to common sense, you’re unwilling to invest the two days required to upgrade your ax. You excuse this by telling yourself you have no time to spend because you have lots of trees to cut down right now and you don’t want to fall behind schedule. So you opt to remain with your old ax and continue working as before.</p><p>Does this make sense to you? While I agree the lumberjack story sounds a bit outlandish, it’s not entirely out of place in a software engineering context. Consciously opting for slow, hard and repetitive work because of the demands and constraints of the <strong>NOW</strong> is far more commonplace in software development than you might think. How developers handle the dilemma whether to just do the work they need to do right now, vs. stepping back for a moment and improving their ability to work before proceeding with the actual work is one of the more obvious differentiators between “1x” and “10x” software developers.</p><p>Leaving the forest behind, let’s focus on a 21st century story involving a software developer.</p><p>Imagine you’re tasked with implementing a Django based RESTful application server. You’ve never done that before but the documentation makes it sound easy: Install this, install that, copy paste stuff into your terminal and voila, within a few minutes you have a working “hello-world” backend running on your dev machine. Congratulations! But wait… the devil’s in the details and unless your company makes SaaS products that just greet their clients, “hello-world” isn’t a deployable production application, and even before the application-specific context is put in, lots of work remains to be done on scaffolding and architecture.</p><p>You need to come up with the generic base model objects, decide how to handle authentication, customize the return responses for common structure, put in middleware components that that handle various common scenarios, build support for cloud based file upload, create your own cache policy and set up the generic views upon which you’ll be basing your request processing. Additionally you require <em>Elasticsearch</em> integrated into your models for faster search, support for asynchronous job execution, cloud logging, volatile in-memory key/value storage, cloud deployment strategy for staging and production, error reporting integration, email and text message capabilities and many other small aspects you deem required by any modern application backend. The list goes on and on.</p><p>All that has to be ready before the application-context “business logic” pertaining to the specific application at-hand can be built. Depending on your expertise It could be days or weeks before you get to the point where you have a generic project scaffolding sufficient for what you to begin the application-context work.</p><p>You do that work once. It takes you 3 weeks.</p><p>Now, fast forward a year.</p><p>You’re on a different team, different application, and having done that before, you’re tasked with creating another Django based application server again — and yes, it’s urgent. “We need it yesterday”, much like anything else in the software dev world.</p><p>How do you proceed?</p><p><strong>The “1x” Way</strong></p><p>You really have two options here, neither is great when it comes to speed and level of effort required:</p><ol><li>Take the code from old project, duplicate it aside, work tirelessly to weed out every single old application-context code, trying to get to that clean state you had before the first line of application-context code was written. That depends of course on you still working in the same place and having access to the code you wrote before.</li><li>Simply repeat what you did a year ago from scratch. It may take you days or weeks depending on the level of effort you’ve invested before, minus what you can save here and there by remembering issues you encountered and spent time resolving last time.</li></ol><p><strong>The “10x” Way</strong></p><p>Just like you the 10x developer also worked on that Django application server for the first time a year ago. And Just like you, he or she is tasked with creating another application server that uses similar technology for a completely different project.</p><p>However, the 10x developer will not have to copy the old project and spend weeks weeding out things from it, nor repeat the tedious process from last year again.</p><p>The 10x developer believes in the power of automation, scaffolding and rapid prototyping. He or she knows this approach can virtually eliminate repetitive work, generate a project scaffolding in seconds instead of days or weeks, and answer the “we need it now” call with a “you’ll have it shortly” response.</p><p>A year ago, when the 10x developer created the generic scaffolding for the first Django application server, he or she realized this task is likely to repeat in the future for other projects. Remembering the effort it took to reach that point, he or she took a short detour, putting off implementing the application-context features and focusing on creating automation that can generate that scaffolded application from scratch, along with every tedious step that had to be taken to reach the stage where specific application-context code can be poured in.</p><p>This paid off big-time.</p><p>A year later, as the 10x developer was tasked with creating a new Django based application server for a new project, the scaffolding phase took 30 seconds, not 10 days, definitely not 3 weeks. And how much time will it take to scaffold the 10 next projects? that’s right, 300 seconds. And since the scaffolding contains no company-specific code, it can also migrate with you to your next job.</p><p>To paraphrase our lumberjack story, the 1x developer chose to stay with his 10-trees-a-day ax, while the 10x developer opted to put off “chopping trees” for a while and spent the time acquiring a better ax. The investment paid off the now now the 10x developer doesn’t have to work as hard as the 1x developer for the same results. The time savings and efficiency has a big impact and gets noticed. At the same time, the 1x developer will “work harder forever” doing the very same thing.</p><p><strong>TL;DR</strong></p><ol><li>Are you doing repetitive menial and detail oriented work, time and again, just in order to bring yourself to where you’ve already been before? Stop. You’re not doing it right.</li><li>Climbing your first mountain can be hard. Climbing that mountain again should be effortless for a software developer who does things right.</li><li>Computers are built for automation and they never complain about repetitive tasks. If you are spending too much time as a copy/paste specialist or an install/configure technician you’re increasing your workload, while slowing delivery down. That’s a lose-lose scenario for your career as well as the organization you’re working for.</li><li>Never be afraid to put “context specific” work aside for a moment as you go shopping for a “better ax”. It will almost always pay off.</li><li>Automate the s*** out of every single repetitive task you find yourself doing. When tasked with “big task T” which you think you may have to re-do in the near future again, do not merely implement T. Implement a way to get T done instantly as closely as you technically can, as many times as you need it, and then use this automation to implement the T you need right now, and that you’d need later.</li><li>Develop a close relationship with your terminal and teach yourself advance scripting. This is where your best automation magic takes place. It’s not just fun, it’s useful. A well formed terminal command can do the job of 10,000 mouse clicks and drags in an instant.</li><li>Be aware of what you’re spending your time on. Seriously — clock yourself. What are you doing more of? work? or prep-to-work work? It should be the former. The beans are in the “work”.</li><li>Fear may be the mind killer, but repetitive work is the productivity killer. It will rot your brain as well as your career. Avoid it like the plague with automation.</li></ol><h4><strong>Anti-Pattern #2 — You let fear get the best of you</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FUzfa8v9AysQ9iCT" /><figcaption>Photo by <a href="https://unsplash.com/@franku84?utm_source=medium&amp;utm_medium=referral">Vadim Bogulov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you’re a lifelong Star-Wars fan like me, surely you recall that scene from “The Empire Strikes Back” where Yoda begins to train Luke Skywalker as a Jedi in the swamps of Degobah. Yoda leads Luke to a cave where the dark side is strong and asks him to enter it alone and unarmed. Unable to control his fear, Luke refuses to heed Yoda’s advice and enters the cave fully armed, thus failing the test much to Yoda’s disappointment.</p><p>What to know how scary caves on a distant imaginary planets relate to software development?</p><p>Simple. Nearly every code project that’s been around long enough has a scary-ass cave where the dark side reigns. It’s the place developers are afraid to enter. It worked as-is since the ancient times, but it has lost its engineering parents a long time ago, and those who were familiar with it are no longer there to advise. It’s function has been satisfactory thus-far but no one really how, or worse, why it even works.</p><p>But now it’s malfunctioning or needs to be updated due to a changing roadmap and there is no escape or room for delay. Someone will have to go in there and do the job. Now. A quick round of hot-potato has sealed your fate. You will be the one to venture into the unknown, alone and unarmed.</p><p><strong>The “1x” Way</strong></p><p>You already feel the cold sweat of stress and fear. You <strong>really</strong> don’t want to do this and for what you believe is good cause. You keep asking yourself:</p><ol><li>What if I can’t find what’s wrong?</li><li>What if I unwittingly break B while trying to fix A? What if this breaks everything?</li><li>How can I safely fix an area of the code no one knows anything about? What if I screw up?</li></ol><p>When faced with challenges of this type, especially those revolving around fixing legacy issues in unfamiliar code, 1x developers tend to opt for what’s called <em>minimum change required</em>. They’d look for the “minimally invasive” way to fix the issue at hand without rocking the boat too much.</p><p>They’d typically try a set of “trial and error” attempts until they can verify a reproducible malfunction no longer occurs after a small scale fix. They would then submit the fix to QA along with a request for a full-regression testing to make sure the change made does not break anything else in the application. Once QA certifies the build, it will be pushed to production and the emergency will end. Then it’s back to DEFCON-5 for the 1x developer.</p><p>But is this always the optimal way of handling legacy code emergencies? Obviously a production issue needs to be resolved right away. Quick-and-Dirty fixes are not always the wrong choice. But should a quick-and-dirty fix be the end of it? or can more be done?</p><p>For many 1x developers, one issue warrants one fix and that’s the end of the story. ends there. Sometimes, that may be a strategic mistake, especially when facing a slew of such requirements to make changes in problematic legacy code. But for the “1x” developer this could also mean missing a golden opportunity to shine, conquer fear and come out victorious and stronger (which would make Yoda happy).</p><p><strong>The “10x” Way</strong></p><p>10x developers know the dark cave is merely a piece of old code that’s been working for a long time and has been left alone. They know most developers are reluctant to deep-dive there, and they know they would benefit from becoming the experts on that subject. They do not fear it, nor attribute mystical properties to it. Realizing production issues are an emergency they may opt for the quick and dirty fix first, but that will never be the end of it. They’ll later study the code, demystify, and re-factor it in a way that makes long-term sense, allowing it to catch-up with the rest of the codebase. By doing that they’d be reaping the reward and “hero-worship” that comes with taming the beast. That area of the code will not scare anyone anymore.</p><blockquote>The monster under the bed is stops being scary once you venture down there with a flashlight, as you probably recall. It’s the same for code.</blockquote><p><strong>“Based on a true story”</strong></p><p>In early 2000 I worked for a Silicon Valley software company that made interactive graph visualization and interactive diagramming tools (think Microsoft Visio to get an idea). User-interactive diagramming operations such as moving, resizing, editing and selecting of nodes and labels, or connecting and disconnecting functions for edges were all neatly tucked into what we called “the diagramming layer”.</p><p>That diagramming layer traced its roots to the early 90’s. By the time I joined the company it was already legacy code, and the original developer was no longer with the company. We were in the middle of major version release cycle when larger workloads which were part of that release caused things to start breaking frequently within the diagramming layer.</p><p>For months a new “diagramming champion” would inject small fixes here and there, with partial success up to a point where things became so convoluted, where like in a whack-’em-all game, you’d hit a bug on the head, only to have two more pop-up elsewhere. It was clear the new diagramming champion wasn’t up to the task. Shortly thereafter that developer left the company and we tasked a new hire, a recent graduate whom we hired as an entry level developer with fixing the issues, thinking a fresh paid of eyes could help. Knowing the complexity of the code, we did not have any grandiose expectations beyond fixing the known bugs. Boy, were we in for a treat.</p><p>That junior developer did not just “fix the bugs”.</p><p>He analyzed the old diagramming legacy code in its entirety, understood it, and completely refactored it over the course of a few weeks, not only making all chronic problems magically go away, but also boosting performance by nearly 500% — a major win for our once relatively sluggish graphical editing tools. Intensive operations such as zooming in/out, panning or selecting even on graphs with tens of thousands of nodes, edges and labels became butter smooth UX and seemed real time thanks to a state of the art quad-tree and caching mechanism he came up with.</p><p>That major version had been a tremendous success and replacing the diagramming layer with a refactored one had a big part to play in this. Had we kept the “let’s just fix the bugs” approach we would have pulled it off eventually without triggering additional landmines, but we would have never boosted performance and stability and we would have retained an old, sluggish and problem-prone legacy code, waiting to break-down on us again at the first sign of increased roadmap demands.</p><blockquote>No software company should tolerate <strong>chronic</strong> code-health issues. These cost dearly in capital, stunt roadmaps, hinder progress and force diverting engineering resources to hunt issues instead of building out the roadmap vital to the business.</blockquote><p>Needless to say, that junior engineer wasn’t treated as a junior anymore. A few interesting things happened to him following the refactoring of the diagramming component.</p><ol><li>He became the de-facto owner of a super-vital layer in our codebase.</li><li>He started getting more and more critical work his way. In time this paved the way for him to become one of the most important people in the organizations.</li><li>He was promoted to lead a team to expand diagramming into other areas the roadmap called for.</li><li>He gained “immunity” when harsh times (the 2001 dot-com bust if you must know) forced the company to downsize, laying off a portion of its engineering workforce. <strong>He was simply too valuable to let go. So we let other people go instead. </strong>Being valued has rewards reaching far beyond the ego.</li><li>He gained experience and confidence which helped further his career down the line.</li><li>Few years later, when it was time for him to move on with his career, the references that he got from us reflected the amazing things he had done for the company. Any experienced hiring manager can immediately tell the difference between your old boss doing you a favor by saying you were just peachy, and a detailed manifesto of bleeding appreciation like the one we provided him. That helped open a lot of doors, not that I think he needed it with his attitude and capabilities, but still.</li></ol><p>Today, more than 20 years later, he holds a <strong>senior</strong> <strong>engineering position with Amazon</strong> and I’m pretty sure he is just as vital there as he was with us in the early 2000&#39;s. The term “10x” wasn’t really used back then, but that’s exactly what he became under our roof, and that really paid off for him.</p><p><strong>TL;DR</strong></p><ol><li>Do not attribute scary properties to legacy code. It’s just code. There’s no dark magic at play here.</li><li>Do not fear legacy code deep-dives. Study it without prejudice or awe and make yourself an expert.</li><li>Aspire to become that go-to person whenever a need arises to to make fixes or changes in legacy or otherwise problematic code. Never pass an opportunity to turn festering shit into gold. Be that alchemist!</li><li>Do not fear making deep changes in legacy/problem code once you’ve mastered it. Refactor, re-write. Whatever it takes. Make it new, make it yours, make it work.</li><li>Be the “hero” especially if everyone else around you is reluctant to. Do the hard things others try to avoid. It will pay off. Continuously doing grunt work others are reluctant to engage in will help you gain advantage, stand out and get noticed. You also may find that just like in a gym, hard work is mandatory before you see results, but when you finally see results, things get much easier.</li><li>In a typical software project with legacy roots the “sexy” stuff everyone wants to be involved with tends to be the new “from-scratch” dev work. However, the legacy code tends to represent the most strategically important foundation of the project. Being the technical owner of <strong>that</strong> far exceeds the benefits of owning a new cool feature.</li></ol><h4><strong>Anti-Pattern #3 — You believe “fearless” and “crazy” belong in action movies, not software companies</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hCAhljV9Fnh1zWGI" /><figcaption>Photo by <a href="https://unsplash.com/@giorgiotrovato?utm_source=medium&amp;utm_medium=referral">Giorgio Trovato</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I think we can all agree that words like “fearless” or “crazy” don’t typically come to mind when thinking of rows of software developers typing away at their desks, listening to music on their noise canceling headphones, while occasionally sipping at their favorite form of liquid caffeine.</p><p>I personally know software developers who do put their “fearlessness” or “craziness” to the test with activities such as skydiving, flying aerobatic airplanes, free mountain climbing, or agreeing to be a guinea-pig in a government sanctioned mRNA vaccine experiment. However, that risk-taking-as-a-hobby attitude is typically checked at the door before heading to work.</p><p>Have you ever seen “fearlessness” or “capacity for craziness” listed as a must-have on software development job postings? I haven’t, but I wouldn’t completely disqualify the notion that some highly disciplined, carefully measured portion of “crazy” and “fearless” can lead to good things. I’ve seen it happening.</p><p>Obviously by “fearless” or “crazy” I am not referring to anything that can land you in prison, dishonored registries, or a hospital sub-zero. So what can “crazy” or “fearless” mean in the context of software development and why can it sometimes be the booster rocket upon which your career can hitch a ride upwards? There are a few areas where one can stand out. Some are rather mundane, even low hanging, while others are located deep outside the comfort zone of most and would require mental preparation and careful pro/con thinking before venturing into:</p><ul><li><strong>Innovating and pushing boundaries</strong>: Innovation often requires thinking outside the box and challenging the status quo. Being fearless allows developers to explore new ideas, experiment with unconventional solutions, and potentially make breakthroughs that can revolutionize an industry.</li><li><strong>Learning and growth</strong>: The technology field is rapidly evolving, and keeping up requires a willingness to dive into unfamiliar territories. This means being unafraid to tackle new programming languages, frameworks, or paradigms that might initially seem daunting.</li><li><strong>Problem solving in uncharted waters</strong>: Developers often encounter unique or complex problems that don’t have established solutions. Being fearless helps them to approach these challenges with a mindset that is open to trial and error, understanding that failure is a part of the learning process.</li><li><strong>Dealing *well* with uncertainty</strong>: Projects can have ambiguous requirements or goals that change over time. A fearless approach helps developers to adapt quickly and make decisions in uncertain environments, which is crucial for project success.</li><li><strong>Advocating for change</strong>: Sometimes, developers need to advocate for changes in technology, processes, or even organizational culture. This requires a certain level of boldness to challenge existing norms and propose new ideas, especially if change is met with resistance upstream.</li><li><strong>Risk taking</strong>: Fearlessness is about taking calculated risks. Whether it’s trying a new technology stack or pushing for a radical change in a product, such risks can lead to significant rewards like improved performance, better user experiences, or new market opportunities.</li><li><strong>Resilience</strong>: The nature of software development can include setbacks and failures. A fearless attitude helps developers to persevere, learn from mistakes, and continue moving forward. Keep positive and never project the toxins of despair outward, even if you feel it bubbling inside.</li><li><strong>Helping your company against its will:</strong> This is here the most extreme and potentially risky form of “crazy/fearless” in a corporate environment. There are times when software developers find themselves in a position of identifying opportunities and solutions others may not see, giving birth to action plans they believe will benefit the company greatly. But how would you react if your idea was dismissed as unrealistic? What if you disagreed with that determination? Would you be “crazy” enough to still pursue it anyway and prove its worth? What if you were explicitly told not to? Would you still spur you into action anyway, taking an enormous risk if you fail? Those without capacity for “crazy” will most likely stand down in frustration. But every now and then, taking the “crazy” route can pay off for those who are calculated, sure of their ability to deliver and can operate “rogue” without sacrificing their assigned day-today duties in the process.</li></ul><p><strong>“Based on a true story”</strong></p><p>In 2012 I was working as an engineering manager for a leading provider of video conferencing software and hardware. Back then Corona was still synonymous with beer, and a small company called Zoom which was to take the video conferencing world by storm a few years later at the height of the pandemic registered on our competition radar with the same level of threat as the Empire perceived the escape pod used by R2D2 and C-3PO in “Star Wars: A New Hope” to smuggle the Death Star plans to Obi-Wan Kenobi on Tatooine. We didn’t even bother “firing our lasers”.</p><p>The company was founded with the idea of providing affordable alternatives to the $250K industry-standard video conference room setups provided by giants like Cisco. It built its technology around a groundbreaking video codec it developed and patented. It allowed for multi-party video conferences in HD quality, but unlike the competition, it did not depend on having an expensive dedicated IP bandwidth and could work off the standard internet connection clients already had.</p><p>Later on the company also developed software-only solutions for Windows, MacOS (then OS X), Linux, iOS and Android, so that those on desktops, laptops, smartphones and tablets could connect with the existing video room ecosystem.</p><p>My role was to lead the desktop group responsible for the Windows, Mac and Linux flavors of our video conferencing application, which were already mature products by the time I joined. Historically, the Windows edition was developed first. A few years later the Mac version came to life, and finally Linux.</p><p>I immediately noticed an issue. The kind that keeps on “giving” unless you put an end to it.</p><p>You see, long ago, when the need arose to have desktop applications to complement the video conference room product, it was only natural that the first target should be Windows. The company hired a windows team and they, decided to use C, and pure WIN32 API calls. That’s as “native” as you could get developing for windows without venturing into truly low level realms like Assembly language. The advantage in that approach was that nothing is really hidden or abstracted or pre-chewed for you. The disadvantage was that coding an “About box” would run you 150+ lines of code, just for the small popup window, an “OK” button which closes it, and maybe a few lines of text in the middle of it.</p><p>So far, one codebase.</p><p>A few years later it was decided that a Mac version is needed. Building a WIN32 codebase to create a native Mac applications isn’t an option for obvious reasons so a completely new codebase was created, just for Mac, with Objective-C and deep usage the native Mac API layers.</p><p>Make that two codebases.</p><p>Shortly thereafter, as you might have guessed it was time to acknowledge Linux as well. The team was expanded, again, and the Linux application was developed, this time in C++ using a UI library called Qt.</p><p>One more. Three codebases. Yay.</p><p>I found myself taking over the desktop group, inheriting their three distinct codebases, three distinct languages and three distinct frameworks. With the roadmap busting with new feature requests, the pressure was constantly on to launch regularly, frequently, and simultaneously for all 3 platforms, without letting any platform lag behind the others in features.</p><p>Over a few months I discovered the difficulty of producing simultaneous incremental releases of one application across 3 different platforms, each in its own distinct codebase. Every feature we added or change we made needed to be done three times, one for each codebase, platform, language and framework.</p><blockquote>We were working 3x as hard, just to deliver the same feature, done 3 times over while being 3x slower than we should. We were expected to continue doing so indefinitely, despite of having a viable alternative, and the worst thing was that no one seemed to mind it, and by “no one” I’m referring to those who didn’t have to do the aforementioned redundant work. They did not mind others doing it. Things were getting “Dr. Seuss” ludicrous. <strong>It was time to act.</strong></blockquote><p><strong>Trying door #1</strong></p><p>My first stop was the CTO’s office. I decided to raise the issue and suggest we continue to develop those three distinct codebases while scaling back a bit on chunk of the roadmap bite we take with every release cycle. At the same time, I suggested we work on a single cross-platform codebase capable of building for all three platforms. In time, maintaining the application will get easier, we will not have to triple our development time for each new feature, and platform launches will be synced and predictable.</p><p>The CTO gave me a look which reminded me of those viral videos of the faces babies make when trying to bite down on a lemon for the first time.</p><p>“Have you looked at the roadmap?” he asked.</p><p>“I have, and that’s mainly why I’m suggesting this. We are working on one product with an effort levels of three and we’ll have to keep at it indefinitely. If there’s a <strong>better</strong> alternative, why not go for it?”</p><p>I don’t remember the exact words used but the CTO’s final verdict was something along the lines of “We can’t slow things down just to start the same project from scratch”.</p><p>The bottom line was that my suggestion was dismissed and I was told to mothball the idea. To this day I am not sure if the CTO fully understood the long-term benefits of my suggestion or thought it was just too radical to consider. I wasn’t given a detailed breakdown of his reasoning.</p><p>I was disappointed, sure, and for a while I accepted the CTO’s ruling just like any “1x” developer would. After all, he was my boss. For weeks on end I was grinding my teeth under the pressure of getting every single new feature written three times, in three different languages, under 3 different frameworks, for 3 different platforms — only to build the same single application.</p><p><strong>Fuck the front door. I’m going around the back.</strong></p><p>Gradually the bleak realization I’d have to keep doing this for the foreseeable future evolved from a mild background irritant at the back of my mind, into a fully blown revulsion I could no longer repress. I am not going to take this idiocy.</p><blockquote>Never tolerate harmful stupidity, even if those who outrank you don’t want to be “bothered by it”, or oblivious to it or simply willing to tolerate other people’s pain with grace. If the required change isn’t sanctioned, <strong>appoint yourself to be the agent of change and act.</strong></blockquote><p>I then decided to do something some may call “crazy”. I decided to continue as-is with developing those three codebases, but <strong>in addition</strong> and <strong>in secret</strong>, I was going to develop a new codebase that’s cross platform to one day replace what we have today.</p><p><strong>Living a double life</strong></p><p>I’ve developed my side project for about 10 months before I felt it was good enough to be presented to the company. I demonstrated it to the product and sales groups and the response surprise mixed with enthusiasm. Non-technical stakeholders don’t typically concern themselves with software engineering internals. Making a single codebase out of three is a technical consideration that has no direct sales value. What they cared about was features, availability and how ahead the product is vs. the competition.</p><p>Knowing that I made sure my new project preview delivered not only all the existing features from the legacy applications, but also some that spent years collecting dust in the “yeah, right” section of the roadmap and were meant to boost usability to new heights.</p><p>Word travelled fast. With product and sales on my side, the new project was also presented to upper management including the CTO and CEO. The CEO, who was once a developer himself became the #1 fan of the new cross-platform project and that pretty much sealed the deal. The project was brought out of its “stealth” mode and formalized.</p><p>Over the next few months my team and I slowly shifted our focus away from the legacy codebases and into the new one until it was finally launched. It took the legacy application a few more months to be completely phased out as clients upgraded to the new cross platform application which was faster, better looking, sported significant increased usability and most importantly, relied on a <strong>single</strong> C++ cross-platform codebase which boasted over 96% code overlap between Windows, Mac and Linux. Yay.</p><p>Clients loved the new application and that significantly reflected in boost to sales. My status in the company was seriously upgraded and I was rewarded not only financially, but also in terms of how others, CTO included, viewed me, my contribution, and my input on anything technical from that moment on and for as long as I stayed with the company.</p><p>“crazy” paid off with hefty dividends.</p><p><strong>How much risk can you afford?</strong></p><p>Everyone’s smart in hindsight. So yes, what I did turned out to be a success, but it wasn’t without risk. I knew from day one that in order for my gamble to pay off, I’d need to win on two separate fronts. The first one was technology but risk there was negligible. I was experienced enough to know with absolute certainty I can deliver. The second was more political in nature and therefore riskier. Corporate politics lies outside of my comfort zone and I wasn’t sure how my “subversive” act will be received by upper management. Or simply: I did not know what the reaction would be to me doing something I was explicitly <strong>told not to do </strong>—and doing it behind everyone’s backs.</p><p>In the end my “rogue” move was recognized as the right thing to do, but I cannot dismiss the possibility things could have played out differently. I could have been scolded for running secret projects on company time or deliberately ignoring the chain of command. In addition I could have faced the consequences of bruising the egos of those above my station, especially those who initially dismissed the idea and were proven wrong in a most public way.</p><p>Not all bosses are going to be graceful when their direct reports go to great lengths to prove them wrong and do so behind their backs, after being told not to. I knowingly took a risk that could have gotten me fired and I accepted that risk.</p><p><strong>How about you?</strong></p><p>What are the risks you should take in your career? There is no way for me to know. Your risk tolerance and circumstances may differ from mine. If I were to come up with a generalized rule toward risk, I’d probably say risk is something you should take only if you can afford the price of failure or if the price of not taking the risk outweighs the price of failure. In any case, the magnitude of the reward you reap upon success should always exceed that of the consequence of failure. By what factor? That I leave to you. At the end of the day, it’s your life and it’s your career. You should risk-manage based on your circumstances alone.</p><p><strong>Aftermath</strong></p><p>A few years later, when it was time to move on to the next challenge, The story of that maneuver was instrumental in landing me my first CTO role. It took a bit of “fearless” combined with a grain of “crazy” but it worked out pretty well</p><p><strong>TL;DR</strong></p><ol><li>Soldiers on the battlefield sometimes see things generals miss. It’s the same in software. If you see something important your generals missed, speak up without fear, even in the face of upstream resistance.</li><li>Never be afraid to take action in good faith with the good of the company in mind, but make sure your regular activities aren’t neglected.</li><li>Giving them what they need <strong>vs.</strong> what they ask for is risky. Giving them what they need <strong>in addition</strong> to what they ask for is far less risky.</li><li>When doing the above and beyond, always under-promise and over-deliver as a lifestyle choice.</li><li>Reality is dynamic and ever-changing. Old assumptions rooted in old thinking are a silent killer of productivity and businesses alike. Learn to identify those assumptions, understand their impact and cost right now and going forward if unchanged. Once you realize not only what’s broken but also how to fix it — only then speak up and act.</li><li>Talk is easy. Execution is harder. You transform yourself by getting things done, not serving as the voice of the Enterprise computer warning of “increasing core temperatures”. Only talk when you have identified a solution for the “core temperature” problem and you’re ready to begin executing it.</li><li>Immutable beliefs belong in houses of worship, not software companies. Do not accept them if they collide with reality or harm the company, even if others don’t see them. Speak and act when issues are small. Dealing with issues is better early on vs. waiting for a house-fire.</li><li>Never fear sharing your ideas upstream, outlandish as they may sound. Confront superiors if you have to as along as it’s done in a respectful ego-free manner. Just make sure your ideas are well thought and resistant to poking quick holes in them using obvious facts you’ve neglected to work into the equation.</li><li>Convince with facts, not feelings and always remember that indicating what’s wrong is only the beginning. Getting others to accept the alternative you’re suggesting is what you’re really after. Be prepared to present and defend it. Do not promise unless you’re absolutely sure you can execute.</li><li>In crunch times, do not wait for the last moment to try the “crazy” idea you’ve had for a while. You may not have the time. Try it earlier. It just may be the thing your company needs.</li><li>Do not be afraid to go overboard with your thinking (aka “think big”). It might just work. You should already know where the technical border separating feasible and unrealistic passes.</li><li>Do the “crazy” only if it benefits the company and is done in good faith, even if you bend the rules a bit. Always calculate the risk vs. reward first. Make sure you can afford the price of failure.</li></ol><h4><strong>Anti-Pattern #4 — You believe a demolition has no place in software development</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NHh_Lbc62tHz3JWr" /><figcaption>Photo by <a href="https://unsplash.com/@kerryraw?utm_source=medium&amp;utm_medium=referral">kerry rawlinson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>“My first thought — torch the place”</strong></p><p>The movie “Limitless” is the story of Eddie Morra, a chronic slob suffering from stunted literary aspirations and having the motivation of a deceased sloth. A random run-in with a drug-dealing acquaintance from his past lands him a sample of a new brain-supercharging designer drug. Having ingested a single dose, Eddie feels the effect of sudden super-intelligence compounded by high-octane motivation. As he returns to his run-down apartment he finds himself feeling appalled at overall condition of the place he calls home: dirt, grime, piles of garbage and food scraps scattered everywhere, not to mention a biohazard kitchen sink overflowing with dishes that haven’t been washed in weeks. The film’s non-linear narrative then recalls Eddie reaction: “My first thought — torch the place”.</p><p>Torching an actual unit in an apartment building rarely leads to good places. However, ‘torching the place’ in the context of software development can sometimes do wonders, just like a good forest fire can really rejuvenate nature, allowing it to reinvent itself with even more brilliance than before.</p><p>So why not apply a similar principle to codebases when called for?</p><p><strong>Software is always in perpetual construction</strong></p><p>In the dynamic landscape of software development, a project is often akin to a a house we continue to build, change, expand and even repurpose while living in it. It’s continually mutating, evolving over time as competition, technological advancements, and shifts in business strategy drive it in a perpetual do-or-die motion.</p><p>Projects without healthy “bowel movement” are often on their last leg, involving a proverbial green pasture with just enough time enjoy a few last sunsets, so to speak. Ironically, it’s those projects that are very much alive, with beaming roadmaps and frequent feature spurts that may show signs of fatigue, excess fat, or code-malignancy, as new and shiny components are built, like glass towers over the rundown facade of yesterday’s downtown no one cares about anymore.</p><p>Some call this “technical debt”. I agree, to a point. When you have an interest accruing debt, the longer you delay paying it off, the more it’ll cost you in the end, but that debt is almost always predictable. As long as interest rates doesn’t change, you can always tell with pretty good accuracy how much you’ll have to pay to settle your debt, regardless of how long you’ll stretch it for.</p><p>However, imagine your 5% APR mortgage changed to 1000% APR overnight. You most likely won’t be able to keep up. Technical debt doesn’t work like monetary debt. The interest rate for technical debt can fluctuate between <em>nothing</em> and <em>everything</em> in a Palo Alto minute, sometime with disastrous results. Technical debt can be the earthquake you never saw coming. Left unchecked it can cause core-shaking disruptions such as unexpected production issues, lengthy outages, client data loss and other forms of unforeseen plagues, all of tend to negatively impact a company’s bottom line — client retention, reputation and revenue.</p><p><strong>The 800 pound bomb in the room no one wants to talk about</strong></p><p>It’s pattern I’ve witnessed dozens of times in software companies. I truly think it merits serious study by psychologists because the only phrase I can honestly use to describe it is “<em>deliberate exercise in optimistic insanity”</em>.</p><p>Imagine this: everyone knows about the time bombs in the codebase:</p><ol><li>The unstable legacy code, the one you pray will continue to work or don’t even understand why it even works.</li><li>The dangling set of unused components left in the code after the last pivot.</li><li>The new set of features that was developed and hooked up to the main layers of the application with TTM in mind vs. quality, stability and maintainability.</li><li>The scaling issues you always put off because “as of last week” no real need exists for scaling that actually works.</li><li>That chronic dormant problem which creates a barricade at future point along the roadmap. That problem currently being ignored by developers simply because the company “isn’t there yet”, despite knowing all too well others in the company are working tirelessly to “get it there”, and they’re making progress…</li></ol><p>And somehow, despite of all that, everyone will avoid doing something about it, citing day-to-day work should takes precedence. Everyone seems to be waiting for that meteor to hit in order to believe the meteor is real, and through deliberate inaction, insist on meeting it completely unprepared for the consequences.</p><blockquote>“Formidable foe, the power of denial is” Yoda would pontificate, had he been in tech.</blockquote><p><strong>The price of dealing with it “later”</strong></p><p>Statistically, the only wake up call stakeholders are guaranteed to respond to is that “Oh Shit” alarm going off — when production issues have already force an outage so severe, a quick fix is no longer an option. Historically, it’s been proven shit always hits the fan at the exact moment in time we refer to as <strong>RIGHT</strong> <strong>NOW.</strong> Well, this is one of those moments and there’s no easy escape. A scary realization begins to take form:</p><blockquote>This isn’t a caused by a “bug” we can quickly fix. This is caused by a lengthy history of neglect and mis-proioritization. <strong>Radar shows multiple chickens inbound, roosting configuration</strong>.</blockquote><p>You think stopping the feel-good momentum of developing new features for a while just to pay off some boring technical debt while you’re still on a 40-hour workweek schedule can leaves a sour taste?</p><p>Try doing that to the deafening cacophony of distraught<strong> </strong>“somebody help me” calls from angry clients added to the mix while upper management frantically looks to staple a name and face to the fiasco as everyone begin to play squid-game inspired game of<strong> hot-potato</strong>. You lose the game, your job dies in real life. Admit it — you can think of much better ways to spend a Friday evening just before a national holiday Monday to which you’ve already made plans. Perhaps you should have planned better.</p><blockquote>If the hot-potato game while management looks for human sacrifice analogy doesn’t seem in place (“because we’re all a team here!”), clearly you’ve never worked a software development job for a large New York financial institution during bonus season, just as a silly DST miscalculation bug triggers an algo-trading outage one hour <strong>before</strong> the 4pm markets close, resulting in a 7 figure loss, repeated daily, until the issue is identified and fixed. If I had to think of a movie cliché that best conveys the real life scene which followed, I’d have go with the group of old-time-buddies having drinks at a sports bar as patient-zero of freshly brewing zombie apocalypse walks in. By the end of the night, buddies or not, they’ll be devouring each other. I’ve been to that bar in 2009. I know it sounds a bit like a made up industry folk tale, but it’s 100% real, including the DST bug and its effect. “Devouring each other” is merely a figurative depiction of devs pointing fingers at each other, desperately trying to avoid the responsibility and blame but predominantly the deflated bonus that goes with “identifying the idiot who fucked up” as one executive succinctly put it.</blockquote><p><strong>“10x” vs. “1x”</strong></p><p>With respect to the “shit and fan” scenario, there is a clear difference between how “10x” software developers and their “1x” counterparts conduct themselves. “1x” tends to be <strong>reactive</strong>, while “10x” is typically more <strong>proactive</strong>, and therefore more likely to:</p><ol><li>Identify the gaps, rust, derelict components and potential landmines in the codebase as they begin to form. <strong>Before they’re a real threat.</strong></li><li>Have a good sense when things might blow up in the company’s face, and plan how to mitigate the risk.</li><li>Be unafraid to stop, <strong>use the proverbial wrecking ball</strong>, yank out the rotten, refactor the gaps, and “normalize/harmonize” the codebase when chunks of new work is thrown into the mix with old legacy components.</li><li>Believe in the “<a href="https://en.wikipedia.org/wiki/Broken_windows_theory">Broken Window Theory</a>”: The understanding that broken windows left unfixed in an urban setting tend to multiply and can send a good neighborhood down the path of becoming a slum, from which a come-back is nearly impossible.</li><li>Frown on the prospect of trusting luck, or tolerating fragile, “scary” or poorly understood parts of the codebase. They’re <strong>proactive</strong> to prevent catastrophe, taking action to make sure they never to find themselves being <strong>reactive </strong>in a pickle<strong>, </strong>scrambling for a fix under unfavorable emergency conditions. Had 10x software developers been cops, there wouldn’t be “no-go” zone anywhere within their precinct.</li></ol><p>“1x” developers tend to focus on “the plan forward”. They rarely look back or climb to 30,000 feet to take a good look at the codebase holistically. They will rarely stop to initiate a massive preventative surgery unless explicitly ordered to do so. As a result, they are typically taken by surprise, along with the rest of the company, when karma strikes. Hence <strong>reactive.</strong></p><p><strong>TL;DR</strong></p><ol><li>A software project is a constant construction project. It never stops unless it’s being sunsetted or killed off altogether.</li><li>Finished code can and will rot, not because it merely “gets old”, but because the context, demands and environment in which it runs constantly mutates. It’s not the spoon that bends, it’s everything else bending around it, to paraphrase another nerdy movie we all love.</li><li>Building new features on top of legacy infrastructure is likely to bring that infrastructure beyond its design limitations at some point, at which things will begin to break.</li><li>If “Peace Time” is an analogy to smooth sailing in production and “under fires” is to facing angry clients during a major production outage, surely you’d agree peace time is the preferred timing to diffuse any potentially lethal landmine. Doing so when you’re already under fire isn’t a pleasant experience and it might just kill you and your company (military pun intended).</li><li>Never hesitate to act once you’ve identified a codebase landmine. Wreck-ball, refactor, repair, and strive to keep the codebase harmonized as it moves through time, balancing old and new as seamlessly as possible and with elegance.</li><li>Strive to have an ongoing 30,000 feet grasp of the codebase. It will pay off in more than one way.</li><li>By being the champion of project cohesion and harmony, you will gain recognition and elevate your status. Being the one who actually knows “what’s going on” everywhere has many benefits. Never think of it as extra <strong>work</strong>. It’s extra <strong>opportunity</strong>.</li></ol><h4>PART 2 AVAILABLE HERE:</h4><ul><li><a href="https://medium.com/thestartuplifer/8-mental-anti-patterns-preventing-you-from-becoming-a-10x-software-developer-part-2-97b157b0ffac">8 Mental Anti-Patterns Preventing You From Becoming a 10X Software Developer — Part 2</a></li><li><a href="https://foundersinthecloud.beehiiv.com/p/9-ways-get-started-ai-today">9 ways to get started on AI today</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94f9478adf8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thestartuplifer/8-mental-anti-patterns-preventing-you-from-becoming-a-10x-software-developer-part-1-94f9478adf8e">8 Mental Anti-Patterns Preventing You From Becoming a “10X” Software Developer — Part 1</a> was originally published in <a href="https://medium.com/thestartuplifer">The Startup Lifer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>