<?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 RAJNISH DASHORA on Medium]]></title>
        <description><![CDATA[Stories by RAJNISH DASHORA on Medium]]></description>
        <link>https://medium.com/@dashora.rajnish?source=rss-77975345d46d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*vnWMXP0bDTyXUCEa.</url>
            <title>Stories by RAJNISH DASHORA on Medium</title>
            <link>https://medium.com/@dashora.rajnish?source=rss-77975345d46d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:11:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dashora.rajnish/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[The Pursuit of Balance among Product Delivery, Engineering Quality, and Life]]></title>
            <link>https://medium.com/@dashora.rajnish/the-pursuit-of-balance-among-product-delivery-engineering-quality-and-life-7721ca47682e?source=rss-77975345d46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7721ca47682e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[RAJNISH DASHORA]]></dc:creator>
            <pubDate>Sun, 07 Jun 2020 17:35:02 GMT</pubDate>
            <atom:updated>2020-06-07T17:35:02.184Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>“How do we keep up with building a high-quality engineering product and at the same time keep customers engaged and continuously deliver business impact?”</em></strong></p><p><strong><em>“While we build this feature, we want to spend a little time on strategic planning, experimenting to get directional correctness and paying Technical Debt.”</em></strong></p><p><strong><em>“We have been receiving this feedback very frequently that our team and product have very little to offer, often the impact of what we do is unclear and not effectively measured? Moral of the team is going low with such feedbacks.”</em></strong></p><p>These are some of the common thoughts we keep hearing while working on a fast-paced product focused engineering team. In this post, I am trying to post some of my learnings over time to solve such problems.</p><p>Well, there would complex frameworks and exhaustive philosophies breaking above scenarios in less complicated ones and doing justice on a case by case basis. In different situations across products and domains, teams and leaders have grown to resolve these conflicts and strike out a balance towards success, while many have failed as well.</p><p>In my opinion, there’s no silver bullet, and solutions are very subjective but, It all cases making decisions, owning failures, and failing early has played a critical role.</p><p>Let’s try to break down the problem and understand the complexity to see what we can do, Shall we?</p><p><strong><em>Continuous feedbacks are important</em></strong>, there is definitely something not right if stakeholders feel there is no much value add by the offerings we have built. There is a need for identifying impacts delivered on a frequent basis and establishing appropriate communication channels to bridge these gaps. This could also help double click into this kind of feedback and provide healthy iterative loops of improvements on Product Development.</p><p><strong><em>Measurement is the key,</em></strong> measuring the right metrics for impact not just helps in creating visibility but also drives clarity of strategy and course correction.</p><p><strong>Define objectives and focus on outcomes, </strong>most often measuring the outcomes is not possible without defining objectives and hence causing distractions and less satisfactory results further boiling down to low esteem inside and outside the team. Further to complicate the problem, the entire prioritization goes on a toss.</p><p><strong>Objective Communications, </strong>bringing pain points forward is important to build a sustainable ecosystem, feedbacks are one way to establish that, regular checkpoints are another but it does not get resolved there. Communications need to be objective, present the information precisely, make every stakeholder aware of situations and complications so that the next set of actions could be in the right direction. Failing early and communicating the failures also works well for the greater good.</p><p><strong>Prioritization and Bucketing Initiatives,</strong> There are always so many options and initiatives out there that can be tried out, experimented with, leading the product into different directions. Its a function of capacity and objectives how wide one should go, this is where prioritization based on well-defined objective can help.</p><p>OKRs are one of the most valuable tools in driving priorities. While that may or may not be the only source of work a team should pick up. A team should able to bucket the initiatives among strategic, quick wins or tactical moves and health measures so that there is a balance between long term and short term impact it can deliver.</p><ul><li><strong>Strategic Initiatives, </strong>are focused on long term goals. These initiatives drive the vision of the product and are a reflection of the direction the product is heading towards. Most of the time these are the major product features and interfaces we build, these should be well thought through and delivered with high quality. At the least, 50% of the team effort should go on defining, building, and improving these kinds of initiatives, while it is okay to drop quality to 80% creating some amount of <strong>payable</strong> tech debt in favor of showing value faster.</li><li><strong>Quick wins and tactical moves, </strong>these are short term efforts focused to demonstrate immediate impact and calculated tactical moves to keep the strategy going. These are small but effective, low hanging, short-lived initiatives that can help to settle many customer feedbacks and blockers. At times these can help to get the team back on higher moral grounds. The objective of running tactical initiatives is to engage with customers better by solving their immediate needs, keeping all cross-functional groups independently operating, and provide the taste of continuous delivery to the team. It is important to not get drown in the loop created with short term gains and lose focus on strategic initiative hence, in a healthy state, no more than 40% of team effort should be on such initiatives.</li><li><strong>Health measures,</strong> Paying back the tech debt on time is the most significant part of the health measures an engineering team should and need to take care of. For the most part, it is hard to demonstrate value out of health initiatives to all stakeholders but having metrics around reliability, customer experience and product growth treated as a first-class requirement should help the case. Managing health is a continuous effort, <strong>overdoing</strong> it does not help unless it is strategic. To strike out a balance, at the maximum 20% of team effort should be on health measures at a time.</li></ul><p><strong>Taking responsibilities of operations, </strong>most common but least cited problems in a product team is to always underestimate the sense of responsibility of operations causing major failures of a team. For a Product team, while building on strategic initiatives is important, keeping the operations going smoothly for what is available for customers is another key factor to build a trustworthy relationship. Operations are painful and sometimes not interesting but they can drive innovation and are owned by product teams that thrive quality of deliverables.</p><p><strong>All hands on deck on failure</strong></p><p><strong><em>“sure, continuous feedbacks, communications, measurements, prioritization, bucketing, quick wins, balancing capacity everything looks fine but how do you manage the crisis? How do you get this healthy state balance?”</em></strong></p><p>Yeah, this is where the awareness of pain points and acknowledgment of the problems within the team plays a very important role. This is when you need to get everyone to objectively agree to the core problems, building consensus, iterating over the solution together. Having shorter iteration loops within the team over a smaller but most critical piece of the problem and forking out parallelism as you build pace to a significant level seems to do the trick.</p><p>Well! if its a production downtime, you need<em> all hands on deck</em>, if its a failure, you need<em> all hands on deck </em>to own it with an intent to rise again together as a team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7721ca47682e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learnings Outlived!]]></title>
            <link>https://medium.com/@dashora.rajnish/learnings-outlived-1f2d42ce5981?source=rss-77975345d46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f2d42ce5981</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[mckinsey]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[problem-solving-skills]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[RAJNISH DASHORA]]></dc:creator>
            <pubDate>Wed, 20 Nov 2019 10:26:10 GMT</pubDate>
            <atom:updated>2019-11-20T10:26:10.240Z</atom:updated>
            <content:encoded><![CDATA[<p>Working as a Engineer, Analyst, Consultant pick whichever label you can, it was fun time to be at Strategy and Tech consulting for a short span. A lot of people have asked me in the past few years what you learnt at the firm and when people ask I can keep picking random examples from my direct experience or from the surroundings.</p><p>Here are few of such pointers and practices as an engineer from the mail I wrote long back to my mentors at McK before leaving the firm. These may not be catch all but have been good reminders for me to keep looking forward through these years,</p><h4>Never write for just for yourself!</h4><p>Consider that you are not writing any thing for yourself neither code nor literature.<strong> Practice:</strong> Write application logs while developing the application and they should be expressive enough to debug the application.</p><h4>Audience First!</h4><p>One should be able to express or narrate any scenario. The understanding of context and scope should be neat, well defined and clear. <strong>Practice:</strong> Keep track of stories, bugs, features and understand the domain at the level where you can explain it to others.</p><h4>Ask the right questions!</h4><p>Think thrice and ask the right question and get the right answer. Asking the right question saves waste of time, miscommunication, lose in trust and unhealthy debates. <strong>Practice:</strong> Frame your questions in a way to answer all the “So what” responses.</p><h4>One thing at a time!</h4><p>Context switch is important to scale, but you need to optimise and avoid context switching overhead. Context is critical for problem solving, break the problem into logical parts and solve one logical unit at a time. Focus should be on one thing at a time and working towards logical closure and pause before you switch context. <strong>Practice:</strong> make atomic commit and practice <a href="https://en.wikipedia.org/wiki/Pomodoro_Technique">Pomodoro technique</a> to context switch.</p><h4>Be slow but be steady!</h4><p>Story of Hare and Tortoise and philosophy around Consistency v/s Pace are well know. <strong>Practice: </strong>gather knowledge consistently by reading.</p><h4><strong>Time Box to make decision!</strong></h4><p>Always time box things based on priority to make decisions. Dealing with uncertainty is important and could be blissful or joyless. Remember there is no silver bullet. Iterate over failures to reach success.<strong> Practice: </strong>Time box your spikes and analysis to move ahead.</p><h4>Commit to yourself!</h4><p>Keep a singular goal in mind and target to finish it in the time you have assigned or committed for yourself. <strong>Practice: </strong>Have a todos with committed time to complete.</p><h4>Be transparent and set right expectation!</h4><p>Calibrate yourself and set right expectations with your peers and be as transparent and honest about your feelings and views as you can. <strong>Practice: </strong>Say no if you can’t!</p><h4>People first!</h4><p>Care for people more than you do for work. Keep asking for feedback and help others with it over time. Surround yourself with positive energy, people around you play a very important role in this. Understanding motivations is important, make hard decisions if its necessary for greater good. <strong>Practice: </strong>observe and put effort to do feedbacks and learn from each other.</p><h4>Chose your next word wisely!</h4><p>Look around and think twice before you speak or act, as you are the king of the words which you haven’t spoken yet and slave of the words you have said. It is hard to get what you want to achieve out of a conversation, if you don’t speak the right words. You need a lot of patience, courage and trust to get someone right without right words. <strong>Practice: </strong>Write down your thoughts, writing helps in clarity of thoughts.</p><h4>Right people! Right time! Right decisions!</h4><p>Discussions are always healthy, but with the stakeholders to drive conclusions. Always discuss with the correct set of people at the correct time and proceed, this avoids a lot of alignment hassle, rework and saves time. <strong>Practice: </strong>Share and involve all stakeholders in<strong> </strong>problem solving activities for efficient context setting and execution.</p><h4><strong>Balance is yet another optimisation problem!</strong></h4><p>Try to understand the balance between time, responsibilities, priorities, and learnings to churn out best possible of your capacity. As its an optimisation problem there are no hack, learn to profile<strong> </strong>for performance optimisation. <strong>Practice:</strong> audit daily/weekly todo list at the beginning and end of the week.</p><h4>Never point fingers!</h4><p>Never ever point out finger on others, always try to get what can be done better from your side as a individual for people. <strong>Practice:</strong> retrospect yourself before feedbacks to others.</p><h4>Optimise for yourself!</h4><p>Optimising for yourself does not mean you are being selfish and its okay to be a bit for your work and people in favour of supporting your goals.Do all the positive what makes you feel happy and motivate you to reach your goals with dedication. <strong>Practice: </strong>Be honest about things you want to do or your don’t want to do in favour of your goals.</p><h4>Be Aware! Be conscious!</h4><p>Stay calm, healthy and always be aware of your mental and psychological state to control your acts. Always be true and honest with yourself. Never let you emotions reflect on your acts. <strong>Practice:</strong> No decisions or forming of strong opinions when you are angry.</p><h4>Debate healthy and Never avoid conflicts!</h4><p>Try to make logical sense out off each and every step you take and always seek for healthy debates. This will gift you an ability to counter yourself in an argument which makes you right in the corse of time if you chose to. <strong>Practice:</strong> always clarify intentions before getting into debates and conflicts.</p><h4>5 Why’s</h4><p>Ask yourself “why” five times at each step of dilemma. It helps in decision making and moving forward without second thoughts. <strong>Practice: </strong>ask 5 why’s to peers while debating over code.</p><h4>Move towards the goal!</h4><p>Ask yourself to improve execution efficiency and choice of directions, “Does the step I am doing, helps my current task or goal?”. <strong>Practice:</strong> just ask yourself.</p><h4>Float with your thoughts!</h4><p>In your free time, practice to leave your mind free and observe how far it goes. This is one of the most interesting ways of learning new things about yourself. <strong>Practice:</strong> find your meditation.</p><h4><strong>Elevator Pitch!</strong></h4><p>Chose right set of impactful but less words to deliver your message. You snooze it, you loose it. <strong>Practice: </strong>try to deliver your message with 2 minutes rule.</p><h4><strong>Don’t Repeat Yourself!</strong></h4><p>Watch out for your mistakes, Try not to repeat them and enjoy the trials. At the end of the day if you are able to fix even a single one, you are a better person.</p><h4>Focus is the key to gain trust!</h4><p>Focus on the problem solving and principles is important to gain trust with peers and stakeholders and build up and efficient ecosystem.</p><h4>Be a team player and lead!</h4><p>Contribute individually for the team to make it matter and lead by examples.</p><h4>Learn to decide your next step!</h4><p>Your ability to make educated guess with least amount of information is defines your growth. <strong>Practice: </strong>make your decisions and own them, no regrets.</p><h4>Solve problems not people!</h4><p>Identify motivations to change behaviours, and position your team accordingly. It not easy to change the nature but its important to value it.</p><p>There is a small story of A Sage and A Scorpio. In a river once a sage was taking a bath. One scorpio came floating towards him and bit him. The sage left him at the river bank and forgave him. This went on for a while and a person who was observing this trend could not hold himself without asking the sage, “It is troubling you for so long, why don’t you kill him?”. Sage replied with all the politeness and petty on his face,”It is all nature,It can never leave to bite and I can never leave to forgive”.</p><h4>The way you work matters!</h4><p>Take a smaller chunk and do it the right way. its the way, you work what matter.</p><h4>Situation! Complication! Resolution!</h4><p>There is a <a href="https://www.ytamizh.com/thirukural/kural-948/">saying in Tamil for medicines</a> which goes on the similar track as this principle solving any problem or communicating with larger audience. Understand the situation, Assess the underlying complications and propose or arrive to a resolution. <strong>Practice:</strong> Draft mails following this structure.</p><h4>Enjoy!</h4><p>If you are not enjoying, you are not preforming.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f2d42ce5981" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create APIs in Clojure supporting file upload and data transformation using ring and…]]></title>
            <link>https://medium.com/@dashora.rajnish/how-to-create-apis-in-clojure-supporting-file-upload-and-data-transformation-using-ring-and-ad40fc3ca2d0?source=rss-77975345d46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad40fc3ca2d0</guid>
            <category><![CDATA[middleware]]></category>
            <category><![CDATA[ring]]></category>
            <category><![CDATA[file-upload]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[clojure]]></category>
            <dc:creator><![CDATA[RAJNISH DASHORA]]></dc:creator>
            <pubDate>Sat, 14 Sep 2019 16:50:37 GMT</pubDate>
            <atom:updated>2019-09-14T17:15:44.599Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to create APIs in Clojure supporting file upload and data transformation using ring and data.csv</h3><p>Few months back, I was working on writing an HTTP endpoint in Clojure. I had a use case to pass a file with comma separated values over http and parse the data for further processing. It does make sense to draft notes at one place.</p><p>In Clojure, ring is one of the most common library while working with HTTP. <strong>What’s ring? </strong><a href="https://github.com/ring-clojure/ring">Ring</a>, yet another library to help build web applications with modular components abstracting out HTTP implementation details into simpler APIs.</p><p><a href="https://github.com/ring-clojure/ring/wiki/Concepts">Concepts</a> in ring are pretty straight forward, you have a request, a response, a handler for the request and a middleware to enrich the handler. <strong>Sure, then how to use ring for file upload?</strong></p><p><a href="https://github.com/ring-clojure/ring/wiki/File-Uploads">File upload</a> over HTTP requires multipart form handling, The wrap-multipart-params middleware is provided by ring for this purpose. We can use this middleware and wrap the api handler with wrap-multipart-param middleware. i.e.</p><pre>(wrap-multipart-params handler)<br>(wrap-multipart-params handler options)</pre><p>Optional parameter, options should be a map as follows,</p><pre>{<br>:store temp-file-store  ;; a function for storing uploaded files<br>:encoding char-encoding ;; character encoding of parameters <br>}</pre><p>By default, <a href="https://github.com/ring-clojure/ring/blob/1.6.3/ring-core/src/ring/middleware/multipart_params/temp_file.clj">store function</a> is used to manage the temporary files created after upload and delete every hour. Lets take an example,</p><p>We have a file, sample.csv</p><pre>id,name<br>1,foo<br>2,bar</pre><p>This is how we can make a http request using curl to upload this file,</p><pre>curl -XPOST  &quot;http://localhost:8010&quot; -F file=@sample.csv</pre><p>The wrap-multipart-param middleware will enrich the request by updating the value offile key in the :params map of the request. The file key now contains:tempfile, :content-type, :tempfile, :size and the request looks like,</p><pre>{...<br> :params<br>  {&quot;file&quot; {:filename     &quot;sample.csv&quot;<br>           :content-type &quot;text/csv&quot;<br>           :tempfile     #object[java.io.File ...]<br>           :size         51}}<br>...}</pre><p>:tempfile key contains java.io.Fileobject which is the uploaded data of the file and this can be used to perform further operations.</p><p>We can print the file content after reading as follows,</p><pre>(prn (slurp &lt;java.io.File Object&gt;))</pre><p>Now that we have the uploaded file’s data as a java.io.File object,<strong> How can we use </strong><a href="https://github.com/clojure/data.csv"><strong>data.csv</strong></a><strong> for creating clojure maps to use comma separated dataset?</strong></p><p>We can now read the file content which is stored in :tempfile key as a java.io.File object as a java.io.BufferedReader object making use of <a href="https://clojuredocs.org/clojure.java.io">clojure.java.io</a> reader function.</p><pre>(io/reader (:tempfile (get request-param &quot;file&quot;))</pre><p>Using <a href="https://github.com/clojure/data.csv">data.csv</a> read-csv function we can further read the csv data,</p><pre>(csv/read-csv reader)</pre><p>This will give us csv-data as,</p><pre>[[&quot;id&quot;, &quot;name&quot;], [&quot;1&quot;, &quot;foo&quot;], [&quot;2&quot;, &quot;bar&quot;]] ;; csv-data</pre><p>Now to create map out of this, we can the following function,</p><pre>(defn csv-data-&gt;maps [csv-data]<br>  (map zipmap<br>       (-&gt;&gt; (first csv-data)<br>            (map keyword)<br>            repeat)<br>       (rest csv-data)))</pre><pre>(csv-data-&gt;maps csv-data) ;; csv-data to map</pre><p>This outputs to,</p><pre>[{:id 1 :name &quot;foo&quot;}, {:id 2 :name &quot;bar&quot;}] ;; csv-data-map</pre><p>Further we can use this data to perform transformation and process the HTTP API response. Using ring middleware and data.csv library it is super easy to write APIs to handle csv file uploads and perform operations.</p><h4>References:</h4><p>clojure.java.io : <a href="https://clojuredocs.org/clojure.java.io/file">https://clojuredocs.org/clojure.java.io</a></p><p>Ring concepts : <a href="https://github.com/ring-clojure/ring/wiki/Concepts">https://github.com/ring-clojure/ring/wiki/Concepts</a></p><p>clojure.data.csv : <a href="http://clojure.github.io/data.csv/">http://clojure.github.io/data.csv/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad40fc3ca2d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>