<?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[WeSpire Engineering - Medium]]></title>
        <description><![CDATA[The thoughts, opinions, and ramblings within represent the best practices of the WeSpire Engineering team. - Medium]]></description>
        <link>https://medium.com/wespire-engineering?source=rss----f2de41dd89fc---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>WeSpire Engineering - Medium</title>
            <link>https://medium.com/wespire-engineering?source=rss----f2de41dd89fc---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:28:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/wespire-engineering" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[5 Organizational Theorems of WeSpire Engineering]]></title>
            <link>https://medium.com/wespire-engineering/5-organizational-theorems-of-wespire-engineering-d62d83c37632?source=rss----f2de41dd89fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/d62d83c37632</guid>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dan Widing]]></dc:creator>
            <pubDate>Thu, 13 Apr 2017 19:35:50 GMT</pubDate>
            <atom:updated>2017-04-13T19:33:29.647Z</atom:updated>
            <content:encoded><![CDATA[<h3>On the Shoulders of Giants</h3><p>If you haven’t read <a href="https://www.slideshare.net/reed2001/culture-1798664">Netflix’s culture SlideShare</a>, <a href="http://www.valvesoftware.com/company/Valve_Handbook_LowRes.pdf">Valve’s employee handbook</a>, or the <a href="http://oldblog.antirez.com/post/redis-manifesto.html">Redis Manifesto</a>, then stop reading this and go read them now. Ok, great to have you back.</p><p>You know why those are all amazing? They make a bold statement about what each of those organizations aim to accomplish and why. They describe cultures that are simultaneously appealing as an outsider and easy to assimilate into as a member. They each contain principles that elevate themselves above the banal corporate anti-culture, representing a radically different way of doing business. We want that.</p><h3>Theorems &gt; Values</h3><p>In part this is related to the values that each company holds. But corporate values are axioms — you don’t need to defend them with evidence in order to justify their adoption. And therefore, while choosing the right values can influence a company’s culture, we believe our organizational principles tell a much more accurate and interesting story about what makes our culture unique. They are kernels of hard-earned wisdom gleaned from practice, data, and academic theory, and subject to constant revision and improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RhHGManDPU-fdlo9." /></figure><p><a href="https://drive.google.com/file/d/0B1qTFUNJku6wN3B0VGNNazVCUWM/view">Source: WeSpire’s Mission, Vision, and Values</a></p><p>The following includes a collection of some of these theories, as a guide for others into how we make our decisions. And I’ve also provided sources for many items, to help illustrate where each of the concepts originated.</p><h3>1. <a href="http://oldblog.antirez.com/post/redis-manifesto.html">Invest in Developer Joy</a></h3><h4>Make Coding Enjoyable</h4><p>I’m humbly paraphrasing the Redis Manifesto here. Writing code can be really difficult work, so we try and offset that by striving to make it as enjoyable as possible.</p><ul><li><a href="http://www.economist.com/node/3307363">Minimize complexity whenever possible</a>. Code should tell a story, and when that story is clear and readable it can be a joy to read.</li><li>Invest in <a href="https://www.researchgate.net/publication/233706115_Employee_Development_and_Organizational_Performance_A_Review_of_Literature_and_Directions_for_Future_Research">employee development</a>. It will pay dividends even if you don’t see it immediately.</li><li>Doing good work breeds good work, and it builds a culture of <a href="https://en.wikipedia.org/wiki/Continual_improvement_process">continuous improvement</a>.</li></ul><h4>Use Natural Motivators</h4><p>Coincidentally at WeSpire, our job is to help our clients engage their employees. <a href="https://en.wikipedia.org/wiki/Self-determination_theory#Intrinsic_motivation">Intrinsic motivators</a> are powerful tools that we encourage our clients to use. Just as we build those tools into our product, we use them to make our own work rewarding.</p><p>Intrinsic motivators have been shown to produce greater returns and stronger outcomes than extrinsic. Some that we encourage are:</p><ul><li><strong>Autonomy</strong> — the ability to control your own work, day, and destiny</li><li><strong>Competence</strong> — the desire to feel that you have mastered or are mastering a skill</li><li><strong>Group Relatedness / Identity</strong> — the desire to be part of a group that you care about and that cares about you</li><li><strong>Greater Relatedness / Purpose</strong> — the desire to help the world in a greater way</li></ul><p>Extrinsic motivators are certainly less encouraged here, except for one particular type that strongly impacts the work we do as engineers.</p><ul><li><strong>Influence / Power </strong>— the desire to see your work affect others in a way that presents yourself positively</li></ul><p>It’s actually the third implicit motivation in <a href="https://en.wikipedia.org/wiki/Need_theory">need theory</a>, and as an organization you should never discount the individual need for recognition of impact.</p><h3>2. <a href="https://en.wikipedia.org/wiki/Decentralized_decision-making">Decentralize Authority</a></h3><p>Decentralizing authority is a fairly standard concept for any organization that has to make complex decisions. Once a problem grows large and complex, it becomes very difficult for one person to see the entire scope. The best way to combat that is to break things down with decentralization. Here are a few ways that we’ve been able to decentralize authority, and where we’ve taken the idea from:</p><h4>Empower Decision Makers</h4><ul><li>Decisions are made at the lowest level possible — <a href="https://www.amazon.com/dp/B004J4XGN6/"><em>Lean Startup</em></a></li><li>Projects, and the individuals assigned to them, have as much authority as possible to solve a problem that is as high-level as possible <em>— Lean startup</em></li></ul><h4>Keep Employees Informed</h4><ul><li>Leadership provides information about how and why a certain decisions are made, but they don’t control whether or not a decision is always made — <a href="https://www.slideshare.net/reed2001/culture-1798664"><em>Netflix Principles</em></a></li><li>Everyone has sufficient information to state what is valuable to the business and why — <em>Netflix Principles</em></li><li>Freedom of responsibility — everyone has the freedom to take on almost any additional responsibility if it helps the company — <em>Netflix principles</em></li></ul><h4>Use Policies Sparingly</h4><ul><li>Policies are made sparingly. Each one is a line of code. They are made only with experimentation, evidence, and reflection — <a href="https://hbr.org/1984/07/good-managers-dont-make-policy-decisions"><em>HBR</em></a></li><li>Remember that you get the behavior that you <a href="http://rady.ucsd.edu/faculty/directory/gneezy/pub/docs/jep_published.pdf">incentivize</a>. Bad incentives originating from bad policies can demotivate the incentivized behavior and incentives that aren’t fully inclusive will eliminate good behaviors. Sometimes you just have to make a leap of faith instead of relying on bad incentives.</li></ul><h3>3. Follow the <a href="https://en.wikipedia.org/wiki/Single_responsibility_principle">Single Responsibility</a> and <a href="https://en.wikipedia.org/wiki/Separation_of_concerns">Separation of Concerns</a> Principles</h3><p>These two concepts are found frequently in computer science. They help to make code clean, understandable, and flexible. But just as they apply in building computer systems they apply in building organizations.</p><ul><li>Whenever possible a responsibility should be delegated to a single person, or at least as few people as possible.</li><li>Individuals should have as few competing responsibilities as possible.</li><li>This applies even to time management. Limiting multitasking and providing a single responsibility for a long amount of time allows our engineers to <a href="http://www.paulgraham.com/makersschedule.html">focus</a>. With greater focus we can avoid very <a href="https://www.petrikainulainen.net/software-development/processes/the-cost-of-context-switching/">costly</a> <a href="http://blog.trello.com/why-context-switching-ruins-productivity">context switches</a>.</li></ul><h3>4. Optimize for Learning</h3><p>This is a concept we’ve borrowed heavily from lean methodology and the Lean Startup. We’re a startup and no startup has a crystal ball that tells which features customers will love most. Instead of optimizing to build features fast, we focus first on what <strong>should</strong> be built. Here’s how we do this:</p><h4>Evaluate Data Strategically</h4><ul><li>We use this rubric <em>(influenced by </em><a href="https://www.detecon.com/sites/default/files/21_DMR_Transformation_Interview_Kohl_Boas_Google_EN_11_2015.pdf"><em>Google HR</em></a><em>, </em><a href="https://hbr.org/2014/05/an-introduction-to-data-driven-decisions-for-managers-who-dont-like-math"><em>HBR</em></a><em>, and our company values)</em> to evaluate available information, before making a decision. Ordered from most to least valuable:</li></ul><ol><li>Data that supports well understood theory</li><li>Quantitative evidence</li><li>Qualitative evidence</li><li>Academic literature research</li><li>Theory</li><li>Internet researched support</li><li>Opinions</li></ol><ul><li>Questions are encouraged, but you should respect the time of others and yourself. If you ask a question is it worth the context switch for someone to answer? If you don’t ask the question are you wasting your time? Frame your questions so that you learn the answers to potential future questions you may have. — WeSpire values</li></ul><h4>Manage Risk</h4><ul><li>Have a plan, but expect that your plan will have <a href="https://www.pmi.org/learning/library/characterizing-unknown-unknowns-6077">inaccuracies and unknowns</a>.</li><li>Determine your riskiest assumption and make a plan to test it as quickly as possible — Lean Startup</li></ul><h4>Communicate Efficiently</h4><ul><li>Communicate all information multiple times. <a href="https://principlesoflearning.wordpress.com/dissertation/chapter-4-results/themes-identified/repetition/">Repetition is key to learning</a>, and we want recipients to retain as much of our message as possible.</li><li>Reflect on everything, both successes and failures. Celebrate success, and don’t blame people for failure. A culture of blame is an easy trap to fall into, so it’s important to remember that <a href="http://www.leanblog.org/2015/11/maybe-we-should-call-it-the-many-whys-instead-of-the-five-whys/">all individual failure is also group failure</a>. There are always many systems at play, and no one should just be expected to know better.</li><li>Everyone should have access information about what the entire company is working on, but only be responsible to know the precise details of their own projects. At WeSpire we keep sprint documents, plans, designs, and retrospectives easily available to the company, but only the engineer/product teams that own the sprint are expected to have total mastery of those documents. — <a href="https://open.buffer.com/why-transparency/">Buffer</a>, WeSpire values</li></ul><h3>5. Eliminate <a href="http://www.lean-manufacturing-japan.com/scm-terminology/bottleneck-constraint.html">Bottlenecks</a></h3><p>Here I borrow again from my experience in computer science and in particular performance engineering. However, finding and eliminating bottlenecks is a well understood concept in any process optimization.</p><h4>Avoid Blockers</h4><ul><li>Almost no one is entitled to slow down or block processes they don’t own. Our natural response as humans is to get involved whenever possible. But sometimes adding one more person to a process just ends up slowing information flow into a bottleneck.</li></ul><h4>Work Together</h4><ul><li>No one should have a monopoly on any skill or authority unless absolutely necessary. Skill redundancy is <a href="http://hiring.monster.ca/hr/hr-best-practices/workforce-management/workplace-diversity/the-importance-of-skill-redundancy-for-your-team-and-business.aspx">helpful on many levels</a>. On the WeSpire engineering team everyone is full stack and no one has a job title that grants exclusive access to any particular type of work. This way we’ll always have overlap for code review, for when people leave on vacations, and for when there is far more front end work than back end.</li><li>Simultaneously the group should still possess a diverse set of skills and perspectives. — <a href="https://insight.kellogg.northwestern.edu/article/better_decisions_through_diversity">Kellogg</a></li><li>Work is most easily managed sequentially, but all members must be able to manage some level of parallelism because no one should ever be 100% blocked.</li></ul><h4>Work Smarter</h4><ul><li>Find solutions that fit the <a href="https://en.wikipedia.org/wiki/Pareto_principle">80/20 rule</a> first then determine if you need to do more. For almost any kind of task you can usually get 80% of the goals completed with just 20% of the work. Deploy that 80% solution as soon as possible. Don’t let all that value be blocked while working towards achieving 100% perfection.</li></ul><p>* * *</p><p><strong>Thanks for reading! </strong>Did we miss anything? Do you do it differently on your engineering team? Let us know in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d62d83c37632" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wespire-engineering/5-organizational-theorems-of-wespire-engineering-d62d83c37632">5 Organizational Theorems of WeSpire Engineering</a> was originally published in <a href="https://medium.com/wespire-engineering">WeSpire Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to the WeSpire Engineering Blog! Why Am I Here?]]></title>
            <link>https://medium.com/wespire-engineering/welcome-to-the-wespire-engineering-blog-why-am-i-here-cb4d42baad5d?source=rss----f2de41dd89fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/cb4d42baad5d</guid>
            <dc:creator><![CDATA[Dan Widing]]></dc:creator>
            <pubDate>Mon, 22 Aug 2016 16:31:02 GMT</pubDate>
            <atom:updated>2016-08-22T16:31:02.539Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog has been a long time coming. It’s been an effort that’s started a few different times over the course WeSpire’s history. Like many things we knew we should do, if it wasn’t a primary goal it eventually fell by the wayside. We just never put together enough items to define <strong>what</strong> the engineering blog would be and we certainly never put enough force or reasoning behind <strong>why</strong> we wanted to blog at all.</p><h3>What Are We Writing About?</h3><p>I’m sure the content of this blog will eventually drift from its initial aims. Right now, though, I can at least guess what we will cover. Development culture is always a fun one. It’s inherently subjective so pretty much any written opinion can’t be totally disproved, which is a big plus for me. I’m also a nut about how things are built and trying to squeeze a little bit more efficiency into all the things. So I’ve got a number of posts planned around trying to build software better and faster. And then there’ll be plenty around solving specific issues that we couldn’t easily Google, Stack Overflow, or intuit to victory. Instead we actually had to work to solve them. Hopefully, we can save you some of the pain we’ve experienced.</p><p>Obsession with purpose and the “why” of things is going to be a recurring theme on this blog. It’s both a personal strength of mine in that I have a good knack for diving into discovering why something is done, but it’s a weakness in that I tend to remember the conclusion and not the reasoning. Welcome to the ride.</p><h3>Why am I Writing?</h3><p>I live to drive business value (I’ll leave it as an exercise to the reader to determine if that is sarcasm or genuine as I’m honestly uncertain). But, no, seriously, there actually is a bunch of value to writing this bloody thing.</p><p>Speaking strictly monetarily, if a single highly qualified engineer decides to apply for a role at WeSpire as a result of reading this blog, it’s probably already paid back the effort involved. It doesn’t take too many $30k recruiting fees to add up to tangible money that accountants care about. Intangibly, it’s so fricking hard to hire for engineers since their attention is being constantly pulled by nigh-infinite other offers and shiny things. Getting the best people interested in your company is itself a tremendous win that will inevitably pay dividends. So if you’re looking for a job, keep reading — I think you’ll be pretty impressed by the problems we solve and the stuff we think about.</p><p>For me and my team I’m most personally interested in getting better at building stuff. Writing about what you are doing requires self-examination of fundamental skills. Writing develops overall teaching methodology and mechanisms for teaching that specific topic. And writing down thoughts organizes them so that you can actually persuade people that you are doing the right thing. These blog posts will become artifacts of team culture. They can help to confirm culture and help steer newbies into the culture. Because if you can’t persuade others that you are doing the right thing culturally or practically, eventually any successes you had building will be swept away when other people don’t follow your direction.</p><p>And hey, what about giving back to the community? WeSpire is inherently a purpose driven company. We want to make the world a better place (<a href="https://www.youtube.com/watch?v=J-GVd_HLlps">Mike Judge be damned, I’m going full speed ahead with this cliché</a>). We’re hoping that you are in that together with us. Regardless, please, please feel free to start conversations with us about the things we are writing. Whatever it is that you are building, maybe we can help you and maybe you can help us. And who knows: maybe I can inspire someone out there to go and achieve my goals so that I don’t have to.</p><h3>That’s Great, Dan, but, Really, Why Should I Bother Reading?</h3><p>I think I’ve over-justified the reasoning on my side, but why are you here, dear reader? Well, maybe you’ve heard of us and you are looking to see if WeSpire has a role in which you are interested (shoot me an email: engineering-recruiting@wespire.com). Maybe you want to learn how to build a web startup. Or maybe you have a very specific problem to solve. Most likely, right now, you already work at WeSpire and you just want to hear me ramble for a while. Though, hopefully, I’ll start to get proportionally less of the last category. Let me know if you came here for a reason I didn’t expect.</p><p>So this is the promise. I’m going to write these things, for those reasons, with your potential audience types in mind. I’m going to assume you have at least some level of software experience. And I’m going to assume you have some level of patience since you’ve already read nearly 1000 words. I don’t really demand anything of you, though, I would love to have your thoughts if you are willing to share.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb4d42baad5d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wespire-engineering/welcome-to-the-wespire-engineering-blog-why-am-i-here-cb4d42baad5d">Welcome to the WeSpire Engineering Blog! Why Am I Here?</a> was originally published in <a href="https://medium.com/wespire-engineering">WeSpire Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>