<?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 Owais Idris on Medium]]></title>
        <description><![CDATA[Stories by Owais Idris on Medium]]></description>
        <link>https://medium.com/@owaisidris?source=rss-980b069fcfe2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6bLAnxut3Ku5XkMnZnH94Q.jpeg</url>
            <title>Stories by Owais Idris on Medium</title>
            <link>https://medium.com/@owaisidris?source=rss-980b069fcfe2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:44:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@owaisidris/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[USED Hyundai i20 Experience]]></title>
            <link>https://owaisidris.medium.com/used-i20-experience-a7cd0254eecb?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7cd0254eecb</guid>
            <category><![CDATA[hyundai-cars]]></category>
            <category><![CDATA[used-cars]]></category>
            <category><![CDATA[buying-guide]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Sat, 01 Mar 2025 12:22:27 GMT</pubDate>
            <atom:updated>2025-03-01T12:41:58.048Z</atom:updated>
            <content:encoded><![CDATA[<p>This is continuation of <a href="https://medium.com/@owaisidris/used-car-ecstasy-with-a-pinch-of-salt-8737701dd709"><em>last article</em>.</a></p><p>We discussed how I narrowed down our search for a suitable make, model, year etc. And reached to two candidate cars. A Honda JAZZ &amp; Hyundai i20.</p><p>We were open to any of the one we could find. Both are good cars. JAZZ is known for it plush ride quality &amp; i20 was introduced as a Premium Hatchback. Like a norm I had already watched tons of dated video reviews and read some motor journalist articles about these cars when they were launched. Honda and Hyundai are feature packed cousins. They are cheaper in maintenance when compared to Mahindra, Tata and German siblings Skoda and Volkswagen. But bit expensive when comparing to Suzuki(or Maruti). The availability of spare parts and service network is also pretty acceptable in India.</p><p>They also have their own cons. Like Honda Jazz and Honda Brio have same engine. So the Brio would feel more peppy and eager when driving since it is smaller and lighter. While with same engine, Jazz feels a little under-powered. But I still wished for Honda for its reputation.</p><p>On the other hand i20 especially from 2011 till 2014 was not known for best mileage. And every other video reviews mentioned about the steering, that it feels a little disconnected. I don’t know what it meant at that time as I had little to know experience. Rest it was marketed as one of the first Premium Hatchback and this has kept me hooked.</p><p>It was November of 2021 when I came across a car and the spec &amp; history<br>was appearing to be balanced as per my expectations. It was a 2013 Hyundai i20 Magna with no air bags or ABS or any split seat arrangement at the rear.. It was driven around 40,0000 km.</p><p>I had very low expectations with any smart feature as I believed in a pure mechanical vehicle. But there was one such feature that I am very happy to have is <strong>Auto Climate control</strong> for Air Condition.</p><p>The elephant in the room was to address problem number one “The Test Drive” Since this was the first car of family, there was no ancestral experience to identify a healthy car. And friends who could help me were not reachable geographically..</p><p>My excitement over shadowed my anxiety, the vibe was quite positive when I booked 1 for a test ride. The used car dealer was modest &amp; they sent the car with an executive at my home, adding to convenience.</p><p>Without introspecting much about the situation we hopped into a car. I announced myself being rookie with out hesitating, to the executive. I had made some prior arrangements with a mechanic who is going to make some sanity checks. And flag if any major trouble with the car. So the next thing was to at least drive a kilometer in a fairly medium congested road in a traffic. The beginner driving experience &amp; the scare muscle memory some how worked that day. Hence minutes well spent.</p><p>Since the mechanic was a stranger to me, complete setup was on trust. I find my self to be observant when we handed over the car to Mr Mechanic. He took the keys &amp; drove off for a test ride alone . I assume<br>he took fairly short round and returned. Next he was checking the steering wheel intending to hear any abnormal sound from it . He crawled the car, again to check any rattling sound. After getting out of car he checked the rubber fitting of doors: This is done usually to get hints of any historic accidents. Finally moved towards the heart of the machine and opened the bonnet. We were waiting for a nod. Which he gave. He approached us and said apart from A/C every thing looks fine. May be it needs a coolant gas refill he added. Before he could complete the executive instantly acknowledged “Yes, that can be fixed before the delivery.” There was little to complain and we proceeded for paper work.</p><p>I don’t feel the need to mention the used car dealer brand as it is so random to find a suitable car. Only thing worth mentioning is that the unit was tagged as their “ASSURED CAR” which make it a candidate for 6 month warranty on any major repair &amp; 2 road side assistance on breakdown, which not many dealers offer.</p><p>On a day of<strong> November 2021</strong>. The ‘Said car was delivered’ . And we happily lived after? Well. Remember in the previous articles I mentioned something about<strong> audacity</strong>. well next it was put to test. We can talk about it in a separate article. Where we will see how much the car costed and what can it further cost to us.</p><p>I hope this readout helped you to understand what kind of inspection can help you finalize the car and move forward. One thing to note is be a good observer. Weather it is test ride or paperwork. Ask questions &amp; demand answers. Remember you are in control until money is with you. The moment you pay you are in the game.</p><blockquote><strong>Keep making decisions, keep moving</strong>.</blockquote><p>Used i20 ownership .. to be continue…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7cd0254eecb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Used Car Ecstasy with a pinch of salt.]]></title>
            <link>https://owaisidris.medium.com/used-car-ecstasy-with-a-pinch-of-salt-8737701dd709?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8737701dd709</guid>
            <category><![CDATA[buying-guide]]></category>
            <category><![CDATA[guidelines]]></category>
            <category><![CDATA[second-hand-cars]]></category>
            <category><![CDATA[i20]]></category>
            <category><![CDATA[buying-a-car]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Thu, 27 Feb 2025 07:41:37 GMT</pubDate>
            <atom:updated>2025-03-01T12:42:52.579Z</atom:updated>
            <content:encoded><![CDATA[<h3>Used car ecstasy with a pinch of salt.</h3><p>It has been a very romantic journey with my Used car up till now. There have been so many pleasures and here and there some reality checks were necessary too. Hence how lucrative it could be for a person to own and maintain a used car?</p><p>If you are someone planning to own a used car. Or already tied a knot, this article will comfort you. It started when I got sparked by a Youtube channel. Where I developed some knack in understanding cars. And gradually it became my favorite leisure time to know about cars . Watch videos of cars that cannot be bought. Just to understand the hype. And slowly I shifted my gears. And started researching the market of Humble Cars. Or cars that we see daily during our commute. What kind of fuel? What kind of gear box? Different types of categories, A hatchback, a sedan or SUV. I was kind of well versed in no time. One fine day it just start making me uncomfortable to know all of this stuff but not having a preference. So I kind of started to understand which configuration I tend to be biased. Then it was not late when I started to question my self. At this point of time What can I own? What should be an ideal starting point? I am already scrolling listings of some online websites.</p><p>I had this sorted in my head that a new car and the spec I am clinging towards are not overlapping at all. Hence what I can dream of will and have to be a Used car.</p><p>Fortunately India is heaven for Re Using and Re Pairing. There is no shame and it’s the most practical culture here. After weeks of reckoning I reached to a conclusion and short listed some cars. Here are the parameters of my interest in year 2021.</p><ol><li>Budget up to 3 Lacs</li><li>It must be at least from a Premium Hatchback segment.</li><li>It must be a petrol variant.</li><li>Car must be 5 to 8 years used. The sweet spot was cars between years 2013–2014.</li><li>Odometer reading must not be more than 50K Kilometers.</li><li>Rest all things are optional. Airbags, ABS, Split rear seat.</li></ol><p>There were initially 3 candidates when my hunt begin.</p><ol><li>Honda Jazz</li><li>Hyundai i20</li><li>Suzuki Baleno</li></ol><p>During this period I got in touch with my historic Gym partner and discover he is into car sales. I took this as an opportunity to understand market sentiments around these 3 cars. Which helped me to rule out the Baleno. I was convince that car is quite light weight which contributes in a good mileage. But often the car is rebuked for its highway stability.</p><p>It was a covenant between me and myself that I want a car that don&#39;t hesitate in city nor on highways. This car is going to be a family car so even my brothers and father is going to drive this. I don&#39;t want it to be limited at least in the basics like engine performance and weight distribution. I was not that wise to understand this on my own but few discussion with people owning a car helped me shape my requirements.</p><p>Buying a Used car and the urgency to have it cannot go together. To find a good car it takes time and a skeptical eye. Due deligence should be your first nature. Used car market people have a PHD to beautify a tin box to look like a brand new car. So being mindful should be your second nature. It could take 1 week to 3 months to find your match. Even though you are getting cars for half the price but that is just half the story. I came to an analogy that used cars are not cheaper than New cars. Its just how you are going to spend money every 5 years.</p><p>When you get a Brand you car, you are sorted for next 5 years. To pay the price in Advance. But for Used one think about you pay something to own it and then your journey starts with addressing problems in the vehicle hence you keep on spending for rest of the years for one problem at a time. Like for example if you can imagine if you acquire a car for more than 5 years old for free, will it be completely free? After 5 years it might have completed 40K km. There must be parts that has to be changed every 10 20 30 40 km. May be breaks, suspensions, or any electronic panel. Or think of it even if you have bought a new car you would have any ways spent on same to keep your vehicle smooth and usable. Hence it is safe to say that your vehicle will need some good investments after 5 to 8 years. Some people are religious enough to keep their car and some are wealthy enough to sell it and get a new one instead. I was in the third category and would like to scavenge on these used cars. And be as productive as a new car owner is but with some work to do on car.</p><p>My hunt begin and I started getting invitations from various seller to come and checkout their inventory. I also asked some of my known touch points to keep an eye on a good car deals. They helped but nothing was getting materialized. Either car was ran too few km to beleive that there is no tempering in the Odometer unit. Like we came accross and I20 Sport 2012 with odometer 16K mileage reported. We thought this car was stranded in the garage most of the time. A car that is used frequently has less problems than which is rusting in a garage. Or the price was set so high that I failed to bargain the price to my liking. I fortunately did not hesitate to walk away as there is a World out there for me to find cars.</p><p>I shared my plans with my family members and they were not convinced initially to have a car in this crowded city like Mumbai because even the parking spaces are premium. So if your car is running you are spending on fuel and when it is parked you are still spending on the parking rents. These rents were any where from 1800 Rs per month to 3500 per month. And the parking owners need a yearly payments to allow them to show some mercy and give discounts.</p><p>Eventually I was able to convince them that how this car will bring some freedom to move around the city and especially in the outskirts. It will widen our diameter of life. And huge pleasures only come to you if you have audacity to bear it. The next thing is they could not stop themselves to trust my instincts and give me a free hand. More over they were ready to contribute in this purchase which made the hunt even amusingly sweet and stress free.</p><p>One more advice I would like to give here. Taking decisions are utterly important. It might give you bad result, or good or you just said no and walk away. But not taking decision is a very pathetic thing to do. You have to do same when finding a used car. If you are not sure say no and move on you will find next. Make it easy for the seller to understand that you have some taste in vehicle.</p><p>I found my match through an online shop. This brand is quite reputed and have a very good recall value. I found an i20 magna which I offered them to give me a trial. At this time I was a learner and had no good experience in driving. I will require some help here. But just to keep your reading concise we will take a pause here and read about the whole car experience of buying and owning in the next article which I will post here.</p><p><a href="https://owaisidris.medium.com/used-i20-experience-a7cd0254eecb">The Used Hyundai i20 experience</a>…(to be continue)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8737701dd709" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let your tests speak for themselves.]]></title>
            <link>https://owaisidris.medium.com/make-your-tests-readable-44f4d508bd3f?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/44f4d508bd3f</guid>
            <category><![CDATA[unit-testing]]></category>
            <category><![CDATA[test-driven-development]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Wed, 20 Sep 2023 11:17:38 GMT</pubDate>
            <atom:updated>2024-09-13T06:09:46.729Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CPTR4OimXVPDmv75UwNE5g.jpeg" /><figcaption>Give me six hours to chop down a tree and I will spend the first four sharpening the axe. PC AI generated Image with Bing.</figcaption></figure><p>Often in Engineering we tend to overdo things which eventually gets difficult to keep up with. It happens with testing too. Since most of us are struggling with good naming, Unit testing is full of it. In this writeup I am going to shed some lights on one way of naming unit-tests.</p><p>Following nomenclature practice is an evolved version from different testing libraries that I came across during my carreer. Its tried and tested over time and proved to be successful in itself. It is inspired by the SQL statements and some de-facto standards used by various testing libraries.</p><p>Having said that it is not mandatory that every Test File in your testing libraries should look like this. But at least each file individually should be self-explanatory. Having some pattern makes easy for the reader to follow the document/test and also help them to make changes in same context.</p><p>You may take these guidelines as is or at least start with this and improvise with time. These guidelines assume that you understand <strong>3 A’s</strong> of testing(<em>Arrangement, Action, Assertion</em>). Also if or your testing libraries allows you to group your tests so that related test stays close to each other, this is better for readability.</p><p>When arranging your test everything boils down to following clauses.</p><ol><li><strong>GIVEN</strong> — Conditions or Parameter. These are conditions that may affect behaviour of a TestClass(Class under test)</li><li><strong>ON ACTION</strong> — Behaviours or Public functions of your Test class</li><li><strong>THEN</strong> — Expectation/s</li></ol><ul><li>When Conditions are repetitive then tests could be grouped by GIVEN clause hence you don’t have to repeat the condition in every sub tests. However each tests may or may not have additional conditions hence even individual test can have GIVEN clause. If not, then GIVEN clause in nested tests can be skipped</li><li>When ACTION is same but based on inputs output may differ then you don’t have to repeat the ACTION in every sub tests and all the similar test with same ACTION can be grouped together. However each tests may or may not have conditions hence on individual test we can have GIVEN clause. If not, then GIVEN clause in nested tests can be skipped</li></ul><pre><br>//1. Declare your Mocks<br><br>//2. Prepare your test class<br>fun buildTestClass(): TestClass{<br>    // Build or prepare the test class. There will be multiple buildTestClassFlavor functions if there are more configuration to check with<br>}<br><br>//3. Test Hooks: Promote common mocking behaviours here those are majorly case with all your test except some.<br>beforeEach{<br>    <br>}<br><br>afterEach{<br>  <br>}<br><br><br><br>//4. Actual tests<br>expect(&quot;GIVEN conditions or parameter ON ACTION or actions THEN expectations&quot;){<br>        //3 A&#39;s of Testing<br>        //Arrangment<br>        /*<br>        1. Initialization code<br>        2. mocking behaviours here<br>        3. Any set of Actions to reach testing stage here. e.g you have test criteria that user is logged in then first call login action in arrangment section<br>        * */<br>       <br>        <br>        //Action<br>        /*<br>        Action for the actual behaviour of the class under test is to be tested. e.g here you want to test logout action for a loggedin user<br>        */<br>        <br>        <br>        //Assert<br>        /*<br>        * 1. Assert outputs<br>        * 2. Verify collaboration by checking if the mockked method is called or should not be called etc.<br>        * */<br>    <br>    }<br>    <br>    //If Given parameters are redundant in your tests then group by Given Clause<br>    context(&quot;GIVEN common-condition&quot;){<br><br>        expect(&quot;GIVEN condition2 or additional parameter ON ACTION or action1 THEN expectations&quot;){}<br><br>        //.... similar test with same shared condition and different some other conditions<br>        expect(&quot;GIVEN  condition3  ON ACTION or 2nd actions THEN expectations&quot;){}<br>        <br>        //No condition case<br>         expect(&quot;ON ACTION or 2nd actions THEN expectations&quot;){}<br><br><br>    }<br>    <br>    //IF the conditions keep on changing but ACTION remains same for Multiple test then group by Action<br>    context(&quot;ON ACTION&quot;){<br><br>        expect(&quot;GIVEN Condition1 THEN expectations&quot;){}<br><br>        expect(&quot;GIVEN Condition2 THEN expectations&quot;){}<br><br>        //....<br>    }</pre><h4>Example</h4><p>Let me give you a real feel of how the tests class should be presented to a reader.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ASG-CjkDGsnzzb6xhYRMyg.png" /><figcaption>All collapsed</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aWIukP8uTKPR3hcCqtH_JA.png" /><figcaption>Level 1 expanded</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yp1lzRFwk1g9nTQz9TFCVg.png" /><figcaption>Grouped by condition</figcaption></figure><h3>Conclusion</h3><p>I know there will be some variations here and there from platform to platform and may differ with different testing environments. The idea here is to find a way to organise our test in a Platform and Library agnostic way, keeping it as simple as possible to read. Unit testing also serve as a great documentation of the software code as it is regularly updated as an when code is updated. Keeping it simple may help other non-coding testers to refer it and also help future developer to understand system. And that future developer could be ourselves too. Test code is like a Gym workout, you will not see its benefits immediately but soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44f4d508bd3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recreating from Legacy - a Developer Story.]]></title>
            <link>https://medium.com/geekculture/recreating-from-legacy-a-developer-story-87eb21503a8a?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/87eb21503a8a</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[kotlin-multiplatform]]></category>
            <category><![CDATA[developer-stories]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[legacy-systems]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Fri, 23 Sep 2022 10:35:33 GMT</pubDate>
            <atom:updated>2022-09-23T10:35:33.780Z</atom:updated>
            <content:encoded><![CDATA[<h3>INTRODUCTION</h3><p>Our attempt to Recreate a big part of On-boarding experience (currently written in web) in Native Android and IOS such that both share same business and application rules while implementing their own native views.</p><h3>CURRENT LEGACY SYSTEM BIG PICTURE</h3><p>Our current legacy system is the whole point of this write up. But before I get inside describing it in detail let me make it clear there are no culprits or any individuals who’s to be blamed. Every code, every architecture comes with an expiry so there is nothing to be cynical about. System doesn’t become legacy in a day, this happens over course of time, due to Time constraints, business constraints, hot fixes and procrastination.</p><p>Now the system we are talking about is a part of the registration process of the <strong>shaadi.com</strong> App. There are a series of screens that the user has to go through in order to create its profile on <em>shaadi.com</em>. Each of these screens have multiple form inputs like dropdowns, text inputs, checkboxes, autocomplete text-inputs and multi selection widgets. Additionally these widgets are conditionally shown or hidden based on complex form rules. These rules are based upon various inputs by user or based upon the country of user or based upon availability of the data from the API.</p><p>Widgets like drop down or multiple actions show various options to the user. These options are either statically available in the system or are downloaded from the back-end providing some arguments in the API for example cities are populated based upon the state selected by the user and ethnicity is downloaded based upon user attributes like mother-tongue religion and country of Living.</p><p>A typical user will start with page 1 fill the data and press the continue button where the inputs by the user are validated followed by page 2, its validation followed by page 3, its validation and finally create profile call to action button . We have considered this as our scope of development and will focus on these three pages called registration page 1, 2 and 3. There are certain screens before page 1 and certain flow after Page 3 but those are out of our scope of consideration</p><p>By a little closer look we noticed that the labels are also based upon som attributes such as the profile creator and its relationship with the bride or groom or gender. We also noticed there are validation messages, some very straight forward and some again based upon the actors.</p><p>Additionally user can go to and fro between these pages, where going back, all the fields should contain the relevant values that the user had filled with and going forward, it must again validate before landing on the next page. Finally there is a feature where a user can start from where he or she left irrespective of the session and the platform i.e. a user could start the journey using shaadi.com website on a browser and later should be able to resume on a mobile App.</p><p>At this point in time we had no idea about the details of implementation or how it is internally working. The current system was being rendered in a WebView with very historic code in action. The screens were eventually embedded in the native screens of Android and IOS apps. As these screens are very important for most of the user acquisition part no one would dare to touch these functionalities due to Legacy code and direct impact on business it can have. The developers who initially worked on this part of the system have left long back with little to no knowledge transfers. Similar is the story with product managers and quality assurance teams. We have fragmented knowledge preserved with some individuals who have worked on the system for a long period of time now or we have fragmented and also outdated documentation. There is no one person or team or documentation to rely completely.</p><h3>Gathering the requirement</h3><p>This was essential for</p><ol><li>Understanding the current system</li><li>Identifying the problem and proposing a long term solution</li><li>Estimating the efforts and time required to achieve our goal</li></ol><p>We already knew that the current system is a Legacy one and addressing such a system is a long pending decision. Since it is rendered in a browser there are a lot of native capabilities it is deprived of. However, there must be a very good reason to touch such a sensitive part of the system.</p><p>We say let’s rewrite this flow in native, this will open a plethora of opportunities to change and tailor the experience according to ever changing business needs, ensuring the solution should have a longer shelf life.</p><p>One thing that we clearly understood about this legacy system is that the business rules are tightly coupled with the platform and the framework. Moreover it is directly accessing the database to fetch any data, hence reusing the existing code is not an option. Since it is directly accessing the data from the database we understood we will require some REST API to access information. These API are either already present in our libraries or we need to understand and draw a new requirement, get it developed as per our need. Finally APIs might already exist but the shape of the data is not compatible with mobile so we will need a decorated compatible version of the same API.</p><p>We also hunted for documentation and found some pieces of information thanks to some individuals who faced the same problem and tried to sketch some documentation around the system behavior. But since these documents are not updated regularly and people from different teams at very different times have collected this information, not everything is true and there is some conflicting information in them. So no matter who we talk to, what we access, we still need some black box testing to understand exactly how the system is behaving in production? Even if the input and output strategies are not enough then, our last resort is to dig the code or reach out to the people who can dig it faster because of their expertise with the platform and the language.</p><p>We didn’t hit these obstacles at once but it happened in all the stages of development even after reaching the first few rounds of QA.</p><p><strong>The </strong><a href="https://kotlinlang.org/lp/mobile/"><strong>KMM</strong></a><strong> Pitch</strong></p><p>Registration Part 2 is not the first <a href="https://kotlinlang.org/lp/mobile/">KMM</a> project we are working on, before this we already deployed a new native version of Registration Part 1 on production which has been fruitful for the product as well as the development team working on the same. Registration Part 1 was written using test driven development hence all the rules and the behaviors are documented in tests. A recent Redesigned version of Registration Part 1 was released and it looks very promising.</p><p>A good architecture is where the business rules are separated from the platform code. This is not particular to <a href="https://kotlinlang.org/lp/mobile/">KMM</a>. This is applicable to Android or an IOS app architecture individually too. What KMM enables us is to share the same business rules as one code base, while the UI code remains local and native to the main app. Finally these business rules are accessed as a library.</p><p>With some good learning from our experience with Registration Part 1 and we understood some problems that needed attention across the platform teams both Android and IOS. One big challenge was to make our iOS developers comfortable with this foreign concept and make them feel home. We understand, the iOS UI System is more like a tree structure and the view system of Android is a flat system. This was the reason the iOS developer had to write an additional wrapper to make things compatible with their own architecture. We have tried to address those problems in Registration Part 2 where iOS developers might not have to write that additional layer of wrapper. We have consolidated individual widget data into a thing called <strong>ViewData</strong> which represents the complete state of View/Screen at any given point of the time. So now iOS developers will not have to subscribe to multiple channels for States of various widgets. However now Android developers have to temporarily write a small layer which compares and updates the widgets based on the change in version of the data.</p><h3>VIEWDATA</h3><p>What do I mean when I say consolidated data? Well just to give a background a complete state of screen is represented by a data where we control the widgets on the screen. This data will have information or commands for the widget such as visibility information or whether the widget is enabled or disabled or what will be the drop down options or what will be the value field etc. Considering each screen is a form with loads of widgets, each widget is controlled with a chunk of data. If we consolidate all these chunks we get <strong>view-data</strong> and that’s what our proposed solution is. I also mentioned that <em>temporarily</em> Android Dev will have to write this additional layer optionally to achieve optimized outputs but in the coming future this flat view system will be replaced with a tree like view system <a href="https://developer.android.com/jetpack/compose?gclid=Cj0KCQjwsrWZBhC4ARIsAGGUJuoqqbLRszRKODvovbDFuPs1CY78K1V0H9q9EAiX6SGg9CAX-O42En4aAj0vEALw_wcB&amp;gclsrc=aw.ds"><strong>Jetpack compose</strong></a>. Hence both iOS and Android view rendering will be more or less similar( off course they will be native in their nature).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WKGSIgKzpb2sXN6H" /><figcaption>Representation of Form in Data</figcaption></figure><p>So now if you have got a picture about how this reactive system will keep on updating the state and both Android and IOS will subscribe to this data and render or update their respectively. Other technical details we will see in the later sections of this article.</p><h3>Approaches and Execution</h3><p>Before I was introduced to this project, most of the requirements gathering with respect to documents and specs for API were already being gathered by one of my colleagues. He had already started some discussion and made some trackers for pending acceptance criterias, opened &amp; assigned some todos to various stakeholders while closing some points. His work gave us that initial thrust.</p><p>This Legacy nature of the project forced us to ask the right questions before anyone <br>could help us. So most of the clarity came only when we were able to ask the right questions. As I said, the documentation won’t be enough to connect some dots. Other developers and testers helped us to find those answers but again they were busy with their priority so the information was not coming at the rate as it was supposed to.</p><p>We already had spent a lot of time trying to find just enough acceptance criteria . Hence we started the development with whatever we knew. The acceptance criteria became our units for testing so we simply added those acceptance in our test. This way we started writing business and application rules in our code. We made all those test passes as per our need. This <em>viewdata</em> approach where the state of all the widgets on the screen is consolidated as a single data was new to us. So we had to test it with a User Interface. One of my colleagues helped me with the UI. I made him understand how he should subscribe to the data and how to interpret that data in such a way that by just changing the rules it should be properly updated on the user interface. And he nailed it. In a very short time he was able to develop a UI that could talk to my business logic and vice versa. Now during the development I could publish my business rules locally(<em>as a library to the main Android project</em>) and actually verify the behavior of the system.</p><p>This way we also started a client level implementation with the Registration library in Android. From now on both shared library development and Android UI implementation will happen simultaneously.</p><p><em>Confidence in Acceptance Criteria</em></p><p><em>At any point of time the system was a reflection of only whatever we knew</em>. We created a portion of page 1 consisting of some related input fields, by applying whatever form rules we knew about. After comparing it with the production App we saw some differences. So we added whatever was missing just to realize that now something else was behaving differently. Eventually we were able to identify a pattern. With some conclusion on a Pattern we reiterated the same functionality again. This was making our life even more difficult in some cases where we were not able to find a pattern. This trial and error would slow us down and we needed another strategy.</p><p>We ask QA for more and more acceptance criteria making life of busy QA even more busy. I remember asking QA if they don’t know end to end acceptance criteria, how will they be able to give a sign off on completion? What will be the strategy for testing? The answer was obvious: they are going to compare the live and the testing version <em>side by side</em>. This answer shook us for a while and later it became the <em>source of gathering acceptance criteria</em>. We simply started sharing this crude version of our Registration build with QA and asked them to verify (and not test these builds). We called it<em> daily builds</em>. To make their life easy we gave them the impact areas and asked them not to spend more than an hour or two with any of the build. QA would go through the build and compare its behavior with production and maintain a tracker/todo where in detail the issue was described. These todos are now our acceptance criteria. These issues were some links that were missing in our initial acceptance criteria.</p><p>This way of gathering acceptance criteria was working for us but eventually there was more work for QA. After some cycles of this said daily build we stopped sharing builds with QA(<em>on demand</em>). By that time we had collected plenty of acceptance criteria. Some of them we already knew but now they were reassured.</p><p><em>The Back End Support</em></p><p>When we started development we considered backend as a detail and deferred the decision of working on any network API related code. The idea was to work on only business and application rules and mock everything else. After spending a considerable amount of time with form rules at some time we had to take some API into consideration. We had to identify from where the data is accessed in order to populate various drop downs on screen. When I say field data, it means the data that is populated in a drop down and when I say field value, it means the item that is selected from that drop down.</p><p>Some field data are statically available and we could simply copy paste in our project while some field data are only accessed via some API. For this same reason we collaborated with a developer from a <em>back-end </em>team. This guy is super supportive. The time and effort given by this person brought so much to the table. He made us understand where we could find static data. He helped us find various endpoints from where field data can be populated(API). He also shared his postman entries with us which was a very mindful collection of API that were usually used together.</p><p>While we were searching for endpoints we understood that some of the API responses were not <em>compatible</em> with <em>mobile</em> so they need some extra development. Also some API never existed as the Web was accessing the database directly. He started the development of these API as soon as possible and shared sandbox environment where this current and upcoming development from the back end will be deployed.</p><p>There were some back and forth during this phase but I was happy with the progress.</p><p><strong><em>The Reverse Engineering</em></strong></p><p>All this time we had been chasing for correct acceptance criteria by following the documentation and comparing the behavior with Production (<em>by sharing daily builds)</em>. Still a myriad of things were happening, at various occasions there was some magic happening on the production which had no pattern. In such situations we always turned up to this experienced developer who is more familiar with this Legacy code of the web then any other on the floor. He used to perform this stunt of diving into Legacy code and finding answers for us. His contribution is really plausible.</p><p>We would spend a lot of time together finding missing answers, identifying if there is a rule or an API adding any behavior of production behind the curtains. He was our last resort to find answers. He made us understand what data was being accessed directly from the database or what API is being called to achieve certain results. Based on his response we either find and integrate the API or develop a fresh one as per our needs.</p><p>Such findings sometimes resulted in rewriting a complete portion of the feature. And we had to rewrite it wherever and whenever needed and stick to the idea with which we started this project: <strong>that the system should be a reflection of what we know.</strong></p><h3>System design</h3><p>Throughout the journey we stood with some values and followed them religiously. The first value is to maintain the quality of the system by using the best practices. We followed programming principles and approaches. The idea was to first <em>Make it Work</em> then <em>Make it organized</em> followed by <em>Make it optimize</em>d.</p><p>We wrote a working version by using <em>Test driven development</em>. If there was any missing case reported it was covered by a test. Similarly if an issue was reported it was again covered by a test ensuring the mistakes were not repeated again. What we thought of as just three screens with user input fields turned out to be a hierarchy of complex rules. There were form rules. There were resetting rules (<em>where if a field is selected with a certain value all the dependent fields must reset or not reset or partially reset</em>).</p><p><em>Session restore — Starting from where left</em></p><p>There are rules for session restore: when the user starts profile creation from some other platform and drops there, later wants to continue from the phone app. His progress must be restored as they it was left. According to the acceptance criteria on each page when it loads there is an API where we check if users have made any progress. If yes those progress are applied, if not then all fields are defaulted accordingly. Then again when Users try to navigate to the next page the fields are validated they are again backed up to the API before navigating to the next page . This backup and restore functionality was the case for all three pages . We saw opportunities here and a way to benefit from native environment, so we optimized it . Instead of calling the same API On load of each page to get progress we called the API and cached the response before starting Registration Part 2. On each page before navigating to the next page we update this cache data and send this consistent data to the draft API where the progress is saved . This way we implemented some use cases that were responsible to backup and restore the progress .</p><p><em>Exposing Public Interfaces for Client</em></p><p>Since we are writing a library it is important that our public interfaces(methods to interact with libraries and their signatures) be stable. On every update it should not break the client. However it should be easy to update and extend the functionalities. For this we have used MVI Architectural Pattern. Where we expose only 3 elements to the client for each ViewModel.</p><ol><li>A <a href="https://kotlinlang.org/docs/flow.html">Stream</a> for States</li><li>A <a href="https://kotlinlang.org/docs/flow.html">Stream</a> for Events</li><li>Actions: A mechanism to add input to ViewModel.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/0*dD_-OKq01qDCyfIT" /><figcaption>Discrete Public APIs</figcaption></figure><p><em>States</em></p><p>There are 2 possible states:</p><ol><li>Loading</li><li>Update(ViewData)</li></ol><p><em>Loading</em> as the name suggests. While Updates carried current snapshot of ViewData, based upon this data UI will react.</p><pre>sealed class UIState {<br>   object Loading : UIState()<br>   data class Update(val viewData: ViewData) : UIState()<br>}</pre><p><em>Events</em></p><p>Events are one-time quick instruction like showing error or navigating away from the screen.</p><pre>sealed class UIEvents {<br>   object Finalized : UIEvents()<br>   object ErrorLoadingData : UIEvents()<br>}</pre><p><em>Actions</em></p><p>Actions are output of User Interaction on screen which are sent as an Input to our business logic. Our libraries process these rules and update ViewData accordingly.<br>Like User Selected Location-State as Maharashtra. This will serve as input to our Library(VM) and as a reaction Cities of selected Location:State will be downloaded and populated. Additionally Actions should be specific. It should not be verbose and for similar kinds of input there should be an Action. For example Action for Checkbox checked should be different from Action for Dropdown Selection. Hence Actions are typed so that there is less or no verbosity when choosing what Action to fire.</p><pre>sealed class Action {<br>   object <strong>Start</strong> : Action()<br>   object <strong>Refresh</strong> : Action()<br>   object <strong>Visit</strong> : Action()<br>   object <strong>Submit</strong> : Action()<br>   data class <strong>Selected</strong>(<br>       val field: Reg2x2SelectionFields,<br>       val value: Selection,<br>       val tag: String = &quot;&quot;<br>   ) : Action()<br>....</pre><pre>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FasEln84jvnO0swu" /><figcaption>Actions Goes up and States and Events goes downward in direction</figcaption></figure><p>As promised, going in detail into what is ViewModel, Use Case or Repository is out of the scope of this article. But all I can say these are different layers, each with some responsibility and these layers are decoupled from each other hence making our system flexible to change.</p><p>This approach was used for every part of Reg 2 in our scope. Any client (say Android and IOS) can now listen to these streams and update their UI accordingly.</p><h3>So far so good..</h3><p>A lot of time was invested. A lot of effort was put into finding Acceptance. Being skeptical about each rule sometimes paid off well. We had so much information it felt like it would be now stupid to wait for even more information. I started a full fledged development. Already behind the deadline things were on fire. Investing any more time or doubting the information was costly. It is so difficult to estimate timelines for such a project that I have already given estimates multiple of time depending upon what was known. Although initially there was no pressure but my own guilt that was driving me to take no rest and progress no matter what.</p><p>Day in and Day out, starting every morning from where it was left in the evening. Everyday was a Registration day. To test anything on Registration 2 one needs to go through all the form filling right from start(Reg 1) finally reaching the testing screen and check if things worked out this time. As per my estimates every week there used to be more than 100 registration(of course not on production). We could have mocked Reg 1 but we did not want to be confused with the system behavior and mocked behavior. So we kept it a natural Production-like experience. We could address multiple things and check them altogether to optimize our testing.</p><p>There were so many sources of Information it was difficult to mentally map them. So I also created a doc to dump everything that I know or is known in a simple layman’s English. Here I documented everything regarding Form Rules, Validations, API Specifications, even static data that is to be used in Project. It is still WIP and we are trying to update it regularly. I don’t know if this document has the same fate as it was for documentations before. Still we would like to contribute considering the future developers who are going to revisit these screens(It could be us also).</p><p>We created the first cut. It was not perfect. But it was high time and we needed at least one round of QA. This would take us closer to our goals eventually closing some todos added during Daily Build rounds.</p><h3>QA Started</h3><p>At that point of time our QA was handling multiple projects and was quite an occupied person. We shared a build with her and she started the QA. But with QA, hunting for even more Acceptance Criteria started. Our build was scrutinized and some very delicate information started to come into the limelight. Such that our build was kind of unstable for QA. It was this time each bit of the system was zoomed in and checked. The result of this first round was mind bending and somewhat disappointing for me. It would have been much much better if these details were available to me earlier.</p><p>Apart from these there were certain ambiguities in the system which initially didn’t make any sense to us so we hesitated to put in this new system. Turns out those ambiguities need to be re-introduced because it might be driving some Product Metrics. Consider a very simple example: We have a country dropdown in Reg Part 1 where the user is presented with a list of countries and needs to select one. In our case we also had a country dropdown but here for a different purpose. We thought we could reuse the country list from Reg Part 1. But it turns out there were subtle differences between the list expected on both screens. Like one case accepts the UK as a country and another accepts the United Kingdom. It was important to keep things as production because there must be some metrics running on these which expects the United Kingdom and keeps count of it. Finding such a list or making the current list as expected was one such task.</p><p><em>From the start as I said we only added those bits that were clear to us. We wanted the system to fail and fail quickly so that we could update it with correct information in hand. Although such approaches are not good when it comes to stats like bug count. But in the longer run it ensures stability and control over the system.</em></p><p>Hence although feedback from the first round made us bleed but we were far from anything like sweating. Now we had better information in hand and most importantly the correct one. Again we had to revisit some sections of the module, even rewrite some. We also reconsidered our tests, updated them compulsorily. The process was slow but steady. We could see the functionality of Reg 2 improving as compared to the build first shared with QA. We tried closing some of the obvious issues and missing cases. While some were closed after detailed discussions with other stakeholders. However, some issues were again a gray Area and we knew it was wrong but did not know what could be the closest correct answer to it. So we had to turn our heads again to people like I mentioned, a super helpful backend developer and our veteran friend who could dive into the legacy codebase.</p><p><em>Reinforcement</em></p><p>Although I was the only developer working on Reg Part 2 till now, all the things I had to hold together was a delicate affair. By stretching everyday from the past few months I was completely indulged in Reg, thinking about code, approaches, handling communications, long meetings everyday was making this uphill climb difficult day by day. I am handling both library and Client implementations now. It was pure gambling of my time everyday. Where should I put my time today, in Library Coding, in addressing clients, Closing QA, chasing people to understand correct behavior of certain issues, getting UI feedback closed etc. It was not simple to keep calibration of work now. At various occasions I found my-self in the center of everything after many days of non-productive hard-works. And quitting was never an option.</p><p>To make my world a little breathable I asked my Manager to give me a Reinforcement. A Senior Dev who could work shoulder to shoulder with me. Someone who have good endurance and could work with me in this mine of fire. And it was granted. I now have a partner! He was fresh and energetic after coming on board he quickly took the responsibility of client side programming and closed various design feedback. He chased people to get the work done, something which I was saturated with. I was about to become a father which added some constraints and my responsibility was channelized away from Reg 2 for some days. During these days my Partner kept the ship sailing. He single-handedly closed various library and client issues even though he was not familiar with <a href="https://kotlinlang.org/lp/mobile/"><em>KMM</em></a> much. There was a learning curve before he could completely take charge which was nailed in a very quick duration.</p><p>After I returned from my quick paternal vacation I joined him again and we kept on closing new issues that were raised. At this stage there was no difference between an issue or acceptance criteria. We already lost our sense of smell to identify which is what. Every week we could close all the issues on Friday and we were greeted with dozens of issues on a Monday. These issues are actually not the visible ones. Up till now our Reg Part 2 screens were working fantastically. It was obeying all the form rules. All the correct data was presented to the user. Flows were working as expected. Then what kind of issue were they?</p><h3>Data Discrepancy Issues</h3><p>With Reg Part 2 we were able to re-engineer the front end of the legacy system but it is not done yet. Our backend services are still legacy one. So, although we have nailed the user facing presentation part, our backend was expecting old type of data. So there were subtle differences between the data we are sending and the system expecting. Due to which the post Reg Part 2 flows of our system were breaking. Metric Tracking was breaking and god knows what.</p><p>We needed a seam that could convert the data to exactly what is needed. Take for example the CastNoBar checkbox. Checkbox is either true or false. Throughout the journey of Reg Part 2 it was saved in boolean type. But the server was expecting something else. Following was expected.</p><ol><li>A String</li><li>If Checked then “Yes”</li><li>If Unchecked then “0”</li></ol><p>We have ridiculously named this type of data as <strong>BoolShit</strong>. A boolean data which is expected in string format where true is a binary Yes and false is a binary 0.</p><p>A huge amount of time was invested in investigating the data discrepancy and its sources and at the end what is expected from the client to server. In most of the cases our Super Supportive Backend Developer and Veteran friend played a huge role here. We were totally dependent on their findings. Although we had been present in some day-long meetings with them(Just of moral Support). It took us light years to get even a small insight enough to know whether we are on the right track or not. Now all of us are stretching everyday to support each other. It was exhausting but I was happy with the progress we made.</p><p>Oh lets not forget the contribution of our dearest Product Manager. None of the product managers were end to end aware of all the business rules that are currently on Production. All they cared about was their Metrics. My existing Product was serving its notice period. He helped us to check what database tables needed to be verified when registration was completed. And left the company after a day or two. And now the new Product manager was actually not the right audience to answer our tricky query. But he was still able to help us by using a magical statement which kept all of us motivated. He said <em>“Let’s keep everything the same as Production”. </em>And<em>…</em>We did the same. In some cases we had to replicate a bug of Production too(Not that we are proud of). Having said that, we never polluted our code with it. Those legacy facing functionalities or processes are hidden in a separate layer which is called Seam. This seam protects the good part from the legacy part. Once our legacy back-ends are addressed in future we can remove these seams or add new and better one’s.</p><h3>Conclusion</h3><p>Re-engineering legacy systems need a good hands-on experience w.r.t tech and domain. It needs dependable resources who are ready to squeeze out time from their busy schedule. It needs better documentation either present before development or made one during development. We need understanding stakeholders who are flexible enough. Once started, de-prioritizing such development will worsen the situation as information is very volatile and holding them together is a delicate affair and chances of miscommunication increases. Larger the project, larger could be the communication gaps. We need strong and decisive QAs who could take calls and understand what is really required for closure and particularly what can be picked up later. Similarly strong UI designers who take calls and help close design faster and who could think ahead of time especially w.r.t intermediate states of UI which are missing in current legacy systems. Finally a wise Product Manager is like the cherry on top.</p><p>I personally feel Paired Programming is answer to complex project as there is always someone to validate each others thoughts.</p><p>Since such features are always rolled out in parts after running experiments there can be certain things that can be deferred and picked up later. Engineering is not about what all can be done, it is also about identifying what is not much required and can be deferred for the best. Our Module is still in QA but in a much much better state and we are confident enough it will bloom some day(at the time I am writing this).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87eb21503a8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/recreating-from-legacy-a-developer-story-87eb21503a8a">Recreating from Legacy - a Developer Story.</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Informed Programmer.]]></title>
            <link>https://medium.com/geekculture/an-informed-programmer-19caedfc1620?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/19caedfc1620</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Thu, 14 Apr 2022 20:15:20 GMT</pubDate>
            <atom:updated>2022-04-27T09:16:04.827Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello World. I hope you are doing well. This article is not a technical but more towards pleasure reading. Idea is to tickle your thoughts so that you can take meaningful decisions ahead. Following are some analogies with real life examples that will help you think programming.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*isziKtVL3FD8zIN-yt6aUg.jpeg" /><figcaption>Image only for representation purpose</figcaption></figure><h3>Code for today</h3><p>Have you ever imagined about hitting the road with your eyes closed. A road unknown to you. Some can try their luck and manage to take that risk, but many can’t. Though walking and carrying ourselves is our day to day activity, we are used to it and have practice hundreds of time. We are sure when we take a step forward. But when we try to walk in a shallow river then we try to find a stable surface only then place our foot.</p><p>This is very similar to writing our code. You can only code if the requirement is clear in your head. Even the smallest unit has to be very clear and one must be able to visualise it. If you can visualise it and find no loose ends then coding is pretty good to start.</p><p>You must only code for the requirements those have clarity today. Any unclear requirement must go through brainstorming sessions with stake holders. Remember, if requirements are difficult to explain, it is an indication that it is not defined clearly. One approach could be dividing requirements in to sub-requirements, identify and address fuzzy part.</p><h3>Software is an ever improving Portrait</h3><p>Have you seen an artist working on a live portrait? Does he/she manage to create final output at once? No, the process is based on a technique of iteratively progressing in a systematic way to achieve desired goal.</p><p>This is same with Software Development, Programming is an Art and you need to think like an artist. Complex problems can be solved only by breaking them into smaller problems and then conquering each.</p><p>Each Software development starts with sketching a bare minimum structure by creating abstractions, creating interfaces, thinking about data and its structure. Once that is done then next iteration include realising those abstractions by writing implementations, going deeper and deeper into implementations and coding for smallest unit possible. Wiring them together and testing and so on.</p><p>Re-Iterating like a sketch is the journey of Software development and for that, one needs to master <strong><em>The</em></strong> <strong><em>Art Of Refactoring</em></strong>.</p><p>Refactoring simply means organising and re-organising the code without changing its behaviour. These could be anything like <strong>Extracting a Method</strong> if the code is repeated more than once or extracting because some lines of code are specifically doing only one thing, <strong>Identifying the Dependencies </strong>by simply drawing the meaning or relating them with real world entities(Like Cycle Depends on Tire and not wise versa) and still preserving the behaviour of a Cycle or a Tire etc.</p><p>I would recommend to <strong>read a book</strong> on Refactoring. Here are couple of books you may start with.<br>1. Refactoring: Improving the Design of Existing Code — Martin Fowler</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/160/1*WMVkn6961e7EighcjqWRkw.png" /></figure><p>2: Working Effectively with Legacy Code- Michael C. Feathers</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/162/1*eW6lImu4cKNwdNkz302n3w.png" /></figure><h3>Test Harness</h3><p>As the software grows, world of things are going to happen with it. Tests will help you to keep a track of your software behaviours. A software is a result of various <strong>Imaginary Rules</strong> that solves a particular Human problem. As time progress it will be very difficult to remember all of them. We might want to add features and check rest of the software is behaving as expected. This could be a repetitive task and could happen on daily basis and so we need some measures to take care of it. Tests are those measures. Computers can keep repeating and running test cases against our software every day or every couple hour without exhausting unlike Human.</p><p>Generally during our schooling very less emphasis given on writing a Unit Test and most of us know Unit Testing theoretically only. Notions like, Unit testing is kind of extra effort, why should we manage two code-bases? If we are making mistakes in writing code what is the guarantee these so called “test code” will be error free? This one is my favourite “We are already writing perfectly working codes, why do we need tests for?”. All these notions create barriers and make even more difficult to understand importance of Tests.</p><p>Let me admit, we also went through all these reluctant thoughts. One peculiar experience if you are starting to learn Tests very late in your career is, even if you read articles, read books you will kind of understand what an author is trying to make you understand but still it will some way not make sense initially. Concepts will sound very obvious but still it will not “Click”. It is very similar to attain “Inner Peace”. Everything else we learnt was knowledge but this part is Wisdom.</p><blockquote>So, what shall we do to imbibe this wisdom? Well the answer to it is also a wise.<br>Take a leap of faith. Surrender to your tests</blockquote><p>You will have to forget that you are a perfect programmer. Write a test, give some input to the Class you are testing and expect some output. This should be even before you write anything in the said Class. The test will fail. Then write code only to pass that test, just enough to pass the test. Leave next behaviour for up coming next test. Don’t think beyond this class and keep on writing tests and passing them until the desired behaviour of the said class is achieved. Don’t hop between other classes. There might be situations like the said class will need to collaborate with other classes but again those classes don’t exist. We can still keep on writing test and passing them for the current class by using techniques of <strong><em>Mocking and Faking</em></strong>.</p><p>You may learn these things on internet there are lots of Testing, Mocking libraries available for almost every kind of programming platform.</p><p>For Java you may check out Junit4, Junit5, Mockito. Similarly for Kotlin to name some Kotest, Mockk</p><h3>Don’t Re-invent</h3><p>Programming and Programmers have been evolving since 1960&#39;s. They have had hit various roadblocks and have addressed most of them. Like the real problems in life there is no one solution to every problem, similarly there have been categorisations of such solution those have been lying in scripts, books, published papers etc. We must learn from such documentations, this will fast-forward us and we will be able to learn from their mistakes and from their findings and from their solutions.</p><p>One way to start is by learning Programming patterns. There are 3 categories of programming pattern.</p><blockquote>Creational<br>Structural<br>Behavioural</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*APgk6W4zjyk-tn9S4Ve49Q.png" /><figcaption>Creational Pattern</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*3PIWyieYhKhsXRxdQVbM2g.png" /><figcaption>Structural Patterns</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*nRTngDhPonEw7cd1yVtYZw.png" /><figcaption>Behavioural Patterns</figcaption></figure><p>Check all of these in detail with example make a quick reference note so that you can revisit at any point of time.</p><p>Additionally, also learn about Architectural Patterns like <strong>MVC, MVVM, MVP, MVI… etc</strong>. Describing these patterns is out of scope of this article as I have promised you this will not be a techie one.</p><p>Having said that do understand the intent of Architectural Pattern. These patterns are adopted to make the communication between developers easier. In short it define more or less what code will go where, and if you are looking for something how should one navigate to it. When working in teams it save you from grave reworks.</p><p>Learn about some philosophies like DRY( Don’t Repeat Yourself) and SOLID principals. With an intent to gain wisdom same as learning Tests. More over all of these things will help you write decoupled and reusable code. Once you get the grip of these things you will not be that same person anymore. Your approach to problems will be different. Your understanding about what is not important will drastically change, eventually will save you from over-engineering. You will understand difference between Framework code and Business logic, this distinction will allow you to defer or delay some decision till the later stage of software development.</p><p>All of these stuff will enable you to Enjoy Software Engineering. Just like an Espresso, for you to develop liking to it will take some time. Its worth it.</p><h3>Develop Empathy</h3><p>As we learnt, its ideal to look for a solution for a problem if that has already been addressed by someone before, can save you from Re-Inventing same. This mean we are together into this and it is the community that contributes to your work and it is you who will contribute to community sooner or later. So be Empathetic. This is the most important gear for a Programmer to progress in career and life.</p><p>As we are in transition every time similarly every one else is in their respective fields. It is important that you request and appreciate everyone. Don’t hesitate to say Thank you even if you think its merely a formality. Respect time and efforts of everyone. If you are working in cross functional team and blessed with QA(Quality Assurance Engineers), even if they logging bugs for you, is kind of helping you and is trying to save you and company from grave problems.</p><p>One quick way to understand the feedbacks is to try understanding their role. Have a friendly discussion and try to find what day to day challenges they face and they work in what constraints.</p><p>Eventually your empathy will make some humble friends around you. Hence a good working culture.</p><blockquote>Lastly I would ask you to always be Useful. Be Enablers. Our existence must always benefit people around us.</blockquote><p>Do let me know your thoughts. If you think if there is a room for improvement in this article we can always accommodate them here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19caedfc1620" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/an-informed-programmer-19caedfc1620">An Informed Programmer.</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Disabled State Alpha: Material Button]]></title>
            <link>https://owaisidris.medium.com/disabled-state-alpha-material-button-c2d21607ce7c?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2d21607ce7c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[themes]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Wed, 03 Nov 2021 07:00:24 GMT</pubDate>
            <atom:updated>2021-11-03T07:26:19.528Z</atom:updated>
            <content:encoded><![CDATA[<p>A very small write up to acheive disabled state of desired color or Opaticy.</p><p><strong>Prerequisites</strong></p><p>Knowlegdge of Material Design basic theming.</p><p>In my case I only need to change default opacity of Button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/143/1*IblZwLmi1rWBLxtc3FH1gA.png" /><figcaption>Desired Disabled state</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/160/1*PfXxeSC3udYFBdrFes8L2w.png" /><figcaption>Default Enabled sate</figcaption></figure><p><strong>Steps</strong></p><ol><li>Add a statful color in your colors folder</li></ol><pre><em>&lt;?</em>xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;<em>?&gt;<br></em>&lt;selector xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;&gt;<br>    &lt;item android:color=&quot;?attr/colorPrimary&quot; android:state_enabled=&quot;true&quot;/&gt;<br>   <strong> &lt;item android:alpha=&quot;0.10&quot; android:color=&quot;?attr/colorPrimary&quot; android:state_enabled=&quot;false&quot;/&gt;</strong><br>    &lt;item android:color=&quot;?attr/colorPrimary&quot;/&gt;<br>&lt;/selector&gt;</pre><p>color_material_disabled_button</p><p><strong>Main Theme</strong></p><pre>&lt;item name=&quot;<strong>materialButtonStyle</strong>&quot;&gt;@style/Widget.MyApp.MaterialButton&lt;/item&gt;<br>&lt;item name=&quot;<strong>shapeAppearanceSmallComponent</strong>&quot;&gt;@style/ShapeAppearance.MyApp.SmallComponent&lt;/item&gt;</pre><p><strong>Button Styles</strong></p><pre>&lt;style name=&quot;Widget.MyApp.MaterialButton&quot; parent=&quot;Widget.MaterialComponents.Button.Icon&quot;&gt;<br>    &lt;item name=&quot;textAllCaps&quot;&gt;false&lt;/item&gt;<br>    &lt;item name=&quot;minHeight&quot;&gt;52dp&lt;/item&gt;<br>&lt;/style&gt;</pre><pre>//Custom Style<br>&lt;style name=&quot;Widget.Shaadi.MaterialButton.Unelevated&quot; parent=&quot;Widget.MaterialComponents.Button.UnelevatedButton&quot;&gt;<br>    &lt;item name=&quot;textAllCaps&quot;&gt;false&lt;/item&gt;<br>   <strong> &lt;item name=&quot;backgroundTint&quot;&gt;@color/color_material_light_grey_button&lt;/item&gt;<br>&lt;/style&gt;</strong></pre><p><strong>Shape Theme</strong></p><pre>&lt;style name=&quot;ShapeAppearance.MyApp.SmallComponent&quot; parent=&quot;ShapeAppearance.MaterialComponents.SmallComponent&quot;&gt;<br>    <em>&lt;!--Your custom shape here--&gt;<br>    </em>&lt;item name=&quot;cornerFamily&quot;&gt;rounded&lt;/item&gt;<br>    &lt;item name=&quot;cornerSize&quot;&gt;20dp&lt;/item&gt;<br>&lt;/style&gt;</pre><p><strong>Theme Overlay:</strong> to get different colored buttons.</p><pre>&lt;style name=&quot;ThemeOverlay.MyApp.Button.Blue&quot; parent=&quot;&quot;&gt;<br>    &lt;item name=&quot;colorPrimary&quot;&gt;@color/colorAccent&lt;/item&gt;<br>&lt;/style&gt;<br><br>&lt;style name=&quot;ThemeOverlay.MyApp.Button.Grey&quot; parent=&quot;&quot;&gt;<br>    &lt;item name=&quot;colorPrimary&quot;&gt;@color/grey_27&lt;/item&gt;<br>    &lt;item name=&quot;colorSecondary&quot;&gt;@color/grey_27&lt;/item&gt;<br>    &lt;item name=&quot;colorOnPrimary&quot;&gt;@color/colorTextTertiary&lt;/item&gt;<br>&lt;/style&gt;<br><br><strong>&lt;style name=&quot;ThemeOverlay.MyApp.Button.LightGrey&quot; parent=&quot;&quot;&gt;<br>    &lt;item name=&quot;colorPrimary&quot;&gt;@color/grey_33&lt;/item&gt;<br>    &lt;item name=&quot;colorSecondary&quot;&gt;@color/grey_33&lt;/item&gt;<br>    &lt;item name=&quot;colorOnPrimary&quot;&gt;@color/grey_3&lt;/item&gt;<br>&lt;/style&gt;</strong></pre><p>2. <strong>Finally in your Layout</strong></p><pre>&lt;com.google.android.material.button.MaterialButton<br>    android:id=&quot;@+id/btn_undo&quot;<strong><br>    style=&quot;@style/Widget.MyApp.MaterialButton.Unelevated&quot;<br></strong>    android:layout_width=&quot;wrap_content&quot;<br>    android:layout_height=&quot;wrap_content&quot;<br>    android:layout_marginStart=&quot;10dp&quot;<br>    android:layout_marginEnd=&quot;12dp&quot;<br>    android:minWidth=&quot;34dp&quot;<br>    android:minHeight=&quot;45dp&quot;<br>    android:text=&quot;@string/undo_last_swipe&quot;<br>    android:textSize=&quot;10sp&quot;<br><strong>    android:theme=&quot;@style/ThemeOverlay.MyApp.Button.LightGrey&quot;<br></strong>    app:icon=&quot;@drawable/ic_undo&quot;<br>    app:iconGravity=&quot;textStart&quot;<br>    app:iconPadding=&quot;6dp&quot;<br>    app:layout_constraintEnd_toStartOf=&quot;@id/btn_partner_preference&quot;<br>    app:layout_constraintStart_toStartOf=&quot;parent&quot;<br>    app:layout_constraintTop_toTopOf=&quot;@id/btn_partner_preference&quot; /&gt;</pre><blockquote>BackroundTint: This will take care of disabled state opacity</blockquote><blockquote>Style: This will take care of button size and text case and button specific attributes</blockquote><blockquote>Theme: Will take care of Shape and Colors.</blockquote><p>My effort is to make this article for a reference and not for the pleasure of reading. So that you see what is important while hunting for an answer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2d21607ce7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Screen BottomSheet Dialog]]></title>
            <link>https://owaisidris.medium.com/full-screen-bottomsheet-dialog-b586974f56a1?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b586974f56a1</guid>
            <category><![CDATA[bottomsheetdialogfragment]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[bottomsheet]]></category>
            <category><![CDATA[fullscreen]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 18:13:44 GMT</pubDate>
            <atom:updated>2021-07-13T18:47:27.800Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is a straight forward way to get it work first before placing any view. This is an inspired article and credits are mentioned below. If you have come this far you might have already visited official design doc link</p><p><a href="https://material.io/components/dialogs/android#full-screen-dialog">Material Design</a></p><p>Now the problem here is to get it work in one go. I have spent almost a day exploring different hacks while clinging to some article more than others. To acheive this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/1*cGXWouIA1bkvsJVnPqGSFQ.gif" /><figcaption>End result</figcaption></figure><p>Check out this Github link for complete implementation.</p><p><a href="https://github.com/owaistnt/FullScreenBottomSheetDemo">owaistnt/FullScreenBottomSheetDemo</a></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/65b946d71b3a9ceb5917db1594537273/href">https://medium.com/media/65b946d71b3a9ceb5917db1594537273/href</a></iframe><p>Example</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*-__11P8cUz5CyAzA.png" /><figcaption>credit: BetterProgramming@Medium</figcaption></figure><p>Credits</p><ul><li><a href="https://www.programmersought.com/article/48737668916/">BottomSheetDialog</a></li><li><a href="https://medium.com/@oshanm1/how-to-implement-a-search-dialog-using-full-screen-bottomsheetfragment-29ceb0af3d41">How to implement a search dialog using full screen BottomSheetFragment</a></li><li><a href="https://betterprogramming.pub/bottom-sheet-android-340703e114d2">Fullscreen Bottom Sheet</a></li><li><a href="https://medium.com/swlh/bottomsheetdialogfragment-made-simpler-b32fa8e20928">BottomSheetDialogFragment Made Simpler</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b586974f56a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fastlane Setup for Android]]></title>
            <link>https://medium.com/geekculture/fastlane-setup-for-android-20615722843d?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/20615722843d</guid>
            <category><![CDATA[fastlane]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Wed, 26 May 2021 14:53:07 GMT</pubDate>
            <atom:updated>2021-05-29T07:14:28.461Z</atom:updated>
            <content:encoded><![CDATA[<p>Simplified steps to setup fastlane for you Android Project.</p><p><em>This is a 2nd part of Fastlane Series. You might want to checkout following</em></p><ol><li><a href="https://owaistnt.medium.com/installing-fastlane-in-ubuntu-c3a7044356d2"><strong><em>Installing Fastlane in Ubuntu</em></strong></a></li></ol><p><strong>Prerequisites</strong>:</p><ul><li>ruby 2.5 or above</li><li>Ubuntu 16.04 or above</li></ul><p>Following steps are required to complete the setup.</p><ol><li>Install Ruby and Fastlane. Follow this article <a href="https://owaistnt.medium.com/installing-fastlane-in-ubuntu-c3a7044356d2">Installing Fastlane in Ubuntu</a></li><li>Install Bundler</li><li>Setup your Android Project</li><li>Create Service Account with Google Console</li><li>Use a Json from 4 to initialise fastlane in project</li></ol><h3>Install Ruby and Fastlane</h3><p>This should give you an output</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/0*Z6nVHwUktkrQdlbt.png" /><figcaption>From previous article</figcaption></figure><h3>Install Bundler</h3><blockquote>sudo gem install bundler</blockquote><h3>Setup your Android Project</h3><p>Create a <strong>Gemfile </strong>in you root directory of project. Containing following text</p><pre>source &quot;https://rubygems.org&quot;<br><br>gem &quot;fastlane&quot;</pre><p>Run following command and add <strong>Gemfile and Gemfile.lock </strong>to your version control</p><blockquote>bundle update</blockquote><p>Following was my output ending with Bundle Updated</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*-ga1lIOmO4bN1zDq74-NyQ.png" /><figcaption>output of bundle update</figcaption></figure><h3>Create Service Account Google Console</h3><p>Actual docs actually have quite a good explanation so I won’t do anything additional. <a href="https://docs.fastlane.tools/actions/supply/">Follow here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EqxgudtA-42SdUX7T_ktAg.png" /><figcaption>Steps to create json secret file</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*DhhyKN0Td9RSIoheuhhGVg.png" /></figure><p>This json secret file is needed during the initialisation of fastlane. Fastlane require path to this file to function.</p><p>The image shows starting point where you will find API Access on new Google Play Console.</p><h3>Use a Json from 4 to initialise fastlane in project</h3><blockquote>fastlane init</blockquote><p>above command will be executed and it will ask for 2 things<br>1. Package Name (com.krausefx.app):<br>2. Path to the json secret file. (created in step 4)</p><p>If all goes well rest of the execution is like a walk through of fastlane doc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F14J8cRLBOlkYOVCFVHBqg.png" /><figcaption>Meta data and screenshots</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8BBQiPT06QnYWPdECC7hgA.png" /><figcaption>Lanes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_aviYn7YEbBNK6cRubBHBQ.png" /><figcaption>Customise Fastfile</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a2DTHLC3dsHoMJqFdDb3Jg.png" /><figcaption>Final output</figcaption></figure><p>Finally Test your Fastlane</p><blockquote>fastlane</blockquote><p>The above command give following output. How ever it is recommend to use</p><blockquote>bundle exec fastlane</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gYZGp12_IK7HRsGvklZxpA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20615722843d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/fastlane-setup-for-android-20615722843d">Fastlane Setup for Android</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing Fastlane in Ubuntu]]></title>
            <link>https://owaisidris.medium.com/installing-fastlane-in-ubuntu-c3a7044356d2?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3a7044356d2</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[fastlane]]></category>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Wed, 26 May 2021 13:50:02 GMT</pubDate>
            <atom:updated>2021-05-27T06:14:57.148Z</atom:updated>
            <content:encoded><![CDATA[<p>Article to help developers trying out fastlane for the first time. Most of the motivation is dependent on how smooth we manage to do the setup. Here is a way I found useful.</p><p>I have also updated in one of the answer on <a href="https://stackoverflow.com/a/67706188/3717301">Stack Overflow</a></p><p>Lets get started</p><h3><strong>Install ruby</strong></h3><pre>sudo apt install ruby ruby-dev</pre><p>Add following to top of your “~/.profile” file</p><pre>export LC_ALL=en_US.UTF-8<br>export LANG=en_US.UTF-8</pre><p>Check of any errors with source ~/.profile command. If there is not output means all is good.</p><h3><strong>2. Install Build essentials</strong></h3><pre>sudo apt-get update<br>sudo apt-get install build-essential</pre><h3><strong>3. Fastlane depends on Google API Clint lets install that first</strong></h3><pre>sudo gem install google-api-client</pre><h3><strong>4. Install Fastlane</strong></h3><pre>sudo gem install fastlane -NV</pre><p><strong>Check your installation</strong></p><pre>fastlane -v</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/0*GkvUITrId7ti9lEk.png" /><figcaption>Successful installation</figcaption></figure><h3>What next?</h3><p>You may check out how to setup project. <a href="https://owaistnt.medium.com/fastlane-setup-for-android-20615722843d">Fastlane Setup for Android</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3a7044356d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Programming for Front End. Any]]></title>
            <link>https://medium.com/series/programming-for-front-end-any-804d72e03b35?source=rss-980b069fcfe2------2</link>
            <guid isPermaLink="false">https://medium.com/p/804d72e03b35</guid>
            <dc:creator><![CDATA[Owais Idris]]></dc:creator>
            <pubDate>Wed, 02 Sep 2020 16:41:55 GMT</pubDate>
            <atom:updated>2020-09-02T16:41:55.978Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is especially targeted for my friends who are still trying out a perfect way to program their front end.</p><blockquote>Let me tell you that there will not be a perfect way rather way to which you might stick to a longer period of time while creating and delivering software.</blockquote><h3>GIST</h3><p>Let us quickly understand how are we going to move ahead.</p><p>We are going to think of a front end, a screen or a website or a window you are most comfortable with. It could be a phone or tablet or a website or even a VR who knows.</p><p>Our goal is to understand 2 things which describes front end very well.</p><ol><li><strong>Events</strong></li><li><strong>States</strong></li></ol><p><strong>Events</strong></p><p>Event are verbs acting on software. Source could be human touch or voice or anything. Source could also be side effect of some other event.</p><p><strong>Example 1</strong>: When user click logout. Event might lead to series of events.</p><p><strong>Example 2</strong>: When user interact with Voice Assistant</p><p>Example 3: Face unlock.</p><blockquote>Front end is any system which has some mechanism to interact with.</blockquote><p><strong>States</strong></p><p>States are current snapshots of system. These are well defined even before we write code or start a feature. State is simply where user is currently is or landed. State expose interactive ends to user. Using these ends, user interact and create events which are processed and new states are identified.</p><p><strong>Example</strong>: User install a fresh Android App. Now suppose 1st state is where a user is asked, weather wants to Login or Register. If user press login an event is generated based on current state with some parameters, system will take user to Login screen where credentials can be input. Similar is the case with Register.</p><p>All we are doing in a nutshell stated as</p><blockquote>We will provide interactive ends(Events) and subscribe for update(States).</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=804d72e03b35" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>