<?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 Sid Azad on Medium]]></title>
        <description><![CDATA[Stories by Sid Azad on Medium]]></description>
        <link>https://medium.com/@sidazad?source=rss-4c7cb7dab711------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xYL07q0dm5s1KmFvmAP38A.jpeg</url>
            <title>Stories by Sid Azad on Medium</title>
            <link>https://medium.com/@sidazad?source=rss-4c7cb7dab711------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:23:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sidazad/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[7 Qualities of “The Ideal ChatBot”]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Tonight I found myself thinking about what makes a good chatbot and that rumination gave birth to the following list that I think makes&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@sidazad/7-qualities-of-the-ideal-chatbot-7472f2a74950?source=rss-4c7cb7dab711------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@sidazad/7-qualities-of-the-ideal-chatbot-7472f2a74950?source=rss-4c7cb7dab711------2</link>
            <guid isPermaLink="false">https://medium.com/p/7472f2a74950</guid>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <dc:creator><![CDATA[Sid Azad]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 03:05:15 GMT</pubDate>
            <atom:updated>2018-06-19T03:05:15.199Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[5 things indispensable for real growth]]></title>
            <link>https://medium.com/@sidazad/5-things-indispensable-for-real-growth-30e0acdbef75?source=rss-4c7cb7dab711------2</link>
            <guid isPermaLink="false">https://medium.com/p/30e0acdbef75</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[mindfulness]]></category>
            <dc:creator><![CDATA[Sid Azad]]></dc:creator>
            <pubDate>Mon, 06 Nov 2017 04:42:03 GMT</pubDate>
            <atom:updated>2017-11-08T03:16:38.535Z</atom:updated>
            <content:encoded><![CDATA[<p>I am defining real growth as that which actually changes you for the better in a sustainable and lasting way.</p><ol><li><strong>Minimization (and the ultimate dissolution) of the Ego</strong> — Ego is the single biggest obstacle to collaboration. It’s that thing you sometimes feel in your chest that makes you angry at someone or upset at their behavior towards you or unhappy about their success or insensitive towards their pain. Minimizing the ego opens doors to embracing others and hence inviting them to embrace you and hence making collaboration and harmony, whether in the workplace or in life easier.</li><li><strong>Reducing the need for recognition or affirmation by others</strong> — The need for recognition by others is another subtle effect of the ego. Needing recognition by others affects our actions and distracts us from our real goals to alternate goals that others would recognize and affirm. Reducing the need for recognition helps keep us on track of the goals that actually matter to us.</li><li><strong>Imposing vs. Influencing</strong>— Imposing ones will or someone else to get them to do something may work at times, but never ends well in the long run. It leaves a grudge in the person who the will was imposed on and they are bound to return the favor (or not be cooperative) at some point in the future when they hold the power. It is much more effective and ethical to influence someone to do something you want them to since influencing is the art of convincing someone and hence bring them on board with your ideas. If they understand and are able to agree with you, they will also give their 100% to help achieve the objective.</li><li><strong>Seeing multiple alternate perspectives</strong> — Acknowledging that people have different perspectives and their perspectives shape their view of the worlds helps understand things that we may have accepted as fixed truths or facts in a much wider light. It also expands the mind and hence our ability to identify and understand what we witness from many different perspectives ourselves. Whether you be writing a book or designing a product, this has clear and countless advantages.</li><li><strong>Finding what works for you</strong> — You may come across many formulas that preach being the right one or best way to be. But the whole point of the universe is diversity. Even though at one level we are all one, on another level we are all unique. And this uniqueness means that each one of us has to find what works for them. So whether it be life hacks or philosophies or diets or ideas, it’s essential to be meticulous like a scientist and test what fits the bill for you, rather than accepting what’s being sold as the panacea.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30e0acdbef75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attention Hijacking (and how not to be a dry leaf drifting in the wind)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Attention Hijacking is a common modern phenomenon that happens when we aim to focus our attention on one thing but end up having it&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@sidazad/attention-hijacking-and-how-not-to-be-a-dry-leaf-drifting-in-the-wind-2661f07ddecc?source=rss-4c7cb7dab711------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@sidazad/attention-hijacking-and-how-not-to-be-a-dry-leaf-drifting-in-the-wind-2661f07ddecc?source=rss-4c7cb7dab711------2</link>
            <guid isPermaLink="false">https://medium.com/p/2661f07ddecc</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Sid Azad]]></dc:creator>
            <pubDate>Fri, 03 Nov 2017 03:03:38 GMT</pubDate>
            <atom:updated>2017-11-03T03:03:38.466Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A Fantastical Future of Software Development]]></title>
            <link>https://medium.com/@sidazad/a-fantastical-future-of-software-development-3c30ec9457?source=rss-4c7cb7dab711------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c30ec9457</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[future-technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Sid Azad]]></dc:creator>
            <pubDate>Thu, 26 Oct 2017 02:54:43 GMT</pubDate>
            <atom:updated>2017-10-26T06:47:09.020Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me jump right into it at the expense of sounding crazy — I think it’s not only possible but likely that in the future software systems will be able to compose themselves. In fact, I am very surprised that this hasn’t already happened. But given the (sorry) state of the industry, it isn’t that surprising.</p><p>So firstly, how would software systems write themselves?</p><p>Imagine the following:</p><ol><li>A Component Repository where developers checkin generic modular components.</li><li>A formal language that describes the interfaces of the software component as well as it’s test cases</li><li>A semi-formal or informal index in which the developer or the team can describe what the component does.</li><li>An NLP system trained to understand the description mentioned in (3)</li><li>A high level language where you can describe what you want the end system to do</li><li>An agent or bot (or interpreter?) that takes (5) and scans the component repository using (4) to discover components that can be used to compose the system</li><li>Another agent that deploys the system in the cloud according to the scaling specs provided in (5)</li></ol><p>So why has this not happened yet? In fact, after all the promises of the research on COTS (Components off the shelf) in the late 90s, the best we have for a component repository is GitHub (and the likes) — no offense to GitHub.</p><p>After description languages such as IDL and systems to discover web services that IBM was actively working on 20 years ago (think pervasive computing using UDDI, WSDL etc.) — none of them took off.</p><p>I think the two mains reasons are:</p><ol><li>The lack of collaboration in the software industry — There really is a each one for self culture in the industry. There is collaboration in small things, for namesake, but as software companies (and as humans) — we find it very hard to agree on standards! Hence no common standard has emerged in anything for discoverability yet. (Think browser wars, Office/Open-office, OS wars, JavaScript standards, Web services standards — need I go on?)</li><li>The pace of change — has been extreme. Innovation is disruptive but that also means that it lacks proper insight. New tools and frameworks appearing (think front end tech) before the old ones have been perfected, and then being replaced by newer ones within 6 months.</li></ol><p>Finally, why would a way for software to compose itself be beneficial?</p><ol><li>Increased innovation and efficiencies — Such as system would greatly increase the pace of development and developers would be very willing to post components here as other teams would be able to buy them.</li><li>Increased Reusability — If there’s one thing I absolutely abhor, it is repetition of software. It bothers me immensely if the same piece of software has to be written again. Having a component registry like this would mean that a software component once written can be used by many (all). Yes I know that’s what open source is, but standardization of describing component interfaces would take reusability and interoperability to a new level.</li><li>Better software — Inevitably such as system would be more robust since it will be composed of well thought of components since once would have to describe the interfaces in detail.</li></ol><p>I am positive that something similar will emerge in the next decade. Whether it be something that the industry leaders come up with or it be a grassroots effort, that remains to be seen. My money is on the latter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c30ec9457" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Complexity of Software Development]]></title>
            <link>https://medium.com/@sidazad/the-complexity-of-software-development-2f0b04c6c66?source=rss-4c7cb7dab711------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f0b04c6c66</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Sid Azad]]></dc:creator>
            <pubDate>Mon, 12 Dec 2016 05:11:48 GMT</pubDate>
            <atom:updated>2016-12-12T05:12:33.828Z</atom:updated>
            <content:encoded><![CDATA[<p>One may argue that Software Development is a relatively recent field and hence hasn’t reached the same level of maturity as say civil engineering. True, but notwithstanding that programming languages haven’t changed a whole lot in the last few decades. At least the basic concepts and constructs have remained the same. Software Development was and remains to be a complex business.</p><p>Why is that? Given that most programs can be written with relatively simple constructs such as if and for loops, functions, records/structures? Most algorithms can be written with the same (or slightly modified renditions) of the data structures that were conceived decades ago.</p><p>Most programmers don’t find standalone programs of medium complexity hard to write. In fact, working in a silo, many programmers can perform quite well. But as more features are added over time and more programmers start working on various parts of the same codebase/product, the complexity increases significantly.</p><p>Writing software is a human problem. The human brain in it’s natural state is capable of focusing on one thing at a time. It could possibly give a semblance of multitasking, but that is more akin to a processor time-slicing threads (threads of attention in case of our brains).</p><p>As programmers develop new features by changing let’s say a function or a class (the proposed change) they make an attempt to think reasonably about how the change in the behavior of a software component will affect any other piece of software that uses it. They need to consider several aspects:</p><ul><li>Who else is using this component?</li><li>What behaviors do they expect from it and does this change break those behaviors?</li><li>Even if the change doesn’t break the behavior today, do the other programmers expect the proposed changes to be made in these components or consider these to be reasonable changes in behavior?</li><li>How does this proposed change change the behavior of other components that rely on or use this component?</li><li>Even if the proposed change is acceptable in current and future expectations of this component, has the proposed change been implemented correctly?</li></ul><p>To address some of these issues the software industry uses certain best practices, the common ones being:</p><p><strong>Code Reviews</strong> — A process where one or more programmers read the changes made by the author of the change and discuss what they agree or disagree with. The result of the code review is usually a set of changes for the author to incorporate. Code reviews are definitely useful but have their own set of challenges, namely:</p><ul><li>Most teams are pressed for time and don’t actually do the code reviews very thoroughly but more as a best effort.</li><li>Most of the time the code reviewer is looking at the code in isolation rather than as a part of a larger code base. In other words, the code reviewer isn’t necessarily aware of all the various ways in which the component is actually being used by other parts of the codebase than the one that he or she is actually reviewing (unless the reviewer wrote a piece of code that uses this component, in which case it is reasonable to expect the reviewer to take into account this usage).</li></ul><p>In many cases the new logic may be complex (for example time dependent, race-condition prone, multithreaded code) that even an accomplished programmer may not be able to account for all the possible conditions in which the code being reviewed may fail. The perspective of the reviewer is very different from that of the programmer as the programmer is actually implementing the component. In some ways, the programmer is a lot more involved (and probably vested) in the correct workings of the component. To understand why consider who understands a book better, the writer of the book or the critic who reads it thoroughly (even if the critic may be an author of a related but different book)? Also, traditionally and typically programmers are more responsible for the correct working of their software than the reviewers that review it.</p><p><strong>Testing</strong> — Software testing is the single most important practice in software development. Testing can be of several kinds but broadly their are two categories, unit testing and integration (or system) testing.</p><p>Unit testing tests a single self-contained piece of software while system testing tests several pieces of loosely (or tightly) connected software components as a single system. Testing, although invaluable and essential for anything that isn’t frivolous software development, isn’t a perfect practice. Some of the inherent problems are:</p><ul><li><strong>The correctness of test cases — </strong>Who shaves the barber? Or who tests the tests themselves for correctness. A logically inconsistent test may prove that a software component with a similar logical flaw works and result in a catastrophe.</li><li><strong>The completeness of the test suite</strong> — It is impossible (or at least impractical in most industries) to tests all possible combinations of inputs to a software component and hence programmers (or more ideally, testers) choose the inputs that are representative of a ‘class’ of inputs. Ideally tests should be written for every decision point in a piece of software and for every possible class of input and for all boundary conditions. But most of the time this isn’t what happens. It takes an enormous amount of time and discipline as well as enforcing of best practices to ensure this. Hence most test suites aren’t complete.</li><li><strong>System Testing =&gt; NOT EASY</strong> — System testing is HARD. Many a time components aren’t written in such a way that they can be easily tested as a whole system. Some components don’t lend themselves to testing and need to be changed to be made more testable.</li><li><strong>3rd Party components</strong> — 3rd party components aren’t always easily testable as the vendor may not have made them so. As a result, a system that uses them is also not fully testable.</li></ul><p><strong>An unpredictable environment</strong> — Many UAT and TEST environments aren’t as stable as production environments. This is partly due to resource constraints and partly due to the inherent nature of such environments (since systems are being deployed to such environments more frequently than production environments). Hence they provide an additional hurdle to system testing.</p><p><strong>Formal Methods, Software Components &amp; Contract by Design</strong>: These methods are less widely used but are areas of theoretical computer science research.</p><p><strong>Formal methods</strong> are an automated way of testing a software component by testing the state of the system after the execution of each statement. This is obviously impractical in many cases, especially with the untenable complexity of modern languages. Also, the time needed to test software components (not to mention 3rd party libraries) probably makes this method limited to theory.</p><p><strong>Design by Contract</strong>: This is the practice of meticulously specifying the inputs, outputs, pre-conditions and post-conditions of units of software components (such as functions, classes) and having the execution environment verify these at runtime. Surprisingly this practice isn’t as widely used as I would have expected. One of the reasons I can think of is that such checks at runtime would make time-sensitive systems slow. The other reason is probably the lack of built-in support for Design by Contract in most popular languages. Lastly, time taken to meticulously think about these contracts, not to mention the ongoing maintenance of the pre/post-conditions as behavior evolves is a major factor as well. TDD or test driven development is often used as a substitute to specify and enforce behavioral constraints.</p><p>The field of software development is complex and the development of new systems, platforms, tools, devices and languages is increasing complexity on an hourly basis. Countless hours are spent in diagnosing bugs after they cause production issues and affect clients. It remains to be seen whether the standard practices of testing software will prove to be sufficient for rapid software development. It suffices to say that we aren’t there yet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f0b04c6c66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Direction]]></title>
            <link>https://medium.com/@sidazad/direction-789a8e736a9?source=rss-4c7cb7dab711------2</link>
            <guid isPermaLink="false">https://medium.com/p/789a8e736a9</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[world]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Sid Azad]]></dc:creator>
            <pubDate>Tue, 06 Dec 2016 04:24:57 GMT</pubDate>
            <atom:updated>2016-12-06T05:04:20.536Z</atom:updated>
            <content:encoded><![CDATA[<p>There is a lot wrong with the world. A deeply elevated spiritual person may say that everything is in it’s right place and cannot be any other way. Sure, this is one way of looking at things. But by looking at things in this manner not much is going to change. To change things it becomes necessary to come down a few levels into the world and realize that things are <strong>not </strong>how and where they should be.</p><p>Are we going in the right direction? Let’s take for instance the preponderance of technology (bear in mind that I am a technologist by profession and a scientist by nature and hence hold no prejudices against technology). Where is this taking us? Are we better off than we were say 20 or 50 years ago? Depends — on what is meant by better. Sure, a lot of things have become easier. But what about the mind which is being bombarded from all directions by information, news, notifications, social updates, offers, texts, tweets, emails, snaps and cat and koala pictures? Can the mind handle this? Even if it can, should it? After all, most meditative practices, whether spiritual or otherwise advocate silencing the mind. Many management and productivity practices also advocate focus and single-mindedness. Can we remember this? I mean not for a minute or an hour or a day. But constantly. What are we sacrificing by over-indulging in technology? Had we not had so much technology or so many disruptions around us, could we have been developing some other faculties? Seriously, could we?</p><p>Anyway, I digress. Even apart from the technological proliferation a lot remains wrong with the world. And it’s not any one person’s fault. In fact, it’s probably nobody’s fault. It’s our own. Each of us are at fault. Since we aren’t making an effort to step back and realize that a lot is wrong and then to figure out what really is needed to fix it. What are we missing and what is that we yearn after and that is so fleeting that despite a lifetime being spent we never obtain it? And if so, are we chasing something that we shouldn’t be? Maybe our whole premise is incorrect. Maybe we should be re-thinking our entire approach and our attitude towards life, towards our situation. Our situation of having been put on this planet under constraints — constraints of our bodies, and our minds (let’s admit that our bodies as well as our minds are imperfect instruments and leave a lot to be desired). What then is the purpose of being in this situation? Can we change it? Can we <strong>REALLY</strong> change it? I mean, I’m not talking about discovering penicillin but something more fundamental. Not a band-aid but something more essential, deeper which changes the equation?</p><p>Let’s at least acknowledge that we are in a situation together — all 7 billion of us — and then maybe some of us can also agree that a deeper understanding is needed as a first step to fixing what is not currently in order.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=789a8e736a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Powerful Common-sense changes in dietary habits]]></title>
            <link>https://medium.com/@sidazad/powerful-common-sense-changes-in-dietary-habits-7847e36569e8?source=rss-4c7cb7dab711------2</link>
            <guid isPermaLink="false">https://medium.com/p/7847e36569e8</guid>
            <category><![CDATA[future-of-food]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[food]]></category>
            <dc:creator><![CDATA[Sid Azad]]></dc:creator>
            <pubDate>Tue, 16 Feb 2016 18:26:16 GMT</pubDate>
            <atom:updated>2016-02-17T02:26:04.521Z</atom:updated>
            <content:encoded><![CDATA[<p>Food is an essential part of our Life. It sustains us and gives us energy to use our bodies to help achieve our goals. But most of us aren’t very conscious of what we put in our bodies and how we get it in there. I have spent some time experimenting on myself with a few simple common-sense dietary changes. Most of these things may seem obvious and are already stated in different holistic philosophies and even Hatha-Yoga. Here are a few:</p><ol><li>Chewing your food — This is probably the most important point I will mention in this article. Food is best chewed in a calm state (since if you are excited chances are you will swallow quickly without chewing it well) and thoroughly. Some practices (Hatha-Yogic) even suggest chewing 32 times from each side before swallowing. This may be overkill but each must find their own sweet spot. From a common-sense point of view this makes sense since the better your food is chewed the less work your Digestive System would need to do.</li><li>Conscious Cooking — When cooking your own food, try to do it in a conscious and calm (mindful if you will) state as well. I can’t provide the rationale for this but I have tried this and found that the food was of overall better quality if I am not rushed while cooking it. For those in holistic or yogic philosophies you could also think of this as instilling the right vibrations in your food.</li><li>Don’t eat stale food — Sure it could be enticing to eat that slice of pizza from last Friday but would you like your body to look rotten from the outside? If not, then why do you want to put something rotten/stale inside it? Try to eat fresh, organic when you can. (I think it’s unfortunate that food isn’t de-facto organic these days and that organic food is more unaffordable for many — hopefully that will change in the future)</li><li>Make small substitutions — Every time you go to buy lunch you see that luscious slice of pizza or chicken parm sandwich or philly cheese steak and obviously the moroccan lentil salad or kale with tomato and feta loses out. Be a bit adventurous and brave and every once in a while choose the healthy options. Your palette is in your control — you may think you won’t like the healthy option but try it once, twice and the fact is that when you are eating it — you do tend to like it and you feel better as well. Once you are done eating, the pleasure of the palette is gone but the effects of the food linger. If you choose the fresher, healthier option you are probably feeling better and less sleepy, lethargic. Try it once— be brave.</li><li>Cook your own meals as much as you can — When you are cooking your meal and trying to do it in a good consciousness, with the freshest ingredients and to your taste and digestive preferences, you will always fare better than eating out or ordering food. When cooking, try to cook 2 things at the same time to reuse some of the effort of cutting vegetables etc.</li><li>Don’t ever overeat — This is another extremely important point. Your stomach is not a trash bag that needs to be filled to the hilt. If you eat calmly paying attention to how your stomach is feeling after every bite, there is a point at which you will know that your stomach has had what it needs. Any more that you put in it is out of the pleasure of the palette you are getting. That may make your palette happy but your stomach is unhappy — or should I say upset. This is extremely important and is something that may be initially hard to do since you are not used to it, but with practice it can become second nature. Try it, leave that last bite of the steak. Surely you are stronger than that!</li><li>And finally, don’t believe me. Try this for yourself for a week and see what works or doesn’t work for you. Even if you do it for 1 meal a day. Give it a shot and if you have a scientist’s curiosity you should be curious about finding out what your body is like and how it reacts to culinary habits. It’s an experiment, be brave and try it!</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7847e36569e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>