<?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 Bartek Hugo on Medium]]></title>
        <description><![CDATA[Stories by Bartek Hugo on Medium]]></description>
        <link>https://medium.com/@bartekhugo?source=rss-e80fb5eabb6d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WPSfirkNhsGFkEDz6rZAqw.jpeg</url>
            <title>Stories by Bartek Hugo on Medium</title>
            <link>https://medium.com/@bartekhugo?source=rss-e80fb5eabb6d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:13:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bartekhugo/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[Phase 5. Design & development]]></title>
            <link>https://medium.com/untitledkingdom/phase-5-design-development-e91d2e9d418f?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e91d2e9d418f</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hardware-development]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Fri, 15 Jan 2021 15:40:34 GMT</pubDate>
            <atom:updated>2021-01-15T15:40:34.020Z</atom:updated>
            <content:encoded><![CDATA[<p>Now it’s time to focus on defining basic mechanics, PCBs, and form factors that allow us to use the product in a limited environment. Does our rocket have a chance to fly? Do all components work as we wanted? Does everything fit inside the housing?</p><p>If this is the first blog post of the series you’ve come across, be sure to take a look at the previous ones:</p><ul><li><a href="https://www.untitledkingdom.com/blog/we-choose-to-go-to-an-mvp-7-phases-of-the-software-and-hardware-development-process-inspired-by-nasa">We choose to go to an MVP. 7 phases of the software and hardware development process inspired by NASA</a></li><li><a href="https://www.untitledkingdom.com/blog/phase-1.-research.-software-hardware-development-process">Phase 1. Research</a></li><li><a href="https://www.untitledkingdom.com/blog/phase-2.-proof-of-concept.-software-hardware-development-process">Phase 2. Proof of concept</a></li><li><a href="https://www.untitledkingdom.com/blog/phase-3.-prototyping.-software-hardware-development-process">Phase 3. Prototyping</a></li><li><a href="https://www.untitledkingdom.com/blog/phase-4.-feasibility-study.-software-hardware-development-process">Phase 4. Feasibility study</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5MHLuHuSVEoN-nx2.jpg" /><figcaption>Photo by <a href="https://unsplash.com/@wizwow?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Donald Giannatti</a> on <a href="https://unsplash.com/s/photos/nasa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>WHAT DO WE HAVE AFTER THE FEASIBILITY STUDY?</h3><p>After this phase, we should have developed the two most important materials that will allow us to decide whether to continue development and move on:</p><ul><li>The risk assessment will show us if there are any big threats and whether we can deal with them.</li><li>The balance sheet and roadmap determine whether the production is financially viable and how we can estimate production, certification, and sales over time.</li></ul><p>In the previous article, I summarized <a href="https://www.untitledkingdom.com/blog/phase-4.-feasibility-study.-software-hardware-development-process">what we have after the first phases</a>.</p><h3>WHAT DO WE DO AT THE DESIGN &amp; DEVELOPMENT PHASE</h3><p>In the case of design and development, the processes happen simultaneously and are very similar to each other. Even if they start separately, they have to connect at the end.</p><h4>DESIGN &amp; BUILDING A LOOKS-LIKE PROTOTYPE</h4><p>If we are dealing with a physical product, we need the cheapest version of the prototype, preferably 1:1, which will show us how this product will look in space and how we can use it. Such solutions can be made of cardboard, foam, everything that will allow you to see the idea in reality cheaply and quickly. In the case of applications, it is much more comfortable; we need a preferably clickable prototype.</p><p>After selecting the best version of the prototype and corrections, we have dimensioned and CMF (colors, materials, and finishes), which can we refine using the appropriate software. This will be the basis for the production of physical models. Finally, we get a high-quality mockup of the product. It should contain all the elements that will be included on the device.</p><p>If we are also working on/or on the application, it is also the moment to reflect high-fidelity mockups and check the user experience.</p><h4>LOOKS-LIKE PROTOTYPE TESTING</h4><p>At this point, we want to collect as much feedback as possible on both design (wireframes, looks-like prototype) and user experience with the product.</p><p>What I would like to emphasize is that testing should be well planned:</p><ul><li>it is worth doing a few tests to catch errors in the planned testing process itself, before we do them on a larger scale,</li><li>we invite clients to test — if someone is not the target group, we can take into account completely unnecessary comments,</li><li>plan your test script and don’t get left out of it too often,</li><li>ideally, you let users run on your prototype themselves without much explanation, which is exactly how they could use it,</li><li>our observations of customer behavior are much more important than their words — in tests, they will often want to explain too much and look for the causes of problems,</li><li>prioritize comments and notes — which require more profound thought and change, which is only a nice-to-have.</li></ul><p>After implementing changes, it is worth planning another feedback to see whether the improvements we have made really solve users’ problems.</p><h4>SERVICE DESIGN</h4><p>Besides having a prototype that looks and works, we also need to rethink how the entire service related to this product will perform. Of course, the components will differ depending on whether it is a physical product or an application.</p><ul><li>Where will the device or application be sold? Where will customers come into contact with it?</li><li>How do we want to convince them to buy? How does our proposal stand out from the rest?</li><li>What will the packaging and the entire unboxing process be like?</li><li>How will we plan the first use of a device or application?</li><li>How will the installation and onboarding work?</li><li>How do we want to involve the user in the regular use of the device and/or application?</li><li>How will we provide support to clients in the most common problems? How do we deal with the less typical challenges?</li></ul><h4>REQUIREMENTS (SPECS)</h4><p>At this stage, after Phase 4. Feasibility study, we have most of the specifications and costs. It is worth taking a second look at all hardware or software elements we must consider. This list should include:</p><ul><li>Software requirements, languages, connectivity methods, firmware etc.</li><li>All hardware components, requirements, bill of materials (BOM), printed circuit board (PCB) specification, strength, appropriate temperatures etc.</li><li>Packaging specification.</li><li>Legal requirements, necessary certificates, depending on the country in which we want to sell the product.</li></ul><p>I will repeat myself once more — these requirements may change when testing various solutions, but it is worth starting somewhere.</p><h4><strong>TESTING WORKS-LIKE PROTOTYPE</strong></h4><p>As in the design process, we tried to build a visual prototype as cheaply and as quickly as possible. Now we are making it from the functional side to check if everything works as planned.</p><p>We check every element, PCB operation, and basic functionalities. You can start with simple 3D printing going to increasingly complex forms and advancement. We should pay particular attention to the PCB, which is the heart of the device. Usually, it requires creating several versions before we achieve a satisfactory result.</p><p>Usually, it requires creating several versions before we achieve a satisfactory result.</p><h4>MARRIAGE OF THE DESIGN AND DEVELOPMENT</h4><p>When the design, materials and form of the device have been refined, it’s time to assemble them with the engineering part. At this stage, we finally verify whether everything works as expected. We check weak points and verify costs.</p><p>After completing the electrical part and on the implemented firmware, we enter the work with software engineers. More about <a href="https://www.untitledkingdom.com/blog/how-the-beginning-of-mobile-app-development-should-look-like.-based-on-11-years-of-experience">the beginning of mobile app development we wrote here</a>.</p><p>At this stage, we combine the looks-like prototype and works-like prototype and check their functioning very carefully. Most often, we need a few more models before we move on to the next stage.</p><h3>THE RESULT</h3><p>This stage aims to verify all the functionality and look of the device so that it can lead to the next phase, which is for EVT, DVT, PVT hardware, i.e., manufacturing.</p><p>In the case of applications, we go straight to the MVP phase.</p><p>If you are developing a project in which you need support in the <a href="https://www.untitledkingdom.com/services/rapid-prototyping?hsCtaTracking=4c345658-366c-4069-b278-0b76f5a55a25%7Cd4bf9a06-5e45-4c03-a95b-dbfaba39d470">design &amp; development phase</a>, see what we can do for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e91d2e9d418f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/phase-5-design-development-e91d2e9d418f">Phase 5. Design &amp; development</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phase 3. Prototyping. Software & hardware development process]]></title>
            <link>https://medium.com/untitledkingdom/phase-3-prototyping-software-hardware-development-process-de37d7280999?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/de37d7280999</guid>
            <category><![CDATA[hardware-development]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Mon, 28 Dec 2020 09:31:15 GMT</pubDate>
            <atom:updated>2020-12-28T09:31:15.458Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>In our trip to the Moon, we have already gone through several stages of preparation. Time to test spacesuits before the expedition. Is it possible to move freely in them? Can you see well through them? What are the first experiences that we could not fully predict?</strong></p><p>If this is the first blog post of the series you’ve come across, be sure to take a look at the previous ones:</p><ul><li><a href="https://www.untitledkingdom.com/blog/we-choose-to-go-to-an-mvp-7-phases-of-the-software-and-hardware-development-process-inspired-by-nasa">We choose to go to an MVP. 7 phases of the software and hardware development process inspired by NASA</a></li><li><a href="https://www.untitledkingdom.com/blog/phase-1.-research.-software-hardware-development-process">Phase 1. Research</a></li><li><a href="https://www.untitledkingdom.com/blog/phase-2.-proof-of-concept.-software-hardware-development-process">Phase 2. Proof of concept</a></li></ul><p>Blast-off!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/0*VNnN5Nl33-cnHUJo.jpg" /></figure><p>Photo by <a href="https://unsplash.com/@nasa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">NASA</a> on <a href="https://unsplash.com/@nasa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><h3>Coming back down to earth. Prototype testing</h3><p>After the research and creating a proof of concept, we know that we can technically deliver our idea. Now we need to make sure that the product will function as planned and it will be well-received by the users.</p><p>The essence of <a href="https://www.untitledkingdom.com/services/rapid-prototyping?hsCtaTracking=4c345658-366c-4069-b278-0b76f5a55a25%7Cd4bf9a06-5e45-4c03-a95b-dbfaba39d470">Rapid Prototyping in our Untitled Lab</a> is to verify that our concepts are consistent with what we can offer the user to test, see, touch, and use.</p><p>Most importantly, at this point, we can observe whether the prototype is used with the intent we designed it with. What’s not intuitive? Note that asking questions directly won’t usually get you the same result as seeing the behavior and product use.</p><p>Before we use all the funds for the engineering team to build the final product right away, it’s best to check as many times as possible if we are going in the right direction. Why?</p><p>The engineering part might get expensive (especially regarding the hardware products), particularly when we discover that we need some changes later. Fixing and implementing large conceptual changes once all is ready will be very painful financially.</p><h3>What are software and hardware prototypes?</h3><p>Depending on what we are building (software or hardware prototype) we can start with simple wireframes to illustrate the user journey from A to Z. Putting a little bit more effort can get you a clickable prototype that can be handed to the users for testing. It is significantly more realistic than a piece of paper, but don’t get me wrong; those can work as well.</p><p>The touch and feel experiences are even more critical when it comes to hardware prototypes. In this case, it’s harder to imagine how it will behave, fit, and feel.</p><p>In general, we can divide prototypes into:</p><ul><li>looks like a prototype (focus on user interactions),</li><li>works like a prototype (focus on checking functionality).</li></ul><h3>How to work in teams on the verification of prototypes</h3><h4>Marriage of the product design and engineer team</h4><p>Likely most of the product design and engineering work will be done in parallel. It’s case dependent how those will crossover and interact in the process; no silver bullet here. Of course, there will be some constraints from the design to the engineering team and likewise that we need to remember about. It’s always better to keep everyone in the team working closely together and communicate as often as possible.</p><p>When the product design team is busy gathering feedback from the users and shaping our product, the engineering team can check if the selected technology and architecture can work well together.</p><h4>The Good, The Bad And The Ugly. The Bettered, The Working, The Functional</h4><p>Depending on the nature of software or hardware prototype (hardware won’t probably go without some sort of connected app or backend), we can talk about a “bettered”, working, “roughly” functional version of the product or some kind of a simulator that will provide some data to the rest of our system, so we can see it all working together.</p><p>Instead of developing a complete backend infrastructure, we could also start with a simplified, of the shelf solution. At this point, we can mock and fake some parts of the system. Our goal here is not to build a production-ready product but rather model the whole solution to understand it better and verify our assumptions.</p><h4>What do we get after this phase of product &amp; software development?</h4><p>To sum up, what we can achieve after Phase 3. Prototyping, before we decide on the Phase 4. Feasibility study, is:</p><ul><li>understanding of the system architecture,</li><li>discovering potential problems challenges,</li><li>feedback report after user testing,</li><li>a better understanding of the look and feel,</li><li>design/hardware/software prototypes.</li></ul><h3>Why is Phase 3. Prototyping so important?</h3><p><strong>The product design and engineering path during the prototyping phase are both essential for the project</strong>. They provide crucial information to the team on how to build it in the right way from the user and the technical perspectives.</p><p>All those information will be necessary for four of our next steps and a booming market release and a happy customer base.</p><p>Thanks for reading up to this point, and see you in the next part, <strong>Phase 4. Feasibility study.</strong></p><h3>Read more from the series</h3><p><a href="https://www.untitledkingdom.com/blog/we-choose-to-go-to-an-mvp-7-phases-of-the-software-and-hardware-development-process-inspired-by-nasa">We choose to go to an MVP. 7 phases of the software and hardware development process inspired by NASA</a></p><p><a href="https://www.untitledkingdom.com/blog/phase-1.-research.-software-hardware-development-process">Phase 1. Research. Software &amp; hardware development process</a></p><p><a href="https://www.untitledkingdom.com/blog/phase-2.-proof-of-concept.-software-hardware-development-process">Phase 2. Proof of concept. Software &amp; hardware development process</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de37d7280999" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/phase-3-prototyping-software-hardware-development-process-de37d7280999">Phase 3. Prototyping. Software &amp; hardware development process</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phase 2. Proof of concept. Software & hardware development process]]></title>
            <link>https://medium.com/untitledkingdom/phase-2-proof-of-concept-software-hardware-development-process-56783aec8413?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/56783aec8413</guid>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[proof-of-concept]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Thu, 18 Jun 2020 14:29:05 GMT</pubDate>
            <atom:updated>2020-06-18T14:29:05.046Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>We tend to get blinded by our ideas, goals, and visions.</strong> We think we are infallible, or even omniscient. How to get out of this blindness “and do the other things not because they are easy (…)”? Let’s start from being wrong. What? Yep. Being wrong is sometimes the best place to get started.</p><p>I invite you to the next article in the series about our software and hardware development process. This time I will describe in detail what is important in <strong>Phase 2. Proof of concept</strong>.</p><p>If you haven’t read the previous articles in the series yet, I recommend starting with it to grab the context of our rapid prototyping approach and how does it look like <strong>Phase 1. Research</strong>:</p><ol><li><a href="https://www.untitledkingdom.com/blog/we-choose-to-go-to-an-mvp-7-phases-of-the-software-and-hardware-development-process-inspired-by-nasa">We choose to go to an MVP. 7 phases of the software and hardware development process inspired by NASA</a></li><li><a href="https://www.untitledkingdom.com/blog/phase-1.-research.-software-hardware-development-process">Phase 1. Research. Software &amp; hardware development process</a></li></ol><p>All engines running. Fasten your seatbelts and liftoff!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bNJEA_c-qst9cV6_.jpg" /></figure><p>Photo by <a href="https://unsplash.com/@nasa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">NASA</a> on <a href="https://unsplash.com/@nasa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><h3>Being wrong is right</h3><p>Kathryn Shulz in her book “Being Wrong” talks about that. <strong>Like Coyote chasing the Road Runner in the cartoon</strong>, always at the end of the episode running off the cliff. All is good for him, and he’s still running fine to the moment until he looks down.</p><p>We need to look often down to be sure we are not too far already. From the previous article, we know that we all have those amazing ideas. Ideas that keep us awake at night. Ideas that could be game-changers.</p><p>Once we explore them and have a basic understanding of how those potentially could be brought into life, <strong>we need to prove ourselves and our stakeholders or investors</strong> that it actually can be done.</p><p>Or otherwise, we wouldn’t build a rocket if we didn’t know that you could create an engine that could lift something into space. That engine is our “proof of concept” in the <a href="https://www.untitledkingdom.com/services/rapid-prototyping">software and hardware development process</a>.</p><h3>What is proof of concept</h3><p>Proof of concept is like the foundation of a house or a base for a rocket — if this is unstable, poorly calculated, all further construction may collapse. <strong>Proof of concept is a small sub-project and test </strong>that confirms the goal of the proposed project is viable. At this point, we examine whether it is possible to implement the most innovative part of our idea.</p><h3>Theory vs. practice</h3><p>In the previous phase, we checked different ideas, we wondered in theory how something can be built, and we made a thesis. We are now starting technical tests and verifying what is feasible. This is <strong>the first engineering work</strong> on a hardware product, business or software testing on other solutions.</p><h3>Building or changing a product</h3><p>Testing is especially important when we are building a completely innovative solution that might be a game-changer on the market. <strong>The </strong><a href="https://www.untitledkingdom.com/services/rapid-prototyping"><strong>rapid prototyping process</strong></a><strong> pays off.</strong></p><p>If we are already working on a product, we do not implement the changes immediately, but first, we wonder if they make sense and how they fit into the current solution.</p><h3>What is the effect of proof of concept</h3><p><strong>Proof of concept is often confused with a prototype</strong>, but they have a slightly different meaning and application. Proof of concept is used to check if something works and whether it can be technically created. A prototype is being built to help visualize how the entire product will work. Long story short, it’s “can be done” vs. “how it’s done”.</p><h3>Proof of concept is all about going in the right direction</h3><p><strong>PoC is just a test to provide us with information</strong>, help refute or uphold some theses. Most likely, it will still not be used. A component may come in handy, but here the goal is to check that the idea itself works.</p><p>Proof of concept most likely will be completely scrapped and optimized. <strong>It doesn’t have to be perfect, it’s good enough</strong> to show that the idea can be done and has the potential to keep on going in this direction.</p><h3>Collecting data to move forward</h3><p>At this phase, we collect information on how well the theoretical assumptions of Phase 1. Research can be implemented. We verify <strong>technical possibilities and solutions</strong>, e.g. if it was not possible to create the right pressure in a lactation pump such as Elvie Pump, and it would be necessary to pump 30 min for 1 ml of milk, then we know that this is not the most advantageous solution.</p><p>At Phase 2. Proof of Concept, <strong>we can have several ideas for checking</strong> theses and verification of solutions — we can then compare several proofs of concepts and choose the best one.</p><p>Proof of concept is finally used to quickly explore different approaches and possible solutions.</p><h3>The examples of proof of concept</h3><p>I can give some examples of a well-carried proof of concept process.</p><ol><li><strong>Shazam</strong> music fingerprinting algorithm. By means of a short piece of music, the application is able to match that with a song in a database and provide the artist and title of the song he is currently hearing.</li><li><strong>Elvie Pump</strong> is using <a href="https://patents.google.com/patent/US20180361040A1/en">a piezo air-pump</a> for creating suction. The pump has been innovatively used, which is noiseless and can be pumped smoothly even at work.</li><li>Proof of concept for <strong>iPhone and iPad </strong>was a multitouch screen technology. Thanks to the construction of such a screen and the possibility of its use, work began on the rest of the device.</li></ol><p>For some projects might be a research study on the accuracy of some market/phone available sensors or actuators.</p><h3>What’s next</h3><p>After that phase you should have:</p><ol><li><strong>Technology feasibility</strong>, i.e. proof that we are technically able to meet the assumptions.</li><li><strong>Testing report and data</strong>, i.e. no matter if the experiment was successful or not, we can collect data and use it at later stages and decide whether they are sufficient or need additional tests.</li><li><strong>Physical proof (or model) or source code (or wireframe)</strong>. After this phase, we remain with tangible proof whether it is a piece of code or hardware, something that can already be shown to an investor, for example.</li><li><strong>Performance analysis</strong>. At this phase, you need to verify if the technical performance is sufficient (e.g. Shazam needs a few seconds to verify the song, but if it needed 3 minutes, it would not be so effective).</li><li><strong>Key findings, </strong>depending on the project.</li></ol><p>- — — — — — — — -</p><p>Thanks for reading and in the next article, I’m going to write more about Phase 3. Prototype.</p><p>More about Untitled Kingdom’s <a href="https://www.untitledkingdom.com/services/rapid-prototyping">software or hardware rapid prototyping</a></p><p>See you soon and if you have any feedback, just let me know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56783aec8413" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/phase-2-proof-of-concept-software-hardware-development-process-56783aec8413">Phase 2. Proof of concept. Software &amp; hardware development process</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phase 1. Research. Software & hardware development process]]></title>
            <link>https://medium.com/untitledkingdom/phase-1-research-software-hardware-development-process-6a1a5cdd00c5?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a1a5cdd00c5</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[sofware]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Thu, 18 Jun 2020 10:51:31 GMT</pubDate>
            <atom:updated>2020-06-18T10:51:31.085Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine having a friend who one day comes and says that “I choose to go to the Moon in this decade (…)”. Crazy right?</p><p>We all have those amazing ideas.<strong> Ideas that keep us awake at night</strong>. Ideas that could be game-changers. Which one, however, has a chance to change something on the market and gain users?</p><p>I invite you to the next article in the series about our <a href="https://www.untitledkingdom.com/services/rapid-prototyping">software and hardware development process</a>. This time I will describe in detail what is important in <strong>Phase 1. Research</strong>. If you haven’t read the first article in the series yet, I recommend starting with it to grab the context of our rapid prototyping approach:</p><p><a href="https://www.untitledkingdom.com/blog/we-choose-to-go-to-an-mvp-7-phases-of-the-software-and-hardware-development-process-inspired-by-nasa">We choose to go to an MVP. 7 phases of the software and hardware development process inspired by NASA</a></p><p>All engines running. Fasten your seatbelts and liftoff!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g6DHtsB_TxWCWr5h.jpg" /></figure><p>Photo by <a href="https://unsplash.com/@nasa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">NASA</a> on <a href="https://unsplash.com/s/photos/liftoff?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><h3>Table of contents</h3><p>Have an idea? Try to be its greatest critic and ask yourself a few questions</p><p>What does the Phase 1. Research consist of?</p><ul><li>Start with why and define the problem</li><li>Out of the shadows. How will the product work?</li><li>Decision point. Plan what to test further</li></ul><p>Wrap up</p><h3>Have an idea? Try to be its greatest critic and ask yourself a few questions</h3><p>Before starting a heavy product development journey, we have to start the process by convincing ourselves that there is an opportunity or <strong>try to criticize our own idea</strong>.</p><p>Answering a couple of <strong>simple questions</strong> might help:</p><ul><li><strong>What is the problem that I want to solve</strong>? Is this problem just mine? Who has this problem?</li><li>Are there any better ways to do it? Has anyone tried it already?</li><li>What do others think about my idea? Especially those who have such a problem?</li><li>Can my solution be implemented? How?</li><li>Why do I want to build something?</li></ul><p>The idea behind our Phase 1. Research is to <strong>answer all of those questions</strong> the best we can. And try to “build the specs” from both technical and business (customer requirements) side. We do that by scratching our heads, brainstorming and exploring all the options. Don’t get me wrong. It’s still a fast and iterative process (isn’t it rapid prototyping?), but according to my experience, it is worth to do research responsibly, because it is cheaper than engineering.</p><h3>What does the Phase 1. Research consist of?</h3><h4>Start with why and define the problem</h4><p>We start work by <strong>defining the problem we want to solve</strong>.</p><ul><li>What is driving us, why do we want to help specific people?</li><li>Who will use it?</li><li>How and when people will use it?</li></ul><p>Most often, the beginning of the FemTech project that we work with looks similar. The founder had a health-related problem and couldn’t find a solution on the market, so she decided to create it to help other women with similar issues. If you have a problem that you want to solve, you need to know <strong>how many others you can help</strong>, i.e. how big your target group can be.</p><p>If you don’t have this problem, you need to f<strong>ind relevant people to deepen your knowledge</strong> and try to understand them. The key to success is the user-centric approach from the very beginning, and empathy will help you with this.</p><p>Ask for everything that comes to your mind.</p><ul><li>Where does this problem come from?</li><li>Can it be divided into stages?</li></ul><p>Perhaps someone from your test group will have an idea of how to solve it. <strong>Don’t assume anything, doubt</strong>, try to make a couple of theses, and refute them. <strong>Rely on data</strong>, not opinions.</p><p><strong>Invite experts</strong> to cooperate, look for data, and market research on this topic. Don’t speed up this phase unnecessarily, because if you do not do it well enough later you can overlook a lot and lose. On the other hand, we remain faithful to iterations and frequent verifications of theses in the <a href="https://www.untitledkingdom.com/services/rapid-prototyping">software or hardware prototyping process</a>.</p><p><strong>Check the competition</strong>. Perhaps such a product already exists on the market.</p><ul><li>How does it help people?</li><li>How big is the interest?</li></ul><p>If you are able to do something better — you can go on, but if the problem is at the heart of the idea — it’s worth considering whether it is reasonable to develop it further.</p><h4>Out of the shadows. How will the product work?</h4><p>If you already know that you are able to give new value to the market, you can find for your product or service customers, you need to <strong>deepen the topic</strong> of the product itself.</p><p>It’s the most flexible phase of the whole product &amp; software development because it depends on the case. You need a lot of <strong>brainstorming</strong> to gather all the ideas and possibilities. You should generate as many questions as possible and try to find answers for all of them.</p><ul><li><strong>What is the biggest value of this solution?</strong></li><li>What basic functions should it have, and what will be nice-to-have?</li><li>How will we reach interested customers?</li></ul><p>If on the way we are not able to answer any question, or in the meantime we find that the idea is not worth further development, then it’s more than okay. We will save time and therefore money. You simply can <strong>devote energy to another idea</strong>.</p><h4>Decision point. Plan what to test further</h4><p>Perhaps the research will give us alternative options, and we can now <strong>make a pivot</strong>. That’s fine and it often happens in the product or hardware development process.</p><p>If the idea seems right and worth developing, we should still think about <strong>business constraints</strong>.</p><ul><li>How are we going to earn and when?</li><li>How do we want to fund this idea?</li></ul><p>At this stage, we already have to <strong>plan what we want to test further </strong>(whether it is <a href="https://www.untitledkingdom.com/services/rapid-prototyping">hardware or software</a>).</p><ul><li>What further theses do we want to confirm or refute?</li><li>What will be the priorities?</li></ul><p>Further down the line, we will split more into two distinct paths, as Tyler Mincey from Bolt likes to call them, it’s the “looks-like” path and the “works-like” path.</p><p><strong>The “looks-like” path</strong> is based on:</p><ul><li>discovering the right customer requirements (customer segments),</li><li>creating prototypes, wireframes and ‘fake it till you make it’ renders or models (we check if our presumptions are correct),</li><li>making sure all the presumptions and specifications are correct.</li></ul><p><strong>The “works like “path</strong> is based on:</p><ul><li>finding out how the product engineering side looks like,</li><li>proving, and demonstrating functionalities and building specs.</li></ul><p>Now we can proceed to the second stage of the process, Phase 2. Proof of Concept.</p><h3>Wrap up</h3><p>We start with an idea, but <strong>the execution</strong> is the most important thing. At least until we test, we won’t know if the concept is worth anything.</p><p>As originators, we often succumb to the temptation to trust our idea and implement it too quickly. An engineer who prefers to build and test may have the same approach. However, <strong>it is not worth skipping the research phase</strong>, because it can answer many important questions for further development. It’s also definitely cheaper than prototyping.</p><p>What to keep in mind during <strong>Phase 1. Research of software &amp; hardware development process</strong>?</p><h4>1. Define the problem:</h4><ul><li>What is driving us, why do we want to help specific people?</li><li>Who will use it?</li><li>How and when people will use it?</li><li>Where does this problem come from?</li><li>Can it be divided into stages?</li><li>How does it help people?</li><li>How big is the interest?</li><li>What is the biggest value of this solution?</li><li>What basic functions should it have, and what will be nice-to-have?</li><li>How will we reach interested customers?</li></ul><h4>2. How will the product work:</h4><ul><li>What is the biggest value of this solution?</li><li>What basic functions should it have, and what will be nice-to-have?</li><li>How will we reach interested customers?</li></ul><h4>3. Plan what to test further:</h4><ul><li>How are we going to earn and when?</li><li>How do we want to fund this idea?</li><li>What further theses do we want to confirm or refute?</li><li>What will be the priorities?</li></ul><p>Thanks for reading this.</p><p>This was the second article in the series of Untitled Kingdom’s <strong>software &amp; hardware development process</strong>:</p><p><a href="https://www.untitledkingdom.com/blog/we-choose-to-go-to-an-mvp-7-phases-of-the-software-and-hardware-development-process-inspired-by-nasa">1. We choose to go to an MVP. 7 phases of the software and hardware development process inspired by NASA</a></p><p>Next time we’ll look at Phase 2. Proof of concept.</p><p>If you have<strong> any questions or feedback</strong>, just let me know.</p><p>More about Untitled Kingdom’s <a href="https://www.untitledkingdom.com/services/rapid-prototyping">software or hardware rapid prototyping</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a1a5cdd00c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/phase-1-research-software-hardware-development-process-6a1a5cdd00c5">Phase 1. Research. Software &amp; hardware development process</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We choose to go to an MVP.]]></title>
            <link>https://medium.com/untitledkingdom/we-choose-to-go-to-an-mvp-553a991284a8?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/553a991284a8</guid>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ideas-to-execution]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Wed, 17 Jun 2020 12:29:02 GMT</pubDate>
            <atom:updated>2020-06-17T12:57:36.679Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>We choose to go to an MVP. 7 phases of the software and hardware development process inspired by NASA</strong></h3><p><strong>We have an idea, and we choose to go to an MVP. What’s next? Use NASA’s example and processes to successfully go through all phases of creating a new software or hardware product.</strong></p><p>Creating a product, regardless of whether it is software or hardware, is complicated and complex. It is an ideal environment for creating countless communication, technological, and quality errors. The only remedy can be an efficient process, thanks to which we can be sure that when we start the next phase of work on the product, we have the maximum knowledge and confidence that we are going in the right direction.</p><p>Through a series of articles, I want to show our process from practitioners at Untitled Kingdom. Today I will present it briefly from A to Z, or from (R)easearch to M(VP), while the next time, I will focus on each phase separately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JhuBOS2tZBNOY9fz.jpg" /></figure><h3>Desperate times call for desperate measures</h3><p>Let’s leave Earth for a moment and return to the title where the Moon is missing. Maybe you associate the famous podcast <a href="https://www.bbc.co.uk/programmes/w13xttx2/episodes/downloads">13 Minutes to the Moon</a>, in which stories from the NASA mission to the Moon are told. If you treat it as a regular project, we get an interesting explosive mixture, and at the same time an example of working in an uncertain, changeable, and unrecognized environment:</p><ul><li>in the mission control center sits an incredibly young team, with an average age of 27,</li><li>the team is not limited by schematic thinking, does not use beaten paths, has a fresh approach and faith that nothing is impossible,</li><li>the team is facing extremely ambitious and unprecedented tasks,</li><li>they are all divided into subgroups as distributed teams, operating independently,</li><li>the essence is many iterations, and subsequent attempts are made very quickly and verified by errors in a short time,</li><li>what matters is the speed of response to problems and searching for possible solutions,</li><li>perfect organization prevails, refined launch status check (aka “go / no go poll”) allows minimizing the risk of failure.</li></ul><p>Some believe in comic superheroes, but for most of us at Untitled Kingdom, NASA people were and are the real idols. Why? We implement their approach to work at many levels in software development projects, but it is crucial when creating hardware products from scratch to MVP. Sometimes it really is rocket science.</p><p>“Desperate times call for desperate measures”. It is worth remembering this every day, but currently, in the face of rapid changes on the market and the vision of the crisis, it is especially important to minimize losses and iterate quickly.</p><p>For this reason, at Untitled Kingdom we have developed our own project status check, with subsequent phases of software and/or hardware prototype creation:</p><p>1. Research<br>2. Proof of concept<br>3. Prototype<br>4. Feasibility study<br>5. Design &amp; development<br>6. EVT, DVT, PVT (hardware only)<br>7. MVP</p><p>Let’s go through them briefly. However, we’ll start with the fuel that allows our spaceship to take off. This fuel is the approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*usT-4arNuxkHhQ1D.jpg" /></figure><h3>Rapid prototyping approach. You’ve got the idea? We’ve got a process to prove it</h3><p>Often, in theory, an idea looks good, but when we start working with it, it turns out that we have not anticipated the enormity of factors. Hence, we need to get back to the starting point, and as a result, we lose time, money and energy.</p><p>We are proponents of <a href="https://www.untitledkingdom.com/services/rapid-prototyping">software &amp; hardware rapid prototyping</a> and our most important goal here is the greatest idea of exploration and providing an experience, not a document (and we save trees, right?).</p><p>When creating solutions, especially those that are unprecedented, we must assume high risk, so in order not to invest huge financial resources in an idea that will be a failure, it is best to test it:</p><ul><li>very fast, iteration after iteration,</li><li>with the lowest budget possible,</li><li>with as many tests and errors as possible,</li><li>with the most frequent feedback from users.</li></ul><p>What allows you to go through the entire process of rapid prototyping from idea to MVP successfully are three factors:</p><h4>The Team</h4><p>What’s the most important is extensive collaboration and coordination between specialists in various fields, including design, mobile, software, hardware engineers, QA, product development experts.</p><h4><strong>The Experience</strong></h4><p>We have 12 years of experience on the market as a software and product development company. During software projects, we often had to create simulators, test hardware solutions, which is why we organically developed the competences of electronic, mechanical, and industrial design at Untitled Kingdom under the banner of the Untitled Lab.</p><h4>The Relationships</h4><p>Prototyping involves testing solutions that we are not sure are possible. Therefore, we cannot assume that we have all the necessary equipment in the Untitled Lab.</p><p>Therefore, to create specific components and prototypes, we use previously built relationships with several partners from San Francisco, London, Krakow and Shenzhen, so we can manage the entire process and commission models and components to create if needed.</p><p>So what happens right after starting cooperation with Untitled Kingdom?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tO5HUH7l1v7wFSGy.jpg" /></figure><h3>From research to MVP in a nutshell. The process of creating software &amp; hardware prototypes</h3><p>We can start work from the very beginning, but if you are already in the prototyping phase or just before the release of MVP — we can examine the needs and adapt the process so as not to start from scratch.</p><h4>Phase 1. Research</h4><p><em>We choose to go to the moon in this decade and do the other things (…)*</em></p><p>We start working on a specific idea for software or hardware at the stage where:</p><ul><li>we conduct competitor research on the market,</li><li>we conduct scientific and technological research,</li><li>we acquire knowledge and consult with domain experts,</li><li>we generate as many ideas as possible during brainstorming,</li><li>we build initial theses to test and prove or refute in subsequent phases of software or hardware prototyping,</li><li>we talk with potential users.</li></ul><h4>Phase 2. Proof of concept</h4><p><em>(…) not because they are easy (…)</em></p><p>After the research phase, we begin to develop Proof of Concept (PoC), which in the case of hardware may be the innovative use of a component, the first version of the algorithm, a study of accuracy or sensor measurement. This is one of the smaller parts of the project, but the key one that shows us whether further work will make sense:</p><ul><li>we verify theses</li><li>we decide if the chosen direction is possible to continue,</li><li>we investigate what technology COULD work.</li></ul><h4>Phase 3. Prototype</h4><p><em>(…) but because they are hard (…)</em></p><p>After the initial verification of theses and choosing a possible architecture, we go to <a href="https://www.untitledkingdom.com/services/rapid-prototyping">software or hardware rapid prototyping</a>, i.e.</p><ul><li>we check in reality whether a given technology and architecture work,</li><li>in the case of hardware, a “bettered”, working, “roughly” functional version of the product is created, tailored to customer requirements, which is not even close to being market-ready (box of wires),</li><li>some parts might be simulated/mocked — we want to understand general architecture,</li><li>it is a base for trying other functionalities,</li><li>we conduct the first tests with users, collect feedback.</li></ul><h4>Phase 4. Feasibility study</h4><p><em>(…) because that goal will serve to organize and measure the best of our energies and skills (…)</em></p><p>After checking how the prototype works, we proceed to the second, complementary research, based on specific solutions:</p><ul><li>we research the final available parts and solutions,</li><li>we check technical feasibility, i.e., “evaluation of the hardware and software and how it meets the need of the proposed system”,</li><li>we check legal feasibility, i.e., required certifications or data management,</li><li>calculation of approximate costs of certification, software or hardware development, early BOM (bill of materials),</li><li>we develop time feasibility, i.e., a roadmap,</li><li>we develop a risk analysis.</li></ul><h4>Phase 5. Design &amp; development</h4><p><em>(…) because that challenge is one that we are willing to accept (…)</em></p><p>In the next phase, we iteratively approach the finished product:</p><ul><li>we carry out product work on the design and the combination of software and hardware,</li><li>we build design prototypes,</li><li>if we lack any skills, at this stage, we use an extensive network of Partners responsible for manufacturing, electrical engineering, firmware, industrial design etc.</li></ul><h4>Phase 6. EVT, DVT, PVT</h4><p><em>(…) one we are unwilling to postpone (…)</em></p><p>In the penultimate phase, which concerns only hardware, we go through three seemingly difficult to decipher abbreviations, i.e.</p><ul><li>Engineering Validation Test is the stage where we make a batch of 20–50 product units that are intended for testing. These are looks-like and works-like prototypes; this is a critical moment in which the last shortcomings in the operation of hardware are caught.</li><li>Design Validation Test is a stage in which, after checking the operation of the prototype, 50–200 units are created for broader testing and the last cosmetic corrections. It is also the moment of performing functional tests in various conditions — on fire, water, after falling from a height.</li><li>Production Validation Testing is the first stage of official production. 5–10% of the first units are made, which undergo the last tests but should be ready for release on the market.</li></ul><h4>Phase 7. MVP</h4><p><em>(…) and one which we intend to win (…).</em></p><p>In the last phase, right after Production Validation Testing, we are ready to celebrate and first public release our Minimum Viable Product into the world (and space).</p><p>At this stage, we are finishing the development of MVP, starting with the idea, but the fun with <a href="https://medium.com/services/rapid-prototyping">product &amp; software development</a> is just beginning here, just as setting foot on the Moon was only the beginning of space conquests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ufqi0CIjfabKoMOx.jpg" /></figure><h3>Wrap up</h3><p>In the article I wanted to briefly present our own project status check at Untitled Kingdom, inspired by NASA, along with the subsequent phases of creating a <a href="https://www.untitledkingdom.com/services/rapid-prototyping">software and/or hardware prototype</a> from a bird’s eye view:</p><ol><li>Research</li><li>Proof of concept</li><li>Prototype</li><li>Feasibility study</li><li>Design &amp; development</li><li>EVT, DVT, PVT (hardware only)</li><li>MVP</li></ol><p>In subsequent blogposts, I will deepen each of the phases, present our approach, and share our experience.</p><p>Thanks for reading so far and if you have any feedback or question, I will gladly answer it: <a href="/service/mailto:bartek@untitledkingdom.com">bartek@untitledkingdom.com</a></p><h4><a href="https://www.untitledkingdom.com/blog">Read more about creating products on our blog</a></h4><p>* All quotes are from President John Kennedy’s Rice Stadium moon speech: <a href="https://er.jsc.nasa.gov/seh/ricetalk.htm">https://er.jsc.nasa.gov/seh/ricetalk.htm</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=553a991284a8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/we-choose-to-go-to-an-mvp-553a991284a8">We choose to go to an MVP.</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security issues in software development with examples (including Amazon, Apple, Snapchat)]]></title>
            <link>https://medium.com/untitledkingdom/security-issues-in-software-development-with-examples-including-amazon-apple-snapchat-76375938d52d?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/76375938d52d</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Mon, 30 Sep 2019 14:43:35 GMT</pubDate>
            <atom:updated>2019-09-30T14:43:35.470Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*htl9f_huDpRUf2pDyLtXLw.jpeg" /></figure><h3>Security issues in software development with examples (including Amazon, Apple, Snapchat). Policy, threat model, mechanism</h3><p>At the end of the cycle of articles on <a href="https://www.untitledkingdom.com/services/software-development">software security</a>, let’s look closer into each of its categories that we need to defend against, which are <strong>policy issues</strong>, <strong>threat modeling</strong> and <strong>defense</strong> <strong>mechanism</strong>. I will give real examples to each of them from Amazon, Apple, Yahoo, Snapchat, Tinder and WhatsApp history.</p><p>If you haven’t had a chance to read my previous articles on security yet, I invite you to read them too:</p><ul><li><a href="https://www.untitledkingdom.com/blog/reflections-on-code-quality.-confession-of-a-cto">Reflections on code quality. Confession of a CTO</a></li><li><a href="https://www.untitledkingdom.com/blog/building-a-top-notch-software-development-team.-confession-of-a-cto">Building a top-notch software development team. Confession of a CTO</a></li><li><a href="https://www.untitledkingdom.com/blog/is-your-product-or-service-secure-what-makes-you-think-that-and-who-is-responsible-for-it-actually">Is your product or service secure? What makes you think that and who is responsible for it actually?</a></li><li><a href="https://www.untitledkingdom.com/blog/how-to-take-care-of-security-in-software-development-software-development-life-cycle">How to take care of security in software development? Software Development Life Cycle</a></li></ul><h3>Policy issues with examples</h3><p>A policy is a statement of what our system is supposed to do and all the goals we are trying to achieve at some point. For example, it’s about confidentiality — who will have access to certain parts of the system. What’s more, important is integrity and modifying data or content but also availability to our users.</p><p>For example, saying that account X should have access to our admin panel is completely different policy than saying that no one else except account X can have access to our admin panel.</p><p><strong>Real-life example can be a security question to reset accounts password.</strong> Knowing a password might be one thing but adding personal info like school, dog names etc. changes the deal. Especially for famous or public people. Years ago there was a case of Sarah Palin and her <strong>Yahoo account</strong>. Someone just simply figured out that all answers for all of those questions can be found on her Wikipedia account.</p><p>On <strong>Amazon</strong>, there was a case where you could buy something without logging in, by simply providing credit card details and account email and later use that new card info to reset the password.</p><p>Next, you could have used the previous card last 4 digits to reset someone’s <strong>Apple account</strong> if u were lucky. That could have been a backup account for Google for example. I’m not joking, that was actually a case in the past.</p><p><a href="https://www.untitledkingdom.com/uk-security-checklist">Download Security Checklist and ask those 60 questions in your company to be up to date with the best security practices.</a></p><h3>Threat modeling issues with examples</h3><p>A threat model is basically knowledge about the adversary. All the techniques, points of access and possible motivation for bad guys trying to compromise our data. It’s basically trying to look through their eyes on our software to understand which parts should be specially taken care of. Good start for a risk assessment and for the team to look at the system holistically.</p><p>We should never assume that users passwords are safe, in most cases even with our password requirements. That’s why we should be extra careful about users access rights.</p><p>Another thing is that <strong>computing power is increasing every year</strong>. Not updating, i.e. our encryption algorithms can be catastrophic over time. Like with Kerberos protocol developed on MIT in the mid-80s. Not using certificate pinning might mean that the bad guy needs to compromise just one certificate authority in the world.</p><p>The <strong>Defense Advanced Research Projects Agency</strong> (DARPA) was super sure that they created a secure system that they hired a bunch of people to try and break it. One of the teams has discovered that the system codebase is on a server in one of the employee rooms and its security wasn’t best. So they broke in there, created a system backdoor in code, waited for the nest release and use that to compromise the system later on.</p><h3>Mechanism issues with examples</h3><p>Mechanisms concern all the software and hardware solutions that are making sure our policy is followed as long as the bad guy is following our assumptions from the threat modeling.</p><p>Again, I will point out that it’s impossible to secure our system so it is unbreakable. It’s a matter of making it really hard at least in a reasonable timeframe for them. Let me refer to more modern mobile problems that were discovered in recent years. By the way, all of them are already fixed.</p><p><strong>Snapchat’s</strong> idea was to remove messages after a certain amount of time. It was done by sending a remove request from the client. Because it was optional, there were created a couple of apps using Snapchats API exploiting that vulnerability and then there was a leak of thousands of photos from those third-party servers.</p><p><strong>Tinder</strong> as a dating app was showing (and still is) distance to your matches. It’s okay the distance is only an approximation, but as it turned out internally in a response from the API, there was for each match the exact last-long location provided. And that was not cool. So, of course, they have fixed that first by just sending only the distance that was being calculated on the server side so no locations in the response anymore. But another mistake was that that distance was provided with 15 digits accuracy. With that precision, you can easily find the users through knowing 3 different locations and trying to triangulate the exact locations of a particular match. Later on, also that problem was resolved.</p><p><strong>WhatsApp</strong> is another interesting example and a super successful product with billions of users. Messaging apps, in general, are a category themselves in security, but let’s focus on this one. Following vulnerabilities were found when it already had a dozen of millions of users. Firstly, the number verification process. It’s a great idea that prevents someone else from using our private number. It turned out that verification code was created on the client (mobile) side and sent to a service, to then send it back as an SMS with that exact verification code to a specified number. It meant with a single device an attacker could easily verify every given number in the app. Also as a bonus, because there was no validation on that verification code that API could be used to send free SMS to any number worldwide. 120 characters were the limitation of an SMS itself, minus, a couple of words from WhatsApp.</p><p>Someone else has discovered that to change app number status you don’t need to authenticate, it was a simple GET request. It was super simple to change anyone’s status to whatever we wanted. There was even a website where you could do that easily. What is pretty scary was that the first quick fix was just to block all requests just from that website…</p><p>Also remembering to limit the number of requests is important. Especially for signing in purposes. Apple once had a problem with that, and because usually user passwords are rather simple it was very easy for someone to brute force all possible combinations. For WhatsApp, it was an API to retrieve statuses when uploading the contact book. In one request you could easily get millions of statuses for real phone numbers. Just imagine what a marketing tool that could have been…</p><h3>Wrap up</h3><p>At the end of my series of articles on various aspects of software security, <strong>I listed recent examples worth remembering when creating policies, threat models and mechanisms</strong>, including mishaps of Amazon, Apple, Yahoo, Snapchat, Tinder and WhatsApp.</p><p>The purpose of the series was of course not to teach how to write a secure system. It would be impossible! My idea is to evangelize security to raise awareness and educate people that should feel responsible for those tasks in their companies, so they would try to introduce some security-related activities into their process of software and hardware development.</p><p>Building a product for months or years and then losing everything in just one day isn’t the best idea. That’s why it’s way better to prevent things from happening or at least trying to minimize the probability of it happening in production.</p><p>Dance like nobody’s watching. Encrypt like everyone is.</p><p><strong>Read more from the software security series:</strong></p><ul><li><a href="https://www.untitledkingdom.com/blog/reflections-on-code-quality.-confession-of-a-cto">Reflections on code quality. Confession of a CTO</a></li><li><a href="https://www.untitledkingdom.com/blog/building-a-top-notch-software-development-team.-confession-of-a-cto">Building a top-notch software development team. Confession of a CTO</a></li><li><a href="https://www.untitledkingdom.com/blog/is-your-product-or-service-secure-what-makes-you-think-that-and-who-is-responsible-for-it-actually">Is your product or service secure? What makes you think that and who is responsible for it actually?</a></li><li><a href="https://www.untitledkingdom.com/blog/how-to-take-care-of-security-in-software-development-software-development-life-cycle">How to take care of security in software development? Software Development Life Cycle</a></li></ul><p><a href="https://www.untitledkingdom.com/blog/security-issues-in-software-development-with-examples.-policy-threat-model-mechanism"><em>The blogpost was originally published on Untitled Kingdom’s blog.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76375938d52d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/security-issues-in-software-development-with-examples-including-amazon-apple-snapchat-76375938d52d">Security issues in software development with examples (including Amazon, Apple, Snapchat)</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SSDLC and risk assessment in software development]]></title>
            <link>https://medium.com/untitledkingdom/ssdlc-and-risk-assessment-in-software-development-d71cd07e10dd?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d71cd07e10dd</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[risk-assessment]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Mon, 15 Jul 2019 10:44:18 GMT</pubDate>
            <atom:updated>2020-06-29T09:40:22.209Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uwu3boSjNXJUKKK5_uR3_g.jpeg" /><figcaption>Photo: <a href="https://www.untitledkingdom.com/">Untitled Kingdom</a></figcaption></figure><p>Security is very important during <a href="https://www.untitledkingdom.com/services/software-development">software development</a>, exceptionally when working with <a href="https://www.untitledkingdom.com/digital-health-new">digital health</a>, <a href="https://www.untitledkingdom.com/industries/iot">IoT</a> and <a href="https://www.untitledkingdom.com/digital-transformation">digital transformation</a> projects, where you have to face a ton of sensitive user data.</p><p>Prevention is better than cure, so after over a decade in software engineering and business, I discovered what is the key to a secure software development</p><ul><li>What is SSDLC and what does it consist of?</li><li>What is a reasonable approach?</li><li>Why important are threat modeling and risk assessment?</li><li>What are high-risk domains and how to handle them?</li><li>Who should be responsible for security in your company?</li></ul><h3>What is Secure Software Development Life Cycle (SSDLC)?</h3><p>SSDLC, in a nutshell, means that we won’t wait with security-related activities till the end of the development. The idea is to have them integrated into our process all the way.</p><p>With that in place, it’s way easier to create <a href="https://www.untitledkingdom.com/services/software-development">secure software</a> as security is a continuous concern, detect early flaws in the system, reduce costs as a result of early detection and resolution of issues and an overall reduction of intrinsic business risks for the organization by raising awareness of security considerations by stakeholders.</p><p>There are definitely some actions that can be taken by developers or testers in their day-to-day activities to improve the security posture of your organization. Like introducing static and dynamic code analysis tools, penetration testing, defining security requirements or performing threat modeling.</p><p>Although I want to emphasize this very strongly here that it’s our <strong>responsibility as </strong><a href="https://www.untitledkingdom.com/services/cto-as-a-service"><strong>CTOs </strong></a><strong>or managers to educate ourselves and co-workers on the best secure coding practices</strong> and available frameworks for security.</p><p><strong>Becoming paranoid with security, on the other hand, is also not a good idea</strong>, as with all extremes. I mean it would be great for all products but unless we are not a bank or any ultra-specific data processing company it&#39;s recommended to stay reasonable with our actions.</p><p>As I mentioned earlier <strong>it’s practically impossible to identify every potential system flow</strong>. We should put enough effort to try to <strong>identify the most crucial ones</strong> especially, without spending horrendous amounts of time. There are a couple of techniques that can be used that will help us get the knowledge about or system holistically and also identify the areas where risk might be the highest. And then we can focus more only on those specific areas. We should end up with a <strong>list of all risks (all important ones) </strong>that are connected to our product. Next step is to assign to each of them the <strong>cost of failure that it can generate</strong> — the expected loss, and also what is the <strong>level of predicted probability </strong>of it happening in production.</p><p>With that done it’s very easy to prioritize all of them. <strong>Only those with high effect should be considered as ones to apply countermeasures</strong>. Of course, it all depends on the available resources. So a classic risk assessment job. If you are not familiar with how it works you can discuss it in more details with me.</p><p>The cool part is that <strong>it gives a holistic view of the system as a whole</strong>, raising awareness among developers about potential problems and even show possible wrong use cases we could have forgotten about.</p><h3>What are the high-risk domains?</h3><p>Risk assessment is a good exercise for every project but if your solution uses one of the following areas of technology I would say it&#39;s a must-have in a development process!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cc8exApLG6iB4ftp_l_qBQ.jpeg" /></figure><h3>Data storage</h3><p>The one of the top and obvious ones are of course <strong>data storage</strong> of any kind. It might be local or in the cloud. Almost every app or piece of software is meant to hold and process some sort of data that needs to be stored somewhere. In most cases, we deal with users very private and confidential information. <strong>It’s our responsibility to make sure that those data will be a top secret, and</strong> we won’t share or give access to them to any third party without our and our users’ knowledge.</p><p>The concept and practice of <strong>securing storage are gaining momentum</strong>, but it still hasn’t taken off really. I really don’t understand that especially if you look at the business risk that it brings. Storage vulnerabilities are a fact. What is worse is that many of them are very easily exploited, meaning someone gets access to all collected data.</p><p><strong>The real business risks are associated with compromising databases, not data that we are sending there. </strong>But it doesn’t mean we should forget about protecting sensitive information as it crosses the wire or the airwaves. Although communication itself isn’t the worst part usually as <strong>SSL and OAuth are pretty standard now</strong>, definitely for particular kind of products is super crucial.</p><h3>Scale problem</h3><p>The real challenge is to make sure we prevent all users&#39; data vs. just single user data, which usually comes down to designing and developing <strong>secure backend API</strong> — as that’s the place where all collected and hopefully encrypted data is gathered and accessible.</p><h3>API is the key</h3><p>A secure API is one that can make sure of the privacy of the data that it deals with by making it visible only to the Users, Apps, and Servers that are authorized to consume it. Likewise, it has to be able to <strong>take care of the integrity of the data it receives from other servers and clients </strong>with which it talks directly to.</p><p>Those two aspects are essential for a reliable API.</p><h3>Mobile apps</h3><p>If our business has a mobile application might be worth mentioning that environments our apps may be running on may vary from those officially released systems. <strong>Jailbreaks and rooted devices are still a thing </strong>in today’s world, and we have to remember that permissions on those systems are completely different from official secure releases.</p><h3>3rd party software</h3><p>Every running software including the ones from our products is constructed from code by developers. They might be using external 3rd party libraries and frameworks to optimize their work or support external services. It’s also important to <strong>check if those 3rd party additions are secure, and updated on a regular basis</strong>.</p><h3>Product intellectual property</h3><p>There might be cases like with games for example that we want to be sure that n<strong>o one is going to try to modify</strong> them in their favor or to distribute omitting us, <strong>or again steal our technology/work</strong> to create competitor product.</p><h3>Cryptography/Encryption</h3><p><strong>Cryptography &amp; Encryption Key Management</strong> is closely connected to software security. It’s just important to mention that there should be a policy to be sure to update them once in a while. Technology might change and we should be ready for that.</p><h3>Human factor</h3><p>And most of the time <strong>the weakest link in the chain is a human</strong>. It’s OK we all make mistakes, it makes us humans. We just need to be aware of that and counteract. Things like <strong>storing and sharing important keys and credentials are the things we don’t think abou</strong>t. The most secure system won’t win if someone is just gonna simply take over admin credentials from someone. Creating office policy in terms of communication and data importance is as essential as secure data encryption.</p><h3>Summary</h3><p>So as you can see, almost everybody should care about security when building software. The last and good motivation for everyone might be different regulations of data storing that might result in millions of dollars of fines.</p><p>Security is an endless fight. If we are going to forget about one thing that is going to be exploited, should be a way easier to fix and won’t look as bad as just having everything on a plate waiting to be taken. Especially when explaining ourselves before investors or company board. Also, a security audit is part of a process of due diligence.</p><p>A business should have one person responsible for security matters. Without a dedicated person that responsibility will usually be handled by a <a href="https://www.untitledkingdom.com/cto-as-a-service">CTO</a> or head of technology.</p><p>Check my previous articles connected to this topic:</p><ul><li><a href="https://www.untitledkingdom.com/blog/how-to-take-care-of-security-in-software-development-software-development-life-cycle">How to take care of security in software development? Software Development Life Cycle</a></li><li><a href="https://www.untitledkingdom.com/blog/is-your-product-or-service-secure-what-makes-you-think-that-and-who-is-responsible-for-it-actually">Is your product or service secure? What makes you think that and who is responsible for it actually?</a></li><li><a href="https://www.untitledkingdom.com/blog/building-a-top-notch-software-development-team.-confession-of-a-cto">Building a top-notch software development team. Confession of a CTO</a></li></ul><p>If you share my ideas or have a question about security, please leave a comment.</p><p>If you have a project to discuss, <a href="https://www.untitledkingdom.com/services/cto-as-a-service">find out what I can do for you as a CTO</a>.</p><p>Here you can find my articles regarding code quality and building software development teams:</p><ul><li><a href="https://www.untitledkingdom.com/blog/reflections-on-code-quality.-confession-of-a-cto">Reflections on code quality. Confession of a CTO</a></li><li><a href="https://www.untitledkingdom.com/blog/building-a-top-notch-software-development-team.-confession-of-a-cto">Building a top-notch software development team. Confession of a CTO</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d71cd07e10dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/ssdlc-and-risk-assessment-in-software-development-d71cd07e10dd">SSDLC and risk assessment in software development</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to take care of security in software development? Software Development Life Cycle]]></title>
            <link>https://medium.com/untitledkingdom/how-to-take-care-of-security-in-software-development-software-development-life-cycle-5af2d6e58f6c?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5af2d6e58f6c</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Wed, 19 Jun 2019 11:48:49 GMT</pubDate>
            <atom:updated>2020-06-29T09:54:06.476Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e0-An0PfESHKsNzGY6eOrw.jpeg" /><figcaption><a href="https://www.untitledkingdom.com/">Untitled Kingdom</a></figcaption></figure><p>Recently security becomes a big thing. Finally! Unfortunately, there had to be a lot of spectacular failures for some people to notice that it might be a problem for their businesses as well.</p><p>After <strong>over a decade in </strong><a href="https://www.untitledkingdom.com/services/cto-as-a-service"><strong>software engineering</strong></a> and business, I gathered a bunch of my thoughts about the most common obstacles through which security is compromised.</p><h3>Software Development Life Cycle</h3><p>It is very easy to forget about security aspects as during development nothing will go very wrong to bring our attention and approach to development usually stays the same. There has been some changed and improved over time to Software Development Life Cycle, for example, <strong>moving from Waterfall to Agile methodologies</strong>, but one problem remains the same. It is a common practice to perform a security-related tasks at the end of the process, if at all.</p><p>This after-the-fact technique usually results in a high number of issues discovered way too late (or not found at all). It is a far better practice to <strong>integrate security-related activities across the SDLC</strong> to help detect and reduce vulnerabilities early, effectively building security in, and raising awareness throughout the whole team that it’s not something we will take care later on.</p><p>There are a lot of different reasons why such practices are widespread, especially in a startup world. Let me point out a few to give you a perspective, or maybe it is going to be a yellow flag sometimes to make sure that everything is going in the right direction.</p><h3>Unrealistic deadlines</h3><p>First and the most common bad practice is <strong>setting unrealistic deadlines</strong> to cut costs and stay ahead of the competition. Such an approach puts a lot of pressure on developers that need to try to find shortcuts to deliver features no matter at what cost. And even when they don’t, it’s still very easy to produce little coding mistakes that will come out at some point in such an environment. Especially when no tests are performed over the development time and before the release of the product to the market.</p><h3>Lack of knowledge</h3><p>Another thing is sometimes the <strong>lack of knowledge and awareness about security</strong> throughout developers. In big corporations, there are teams of developers working together in specific areas of software development. In smaller companies, developers usually have to have a broader knowledge to be able to fulfill feature requirements.</p><p>Security aspects are a whole another area of knowledge. It’s not that they don’t want to create great software, most of the time they do, but very often without even thinking about it. That’s why one of the CTO’s roles is to raise awareness of the importance of software security. On the other hand, <strong>it’s not smart to require 100% secure systems</strong>, that would be a waste of time and money. With a proper risk assessment, we only take care of the most crucial parts of our systems.</p><h3>Development in isolation</h3><p><strong>It’s not a good idea to </strong><a href="https://www.untitledkingdom.com/services/software-development"><strong>develop software</strong></a><strong> in isolation.</strong> What I mean by that is that usually a system consists of several different parts — server, mobile, hardware, etc. — and each developer working on his part is not looking at the system holistically, and might not see threats that this brings, like validation, or limiting the number of requests to log in. Wrong assumptions that someone else is going to take care of that is usually false. And just because in a different project it was implemented in a certain way this doesn’t mean it will work this time. That is another <strong>role of CTO to make sure everyone understands the whole product and not just the parts of it</strong>. That can also lead to forgetting to cover specific scenarios which might get exploited by the attacker.</p><p>Of course, if developers don’t follow known excellent software development standards, it’s the whole another problem and our responsibility is to make sure that the quality of software used and created for our solution is on a right level.</p><h3>No security review policy</h3><p><strong>Quite dangerous might be forgetting about security after our </strong><a href="https://www.untitledkingdom.com/services/digital-product-design-development"><strong>product</strong></a><strong> is launched as well.</strong> Even if all tests and development process went smooth and according to current standards. Unfortunately sometimes, for example, with <strong>encryption algorithms, those might get outdated over time</strong>. Computing power is increasing every year, and sometimes bugs and security loopholes are discovered in “secure” in their times’ algorithms of frameworks. It’s essential to have a process in place requiring a review of our system once in a while.</p><p><strong>Situations, where no QA or testing procedures are involved in the development, are unacceptable</strong>! It’s like jumping out from a plane without a parachute. Chances that we are going to land on a stack of pillows are close to zero.</p><p><strong>What to do to care about security in software development?</strong></p><ol><li>Think about your Software Development Life Cycle and find out what you can improve. Prepare a list of priorities and plan to implement changes.</li><li>Set realistic deadlines because mistakes will come to light at the least expected time and will cost you dearly.</li><li>Find one person responsible for security in your company because otherwise the responsibility could be blurred. Most often such a person should be a CTO.</li><li>Don’t develop software in isolation. It’s really important to create an environment where there is a smooth knowledge flow between developers working on different aspects of the project.</li><li>Don’t forget about the security review policy, because IT market is evolving constantly.</li></ol><p>_____________________________________</p><p>Check my previous article <a href="https://www.untitledkingdom.com/blog/is-your-product-or-service-secure-what-makes-you-think-that-and-who-is-responsible-for-it-actually">Is your product or service secure? What makes you think that and who is responsible for it actually?</a></p><p>In my next articles I’ll tell you:</p><ul><li>What is SSDLC and risk assessment? How to implement them?</li><li>Security issues in software development (policy, threat model, mechanisms) with examples.</li></ul><p>____________</p><p>If you share my ideas or have a question about security, please leave a comment.</p><p>If you have a project to discuss,<a href="https://www.untitledkingdom.com/services/cto-as-a-service"> find out what I can do for you as a CTO</a>.</p><p>____________</p><p>Here you can find my articles regarding code quality and building software development teams</p><ul><li><a href="https://www.untitledkingdom.com/blog/reflections-on-code-quality.-confession-of-a-cto">Reflections on code quality. Confession of a CTO</a></li><li><a href="https://www.untitledkingdom.com/blog/building-a-top-notch-software-development-team.-confession-of-a-cto">Building a top-notch software development team. Confession of a CTO</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5af2d6e58f6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/how-to-take-care-of-security-in-software-development-software-development-life-cycle-5af2d6e58f6c">How to take care of security in software development? Software Development Life Cycle</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is your product or service secure?]]></title>
            <link>https://medium.com/untitledkingdom/is-your-product-or-service-secure-d22b50b90e73?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d22b50b90e73</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Mon, 10 Jun 2019 15:15:50 GMT</pubDate>
            <atom:updated>2020-06-29T09:47:17.240Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rBiCzqtRzcJNlLHu" /><figcaption>Photo by <a href="https://unsplash.com/@arvinfebry?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">arvin febry</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Is your product or service secure? What makes you think that and who is responsible for it actually?</h3><p>I have <strong>over a decade of experience</strong> in software engineering. At the beginning of my career, I was a software developer, and now I’m a Head of Technology at <a href="https://www.untitledkingdom.com/">Untitled Kingdom</a>, a <a href="https://www.untitledkingdom.com/product-development">product</a> &amp; <a href="https://www.untitledkingdom.com/services/software-development">software</a> company. Apart from other activities, I have a mission to evangelize and pay attention to the relevance of security and its business aspects.</p><p>I’ll share with you my knowledge and experience in a series of articles regarding this important matter.</p><h3>What is security? What makes you think that your product or service is secure?</h3><p>Let’s start with a couple of simple questions I would like you to ask yourselves in your heads:</p><ul><li>Do you think the products or services you provide and create are secure right now?</li><li>What makes you think they are secure?</li><li>You might think they are or are not, but what is your answer based on?</li><li>What kind of information or processes do you have in place to answer in all honesty?</li><li>Do you have a holistic vision of the whole system or just its parts in isolation?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/285/0*JTRhMAq6sIsY_eRD.jpg" /><figcaption><a href="https://www.untitledkingdom.com/uk-security-checklist">Download our full checklist here</a></figcaption></figure><p>Why am I asking? We are living in times when there are a lot of startups trying to create something revolutionary, pioneer, in one of the upcoming tech areas, be the first one to offer something new, be ahead of the competition. That’s understandable, but unfortunately often leads to forgetting or at least postponing any efforts to make sure our users and our business are secure.</p><p>The problem is sometimes it might be too late for that. The best case scenario is that we might lose users trust, and that is very difficult to regain. The worst case? In production? You can imagine, implications might be catastrophic for the business. Also, making sure to meet all the necessary regulations for a given market is another thing to remember. GDPR for example. All in all millions in fines or lawsuits…</p><p>Security itself is a vast topic, trying to cover everything in one article is impossible. That’s why <strong>I’ve prepared a series of blog posts where I would like to focus on why should we care about it and show you real-world examples how simple mistakes can lead to considerable problems</strong> to raise your awareness and try to show you what might be the first steps and who should be responsible for it in your organization.</p><h3>What is security?</h3><p>What exactly I mean by the word ‘security’?</p><p>The most straightforward definition is that ‘<strong>Security is all about achieving a particular goal when there is an adversary present</strong>’.</p><p><strong>So think of it as a bad guy trying to do something wrong with your system, app or data.</strong> It might be, i.e. shutting the entire system down, stealing and sharing users private data or your business data, trying to use/steal your technology to build a competitor product.</p><p>So again secure systems are the ones that can do something when whatever a bad guy is trying to do with it. That is why we need to apply some countermeasures and mitigations against hackers or anyone trying to compromise whatever we have achieved.</p><p><strong>Of course, I am not asking anyone to know everything about the security and try to do everything on your own. </strong>That would be impossible, and almost certainly there is not a single 100% secure system on the planet — it just might be a matter of millions of years to hack it ;). It’s a constant fight between us creators and the bad guys. <strong>It’s about being aware of all the risks and costs that come with them </strong>to minimize the chances for something to go wrong, to something awful hits the fan.</p><p>Small problems are way easier to fix. Also, earlier you want to change or improve something the easier and cheaper it is. As Brian Tracy puts it: ‘<strong>Every minute you spend in planning saves 10 minutes in execution; this gives you a 1000% Return on Energy!</strong>’.</p><p>Some aspects we should be able to handle ourselves and some it’s definitely better to outsource to security experts if we decide that it’s something we should take care of or at least test properly before releasing to the public.</p><h3>Who is responsible for security in your company?</h3><p>So who is responsible for security matter in your business you may ask?</p><p>Naturally, you could think that because developers and engineers are the ones to design, create and maintain the system, they should be the ones to raise awareness and take care of all the security aspects. Well, that is true — partially. They are the ones to apply some countermeasures in code, no doubt about that.</p><p><strong>However, in every company and business, there should be someone who’s the driving force for the technological part of the company.</strong> The one to keep the business ahead of the latest cybersecurity and tech trends. <strong>I guess you can ask if that also falls to the CTO responsibilities, to both manage and overcome the connected threats as well.</strong> Well indeed, CTOs are fundamentally not doing their job if they don’t achieve this!</p><h3>Summary</h3><p>How to start dealing with security in your company? Firstly, try to think about it and honestly <strong>answer those questions</strong>:</p><ul><li>Do you think the products or services you provide and create are secure right now?</li><li>What makes you think they are secure?</li><li>You might think they are or are not, but what is your answer based on?</li><li>What kind of information or processes do you have in place to answer in all honesty?</li><li>Do you have a holistic vision of the whole system or just its parts in isolation?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/285/0*_N16u9ChUw3fux_8.jpg" /><figcaption><a href="https://www.untitledkingdom.com/uk-security-checklist">Download our full checklist here</a></figcaption></figure><p><strong>If you are interested in getting a </strong><a href="https://www.untitledkingdom.com/uk-security-checklist"><strong>full checklist with 60 questions</strong></a><strong> that you should answer in your company regarding security, you can download it here on our </strong><a href="https://www.untitledkingdom.com/uk-security-checklist"><strong>Security Checklist</strong></a><strong> site.</strong></p><p>Check your processes and people responsible for different aspects of security. Find one person who will be liable for it at the highest level.</p><p>As they say, people are divided into those who make backups and those who will make them. It is the same with security.</p><p><strong>In my next articles I’ll tell you:</strong></p><ul><li>How to take care of security during software development.</li><li>What are SSDLC and risk assessment? How to implement them?</li><li>Security issues in software development with examples. Policy, threat model, mechanisms.</li></ul><p>____________</p><p>If you share my ideas or have a question about security, please leave a comment.</p><p>If you have a project to discuss, <a href="https://www.untitledkingdom.com/services/cto-as-a-service">find out what I can do for you as a CTO</a>.</p><p>____________</p><p>Here you can find my articles regarding code quality and building software development teams</p><ul><li><a href="https://www.untitledkingdom.com/blog/reflections-on-code-quality.-confession-of-a-cto">Reflections on code quality. Confession of a CTO</a></li><li><a href="https://www.untitledkingdom.com/blog/building-a-top-notch-software-development-team.-confession-of-a-cto">Building a top-notch software development team. Confession of a CTO</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d22b50b90e73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/is-your-product-or-service-secure-d22b50b90e73">Is your product or service secure?</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a top-notch software development team. Confession of a CTO]]></title>
            <link>https://medium.com/untitledkingdom/building-a-top-notch-software-development-team-confession-of-a-cto-1add155cb869?source=rss-e80fb5eabb6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1add155cb869</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Bartek Hugo]]></dc:creator>
            <pubDate>Mon, 20 May 2019 08:25:45 GMT</pubDate>
            <atom:updated>2020-06-24T08:01:53.669Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zEgWJPylL4VsYbe2" /></figure><p><strong>What influences the code quality?</strong> Is it just the responsibility of developers? They need to be passionate about their work or just be experienced? <strong>What makes developers bad? </strong>How to maintain the best security of their work? How to manage their work? <strong>How to estimate software development?</strong></p><p>These are the questions that every person responsible for building a <a href="https://www.untitledkingdom.com/services/software-development">software development</a> team has to answer.</p><p>After 11 years of experience as a software engineer and then as a<a href="https://www.untitledkingdom.com/services/cto-as-a-service"> CTO of a software company Untitled Kingdom</a>, I want to share with you more thoughts regarding key challenges in building software teams.</p><p>If you are more interested in the topic, here you can find my <a href="https://www.untitledkingdom.com/blog/reflections-on-code-quality.-confession-of-a-cto">first article about code quality.</a></p><h3>DON’T CHOOSE BETWEEN PASSION OR EXPERIENCE IN SOFTWARE DEVELOPMENT. YOU NEED THEM BOTH</h3><blockquote>If the software is being used and further evolved during 5, 10 years, many people will try to work on it, and each of them will struggle with those problems and pay for them with time when trying to understand the code, when trying to modify the non-modular, amorphic, copy&amp;paste code absolutely unfit for any evolvability, and finally when hunting bugs caused by those failed attempts. And the time of those people is quite expensive and it is the customer, originally supposed to profit from the quick hack solutions, who pays the bill.</blockquote><blockquote><em>Jakub Holý, quotation from his blogpost </em><a href="https://blog.jakubholy.net/2011/04/02/code-quality-matters-to-the-customers-a-lot/">Code quality matters to the customers. A lot.</a></blockquote><p>So there is one of the most common problems for young startups and companies, especially when there is a lack of technical knowledge, which can be used to verify if the codebase quality is doing ok. Let me explain.</p><p><strong>Experienced developers and companies know their value. </strong>And even though at first sight it might sound like its a lot, compared to wasted time, money and nerves you can end up with working with someone passionate but inexperienced. <strong>But remember that a higher price doesn’t have to mean better quality. </strong>It’s always necessary to do your research.</p><p>If you are a technical person, you can, of course, verify the approach and knowledge by yourself. So what to do when you lack that valuable knowledge? Try to look for someone in your friends’ network that could help you or at least look for some references that could express their opinion and experience with a particular team, person or company.</p><h3>SECURITY AND IMPORTANCE OF REFACTORING</h3><p>Talking about security, its recommended to have a process to check those things once in a while. Most often our apps evolve and pivot over time. Continually adding and changing features sometimes makes it difficult for the codebase to keep up with the concepts that developers have designed initially without that knowledge. That is why it’s best to take it into account in a <a href="https://www.untitledkingdom.com/services/software-development">software development</a> process as a regular and very good habit to do. As with everything, it is better to do it often and in small pieces, before the number of things to fix will be overwhelming.</p><p>If we are going to get there <strong>it might be sometimes better and simpler to rewrite some modules from scratch</strong> but that, unfortunately, takes a lot of time and might fix current problems and bug, but almost certainly it will generate new ones.</p><p>I was in that situation where the legacy code wasn’t allowing me to add newly requested features, wasn’t super readable, but the most important thing was that it wasn’t extensible.</p><p>It took me a long time to make the right decision as the code was not covered with tests, so the refactoring was dangerous, and rewriting the whole module would take me two months at least. Adding a unit test to a code that needs to be refactored doesn’t make sense as it will change and usually if it’s not a right code will be impossible. That’s why I figured out that creating more complicated UI test scenarios will make sure that any changes I will perform won’t affect the current behavior. And I could comfortably start refactoring. In the end, I gained a new automated tool for future use, improved that lousy code, making it ready for adding new features and saved over six weeks of rewriting time.</p><p><strong>Rewriting software is the most tempting solutions, especially for less experienced developers. </strong>That is why it’s good to challenge developers to see if there are maybe any other options. Sometimes complete rewrite might be the best solutions if the codebase is in pathetic condition. But I suggest to leave that option to be the last resort but don’t ever exclude it as a possibility.</p><h3>HOW TO MANAGE THE WORK OF DEVELOPERS. PEER REVIEW AND TOOLS</h3><p><strong>Developers should be familiar with the possible amount of the codebase of the project.</strong> Depending on the size of it might be a complete app knowledge or at least one complicated module. <strong>If only one person has an idea of how a system works under the hood, it is a huge business risk. </strong>Especially if the quality of the software was very poor and undocumented.</p><p>Let’s imagine a situation where that project guru is absent for some reason. Not a very bright future, unfortunately. Even coworkers might have a problem understanding and onboarding to some parts of the system then.</p><p><strong>There is a process that can improve two things at once. It’s called peer review. </strong>How it works is that besides the author at least one (or preferably more) colleagues examine every single change in the products codebase, document, graph, design or anything created to evaluate its technical content and quality.</p><p>The first problem it solves is the project knowledge; thus the author is not the only one that knows the mechanics of his creations. What’s more, it also reassures that the quality of the produced code is reviewed and evaluated by someone else. If that process works well, we can be sure that nothing sketchy won’t pass that point.</p><p>As a bonus, it’s a knowledge exchange for developers so they can learn from each other. There is an extreme case of doing so working in a pair programming approach. That means in front of one computer we put two developers so one of them is coding and the other one might be helping him or learning in the process. In our office, we do that once a week for an hour or two. It’s also an excellent idea as an exercise when hiring a new developer to see what is the quality of code and cooperation at once.</p><p>There are available plenty of developer tools helping keep the code in good shape.</p><p><strong>Whatever your company is, it might be reasonable to perform a cross-review with a different company or use services of more experienced companies with a brief code audit. </strong>With small applications, it might take as short as a day to have a general idea if the code is acceptable or not. Later you can be advised to take a closer look at more crucial modules that raised some yellow/red flags or simply need more attention. A code audit is also a standard part of due diligence for example. So you might want to know what shape it is before is too late to fix it.</p><h3>BAD CODE MAKES DEVELOPERS BAD</h3><p><strong>Developers want to learn new things</strong>, they want to work with new technologies, and they want to write a clean code of which they can be proud of at the end of the day.</p><blockquote>Companies want to have happy employees and they especially want their employees which build their product to be happy. What’s even more important: there is currently a shortage of developers on the job market — so companies can’t afford to loose developers on a regular basis.</blockquote><blockquote>Last but not least: happy employees will work harder and write better code, which leads to even more happy employees.</blockquote><blockquote><em>Markus Oberlehner, quotation from his blogpost </em><a href="https://markus.oberlehner.net/blog/code-quality-matters-for-developers/">Code Quality Matters (for Developers)</a></blockquote><h3>HOW TO ESTIMATE SOFTWARE DEVELOPMENT</h3><p>When creating software is hard to predict and estimate correctly, it puts a lot of pressure on the team which is demotivating and brings the quality even more down. It’s way better to finish a day being proud of your achievements and amount of work instead of living in constant stress. <strong>We only live once, so I recommend being happy and satisfied with what we are doing every day.</strong> That way you can trust more people you work with and without that might be impossible to scale up your business.</p><p><strong>Also regarding scalability, with sloppy code adding more people to the team might be complicated</strong> as I mentioned before. With some processes and good practices, we should also reduce dependency on a sine developer to make our business more stable when everybody knows how the system works.</p><h3>SUMMARY. BETTER CODE QUALITY MEANS HIGHER MAINTAINABILITY</h3><p>At the end of the day better code quality means higher maintainability, you can add more features quickly without any risk of breaking something else, and that should leave more time for non-functional requirements like performance, scalability, security, reliability, etc.</p><blockquote>Code quality, especially on the overall structural level, is an essential property of product software, which translates directly to financial losses or gains as the software is further maintained, modified and adjusted.</blockquote><blockquote><em>Shwe Yee, quotation from a presentation </em><a href="https://www.slideshare.net/Uniqueangel1/importance-of-the-quality-of-code">Importance of the quality of code</a></blockquote><p>__________________</p><p>If you share my ideas and want to talk more about code quality or building a software development team, <strong>please leave a comment</strong>.</p><p>If you have a project to discuss, <a href="https://www.untitledkingdom.com/services/cto-as-a-service">find out what I can do for you as a CTO</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1add155cb869" width="1" height="1" alt=""><hr><p><a href="https://medium.com/untitledkingdom/building-a-top-notch-software-development-team-confession-of-a-cto-1add155cb869">Building a top-notch software development team. Confession of a CTO</a> was originally published in <a href="https://medium.com/untitledkingdom">Untitled Kingdom | Blog about HealthTech, digital health, FemTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>