<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software-Development on Tobi(as Mende)</title><link>https://mende.io/tags/software-development/</link><description>Recent content in Software-Development on Tobi(as Mende)</description><generator>Hugo</generator><language>en-us</language><managingEditor>tobi@techunicorn.builders (Tobias Mende)</managingEditor><webMaster>tobi@techunicorn.builders (Tobias Mende)</webMaster><lastBuildDate>Fri, 05 Dec 2025 05:00:00 +0000</lastBuildDate><atom:link href="https://mende.io/tags/software-development/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Made Me 10x More Productive – Now What?</title><link>https://mende.io/blog/ai-made-me-10x-more-productive-now-what/</link><pubDate>Fri, 05 Dec 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/ai-made-me-10x-more-productive-now-what/</guid><description>&lt;h2 id="thoughts-on-ai-productivity-and-what-we-should-do-differently">Thoughts on AI, Productivity, and What We Should Do Differently&lt;/h2>
&lt;p>In the last couple of months, I got to use Claude code a lot for software development, and I am at a point with it, where it gives me consistently high-quality results at incredible speed. In 99.5% of all cases, I get the results that I expect/desire. In other areas of my life, (other) AI tools have a drastic influence on my productivity and (sometimes) even my ability to do certain things, too.&lt;/p></description></item><item><title>Building Diving Nomads in Public Part 3</title><link>https://mende.io/blog/building-diving-nomads-in-public-part-3/</link><pubDate>Fri, 31 Oct 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/building-diving-nomads-in-public-part-3/</guid><description>&lt;h1 id="building-in-public--part-3-how-we-built-the-diving-nomads-partner-map">Building in Public – Part 3: How We built the Diving Nomads Partner Map&lt;/h1>
&lt;p>This is part three of the &lt;em>Building Diving Nomads in Public&lt;/em> series.&lt;/p>
&lt;p>After sharing &lt;a href="https://tidbits.mende.io/p/building-in-public-part-2">how we automated outreach for dive centers and coliving / coworking partners&lt;/a>, this chapter is about the thing people actually use – our &lt;strong>Partner Map&lt;/strong>.&lt;/p></description></item><item><title>Building in Public: How Diving Nomads Automates Coliving &amp; Coworking Partner Outreach</title><link>https://mende.io/blog/building-diving-nomads-in-public-part-2/</link><pubDate>Fri, 29 Aug 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/building-diving-nomads-in-public-part-2/</guid><description>&lt;p>At &lt;strong>Diving Nomads&lt;/strong>, we’re building something special for digital nomads who love scuba diving. Our mission is to make it easy for them to find great places to work, live, and dive — without having to choose between beautiful dive spots and solid remote work setups.&lt;/p></description></item><item><title>Building Diving Nomads in Public Part 1</title><link>https://mende.io/blog/building-diving-nomads-in-public-part-1/</link><pubDate>Fri, 25 Jul 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/building-diving-nomads-in-public-part-1/</guid><description>&lt;h1 id="building-diving-nomads-in-public-how-we-onboard-dive-centers-and-automate-memberships-with-almost-no-code">Building Diving Nomads in Public: How We Onboard Dive Centers and Automate Memberships with (Almost) No Code&lt;/h1>
&lt;blockquote>
&lt;p>&lt;strong>TL;DR&lt;/strong>&lt;br>
We&amp;rsquo;re building a platform for digital nomads with a passion for scuba diving. Our lean, automation-first tech stack allows us to move fast, deliver value early, and maybe inspire other early-stage founders to rethink how they build.&lt;/p></description></item><item><title>How to give outstanding code reviews (if you have to)</title><link>https://mende.io/blog/how-to-give-outstanding-code-reviews-if-you-have-to/</link><pubDate>Sat, 20 Jul 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/how-to-give-outstanding-code-reviews-if-you-have-to/</guid><description>&lt;h1 id="how-to-give-outstanding-code-reviews-if-you-have-to">How to give outstanding code reviews (if you have to)&lt;/h1>
&lt;p>Most software companies use code reviews to ensure that at least two people check each part of the code base and maintain its quality. Although I prefer pair or team programming over asynchronous code reviews, I recognize that this isn’t always possible. In such cases, asynchronous code reviews are the next best option.&lt;/p></description></item><item><title>Things I love and hate about the state of software companies in 2024</title><link>https://mende.io/blog/things-i-love-and-hate-about-the-state-of-software-companies-in-2024/</link><pubDate>Sat, 16 Mar 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/things-i-love-and-hate-about-the-state-of-software-companies-in-2024/</guid><description>&lt;h1 id="things-i-love-and-hate-about-the-state-of-software-companies-in-2024">Things I love and hate about the state of software companies in 2024&lt;/h1>
&lt;p>&lt;strong>Disclaimer:&lt;/strong> This started as a rant, not meant to be published. But sticking to my “&lt;a href="https://nudge.unblocked.engineering/p/cutting-through-the-noise-becoming">New Year’s resolution&lt;/a>” to write about what triggers me most, I decided to publish it anyway. I wanted to publish it as a LinkedIn post, but it got too long. So here is the unshortened, unpolished and authentic original version of this document, most of which I wrote on my phone after waking up on a Sunday at 5:45am. 😬&lt;/p></description></item><item><title>May the LLM be with You – On Planes and German Trains</title><link>https://mende.io/blog/may-the-llm-be-with-you-on-planes-and-german-trains/</link><pubDate>Sat, 30 Dec 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/may-the-llm-be-with-you-on-planes-and-german-trains/</guid><description>&lt;h1 id="may-the-llm-be-with-you--on-planes-and-german-trains">May the LLM be with You – On Planes and German Trains&lt;/h1>
&lt;p>This might be the unofficial seventh part of the “&lt;a href="https://mende.io/blog/tag/ai-for-devex/">AI for DevEx&lt;/a>” series. LLM tools are a great help during the entire software development process. But what if we are offline or if data privacy concerns disallow using ChatGPT and similar tools?&lt;/p></description></item><item><title>Managing Technical Debt in Software Development</title><link>https://mende.io/blog/managing-technical-debt-in-software-development/</link><pubDate>Sat, 29 Apr 2023 07:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/managing-technical-debt-in-software-development/</guid><description>&lt;h1 id="managing-technical-debt-in-software-development">Managing Technical Debt in Software Development&lt;/h1>
&lt;p>Organizations often accumulate technical debt as the pressure to deliver customer value quickly increases, systems grow, and extending functionality the &lt;em>right&lt;/em> way becomes more difficult.&lt;/p></description></item><item><title>Make three friends with one gift: Why developer experience is key to productivity, engineering excellence and stakeholder satisfaction.</title><link>https://mende.io/blog/make-three-friends-with-one-gift-why-developer-experience-is-key-to-productivity-engineering-excellence-and-stakeholder-satisfaction/</link><pubDate>Sat, 11 Feb 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/make-three-friends-with-one-gift-why-developer-experience-is-key-to-productivity-engineering-excellence-and-stakeholder-satisfaction/</guid><description>&lt;h1 id="make-three-friends-with-one-gift-why-developer-experience-is-key-to-productivity-engineering-excellence-and-stakeholder-satisfaction">Make three friends with one gift: Why developer experience is key to productivity, engineering excellence and stakeholder satisfaction.&lt;/h1>
&lt;p>In today’s fast-paced, technology-driven world, software development has become a critical aspect of many organisations. However, with increased demands on development teams, it’s easy to overlook the importance of developer experience.&lt;/p></description></item><item><title>The Importance of Developer Productivity in a Recession</title><link>https://mende.io/blog/importance-of-developer-productivity/</link><pubDate>Sat, 26 Nov 2022 13:30:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/importance-of-developer-productivity/</guid><description>&lt;h1 id="the-importance-of-developer-productivity-in-a-recession">The Importance of Developer Productivity in a Recession&lt;/h1>
&lt;p>When times get rough, companies and investors get more cautious with how they spend and invest their money. Many companies reduce their spending on employees and salaries by laying off large numbers of people.&lt;/p></description></item><item><title>How to do Architecture Mapping Workshops in a Remote Setup</title><link>https://mende.io/blog/remote-architecture-mapping-workshops/</link><pubDate>Sat, 23 Jul 2022 13:27:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/remote-architecture-mapping-workshops/</guid><description>&lt;h1 id="how-to-do-architecture-mapping-workshops-in-a-remote-setup">How to do Architecture Mapping Workshops in a Remote Setup&lt;/h1>
&lt;p>Mapping the architecture of the system that you are building in your company, is a worthwhile activity. The worth does not come so much from the end-result, the map, but much more from the activity itself, if done right.&lt;/p></description></item><item><title>DRY – DO repeat yourself</title><link>https://mende.io/blog/dry-do-repeat-yourself/</link><pubDate>Sat, 30 Apr 2022 13:13:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/dry-do-repeat-yourself/</guid><description>&lt;h1 id="dry--do-repeat-yourself">DRY – DO repeat yourself&lt;/h1>
&lt;p>When I started my career as a software developer and already during university, almost no principle was mentioned as often as the DRY principle: “Do &lt;strong>not&lt;/strong> repeat yourself”&lt;/p></description></item><item><title>Code ownership conflicts as a signal for structural mismatch</title><link>https://mende.io/blog/code-ownership-conflicts/</link><pubDate>Sat, 19 Feb 2022 12:54:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/code-ownership-conflicts/</guid><description>&lt;h1 id="code-ownership-conflicts-as-a-signal-for-structural-mismatch">Code ownership conflicts as a signal for structural mismatch&lt;/h1>
&lt;p>In my &lt;a href="https://mende.io/blog/code-ownership/">last article&lt;/a>, I explained why I believe that individual code ownership is bad and why weak code ownership on a cross-team level can be highly beneficial.&lt;/p></description></item><item><title>Code Ownership: Keeping the balance between structure and agility</title><link>https://mende.io/blog/code-ownership/</link><pubDate>Sat, 12 Feb 2022 12:53:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/code-ownership/</guid><description>&lt;h1 id="code-ownership-keeping-the-balance-between-structure-and-agility">Code Ownership: Keeping the balance between structure and agility&lt;/h1>
&lt;p>Code ownership is an important topic when it comes to enabling your teams and allowing developers to improve the system while keeping the overhead of changes low.&lt;/p></description></item><item><title>A platform team for next-level developer experience</title><link>https://mende.io/blog/developer-experience-platform-team/</link><pubDate>Sat, 05 Feb 2022 12:49:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/developer-experience-platform-team/</guid><description>&lt;h1 id="a-platform-team-for-next-level-developer-experience">A platform team for next-level developer experience&lt;/h1>
&lt;p>In this article, I am sharing my experience (and opinions) of how a platform team should be set up to provide great developer experience for other development teams.&lt;/p></description></item><item><title>OKRs are NOT guaranteed deliveries</title><link>https://mende.io/blog/okrs-are-not-guaranteed-deliveries/</link><pubDate>Sat, 22 Jan 2022 12:44:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/okrs-are-not-guaranteed-deliveries/</guid><description>&lt;h1 id="okrs-are-not-guaranteed-deliveries">OKRs are NOT guaranteed deliveries&lt;/h1>
&lt;p>Objectives and key results are a great tool for collaborative goal-setting and for aligned on a company-wide direction. While the key objectives or north-stars might be handed down from C-level management, the concrete objectives and key-results are discovered by the teams. Only they know best, how to achieve the bigger goals of the company. Thus, all teams needs to figure out, how they can best contribute to the company goals.&lt;/p></description></item><item><title>There is no system like production: Why you should test in production</title><link>https://mende.io/blog/testing-in-production/</link><pubDate>Sat, 11 Dec 2021 12:27:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/testing-in-production/</guid><description>&lt;h1 id="there-is-no-system-like-production-why-you-should-test-in-production">There is no system like production: Why you should test in production&lt;/h1>
&lt;p>&lt;img src="https://mende.io/img/import/2021-10-testing-in-production.jpg" alt="">&lt;/p>
&lt;p>Shipping software without testing sounds scary. And this is also, what this article &lt;strong>is not&lt;/strong> about. Organisations spend a lot of time and money to make sure that code is as much error-free as possible, when it reaches production and affects users.&lt;/p></description></item><item><title>Adopting Continuous Delivery: More a culture change than automation of processes</title><link>https://mende.io/blog/adopting-continous-delivery-culture/</link><pubDate>Sat, 04 Dec 2021 12:07:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/adopting-continous-delivery-culture/</guid><description>&lt;h1 id="adopting-continuous-delivery-more-a-culture-change-than-automation-of-processes">Adopting Continuous Delivery: More a culture change than automation of processes&lt;/h1>
&lt;p>Continuous delivery, the process of automatically delivering changes of a system without human interaction, is one of the most beneficial practices that software teams can adopt. In &lt;a href="https://www.goodreads.com/en/book/show/35747076-accelerate">Accelerate&lt;/a>, the authors Nicole Forsgren, Jez Humble and Gene Kim, discovered a strong link between using continuous delivery and organisational performance: Teams that continuously deliver their changes have a stronger sense of ownership, get faster feedback and need to rework their code less. Furthermore, deployments are less stressful and the risk of burnout is reduced.&lt;/p></description></item><item><title>Crucial developer practices: Decoupling deployments and releases</title><link>https://mende.io/blog/decoupling-deployments-and-releases/</link><pubDate>Sat, 27 Nov 2021 12:02:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/decoupling-deployments-and-releases/</guid><description>&lt;h1 id="crucial-developer-practices-decoupling-deployments-and-releases">Crucial developer practices: Decoupling deployments and releases&lt;/h1>
&lt;p>When systems are small and the risk of introducing defects when changing its behaviour is low, these changes can happen during deployment. However, when systems grow, the behaviour becomes more complex and more people are working on the system, it is essential to decouple behaviour changes, the releases, from deployments.&lt;/p></description></item><item><title>Do you have walls in your deployment process?</title><link>https://mende.io/blog/deployment-process-walls/</link><pubDate>Sat, 20 Nov 2021 11:59:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/deployment-process-walls/</guid><description>&lt;h1 id="do-you-have-walls-in-your-deployment-process">Do you have walls in your deployment process?&lt;/h1>
&lt;p>Enabling units to quickly deploy and release new features to their customers is one of the goals of &lt;a href="https://mende.io/blog/cross-functional-units-uni-functional-teams/">cross-functional units&lt;/a> and the “you build it, you run it” DevOps mentality.&lt;/p></description></item><item><title>Just care less about not being aligned</title><link>https://mende.io/blog/just-care-less-about-not-being-aligned/</link><pubDate>Sat, 06 Nov 2021 10:12:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/just-care-less-about-not-being-aligned/</guid><description>&lt;h1 id="just-care-less-about-not-being-aligned">Just care less about not being aligned&lt;/h1>
&lt;p>If you work in a company that is aiming for fast growth, being overly aligned will slow you down as the number of stakeholders increases. If every time I want to introduce a new linting rule I would need to agree with 55 other developers, I will likely not do it. Instead of forcing all units to use the same tech stack, the same code style, the same testing framework and so on, we need to learn to &lt;em>just care less&lt;/em>. Of course, the ability to care less depends on the architecture and the company structure. In a monolithic application, it is far more difficult to reduce the impact of units on each other, than in an environment of properly structured microservices. Thus, the goal is to identify and create structures that allow you to care less about alignment. The entire idea of cross-functional units is aiming for units to be independent. This is achieved by having units own vertical slices of the system completely, which reduces the need for alignment with other units to a minimum. However, sometimes even cross-functional units can influence each other because of technical dependencies or suboptimal structuring of these units.&lt;/p></description></item><item><title>Cross-functional units and uni-functional teams</title><link>https://mende.io/blog/cross-functional-units-uni-functional-teams/</link><pubDate>Fri, 29 Oct 2021 09:08:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/cross-functional-units-uni-functional-teams/</guid><description>&lt;h1 id="cross-functional-units-and-uni-functional-teams">Cross-functional units and uni-functional teams&lt;/h1>
&lt;p>Many modern companies put a high emphasis on having multiple functions within one unit or team. The goal: The unit should be able to function with a high degree of autonomy, working on its area and owning everything in this area from beginning to end.&lt;/p></description></item></channel></rss>