<?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 Sabareesh Iyer on Medium]]></title>
        <description><![CDATA[Stories by Sabareesh Iyer on Medium]]></description>
        <link>https://medium.com/@sabareeshmb?source=rss-2aaf0d007dd3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UoYkSQytK8Sdt1k3InLfMA.jpeg</url>
            <title>Stories by Sabareesh Iyer on Medium</title>
            <link>https://medium.com/@sabareeshmb?source=rss-2aaf0d007dd3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:49:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sabareeshmb/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[[Book Review] Death with Interruptions by José Saramago]]></title>
            <link>https://medium.com/@sabareeshmb/book-review-death-with-interruptions-by-jos%C3%A9-saramago-d7a18b3546c4?source=rss-2aaf0d007dd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7a18b3546c4</guid>
            <category><![CDATA[portuguese-literature]]></category>
            <category><![CDATA[literature]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[jose-saramago]]></category>
            <dc:creator><![CDATA[Sabareesh Iyer]]></dc:creator>
            <pubDate>Sun, 08 Mar 2026 03:57:19 GMT</pubDate>
            <atom:updated>2026-03-08T03:57:40.248Z</atom:updated>
            <content:encoded><![CDATA[<p>This year, I have decided to venture more intentionally towards literature and across languages. I do not recall where I found Saramago–and I really wish I did–but I couldn’t help but be drawn to the absurd nature of his work. Saramago probes at the very foundation of knowledge and logic, how a lot of what we see around is only inductively true — subtly harkening back to Bertrand Russell-ian philosophy. There is no way for us to truly know if the sun will rise tomorrow — it has always done so, so we assume that it reliably will. But the laws of the universe are mere derivations, observations — there is no reason to believe that they are absolute edicts that will never be violated. Physics doesn’t have to be the way it is; and there is nothing we know that challenges this. So, Saramago plays with that one constant that has been common to every single living creature to have ever existed–they have all died or will die in a finite time. Saramago suspends that most underlying of commonalities between all life, save for that they are or have been alive, and rolls into the ramifications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vJzfRHk3DgRCTB1_rnnfQ.jpeg" /></figure><p>And it’s not just ideas that Saramago plays with, but, in addition to his lovely prose, he experiments with sentence structure and pushes the bounds of punctuation, thereby challenging preexisting norms of language. You little rebel, you!</p><p>The first half of the book was fun to read, albeit a bit meandering in direction or purpose aside from exploring a hypothetical. But the sudden turn of plot in the middle is rather anticlimactic–perhaps intentionally so, or perhaps Saramago ran out of ideas to follow the arc. But with almost Vonnegut-esque prose, prose that treats the morbid and melancholy with a lightness that draws on the absurdity of reality, Saramago manages to maintain a veneer of allure that sustains the reader through this drop-off in density to act 3 where we encounter a character that defies death (the how of it we never find out). This part is the weakest of the book. The sequence of actions that followed felt rather empty, and the ending a little contrived, as if, as I previously remarked, the author ran out of ideas. What ensued was some dodgy character evolution that wasn’t explained and doesn’t quite make sense. &lt;spoiler&gt; Why would death fall for this man who defies death? He becomes something of an obsession for her, an anomaly, and with no obvious motivation, she ends up falling in love with him. &lt;/spoiler&gt; Once again, his prose rescued the plot and made it look substantial, but it’s just an empty coat of armor. And to be honest, the ending which is a pointer towards a circular tale, is so hackneyed and obvious that it feels like a cop out. “I can’t find anything significant to say so I’m going to drop a bomb that makes me sound intentional and impactful.”</p><p>Considering the quality of the prose and the pure fun-ness of the writing, I would have gone for 4 stars if the plot had a bit more direction. As it was, it was a little unrewarding: so 3.5 stars.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7a18b3546c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Book Review] The Trial by Franz Kafka]]></title>
            <link>https://medium.com/@sabareeshmb/book-review-the-trial-by-franz-kafka-785e26eec235?source=rss-2aaf0d007dd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/785e26eec235</guid>
            <category><![CDATA[franz-kafka]]></category>
            <category><![CDATA[the-trial]]></category>
            <category><![CDATA[classics]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[kafka]]></category>
            <dc:creator><![CDATA[Sabareesh Iyer]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 00:20:00 GMT</pubDate>
            <atom:updated>2026-01-31T00:20:00.327Z</atom:updated>
            <content:encoded><![CDATA[<p>It is one of the peculiarities of reading Kafka that his writing is not divorceable from the man himself. Indeed most great art created by artists with mental health issues loses much of its significance if it is cleaved asunder from the artist — take Caravaggio, for instance — although that is not to say that it is lessened in stature without that history. Rather, though the art stands impressive on its own, a certain insight into the mind and situation of its creator enlightens us to the sheer depth it contains. But with a lot of art, either one does not need to probe into its background and provenance but one is instead granted that enlightenment should they chance upon the background, or the art is so obviously self-referential and direct that an inquiry into the conditions and the life of the creator is inescapable (such as with the poems of Langston Hughes, or the blues, or heavy metal music). But that is not quite the case with Kafka’s writings. In <em>The Trial</em>, there is no obvious self-reference that is apparent to the dilettante reader uninitiated in the details of Kafka’s life, and yet a certain amount of Kafka’s emotional state of darkness filters through to the writing such that the reader is led, not voluntarily by the author, to be curious about the author’s life and what circumstances brought about such an examination and exposition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R10mWl4LhXzlmpwL.jpg" /><figcaption>David with the Head of Goliath, by <em>Caravaggio, where he painted his own face as Goliath</em></figcaption></figure><p>Vonnegut, talking about the theory of writing, says of Kafka that, whereas most books start with the protagonist in a positive state going on to experience crisis and difficulty or with a protagonist in suffering finding a way to climb out of it, Kafka’s writing starts with a protagonist in misery who is only plunged ever deeper into despair. <br>No art is separate from the artist. For, by necessity, there is an element of truth and nakedness embedded in art which is what makes it appealing to those who consume it. Without that, art should be sterile, devoid of meaning, and hence not worth one’s efforts of understanding any more than a scribble on the walls of a public toilet. So it is that the misery that fills Kafka’s writings leads one to question his mental state.</p><p>In the epilogue written by Kafka’s “close friend” Max Brod, Max talks about the battles with self-doubt and nihilism that Kafka fought, going so far as to ask Max to burn all his writings after his death. And in the Introduction, parallels are drawn (by virtue of Kafka’s personal letters) between the real-life saga of his his engagement to Felice Bauer — including her friend’s intrusion telling Fraulein Bauer to break it off, and an eventual tribunal that was convened to execute that suggestion — and the allegorical arrest, confusion, trial and execution that Joseph K. endures. In fact, Kafka even writes in his letters referring to the engagement: “was tied hand and foot like a criminal.” His musings on the surroundings at this “tribunal” centering on waiters, bed bugs, comments on the afternoon sun, etc. betray a nervousness that he was likely trying to mask or distract himself from by concentrating on irrelevant details. Much like Joseph K. does.</p><p>As the Introduction (in my Vintage Classics 2019 edition) says, there are a lot of lenses through which The Trial can be analyzed, but perhaps the most accurate intention of the author was as a mirror to this relationship with Felice Bauer. However, that does not make the other lenses any less valid and useful. For instance, I cannot help but notice a glaring similarity between the opaque nature of the courts in the book and a similar opaqueness, or at least a high degree of convolution, that exists in the immigration system of today’s United States.</p><p>The Trial has already proven to be and will continue to persist as a significant work of literature due to the fact that the ubiquitous ever-lasting nature of bureaucratic system is an inalienable part of the modern urban life. Most common people have been victim to the system in some way or another. The trouble with the system is it is all-powerful but it also does not exist — for it is comprised of people, and individuals can be prevailed upon to change their opinions and modify their actions accordingly. Be it with life events like buying a house, or interactions with the law where the corpus is so large that even most lawyers cannot have a full grasp of it, or, as I said above, immigration which gets more common every day, the pestilence of bureaucratic institutions is interminable. Even in the 21st century with unprecedented levels of access to information and reach of news, the sheer quantity of injustice renders most of us incapable of taking any meaningful action to end it. Jeez, as I write this, I realize it is no wonder that Kafka was depressed.</p><p>Let me shift gears and go into the actual details of the book.<br>First, I should note that although the story of the book does come to a conclusion, the book is not quite complete. As the epilogue says, there is a lot that is missing between the penultimate chapter and the end. However, the absence of this does not necessarily detract from the book. Its presence would only have served to drive further home the point of struggle to infinity against darkness. <br>Second, although Kafka was nihilistic and doubtful of his own abilities, he had to have had a certain belief in his intellect for him to have written these at all. And perhaps this is what he is mocking self-deprecatingly with the various number of instances where Joseph K. goes about life utterly convinced of his own superiority. He has a certainty in the thoroughness of his thinking, which is admittedly cognizant of various possibilities and points of view, yet is demonstrated to be severely limited by the prison chaplain in the Cathedral. In fact, Joseph K. has such a high opinion of himself that he calls most of the people he runs into some variation or the other of “stupid.” He is full of uncharitable thoughts and remarks for everybody he meets, and he holds himself high not just in his own opinion but also in theirs. There is a high degree of misanthropy displayed by Joseph that, if he is indeed autobiographical, explains Kafka’s melancholia. Joseph K. also shares Kafka’s tendency to fixate on irrelevant details to distract himself from difficult situations.</p><p>K.’s relationship with Leni who has webbed hands — which are traditionally thought of as undesirable — is indicative of low self-esteem that he masks with his intellectual accomplishments in his career. The remarks by the girls at the painter’s apartment calling him ugly reinforce the notion of his looks. Only two people in the book find him attractive: one is Leni who is also attracted to Block, who is perhaps the character that Joseph has the most disdain and disrespect for, going so far as to treat him as less than human in the Advocate’s office. The other is Frau Burstner’s handicapped roommate who can’t take her eyes off his lips. His only other sexual relationship in the book is with Elsa who is a prostitute. The profile of a well-to-do official in the bank at 30 with no stable relationship history speaks volumes. After he was first arrested, he develops an obsession with Fraulein Burstner and even goes so far as to kiss her uninvited. Kafka writes, “…kissed her first on the lips, then all over the face, like some thirsty animal lapping greedily at a spring of long-sought fresh water.” Fraulein Burstner’s response to this was to try her best to never run into him again and even invite another boarder to share her room for protection.</p><p>At the end of the book, &lt;spoiler ahead&gt; Joseph sees Fraulein Burstner when he is being taken to his execution. He follows her but also acknowledges that it might not even be her, but that makes no difference. Kafka evokes a symbolic sense of loss, the one that got away, and shows Joseph pining over her even as he is being taken to his death.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6yP7GmQRR-5gSdnEIBu3ig.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=785e26eec235" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cracking the CodeSignal interview]]></title>
            <link>https://medium.com/@sabareeshmb/cracking-the-codesignal-interview-1f74262630?source=rss-2aaf0d007dd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f74262630</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[interview-preparation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[interview-tips]]></category>
            <category><![CDATA[software-interview]]></category>
            <dc:creator><![CDATA[Sabareesh Iyer]]></dc:creator>
            <pubDate>Thu, 17 Aug 2023 22:53:54 GMT</pubDate>
            <atom:updated>2023-08-17T22:53:54.034Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A guide to beating the Industry Standard Coding Framework evaluation for Software Engineers</em></p><p>Much has been said about the inefficacy and inaccuracy of the hiring process for software engineers. It is not just the interviewees who bemoan having to slug through hundreds of obtuse coding problems on LeetCode to have a shot at landing a top job — the companies doing the hiring are equally displeased with a process that lets false positives abound and creates mis-hires aplenty. Companies, like Amazon, which are notorious for their hire-to-fire culture can hardly be held fully culpable when the industry standard process, for the lack of more appropriately cathartic words, sucks donkey balls.</p><p>Into this yawning chasm of interviewing incompetence steps CodeSignal’s <em>Industry-Standard Coding Framework</em> evaluations. These evaluations are quickly becoming the pre-screen of choice for ambitious tech-forward companies big and small alike. They combine the scalability of LeetCode-style algorithmic challenges with the utility and relevance of testing on skills one is actually likely to use on the job. Fat lot of good a thorough knowledge of dynamic programming will do if an engineer is unable to produce modular, bug-free, extensible software. And it is for this reason that the CodeSignal assessments are here to stay.</p><p>In this article, we will go over some techniques, thought patterns and tips a budding software engineer can use to get through these assessments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AoByLHNK7zhF2Jp-" /><figcaption>Photo by <a href="https://unsplash.com/@clark_fransa?utm_source=medium&amp;utm_medium=referral">Arnold Francisca</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>1. Understand the assessment</h3><p>Your assessment will ask you to build a fairly simple system to perform some business logic on representations of real-life entities. For example, you might be asked to build a mock banking system or an employee management system. The question is usually structured in 4 levels with each successive level unlocking only upon the successful completion of the previous level.</p><p>The prompts are deceptively simple. For someone coming from the background of taxing LeetCode interviewing which depend on determining the exact right algorithm, optimization or insight to apply to the question, these prompts might even look trivial. But as one of my favorite YouTubers says, <em>this is just an illusion</em>: the devil is in the details. The assessment is fairly demanding in terms of technical complexity, so solving the whole thing is no cake walk. The key to solving multiple levels of the assessment is extensibility.</p><blockquote>The key to solving multiple levels of the assessment is extensibility.</blockquote><p>Below we’ll look at how to approach the problem in such a way that these concerns can be adequately addressed.</p><h3>2. Be classy</h3><p>Although a certain sense of style can never hurt your chances, I’m referring here to the core premise of all long-term maintainable, extensible code: a generous usage of classes. Object-oriented programming is critical to maintaining state, depicting real-life entities and code-extensibility. Embrace it.</p><p>As a general rule, you should represent each real-life entity with an object — $10 is not an object, but a payment of $10 is; Carl Sagan is not an object, but an astronomer named Carl Sagan is; employment is not an object, but an employee is. During the assessment, you should take time to think about which entities (and hence, objects) you’ll be working with and which operations go on which objects. A good rule of thumb is to put each operation on the class of the actor who performs the actions that the operation denotes. An obvious example might be: if an employee enters the office, that is an action s/he is taking — so enter_office() should be on the Employee class. By contrast, if an employee gets paid, even though it might sound like something he did, the <em>actor</em> is the manager, so we should be partial to a pay_employee() method on the manager over a get_paid() on the employee.</p><h3>3. Be mindful of state — modularization is your friend</h3><p>This is never explicitly specified at any point by the platform, but the major thing that CodeSignal assessments actually test you on is your ability to maintain state. If you try to get by Level 1 with a bare-bones architecture, you will quickly find yourself in a state of befuddlement as you try to juggle all the objects you work with in one central entity that maintains state. The assessment challenges you to find a way to extend your classes in such a way that the objects can maintain their state in the right way without compromising data integrity. For example, you might have a function on your BankAccount class to record when money goes out of the account. In that function, you deduct the withdrawn amount from the balance and maintain a total of all withdrawals and you’re feeling pretty good about yourself. However, the next Level might throw a curveball asking you to maintain a list of all outgoing payments and you find yourself scrambling to cram more logic into the function which is growing out of control faster than you expected. Here, modularization can be your friend. Put any discrete action you can think of in a separate function.</p><blockquote>Put any discrete action you can think of in a separate function.</blockquote><p>At the time of writing, this can be a little annoying since CodeSignal gives you just one file to work with and makes you scroll up and down, but hopefully this will get a little less cumbersome.</p><h4>Why is this important?</h4><p>In a production environment when you’re working at a company, everything you touch is to perform a business action. What do actions do? They move entities from one state to another. Any company, from the smallest to the largest, tech or otherwise, is basically a state machine. This applies to your local mom-and-pop store just as much as it does to Google or Amazon. It is critical to maintain the state of the objects that we touch. To illustrate the impact of this, can you imagine the consequences if we put out some code into production for an e-commerce website which refunds customers for returns but does not maintain that state in the database? We would never know if the customer was refunded based on the object state.</p><p>You might rightly ask at this point, seeking a less abstract answer, what exactly do we mean by state? When an employee gets paid, we want to store that information somewhere. When a bank account gets money deposited into it or withdrawn from it, we want to store that information somewhere. Whenever something happens in our system that affects its entities, we need to have a way to store it. This can be as simple as an attribute on the Employee class to store TotalWagesReceived, for instance, but always store state.</p><h3>4. Slow is smooth, Smooth is fast</h3><p>When I take a CodeSignal assessment, I try to plan my time beforehand so that I don’t fall behind unawares. Since there are 4 levels and each level gets successively harder, I try to plan it as 10 minutes for Level 1, 20 minutes for Level 2, and 30 minutes each for Levels 3 and 4. Without exception, my estimation has been way off the mark every single time. And when you find yourself having taken 20 minutes for level 1, it is natural to find yourself trying to rush it for the next level. Don’t. The challenge is not to write as many lines of code as possible. The challenge is to get as much of the functionality as you can working.</p><blockquote>You’d be much better served slowing down to deliberate on design considerations rather than ploughing head-first into the problem trying to outrun the clock with your fingers.</blockquote><p>No matter how far behind you find yourself, take a minute in between levels to think about your approach. Make a quick plan in your head of how you’re going to implement <em>everything</em> that level asks you to do before proceeding, lest you might find yourself on the second half of the level wishing you had spent a few more seconds designing the first half better. Knowing the requirements and addressing them properly beforehand allows you to produce the best possible code.</p><h3>5. Fret not</h3><p>Unlike LeetCode challenges, your success in a CodeSignal assessment is not predicated on your ability to knock the whole problem out of the park. Do your best to solve each stage of the problem with the best code you can produce. I have gotten past the pre-screen sometimes without even finishing Level 3. Also, don’t concern yourself with time or space complexity. For example, if you have some functionality you’re working on where the easiest solution is to sort a list, do it. From my experience, you are not penalized for sub-optimal performance of your code. I don’t mean to imply you should brute-force using exponential algorithms, but usually, you do not have to worry about optimizing something from O(n logn) to O(n) if that requires you writing your own algorithm to solve the problem instead of in-built sort. The evaluation is not algorithmic — keep that in mind. All that matters is the test cases.</p><p>If you have any additional tips or questions, leave it in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f74262630" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>