<?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 Adam Beleko on Medium]]></title>
        <description><![CDATA[Stories by Adam Beleko on Medium]]></description>
        <link>https://medium.com/@adambeleko?source=rss-22ae27d512aa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*pfA60GWxNv1JOggx.jpg</url>
            <title>Stories by Adam Beleko on Medium</title>
            <link>https://medium.com/@adambeleko?source=rss-22ae27d512aa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:28:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adambeleko/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[5 Things I Wish Business People Knew About Dealing With Software Developers]]></title>
            <link>https://medium.com/@adambeleko/5-things-i-wish-business-people-knew-about-dealing-with-software-developers-03ea36c64013?source=rss-22ae27d512aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/03ea36c64013</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Adam Beleko]]></dc:creator>
            <pubDate>Mon, 27 Apr 2026 07:23:38 GMT</pubDate>
            <atom:updated>2026-04-27T07:23:38.250Z</atom:updated>
            <content:encoded><![CDATA[<p>For 8 years I have watched friends and colleagues lament over some coder. In these 8 years as a Software Developer, I have seen it all; From a lead developer disappearing with company source code, a 6AM manhunt for a developer in the streets for him to fix a bug, and a client being forced to pay at gunpoint! (Just kidding, I guess we all have that client that wouldn’t pay.)</p><p>I feel like I am the right person to save business people from painful situations while finding or working with technical co-founders, IT seniors/colleagues, or hires. The right ones always have a simple pattern and understanding it will save you headaches, time arguing, feelings of resentment, and your life — if you’re ever held at gunpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bZdVv6X--5UXOyk4" /><figcaption>5 Things I Wish Business People Knew About Dealing With Software Developers</figcaption></figure><h3>1. Know What You Don’t Know</h3><p>As a life principle, this will save you more than your working relationship. Software developers are naturally technical and unless you possess a similar or greater expertise, it is best to keep your mouth shut — or devote it into asking.</p><p>This is more of a matter of respect — for each other’s knowledge, professionalism, and craft; because the best work is done when the coder and the businessperson are both competent and reliable. And if so, it is absurd to expect that the coder will waste time teaching the business person about business modelling or the business person teach about code complexity.</p><p>I understand that technology has shown that we all deserve a platform to share thoughts; and that Sci-Fi movies have always explained about algorithms. But please, hold that clever comment you have about algorithms and let the expert figure out the how-tos.</p><blockquote>Provide requirements, not coding instructions.</blockquote><h3>2. Know What You Want</h3><p>More important than all, you should know exactly what you wish for. Coding is an intensive practise, requiring a lot of thinking — I’m seriously not bragging.</p><p>It then becomes the most annoying thing when someone offers vague details about what they want and rants about how bad the result is. It is the best way to show someone how much you enjoy wasting their time and putting them to misery.</p><p>Knowing what you want means providing website copy, images, documents, and everything there is to enable the coder to develop your website — and providing it in advance. It means stating every little detail that is important to you because for a coder, whatever is left out is not important. To put it simply, never ask a carpenter to make a small table when you actually expect a three-legged stool.</p><p>Simply understand that once your 6 inch cake is half baked, changing it into an 8 inch cake might not just entail glueing 2 inch dough around the cake. Just 2 inches might mean redoing the whole thing.</p><blockquote>Provide detailed requirements and avoid frequent changes.</blockquote><h3>3. Let ‘Em Cook!</h3><p>The insane Silicon Valley stories almost always involve a geek building a magical spaceship and happens to make it work at the last second of the 1 week timeline his arrogant master gave him.</p><p>Elon Musk is also to blame for saying, “if you give yourself 30 days to clean your house, it will take 30 days. If you give yourself 3 hours, it will take 3 hours.” While I totally agree with him, many “Tony Stark” managers were misled into believing that you only have to “give yourself” 1 minute to bake a cake, and surely it will be done.</p><p>Especially if you are not a coding expert, you will avoid a lot of unnecessary stress by openly asking about the timelines and then reasoning with the developer — because you may in fact have constraints. Developers are more than willing to compromise their sleep every once in a while, but no human being can afford this for long.</p><p>Software built steadily and carefully is more reliable, which is good for business in the long run. Being in a rush about everything gives people the feeling that nothing is important to you; and having priorities is a trait of a good businessperson. So, let the cake burn when your life depends on it, but in the other times, let ‘em cook!</p><blockquote>Apply pressure once a while and always make a case for it.</blockquote><h3>4. Know That It Is Hard Work</h3><p>Coding is uniquely difficult because:</p><ul><li>It is technical,</li><li>It is practical — often demanding very long hours on a daily basis, and</li><li>It is fast paced — coders need to always study new technologies.</li></ul><p>This means that to build you the cool website you deserve, the developer needs:</p><ul><li>To have acquired special scientific knowledge,</li><li>To have spent sleepless nights practising to be able to deliver, and</li><li>To adhere to coding principles.</li></ul><p>The least you can do is appreciate the craft and not treat it lightly.</p><p>I am not suggesting that you stroke the coder’s ego or massage his feet, all I’m suggesting is that you don’t underestimate the work that is put in. I once encountered a situation where the business department of an organization requested for a single input form addition. This single input field had developers discussing for an hour about how to incorporate it. The issue was clearly not adding a single dropdown component, or saving user’s input in the database; the issue was that the new captured data would become central to all business logic. To the business team, this was just a small form change, to the development team, it could mean re-writing an entire software.</p><p>Avoid belittling work by calling it a “minor” change or by constantly adding new requirements. Your developer has limited energy and most importantly, limited creativity. Use this energy and creativity on necessary tasks because adding a single field might take as much as building an app.</p><blockquote>Reward hard work with more noble work.</blockquote><h3>5. Keep Your Dreams To Yourself</h3><p>Your typical developer is never interested in your vision or the grand plans you have for the next five years. Say you want users to send each other money in your messaging app in Q3. A simple sentence is all a businessperson needs to have in mind. For a developer, this simple sentence carries with it a baggage of questions like:</p><ul><li>How should the app track payment status? How do users know a payment was sent, received, or pending? Do we rely on push notifications, SMS, or in-app alerts?</li><li>What if someone sends money to the wrong person? How can transactions be reversed? Do we need a dispute resolution system? Should it be automated?</li><li>How can the system handle thousands of transactions per second during peak times?</li><li>Where do we store transaction histories? How long do we retain them? How easily can they be accessed?</li><li>What happens to the payment if a user is offline? What if their account is frozen mid-transaction?</li></ul><p>The energy needed by a developer to process this information is significant and exhausting — especially when this information is not to be acted upon in a span of a week.</p><p>It is healthy for a coder to understand the project roadmap, but this should be done in dedicated briefings where the coder’s mind is preconditioned to listen and not go into a thinking spree.</p><p>Apart from boggling developers’ minds, these grand plans are often vague and not well conceptualized — leading to confusion. Add to this the scenario where a businessperson does not spend time prioritizing tasks, then the developer would end up building in Q1, what you planned for Q4. In business, this is suicidal.</p><p>In recent software development planning, developers are assigned weekly or bi-weekly tasks. These momentary collection of tasks are called “<a href="http://atlassian.com/agile/scrum/sprints">sprints</a>”. It is no wonder that this method has proven to be successful because it is best suited to adapt to developers’ minds.</p><blockquote>Talk vision in dedicated, preconditioned settings.</blockquote><h3>Conclusion</h3><p>I have learnt to appreciate business minds after walking their path. It is hard for most developers to comprehend how a great businessperson thinks. Through this article, I hope to shed light just in how mistakenly businesspeople use their gifted brains by assuming that developers process things the same way. In reality, both need each other and would always do best when each is shown the empathy needed to unapologetically be themself.</p><h3>TLTR:</h3><p>There’s a lot that could be stated about what bugs developers when working with their non-technical colleagues. To get the most out of developers we need to adapt to how they’re wired — to be focused, to avoid dead-ends, to maximize efficiency, to innovate, and to solve problems. Anything shallow kills focus; anything rushed leads to dead ends; anything complicated kills efficiency. But structured thinking leads to problem solving and innovation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=03ea36c64013" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Mobile UI — Combination Lock Navigator]]></title>
            <link>https://medium.com/@adambeleko/the-mobile-ui-combination-lock-navigator-f3ece5a73ea2?source=rss-22ae27d512aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3ece5a73ea2</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Adam Beleko]]></dc:creator>
            <pubDate>Thu, 25 Jul 2024 13:48:23 GMT</pubDate>
            <atom:updated>2024-07-25T13:48:23.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*A8IVGcVzVeTbwxLY5V_WQw.png" /><figcaption>Combination lock by Nicky Knicky from <a href="https://thenounproject.com/browse/icons/term/combination-lock/">Noun Project</a> (CC BY 3.0)</figcaption></figure><h3>The Mobile UI — Combination Lock Navigator</h3><p>The approach to mobile applications’ screen navigation has been innovative as necessitated by the use and dimensions of the device. Throughout the rise of smartphones, it was clear that a different approach to design was needed.</p><p>In the period of two decades, we have seen beautiful and innovative navigation approaches commonly referred to as “Navigators” by geeks. The following are the major mobile applications screen navigators:</p><ol><li>Top Tab Bar Navigation</li><li>Side Drawer Navigation</li><li>Bottom Navigation Bar</li></ol><p>Another great way to categorize these navigators is by their patterns as done well by Lyubov Kurach in the medium article <a href="https://medium.com/@lyubovkurach/9-mobile-navigation-patterns-usage-pros-cons-45ba10d6f59e">https://medium.com/@lyubovkurach/9-mobile-navigation-patterns-usage-pros-cons-45ba10d6f59e</a>. In summary, these are the 9 Mobile Navigation Patterns:</p><ol><li>Hamburger Menu (or List Type Menus)</li><li>Tab Bar (Bottom and Top)</li><li>Priority+</li><li>Full-Screen Navigation</li><li>Floating Action Button (or Pictorial Circle Menus)</li><li>Gesture-Based Navigation</li><li>3D Touch</li><li>One-handed navigation</li><li>Bottom Navigation Interface</li></ol><p>The most celebrated of the screen navigation designs in the Bottom Navigation Bar well popularized by Instagram; it’s certainly my favorite. The Bottom Navigation Bar has hand-down beat all of the other navigations in terms of consumer and design preference. Recently, the app giant WhatsApp followed suit, perhaps confirming the dominance of this screen navigation. Dinesh Samala puts it well in the article Why WhatsApp Redesigned Its UX — <a href="https://uxplanet.org/why-whatsapp-redesigned-its-ux-73d5f799f8cd">https://uxplanet.org/why-whatsapp-redesigned-its-ux-73d5f799f8cd</a>.</p><p>Adding to this, and perhaps after careful research and consideration, is a design concept, approach, and pattern I want to point out. This mobile screen navigation design takes in elements from different patterns, combining them into a hopefully more powerful and engaging design. Its inspiration is derived from a Money Safe Combination Lock which uses a rotating handle to allow one to “dial” the correct keys to unlock the safe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/608/1*-hwXSh926YH3Wyer3VzJrQ.png" /><figcaption>Diagram: Basic anatomy of the Combination Lock Navigator</figcaption></figure><p>The above diagram is the basic anatomy of the Combination Lock Navigator. It typically is a rounded “combination lock” placed at the far corner of the screen such that a part of it is hidden. I must say that this basic diagram does not look the part. But the real test of the navigation is to throw in all UI/UX design concerns and try to resolve them with the same implementation. The following are notable concerns we wish to resolve:</p><ol><li>Number of available menu buttons</li><li>Allowing for submenu buttons</li><li>Usage with a leftie</li><li>Ease of reach/Thumb reachability</li><li><strong>Number of available menu buttons</strong></li></ol><p>From the design, it is clear that the navigation menu will not work for most applications with 4 to 5 bottom navigation options. However, using the “hidden part” of the menu, we can additionally obtain more space to accommodate more menu options. 4 certainly, 5 surely, more maybe!</p><p>To uncover these added options, the navigation menu will rotate clockwise or anti-clockwise by following the users gesture. The user will hold the menu and drag up for a clockwise rotation or drag down for an anti-clockwise rotation — hence the “Combination Lock Navigator”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*StvRlY4dhDnANZq_vIqRHg.png" /><figcaption>Diagram: The Combination Lock Navigator support for more menu options</figcaption></figure><p><strong>2. Allowing for submenu buttons</strong></p><p>While the usual Bottom Navigation Bar has no submenu options, I can imagine the Combination Lock Navigator supporting submenu options. And with this, it would likely be that the Combination Lock Navigator will be preferred in instances where most/all the menu options have corresponding submenu options.</p><p>The submenu options should adhere to the design implementation of the menu options. By now, the navigation’s more closely resembles the combination/dial lock.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*J4FoUDLUYZqP0gSdzq3xOQ.png" /><figcaption>Diagram: The Combination Lock Navigator support for submenu options</figcaption></figure><p><strong>3. Usage with a leftie</strong></p><p>It is without a doubt that the Combination Lock Navigator is well accessible with a single finger. Considering that some use the left hand, it would be difficult for them to easily access the menu with their left hand. To make the navigation adaptable, it should have the ability to be moved to the other side of the screen. Here, we can envision that a horizontal dragging gesture that originates from the center of the navigation will trigger the menu transposition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*4eOdFYhh_QEp36tnHJikTQ.png" /><figcaption>Diagram: The Combination Lock Navigator transposition demonstration</figcaption></figure><p><strong>4. Ease of Reach</strong></p><p>The navigator is easy to reach with a left thumb and right thumb. What’s more is that it’s flexibility to transition to the left, center, and right means that it can cater to every “thumb’s comfort”. This is perhaps the most unique and important proposition of the Combination Lock Navigator. The diagram below displays zones of thumb reachability where the green zones are areas of easy reachability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*eG1L8GOlG_t9BkbVz-NIZA.png" /><figcaption>Diagram: Mobile Interface Reachability</figcaption></figure><p>This diagram was taken from Lyubov Kurach’s medium article <a href="https://medium.com/@lyubovkurach/9-mobile-navigation-patterns-usage-pros-cons-45ba10d6f59e">https://medium.com/@lyubovkurach/9-mobile-navigation-patterns-usage-pros-cons-45ba10d6f59e</a></p><p>The Combination Lock Navigator is not short of defects, at least for now. If it does not inspire a new design, I hope that it shows that we have not reached the end of design innovation; just not yet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3ece5a73ea2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>