<?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 Vaibhav Kumbhar on Medium]]></title>
        <description><![CDATA[Stories by Vaibhav Kumbhar on Medium]]></description>
        <link>https://medium.com/@vkumbhar94?source=rss-22b6f36b5ccd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fX37VmDESHX7vSkpmwhe3g.jpeg</url>
            <title>Stories by Vaibhav Kumbhar on Medium</title>
            <link>https://medium.com/@vkumbhar94?source=rss-22b6f36b5ccd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:47:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vkumbhar94/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[Want to be a good software developer?]]></title>
            <link>https://medium.com/@vkumbhar94/want-to-be-a-good-software-developer-6cf98f0c5e5e?source=rss-22b6f36b5ccd------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cf98f0c5e5e</guid>
            <category><![CDATA[success]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[career-paths]]></category>
            <dc:creator><![CDATA[Vaibhav Kumbhar]]></dc:creator>
            <pubDate>Mon, 14 Oct 2019 18:50:58 GMT</pubDate>
            <atom:updated>2020-08-26T04:26:45.995Z</atom:updated>
            <content:encoded><![CDATA[<p>A few of my colleagues and college juniors asked me about “what should we learn and how?” “What is important to learn going forward in career?”</p><p>I am here trying to answer a few frequently asked questions and a typical career path for beginner <em>coders</em>.</p><p>When a student joins an organization after graduation, initially he would be mostly inclined to curricular subject knowledge like data structures, algorithms, etc. The few years (typically 1–2 years) after graduation are very important to learn the skills of applying that knowledge to solve real-time problems.</p><p>An honest suggestion to new beginners is that please please don’t rush to change the choice of organization for money.</p><blockquote>Choose the correct role and responsibilities wisely at least for early days of your career. If you choose it with keeping only money in mind, it may put you on struggle for next few years.</blockquote><h3><strong>Keep SOLIDs in mind 24*7</strong></h3><p>Now what are SOLIDs? Many of you have read SOLID principles in context of OOPS. Read more about SOLID <a href="https://en.wikipedia.org/wiki/SOLID">here</a>.</p><blockquote>No matter whether you are writing class, module, microservice or anything, you should always think about SOLIDs.</blockquote><blockquote><strong>If you are writing a new class, as usual apply SOLID principles</strong></blockquote><p>You can google to get more detailed information about SOLIDs in the context of OOPS.</p><blockquote><strong>If you are writing new module, apply SOLID principles</strong>.</blockquote><p>Determine the boundary of the module <strong>(S) </strong>ask the following questions to yourself.<strong> </strong>Can I extend the module to add new capabilities or features<strong>(O)</strong>, how easy it is to replace the module implementation<strong>(L)</strong>, am I making fat module APIs<strong>(I)</strong>, am I exposing internal implementation to outside world, is any API directly depends on implementation than abstract interfaces <strong>(D)</strong>?</p><blockquote><strong>If you are writing any microservice, apply SOLIDs.</strong></blockquote><p>As the microservice name itself says all - it is a fine-grained service. In a typical REST service environment, a single resource could be a criterion for the separation of services.</p><p>Determine the boundary of microservice <strong>(S)</strong>. Can I enhance service APIs without affecting old behavior<strong>(O)</strong> — typically versioning helps, how easy it is to replace the implementation with new technology or using new libraries or tools<strong>(L)</strong>, am I making fat API endpoints which behave differently on client’s consent<strong>(I)</strong>, am I using proper abstraction to expose APIs and to hide internal implementation also<strong>(D)</strong>.</p><h3><strong>Want to design a system? want to learn system design?</strong></h3><p>Few of the software developers still struggle to design a system even after spending several years of working as a software developer.</p><p>We know system design is a wide topic. But if we plan and divide it well, it would help us to learn faster.</p><blockquote>You might have heard “Cop Copimar’s story” about success principle. he says <strong>“use proven success methods.”</strong> If you invest/invent yourself to build your life then it would become very less to achieve/success.</blockquote><blockquote>Similarly, if you want to become good in system design, don’t try to learn everything yourself and invent something new all the time. Whole career span would become very short to learn all languages, algorithms, databases, etc. <strong>Simply try to gain knowledge about every aspect of the system and be expert in one or few of them.</strong></blockquote><blockquote>No design is best design, no design is bad design; There is either better design or good design always.</blockquote><p><strong>Better design can be defined as the system design which is designed by considering the simplicity, reliability, scalability, maintainability, resiliency, fault tolerance.</strong> Whereas good design just works — fails miserably with a slight change in user/consumer interaction. Probably it may have more bugs in it. Moreover, it doesn’t scale enough. Best design means a design with no bugs and no limitations which never exists in reality. Bad design is the design that never worked probably because of not having proper requirements of the system beforehand.</p><p>A better design would have the best suitable tools and technologies chosen as per the requirements. It would have fewer bugs and can easily scale as well as fault tolerance to different user/consumer interactions.</p><blockquote>The goal of software developer should always be to keep the system inclined to better design.</blockquote><p>I hope you liked this article so don’t hesitate to press the claps button below. I have written this from my perspective, please provide your suggestions or corrections in the comments to improvise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cf98f0c5e5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[आयुष्य सुखी होण्यासाठी काय करावे?]]></title>
            <link>https://medium.com/@vkumbhar94/%E0%A4%86%E0%A4%AF%E0%A5%81%E0%A4%B7%E0%A5%8D%E0%A4%AF-%E0%A4%B8%E0%A5%81%E0%A4%96%E0%A5%80-%E0%A4%B9%E0%A5%8B%E0%A4%A3%E0%A5%8D%E0%A4%AF%E0%A4%BE%E0%A4%B8%E0%A4%BE%E0%A4%A0%E0%A5%80-%E0%A4%95%E0%A4%BE%E0%A4%AF-%E0%A4%95%E0%A4%B0%E0%A4%BE%E0%A4%B5%E0%A5%87-8f48ca14a739?source=rss-22b6f36b5ccd------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f48ca14a739</guid>
            <dc:creator><![CDATA[Vaibhav Kumbhar]]></dc:creator>
            <pubDate>Sun, 06 Oct 2019 16:10:00 GMT</pubDate>
            <atom:updated>2019-10-09T05:20:20.809Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>आयुष्य सुखी होण्यासाठी काय करावे?</strong></p><p>खासकरून मराठी माणसांसाठी खूप उपयोगी आहे. अगोदर एक छोटीशी गोष्ट वाचा.</p><p>एके ठिकाणी इमारत उभारणीसाठी <strong>खांब</strong> उभे केलेले असतात. अजून त्यावर <strong>इमारत</strong> बांधली गेलेली नसते. एके दिवशी <strong>सोसाट्याचा वारा</strong> सुटतो, तेव्हा खांबाला समजतं की तो ज्या वीटांवर उभा आहे त्या तर ठिसूळ आहेत. मग त्याला स्वत:च्या अस्तित्वाचाच प्रश्न पडतो की इमारत बांधण्यापूर्वीच आपण नष्ट होऊ. मग तो एका दगडाला <strong>सहारा</strong> द्यायला सांगतो व त्याप्रमाणे दगडाच्या साहाय्याने तो वारा कमी होईपर्यंत <strong>तग</strong> धरतो.</p><p>दगड खांबाला <strong>विश्र्वासाने</strong> आधार देत असतो. खरंतर वारा बंद झाल्यावर खांबाला दगडाची <strong>गरज</strong> वाटत नव्हती पण इमारतीसाठी त्याला मजबूत पायाची गरज आहे हे तो <strong>विसरतो</strong>. जेव्हा त्याला समजतं की इमारत उभारणीचे श्रेय दगडाला जाणार तेव्हा तो दगडाला <strong>हटवण्यासाठी प्रयत्न</strong> करतो. पण तो दगडाच्या <strong>खाचेत</strong> अडकलेला असतो.</p><p>आता खांब खाचेतून निसटून दगडाला <strong>दूर</strong> करण्यासाठी <strong>दुसरे मार्ग </strong>शोधायला सुरुवात करतो. इमारत पडली तरी चालेल पण दगडास पाया होऊ नाही द्यायचं. लवकरच <strong>ठिसूळ वीटांच्या</strong> आधारे उभा राहतो आणि दगडाच्या खाचेतून निघून त्याला <strong>ढकलून</strong> देतो. नंतर इमारत उभारण्यात आली पण थोड्याच दिवसात इमारतीसहीत <strong>खांबाचेही अस्तित्व संपुष्टात </strong>आले. दगड ज्या इमारतीचा भाग व्हायला तयार होता पण खांबाचा <strong>सहयोग/मैत्री</strong> मजबूत नव्हता.</p><p>आता तुमची स्वत:ची आत्मचिंतन करण्याची वेळ. दगडाच्या ठिकाणी स्वत:ला ठेवा आणि बाकीचे ठळक केलेले शब्द आपापल्या परिस्थितीनुसार बदला. परीस्थितीप्रमाणे कथेत थोडासा बदल करा आणि व्यवसाय, नोकरी, नाती, मैत्री, शिक्षण, प्रेम अशा प्रत्येक घटकांशी संबंध जोडू शकता. मग कलियुगाची व्याख्या आपोआपच कळेल. प्रत्येक वेळी तुम्हीच दगडाच्या ठिकाणी नसून खांबाच्या जागी असाल, हे पण विचारात घ्या.</p><p>काही सामान्य शब्द ठळक शब्दाच्या जागी ठेवण्यास:</p><p>मदत, कृतज्ञता, कृतघ्नपणा, व्देष, मत्सर, मजबूरी, प्रतिकूल प्रतिक्रिया, सहनशीलतेची कमी, रागातील निर्णय, विना विश्र्वासातील लोकांना मदत, दुसऱ्याच्या अपयशातून आनंद.</p><p>एवढं सगळं कळाल्यानंतर कलियुगाकडून सत्ययुगाकडे कसं परतायचं यावर विचार करा. <strong>अन्यथा दुसरा वाईट वागतो म्हणून तुम्ही तुमचे संस्कार सोडले की तिथंच कलियुग सुरू होतं.</strong></p><p>All above content is copyrighted by <a href="https://medium.com/u/22b6f36b5ccd">Vaibhav Kumbhar</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f48ca14a739" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[आधुनिक युगामधील पाहुणचाराची एक अनोखी आरोग्यदायी कल्पना]]></title>
            <link>https://medium.com/@vkumbhar94/%E0%A4%86%E0%A4%A7%E0%A5%81%E0%A4%A8%E0%A4%BF%E0%A4%95-%E0%A4%AF%E0%A5%81%E0%A4%97%E0%A4%BE%E0%A4%AE%E0%A4%A7%E0%A5%80%E0%A4%B2-%E0%A4%AA%E0%A4%BE%E0%A4%B9%E0%A5%81%E0%A4%A3%E0%A4%9A%E0%A4%BE%E0%A4%B0%E0%A4%BE%E0%A4%9A%E0%A5%80-%E0%A4%8F%E0%A4%95-%E0%A4%85%E0%A4%A8%E0%A5%8B%E0%A4%96%E0%A5%80-%E0%A4%86%E0%A4%B0%E0%A5%8B%E0%A4%97%E0%A5%8D%E0%A4%AF%E0%A4%A6%E0%A4%BE%E0%A4%AF%E0%A5%80-%E0%A4%95%E0%A4%B2%E0%A5%8D%E0%A4%AA%E0%A4%A8%E0%A4%BE-726e1c8b16c1?source=rss-22b6f36b5ccd------2</link>
            <guid isPermaLink="false">https://medium.com/p/726e1c8b16c1</guid>
            <category><![CDATA[hospitality]]></category>
            <category><![CDATA[hospitality-management]]></category>
            <category><![CDATA[health-recipe]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[health-foods]]></category>
            <dc:creator><![CDATA[Vaibhav Kumbhar]]></dc:creator>
            <pubDate>Fri, 26 Jul 2019 17:41:09 GMT</pubDate>
            <atom:updated>2019-07-26T17:41:09.145Z</atom:updated>
            <content:encoded><![CDATA[<p>पावसाळ्याचे दिवस नुकतेच सुरु झाले आहेत आणि हा काळ म्हणजे व्हायरल इन्फेकशन्सने आजारी पडण्याचा. अशातच माझ्या पावसात भिजण्याने मी ही सर्दी आणि कफला बळी पडलो.</p><p>आज ऑफिसमधून आल्यानंतर मी लिंबू आणि मध कोमट पाण्यातून घेत होतो. सहजच मनामध्ये विचार येऊन गेला कि लिंबू सरबत ऐवजी सर्वांनी हे पेय प्यायला काय हरकत आहे.</p><p>साधारणतः आपण पाहुण्यांच्या पाहुणचारासाठी चहा करतो. चहाने तरतरी येते तसेच झोप किंवा थकवा निघून जातो. परंतु अजून एक विचार केला तर चहामुळे भूकमोड होते. समजा तुम्ही जेवणाअगोदर काही वेळ चहा पिलात तर जेवणाची वेळ मागे-पुढे होते. अवेळी जेवणाचे दुप्ष्परिणाम तर सहज कळतील किंवा google वर सविस्तर भेटतील.</p><p>अगोदरचे लोक गुळाचा तरी चहा करत असत पण आता सर्रास साखरेशिवाय चहा करत नाहीत. पण खरं पाहिलं तर साखरेला आपण सिन्थेटिक शुगर (synthetic sugar ) म्हणतो जी केमिकल सिन्थेसिसने बनवली जाते. साखरेचे काहीसे दुष्परिणाम आहेत, Google वरती सहज सापडतील. शरीराला - मुख्यतः मेंदूला - साखरेची गरज असते. जर का ती आपण नैसर्गिक साखरेमधून पुरवू शकलो तर त्याचे इतर दुष्परिणाम कमी राहतात. जसे कि केळी एक नैसर्गिक साखर जास्त असण्याचं उत्तम उदाहरण आहे.</p><p>ज्या लोकांना सकाळी सकाळी चहाची सवय आहे जर त्यांनी ती बदलून लिंबू आणि मध कोमट पाण्यातून घ्यायला सुरुवात केली तर एक पाऊल आरोग्यदायी जीवनशैली कडेच ना !!!</p><p>जेव्हा कधी कोणी पाहुणे, मित्र घरी आले तर त्यांनाही जर तुम्ही चहाऐवजी लिंबू सरबत, पण ते विना साखरेचे आणि मध मिसळलेले दिले तर कदाचित त्यांना तो एक अनोखा पाहुणचार वाटेल. एखादा स्वतःहून विचारेल पण, “अरे लिंबू सरबत मध्ये कोणती साखर घातलीय”.</p><p>त्यातील एकाने जरी त्याची दररोजची सवय बदलली तरी तुमच्यासाठी ती एक achievement ठरेल.</p><p>आणि हो मला आशा आहे कि तुम्हाला कल्पना आवडली असावी. तुम्हाला कल्पना आवडली असेल तर या ब्लॉगखाली टाळ्या वाजवायला विसरू नका.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=726e1c8b16c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cookblog — How to leverage lambda expressions for design patterns in Java 8]]></title>
            <link>https://medium.com/@vkumbhar94/cookblog-how-to-leverage-lambda-expressions-for-design-patterns-in-java-8-e049c8078158?source=rss-22b6f36b5ccd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e049c8078158</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[java8]]></category>
            <dc:creator><![CDATA[Vaibhav Kumbhar]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 13:00:10 GMT</pubDate>
            <atom:updated>2019-07-24T17:49:22.915Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cookblog — How to leverage lambda expressions for design patterns in Java 8</h3><p>What is design pattern? Design pattern is a solution to a software design for a problem having some characteristics.</p><p>Perhaps, some people try to fit every problem in one of the design pattern. <strong>Do not fit every problem in a design pattern unless needed.</strong></p><p>As we know that lambdas have helped to remove the dependency of creating anonymous classes and the boilerplate code. Lambdas have been served as building blocks for other features like streams, etc.</p><p>Here I am trying to enlist some practices - based on my understanding - to use lambdas for design patterns.</p><h3><strong>Iterator pattern</strong></h3><p>With the <strong>internal</strong> iterators, you can focus more on the business logic than the how to iterate. <strong>forEach </strong>is available on java collections. Several third party libraries also started providing internal iterators viz. Apache Jackson APIs have forEach.</p><p>Things to remember:</p><p>1. Pass a function reference, not method reference. Perhaps we use terms <strong>method</strong> and <strong>function</strong> interchangeably. But immutability is main difference, function does not mutate the data, whereas method can mutate the data.</p><p>2. Do not pass a function which have side effects. For ex: if function is generating some another collection, events, etc.</p><h3>Template method pattern</h3><p>Template method pattern defines an common/generic algorithm for a particular operation whereas it calls few other abstract or default methods - traditionally - whose behavior will be defined by its child classes.</p><p>Things to remember:</p><p>Before going to define abstract or default method and implementing or overriding it in the child class. Try to think the other way around as follows:</p><p>Receive the function reference in the constructor, potentially it will reduce the creation of child classes just to override/implement the method.</p><h3>Strategy pattern</h3><p>Typically we create another interface (to have uniform contract to call strategies) and its child class hierarchy for defining strategies.</p><p>Instead accept strategy as function reference, it will potentially reduce the class hierarchy created for strategies.</p><h3>Decorator pattern</h3><p>Traditionally, you can have a base object and you wrap it using other additives using a common base class.<br>For ex: say, you are buying a gift. You can have several options to decorate it. The cost of gift will be calculated as cost of gift and cost of its all decorated ornaments.</p><p>Using lambda, you can create a combo/container class which will contain the collection of base gift item and all additives.<br>For ex: for the above example, you can calculate cost of combo using the cost of each gift item of collection.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e049c8078158" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>