<?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 Jeffrey Kern on Medium]]></title>
        <description><![CDATA[Stories by Jeffrey Kern on Medium]]></description>
        <link>https://medium.com/@differenceeng?source=rss-402567da8221------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*orjYE4MHQn-gsjGvMQAl3A.jpeg</url>
            <title>Stories by Jeffrey Kern on Medium</title>
            <link>https://medium.com/@differenceeng?source=rss-402567da8221------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:30:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@differenceeng/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[The Real Purpose of Agile Standups: Simplifying the Daily Check-In]]></title>
            <link>https://medium.com/@differenceeng/the-real-purpose-of-agile-standups-simplifying-the-daily-check-in-2d76960fcec9?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d76960fcec9</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Tue, 16 Apr 2024 20:29:03 GMT</pubDate>
            <atom:updated>2024-04-22T15:35:31.337Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wSE5P690giYQPmLP" /><figcaption>Photo by <a href="https://unsplash.com/@parabol?utm_source=medium&amp;utm_medium=referral">Parabol | The Agile Meeting Toolbox</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In recent months, questions about agile standups — or daily scrums — have surfaced repeatedly in various aspects of my professional life. From “What exactly are standups?” to “Should we use bots in our daily meetings?” and “What topics should be avoided during these sessions?” These inquiries have become increasingly common. Having practiced standups for years, I realized that it had been a long time since I critically analyzed this routine part of my day. Prompted by a surge of questions from my mentees, my curiosity was piqued to revisit what I had taken for granted as just another trivial daily task. As I often do when I delve into a topic anew, I reached out to my network for insights and perspectives. This time around, I’ve decided to share the collective wisdom and diverse approaches that came back, shedding new light on how we can all make the most of these essential, yet often underestimated, agile meetings. For a deeper dive into refining agile practices, see my article ‘Unraveling Agile: Tune Out the Noise, Get Things Done’ <a href="https://medium.com/@differenceeng/unraveling-agile-tune-out-the-noise-get-things-done-6f5a725ff231">here</a>.”</p><h4>Why Should You Care About Your Standup Role?</h4><p>Whether you’re a seasoned professional or just getting acquainted with agile methodologies, your contribution to daily standups matters immensely. The way you present your updates can set the tone for the entire team, propelling everyone towards more meaningful and efficient communication. If you’re tired of the same repetitive standup routine, a small change in how you communicate can spark a wave of improvement across your team — no formal directives needed. Others will see the value in your approach, adopt similar practices, and collectively, you’ll all rise with the tide, alleviating the drudgery of poorly run meetings. For quick tips and tools that can enhance your standup meetings, check out my ‘Agile Cheat Sheet’ <a href="https://medium.com/@differenceeng/agile-cheatsheet-a13463ca721d">here</a>.”</p><h4>Transform Your Agile Standups with These Direct Actions</h4><p>Agile standups should be succinct, impactful, and above all, effective. By focusing on specific, actionable improvements, you can immediately enhance the dynamics of these meetings:</p><h4>Focus Solely on Blockers and Immediate Priorities</h4><p>Narrow your updates to only blockers and critical tasks. If it’s not a hurdle or pivotal to today’s goals, it can wait. This focus encourages the team to ponder whether sharing something will actually aid in making the day more productive.</p><h4>Emphasize Preparation and Brevity</h4><p>Arrive at each standup knowing precisely what you need to share, and encourage your team to do the same. Each member should aim for brief updates of 30–60 seconds. This practice not only shortens the meeting but also sharpens the communication, making every second count.</p><h4>Shift from Passive Reports to Active Planning</h4><p>Transform your updates from passive recounts to active next steps. Instead of stating, “I worked on X,” shift to “Today, I’m completing X to advance to Y.” This keeps everyone focused on progress and next steps, rather than just a recount of past actions.</p><h4>Utilize a ‘Standup Board’ for Clarity</h4><p>If possible, use a physical or digital board to visually represent key update points. Simple columns for yesterday’s achievements, today’s goals, and current blockers can drastically streamline communication and comprehension.</p><h4>Tackle Blockers Immediately</h4><p>Promptly address any identified blockers by assigning them for immediate resolution post-standup or setting a specific time to strategize a solution. This proactive approach prevents productivity stalls.</p><h4>Key Missteps to Avoid</h4><p>Effective agile standups hinge on concise and relevant communication. To ensure your standups contribute positively to team dynamics and productivity, be mindful of these specific pitfalls:</p><p><strong>Technical Showboating:</strong> Avoid using standups as a platform to demonstrate technical skills or secure your job security. Speak in clear, concise language that all team members can understand, focusing on essential updates rather than technical depth.</p><p><strong>Unnecessary Updates:</strong> If you have no progress or relevant information to share, it’s acceptable to say, “No updates.” This approach keeps the standup streamlined and gives space for more pressing issues.</p><p><strong>Overthinking Your Update: </strong>Remember, the details of your update are less important than you might assume. Your team’s goal is to gauge progress, not dissect every task. Keep your updates brief and relevant.</p><p><strong>Stick to KISS:</strong> Adhere to the “Keep It Simple, Stupid” principle. A sticky note on your monitor with “KISS” can serve as a constant reminder to keep your communication straightforward and focused.</p><p>These targeted practices will help you avoid common standup blunders, ensuring that your updates are efficient and directly contribute to the team’s progress and cohesion.</p><h4>Small Changes, Big Impact</h4><p>These simple yet focused modifications can transform your standups into a powerful tool for daily efficiency. Embrace these changes and witness how your agile routine evolves into a more effective and engaging process.</p><p>Incorporating insights from your network into your article on agile standups provides a comprehensive view that enriches the content with diverse perspectives. Here’s a refined introduction to the Q&amp;A section that sets the stage for sharing these varied insights:</p><h4>Diverse Insights: Standup Strategies from Seasoned Professionals</h4><p>Having delved into the mechanics and common pitfalls of agile standups, I reached out to my network for further enlightenment. These professionals, each with over a decade of experience in our industry, offer a variety of viewpoints on optimizing daily scrums. It’s important to note that while their approaches may differ, each perspective is valid and demonstrates the flexibility and adaptability of agile methodologies.</p><p>In wrapping up this discussion, we dive into real-world insights directly from the professionals in my network. Their answers highlight distinct approaches and common obstacles encountered during standup meetings.</p><h4>Question 1: Maximizing the Impact of Standup Updates</h4><p><a href="https://www.linkedin.com/in/branden-adams-73696212a/">Branden Adams — Systems Engineer<br></a>“For standup, I think the most effective standups I’ve been part of are the ones that we only use the time to get unblocked. This is heavily dependent on a successful sprint refinement ceremonies. All the status update standups are a pain in the arse. If you wanna know the status of a ticket, look in Jira.”</p><p><a href="https://www.linkedin.com/in/sjcarlson/">Stephen Carlson — Senior Product Owner | Design Operations<br></a>1) “Keep it tactical: stand ups provide an opportunity to refocus their task-based efforts in the context of their team, rather than thinking solely in terms of individual contribution.” <br>2) “Avoid high-level or strategic talk which tends to spiral into conversations about how things could be in the future rather than what’s pertinent to the now and what needs to be delivered in short order.”</p><p><a href="https://www.linkedin.com/in/karli-niemann-227786118/">Karli — Software Engineer</a><br>“Stand-ups are vital for ensuring our team functions effectively, much like a crew navigating a spaceship. Each session should serve as a platform for sharing critical updates about our day-to-day operations. This includes any blockers that are impeding progress, as well as insights that might impact other teams or contributors. By treating these meetings as an opportunity to deliver concise status reports, we keep our ‘spaceship’ on course and prevent small issues from becoming larger problems.”</p><h4>Question 2: What to Avoid in Standups</h4><p><a href="https://www.linkedin.com/in/douglas-jarnot-3ba87334/">Doug Jarnot — Director — Product Transformation &amp; Agile Delivery: <br></a>“Don’t do status updates. Focus on what is relevant. Make sure to solve your problems as they arise. Don’t spend an hour on a [redacted] saying it’s a standup. Ensure everyone participates effectively. If you’re updating on work that doesn’t align with current priorities, it’s worth reassessing the relevance of that work.</p><p><a href="https://www.linkedin.com/in/jacob-fulton-dev/">Jake Fulton — Senior Software Engineer<br></a>“The short answer is to always make it short and sweet. It’s named standup in order to make you give a quick update since standing for long periods is uncomfortable. Nobody likes a bloated standup, and it will mean less people giving their full attention.”</p><p><a href="https://www.linkedin.com/in/karli-niemann-227786118/">Karli — Software Engineer<br></a>“Over sharing with minor details can dilute the information that should be shared with others and can inadvertently convince members of the team that stand-ups don’t bring value. Keeping things short and simple is what not only retains attention for the team but brings only the highlights that others should be in the loop on.”</p><p><a href="https://www.linkedin.com/in/ryansjohnson/">Ryan Johnson — Vice President Of Software Engineering: <br></a>“I f***ing hate standups.”</p><p><a href="https://www.linkedin.com/in/samjjohnson/">Sam Johnson — Director of Performance Marketing</a>:<br>If an item takes longer than anticipated, push it to a separate meeting. Make sure everyone participates in some way. Don’t over focus time on one issue — use it as a diagnostic to find what needs more time then dedicate appropriately.</p><p><a href="https://www.linkedin.com/in/sjcarlson/">Stephen Carlson — Senior Product Owner | Design Operations</a>:<br>Basically, avoid going down rabbit holes. Extension of 1: allows teams to uncover blockers and figure out how to resolve in the context of the tasks at hand.</p><p>Many Others:<br>“I really don’t want to think about standups.”</p><p><strong>Further Reading:<br></strong>For those looking to dive deeper into effective agile practices, Mountain Goat Software offers a wealth of resources that can further enhance your understanding and execution of agile methodologies. Explore their extensive collection <a href="https://www.mountaingoatsoftware.com/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d76960fcec9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flavor Meets Function- How Sweet Lou’s Food Truck Cooked Up Success with Tech Innovation]]></title>
            <link>https://medium.com/@differenceeng/flavor-meets-function-how-sweet-lous-food-truck-cooked-up-success-with-tech-innovation-1d4fc551522c?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d4fc551522c</guid>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Mon, 20 Nov 2023 22:27:27 GMT</pubDate>
            <atom:updated>2023-11-20T22:27:27.025Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l5lhCqVmkNCT1A_QqVnt3g.jpeg" /></figure><ul><li><strong>Culinary Innovation Meets Operational Challenge —</strong> Sweet Lou’s, a unique food truck, faced challenges with limited space and efficiency, impacting their high-demand service.</li><li><strong>Strategic Tech Solution —</strong> In partnership with Difference Engine, Sweet Lou’s implemented a QR-based ordering system, seamlessly integrating it with existing operations and utilizing AI for easy menu updates.</li><li><strong>Enhanced Operational Efficiency — </strong>The innovative solution, managed entirely via a smartphone, significantly reduced operational costs and streamlined customer service.</li><li><strong>Impact of Fractional CTO Partnership — </strong>This collaboration highlights the effectiveness of tailored tech solutions in addressing specific business challenges, demonstrating the value of a Fractional CTO in dynamic business environments.</li></ul><p>In the whirlwind world of food trucks, where quick adaptations and culinary flair are key, technological advancements can be a real game changer. Take <a href="https://www.sweetlousmeats.com/">Sweet Lou’s</a>, for example — more than just a food truck, they’re a culinary sensation on wheels. Their standout dish? A burger that’s nothing short of a flavor explosion, featuring a blend of meats ground by Lou herself on the day it’s served. Top this off with a decadent red onion and bacon jam, marrownaise, and American cheese fondue and you’ve got a dish that screams commitment to freshness and quality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xyws3fO8lTVb9KeIGNPiTQ.jpeg" /><figcaption>Credit: <a href="https://www.instagram.com/sweetlousmeats/">https://www.instagram.com/sweetlousmeats/</a></figcaption></figure><h4>The Problem</h4><p>The short of the issue lay in the limited space inside the truck. During peak periods, Sweet Lou’s had to allocate one person solely to handle the register, even at prepaid events. This setup not only increased operational costs but also decreased their output, a critical limitation given the confined workspace of their food truck.</p><p>This is where our partnership as a Fractional CTO through Difference Engine came into play. We stepped in to devise a strategic, solution that was in perfect sync with Sweet Lou’s unique business model and their need to maximize space and efficiency.</p><h4><strong>Strategic Tech Solution</strong></h4><p>When we first floated the idea of a QR-based ordering system, Sweet Lou’s team was no stranger to the concept. They’d toyed with it before but ran into a bunch of roadblocks. The big questions were about how it would fit into the fast-moving rhythm of their truck and whether it could genuinely make things more efficient, not just add another layer of complexity.</p><p>At Difference Engine, we tackled these concerns head-on. Instead of brushing them aside, we took each ‘limitation’ they mentioned and flipped it into a project requirement. This approach underscored an important point: Sweet Lou’s crew knew their business inside out. They just weren’t as up to speed on the tech side of things, which is totally understandable. They’re culinary geniuses, not tech gurus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ozvHgFILr7HQoqoe2S3CPA.jpeg" /><figcaption>Pickled blueberry and cotija crema brat: <a href="https://www.instagram.com/p/CueYEhFO5Co/">https://www.instagram.com/p/CueYEhFO5Co/</a></figcaption></figure><p>So, we went back to the drawing board together, exploring all sorts of tech possibilities that could align with the unique hustle of a food truck. After turning over every stone, we circled back to the QR code idea, but this time with a strategy to overcome the initial hurdles. The final solution was tailored to Sweet Lou’s needs — straightforward, effective, and not a burden on their busy workflow.</p><h4><strong>Enhanced Operational Efficiency</strong></h4><p>This project was a classic case of culinary mastery meeting tech innovation. Sweet Lou’s rocked their kitchen, and they needed someone to translate their operational needs into a viable tech solution. That’s where we came in.</p><p>In addressing Sweet Lou’s challenges, our approach was to integrate technology seamlessly into their existing operations. We harnessed Square’s online ordering and ticketing systems, intertwining these with their current website and several other key integrations. These allowed Sweet Lou’s to utilize a single QR code effectively.</p><p>The real magic happened with the menu updates. Each day, after crafting their rotating menu, the team at Sweet Lou’s would simply take a photo of their handwritten menu. Utilizing AI services, this image was then converted into text, automatically updating a new version of their website with the day’s offerings. Remarkably, all of this occurred in seconds and was managed entirely from a smartphone. The need for a laptop was eliminated, as was the repetitive task of digitally re-entering the menu. This solution not only saved time and reduced operational stress but also ensured that Sweet Lou’s could maintain their dynamic, ever-changing menu with ease and efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OcZzVevASYI_Ke2_199wJw.jpeg" /><figcaption>Chili Cheese Dog — <a href="https://www.instagram.com/p/CgHetrNO5Xn/">https://www.instagram.com/p/CgHetrNO5Xn/</a></figcaption></figure><h4>Tech That Empowers Business</h4><p>Sweet Lou’s adoption of the QR-based ordering system was a strategic decision, tailored to enhance efficiency without compromising the personal touch they’re known for. They currently employ the QR menus primarily at events where increased efficiency is crucial, maintaining the personal interaction of taking orders the old-fashioned way whenever possible.</p><p>This flexible approach to technology underscores that Sweet Lou’s is in command — they steer the ship, not their tech. Depending on the nature of the event, they can switch between QR only ordering, a combination of online and in-person ordering, or in-person only ordering. This adaptability allows them to tailor their service to each event’s specific needs, ensuring that their technology enhances the customer experience rather than dictating it.</p><h4>The Bottom Line</h4><p>Working with dedicated professionals like Lou and Tim at Sweet Lou’s is what makes our job at Difference Engine so rewarding. They have a deep understanding of their business and possess innovative ideas about what they wish to achieve, but often lack the time or resources to fully explore or implement these solutions. In the midst of an overwhelming flood of marketing and tech trends, some of which promise unrealistic returns, our role is to cut through the noise.</p><p>Having a partner like us, who steps into a Fractional CTO role, means more than just bringing tech expertise to the table. It’s about genuinely understanding the vision and needs of business owners like Lou and Tim, and working hand-in-hand to transform their ideas into practical, effective tech solutions. This collaboration isn’t just about tech implementation, it’s about building a relationship based on trust, where we’re equally invested in seeing their business thrive in the most efficient and innovative ways possible.</p><p>Big shout-out to Lou and Tim for teaming up with us and for all the amazing food. If you ever spot Sweet Lou’s truck, do yourself a favor and stop by. Our team swears by the burger, but honestly, everything they whip up is a hit. You really can’t go wrong with anything they serve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ai1sdJ6Sxv3kIMWt39WPSQ.jpeg" /><figcaption>pigs in a blanket- <a href="https://www.instagram.com/p/CiFiqIiu9r8/">https://www.instagram.com/p/CiFiqIiu9r8/</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d4fc551522c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile —  Cheatsheet]]></title>
            <link>https://medium.com/@differenceeng/agile-cheatsheet-a13463ca721d?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/a13463ca721d</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Mon, 18 Sep 2023 19:23:49 GMT</pubDate>
            <atom:updated>2023-09-18T19:27:37.974Z</atom:updated>
            <content:encoded><![CDATA[<h3>Agile Cheatsheet</h3><p>See something missing or think it could be phrased better? Please leave a comment or connect 😊</p><p><a href="https://medium.com/@differenceeng/unraveling-agile-tune-out-the-noise-get-things-done-6f5a725ff231"><strong>Agile</strong></a><br>I cover this in detail in another<a href="https://medium.com/@differenceeng/unraveling-agile-tune-out-the-noise-get-things-done-6f5a725ff231"> post</a>.</p><p><strong>Backlog</strong><br>What it is: A prioritized list of work items, such as features, user stories, and tasks, that need to be completed by the development team.<br>What it isn’t: A fixed set of requirements; the backlog evolves as priorities change.</p><p><strong>Burndown Chart<br></strong>What it is: A visual representation of remaining work over time, often used in Agile to track progress and predict when work will be completed.<br>What it isn’t: A detailed task list; it provides an overview of progress.</p><p><strong>Cross-Functional Teams<br></strong>What they are: Teams composed of members with diverse skills and expertise, capable of completing all aspects of a project within a sprint.<br>What they aren’t: Siloed or specialized teams; cross-functional teams collaborate to achieve goals.</p><p><strong>Daily Standup<br></strong>What it is: A brief daily meeting where team members discuss progress, plan their work for the day, and identify any impediments.<br>What it isn’t: A long status report; it focuses on quick updates and coordination.</p><p><strong>Definition of Done<br></strong>What it is: A shared set of criteria that must be met for a user story or task to be considered completed.<br>What it isn’t: A rigid checklist; it varies based on the work.</p><p><strong>DevOps</strong><br>What it is: A set of practices that combines development (Dev) and IT operations (Ops) to enhance collaboration, automation, and the delivery of software.<br>What it isn’t: Limited to development or operations alone; it bridges both areas.</p><p><strong>Epic</strong><br>What it is: A large body of work that cannot be completed in a single sprint and is broken down into smaller user stories or tasks.<br>What it isn’t: A detailed user story; epics represent higher-level themes or initiatives.</p><p><strong>Estimation<br></strong>What it is: The process of assigning relative sizes or effort points to user stories or tasks to determine their complexity.<br>What it isn’t: Precise predictions; it’s a relative gauge, not an absolute measure.</p><p><strong>Feature</strong><br>What it is: A distinct piece of functionality that provides value to the end user or customer.<br>What it isn’t: A technical component or implementation detail.</p><p><strong>Increment</strong><br>What it is: A potentially shippable piece of work, often a user story, completed within a sprint.<br>What it isn’t: An incomplete or non-functional deliverable.</p><p><strong>Inspection and Adaptation<br></strong>What they are: Core principles of Agile, emphasizing regular assessment of progress and making adjustments as needed.<br>What they aren’t: A one-time planning and execution process; they occur iteratively.</p><p><strong>Iteration<br></strong>What it is: A repeating cycle of work in Agile, typically lasting 2–4 weeks, during which the team completes a set of tasks.<br>What it isn’t: A fixed or unchangeable period; iterations allow for flexibility.</p><p><strong>Kanban<br></strong>What it is: A visual workflow management method that emphasizes continuous flow and limiting work in progress (WIP).<br>What it isn’t: A time-bound approach with predefined sprint lengths.</p><p>Lead Time<br>What it is: The time it takes for a task or user story to move from the initial request to completion.<br>What it isn’t: The same as cycle time; it includes request processing time.</p><p><strong>MVP (Minimum Viable Product)<br></strong>What it is: The smallest version of a product that can be released to gather feedback and validate assumptions.<br>What it isn’t: A complete or fully-featured product.</p><p><strong>Pair Programming<br></strong>What it is: A development practice where two programmers work together at one workstation, collaboratively writing code and reviewing each other’s work.<br>What it isn’t: Working in isolation; it emphasizes collaboration and knowledge sharing.</p><p><strong>Product Owner<br></strong>What they are: The individual responsible for defining and prioritizing the product backlog and representing customer interests.<br>What they aren’t: A project manager; their focus is on defining “what” and not micromanaging “how.”</p><p><strong>Product Backlog<br></strong>What it is: A prioritized list of features, user stories, and tasks that need to be addressed in a product.<br>What it isn’t: A fixed project plan; it evolves with changing priorities.</p><p><strong>Quality Assurance (QA)<br></strong>What it is: A practice of ensuring the quality of software through testing and validation.<br>What it isn’t: Solely the responsibility of a separate QA team; it involves the entire development team.</p><p><strong>Release Planning<br></strong>What it is: The process of planning and scheduling the release of product increments to customers, considering feature prioritization and dependencies.<br>What it isn’t: Sprint planning; it’s a broader, strategic activity.</p><p><strong>Retrospective<br></strong>What it is: A meeting held at the end of a sprint where the team reflects on their processes and collaboration, identifying areas for improvement.<br>What it isn’t: A blame session; it focuses on constructive feedback and continuous improvement.</p><p><strong>Sprint</strong><br>What it is: A time-boxed development iteration, typically lasting 2–4 weeks, during which a team completes a set of user stories or tasks.<br>What it isn’t: An arbitrary deadline; it’s focused on delivering valuable increments.</p><p><strong>Scrum</strong><br>What it is: An Agile framework that organizes work into time-bound iterations called sprints, emphasizing roles, ceremonies, and incremental progress.<br>What it isn’t: A strict project management methodology; it values collaboration and adaptability.</p><p><strong>Scrum Master<br></strong>What they are: A role in Scrum responsible for coaching the team, removing impediments, and ensuring adherence to Scrum practices.<br>What they aren’t: A manager or team lead; their role is facilitative.</p><p><strong>Sprint Goal<br></strong>What it is: A short, concise statement that describes the purpose or objective of a sprint.<br>What it isn’t: A detailed task list; it provides high-level direction.</p><p><strong>Stakeholder<br></strong>What they are: Individuals or groups with an interest in the project or product, including customers, users, and sponsors.<br>What they aren’t: Direct members of the development team; they provide external perspectives.</p><p><strong>Stand-up<br></strong>What it is: A brief daily meeting where team members discuss progress, plan their work for the day, and identify impediments.<br>What it isn’t: A lengthy discussion or problem-solving session; it’s focused and time-bound.</p><p><strong>Story Points<br></strong>What they are: A relative estimation technique used to gauge complexity and effort for user stories or tasks, aiding in prioritization and planning.<br>What they aren’t: Fixed time units; they represent effort, not time.</p><p><strong>User Story<br></strong>What it is: A brief description of a feature or functionality from an end user’s perspective, often used to define requirements.<br>What it isn’t: A technical specification; it focuses on the “what” and “why.”</p><p><strong>Velocity</strong><br>What it is: A measure of a team’s capacity and historical performance, often expressed as the average number of story points completed per sprint.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a13463ca721d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unraveling Agile — Tune Out the Noise, Get Things Done]]></title>
            <link>https://medium.com/@differenceeng/unraveling-agile-tune-out-the-noise-get-things-done-6f5a725ff231?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f5a725ff231</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[managment]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Mon, 18 Sep 2023 19:05:24 GMT</pubDate>
            <atom:updated>2023-09-18T19:41:42.932Z</atom:updated>
            <content:encoded><![CDATA[<h3>Unraveling Agile — Tune Out the Noise, Get Things Done</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1SRe2FExGG1wkBco" /><figcaption>Photo by <a href="https://unsplash.com/@patrickperkins?utm_source=medium&amp;utm_medium=referral">Patrick Perkins</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I often find myself on the receiving end of statements and questions about Agile. “Can Agile work with timelines?”, “We’re not doing Agile the right way”, or the age-old “Agile is superior to Waterfall”. With over a decade in the industry, having waded through countless workshops, mentorships, and consultations, and having instructed on Agile and project management, I’ve seen and heard a truckload of misinformation. The space is rife with trends, fads, and sales pitches dressed as wisdom, each claiming to know the “true” essence of Agile. So, I felt the need to distill this down further, to three immutable practices. But first, let’s debunk some myths and clarify what Agile is not. For those wanting a deep dive into the myriad tools and concepts, I’ve included a link to a <a href="https://medium.com/@differenceeng/agile-cheatsheet-a13463ca721d">cheat sheet</a> for further reading.</p><p>Agile is not about Jira, Trello, Kanban, or sprints. It doesn’t revolve around story points, timelines, or standups. All these are just sophistication layered on top of the core principles. They’re tools designed to cater to the unique needs of individual organizations. For someone to say you’re doing Agile “wrong” because you’re using or not using a specific tool is as absurd as claiming someone isn’t a genuine carpenter because they wield a hammer. Such declarations, even with added context, are empty of substance.</p><p>This article aims to provide a no-BS definition of Agile. Like any industry, the deeper you delve, the more nuances you uncover. But for the sake of clarity, there are three immutable properties that define Agile. Without these, you simply don’t have an Agile team.</p><p>Straying from these core tenets, Agile devolves into a smokescreen for managerial shortcomings. It lets flawed leadership hide behind the veil of “process”, often leading to micromanagement and confusion. To then declare, “This is how we do Agile,” is like stating, “This is how we play soccer without a ball.”</p><h4>1. Empowered Contributors</h4><p>Team members in Agile settings are empowered to make decisions and act without always seeking management approval, allowing for swifter, more efficient outcomes.</p><h4>2. Parallel Work Streams</h4><p>Agile endorses simultaneous task handling, preventing delays from becoming cascading bottlenecks and promoting proactive adjustments based on real-time insights.</p><h4>3. Minimal Compartmentalization</h4><p>Agile teams are comprehensive, housing all the expertise required to drive results. Members move beyond traditional role confines, concentrating not on job titles but on the most effective way to complete the task at hand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f5a725ff231" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Common Analytics Tools]]></title>
            <link>https://medium.com/@differenceeng/common-analytics-tools-cc131e3ac598?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc131e3ac598</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Wed, 16 Aug 2023 18:28:37 GMT</pubDate>
            <atom:updated>2023-08-16T18:28:37.030Z</atom:updated>
            <content:encoded><![CDATA[<h4>Here are some common analytics tools I’ve used over the years, organized by the product and marketing sides of organizations’ tech stacks.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j_rfmQ612aPWMi-x" /><figcaption>Photo by <a href="https://unsplash.com/@alinnnaaaa?utm_source=medium&amp;utm_medium=referral">Alina Grubnyak</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>📱 Product</h3><p>🎯 Goal: Maximize product revenue by refining user experience.</p><ol><li>Product Usage and Engagement:</li></ol><ul><li><a href="https://mixpanel.com/">Mixpanel</a> or <a href="https://amplitude.com/">Amplitude</a>: Understand feature usage.</li></ul><p>2. User Feedback &amp; Surveys:</p><ul><li><a href="https://www.typeform.com/">Typeform</a>: Forms that can be embedded into your product experience.</li></ul><p>3. Error &amp; Performance Monitoring:</p><ul><li><a href="https://logrocket.com/">LogRocket</a>: Ensure a smooth user experience.</li><li><a href="https://sentry.io/">Sentry</a> or <a href="https://rollbar.com/">Rollbar</a>: Fix issues fast.</li></ul><p>4. Feature Flagging &amp; A/B Testing:</p><ul><li><a href="https://www.optimizely.com/">Optimizely</a> or <a href="https://launchdarkly.com/">LaunchDarkly</a>: Test and launch profitable features.</li></ul><p>5. User Interaction &amp; Tagging:</p><ul><li><a href="https://tagmanager.google.com/">Google Tag Manager</a>: Track revenue-driving interactions.</li></ul><p>6. User Retention &amp; Churn Analysis:</p><ul><li><a href="https://mixpanel.com/">Mixpanel</a>: Improve retention.</li></ul><p>7. Customer Support and CRM Integration:</p><ul><li><a href="https://www.zendesk.com/">Zendesk</a>: Keep customers happy for more sales.</li></ul><h3>🌐 Marketing Site</h3><p>🎯 Goal: Increase website profitability by understanding visitor behavior</p><ol><li>Traffic and User Behavior:</li></ol><ul><li><a href="https://analytics.google.com/">Google Analytics</a>: Know where your traffic comes from and target high-converting sources.</li><li><a href="https://search.google.com/search-console/">Google Search Console</a>: Ensure you’re visible on Google.</li></ul><p>2. Conversion Tracking:</p><ul><li><a href="https://analytics.google.com/">Goal Tracking in Google Analytics</a>: Understand your conversion rate.</li><li><a href="https://ads.google.com/">Google Ads Conversion Tracking</a>: Optimize ad spend.</li></ul><p>3. User Experience:</p><ul><li><a href="https://www.hotjar.com/">Hotjar</a> or <a href="https://www.crazyegg.com/">Crazy Egg</a>: Optimize website layout.</li><li><a href="https://logrocket.com/">LogRocket</a>: Identify and fix site issues.</li></ul><p>4. SEO Tools:</p><ul><li><a href="https://moz.com/">Moz</a>, <a href="https://ahrefs.com/">Ahrefs</a>, or <a href="https://www.semrush.com/">SEMrush</a>: Improve search ranking.</li></ul><p>5. Social Media Tracking:</p><ul><li><a href="https://buffer.com/">Buffer</a> or <a href="https://hootsuite.com/">Hootsuite</a>: Optimize social campaigns.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc131e3ac598" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quantifying Value in Organizational Decisions]]></title>
            <link>https://medium.com/@differenceeng/quantifying-value-in-every-organizational-decision-88c4acd38d34?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/88c4acd38d34</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Wed, 16 Aug 2023 18:09:49 GMT</pubDate>
            <atom:updated>2023-09-06T20:11:21.221Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qdp8Rv_4EuogukSB" /><figcaption>Photo by <a href="https://unsplash.com/@pablomanzoni?utm_source=medium&amp;utm_medium=referral">Pablo Manzoni</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Picture this a pristine, untouched lake. That’s your digital analytics. Clear. Reflective. A perfect snapshot of everything underneath.</p><p>Now, think of every decision you make in business as a raindrop. A feature release? Drop. Social media post? Another drop. Google Ad? Yet another. And those ripples, spreading across the water? That’s the business impact. Sometimes, they mingle, overlap, even interfere with each other.</p><p>On any given day, in companies all over, it’s pouring. And our tranquil lake? It’s getting harder and harder to read. Waves of content marketing, showers of updates, a deluge of decisions.</p><blockquote>But what if… we could do things a bit differently?</blockquote><p>Imagine, gathering each raindrop — every decision, every feature release, every ad — understanding it, and then… releasing it in a way that ensures each ripple is purposeful, measured, impactful. This is the art and science of refined digital strategy in the modern age. Here are steps to navigate these waters effectively.</p><p>Now what I typically here at this point is - “We can’t right now for XYZ reasons,” “We ship too fast,” or “Our work is too complex to measure.” Developing a strategic software and digital strategy is challenging. With ever-shifting platforms due to various factors, it’s a steep learning curve. However, I have five steps to guide you in understanding how to create a strategy that allows you to measure if your work has a positive or negative impact</p><p>or no impact at all</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*pX8uxo0Y-O_UWGTJAXI7LQ.gif" /></figure><h3>1. Setup a starting point for analytics</h3><p><strong>Product Analytics</strong></p><ul><li>Product Usage and Engagement- <a href="https://marketingplatform.google.com/about/analytics/">Google Analytics</a> or <a href="https://mixpanel.com/">Mixpanel</a></li><li>Error &amp; Performance Monitoring — <a href="https://logrocket.com/">LogRocket</a></li></ul><p><strong>Marketing Site Analytics</strong></p><ul><li>Traffic and User Behavior — <a href="https://marketingplatform.google.com/about/analytics/">Google Analytics</a></li><li>Conversion Tracking —<a href="https://marketingplatform.google.com/about/analytics/"> Google Analytics</a></li></ul><p><a href="https://medium.com/@differenceeng/common-analytics-tools-cc131e3ac598"><em>Full list with descriptions</em></a></p><h3>2. Stop Waiting - Start Today</h3><p>It doesn’t happen overnight and you will never be “ready”. Good strategy requires persistence and time. Start today, incrementally. Although shortcuts may tempt you, avoid them. Eliminate “I can’t” or “we are waiting” from your vocabulary.</p><h3>3. Break Down Silos</h3><p>Connect your teams to the bigger picture — People will begin to intuitively and organically link each other’s work and support one another.</p><h3>4. Break Down the Work</h3><p>Start with a desired outcome. Segment it into Software, Sales, Marketing, and Customer Support, then execute strategies in parallel.</p><p>Let’s take “Drive more user signups” as our outcome</p><p>User Signups — Go Live Date: June 27th</p><ul><li><strong>Engineering</strong> (starts mid-May): Develop a more seamless signup process based on user research from UX.</li><li><strong>Engineering</strong> (launch day): Team up with support to be on standby for any issues.</li><li><strong>Sales</strong> (starts early June): Reach out to leads and inform them of the upcoming enhanced signup process, emphasizing how it simplifies their journey.</li><li><strong>Marketing</strong> (starts early May): Initiate new email campaigns highlighting the enhanced signup experience for potential customers.</li><li><strong>Support</strong> (starts early June): Get briefed on changes and messaging. Receive elevated troubleshooting solutions in case of issues.</li></ul><h3>5. Measure</h3><p>Use your tools to report on views, interactions, impressions etc. By collecting and organizing your ‘drops’, you’re now poised to measure their impact, accounting for both long and short-tail effects. Remember, if you’ve made it this far, you’re already ahead of 95% of organizations. Strive for continuous improvement.</p><p>Using our signup example</p><ul><li><strong>Engineering</strong>: Success Rate: Percentage of successful signups vs. failed attempts.</li><li><strong>Sales: </strong>Lead Conversion: Number of leads that converted to signups.</li><li><strong>Marketing</strong>: Campaign Effectiveness: Number of signups attributed to specific marketing campaigns or channels.</li><li><strong>Support: </strong>Volume of Queries: Number of support tickets or queries related to the signup process.</li><li><strong>UX</strong>: User Journey Analysis: Analysis of where users drop off during the signup process.</li></ul><p>So, while we started with the imagery of a lake and raindrops, it’s clear that it’s more than just a metaphor. By meticulously understanding each decision, like those individual drops, we can unify our teams, measure success more accurately, and chart a clearer course for future investments. Dive deep into analytics, make waves with intention, and let your business strategies flow with purpose.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88c4acd38d34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git Cheatsheet]]></title>
            <link>https://medium.com/@differenceeng/git-cheatsheet-3bbc13928226?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bbc13928226</guid>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cheatsheet]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Sun, 06 Aug 2023 19:44:25 GMT</pubDate>
            <atom:updated>2023-08-23T22:37:35.335Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g5_9Hk3odROOiJSY" /><figcaption>Photo by <a href="https://unsplash.com/@synkevych?utm_source=medium&amp;utm_medium=referral">Roman Synkevych</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>git init: This command starts a new Git repository. Think of it as creating a new save file for your project.</p><p>git clone &lt;repository-url&gt;: This is like downloading a copy of someone else’s save file to your computer.</p><p>git remote add origin &lt;repository-url&gt;: This is like telling your game console where to find the online server so you can upload or download save files. Once set, you don&#39;t need to tell it again.</p><p>git status: This command is like asking, “What’s different in my project since the last save point?”</p><p>git add &lt;file-name&gt;or git add .: This is like selecting which changes you want to save. git add . selects all changes.</p><p>git commit -m “Your message here”: This creates a new save point with all the changes you selected using git add. The message should describe what changes you made.</p><p>git push origin &lt;branch-name&gt;: This is like uploading your save file so others can see or download it. The &lt;branch-name&gt; is the version of your project that you want to upload.</p><p>git pull origin &lt;branch-name&gt;: This is like downloading the latest version of the project from a specific branch.</p><p>git checkout -b &lt;branch-name&gt;: This creates a new ‘branch’ or version of your project. It’s like creating a new save file where you can try out changes without messing up your main project.</p><p>git checkout &lt;branch-name&gt;: This lets you switch between different branches or versions of your project.</p><p>git merge &lt;branch-name&gt;: This is like combining two different versions of your project into one. If you’ve made changes in a branch, you can use git merge to combine those changes into the main project.</p><p>git branch — show-current: This tells you which version (or branch) of your project you’re currently working on.</p><p>git diff: This shows you what changes you’ve made since the last save point.</p><p>git log: This is like a history book of all the save points (commits) you’ve made in your project.</p><p>git stash: This lets you temporarily set aside (or stash) changes that you aren’t ready to commit yet. It’s like creating a temporary save file.</p><p>git reset — hard &lt;commit-id&gt;: This lets you go back to a previous save point. The &lt;commit-id&gt; is a unique code that identifies each commit.</p><p>Have something you use often that isn’t part of this list, please comment or contact me so we can add it. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bbc13928226" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unraveling Git — Clear the Fog, Focus on Coding]]></title>
            <link>https://medium.com/@differenceeng/unraveling-git-clear-the-fog-focus-on-coding-a665b869be0d?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/a665b869be0d</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[softare-development]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Sun, 06 Aug 2023 19:31:38 GMT</pubDate>
            <atom:updated>2023-08-07T20:35:10.382Z</atom:updated>
            <content:encoded><![CDATA[<h3>Unraveling Git — Clear the Fog, Focus on Coding</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_L8DONSCAXcloyrP" /><figcaption>Photo by <a href="https://unsplash.com/@yancymin?utm_source=medium&amp;utm_medium=referral">Yancy Min</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Throughout my career, assisting students, mentees, and team members alike, I’ve observed that understanding Git can sometimes become an obstacle to their journey. While Git is an indispensable part of the development process, mastering its intricacies shouldn’t overconsume your time. Reflecting on it, much of my day-to-day Git operations feel like “loops”, with a series of “if-else” decisions guiding the way.</p><blockquote>Consider this a reference manual for Git tasks. No need to dive deep into the hows or whys — just find the step you need, follow the instructions, and return to coding. Clear, concise, effective.</blockquote><p>Instead of adding to the countless articles detailing Git workflows, collaboration techniques, or niche features, I aim to provide a streamlined guide. A guide that helps you spend less time fighting with Git and more time doing what you love, writing code. Whether you use GitHub or another platform, this guide is designed to streamline your Git experience.</p><p>To make this guide as effective as possible, I welcome any and all feedback. Please leave comments or contact me. We all stand on the shoulders of giants so help me pay it forward.</p><h4>But before we get started, let’s lay out some ground rules:</h4><ul><li><strong><em>Never</em></strong> work on the main branch — always start by creating a feature branch.</li><li><strong><em>Never</em></strong> push to the main branch — always use pull requests.</li><li><strong><em>Always</em> </strong>usegit status. This command is your compass. Use it to either confirm the changes you are about to make, or to verify that you&#39;ve made the changes you intended to.</li><li><strong><em>Always</em></strong> Commit often, especially when your app is working. Things will go wrong, and the more recent your last “save point”, the less rework you’ll need to do.</li></ul><p>As you get more comfortable with the basics of Git, you may find this Git <a href="https://medium.com/@differenceeng/git-cheatsheet-3bbc13928226">Cheat Sheet</a> useful for quick references. This Cheat Sheet covers a wide range of Git commands and can be a handy guide for your Git journey. But always remember, you can always come back to these loops whenever you feel the need.</p><p>With all that said, let’s dive into the world of Git!</p><h3>The Loop</h3><h4>Cloning a Repo</h4><pre>git clone &lt;repository-url&gt;</pre><h4>Creating a New Branch</h4><pre>git status<br>git checkout -b &lt;branch-name&gt;</pre><h4>Committing Changes</h4><pre>git status<br>git add .<br>git commit -m &quot;Descriptive message about changes&quot;<br>git status</pre><p><em>Note — </em>If you don’t see the message “nothing to commit, working tree clean,” repeat this step</p><h4>Getting Ride of Changes</h4><pre>git status<br>git add .<br>git stash</pre><p><em>Note — </em>If you don’t see the message “nothing to commit, working tree clean,” repeat this step</p><h4>Changing Branches:</h4><pre>git status<br>git checkout &lt;other-branch-name&gt;</pre><h4>Changing Branches — if you have files to commit:</h4><ol><li><strong>Committing Changes - follow this step</strong></li><li><strong>Changing Branches - follow this step</strong></li></ol><h4>Changing Branches — when we have changes we want to get ride of</h4><ol><li><strong>Getting Ride of Changes— follow this step</strong></li><li><strong>Changing Branches — follow this step</strong></li></ol><h4>Creating a Pull Request:</h4><ol><li>git push origin &lt;branch-name&gt;</li></ol><p>2. Navigate to the GitHub (or other providers) project in your browser and follow the steps.</p><h4>Pulling Down Changes from Main and Merging into Your Feature Branch:</h4><pre>git status<br>git checkout main<br>git pull origin main<br>git checkout &lt;branch-name&gt;<br>git merge main<br>git status</pre><h4>Down merging changes</h4><ol><li>Run these commands</li></ol><pre>git status<br>git checkout main<br>git pull origin main<br>git checkout &lt;branch-name&gt;<br>git merge main</pre><p>2. <strong>Committing Changes — follow this step</strong></p><h4>Creating a Pull Request:</h4><pre>git status<br>git push origin &lt;branch-name&gt;<br>git status</pre><h4>Updating an existing pull request</h4><ol><li><strong>Committing Changes — follow this step</strong></li><li><strong>Creating a Pull Request — follow this step</strong></li></ol><h4>Updating an existing pull request — when changes have been merged into main</h4><ol><li><strong>Committing Changes — follow this step</strong></li><li><strong>Creating a Pull Request — follow this step</strong></li></ol><h4>Updating an existing pull request — when you have been working on another branch</h4><blockquote><strong>Big Alert! The root cause of most git troubles starts right here. Before you switch branches, double-check you’ve saved and cleared all your work. Use </strong><strong>git status after switching to be extra sure. Don&#39;t skip this; it&#39;s where a lot of the mix-ups happen!</strong></blockquote><ol><li><strong>Changing Branches — follow this step</strong></li><li><strong>Make required updates</strong></li><li><strong>Updating an Existing Pull Request — follow this step</strong></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a665b869be0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open-Sourcing the Keys to Modern Development, A Hands-On Workshop Series for Leaders and Educators]]></title>
            <link>https://medium.com/@differenceeng/open-sourcing-the-keys-to-modern-development-a-hands-on-workshop-series-for-leaders-and-educators-acf00791b2ee?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/acf00791b2ee</guid>
            <category><![CDATA[material-design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Wed, 14 Jun 2023 17:41:31 GMT</pubDate>
            <atom:updated>2023-06-14T17:41:31.321Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_zpvLh6YsQfZQ00J" /><figcaption>Photo by <a href="https://unsplash.com/@disruptxn?utm_source=medium&amp;utm_medium=referral">Desola Lanre-Ologun</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>TL;DR:</h3><p>I’m launching an open-source workshop framework for leaders and managers. It promotes active knowledge construction and customization, combining theory and hands-on coding. Let’s deepen knowledge and foster continuous learning.</p><h3>Imagine a different approach to tech workshops</h3><p>An approach that shifts focus from following the guidelines to constructing knowledge. This is the idea behind the open-source workshops I’m launching, and I am thrilled to share the details with you. The workshop’s name? UI Foundations with Google Material Design 2.0 and React MUI, and they are available on my GitHub .</p><p><a href="https://github.com/jakele">https://github.com/jakele</a>.</p><p>Unlike standard workshops you might have encountered, this workshop caters to leaders and managers. If you’re seeking to train and upskill your teams, here’s a tool you can wield with precision, versatility, and effectiveness.</p><h3>The architecture of this workshop</h3><p>The architecture of this workshop is structured, yet flexible, allowing customization to match your team’s standards, conventions, and tooling. It presents a different approach to learning. one that does not rely solely on an instructor-led model but encourages participants to get their hands dirty with the code.</p><p>Now, let’s dive a little deeper into the format of these workshops. They are broken down into crucial segments, each serving a unique purpose in the learning journey.</p><h3>For the workshop leader</h3><p>The package includes a comprehensive slide deck filled with course content, an introductory email to set the stage for the workshop, and a post-workshop email loaded with additional resources and FAQs. This material is designed to help the leader guide their team through the workshop. Also included are teacher’s notes and everything needed. The slide deck, pre and post-workshop communications, and a project folder with all the files to be sent to participants ahead of the workshop.</p><h3>For the participants</h3><p>the workshop follows a two-fold approach:</p><ol><li>The Lecture: Concepts and definitions are introduced and explained to provide a theoretical foundation. This is the stage where we introduce the mindset — the ‘why’ behind the ‘how.’</li><li>The Hands-On Coding: Building on the theoretical foundations, participants now dive into the practical application. This is the ‘doing’ phase, where participants will be actively coding along.</li></ol><h3>The mission</h3><p>-is to deepen knowledge and lay a firm groundwork for further exploration of more advanced concepts. These workshops are a starting point. As time progresses, expect more topics, including backend, DevOps, AI/ML, foundations, and more.</p><p>Everyone is encouraged to contribute to the growth and improvement of the workshops, ensuring that the resources remain relevant, robust, and beneficial to all. Your feedback and contributions can have a far-reaching impact, enhancing the workshop’s effectiveness and ensuring the continued growth of our collective knowledge.</p><p>So here’s to a new journey, a new way of learning, and a new chapter in tech education. Let’s dive in and make the web a better place to interact. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acf00791b2ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Created Difference Engine]]></title>
            <link>https://medium.com/@differenceeng/why-i-created-difference-engine-808de2162f06?source=rss-402567da8221------2</link>
            <guid isPermaLink="false">https://medium.com/p/808de2162f06</guid>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Jeffrey Kern]]></dc:creator>
            <pubDate>Thu, 06 Apr 2023 11:33:48 GMT</pubDate>
            <atom:updated>2023-11-20T23:11:57.103Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*1FUH8NeeKp87mpgUFLLCIA.png" /></figure><p>In a tech consulting world that’s often all talk and no action, I saw the need for something different — that’s why Difference Engine came to life. We’re not about just throwing technical jargon at you or dazzling you with buzzwords. We’re here to roll up our sleeves, dive into the real work, and get stuff done alongside you.</p><h4>Real Experience, Real Growth</h4><p>My path through software, working with giants and startups alike, showed me a clear truth. A lot of folks are learning to run a digital company only after they’ve got their initial product out there. But here’s the thing — understanding how to measure work, what agile really means, or how to handle a high-performing engineer — it’s not just about hiring more developers or chasing after the latest tech trend.</p><p>At Difference Engine, we cut through that nonsense. We’re about giving you the straight story, teaching you not just how to use tech, but how to really understand it. It’s not about adding more heads or stacking up debt, it’s about growth, learning, and taking the reins confidently.</p><h4>No More Tech Babble</h4><p>We’ve seen too many companies sold on the dream of ‘rockstar engineers’ or ‘marketing wizards.’ That’s not us. We’re your partners in this — we sit with you, work through the tough problems, and show you how it’s done. Our team has been in the thick of it, from New York to Silicon Valley, leading teams, closing funding, and making real things happen across industries.</p><h4>Learning to Fish in the Tech Pond</h4><p>Here’s where our approach takes a cue from private equity but flips the script. We’re not just about growth, we’re about empowering you. We don’t just hand over a fish, we’re here to teach you to fish. Think of us as both your delivery team and your tech bootcamp. We help you understand the ins and outs, so you’re not just following along — you’re leading the charge.</p><h4>No Bullshit, Just Solutions</h4><p>We tackle projects head-on. Forget cookie-cutter solutions, we tailor everything to fit your needs. Difference Engine is all about bridging that gap between fancy deliverables and actual outcomes. We challenge the usual tech consulting approach and bring you into the heart of it all.</p><h4>Joining Forces with Difference Engine</h4><p>If you’re fed up with the tech runaround and looking for someone who will genuinely work with you, not just for you, then it’s time to talk to us. Whether it’s shaping up your digital strategy, getting the right people on board, or navigating the complex tech market, we’re here to make it happen. With Difference Engine, you’re not just getting solutions, you’re gaining a lifelong ally in the tech world.</p><p>And this, folks, is just the start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=808de2162f06" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>