<?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 Anish E=mc² Talwar on Medium]]></title>
        <description><![CDATA[Stories by Anish E=mc² Talwar on Medium]]></description>
        <link>https://medium.com/@technogsalad?source=rss-1acebcbf4b63------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*47wPt1iryQWarcdC.jpg</url>
            <title>Stories by Anish E=mc² Talwar on Medium</title>
            <link>https://medium.com/@technogsalad?source=rss-1acebcbf4b63------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:18:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@technogsalad/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[Let’s Prototype!]]></title>
            <link>https://medium.com/@technogsalad/lets-prototype-4afc77338e94?source=rss-1acebcbf4b63------2</link>
            <guid isPermaLink="false">https://medium.com/p/4afc77338e94</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Anish E=mc² Talwar]]></dc:creator>
            <pubDate>Mon, 18 Sep 2017 13:53:04 GMT</pubDate>
            <atom:updated>2017-09-18T13:53:04.230Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33pwmeOA5AeX8Ra4QuFqTA.png" /></figure><p>Hello! Hope everyone had amazing weekend! Back to work…LOL its Monday! Today I will discuss about various prototyping tools which I used and which I will be using in future. A prototype is used to enhance and give a better vision of the project as a whole.</p><p>In design we need to express out concept and thinking.. as Steve Jobs said “Design is not about the looks, its about how it works!” I prefer not to show my clients and my company team pdf files/images of design. I use prototyping tools which makes work more easier. Also human beings are visual so its always good to show them how the design works and make them experience the different transitions, effects etc.</p><p>Prototyping and user testing is the best way to create amazing and successful products. How to build a good prototype is good questions but which tools &amp; resources to used is really an important question. Its easy to stick with one tool and be comfortable with but its really important to learn and explore new tools as they have amazing feature and lots of plugins + integrations!</p><ol><li>Invision</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*F91BVoGrNFHYrYGpE0MsyQ.png" /></figure><p>Invision is always one of the amazing design, prototyping and collaboration tool. It is great web based prototyping tool and teams can write comments and quickly collect feedbacks. Invision supports files in PNG, JPG, GIF, AI and PSD format.</p><p>2. Marvelapp</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w0foL9ZITFlZrYarvfVjgA.png" /></figure><p>Marvelapp is one of my personal favourite prototyping tool. It has plugins for sketch(design tool) and its easy to use. It took me less than 30mins to figure out how this tool works… Very good for quick and rapid prototyping. Provides sharing with team and you can add people from your team to not only give feedback but to also collaborate.</p><p>3. Atomic.io</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KyKoDXtvaGXk1aQeJ0wTvA.png" /></figure><p>Atomic.io is another tool which I use and it has great support to both design and prototyping. One thing it lacks is that we cannot record our prototype. Which can be easily fixed by using third party screen recording tool but still I would be really happy if they introduce this feature.</p><p>4. Adobe XD</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qzRvydXvc9N1XsO2MuXewQ.png" /></figure><p>AdobeXD has very good features and for sure we can connect with adobe creative suite libraries. Also with updated UI resources one can jumpstart their design using provided high quality UI components. Furthermore, it has paste styles and paste interactions with which we can copy the style from one object and paste it onto another to apply all and similarly we can copy paste interactions which saves a lot of time.</p><p>5. Axure</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JPj-TFdyXP5KzKJdIXAY1A.png" /></figure><p>Without any doubt Axure is one of the leading tool for prototyping in design industry. Its amazing for prototyping of web based applications however it lacks some features when it comes to mobile based applications. Its used to build sophisticated prototypes and wireframes.</p><p>6. Framer</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5zyQunogOjFinVyCUD-_cw.png" /></figure><p>Framer is best for designer’s who code. It gives you the freedom to design and then make them live using build in animations and also we can modify using code. Sharing our design with team is made easy and this tool is again very easy to learn and one of my favourite.</p><p>Conclusion</p><p>The tools I have discussed here are random order and if you guys have any more suggestions please mention in the comments. In order to compare more about these tools I will provide a resource which is amazing. Some would argue that code is quicker to begin with but sometimes its better to spend time engineering something that may fall quickly to the wayside.</p><p>Do check it out <a href="http://prototypingtools.design/">http://prototypingtools.design/</a> using this anyone can compare tons of prototyping tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RjZlbRPDDp_0NQJpqU3A7w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4afc77338e94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“6/97 Things Every Programmer Should Know”]]></title>
            <link>https://medium.com/@technogsalad/6-97-things-every-programmer-should-know-f854af65b530?source=rss-1acebcbf4b63------2</link>
            <guid isPermaLink="false">https://medium.com/p/f854af65b530</guid>
            <category><![CDATA[wisdom]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Anish E=mc² Talwar]]></dc:creator>
            <pubDate>Fri, 15 Sep 2017 13:15:41 GMT</pubDate>
            <atom:updated>2017-09-15T13:15:41.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*3RsZzl0paU_LVFukYRht1A.png" /></figure><p>Must be wondering what’s the 6/97? I will help you figure it out :D</p><p><em>Don’t just learn the language, Understand its Culture by Anders Noras</em></p><p><em>Don’t repeat yourself by Steve Smith</em></p><p><em>The Golden rule of API design by Michael Feathers</em></p><p><em>Know well more than two programming languages by Russel Winder</em></p><p><em>Your customers do not mean what they say by Nate Jackson</em></p><p><em>The single responsibility principle by Uncle Bob</em></p><p><strong><em>How my approach changed</em></strong></p><p><strong><em>Don’t just learn the language, Understand its Culture by Anders Noras</em></strong></p><p>Throughout my programming career, I’ve been very focused and enthusiastic about learning different programming languages. Every time I used to learn a new programming language, I used to dive in and try out the syntax and programming structure but after reading the article “Don’t just learn the language, Understand its Culture”, I plan to focus on design patterns and multiple ways to implement a certain thing for example using the ternary operator, which is another way of implementing if-else condition statements.</p><p>Although I was aware of the basic idea this article states, it has certainly given me an enhanced perspective and outlook going forward with learning programming languages. As every programming languages has a different design paradigm, which reflects the specific purpose or reasons for it was created, it also has varying strengths and weaknesses. With so many programming languages at our disposal in the present era, choosing the most appropriate one to implement the solution to your problem is vital. Hence I plan to lay more stress on “understanding the culture” which includes to understand if they are better suited for certain problems, used more in certain industries, or favored by programmers with a particular approach.</p><p><strong><em>Your customers do not mean what they say by Nate Jackson</em></strong></p><p>“Your customers do not mean what they say” reminds me of the time when I used to be a freelance web developer/designer. I was working for a real estate company and the owner was really not sure of what she wanted. She asked me for a basic design and then when I drafted the first design, she asked me to make the website look more modern. I faced same problem with other clients and now I have found the way to ask what they want. I present them a mood board and also ask them for a mood board by which I can get idea about what exactly they are looking for in the design.</p><p>This image shows the example of moodboard which I ask my clients to make it and I also design it. A moodboard is a type of big collage consisting of images, color combinations and also typography from which a person gets his/her inspiration. Images can be family, nature anything which motivates or gives inspiration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*qqO_PGp5LSZZLh_J." /></figure><p>This <em>image[1] </em>shows the example of moodboard which I ask my clients to make it and I also design it. A moodboard is a type of big collage consisting of images, color combinations and also typography from which a person gets his/her inspiration. Images can be family, nature anything which motivates or gives inspiration.</p><p>As we know that service is directly proportional to customer satisfaction which basically means if customer is not receiving what they want that customer won’t be a customer for very long. After understanding and analysing the article my focus would be to gather more information. People do talk and share information, it only differs how they express that information. My solution would be to use moodboard, by which both technical and non-technical customers can express themselves. Also sometimes image says more than words so I believe this would be my approach. Taking feedback is another approach I would use as it will provide a valuable insight into the characteristics of product. Follow-up emails/calls also gives an opportunity in improving the process to understand the customer with more clarity. Also I designed and developed a client communication app. This would help in sharing information and project feedbacks.</p><p><strong><em>The single responsibility principle by Uncle Bob</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/0*2kqoEzTYPaMgie3I." /></figure><p><em>Image[2]</em></p><p>When I came across the article “The single responsibility principle” I could relate it to the design patterns we use when working in software industry. Never put all the functions together in a single class. Knowing the importance of this pattern I have learned that there should be separate modules/classes for every functionality.</p><p>Learning the single responsibility principle seems to be a daunting task at first but it is definitely important for the growth of the product and development culture. This principle will help to determine the optimal amount of classes and also will state the functionality of every class.</p><p><strong><em>What I expect to improve in my programming style</em></strong></p><p>The six principles I chose and then went through in detail will definitely improve my perspective while going about the final product as a developer and designer. They were very helpful in determining how to shape my skills and create better products. From every topic I have learned valuable points which I can use in practice and also in theory. These articles emphasize the fact that to build efficient products one requires vast domain knowledge of all the verticals. Some implementations are more efficient and compact in some programming language than others, and hence can result in an optimized final result. When I was working as web developer with Ruby on Rails I heard about DRY(Don’t Repeat Yourself) and naturally when I read this article I plan to use this for my products as it eliminates redundancy. Knowing the customer and market is always a good idea especially when you work as a freelancer, by exploring the multiple ways a customer can express his demands I can find out ways to read my customers and in turn help them to get to know what exactly they want. I plan to write programming code which is decoupled, every class has its own job. This will make sure that if I make any changes it would less likely to break the entire application. Importance of maintainability I learned from this article and also I learned that writing great code is an art but learning new programming design principles would help me to produce robust and maintainable software.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f854af65b530" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vintage Darling]]></title>
            <link>https://medium.com/@technogsalad/vintage-darling-67006803811e?source=rss-1acebcbf4b63------2</link>
            <guid isPermaLink="false">https://medium.com/p/67006803811e</guid>
            <category><![CDATA[retro]]></category>
            <category><![CDATA[vintage]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[posters]]></category>
            <dc:creator><![CDATA[Anish E=mc² Talwar]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 14:31:00 GMT</pubDate>
            <atom:updated>2017-09-14T14:31:00.908Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*gdTUcgZA41B9eQhBiYFeLw.png" /></figure><p>As we know that retro and vintage design are considered as outdated. It have amazing benefits which are overlooked by the modern designers. Basically the impression of retro design is old looking, unattractive, dull and boring. But when I started looking at amazing posters which are designed in the earlier times, I just fell in love with them. I learned a lot by looking and observing vintage posters.</p><p>Some of my favourite posters are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*59VLvGAm19Dshu4S." /></figure><p>Mads Berg’s Illustration</p><p>You can find him here <a href="https://www.behance.net/madsberg">https://www.behance.net/madsberg</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*jYb7FlUinpfVPGgo." /></figure><p>This is designed by Evgeniy Kiselev</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*7ONRZSI7zCKJiOdZ." /></figure><p>This is a mid-century ad-print which is done beautifully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*6SDcYd3aJIEEl18f." /></figure><p>Here we can see the beautiful play of typography(year 1969).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*w6Xsi6POQlu_MFjK." /></figure><p>Poster for Ulrich schnauss. Beautiful dynamics and color combination.</p><p>From all these posters and design I learned a lot and would be using some similar combinations in my future designs. Studying these designs and taking inspiration from them is really important for me. As designer’s we all have to continuously evolve our creative skillset and learn more about various color and typographies. Getting inspired from retro design and combining it with our modern approach is not a bad idea! I think this will create more interesting design results.</p><p>So keep learning, keep sharing!</p><p>So which one is your favourite? Leave comments below or if you have any other favourite poster/artwork then paste the link :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67006803811e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Programming practices may not stand the test of time]]></title>
            <link>https://medium.com/@technogsalad/programming-practices-may-not-stand-the-test-of-time-811dab399725?source=rss-1acebcbf4b63------2</link>
            <guid isPermaLink="false">https://medium.com/p/811dab399725</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Anish E=mc² Talwar]]></dc:creator>
            <pubDate>Wed, 13 Sep 2017 13:28:01 GMT</pubDate>
            <atom:updated>2017-09-13T13:36:23.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*ZIpaLB66jMBHyQ0Lz-a1AA.png" /></figure><p><strong>Obsolete</strong></p><p><em>“Although it(programming practice) may still work in some companies, its use is discourage since it could be bad practice.”</em></p><p><strong>Programming Practices</strong></p><p><em>“Programming practices are set of informal rules which are learned by programmers &amp; software community to improve the quality of the software.”</em></p><p>Hallmarks of a professional programmer are superior programming practices and techniques which he/she abides by. There are tons of programming practices which are present in the software engineering universe but how to choose among them is not just a skill but also talent and hard work which can be learned from experience and lots of practice.</p><p>This essay addresses to three of the programming practices which are obsolete which means they are no longer used in the software development industry. As we know that programming practices are important in improving our code maintainability and readability, it is very important to know the ones which are used lately and are no longer being practiced. These obsolete programming practices which are discussed below are from different programming languages and also some are very general to the universe of software engineering.</p><p>“Bye Bye! Hungarian Notation”</p><p>Hungarian notation is an identifier for a naming convention in programming practices in which name of function or variable indicates its intention. These days programmers have stopped using this notation as it creates complexity when it comes to naming, it makes the variable names long &amp; hard to memorize and it is considered to be a bad programming style. When I was exposed to this type of notation in Visual Basic programming language my experience was that I found it difficult to read and understand the code. It made the code look ugly. Furthermore, I found that the variable names are consistent which was a positive feature, but still, I thought it was a cumbersome way to code and in the modern era Integrated Development Environment displays the variable types on demand so why use such a complex notation?</p><p>Few examples are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*83lJt7UuvMbcMQ4N." /></figure><p>Fig1. Hungarian Notation example</p><p>“Multiple return points a bad idea in OOP?”</p><p>Lately, I had a conversation with a fellow programmer who totally agrees with the notion of multiple return points, well, I had to disagree and explain my point. According to my programming experience, I really think it’s a bad programming practice to use multiple return points. What I always learned and observed is that in pure object oriented programming we use only single return statement that’s all but now the idea of using multiple return statement go against the practice of OOP’s. Also from my point of view, I would go in the favor of single return point because it will make it easy for me to debug the code and it makes my code readable. Finally, we agreed that single return point is better programming practice but also I observed that if someone knows when and where to use multiple return points he/she can write highly expressive code. My advice is if your code is complex and has multiple returns points one should try splitting it into smaller methods and each method having a single responsibility. This will not only make the code readable but also it will be easy to maintain and reuse.</p><p>Example displaying multiple return points and single return point.</p><p>Fig2. Multiple return points example</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/345/0*9Db-5uYC5rAQl6hF." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/0*zSWDEb86bp14gABH." /></figure><p>Fig2. Single return point example</p><p>“Using too many global variables? Outdated javascript practice”</p><p>We have seen how javascript has evolved during the years and now it’s one of the most powerful programming languages. Earlier we used javascript only for the validation and very minimally on the front-end but now javascript is used as a full-stack for web development, means it supports both client and server side programming. However, I was curious to know what happened when we practiced javascript before it became famous and then I found some javascript practices which used too many global variables(You can still find them used in some web pages). This is the sign which displays that the javascript code is outdated. The primary reason why I will not recommend to use global variable is because in javascript all code share a single global namespace. Some supporting examples are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/0*3ZUp7yHskt7zuxhX." /></figure><p>Fig3. Bad practice of global variable in Javascript</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*KNtEr4oI0JD2JEmK." /></figure><p>Fig4. Good practice in Javascript</p><p>Hence we can observe that good programming practice is really important for good software development. Although we know that we cannot fully commit to one programming practice, sometimes I personally feel that if we can combine old and new programming practice to obtain the best from both the worlds.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=811dab399725" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>