<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[baepaul's weekly notes]]></title><description><![CDATA[writings - of sorts.]]></description><link>https://www.baepaul.com</link><image><url>https://www.baepaul.com/img/substack.png</url><title>baepaul&apos;s weekly notes</title><link>https://www.baepaul.com</link></image><generator>Substack</generator><lastBuildDate>Fri, 17 Apr 2026 05:27:56 GMT</lastBuildDate><atom:link href="https://www.baepaul.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Paul Bae]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[baepaul@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[baepaul@substack.com]]></itunes:email><itunes:name><![CDATA[Paul Bae]]></itunes:name></itunes:owner><itunes:author><![CDATA[Paul Bae]]></itunes:author><googleplay:owner><![CDATA[baepaul@substack.com]]></googleplay:owner><googleplay:email><![CDATA[baepaul@substack.com]]></googleplay:email><googleplay:author><![CDATA[Paul Bae]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[On ownership]]></title><description><![CDATA[It&#8217;s been a bit.]]></description><link>https://www.baepaul.com/p/on-ownership</link><guid isPermaLink="false">https://www.baepaul.com/p/on-ownership</guid><dc:creator><![CDATA[Paul Bae]]></dc:creator><pubDate>Sun, 16 Feb 2025 20:54:15 GMT</pubDate><content:encoded><![CDATA[<p>It&#8217;s been a bit.</p><p>As expected, a weekly cadence has proven to be ambitious. It&#8217;s hard to say exactly what I was up to. If you ask me, I&#8217;d respond &#8220;I was busy&#8221;, but if you continued &#8220;with what&#8221;, I&#8217;d have a hard time answering. And whether that be a deficit in my short-term memory or a symptom of the modern workplace, the affliction remains.</p><p>There&#8217;s a number of thoughts rampaging about. Noisy neighbors, I call them. I&#8217;m acquainted. I accept them at times, ignore them on others, and use them on occasion.</p><p>I&#8217;d like to write them all. But for some, I can&#8217;t.<br>Time is a lens; recent events are inevitably blurred. Those older are not necessarily clear, but do develop the resilience to weather repeated dissection and analysis. At the end of that process, the thought disappears. The neighbor ceases his noise. He settles.</p><p>Today is less an effort to expound on my now. It&#8217;s to talk about an idea I&#8217;ve thought about far too much for far too long. Ownership.</p><p><br></p><p><em>&#8220;I&#8217;m an obsessive owner.&#8221; - </em>so I wrote in my annual review. <br>Five years ago, I wrote the same words in my review then.</p><p>As a word, ownership means the &#8220;state of being an owner.&#8221; At Amazon, it&#8217;s one of our leadership principles:</p><blockquote><p>Leaders are owners. They think long term and don&#8217;t sacrifice long-term value for short-term results. They act on behalf of the entire company, beyond just their own team. They never say &#8220;that&#8217;s not my job.&#8221;</p></blockquote><p>It&#8217;s not hard to think of why a company would want to promote it. It empowers your employees, indebts loyalty and makes them work harder. At first blush, it seems as if there&#8217;s very little downside to having all of your employees be owners (or at least think they are).</p><p>But viewed from the lens of management theory, it&#8217;s paradoxical. Ownership gives power to the employees. At first, in theory only, as though employees may act like owners, they aren&#8217;t truly. But eventually, in practice as well. The strongest owners will realize what they own and what they don&#8217;t, seeding discontent as to their scope.</p><p>The alternative to ownership is to delineate. Leadership owns the product, the business, and the bottom-line. Workers deliver on the tasks assigned; they&#8217;re evaluated based off their performance and expected to do nothing outside of guidelines.</p><p>And thought that might seem barbarically industrialist, it&#8217;s not a bad system either. Leaders own repercussions; if the performance of your firm goes down and your clients are mad, that is your burden to bear. If your restaurant fails to flip a profit, you still have to pay your employees their wage. If your startup fails, you lose everything, your employees still get their salaries. You own both the upside and the downside.</p><p>Employees are given stability in exchange for autonomy. The scope of their work is rigid and less readily influenceable, but their work and their wage is guaranteed. I don&#8217;t have to care about my company and its idiot management, all I have to do is some data analysis and be netted my salary. If no customers come during rush hour, that&#8217;s a boon not a curse. I don&#8217;t have to exceed expectation, all I have to do is meet it.</p><p>So in a sense, a top-down environment encourages work-life balance. Work is work, life is life; separate the two and act to minimize the former. That might seem ironic, especially in lieu of draconic workplaces where expectations are high and supervisors are stringent, but it holds some truth. It&#8217;s surprisingly nice to be told what to do.</p><p>Bottom-up environments are different. It&#8217;s tempting to only think about the benefits. Imagine the freedom, imagine the autonomy of only doing what I want to do! And while that is the primary reward reaped, the repercussions are necessarily cruel. </p><p>If you let your employees do whatever they want, you pick winners and losers. The former is rewarded, they&#8217;re given more scope, more resources, and fast-tracked promotions. The latter is penalized; if you don&#8217;t contribute value, you&#8217;re cut. It hinges heavily on talent and competition. Weakness in a peer is not to be remedied, it&#8217;s an opportunity.</p><p>Ironically, these systems are also inherently exclusionary. Although there&#8217;s nothing explicit, bottom-up environments tend to self-select the people it prefers by its criterion. There&#8217;s a certain breed of individual that tends to succeed. This isn&#8217;t to say that top-down environments are inclusionary, they most certainly aren&#8217;t as they expect you to conform to the culture they set, but they are more explicit about it.</p><p></p><p><br>This essay has taken a surprising analytical bent.</p><p>All that said, it doesn&#8217;t really matter. Regardless of what&#8217;s optimal, I do what suits me. I act on principle over probability. And though you may be able to convince me that a certain strategy is optimal, I will usually ignore it and simply do what I think is right.</p><p>That&#8217;s ownership. That&#8217;s caring about your work: owning it and living by it. </p><p></p><p><br>Where that comes from is a good question. </p><p>One aspect is personality. I was raised in a family where academic excellence was king. I was told to do a lot: near every waking hour of my youth was micro-managed by my parents. Wake up at 6, leave the house by 6:30, study till 12, eat till 12:30, study till 6, eat dinner till 6:30, study till 10, go to bed and repeat.</p><p>That lack of control made me obsess for the opposite. I wanted freedom - and would do anything to achieve it, including a few flawed attempts at running away from home. So bluntly put, I don&#8217;t take well to being told what to do. I condone it from those I respect, but even then, I will disagree on directives I think unjust.</p><p>The need for independence is what defined my childhood. I craved it - financial independence, emotional independence, professional independence; and worked rabidly to achieve it. Now that I have it, my obsession with it certainly has petered, but it still stands as a hallmark character trait.</p><p>There&#8217;s other aspects of personality that tie into it. Perfectionism is one, the insistence on doing things well and wanting to do things my way. Empathy and sensitivity is another, the need to feel involved with not just your own work but that of those around you. Sheer egoism is another, the desire to own things out of pride alone.</p><p>But ownership can also be taught. If you treat your employees as workers, that&#8217;s all they&#8217;ll ever be. If you treat them as owners, they&#8217;ll grow into leaders.</p><p>My principal engineer was the one who taught me that. There&#8217;s a phenomenon in the tech industry where companies spend copious amounts of money and time recruiting the smartest college graduates, then proceed to baby them by giving them trivial tasks and treating them as children.</p><p>He did the opposite. From the get go, he treated me like he treated himself. He gave me projects that he knew I&#8217;d fail on and held me to his bar, not any other. He treated me like an owner - and nothing else made me work harder.</p><p>This approach doesn&#8217;t work for everyone. There&#8217;s downsides to it. For one, you are intentionally encouraging failure. I don&#8217;t mean that purely from the perspective of giving engineers projects with big scope that they may or may not deliver on (and then secretly have ways to guarantee success). I really mean it.</p><p>Ownership makes people fail. It makes them personally responsible for failure and incents them to grow. And that is a cruel, albeit fair, thing.</p><p></p><p><br>To end on, there&#8217;s an admitted irony here. Ownership is the &#8220;state of being an owner&#8221;, it doesn&#8217;t mean you are. I act as an owner, but I&#8217;m not really. I acknowledge that, yet still choose to bear that farce. The reason why is because I would rather be, or attempt to be, than be complicit to hierarchy.</p><p>Freedom isn&#8217;t free. You have to fight for it. Be it now or in the future, in petty corporate politics or in matters of consequence, there are times where you have to stand up and fight. It feels pointless at times. More than anyone, I doubt why I do the things I do for a company or a country I disagree with.</p><p>But still, I do. <br>And whether it be naivet&#233; or absurdity, I refuse to change.</p>]]></content:encoded></item><item><title><![CDATA[A punk]]></title><description><![CDATA[&#8220;Complacency leads to mediocrity.&#8221;]]></description><link>https://www.baepaul.com/p/a-punk</link><guid isPermaLink="false">https://www.baepaul.com/p/a-punk</guid><dc:creator><![CDATA[Paul Bae]]></dc:creator><pubDate>Sun, 19 Jan 2025 12:39:47 GMT</pubDate><content:encoded><![CDATA[<p>&#8220;Complacency leads to mediocrity.&#8221;<br>A cruel sequence of four words.</p><p>My older brother said it to my younger, in lieu of some argument the family was having about the latter&#8217;s grades. He wasn&#8217;t struggling in school; on the contrary, he had a 4.0, was taking advanced classes two years above his age, and already had a near-perfect SAT and ACT score as a sophomore in high school.</p><p>But that wasn&#8217;t enough for our family. Getting As at some &#8220;public school&#8221; was a given. They wanted more. Math camps, AP exams, honors courses, Olympiads. Any thing that you could study for and test for - you did. It wasn&#8217;t a matter of learning, it was a matter of status. Success was determined by your scores, and as a child, your self-worth was too.</p><p>That crescendo culminates in the final test of youth: college admissions. The only ivies worth their salt are Harvard, Yale, and Princeton. The other good ones are MIT, Carnegie, and Stanford. The rest are fake: no-names that only serve as a reminder of your inadequacy years down the road. And God forbid if you went to a state school.</p><p>Well, I failed.</p><p>I went to the University of Texas at Austin. I submitted 20 college applications and was only accepted there. I did not get into the honors program. I did not get a scholarship. I did not get a 4.0. I did not get any internships.</p><p>I was expelled from Carnegie Mellon for truancy. I was accepted into their Master&#8217;s program for Computer Science, chose to study computational complexity out of pride, quickly realized I was out of my depths, and fell into a depressive hole. I lied to my advisor, my professors, my parents and spent my days skating around Pittsburgh smoking cigarettes and making regrettable life decisions.</p><p>I was a punk. And still am.</p><p>For all my quirks of personality, the one that&#8217;s strongest is the need to oppose authority. If I&#8217;m told to do something, even if it&#8217;s something rationally sound, my first instinct is to disagree. Not because I have any good reason to (though I&#8217;d hope I at least have some), but on ethic alone.</p><p>So school didn&#8217;t suit me. Neither did my parents. They applied the same principles that they had with pedagogy to the practice of. They read &#8220;Tiger Mom&#8221; and thought to do better. It was barbaric - I won&#8217;t lie. Yelling, shouting, even physical abuse was mundane in our household. Perhaps that would&#8217;ve all ended sooner if I had simply complied, but all that did was elicit a stronger response in return.</p><p>I&#8217;m fortunate to have grown and healed in ways I didn&#8217;t think possible. My parents and my brothers did too, despite their old habits re-surfacing now. Truly, at times, the normal relationship we have now seems miraculous. Yet, the past still stands and to the extent that I can, I won&#8217;t misrepresent it. And in some odd way, I&#8217;m grateful for it.</p><div><hr></div><p><br>More and more, does writing this blog seem ill-advised for my career. I&#8217;ve grown aware of my (very small) readership and imagined a few scenarios in my head. But screw it, I suppose that means I&#8217;m writing something worthwhile.</p><p>The bar is the topic on my mind.</p><p>It&#8217;s a very Amazonian concept, one that I haven&#8217;t explicitly thought about in a while, but learned to live with. The bar is the standard to which you hold yourself and others. When we hire individuals, we evaluate whether they &#8220;raise the bar,&#8221; whether they are better than the average individual at that role. The idea being that if you continue to hire individuals that only raise the bar, you&#8217;ll continuously shift the average upwards.</p><p>I have a high bar. Some of it is individual: I hold myself to high expectations and I expect others to do the same. It&#8217;s a natural, if not honest, thing to do. I&#8217;ve learned that I&#8217;m certainly more popular when I don&#8217;t, but there&#8217;s an irony in that. Lowering expectations disrespects the other. I can afford people leniences and say &#8220;oh that&#8217;s good for <em>you,&#8221; </em>but how bigoted is that? How vain is it for me to categorize people as to what they can and cannot do, rather than treat them as equals? </p><p>So I don&#8217;t believe in a selective bar. There&#8217;s only one - my own. <br>And now&#8217;s the hard part. Raising the bar is hard. Very hard. You&#8217;re breaking the status quo. You&#8217;re walking in, saying &#8220;this is not the way we should be doing things&#8221; and waging war on precedent.</p><p>There&#8217;s a few ways people typically go about it. For one, fear. Fear is an incredibly effective way to spur action, as regrettable as it is. Simply being in the presence of a superior will quickly force most to get their act together. Couple that with draconian punishment doled out at any hint of incompetency and you have a recipe for the military. And it does work - just look at how hedge funds and big law firms are run.</p><p>That&#8217;s all very familiar to me. It&#8217;s how I was raised. So when I joined Amazon and encountered more of the same, I wasn&#8217;t fazed. The challenges I confronted paled to my past. But despite that, I refuse to do the same.</p><p>Fear is effective. And if I were the type of person to optimize on outcome, it&#8217;s the logical choice. But I&#8217;m not. I&#8217;m a punk and my vanity makes me think I can do without.</p><p><br>And now&#8217;s where I&#8217;m stumped.<br>I tried a lot of things. I asked questions, I talked about goals, I gave lectures, I wrote letters, I learned that team events are incredibly high return on investment (so are snacks) and tried to get into the mind of my mid 20-somethings (I downloaded TikTok) before realizing that my attempts to do so would only further estrange me.</p><p>I&#8217;m trying to inspire them. To work, yes, but to also take pride in what they do and find purpose in it. </p><p>I&#8217;m up against tough competition and I know. There are way too many fun things in life to list out here and it&#8217;s a far sell to think that a corporate job at a big tech company could compare. But still, I&#8217;ll try. </p><p>The only thing to beat fear is hope. Well at least, that&#8217;s mine.</p>]]></content:encoded></item><item><title><![CDATA[Indignance]]></title><description><![CDATA[A word sets a tone.]]></description><link>https://www.baepaul.com/p/indignance</link><guid isPermaLink="false">https://www.baepaul.com/p/indignance</guid><dc:creator><![CDATA[Paul Bae]]></dc:creator><pubDate>Sun, 05 Jan 2025 20:14:14 GMT</pubDate><content:encoded><![CDATA[<p>A word sets a tone. <br>In this case, a rather pretentious and archaic one.</p><p>I feel the need to write. No idea to convey or point to persuade, simply a drooling of pen on paper. An untitled unmastered mess.</p><p>Writing is strange. Given a context, it&#8217;s a rather mundane thing. If the aim is clear, the words write themselves. If I know what to write, writing is a matter of the means. Find the diction, find the tone to paint the picture as I perceive it.</p><p>Other times, as now, it&#8217;s a strange thing. It&#8217;s an act of effort. One that requires me to wake, don the garb of courage (or something like it), and stare vapidly at a blank page while I ruminate what it is I want to write - what I need to write. </p><p>It demands honesty. It&#8217;s easy to escape from anxious thought to another in the recesses of one&#8217;s mind. It&#8217;s harder to do so on paper. The pen doesn&#8217;t lie. If you write something untrue, it stares blankly back. Each word a stake in your conscience, a reminder of guilt.</p><p><br></p><p>I haven&#8217;t written like this in quite some time and it shows. <br>I used to write for self more frequently. Day by day, or week by week, whenever the need strikes, just writing to write.</p><p>It&#8217;s not so enjoyable really. The term journaling has come into vogue, and though that seems to share similarities with what this is, I&#8217;m skeptical that it is. Perhaps it&#8217;s just the way that its marketed as part of &#8220;wellness weeks&#8221; and &#8220;self-care routines.&#8221; Or perhaps it&#8217;s just my personality to eschew anything popular.</p><p>But its effects are clear. For one, I seem to adopt the language used in speech. Often, I regurgitate written answers to common questions asked, as if I had crammed for a pop quiz on my personality. The same goes for what I read. What leaves my mouth is a mix of the prose I consume and the words I write. If I happen to be on a particular esoteric binge, I&#8217;ll gladly give voice to anachronistic words like &#8220;antediluvian&#8221; and &#8220;multilateral.&#8221; Pretentious, I know.</p><p>And for two, there&#8217;s a certain assuredness I gain after writing. As if I&#8217;ve made that amorphous thing known as identity concrete by giving it form. I feel better, in self. Resolute in who I am and who I strive to be. That armor doesn&#8217;t last long; its chipped at and taken away by the deluge of the day-to-day. Hence, I write. To find self and define what it be.</p><p>Why I publish what I write is a better question. I remember being reticent to share what I wrote prior, and it took quite a while to be comfortable in doing so. My answer now is I simply don&#8217;t care. I am who I am - and unapologetic in that.</p><p>That isn&#8217;t to say I don&#8217;t think about how I&#8217;m perceived. I do, and often to my own detriment. Even now, the faces and reactions of the few readers who might read this  flash by. But they&#8217;re secondary. What matters most is what I think of myself. And if I&#8217;ve chosen to share, chosen to be vulnerable and let others in, might as well show them everything.</p><p></p><p><br>In lieu of that, there&#8217;s been a few thoughts on my mind.</p><p>I&#8217;m getting older. I tweaked my neck again and it serves as a sobering reality that I&#8217;m not as young as I used to be. Pain makes the present palpable. You become distinctly aware of your own finitude. The limit on what you can achieve and the time you have to do it.</p><p>I can&#8217;t do what I used to do. Perhaps a tad exaggerated as I&#8217;m still young yet, but less and less will doing the same things that led me to success prior, continue to work for me now. </p><p>It&#8217;s a tough habit to break. I walked the path of an individualist for a long time. As a child, be it for one reason or another, I read Emerson&#8217;s essay on Self-Reliance. That work shaped me. It incepted the idea of self-sufficiency, that if you want something done right, to do it yourself. And I lived by that philosophy. I avoided relying on others and always did things myself even if it was work I was ill disposed to.</p><p>Things are different now. I&#8217;ve grown to trust others, both out of inclination and necessity. There&#8217;s a limit on what I can achieve as an individual. And though vain of me to say, I think I&#8217;ve gotten pretty close to it already. That is, I don&#8217;t think I could&#8217;ve worked much harder in times past. </p><p>But it remains to be seen what I can achieve with the help of others.</p><p>Mikkel, my cofounder, cemented that point. I view myself as capable of doing most things relatively well, whether that&#8217;s engineering, sales, marketing or what be it. Yet, I&#8217;m not someone capable of solving fundamentally hard problems. Mikkel is. And by putting my trust in him, in his ability to do things that I can&#8217;t, we can achieve what I cannot alone.</p><p>My relationship with my directs is different. Many of them are young, and yes, I can do more than they can. Much of management is ensuring the minimum. For this person, at this role, what is the expectation and how do you ensure they meet it. It&#8217;s unglamorous, boring work, largely consisting of asking questions and reminding people of their deliverables.</p><p>That alone is a self-fulfilling prophecy. If the goal is to meet expectation, you will never exceed it. It doesn&#8217;t interest me. It doesn&#8217;t expand possibility, it only systemizes it.</p><p>The bet I took is that I can achieve more together than I can alone. That only works if I can raise the upper bound. It&#8217;s the belief that my directs can and will supercede me. That they will obviate me and achieve what I cannot.</p><p><br></p><p>Indignance is the word to start and end on. </p><p>The higher you get up in a company, the more nebulous progression appears to be. Early in your career, promotions are well-defined. There&#8217;s many people to compare yourself to and there&#8217;s much to learn and do. Doing what&#8217;s in front of you is often all it takes to move forward.</p><p>Higher up, it&#8217;s less clear. Tenure plays a part, as does delivery. But what distinguishes a good director from another and how does one go about pushing for a promotion at that level? Many seem to answer with politics. They chase the coattails of their superiors, seeking to appease and get on the good-side of whoever is most influential at the time. They cascade fear, lashing out at their directs in response to their bosses doing the same to them. They wage wars to gain scope and increase their number of reports to embed themselves more firmly as people of undeniable import.</p><p>It&#8217;s the pursuit of power. <br>And I won&#8217;t claim to be above the rest.</p><p>Frustration was the feeling that filled me after abandoning my startup. A feeling of lack. I tried my best to solve a problem that was personal to me - and failed because I was insufficient. I was unable to build the future I envisioned. I lacked power.</p><p>Power is the ability to do what <em>you</em> want to do. At a small scale, it&#8217;s the ability to work on whatever you want to work on and make a living from it. That&#8217;s hard enough. At a larger scale, it&#8217;s the ability to create real change and build assets to do so.</p><p>It&#8217;s tempting to chase scale. To chase capital, to chase influence, to chase promotions and conflate that with ability. But call it indignance or immaturity, I disagree.</p><p>I&#8217;m going to do what I want to do.<br>I&#8217;m going to do what I think is right, be that as indignant as I may.</p>]]></content:encoded></item><item><title><![CDATA[Lessons from JJ]]></title><description><![CDATA[&#8220;What do you want to do with your life?&#8221;]]></description><link>https://www.baepaul.com/p/lessons-from-jj</link><guid isPermaLink="false">https://www.baepaul.com/p/lessons-from-jj</guid><dc:creator><![CDATA[Paul Bae]]></dc:creator><pubDate>Fri, 20 Dec 2024 15:00:00 GMT</pubDate><content:encoded><![CDATA[<p>&#8220;What do you want to do with your life?&#8221; <br>Those were the first words JJ said to me.</p><p>I was an intern at the time. The team I was on owned an internal logging tool for retail systems (i.e., RTLA), but we were soon to be defunct: mandate had came that we be merged into AWS Cloudwatch. I was given two options. I could either accept the return offer, contingent that I emigrate to Dublin, or find another team to return to. I chose the latter.</p><p>I spent the remainder of my internship interviewing. I cold-called managers in Alexa, SageMaker, Last Mile, and a few dozen more. I didn&#8217;t quite know what I was looking for, but I knew what not to look for. Many teams sounded the same. They were all working on something &#8220;business critical&#8221; and I&#8217;d be given opportunities to &#8220;grow my career&#8221; and &#8220;own scope.&#8221; I was being sold - and I disliked it. I distrusted them.</p><p>My first call with JJ started off similar. I explained who I was, the position I was in, and then asked for an overview of his team and the work I&#8217;d be doing. He stared at me for a few seconds in silence, ignored me, and then asked me what I wanted to do with my life.</p><p>I don&#8217;t quite know what I replied with. Probably some incoherent anxious mess, something along the lines of &#8220;I want to learn and build something great.&#8221; His response was as honest as his character. &#8220;Great" and hung up. A few days later, Jim reached out to me to give an overview of Percolate, and a few months later, I was on the team.</p><p>JJ was our team&#8217;s Principal Engineer. He built Percolate, Amazon&#8217;s content optimization system. He created that vision and made it a reality. He wrote every doc, was in every meeting (and was always right), still found time to push code daily, and tore through any and all blockers (be that people or systems).</p><p>He was my mentor. And though my ego wouldn&#8217;t let me admit it at the time, he and I were quite similar. He worked hard and I did too. He loved work and taught me how. He held a ruthlessly high bar and I did the same. He was blunt (at times, overly so) and whether you loved or hated him, everyone in our org knew him. He was incredibly hard to work with, and I loved working with him.</p><p>There&#8217;s a lot I learned from JJ. Some of it was new, ideas that challenged me and made me grow in ways I didn&#8217;t envision before. But most of it was pushing me to be a better version of who I already was. This doc sheds light on a few &#8212; the principles I&#8217;ve learned to work by.</p><p></p><div><hr></div><h3><strong>Aim for great</strong></h3><p>When I first joined Percolate, work was not my motive. I had just dropped out of graduate school at Carnegie Mellon and moved to Seattle. There was much to distract me and fascinate me outside of work. I was addicted to Overwatch at the time. I tend to get quite competitive when playing video games, with the mindset of either I&#8217;ll be the best in the world or quit it entirely. </p><p>I did that initially with League of Legends, where I no-lifed it for a season and got up to Diamond, but then quit when I plateaued shortly afterwards. Overwatch was dangerous because I didn&#8217;t. I kept climbing until I was ranked in the top 100 and was even courted by a few pro teams to come do tryouts. That&#8217;s all to say, my day-to-day initially consisted of coding in the office from 10AM to 5PM, going home, and then playing Overwatch from 6PM to 2AM.</p><p>The first project I was given exacerbated that fact. Jim gave me the Percolate Management Tool. The goal of the tool was to provide a single consolidated view of all the different content strategies scheduled in Percolate. It was an odd project as it was isolated from the rest of the team. And it was an easy project, as it was just spinning up a web server to call an API and render some JSON data in a Gantt chart view. So I just did it. I hacked it up, showed Jim what I built, made him happy enough, and went along thinking &#8220;Is this all work really is?&#8221;</p><p>JJ broke that. About three months in, I received an email for a &#8220;Search-Percolate kick-off meeting.&#8221; I showed up and JJ was in the room, along with a Sr. Manager and two Sr. SDEs from Search. He began commandeering the meeting, throwing a deluge of terms I didn&#8217;t understand: link parameters, eventual cache consistency, customer targeting criteria. The meeting escalated as JJ and the SDEs began arguing over both technical and business details. &#8220;What&#8217;s the expiry time on the cache, should it be configurable per provider?&#8221; &#8220;How do we ensure data isolation between different providers?&#8221; &#8220;Is the end customer experience we&#8217;re enabling here sufficiently large to justify the investment?&#8221;</p><p>Then JJ turned around, quit talking, stared at me and asked &#8220;What do you think Paul?&#8221; I felt a rush of red course through my head and stammered out &#8220;I don&#8217;t know.&#8221; After the meeting ended, JJ grabbed me and said &#8220;You&#8217;ll be owning this, write a design doc.&#8221; and walked briskly away to another meeting.</p><p>I felt a mix of feelings. Yes, I felt embarrassed, I felt unprepared, I felt I was in a position I was unready for. But at the same time, I was excited. I was shown how much I didn&#8217;t know, how much I lacked, and how much I could learn.</p><p>I wrote my first design doc the next day of and sent it to JJ by email at 5PM. An hour later, he replied with 60 comments in red. State all requirements as P0 or P1. Propose a singular solution. Use the word shall not will. Does this meet the latency requirement, have you tested? This schema isn&#8217;t flexible enough, fix it.</p><p>I was in shock. For one, I didn&#8217;t expect he&#8217;d reply so quickly. And for two, I never received feedback like that before. It was direct, it was detailed, and it was stated as fact. As much as I tried to dispute his comments, they were right. I revised the design doc the night of, sent it to JJ, and he replied a few minutes later with &#8220;Great, thanks, go build it.&#8221;</p><p>A lot happened after that. I started working hard because I found a reason to care. I was given projects that were beyond me, things that I couldn&#8217;t handle and was expected to fail. And I did fail. I failed a lot. Those failures made it clear how I lacked and motivated me to become more than who I was before.</p><p>I&#8217;ll caveat that this rather draconian way of mentorship isn&#8217;t one I think works for all people. People are different, and there&#8217;s some inherent parts of my personality that suit the JJ school of thought well. Yet, I&#8217;ll be transparent and honest in who I am. This is the way I&#8217;ve learned to work and this is the way I love to work.</p><p>Aim to be great. Don&#8217;t settle for good. Don&#8217;t compare yourself to the other SDE Is, or the other SDE IIs, or even the other SDE IIIs. Find the single smartest person in your org, the guy who&#8217;s doing 10 times the work others are, the guy who&#8217;s always right about everything, the guy who comes up with new ideas every week and aim to be him. If you can&#8217;t find him, then define him. Redefine expectations and push the bar of what&#8217;s possible. That&#8217;s your comparison.</p><p>JJ was my bar. Not anyone else. My goal was to exceed him: to do something he couldn&#8217;t and to make him proud.</p><p></p><div><hr></div><h3><strong>Work hard</strong></h3><p>I&#8217;ve never thought of myself as a dumb person. And though I wouldn&#8217;t say I was particularly precocious, I did pretty well in school while trying relatively little. I made games of skipping university classes, minimizing the number of in-person attendances required to get an A contingent I&#8217;d ace all my exams. My linear algebra professor caught notice of it and used to announce my arrivals with especial emphasis, &#8220;Paul, how nice of you to join us today!&#8221;</p><p>But I&#8217;ve never thought of myself as a smart person either. That was painted in clear reality when I met my cofounder, Mikkel, freshman year of college. I was taking discrete math at the time and catching up on overdue homework as usual. There was a particular proof I struggled with, and though I solved it, I presented the answer with some uncertainty. Mikkel took one look and said &#8220;Wrong.&#8221; I asked &#8220;Why?&#8221; His reply,  &#8220;It&#8217;s obvious.&#8221; I spent the next three hours furiously trying to disprove him, but then realizing he was (as he always tends to be) right.</p><p>I felt the same in Percolate. I keenly understood that I was the dumbest person in the room. And not just JJ and Jim, it was everyone in our team. Our team leaned very senior, we had one Principal Engineer, three Sr. SDEs, two SDE IIs, and then me. These people weren&#8217;t only strong because of their tenure, they exceeded it. They were smarter than me, more talented than me, and had more experience than me. How was I to catch up? My answer was to work.</p><p>There&#8217;s times in life where failings can feel crippling. Where I feel frustrated at my own weaknesses, my own lacking, and lament myself for it. I wish I was smarter, I wish I was older, I wish I walked a different path than I had thus far. It&#8217;s painful because it&#8217;s true - there are certain walls you can never overcome despite how much you might try.</p><p>But still, I choose to work. Hard work is my solace. And if I&#8217;m about what I say I&#8217;m about, if I really want to build something great, that&#8217;s my only option. I can&#8217;t change who I am. I won&#8217;t ever be smarter than Mikkel. I won&#8217;t ever be older than I am. </p><p>The only thing I can do is work - so I will.</p><p>It&#8217;s easy to romanticize the life of a startup founder, thinking that your passion will be so fulfilling that it&#8217;ll obviate all the effort required. That once you&#8217;re doing what you want to do, work will be effortless. It won&#8217;t. You&#8217;ll be working 80 hour weeks and if you can&#8217;t deal with that, if you can&#8217;t do that, you shouldn&#8217;t start. It&#8217;s the same for many other pursuits. It&#8217;s fun to talk about starting a restaurant, it&#8217;s not fun to actually do it. I can talk about wanting to be a journalist, but the reality will always betray the thought.</p><p>If you want to do what you want to do, if you want to do something real and meaningful to you, then work. </p><p>Work hard. Try the hardest you&#8217;ve ever tried. Give it your all and do everything you can. Do that every single day. Don&#8217;t just read this and be motivated for a few days. Each and every day, wake up, remind yourself of the person you want to be, and work hard.</p><p></p><div><hr></div><h3><strong>Love what you do</strong></h3><p>There&#8217;ll be times in life where the only thing you want to do is work.</p><p>JJ said that to me on a Friday night in the office. I don&#8217;t recall why he said it, but the phrase strikes in my memory since.</p><p>Work gives me purpose. I like what I do, I like building products for people, I like mentoring and developing others, I like writing, I like inspiring, at times I even like the politics and the absurdity of it all.</p><p>When I was on Percolate, work gave me an incredible amount of purpose. I believed in our vision, I truly wanted to make Percolate succeed and thought that what we were doing was the right thing to do for the customer. We were buccaneers making the site for better. We went from page to page, found crappy content systems, and replaced them with dynamic personalized recommendations. I loved the people I worked with. I learned from them, became close to them, and eventually felt responsible for them. They relied on me and I was intent on never betraying that trust.</p><p>After I quit Percolate, there was a certain void that occurred. Work had been the primary thing in my life that fulfilled me, to perhaps an abnormal degree. Some part of me attempted to rectify that by doing more of the same. I found stuff to work on, kept myself busy by taking lectures and reading papers, and continued to build side-projects. That didn&#8217;t quite work: I still felt empty and unfulfilled. </p><p>So I started something new. I got into a lot of hobbies, met a lot of people, and did things I&#8217;d probably never do again. I learned how fulfilling life can be outside of work, how purposeful relationships can be, and how meaningful life in itself really is. I'm grateful for that and cherish what I&#8217;ve found.</p><p>But I still love work. I love what I do. <br>At the end of the day, few things are cooler than building products that solve problems for people.</p><p>So learn to love work. Give it a shot. Rather than think about how to minimize effort, give a shit. Actually try. Be an owner and think about what would you do if you were in charge. What would you do instead? </p><p>And even after that, if you find that what you&#8217;re doing is not what you&#8217;re supposed to be doing, then quit. Figure out what you want to do: be that art, literature, activism, or whatnot. Quit and go do that. Be proud of what you do. You choose what to work on. Not your manager, not your director, not anyone else. Don&#8217;t forget that.</p>]]></content:encoded></item><item><title><![CDATA[141 Days]]></title><description><![CDATA[It&#8217;s been 141 days since I rejoined Amazon.]]></description><link>https://www.baepaul.com/p/141-days</link><guid isPermaLink="false">https://www.baepaul.com/p/141-days</guid><dc:creator><![CDATA[Paul Bae]]></dc:creator><pubDate>Fri, 13 Dec 2024 15:00:00 GMT</pubDate><content:encoded><![CDATA[<p>It&#8217;s been 141 days since I rejoined Amazon.</p><p>In that time, I did a lot. Wrote a lot of code, wrote many more docs, pitched a lot of ideas, and was fortunate enough to have one go through. I was busy, and the languid state of my body corroborates that fact. Yet, it feels as I&#8217;ve achieved very little. Perhaps more telling of my own personality than anything, but it stands as my own truth I can&#8217;t deny.</p><p>The intent of this doc, this series of weekly notes, is a few-fold. For one, it&#8217;s to write. I like writing, and while Amazon lends itself well to that, there&#8217;s aspects of its written culture I disagree with. Too often do we seem to focus on the audience, harping on particular words and dictions to appease. We rewrite docs to be more &#8220;scientific&#8220; if that&#8217;s in leadership vogue and avoid particular words like the plague (the word graph, I&#8216;ve learned, is perhaps more taboo than common expletive). That irks me. And while I recognize the practicality of it and am no longer as indignant as I used to be, it still leaves me wanting an outlet for self.</p><p>There&#8217;s a particular way I write. I like short sentences, I like esoteric words, I like flirting with the grammatically incorrect. I like statements with a bit of bombast, the unsubstantiated to inspire. I write for myself - and I take pride in what I write. And in some sense, the way I write <em>is</em> very Amazonian. I remember religiously reading &#8220;The Elements of Style&#8221; by William Strunk after having my first doc be ravaged by a slew of comments. Remove what doesn&#8217;t add. Revise obsessively. Active voice over passive. I&#8217;d repeat those rules to myself chronically as I wrote and re-wrote. And then to others as I began to review their writing.</p><p>The second purpose is to be read. Although many writers will often say that the act of writing itself is satisfaction enough, I disagree. There is a lucidity that writing can bring about and its something I rely upon heavily, both personally and professionally. But <em>writers</em> are quite the egotistical bunch. What writer doesn&#8217;t want their work to be read? And I aspire to write well. To write something real that stands on its own.</p><p>The third, and the most vain of all, is to sell. There&#8217;s a vision I have of Amazon. I was lucky enough to be exposed to it 8 years ago. The people around me embodied it: they were incredibly smart, worked hard, and made amazing things happen for our customers. I followed suit. I was inspired to work and I fell in love with my job. Work, in no small part, gave me purpose. At the time, I knew the team I was in was special, but I didn&#8217;t realize how special it was until I left.</p><p>Things are different now. The company&#8217;s changed and I&#8217;ve changed. No longer am I an over-confident SDE I, my role&#8217;s different now. Some of it, yes, is to &#8220;manage risk&#8221; and be the cog that keeps the company churning. But the other part of it is to be a mentor and a friend. To pass the torch on and do what was done for me. Show people how fun work can be, how exciting it can be to build products for people and relish that joy together.</p><p>So, some part of this will be stories about work. From Percolate, from Stripe, from my startups (DeepDive &amp; Rehabbit), and the random things in between. The other parts (unsurprisingly) will also be about work: lessons I&#8217;ve taken to heart, principles to operate by, and ideas to share. And on occasion, a soapbox on whatever happens to be gnawing at me at the time.</p><p>It is my hope that in some small way, these writings will be of use to you.<br>&#8212;baepaul</p>]]></content:encoded></item><item><title><![CDATA[Rehabbit]]></title><description><![CDATA[I have a long history with pain.]]></description><link>https://www.baepaul.com/p/rehabbit</link><guid isPermaLink="false">https://www.baepaul.com/p/rehabbit</guid><dc:creator><![CDATA[Paul Bae]]></dc:creator><pubDate>Sun, 21 Jul 2024 18:06:00 GMT</pubDate><content:encoded><![CDATA[<p>I have a long history with pain.</p><p>I started climbing at the end of COVID-19. </p><p>Lockdown restrictions were loosening and I, just like many others, was anxious almost rabid to get out and about. Climbing hadn&#8217;t appealed much to me before - I&#8217;d been taken a few times in Seattle by tech yuppies, a predominant faction of gyms&#8217; clientele, and found it boring. A modern-day social sport, the equivalent of bowling alleys in the 90s. But be it for one reason or another (likely some pent-up ennui), this time I was hooked.</p><p>I&#8217;m quite obsessive. I&#8217;m the sort of person to look for purpose in pursuit and commit myself wholly to it, often times to my own detriment. I was addicted to work, I was addicted to video games, and this time, I got addicted to climbing.</p><p>There&#8217;s a certain combination of traits I look for in a discipline. Climbing had them all: it was individualist (you don&#8217;t need a team to climb), it was a skill sport (that lent itself well to progression), and it suited me well (one of the few sports a skinny 5&#8221;7 guy could excel at). So I did as I always have, I obsessed over it: climbing as much as my body would allow me, tossing myself relentlessly at the wall, and spending copious amounts of time analyzing my own climbing and that of others.</p><p>That led to two outcomes: I got a lot stronger and I got a lot of injuries. </p><p>Not a particular surprise, when you consider moments like these:</p><div class="native-video-embed" data-component-name="VideoPlaceholder" data-attrs="{&quot;mediaUploadId&quot;:&quot;5163c5d3-a7b9-414e-b1bd-caaed39dabd2&quot;,&quot;duration&quot;:null}"></div><p></p><p>And that started my history with pain.</p><p>The first injury I ever got was a lumbrical injury, a minor muscle in the palm of the hand. I sprained mine while matching the finish hold on my first V8. I felt something funny immediately which cascaded into a sharp pain radiating through my palm. The morning after, I was unable to open or close my hand without intense pain shooting through my arm.</p><p>That terrified me. To have something you&#8217;ve taken for granted, something you&#8217;ve done millions of times before, be rendered decrepit in a day. It was traumatic.&nbsp;</p><p>In hindsight, after receiving and rehabilitating a long list of injuries, this episode seems almost minor. I&#8217;ve had TFCC tears, MCL sprains, pulley injuries, joint synovitis, shoulder impingement, and even a cervical herniated disc. Many of those hurt far worse and disabled me for far longer. Yet the first is still hard to forget.</p><p></p><div><hr></div><p></p><p>Now again, I&#8217;m obsessive. </p><p>So when I, a try-hard who would literally do anything to climb harder, was set back by injury; what did I do? I contacted sports doctors, physical therapists, certified hand therapists and spent copious amounts of time and money to fix my body. I learned a lot about injury.</p><p>Take shoulder impingement for example. Patients typically present pain in the shoulder, limited range of motion, and weakness. The underlying pathophysiology is vague. The hypothesis is that something in your shoulder&#8217;s subacromial space is impinging against each other: tendon rubbing across bone or inflamed bursas. But we don&#8217;t know what. In other words, something in your shoulder is inflamed and it&#8217;s causing you pain.</p><p>When I went to my sports doctor for a diagnosis, he didn&#8217;t administer any scans or MRIs, he simply moved my shoulder around a few times and gave me a referral to physical therapy. The physical therapist did the same. He moved my shoulder around a few times and told me to do a bunch of shoulder exercises.</p><p>That bewildered me. I advocated for myself and pushed for scans, but they were deemed medically unnecessary. How was it that my doctor could accurately diagnose me based off nothing but a few questions and physical tests? How was it that the only treatment I was prescribed were a bunch of exercises with rubber bands?<br></p><p></p><p>I was skeptical. </p><p>I began to research the literature myself: buying orthopedic textbooks, reading dozens of papers on treatment efficacy, and experimenting with myself (running A/B tests on different treatments and recording progress/pain over time).</p><p>And the evidence was clear: physical therapy does work. It&#8217;s a proven scientifically backed treatment to many forms of physical pain. It&#8217;s a long-term fix that addresses fundamental root causes. It was the only thing that truly helped me.</p><p><br></p><p>But while physical therapy as a treatment was effective, the industry wasn&#8217;t.</p><p>It&#8217;s expensive. It costs a minimum of $125 per session in New York, running up to $250 for boutique clinics. That&#8217;s a recurring cost - one session of PT isn&#8217;t enough, you need 2-3 visits a week for months.</p><p>The quality of care is going down. As margins grow thinner for clinics, &#8220;mills&#8221; are becoming the prevalent model of care. Clinics where the primary form of treatment is group sessions, where a single physical therapist aide runs around supervising groups of 8-12 patients doing exercises.</p><p>The real value of physical therapy is information. The diagnosis and the exercise plan. Once I know what to do, it&#8217;s a matter of doing my exercises regularly. I don&#8217;t need to go into a clinic to do that; I can do that on my own time in my own home.</p><p>And that&#8217;s the PT idea. We founded Rehabbit on three beliefs.</p><ol><li><p>Physical therapy is effective</p></li><li><p>Physical therapy is just exercise</p></li><li><p>Anyone can exercise</p></li></ol><p></p><div><hr></div><div class="native-video-embed" data-component-name="VideoPlaceholder" data-attrs="{&quot;mediaUploadId&quot;:&quot;b09648aa-63a4-4c98-881e-b0751f479b75&quot;,&quot;duration&quot;:null}"></div><p></p><p>Our MVP.<br>A medical chatbot.&nbsp;<br>A historically bad startup idea.</p><p>But we believed our approach to be different for two reasons:</p><ol><li><p>We mitigate risk</p><ol><li><p>Diagnosing physical injuries is easier than medical conditions.</p></li><li><p>A sore throat can indicate a large range of diseases, ranging from minor colds to serious conditions. Muscular pain is a lot easier and a lot less risky.</p></li></ol></li><li><p>We treat directly</p><ol><li><p>A chatbot might be right in diagnosing you with the flu. But what&#8217;s the next step? It can&#8217;t prescribe treatment.</p></li><li><p>But we can. If we diagnose a patient with shoulder impingement, we can recommend a personalized rehab plan immediately.</p></li></ol></li></ol><p></p><p>We showed it to climbers.</p><p>The response was largely positive. People liked the immediacy, the diagnosis, and the simplicity. But we had to take that with a grain of salt: they were churning. They would use it initially, do some exercises for a few days, and then quit subsequently after. We had an adherence problem. Our app could diagnose injuries and tell people what exercises to do. But how do we ensure patients adhere?</p><p>We decided to onboard physical therapists.</p><p>Our pitch to providers was simple: $30 for a 30 minute call. After the call, patients would be able to text their providers and vice-versa. What we wanted was accountability. We believed that patients would be more likely to adhere if they were told to do so by a real person, not an app. Someone they could call, someone they could text, someone they would see - whenever they opened the app.</p><p>The pitch worked. We cold-called therapists and were able to onboard a dozen or so with nearly all calls converting.<br></p><p></p><p>We launched a few weeks later. Our go-to-market targeted climbers: a chronically injured and obsessive customer base. We launched on Reddit, first on a smaller niche <a href="https://www.reddit.com/r/climbharder/comments/1d9sn2i/looking_for_feedback_on_app_for_injury_rehab/">/r/climbharder</a> subreddit and again on the larger <a href="https://www.reddit.com/r/climbing/comments/1deeztn/i_built_a_free_app_for_rehabbing_climbing_injuries/">/r/climbing</a> subreddit.</p><p>The response was overwhelming. 150K impressions, 1K upvotes, 100 comments, 500 shares, and 500 installs within a few days. But it felt odd.</p><p>Mikkel and I would often talk about firsts. Our first customer, our first dollar, our first employee. How good it would feel, how motivated we&#8217;d be, to know that what we&#8217;re working on is no longer just an idea, but a business. A small business no doubt, but a business nonetheless. Something real.</p><p>It didn&#8217;t feel that good. </p><p>I was at the climbing gym when Mikkel texted me the numbers. For a few minutes, I was euphoric bouncing around the walls grinning like an idiot. But then I started thinking what next. Now that we have customers, how do we scale, how do we grow, how do we raise?</p><p></p><div><hr></div><p></p><p>The ending of this story is as abrupt as reality. I quit working on Rehabbit a few days after we launched.</p><p>Life happened. I won&#8217;t explain the details, but my time was cut short. If I wanted to keep working on Rehabbit, I needed it to succeed and do so in a short time-frame.</p><p>So I quit.</p><p>Fear was a factor. If I had full confidence, the conviction that our idea would succeed no matter what, I would&#8217;ve stuck with it. I would&#8217;ve made things work. I didn&#8217;t - I&#8217;ll admit it.</p><p>We were struggling to raise capital to scale. We didn&#8217;t have a concrete plan on how we&#8217;d support insurance. We didn&#8217;t have a why now. Why our idea wasn&#8217;t done already given the underlying technology was all present years prior.</p><p>If I had the pluck I typically carry myself with, I probably would&#8217;ve kept trying. Kept bullishly pursuing my beliefs, regardless the obstacle. I didn&#8217;t.<br><br><br></p><p>Startups are hard. Really hard.</p><p>There will always be questions unanswered and challenges to confront. There will never be a point with certainty where we can say we&#8217;ve succeeded. It is, and always will be, an uphill battle.</p><p>I didn&#8217;t know what it means to start a business a year ago. I won&#8217;t claim that I do now.</p><p>But what is clear is that your business is your life. And nothing else in your life, takes precedent. To succeed, you need to commit - for as long as it takes.</p><p></p><div><hr></div><p></p><p>To end, here are some thoughts.</p><p>Physical therapy is broken.</p><p>It&#8217;s growing rapidly as a whole, projected market cap from $60B to 2024 to $128B in 2032. But margins are thin. Net profits are single digit percentages. There&#8217;s a huge discrepancy between what&#8217;s billed for a session and what the therapist takes home. Reimbursements for a session can total over $200. A therapist takes home $50.</p><p>The existing business model isn&#8217;t scaling.</p><p>Clinics can&#8217;t set their own prices. They&#8217;re subject to billing the CPT codes mandated, which means their only means of leverage over revenue is optimizing costs. That leads to acquisition and conglomerations: larger groups buying up individual clinics and standardizing operations. More &#8220;mills&#8221;, more group sessions, all of which directly reduce the quality of care.</p><p>The model needs to change. And it has already.</p><p>What we&#8217;ve built is Hinge Health for the public. Hinge Health is a MSK startup valued at $6.2B. It has the same model of care we do. Patients get assigned physical therapists who provide initial 15 minute consultations and support through text messages. Patients then do their exercises without in-person supervision.</p><p>This model has been <a href="https://phti.org/announcement/new-analysis-virtual-msk-solutions-improve-health-outcomes-and-lower-costs/">proven</a> to work. </p><p>It&#8217;s cheaper and more effective than traditional models of care. But, it&#8217;s hard to take it and deploy it en masse. Insurance is the blocker. Telehealth consultations with physical therapists aren&#8217;t supported. You can&#8217;t bill for text message support and monitoring. So what MSK startups, such as Hinge Health, have done is sell their product directly as a cost savings to employers, given that insurers don&#8217;t support their model as-is.</p><p></p><p>However - things are changing.&nbsp;<br>This model can be supported by insurers now.</p><p>Telehealth consultations can be billed for under COVID provisions. <a href="https://www.cms.gov/files/document/r11118cp.pdf">RTM devices</a> are a new class of billables that let providers charge for remote patient monitoring and text support. Admittedly, these codes are on shaky ground. Some of the bills are temporary and it&#8217;s unclear whether they&#8217;ll be <a href="https://www.govtrack.us/congress/bills/118/hr7623">permanent</a>. Others are nascent and their reimbursement rates remain to be negotiated. But it is possible.</p><p>And if it were, we could take a proven superior model of care and directly replace traditional clinics.&nbsp;</p><p>That&#8217;s the vision for Rehabbit: to redefine physical therapy.</p><ol><li><p>Personalize physical therapy for the patient</p></li><li><p>Build a sustainable model for the provider</p></li></ol>]]></content:encoded></item><item><title><![CDATA[A deep dive.]]></title><description><![CDATA[Welp, we failed.]]></description><link>https://www.baepaul.com/p/a-deep-dive</link><guid isPermaLink="false">https://www.baepaul.com/p/a-deep-dive</guid><dc:creator><![CDATA[Paul Bae]]></dc:creator><pubDate>Mon, 29 Apr 2024 22:04:40 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/e76712a1-c976-4f59-b6cf-b1d1ec84e56a_512x512.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Welp, we failed. DeepDive is dead.</p><p>Though there are a few reasons I could articulate as to why, there&#8217;s only one that matters.&nbsp;</p><p>We quit working on DeepDive because we didn&#8217;t believe it solved a real problem.</p><div><hr></div><p>DeepDive was an AI-powered tool for data analysis and visualization.</p><p>It enabled users to interact with data in natural language.<br>Given a question (e.g, &#8220;get average salary by department&#8221;), it would generate a SQL query, execute it, and visualize the result.</p><p>And while natural language was the primary mode of interaction, it wasn&#8217;t the only.<br>Users could edit resulting visualizations through our UI and correct any mistakes that our models would make. Those edits would then serve as training data for our models, allowing us to effectively learn from direct user feedback.</p><div class="native-video-embed" data-component-name="VideoPlaceholder" data-attrs="{&quot;mediaUploadId&quot;:&quot;b8792154-75dd-4274-bbc0-4293548c2f86&quot;,&quot;duration&quot;:null}"></div><div class="preformatted-block" data-component-name="PreformattedTextBlockToDOM"><label class="hide-text" contenteditable="false">Text within this block will maintain its original spacing when published</label><pre class="text">                                                               <a href="https://www.youtube.com/watch?v=mZ9mRn0zGo8">(full demo)</a></pre></div><p><br></p><p>We worked on DeepDive for about 5 months.</p><p>We started with a problem: data analysis for machine learning.<br>We both come from data-driven companies and spent a lot of time debugging large, complex, machine learning models. Most of that took place in notebooks: web-based IDEs where we wrote one-off scripts in Python and SQL to fetch and visualize data. That process is painful - and we knew it well.</p><p>So our initial goal was to build a tool that would solve that problem.<br><br></p><p>We did with a technology we believed to be revolutionary: LLMs.<br>We hacked up a prototype, tested it on a few data sources, and soon came to a rather rude awakening.</p><blockquote><p><em>How was this different from a notebook with a ChatGPT plugin?</em></p></blockquote><p>At the time, GPTs weren&#8217;t launched, but many others had the same idea we had, and we knew. It worked well, surprisingly well, for how little effort it took to build.</p><p>And that was the issue.<br><br></p><p>If our target audience were other tech companies building machine learning models, why wouldn&#8217;t they just build an internal tool to do the same? Would they be willing to pay per seat subscription fees, share private data, and take a bet on an unproven startup?</p><p>We didn&#8217;t think so.<br>At least, for our tool as we had defined it.<br><br></p><div><hr></div><p>For a few weeks, DeepDive lived as an ambiguously defined business intelligence platform.</p><p>We began to think: isn&#8217;t the real value in our tool to people who don&#8217;t know SQL?<br>Engineers already know how to write SQL.<br>Product managers don&#8217;t.</p><p>By enabling them to analyze data themselves, we&#8217;d be empowering them to do something that they couldn&#8217;t before. But there was a big problem with that: LLMs are inherently wrong.</p><p>While we could easily generate a SQL query, how could we guarantee its correctness?<br>Engineers can read SQL and point out mistakes.<br>Product managers can&#8217;t.<br><br><br>Our answer was to build.</p><p>We built a visual editor that exposed SQL through a series of dropdown and drag-and-drop gestures. We wrote a SQL decompiler, came up with an intermediate language for a &#8220;viz spec&#8221;, and created intuitive UIs around it. Those UIs both explained the underlying SQL query and enabled users to edit them as needed.</p><p>That not only made it okay to be incorrect, it gave us a long-term plan on how <em>to be correct</em>.</p><p>That is, if a user asks &#8220;top market segments,&#8221; then clicks a few times to indicate that his definition of &#8220;top&#8221; really means highest revenue and the &#8220;market segments&#8221; he cares about are limited to automobiles, he&#8217;s really just given us a training sample. He&#8217;s given us a question (i.e, &#8220;top market segments&#8221;) and a SQL query that he&#8217;s satisfied with.</p><p>That data is rare; the state-of-the-art dataset on natural language to SQL only has ~10K <a href="https://yale-lily.github.io/spider">samples</a>. We thought we could get millions. And our plan was to use that data to train fine-tuned models for SQL generation that would be unequivocally superior.<br><br></p><div><hr></div><p>That plan failed on its first step: getting customers.</p><p>Our go-to-market was nebulously defined.<br>We&#8217;re two introverted engineers. We don&#8217;t have many friends, don&#8217;t have sales experience, and found it awkward (and daunting) to cold-call strangers.<br><br>Yet we tried.<br>We paid for a LinkedIn sales account, compiled spreadsheets on leads, and started sending dozens of emails daily with no reply. We talked a lot and we learned a lot.</p><p>In that process, we realized our tool wasn&#8217;t built for business intelligence.</p><ol><li><p>Business intelligence wasn&#8217;t what we thought</p><ol><li><p>We thought business intelligence was data analysis (e.g, &#8220;why did our ranking models change behavior on June 16th?&#8221;)</p></li><li><p>We learned business intelligence was really reporting.&nbsp;</p></li><li><p>Most users ask the same questions: "revenue by year&#8221;, &#8220;KPIs by month,&#8221; and the real need is to surface a report that answers those questions in a consistent way.</p></li></ol></li><li><p>It&#8217;s hard to differentiate BI platforms</p><ol><li><p>Most BI platforms are the same.</p></li><li><p>They all have dashboards, they all have reports, they all have hundreds of visualizations.</p></li><li><p>They&#8217;re more mature than we are - and our one differentiator, natural language, they were building too.</p></li></ol></li><li><p>It&#8217;s hard to sell to companies</p><ol><li><p>We didn&#8217;t know what it meant to be a B2B company.</p></li><li><p>We had the notion that it was a safer business than selling directly to customers, but didn&#8217;t know how enterprise sales worked.&nbsp;</p></li><li><p>We didn&#8217;t have the connections, the experience, or the motivation to pursue it.</p></li></ol></li></ol><p><br><br>But what was unexpected was that we still thought our tool was useful as-is.</p><p>We were in the habit of testing DeepDive on local CSV and Excel files.<br>We would download sample datasets off Kaggle (i.e, 120 years of Olympics history), and then use DeepDive to quickly explore and create reports from those datasets.&nbsp;</p><p>And in conversations with data analysts, we learned how much of their day-to-day still revolved around Excel. They were asked to create reports off spreadsheets on an ad-hoc and regular basis. One of them mentioned that he&#8217;d never be rid of it; despite his company&#8217;s BI platforms and modern tooling.<br><br><br>So we thought. Why don&#8217;t we focus on Excel?</p><p>Excel users had many of the same needs that BI users did. They had data and wanted visualizations. Our product worked well for their use; in fact, even better than it did for BI.&nbsp;</p><p>Our natural language models struggled with many tables, but did very well on a few. Latency was now a none-concern, since we could cache the entire spreadsheet into memory.&nbsp;And, we&#8217;d be able to go to market quicker by targeting the end user; rather than attempting to upsell companies on their existing BI platforms.</p><p><br>And so we built.<br><br></p><div><hr></div><p>A few weeks later, we went to market again.<br>Our target customer was: &#8220;anyone who creates graphs in Excel.&#8221;</p><p>That was a lot of people: marketers, accountants, consultants, brand managers, insurers, even an e-sports team manager.<br><br>But in talking to them, we found that most didn&#8217;t have a real need.<br>They found the product cool and thought of how it <em>could be</em> used, but ultimately their real needs were different: whether that was substantiating their pitch deck or coming up with a League of Legends draft.&nbsp;</p><p><br>But we did find one that was real: lab experiment analysis.</p><p>We found a few material science PhD students who were running experiments day-in and day-out. The lab machines they used to run their experiments outputted CSV files and a significant portion of their day (~30%) would be dedicated to importing these CSV files into Excel, formatting it, applying a few pivot columns and then creating visualizations.</p><p><br>We thought this was it. This was a real problem, a real need for data analysis, and our product solved it.</p><p>We were initially hesitant to pursue it, as we knew, it was a smaller market and an industry we knew little about. But we still chose to do so: we thought it was a real problem, and that, motivated us more than anything else.</p><p><br>We tried for a while.<br>We built a PowerQuery-esque data pipeline to sanitize CSVs. We implemented visualizations our customers asked for: Seurat violin plots, RNA heatmaps, spiral luminescence charts. We cold-called PhD students, material science professors, and read papers to understand what exactly it is that our customers did.</p><p><br>At last, we found a problem and had a solution that worked.<br>But slowly, we realized that we weren&#8217;t the right people to solve this problem.</p><p><br>We didn&#8217;t know much about experimental science.<br>And that hampered us. It made us unsure whether we were doing the right thing and made us reliant on our customers for our vision.</p><p><br>So we quit.<br></p><div><hr></div><p>Failure is the right word for DeepDive.</p><p>I don&#8217;t like the word pivot.<br>In each of our attempts, in each of our efforts to build something great, if we saw some success, we would&#8217;ve kept going. The reality is: we did not.</p><p><br>So we failed. And that&#8217;s something I&#8217;m not ashamed to admit.<br>We had much hubris to eat, coming as two engineers from big-tech.&nbsp;</p><p><br>We looked down on and disdained writing front-end code. But we did.<br>We were reluctant to cold call people and hated rejection. But we did.</p><p>We were scared, we were anxious, we were tired.<br>We didn&#8217;t want to work so hard for nothing but an idea.</p><p>But we did.</p><p><br>We failed and I&#8217;m proud that we did.<br><br></p><div><hr></div><p>We&#8217;re trying something different now.<br>DeepDive was a tech-first approach where we started with the technology and tried to find a problem for it. What we&#8217;re doing now is the opposite.<br><br>We&#8217;re working backwards from a problem that we know is real.<br>We&#8217;re trying to solve my problem: physical therapy.</p><p>I have a long history with physical pain, and though I won&#8217;t use this as an opportunity to pitch, it is a problem that I&#8217;ve tried desperately to solve on my own terms. And now - we&#8217;re building a product to solve it for all.</p><p><br><br>Thank you for reading my eulogy.<br>I am sure, in some senses, this may read as trite.<br>But regardless, the lessons here are those we&#8217;ve taken to heart.</p><p><br>(p.s., if anyone would like to learn more about DeepDive, we&#8217;ve decided to open source it <a href="https://github.com/bkdevs/deepdive-server/tree/main">here</a>. please do feel free to reach out: pybbae@gmail.com)<br>(p.p.s.,  i&#8217;ll be making an effort to write and publish regularly on here, please do subscribe if you&#8217;d like)</p>]]></content:encoded></item></channel></rss>