<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Naveed Nadjmabadi on Medium]]></title>
        <description><![CDATA[Stories by Naveed Nadjmabadi on Medium]]></description>
        <link>https://medium.com/@theLoudBoy?source=rss-b16270aa2db8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*10KN08qylxF4tBLF.jpg</url>
            <title>Stories by Naveed Nadjmabadi on Medium</title>
            <link>https://medium.com/@theLoudBoy?source=rss-b16270aa2db8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:01:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@theLoudBoy/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Six lessons from my first six(ish) months of engineering management]]></title>
            <link>https://medium.com/building-carta/six-lessons-from-my-first-six-ish-months-of-engineering-management-29855b66d92f?source=rss-b16270aa2db8------2</link>
            <guid isPermaLink="false">https://medium.com/p/29855b66d92f</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Naveed Nadjmabadi]]></dc:creator>
            <pubDate>Fri, 25 Feb 2022 22:44:06 GMT</pubDate>
            <atom:updated>2022-05-20T18:55:46.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qIEqFqptlAB8uyUa" /></figure><p>I made a significant career change last March: I switched into engineering management. I’d been an individual contributor for seven years and needed a new challenge. I soon realized, though, that there was a significant gap between my assumptions for the role and reality. Here are some of the major lessons I’ve learned. I hope you’ll find them useful if you decide to transition into management.</p><h3>Lesson 1: Effective technical writing scales</h3><p>The best way for front-line managers to expand their influence and demonstrate impact is effective communication. At first, I imagined myself negotiating with my bosses to green-light engineering projects, but that has been rare. My most important communications have been <a href="https://www.inc.com/carmine-gallo/jeff-bezos-bans-powerpoint-in-meetings-his-replacement-is-brilliant.html">one-to-two-page documents</a> that helped my team and larger groups solve problems autonomously.</p><p>A clear, shared understanding of the problem empowers teams to maximize group intelligence and converge on an optimal solution quickly. Collective intelligence and <a href="https://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html">psychological safety</a> are two necessary prerequisites for developing <a href="https://rework.withgoogle.com/print/guides/5721312655835136/">high-performing teams</a>.</p><p>So, how do you write an effective document? I follow these principles:</p><ul><li>Know your audience</li><li>Communicate context through the 5 W’s (<strong>W</strong>ho, <strong>W</strong>hat, <strong>W</strong>here, <strong>W</strong>hen, <strong>W</strong>hy)</li><li>Keep it short and simple</li><li>Give yourself time to iterate</li></ul><h4>Know your audience</h4><p>Technical detail should be appropriate for the stakeholders and the problem. Start by asking yourself, “What is the purpose of this document?” Is it to inform a group of a technical decision, to convince a decision-maker, or to solicit advice from a peer? If you actively think about your audience and <em>their</em> interests, you’ll encourage more productive and focused discussions.</p><h4>Communicate context through the 5 W’s (Who, What, Where, When, Why)</h4><p>I answer the 5 W’s early in my documents because they often answer the reader’s most pressing questions. Determining who, what, where, when, and why (and “how,” when appropriate) summarizes even the most difficult problems — especially for stakeholders who may not be familiar with the details.</p><h4>Keep it short and simple</h4><p>No one wants to read a 15-page document when two pages would suffice … and they won’t. Most people scan a document when they first open it, calculating whether they should read the whole thing. I try to maximize my chances of success by making it as concise as possible. I’ve struggled to keep my documents succinct, but I found <a href="https://www.youtube.com/watch?v=JhEUw90C_lA">Brianne Hughes’ short talk</a> to be helpful as a framework for the writing process. When in doubt, follow the design principle: <a href="http://www.paulgraham.com/simply.html">Keep it simple, stupid</a>!</p><h4>Give yourself time to iterate</h4><p>Most documents I write start as a messy brain dump of all my thoughts. I then write in chunks and make <a href="https://medium.com/luminesce/how-to-do-more-without-burning-out-39eb6755636d">incremental improvements</a> as I flesh out ideas, organizing my main points into a clear structure. Along the way, I clarify my pitch in one-on-ones with teammates and in other informal settings, taking time to rewrite and polish according to their feedback. I make my writing process a deliberate endeavor and allocate adequate time for it.</p><h3>Lesson 2: The process is more valuable than the result</h3><p>The effort spent writing a good document is even more valuable than the document itself, because clear writing encourages clear thinking. The focus and critical reasoning I use to produce a concise document gives me insight that helps me and my team make better decisions.</p><p>Avoid relying on slide decks to summarize important information, as this shortcut leads to a superficial understanding of the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/0*-OQCKfQEomWF6j5f" /></figure><p><a href="https://twitter.com/paulg/status/1462073230932549634?s=21">https://twitter.com/paulg/status/1462073230932549634?s=21</a></p><h4>Corollary: Revisiting your roadmap often is the key to a consistent workload for your team</h4><p>Arguably, the most valuable document that managers can produce is the roadmap. A roadmap is crucial for tying together the <a href="https://debliu.substack.com/p/connecting-the-dots-from-vision-to?utm_campaign=post&amp;utm_medium=email&amp;utm_source=copy">higher level vision to the strategy</a> the team will take to get there. It’s the yardstick your team’s performance will be measured by.</p><p>“What is the team working on in the next six months? How will they hit their milestones? What is the impact of project X?” Your roadmap should answer these questions.</p><p>But plans change all the time as new information propagates across the organization. A new competitor has entered the market, a key business opportunity has been identified, or the company is changing its priorities — whatever the reason, often your original plan will be made obsolete.</p><p>Embrace change as your only constant. You’ll need to adapt by discarding parts of your roadmap, reprioritizing projects, and creating new line items. I plan ahead for multiple scenarios, preparing hypothetical decision trees and sequencing the projects the team will commit to if some potential event occurs.</p><p>A great manager once told me, “Our job is to have a backup plan for the backup plan for the original plan.” You don’t want to be scrambling at the last second; otherwise, you’ll negatively impact team morale and focus.</p><h3>Lesson 3: Be generous with your estimates.</h3><p>On the theme of roadmapping, one of the bigger mistakes I’ve made is not adding adequate buffer to project estimates.</p><p>Here is a painful example: Our team was about to reach a milestone in a complex engineering project. After we started the sprint, two unexpected things happened. First, a senior engineer on the team was tapped into an on-call support rotation, making them unavailable to work on sprint tasks. Second, the subject matter expert needed to take emergency leave. Other details had escaped my attention: The remaining engineers were new to the team, our division was having a full-day offsite, and some staff were taking planned vacations in subsequent sprints. The result? We missed our deadline.</p><p>While you could dismiss that as simply bad luck, the fault rested solely on my shoulders. Managers must prepare for the unexpected; by not accounting for worst-case scenarios, we weren’t meeting our commitments for the project and I jeopardized the credibility of my hard-working team.</p><p>It’s tempting to give optimistic estimates when presenting the roadmap to a wider audience — people will be excited by the promise of what’s to come. But if you can’t deliver on those commitments, you’ll simultaneously disappoint your bosses and burn out your team. Learn to “underpromise and over-deliver.”</p><p>How much buffer is necessary? It varies based on the team’s capabilities and your accuracy in accounting for unknowns in risk management, but I generally add about a 40–60% buffer until I’m confident that the team will hit the deadline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/0*pKnMnWLNFIg_qYqR" /><figcaption>the known-unknown matrix</figcaption></figure><h3>Lesson 4: Don’t “peanut-butter” your resources</h3><p>Be mindful of how many commitments your team is juggling. I was put in charge of a team of senior engineers — a luxury that few first-time managers have. Working with a highly skilled team makes it easy to deploy engineers to different problems and spread them thin.</p><p>Delegating multiple tasks to each engineer forces them to context-switch frequently, which we all know <a href="http://blog.ninlabs.com/2013/01/programmer-interrupted/">is <em>expensive</em></a>. The act of delegation assigns responsibility to that person. If they become overwhelmed by too many tasks, their sense of responsibility can make it hard for them to ask for help. No one wants to feel like they can’t do the work, so the engineers will try and slog through it in isolation, despite not being aware that they’re exhausted and slowing their pace.</p><p>As a manager, you’ll need to observe your team’s energy levels and calibrate the incoming workload accordingly. To break down silos, you’ll need to encourage your team to use their voice and have them drive what work can get done and how. The team needs to be able to discuss the scope of remaining work, delegate tasks to one another, pair program through thorny problems, and push back on you if the workload is unrealistic. Building a team that takes ownership and holds <em>each other</em> accountable keeps them cohesive and focused, providing a set of necessary checks and balances to prevent you from encumbering them with too many tasks.</p><h3>Lesson 5: Don’t delay in giving critical feedback</h3><p>This lesson was the hardest one for me to learn, because it forced me to realize that not every interaction or decision we make as managers will be a positive or a pleasant one.</p><p>I’m someone who doesn’t like to be micromanaged or nit-picked. As a manager, I externalized this by waiting until I saw enough instances of a problem or growth area that I could classify it as a pattern. Only then would I bring it up with a direct report. This was a mistake — although it wasn’t clear to me at first.</p><p>The longer you wait to discuss a specific action or event with your direct report, the harder it will be for them to draw a connection back to the problem and work on fixing it. It’s important to be compassionate and respectful because it’s a delicate matter, but we owe it to each other to be honest. Timely, meaningful feedback is necessary so we can course-correct and improve in our work.</p><p>Giving feedback about self-directed work can be tricky. When you give your team freedom in <em>how</em> they execute, you must establish particularly clear rubrics about <em>what</em> you want them to achieve. I’ve learned the best way to help people grow is to be upfront about my expectations, observe and assist while they execute, and discuss my observations in regularly scheduled one-on-ones. Some things can’t wait for a regular meeting, though: If some disruptive event occurs (a bad client call, or skipping steps to resolve a P1, for example), I quickly schedule a meeting to discuss and reflect, so I can help get us back on track.</p><p><em>Note:</em> I didn’t figure this out entirely by myself. Carta’s new manager accelerator program gave me a curated set of Udemy courses and access to a leadership coach via <a href="https://www.platohq.com/">PlatoHQ</a>, and paired me with other managers to practice conflict management and coaching. It was a fantastic experience that set me up for success, and it’s a major reason why I think Carta is a great company to work for.</p><h3>Lesson 6: Always be recruiting</h3><p>Early on, a senior manager offered advice that felt mysterious but proved to be prescient. When asked how best to grow a team, he taught us his mantra: “Always. Be. Recruiting.”</p><p>Setting up a recruiting pipeline is a significant undertaking, and can take anywhere from 10 to 40% of a manager’s time, depending on the company. Here’s my own breakdown of tasks to illustrate:</p><ul><li>Identifying skill gaps and the immediate / long-term needs of the team</li><li>Requesting and getting approval for headcount at the requisite level</li><li>Drafting, posting, and publicizing job descriptions</li><li><strong>Building a queue of candidates</strong> via sourcing and direct outreach</li><li>Training the team to calibrate and give fair interviews</li><li>Interviewing candidates via a phone screen</li><li>Working with recruiting to schedule candidates for the onsite, and handling delays</li><li>Final round onsite interviews</li><li>Preparing hiring packets and getting approvals from the hiring committee</li><li>Waiting for candidates to finish interviewing with other companies</li><li>Completing final negotiations with candidates and determining start dates</li><li>Building a 90-day onboarding plan and ironing out last minute wrinkles</li></ul><p>Given such a list, it’s imperative to start sourcing <strong>before</strong> you get the headcount approved. If you wait until you have the official headcount, you’ll waste valuable time in the initial stages of building the pipeline. Since the job market is so hot right now, it can take months to recruit a single high-potential candidate. It’s significantly easier to keep an active pipeline warm than it is to start from scratch every time.</p><p>In addition, understand that headcount allocations will change to reflect shifts in business priorities. In other words, if you don’t use it, <em>you lose it</em>. In my case, I took too long to get my pipeline started, and by the time I was ready to close on a few candidates, my headcount was re-allocated to a team which had greater need.</p><p>These are the biggest lessons I’ve learned in my tenure as a first-time engineering manager. I’m excited to grow and learn new lessons in the next six months, and build a great product with my team while I’m at it. If you’re interested in switching into management, <a href="https://boards.greenhouse.io/carta">check us out</a>!</p><p><em>Note: I’ve reposted this article to my personal blog. If you’ve enjoyed my writing, check out some of </em><a href="https://www.naveed.dev/category/interviews/"><em>my other posts</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29855b66d92f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-carta/six-lessons-from-my-first-six-ish-months-of-engineering-management-29855b66d92f">Six lessons from my first six(ish) months of engineering management</a> was originally published in <a href="https://medium.com/building-carta">Building Carta</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Summer Jam Challenge:]]></title>
            <link>https://medium.com/@theLoudBoy/summer-jam-challenge-86f459b4fa97?source=rss-b16270aa2db8------2</link>
            <guid isPermaLink="false">https://medium.com/p/86f459b4fa97</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Naveed Nadjmabadi]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 11:39:38 GMT</pubDate>
            <atom:updated>2019-04-24T11:50:53.585Z</atom:updated>
            <content:encoded><![CDATA[<p>A career dream i’ve had floating around for a while now has been to live as a digital nomad — working out of any city with just my laptop and traveling throughout the world. But how can I get there?</p><p>Most of the time, it seems that these remote jobs come through 1 of 3 channels:</p><ul><li>contractor / remote FTE for some enterprise corporation via some platform</li><li>Working as a consultant for hire, same as above, but with more flexibility to choose projects and increased burden of the management side</li><li>Working as a founder / principal engineer on a startup / business that makes enough money to support themselves</li></ul><p>While 1 is feasible, those jobs seem generally unsatisfying to me because the need for communication is high and the remote aspect makes it so contractors become “fire and forget” solutions to enterprise-y problems. Not interested.</p><p>Strategies 2 &amp; 3 sound much more appealing. They are similar but strategy 2 is more about building things other people want and loaning your expertise, whereas strategy 3 may be pursuing your own idea or a friends idea that may be successful. Regardless, both of these options give you a lot of ownership / agency in deciding what to do, at the expense of being more demanding than working a “regular” job.</p><p>Being successful in this endeavor is even more difficult — it would certainly be overwhelming for some people and would require you to be very good at a variety of skills (personal time management, shrewd business sense, engineering craftsmanship).</p><p>I think where I am today is a far cry of where I need to be in order for me to be able to engage in this type of work. While I work at a startup, I find that my pace and thought process reflects years of experience in enterprise programming systems. Many times, my own solutions and timelines to problems where significantly higher than that of the founders. It seemed to me that they were better at prioritizing “getting shit done”, even if that meant cutting a few corners here or there.</p><p>Part of me is interested in cultivating those skills for myself, if only to have a greater appreciation for the decisions that leaders need to make when *<strong>doing a thing</strong>*. I think by dedicated practice, i can distill lessons from these projects, and learn to be a faster, more effective, engineer. And whether or not i decide to do remote work, these skills will certainly help me be better at my day-to-day job.</p><p><em>So</em>:</p><p>This summer I plan to do 5 side projects. It can be a startup idea, a cool open source project, re-skinning my personal site, or really anything else that resembles something that would allow me to focus on improving time management, design oriented thinking (“continuous innovation” mindset), or the ability to churn code out faster and better. I’ll generally do a project, and then post my reflections and see if there are ways to improve. I’ve been successful in keeping myself committed to these projects because i have a good group of people who also have side projects, and we end up “jamming” most Saturdays together.</p><p>Wish me luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86f459b4fa97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Side project 1: Restaurant App(s)]]></title>
            <link>https://medium.com/series/side-project-1-restaurant-app-s-5ed949855afb?source=rss-b16270aa2db8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ed949855afb</guid>
            <dc:creator><![CDATA[Naveed Nadjmabadi]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 11:03:21 GMT</pubDate>
            <atom:updated>2019-04-24T11:03:21.186Z</atom:updated>
            <content:encoded><![CDATA[<p>AKA: “QR Codes, Morty!”</p><p>Motivation and Goals:</p><ul><li>Get experience with React / modern frontend architecture</li><li>Get a side project under the belt to improve skills as programmer, specifically going 0 to 1 and shipping an app</li><li>Test out a business idea i have had for a while that is similar to current industry apps (seamless, grubhub)</li></ul><p>Progress Made:</p><ul><li>Did preliminary research and scoping of project</li><li>Built a V1 of a customer facing ordering app</li><li>Built a V0 of a restaurant facing ordering app</li><li>Built a V1 api server leveraging existing node.js skills</li><li>Will have first round of user testing this weekend (Hopefully!)</li></ul><p>Feedback and lessons learned:</p><ul><li>Lots of thrashing (writing code without thinking thru idea because wanted to get something out — trying to break past analysis paralysis)</li><li>Could have benefitted from doing a mockup first, walk through all user interaction flows with chris, do a faster, lo-fi prototype. Also would be able to communicate that with zill, as that led to some goofy code / backtracking on api layer</li><li>Final deliverable is between a PoC and a MVP. Should have been closer to PoC because i made assumptions that may be expensive to fix if user testing proves that my design has a flaw</li><li>Its ok to refactor. Zills refactor taught me that if i am struggling to parse through a file because its doing a lot of things, it is worth the time to separate it out into different files.</li></ul><p>Final thoughts :</p><ul><li>Happy i got through one project to a point where i feel satisfied with what i have accomplished</li><li>Definitely think there is room for efficiency improvement with next side project</li><li>Need to spend more time learning react (doing a tutorial or two)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ed949855afb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Growth Stage Challenge #23: How to scale your code to sliding business concerns.]]></title>
            <link>https://medium.com/@theLoudBoy/growth-stage-company-challenge-23-how-to-scale-your-code-to-sliding-business-concerns-a35508ebf94f?source=rss-b16270aa2db8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a35508ebf94f</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Naveed Nadjmabadi]]></dc:creator>
            <pubDate>Mon, 30 May 2016 18:02:28 GMT</pubDate>
            <atom:updated>2016-06-12T12:47:37.190Z</atom:updated>
            <content:encoded><![CDATA[<p>One thing that people can agree on is that working at a startup is never boring. Stressful? Sure. Unorganized? Definitely. Efficient? Don’t get me started.</p><p>There comes a point, in my humble experience, where the organization is pressured to reach certain milestones that it is in no way prepared for. Especially in this climate of “<a href="http://m.economictimes.com/small-biz/startups/cockroach-vs-unicorn-investors-looking-for-startups-that-can-survive-anything/articleshow/51862823.cms">cockroach startups</a>”, the success of an investor backed company depends on its ability to adapt to shifting monetary concerns. 5 years ago, it was all about market share. Now, it’s about profitability.</p><p>Now, these kinds of shifts in strategic vision usually means that the organization will re-organize itself as fast as possible (Read: layoff people). It’s not necessarily a secret — I mean, Forbes wrote an <a href="http://www.forbes.com/sites/waldleventhal/2014/07/22/startup-phases-and-the-turning-of-the-team/#5a13181d40b0">article</a> on it.</p><p>The real challenge for the remaining engineers is to handle managing the existing systems in a sustainable fashion until a point where you can 1) find a new job, or 2) get more resources to continue building.</p><p>Now, full disclosure — I have not solved this problem. But in my attempts to try and stay sane while taking on 4 new projects, I found myself thumbing through the pages of “<em>The Laws Of Simplicity</em>” by John Maeda. (Side note: if you haven’t read this book, <a href="http://www.amazon.com/Laws-Simplicity-Design-Technology-Business/dp/0262134721">get it</a>! It’s a true gem for any aspiring tech person, no matter what your role).</p><p>Maeda makes a point to say that simplicity = sanity. He goes on to say:</p><blockquote>“The simplest way to reach simplicity is through thoughtful <strong>reduction</strong>”</blockquote><p>When standing back and having to take on a lot more codebases, the task is daunting. It cripples you with fear; you spend precious hours contemplating how trivial changes will impact this big scary system you never had to reason about.</p><p>The 🔑 to success here is to reduce the scope of the problem until it is one that you can feel confident in solving. In my case, it was determining which projects I could reasonably work on. Some things, like the production front end systems, will require my attention no matter what the situation. Others, like an internal app used to speed up processes, do not. It’s about picking and choosing your battles here; trying to take on all the bugs and feature requests is a Sisyphean task, and one that sets a bad precedent for your team. If your coworkers think you can solve all the bugs all the time, you will never get the peace of mind you need to effectively keep hacking at the backlog. It encourages reliance on certain individuals, unwittingly making them single points of failure for the rest of the organization. It’s also the quickest way to burnout-land for the poor bastard who agreed to make changes to foreign code while still doing his usual work.</p><p>All that being said, this is NOT an excuse to not do work. Whatever commitments you make, you have to be accountable to the team and the organization for. If you say you’ll do something, <strong>do it</strong>. It’s your responsibility to make sure you can manage other people’s expectations fairly, though.</p><p>Ok, so we limited the scope of our work to only the essential projects that we <em>need</em>. Now what?</p><p>Now, we take the opportunity to analyze our stack and see which libraries / code bases can be modified to fit a whole range of projects. Take, for example, our open source UI component library, <a href="https://github.com/jibeinc/juice">JUICE</a>. We built it for our front end system to the company’s largest product offering. I made a presentation with the other engineer who built this library and demoed it to the company. I spent weeks evangelizing it to other teams and discussing how they can use it for their upcoming projects. I boasted about it being Open Source Software, so people can increase their GitHub visibility if they contributed to it.</p><p>I did all of this because I knew that it would be easier to manage our entire system if we had a single UI component library to reason about, instead of many. The truth is, there will always be more codebases than people to manage them. So, we should put a lot of effort into generalizing the code so it can apply to as many projects as possible.</p><p>The benefits are numerous:</p><ol><li>New features and bug fixes will be made in one place, and applied across the board. This keeps things DRY, and ensures that all consumers get the benefit of the upgrade without manual intervention. It’s like Saas on a code level.</li><li>More hands make light work: if more people are involved, the amount of time myself and my team have to spend is reduced. This allows us to spend more time on the other codebases, ensuring that we can manage a wider “breadth” of projects with less people.</li></ol><p>It’s been about a month since I’ve started to set about these changes, and it’s been interesting to watch. The results are promising, albeit in its early stages. By late July, this “round” of projects will be finished, and I will re-examine the efficacy of the points I made in this article. Stay tuned, and wish me luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a35508ebf94f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quantum Computing in 35 seconds or less from a Software Engineer]]></title>
            <link>https://medium.com/@theLoudBoy/quantum-computing-in-35-seconds-or-less-from-a-software-engineer-1108187a5ef0?source=rss-b16270aa2db8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1108187a5ef0</guid>
            <category><![CDATA[quantum-computing]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[justin-trudeau]]></category>
            <dc:creator><![CDATA[Naveed Nadjmabadi]]></dc:creator>
            <pubDate>Sun, 01 May 2016 23:18:23 GMT</pubDate>
            <atom:updated>2018-03-18T20:29:23.853Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I have been seeing <a href="https://www.youtube.com/watch?v=Eak_ogYMprk">this video</a> making its rounds on my Facebook feed. The video shows Canadian Prime Minister Justin Trudeau explaining Quantum Computing to an audience of physicists. The video is highly entertaining, and Trudeau’s explanation was met with uproarious applause.</p><p>One of my Facebook friend’s then shared <a href="http://www.macleans.ca/society/science/trudeau-versus-the-experts-quantum-computing-in-35-seconds/">this post</a>, where 7 experts were challenged to explain quantum computing in the same amount of time as Justin Trudeau. This inspired me to try to do the same, for all my friends who aren’t computer scientists. Here goes:</p><ul><li>A bit is the smallest amount of information that a computer can handle. It can be a 0 or a 1.</li><li>8 bits strung together makes a byte. This is what computers work with most of the time. (e.g 00101011)</li><li>You have eight positions in a byte, and each position can be one of two values (0 or 1). The total number of different combinations you can arrange those 8 bits is 2⁸. For example, you can have 00000001, 01011010, 11111111.. Etc.</li><li>Now, with quantum computers, you can have 4 <strong>unique</strong> bits (represented as: 00, 11, 10, 01) as the <em>smallest</em> value a computer can understand.</li><li>So, by that logic, a byte, which is 8 bits, can now have 1 of 4 different values for each position, instead of 1 of 2. That means the total number of ways you can order those 8 bits is 4⁸ = 65,536.</li><li>With the exact same amount of space (1 byte), you can send exponentially more data!</li></ul><p>And that’s just 1 reason why quantum computing is cool. Think about it, your webpages take a while to load because it takes time to send all those 1&#39;s and 0&#39;s to your computer. Imagine when they only have to send 1/100 the data through the Internet to render the same page.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1108187a5ef0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>