<?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"  xmlns:media="http://search.yahoo.com/mrss/" version="2.0">
      <channel>
      <title>Xipu Li</title>
      <description>Learn more about what I am doing at xipuli.com/now</description>
      <link>https://xipu.li</link>
      <lastBuildDate>2025-08-05</lastBuildDate>
      <item>
          <title>From Wall Street to Silicon Valley</title>
          <link>https://xipu.li/posts/from-wall-street-to-silicon-valley</link>
          <guid>https://xipu.li/posts/from-wall-street-to-silicon-valley</guid>
          <pubDate>2022-06-11</pubDate>
          <media:content medium="image" url="https://xipu.li//images/from-wall-street-to-silicon-valley/edge-office-view.jpeg" />
          <comments>Office view from <a href="https://edge.app/" target="_blank" rel="noopener noreferrer">Edge</a> in San Diego. Huge contrast to the forest of skyscrapers I was used to when working in Manhattan.</comments>
          <description>A series of unexpected turns of life had brought me from New York back to the West Coast to pursue a career in Software Engineering.</description>
          <content:encoded><![CDATA[
## Intro
Last week, I was still crunching numbers in financial models to evaluate investment opportunities, and now, I'm thousands of miles above the ground, on my way to San Diego to begin a software engineer internship at a crypto startup.

Life had been dramatic these two years and things had developed so quickly that I still wonder if I'm in a dream. I have three hours left until arrival, so I would like to write this milestone post to reflect on what had happened in the past four years.

*Note: the part about my journey on Wall Street was also [posted on WSO](https://www.wallstreetoasis.com/forum/job-search/break-into-wall-st-to-break-into-tech), an online forum for high-finance related topics.*

## Beginner's Luck
When I started my undergrad in finance, I was naive but ambitious. I wanted to be the Wolf of Wall Street, and the lure of a gilded lifestyle had intoxicated me to network with industry professionals non-stop as to get my foot in the door.

Coutless cold emails were sent. After a sea of rejections and non-responses, I got an offer from a [Private Equity fund](https://pouschinecook.com/), where I spent my freshman summer. It was an incredible experience in terms of actually building out [Leveraged Buyout](https://www.investopedia.com/terms/l/leveragedbuyout.asp) [models](https://multipleexpansion.com/2018/04/23/easy-lbo/) for live deals, [due diligence](https://www.investopedia.com/terms/d/duediligence.asp) with CEOs, lawyers, customers etc. On top of all, I learned the importance of communication and how to drizzle business conversations with American idioms.

Leveraging the skills acquired that summer, I got into a large ($80B) [credit fund](https://www.hpspartners.com/en/home/) for a part-time internship. The brand-name worked very well for me to network with [elite boutiques](https://mergersandinquisitions.com/elite-boutique-investment-banks/). Everything was so smooth that I almost got a guaranteed internship at an EB for junior summer. Then, Covid came.

## Survival Mode
My parents informed me that they could no longer support my study in the US financially. And I was facing a $50k overdue tuition. The financial stress destroyed my mental health, which led to absurdly terrible performances for interviews that I worked hard for two years to secure. And the EB that I almost got a guaranteed ticket for canceled their 2021 summer class recruiting process.

That's it. In those two or three months of year 2020, everything went away.

Of course, during that time, recruiting was less a priority than the immense financial pressure I was facing. I could not go back to my home country because there's nothing left for me. My parents had sold the house and car to pay off debt they owed. The thought of giving up was haunting me on a daily basis.

Fate was a very interesting thing. A friend appeared just right before I almost broke down. He taught me how to run ecommerce stores. I was super lucky. The ecommerce business went very well -- I was making, at peak, $3k a day; and the stock market, well, was to the moon everyday so I started allocating free cash flows from the ecom biz to options trading.

It was a miracle that I paid off my tuition in less than half a year. But the cost was that I missed the most important recruiting cycle in high-finance. The ecommerce business was lucrative but it was very labor intensive: I had to carry and manage an inventory, taking photos of the goods, posting, packaging and shipping, dealing with unreasonable customers off-line. I quit as soon as I paid off my tuition.

Then, I was like an aimless fruit fly for that year. I tried out a hedge fund internship, a VC internship, and settled with a small [special situations fund](https://www.c2.energy/) to conclude year 2020.


## Break Into Tech
At this point, I've seen and done most of the things expected from junior level professionals, at least on the Private Equity side. I realized that what I enjoyed (modeling, writing investment memos) were just checking boxes. The value creation and winning bids had little to do with things I enjoyed. 

I also became quite frustrated by how inefficient Wall Street was. Like creating deal folders, finding files, creating due diligence trackers, Q&A logs, extracting schedules from exhibits of some legal documents that were poorly scanned, etc.. And hell, managing data rooms! I started picking up some Python and VBA to automate lots of the tedious works. And I enjoyed it.

That was year 2021. Tech was booming. My [high school friend](https://shumingxu.com/about), who's a Comp Sci major, told me that it's possible to transition into tech. I kind of just put that in the back of my head since I thought the chance for me was not that good because of my non-STEM major. But I kept [learning](https://www.xipu.li/posts/new-things-2021) and [building things](https://github.com/GoodluckH?tab=repositories) on the side, just for fun.

Fast forward to early this year, I joined the company I've been interning at full-time. It's kind of like a dream came true, working in private equity (although it's infrastructure investments) right out of college. I graduated December 2021, and joined the firm in Feb. However, during that one month interim, I got very interested in web3 -- everything from DeFi to writing Smart Contracts. 

The more I built the more I loved tech, and the more faded passion for finance. When [my app](https://apps.apple.com/us/app/apple-store/id1594982631) got accepted by Apple to app store, I decided to make a bold move.

## Start All Over Again
In late April, I started wondering "why don't I get a tech internship for the summer?" It was a daunting thought because the tech industry had been declining this year. [Layoffs](https://news.crunchbase.com/startups/tech-layoffs-2022/) and [hiring freezes](https://news.yahoo.com/tesla-apple-microsoft-peloton-all-of-tech-companies-hitting-the-brakes-on-hiring-202428628.html) were rampant in tech. The macro environment was so dire that I actually thought about delaying my breaking-into-tech plan. 

But I realized that the time was against me. I was 23 already (since I re-did one year of high school when I came to the US), it's now or never. 

Yes, I had to start everything from scratch again, while balancing a full-time finance job. Applying to internships on LinkedIn and AngelList became a second-nature. And I started to cold DM founders/CTOs on Twitter. During that searching period, I saw a fool in the mirror on a daily basis. I wondered why on earth I'm doing this. Oh, I also applied to master schools so I can get that CS degree for visa/immigration reasons.

Once I got accepted into a master school for a Computer Science program, I learned that my current work visa will be voided soon. So, I had a very tight timeline to find an internship. Otherwise, I'll be spending this summer doing nothing while having to bleed my savings to support a life in NYC. 

Big tech firms had already concluded their internship programs last fall. And the few small firms left mostly require Computer Science degrees or prior tech internship experiences. For a whole month straight, I applied to at least 300 internships (lots of them were posted over three months ago).  Didn't get a single response. Not even rejection emails.

It was mid May when I got interviews from three firms. One rejected me after two weeks. One had no response after the HR round. One was a SF based startup that pays very well (2k/week) for interns and for this one, I got the onsite (kinda like [superday](https://www.wallstreetprep.com/knowledge/superday/) in finance) invite after passing the technical round.

I thought I was all set until two days before onsite, I was informed that they had canceled onsite. It's probably because of that [YC warning email](https://techcrunch.com/2022/05/19/yc-advises-founders-to-plan-for-the-worst/) since it's a YC startup that wants to practice financial disciplines.

Three days after, the other startup (crypto) responded, and I was invited to a technical round with the founder.

But after that round, I heard nothing for another week. I checked their LinkedIn job post, that internship position had 900 applicants. And that they were only taking one intern. I thought I was probably a nobody comparing to those with CS degrees and impressive internship experiences.

I was already making other plans for my summer when last Monday (May 30), the HR told me that I got the offer. 


## The New Chapter

Since the intro of this post, I've started my internship at [Edge](https://edge.app/) for a few days. These few days, though, has been an eye-opening experience.

I have observed so many differences between Wall Street and Silicon Valley. Starting with the vibe. The keyword for Wall Street is "discretion". Since many high-finance roles require interfacing with multiple external parties, strict dress codes and languages apply to professionals. You rarely see any high-finance professionals wearing a t-shirt to work. Professionalism is expected everywhere from the [font](https://www.wallstreetoasis.com/forum/off-topic/what-is-the-default-font-at-your-firm) you use for a presentation to the tone of a clarification email.

But on my first day stepping into the startup's office, I immediately notice the expressive vibe that epitomizes Silicon Valley. There are bikes and e-skateboards near the door, people wear all different kinds of clothes, even caps. Oh, there's also a dog! In today's lingo, the vibe is "chill". Even for external facing communications, nothing stops people from using emojis.

Another salient difference is about the mode of work. By that I mean, on Wall Street, trudging through back-to-back meetings can be your daily job. I've made friend with the Outlook reminder that pops up 15 minutes before a meeting. As a result, everyone's very busy because these meetings can be disruptive to workflows to start with, and to-do items get generated from meetings to add on your plate. In short, there's little predictability to what you will be working on before starting the day.

While investment professionals live in their Outlook inboxes, software engineers reside in GitHub, where most of the coding works are being saved, reviewed and version-controlled. Aside from daily huddles and the weekly engineering meetings, my calendar is basically wide-open. And there's a clear sense of what to do everyday, so that predictability allows me to spend time on solving problems (well, that's basically what software engineers do).

Although coding can be self-taught, I've learned so much high-tech knowledge (like [race conditions](https://en.wikipedia.org/wiki/Race_condition), [mutex](https://en.wikipedia.org/wiki/Mutual_exclusion), [Redux](https://redux.js.org/)'s [data flow](https://redux.js.org/tutorials/fundamentals/part-2-concepts-data-flow) logics, [runtime type checking](https://www.npmjs.com/package/cleaners), [future commits](https://github.com/EdgeApp/edge-conventions/blob/master/git/future-commit.md), and more!) in the past few days than I would otherwise learn by myself in months. I think this is a huge benefit of working in-person vs remote. I can just bounce off ideas immediately to engineers around me and ask them anything and get an instant response.

The learning curve ahead of me is very steep, but it will leapfrog my engineering skills. I always want to be a startup founder, so the easy access to founders at Edge becomes very valuable. I look forward to having a cerebral summer and writing another post to share what I learned.

Goodbye Wall Street. 

Hello, Silicon Valley.]]></content:encoded>
        </item><item>
          <title>New Things Learned in 2021</title>
          <link>https://xipu.li/posts/new-things-2021</link>
          <guid>https://xipu.li/posts/new-things-2021</guid>
          <pubDate>2022-01-16</pubDate>
          <media:content medium="image" url="https://xipu.li//images/new-things-2021/vail-mountain-view.jpeg" />
          <comments>Credit is all <a href="https://www.linkedin.com/in/li-w-190868105/" target="_blank" rel="noopener noreferrer">Frank's</a></comments>
          <description>An uneventful year full of trying out new things and learning opportunities</description>
          <content:encoded><![CDATA[
## Breaking into tech (Jan - Oct)

Year 2021 felt like an uneventful weekend given the backdrop of how much had occurred in 2020. However, I had officially made an [inroad](https://github.com/GoodluckH) into tech as I had spent most of my first-half of the year on learning the fundamentals like [algorithms](https://cs61a.org/) and [data structures](https://github.com/GoodluckH/learn/tree/main/Computer%20Science/Data%20Structures%20and%20Algorithms). I'm very grateful for having a part-time internship that had left me with ample amount of time to dig into these computer science concepts while able to earn a living in Manhattan.

Once grasped foundamental concepts, I started to seeing the world differently. Many things we take for granted &mdash; like the traffic control, social media apps, websites, etc. &mdash; started to appear glamorous to me. I marveled at how smart human beings are, how we are able to come up with powerful abstractions like [trees](<https://en.wikipedia.org/wiki/Tree_(data_structure)>), [graphs](<https://en.wikipedia.org/wiki/Graph_(abstract_data_type)>), [lists](<https://en.wikipedia.org/wiki/List_(abstract_data_type)>), and so on, to represent and build our world.

Although there is a copious amount of resources online, many are of low-quality or contain fragmented concepts. I was lucky to avoid wasting time on those hours-long YouTube videos that most uninformed beginners would start with. Thanks to [a high-school friend](https://shumingxu.com/) who now attends UC Berkeley, I was able to get a high-quality self-study curriculum that was ridiculously simple:

1. [CS61a](https://cs61a.org/): an introductory course on programming offered by UC Berkeley
2. Algorithms ([Part I](https://www.coursera.org/learn/algorithms-part1), [Part II](https://www.coursera.org/learn/algorithms-part2)): coursera courses designed and taught by [Kevin Wayne](https://www.cs.princeton.edu/people/profile/wayne) and [Robert Sedgewick](https://www.cs.princeton.edu/~rs/) of Princeton University

All of these resources are available to the public and free-of-charge, which makes me regret about picking finance as my undergrad major (the ROI and the utility are just subpar). High quality learning should involve [robust and frequent tests](https://www.scientificamerican.com/article/researchers-find-that-frequent-tests-can-boost-learning/), and I benefitted a lot from the challenging tests and projects designed by best-in-class professors in the field.

To work in tech as a software engineer, I would have to obtain a degree in Computer Science or related fields due to my visa status. Meaning, there is a good chance that I will be attending a grad school. As a non-CS major, I face a very limited choice when selecting schools. Currently, I have submitted my application for University of Washington, and in the process with Northeastern and Brandeis. From what I learned, grinding LeetCode seems to be more important than the prestige of the school. So, I optimized for location and affordability.

After drafting a list of potential schools, I started planning for something that I thought I would never have to touch again in my life: the standardized test.

Preping GRE was quite an experience. It refreshed my understanding on foundamental math concepts, but more importantly, it taught me how to engage in critical thinking. Within the reading section, there are logical inference questions like "_Which of the following is an assumption on which the argument depends?_", or
"_The argument is most vulnerable to criticism on the grounds that it fails to consider the possibility that..._". Answering lots of these questions had left a mark in my mind. I found that most reading sources online are either biased or outright misinforming. By simply asking what assumptions the claim is based on is a worthwhile mental exercise to help gain clarity and stay objective.

I'm still learning and breaking into tech, but so far, I've been very much fascinated by the power of technology and excited to see how emerging tech like blockchains can transform and empower individuals. [It's time to build](https://future.a16z.com/its-time-to-build/)!

## Trip to California (Nov)

I went to [Bishop O'Dowd](https://www.bishopodowd.org/) for high school and naturally, a good amount of my friends stayed in Cali in pursuit of computer science related majors. It had been more than three years since the last time I visited California, so I decided to take advantage of the Thanksgiving break to pay a visit.

With a duffle bag and a backpack, I hopped on a Uber. Destination JFK. Once I passed the security check, I kinda just walked into the plane as there was no line at the terminal. I later found out that the gate was supposed to be closed 15 minutes before departure but since I hadn't taken a flight for so long, I thought I was early by being there 5 minutes before the departure time &mdash; I had certainly taken so many subways. In other words, I almost missed my flight but because I was not aware of the urgency, the whole process felt was personally tailored.

The next I knew was me, three-hour younger, bathing in the San Francisco sunlight.

California had a unique vibe. There's no exhaustive way to describe it, but many things were of stark contrast to that of New York. The foremost difference was how Uber drivers were so talkative in San Francisco, whereas their New York counterparts were more taciturn. Another difference was obviously the weather. I took the photo below when I was in high school, but didn't start appreciating the picturesque view until after having lived in New York's concrete jungle for a while.

<BlogImg
  src="/images/new-things-2021/hills.jpg"
  alt="Marin Headlands picture"
  width={120}
  height={60}
  objectFit="cover"
  caption="The pic was taken on the Baker Beach. The landscape should be Marin Headlands."
/>

I had a great catch-up with the Berkeley friend mentioned before. We grabbed [pizza](https://www.sliverpizzeria.com/), enjoyed [boba](https://www.instagram.com/hayteaca/?hl=en), and talked hours about everything from what's up with our high school teachers and friends to investing strategies.

Next day was Thanksgiving, and knowing I came to SF alone, a co-worker at my [current company](https://www.edpr.com/north-america/) invited me for a family dinner (Thank you Louis!). The most memorable thing was when kids asked what superpower they should have, a girl answered "hugging", which resulted in kids running around the house hugging everyone. Very wholesome!

The care-free vibe, the weather, the hospitality, and the tech scene finally convinced me to go back to California in the future.

## Things learned from the ski trip (Jan 2022)

A whimsical call to my friend Frank led to an excursion to Vermont. Up until then, I hadn't engaged in any outdoor sport since I moved to New York in 2018.

At Penn Station, Frank, Tom and I convened. We took a train to a parking lot in Long Island to pick up the car, and then drove into a very large boat that could accomodate vehicles. We offboarded in Connecticut and took a break at a Domino's in Massachusetts. Two slices of pizza and three chicken wings later, I learned that Tom and Frank were working on [a startup idea](https://www.etroduce.net/) that sounded quite interesting. The remainder of the drive to hotel, therefore, was dedicated to an intensive conversation about growth strategies, margin projections, and how to pitch the idea to VCs.

<br />
<ExpandableCard 
    title="More on their startup idea"
> 
Basically, they thought the rental market was inefficient as brokers get paid handsomely (usually a month of rent) by just showing potential renters around the apartment. Instead, they were trying rebate a portion of that commission back to renters. So, if I decide to rent a studio for $2,000 a month, then I will get, say, $500 back from their startup. Two founders were thinking about hiring agents on a full-time basis and paying a generous, albeit fixed, salary instead of commissions. They were also envisioning a one-stop shop where people who are poor on paper can get a guarantor service to fulfill property owners' requirements.

<br />

This would be a heavy operating leverage with which the profit margin scales dramatically with revenue growth. Evidently, the hardest part is to ramp up the business to hit that critical mass point. I hope by publicizing their ambition through this blog, Tom and Frank can get an extra boost of motivation.

</ExpandableCard>

<br />

Next day, we arrived at [Okemo Ski Resort](https://www.okemo.com/). And the fun began! As a total beginner equipped with overweight cheap rental gears, I could not possibly enjoy this sport without Tom's patient training. With over a decade of experience, Tom was an expert skier who could do things like spinning and dancing down a [black trail](https://www.skiclub.co.uk/info-and-advice/before-you-go/how-to-read-a-piste-map) or ski on one leg &mdash; all without wearing a helmet.

<BlogImg
  src="/images/new-things-2021/ski-mountain-top.jpeg"
  alt="Me in ski gears. Smiling."
  width={120}
  height={100}
  objectFit="contain"
  caption="There's a black trail behind. The smile was forced."
/>

With Tom's robust training, I was on a lift to [a green trail](https://www.trailforks.com/trails/expresso-409525/) on the second day. Everything was enjoyable until I suddenly face an intimidatingly steep slope. I could barely [pizza](https://en.wikipedia.org/wiki/Snowplough_turn) well, so the slope looked a suicide mission to me. I was paralyzed with my mind envisioning all the epic falls that could happen to me. My legs were shaking. Every cell in my body was in survival mode. Fear took over.

I ended up stood there for quite a while. I tried to postpone the inevitable by telling myself "I will go once there were fewer people". But there was a constant stream of people breezing past me. "There will always be people", Tom said, "the only way to go is down. If you fall, you fall."

I did fall, multiple times. But Tom's words sank in. If you fall, you fall. Our fears and worries are what prevent us from achieving amazing things in life. But life has taught me that the things we fear and worry either 1) did not happen, or 2) happened to us but we've already gotten over with them.

Another thing I learned from skiing was that going too fast can result in dramatic failures. When I just started, I didn't know how to stop, so I dashed down steep slopes like a bullet &mdash; into the woods. The lesson applies beyond skiing. According to [a podcast](https://open.spotify.com/episode/3roDdtLjzduKgLDG0Y8CD9), one of the major reasons why startups fail was that they grow too fast to maintain control.

Now I can do black trails without fears (still with falls, though), and I intend to ski as many times a month as possible. So if you are into skiing, definitely hit me up!

## Inspirations (Jan 2022)

Early in Jan, 2022, I stumbled upon [Nathan Leung's blog](https://www.natecation.com/) on [how to become an accredited investor](https://www.natecation.com/accredited-investor-investing-startups-series-65/). I thought he was a finance-major but as I explored more of his posts, a new world just opened up to me.

There are so many talented college students in the startup game! I was amazed by the things they are building and lifestyles that would be considered as odd in New York. Somehow, I felt a sense of belonging. That had motivated me to learn more and build more.

One thing I learned from reading Nathan's blog was his strong networking skills. This year, I strive to walk out of my comfort zone and meet more people in the startup field. And that's one of the reasons [why](https://www.julian.com/guide/write/intro#:~:text=3-,Human%20connection,-The%20most%20efficient) I was motivated to start this blog to share my journey and updates with my network.

I will start my full-time job in Feb 2 in New York but always willing to meet and chat. Feel free to drop me a note via [email](mailto:xli347-contact@fordham.edu) or a DM on [Twitter](https://twitter.com/theXipuLi). I hope you stay safe and healthy and wish you a wonderful new year ahead!
]]></content:encoded>
        </item><item>
          <title>The Last Programmers</title>
          <link>https://xipu.li/posts/the-last-programmers</link>
          <guid>https://xipu.li/posts/the-last-programmers</guid>
          <pubDate>2025-09-07</pubDate>
          <media:content medium="image" url="https://xipu.li//images/the-last-programmers/six-claude-code.jpg" />
          <comments>To vibe code, or not to vibe code. That's the question.</comments>
          <description>We're witnessing the final generation of people who translate ideas into code by hand.</description>
          <content:encoded><![CDATA[
I quit my job at Amazon in May to join a startup called [Icon](https://icon.com). Best career decision I ever made, but not for the reasons you might think.

At Amazon, I was on the [Amazon Q Developer](https://aws.amazon.com/q/developer/) team, building their AI coding assistant. You'd think being at the center of Amazon's AI developer tools would be exciting, but it was actually deeply frustrating. It was apparent to anyone outside the Amazon bubble that we were losing the AI game badly. The leadership was constantly playing catch-up because there was very little true product vision. They kept saying they wanted to move like a startup, but then had the risk tolerance of IBM.

Everything took forever. AppSec reviews, design doc reviews, architectural review boards. By the time we shipped anything, companies like [Cursor](https://cursor.com) and [Anthropic](https://www.anthropic.com/) had already iterated through ten versions. We'd spend months debating whether a feature was safe enough to release while our competitors were shipping weekly updates based on actual user feedback.

What really struck me was how Amazon's product decisions were driven by internal KPIs rather than user empathy. The most obvious example was authentication. GitHub auth is the standard for developer tools because it removes friction for the exact audience you're trying to serve. But Amazon insisted on funneling users through [Builder ID](https://docs.aws.amazon.com/signin/latest/userguide/sign-in-aws_builder_id.html), their own auth system. From an internal metrics perspective, it probably looked great (more Builder ID signups!). From a user perspective, it was just another barrier to trying the product. I watched potential users bounce off that requirement constantly.

I felt like I was reaching the ceiling of what I could learn about AI and building good products within Amazon's constraints. That's why I joined Icon. At Icon, we move at a completely different speed. We ship features in days that would have taken Amazon months to approve.

But that's not the interesting part. The interesting part is watching how my teammates work. One of them hasn't looked at actual code in weeks. Instead, he writes design documents in plain English and trusts AI to handle the implementation. When something needs fixing, he edits the document, not the code.

It made me realize something profound: we're living through the end of an era where humans translate ideas into code by hand. Within a few years, that skill will be as relevant as knowing how to shoe a horse.

## What I'm Seeing Right Now

My teammate has six [Claude Code](https://www.anthropic.com/claude-code) terminal windows open at once, each one handling a different task or feature. He literally speaks to them one by one using [Whispr Flow](https://wisprflow.ai/), and they all execute in parallel. Most of his day is spent reviewing design documents and looking at the actual web app to see the changes being made in real time. Only in very rare cases does he actually dive into the code to debug something.

This developer isn't becoming less valuable. If anything, he's becoming more valuable because he can focus on the hard problems that actually matter. Now I see him spending most of his time doing what product managers traditionally do: talking to users, understanding their problems deeply, figuring out what's actually worth building. Coding has become maybe 20% of his job, and even that 20% is mostly about understanding requirements and translating them into clear specifications. The actual implementation work that used to consume 80% of his time is now handled by machines.

The only bottleneck is model speed and quality. But with billions of dollars pouring into generative AI every year, we will see instant voice-to-code capabilities + bug-free quality in 2-5 years.

The code itself has become an implementation detail, like the electrical wiring behind your drywall. You know it's there, you trust that it works, but you don't think about it unless something breaks. And increasingly, nothing breaks.

That will change everything about how products get made and who gets to make them.


## The Split I'm Watching

Something interesting is happening on our team right now, and I think it's a preview of how the entire industry will divide over the next few years.

There are two camps emerging, and the difference isn't really about skill level or experience. It's about fundamental attitudes toward what programming should be.

On one side, we have what I call the experimenters. These are people who spend their lunch breaks trying out new AI coding tools, setting up workflows that generate entire features from voice commands, and constantly pushing the boundaries of how little manual coding they can get away with. To traditionalists, they might look lazy. They're always looking for shortcuts, always asking "can AI do this for me?" instead of just buckling down and writing the code themselves.

But here's what I've realized watching them: they're not lazy. They're just following the natural path that technology has always followed. Every major advancement in programming has been about abstracting away complexity so humans can focus on higher-level problems. We moved from machine code to assembly to high-level languages to frameworks to libraries. Each step made things "easier" and each step had people complaining that developers were getting soft.

These experimenters understand something fundamental: laziness wins in technology. The person who finds a way to accomplish the same result with less effort doesn't just make their own life better. They often discover the path that everyone else will eventually follow.

On the other side, we have the guardians. These are people who believe deeply that understanding code at a fundamental level is non-negotiable. They can spot inefficient algorithms, they know why certain design patterns exist, they understand the underlying systems well enough to debug problems that AI tools can't handle. They see the experimenters as shortcuts artists who are building on shaky foundations.

And honestly? They're not wrong. When the AI-generated code breaks in subtle ways, when performance becomes an issue, when edge cases emerge that the AI didn't anticipate, these are the people who can actually fix it. They have a depth of understanding that the experimenters often lack.

But here's what I think the guardians are missing: the world is changing faster than their gatekeeping can keep up with. The bar for "good enough" code keeps dropping while the bar for understanding users and building valuable products keeps rising. A slightly inefficient implementation that ships next week is often better than a perfectly optimized implementation that ships next month.

I watch these two groups work on the same problems, and it's fascinating. The experimenters ship faster, iterate more, and often end up with products that users prefer (even if the underlying code makes the guardians cringe). The guardians build more robust, maintainable systems, but they sometimes spend so much time perfecting the implementation that they miss opportunities to learn what users actually want.

Neither approach is completely right, but I have a prediction about which one wins in the long run. Technology trends toward convenience and abstraction. The tools get better, the AI gets smarter, and the "shortcuts" that look like cheating today become standard practice tomorrow.

The experimenters aren't just being lazy. They're adapting to a world where the bottleneck isn't code quality. It's everything else.

## The Great Commoditization

The entire game changes from "can we build this?" to "should we build this?" and "how do we get people to use it?"

Anyone can learn to make chocolate. The ingredients are commoditized. The manufacturing process is well-understood. You can literally buy chocolate-making equipment on Amazon and start a brand tomorrow.

But look at who wins in the chocolate industry. It's not the people with the best manufacturing processes. It's Hershey's, Cadbury, Lindt. These are brands that figured out distribution, marketing, and customer psychology decades ago. The product quality matters, but it's table stakes. What matters is whether people know your brand exists and trust it enough to buy it.

Software is heading exactly the same direction. The gap between software products and consumer goods is shrinking every month. Both compete on branding, distribution, and understanding customer psychology rather than pure functionality.

I can already imagine (and I bet someone is building this right now) AI that can clone any app from a URL. You feed it a competitor's website or app store listing, and it spits out a functionally identical product in minutes. When that happens, and it will happen soon, the product itself becomes completely commoditized. Success depends entirely on whether you can market and distribute better than the original.

## What Actually Survives

Three things become incredibly valuable when technical implementation gets commoditized.

First is understanding what people actually need. Not what they say they need in surveys or focus groups, but what they'll actually pay for and use every day. This is harder than it sounds. I've seen brilliant product managers get this wrong constantly. It requires talking to users, watching how they actually behave, understanding the gap between stated preferences and revealed preferences. It's part psychology, part anthropology, part business intuition.

Second is knowing what to build and what not to build. This is taste, but it's also strategy. Understanding which features will create real value versus which will just add complexity. Recognizing when a product is good enough versus when it needs more polish. Seeing the difference between a feature users will try once and a feature they'll use every day. Most people are terrible at this. They either build everything anyone suggests or they build nothing because they can't decide what's important.

Third is getting products in front of the right people and convincing them to care. Distribution and marketing, but also positioning, timing, and understanding customer psychology. Building trust and brand recognition. Creating word-of-mouth growth. Understanding how people discover new products and what motivates them to switch from existing solutions.

These skills don't get automated away. If anything, they become more valuable as technical implementation becomes commoditized. Because when everyone can build software, **the winners are the people who understand humans**.

## What This Means If You're Starting Out

If you're learning to code today, please don't stop. But don't make coding your only skill. The developers who thrive in this new world will be the ones who understand users, markets, and business models as well as they understand technology.

Spend time talking to people who use software. Not other developers but actual users. Learn what frustrates them about existing products. Understand how they discover new tools and what convinces them to adopt something new.

Study successful products in industries you care about. Not just their features, but their go-to-market strategies. How did they get their first thousand users? How do they retain customers? What makes people recommend them to friends?

Practice communicating complex ideas simply. The most valuable skill in an AI-assisted world might be the ability to translate fuzzy human problems into clear, implementable specifications.

## What This Means If You're Already Building

If you're already a developer or building a company, remember that your technical implementation will soon be replicable by anyone with access to good AI tools. Your competitive advantage needs to be something else.

Better user understanding. Stronger distribution channels. Clearer market positioning. Faster learning cycles. Better taste in what to build. Superior execution on the parts that can't be automated: talking to customers, understanding their problems, iterating based on feedback.

Start making this shift now while you still have time. If you're a senior developer, spend more time with your product team. Sit in on user interviews. Understand the business metrics that actually matter. Learn why certain features get prioritized and others don't.

If you're leading a team, stop hiring purely for coding skills. Look for people who can think about systems holistically, who can communicate clearly with non-technical stakeholders, who have strong opinions about user experience. The developers who thrive will be the ones who can bridge technical possibilities with business needs.

The transition is already happening. The question is whether you'll adapt proactively or get caught off guard when your current skills become less relevant.

## The Last Generation

We're the last generation of people who translate ideas into code by hand. Our children will describe what they want and watch it appear on screen, the same way we describe what we want to search engines and watch results appear.

They'll judge us the way we judge people who manually calculated ledgers before spreadsheets existed. Impressive dedication to craft, but ultimately unnecessary effort spent on problems that got solved by better tools.

The question isn't whether this future arrives. Looking at the money and talent flowing into AI development, it's inevitable. The question is whether you'll be ready when it does, and whether you'll be working on the parts of product development that actually matter in that world.

The parts that have always mattered, really. Understanding people. Building things they want. Getting those things in front of them. Everything else was just implementation details.
]]></content:encoded>
        </item><item>
          <title>Year 2023 Reflection: First Start-Up</title>
          <link>https://xipu.li/posts/year-2023-reflection</link>
          <guid>https://xipu.li/posts/year-2023-reflection</guid>
          <pubDate>2024-01-21</pubDate>
          <media:content medium="image" url="https://xipu.li//images/2023-reflection/arrow.jpeg" />
          <comments>EthDenver 2023</comments>
          <description>Bought and sold a car, started a company, and one-year anniversary with my girlfriend.</description>
          <content:encoded><![CDATA[
A crazy amount of events had happened, let's skip the intro.

## March - Arrow Meetup
As a member of [Arrow Air](https://arrowair.com/), I went to Denver, CO for a large event:
[ETHDenver](https://ethdenver.com/). It's the first time that Arrow's active contributors have met
offline. We got errrks.eth from Alaska, A.M. Smith from San Diego, CA,
Thomas and WhiteDadJokes from Texas, sleety from UK, alperenag from
Turkey, and deetwo from a mysterious place.


We stayed at an Airbnb and got our Arrow swags (see pic above). During
the event, we glad to see that more females were participating what it
used to be a male-dominated industry and that there was a significant
presence of orgs building for public goods.


It was exciting as we finally got to match the Discord usernames with
real faces. I only stayed for 3 days as I had to head back for school.

## April - First Car

### Driver's License

When I was in New York City, I failed my road test. Manhattan was known
for its difficult road conditions and the strict road tests. I
completely butchered the parallel parking by not had parked in perfect
parallel with the curb.

By contrast, California is way more lenient. I passed the road test in
one go. There was no parallel parking at all!


I got my driver;s license primarily for ID purposes.  However, thinking
that I'd be commuting long-distance [from San Francisco to Sunnyvale](https://www.google.com/maps/dir/San+Francisco,+CA/Sunnyvale,+CA/@37.5530596,-122.5597597,10z/data=!3m1!4b1!4m14!4m13!1m5!1m1!1s0x80859a6d00690021:0x4a501367f076adff!2m2!1d-122.4194155!2d37.7749295!1m5!1m1!1s0x808fb645a9d05d3b:0x768dfb26dd7cc3a2!2m2!1d-122.0363496!2d37.36883!3e0?entry=ttu) for
my Amazon internship, and it appeared that life could be more
convenient, I decided to buy a car.


### Shop for a Cheap Car

Now, here came the most excruciating shopping experience. There were so
many models, builds, configurations. I had to make so many decisions
regarding comfort, budget, fuel economics, etc.

First, the budget. I assessed my financial situation and decided that
$30k was my ceiling. Then, the brands. I heard many good things about
Japanese cars like Toyota and Honda, about how long-lasting,
low-maintenance and fuel efficient they were.

Except that none of them fit my budget.

I thought Japanese cars would be cheap, but that's not the case for the
Bay Area. I figured that it was probably because everybody wanted them,
so the law of supply-and-demand pushed up the price. What's more insane
was that used Japanese cars were more expensive than the new ones! This
was because there's a shortage and many had to wait for months to get a
new car.


I went to a Toyota dealership and test-drove the only new car left in
inventory: a Toyota Corolla. I was quite confused as to why it's so
in-demand because it was a terrible driving experience. Me who just
suffered from a back injury couldn't stand the thought of driving in
that plastic box for 2+ hours a day for my internship.


### Shop for a Cheaper Car

After some research, I went to a BMW dealership. I always thought that
cars like BMW were out-of-touch. Surprisingly, the used ones were pretty
cheap — way cheaper than the Japanese cars that ironically had a
reputation for being cheap.

I got my eyes on a 2020 X1. It's a black SUV with premium package: [HUD](https://www.google.com/search?q=bmw+hud+x1+2020&tbm=isch&ved=2ahUKEwj-nbmAtseDAxVJPEQIHbpVC3MQ2-cCegQIABAA&oq=bmw+hud+x1+2020&gs_lcp=CgNpbWcQAzoECCMQJzoGCAAQCBAeUOcEWL4MYP0NaABwAHgAgAGSAYgBkwSSAQM1LjGYAQCgAQGqAQtnd3Mtd2l6LWltZ8ABAQ&sclient=img&ei=dZOYZb6PKcn4kPIPuqutmAc&bih=702&biw=1440#imgrc=Lvk-YKsERcv_VM),
heated leather seats, etc. with a 40k mileage for $27k. I test drove it.
It was a 10x experience for someone who just test drove a Toyota.

I felt like I was driving a spaceship: the controlling was so smooth,
and the HUD was so futuristic (even though, now I knew X1 was actually
the lowest tier). I immediately proceeded to the purchase process.
However, they weren't able to offer me a loan due to my visa status and
the next day when I decided to pay upfront, the car was sold to someone
else.


Back to the search. This time, a friend of mine took me to a Mercedes
dealership to test drove a 2020 C300. It's a sedan that didn't have HUD
but the interior was quite ahead of its time. I was exhausted from the
shopping process so I decided to just go with it.


It was retailing for $30k, and I bought a maintenance plan and warranty
with it, bringing total price to $40k. It's above my budget but I was
able to get a loan from Mercedes and was told that the maintenance plan
and warranty can be sold back to the dealership.

<BlogImg
  src="/images/2023-reflection/car.png"
  alt="My car"
  width={120}
  height={70}
  objectFit="cover"
  caption="I took my new whip through a winter storm to Tahoe"
/>

### Regrets and Opportunities

Once my excitement receded, I felt stressed. I ignored other costs came
with the car: insurance, the sky-high fuel price (I had to use the
premium gas, which was around $6/gal at that time), penalties for
parking at the wrong places or at the wrong times, and most importantly,
my health.

I realized that my typical day had become either sitting in the car or
sitting in the office or sitting at home. Fatigue and lower-back pain
soon became daily.

It was a huge relief after I sold the car after 6 months. In total, I
spent $17k on the car, which was equivalent to $90 a day. 

It wasn't the best financial decision but I got to explore the Bay Area:


<BlogImg
  src="/images/2023-reflection/alviso.jpg"
  alt="Alviso Marina County Park"
  width={120}
  height={70}
  objectFit="cover"
  caption="Alviso Marina County Park"
/>
<BlogImg
  src="/images/2023-reflection/mori.jpeg"
  alt="Mori Point"
  width={120}
  height={70}
  objectFit="cover"
  caption="Mori Point"
/>

… and Taylor Swift's Era's Tour in Santa Clara.

<BlogImg
  src="/images/2023-reflection/ts.jpeg"
  alt="Taylor Swift Era's Tour in Santa Clara"
  width={120}
  height={70}
  objectFit="cover"
  caption="Taylor Swift Era's Tour in Santa Clara. We were pretty far away from the stage."
/>

Beyond fun and sceneries, my car also changed my life trajectory. 


## May - Cofounder

2023 was the year when generative AI took off. There were plenty of
hackathons going on in San Francisco. Having a car allowed me to
participate in a Microsoft sponsored hackathon: AISF.


I was building an AI motivational speech app during the three-day long
hackathon. And in the last day, I was selected to demo the product.
That's when I met [Eugene
Yao](https://www.linkedin.com/in/eugene-yao-nz/), who was working on a
AI guided meditation app.

He approached me because he wanted to do something in the wellness
space, and my hackathon project resonated with him. Eugene felt that we
shared the same passion and was searching for someone technical to build
something big.

<BlogImg
  src="/images/2023-reflection/aisf.jpg"
  alt="AISF Hackathon"
  width={120}
  height={70}
  objectFit="cover"
  caption="AISF Hackathon"
/>

So, we decided to work on my AI motivational speech app during the
summer when he was in New Zealand and I was doing my Amazon internship. 

The “trial” period went well for both of us, and we decided to official
form a cofounder relationship to build something useful. More on that
later.


## June - Aug: Amazon Internship

### Luck

I got very lucky with this internship.

One year prior, I applied to the summer internship program as soon as it opened because I was panicking that the tech industry was experiencing layoffs. And as soon as I got Amazon's email for an online assessment, I started feverishly study all the past Amazon coding problems leaked online, and was doing LeetCode all day long.

I was lucky that the online assessment consisted of the same exact problems that I already practiced. So I was invited for the final round with an engineer.

I was lucky that the interviewer did not ask me any algorithm questions that were commonly expected. Instead, he just asked me something so easy that my answer "just use a [hashmap](https://www.reddit.com/r/learnprogramming/comments/1rljsu/java_eli5_hashmaps_how_are_they_used/)" was sufficient. 

Another friend of mine who also got an offer from Amazon told me that he was asked a dynamic programming ("hell”) question. His interview was scheduled only one month after mine. Early birds do eat worms.

### What I did

I was assigned to a confidential project that's related to building a new product related to FireTV. When I joined, the codebase was new and small. Everything was easy to understand and teammates were still figuring out basic things like code structures.

It was a fullstack project, meaning I was responsible for building the user interface as well as the backend and for connecting the two. It wasn't difficult but as a large company, a considerable amount of time was spent on documentation and code styles.

I went through very robust code reviews to ensure that my code can be
used in the real world. At the end of the internship, my codes were
merged into the production codebase.

### Learnings

However, I was appalled by the excessive processes and reviews for a new
project. It appeared that big companies were shooting themselves in the
foot by being big. [It was near impossible to push new features/products
to the world without getting through layers of approvals, comments,
politics, etc](https://pravse.medium.com/the-maze-is-in-the-mouse-980c57cfd61a). 

An ocean of “[nits](https://www.codelantis.com/blog/code-review-acronyms-lgtm-nit)” on my projects was more than enough for me to remember never to build a company that ends up like today's big techs. The problem was from ill-conceived KPIs that prompted employees to pump out zero value work for the sake of keeping their job or for climbing up the corporate ladder.

If I were to restructure the company, I would get rid of the ladder
itself: a super flat org structure that compensate managerial and “do”
positions equally. The more layers between an intern to the CEO, the
closer a company to become IBM.


## Sep: One-Year Anniversary

I fell in love in Sep, 2022 with my girlfriend, Nataliya. It was my first romantic relationship and it had been a very rewarding journey.

### Rediscover Myself

It was a bumpy ride. We fought many nasty fights. We pushed and pulled each other. But overall, we both learned something and improved our selves.

I wasn't aware of many flaws in the way I interacted with other people, and this relationship made me see those flaws sharp and clear.

For example, I wasn't aware that the way I said things had unwanted effects. My sarcasms were often interpreted as serious criticisms. No one would point out these problems but Nat did a great job of making me see it and correct the course.

Living together meant that I was finally able to acknowledge and tolerate different, if not opposing, individualities. It made my heart bigger, my temper tamer, and patience more. One interesting note, I reduced my caffeine consumption after finding out that I tended to get more anxious and easily annoyed after drinking coffee. 

### Women

Spending intimate time with a girl made me see how our world had made it difficult for women to succeed. There's period, which many places still considered a taboo topic. It's painful and the hormonal effects lasted weeks. The corporate world still refused to accommodate this biological bane. Making it worse, over-progressive western society perceived period leave as a sign of weakness and, ironically, sexist (“Women are not weak. We can still work while on period so we don't need special treatments”).

It's relieving to see countries like India were making period leave into legislation. I hoped to see more countries do the same sooner.

### Personality

One activity we enjoyed was to identify tech bros on the street. “Tech bro” was a personality, or the lack of it. San Francisco was the HQ of tech bros because here, the lack of personality and extreme minimalism were celebrated as must-haves for those who aspired to change the world.

The Bay Area had a different vibe. Coming from Manhattan, one word to describe Silicon Valley was “dead”. Everyone's weekend activity was hiking, if not coding. This and the spread-out landscape gave me an intense [ennui](https://www.google.com/search?q=ennui+meaning&oq=ennui&gs_lcrp=EgZjaHJvbWUqCAgAEEUYOBg7MggIABBFGDgYOzIOCAEQRRgnGDkYgAQYigUyBwgCEAAYgAQyBwgDEAAYgAQyBwgEEAAYgAQyBwgFEAAYgAQyCggGEAAYsQMYgAQyBwgHEAAYgAQyBwgIEAAYgAQyBwgJEAAYgATSAQgxMTQ0ajFqN6gCALACAA&sourceid=chrome&ie=UTF-8) (I've gotten used to it now, and found joy in my weekly bakery trip to [Arizmendi](https://arizmendibakery.com/)).

I'd been to multiple “tech parties” in SF and found it a common sight of two people staring at each other in silence for minutes. Everyone wanted to build startups but many should build themselves first.

I was a borderline tech bro, too. My entire wardrobe could fit one small luggage and you could only find black, gray, and white. Thanks to Nat, I reclaimed my personality. Now I [dressed like a Gen-Z](https://www.google.com/search?sca_esv=596298580&sxsrf=AM9HkKmdZgoX10xgeuWTeWTkoCJw2yEwaQ:1704602234689&q=gen-z+fashion+men&tbm=isch&source=lnms&sa=X&ved=2ahUKEwiR-bmVusqDAxX0J0QIHXY0CYMQ0pQJegQIDRAB&biw=1440&bih=702&dpr=2).

Many would argue that a lack of personality was the sacrifice needed to change the world. But they failed to understand that the world is made up with people. Tech bros who actually ended up changing the world did not bring any positive value or beauty but only toxicity (Facebook, Web3, Metaverse, etc. The only exception I could think of was Google). 

To change the world is to dream big while not losing touch with reality.


## Sep - Now: My First Startup

Eugene and I started working on the motivational speech app during the summer. However, that direction didn't seem to be too great as AI voice generation had its limit and we were not sure the product met a real world problem.

So, we went back to square one and started problem discovery. This was a missing step for many of my side projects. I was, like many tech bros, excited to build something that sounded cool but no one wanted to use.

Eugene, having founded a startup, saved us many unnecessary mistakes. We stopped jumping into coding and was meeting daily to clarify problems that were relatable to ourselves and that we're passionate about solving.

### First Attempt

We found that many people suffer from procrastination, which led to stress and overwhelm when deadlines drew nigh. Initially, we thought a solution was to break down big tasks into manageable chunks.

This was a well-researched technique called “microtasking”. With the
rise of generative AI, we thought that it's a good timing to work on
microstasking. Plus, an AI product would be easier to get funded.

<BlogImg
  src="/images/2023-reflection/buildspace.jpeg"
  alt="buildspace goal"
  width={120}
  height={70}
  objectFit="cover"
  caption="Our buildspace goal"
/>

Our product asked users to input their tasks, choose a duration, and add
additional context, then GPT would spit out a todo list of small steps
that would lead users to complete their tasks.

People liked the UI/UX but we quickly found out intensive editing was
needed to modified the AI generated list. No matter how we prompted the
AI, we couldn't make it consistently output high quality and accurate
lists.

The lack of control over the AI eventually led us to pivot away from AI.
The most valuable feature from the product was the editor. So, we
decided to make it a non-AI product.

### The Story about Forget
The idea was simple. You wrote down your daily todo items on the list, then you could enter the “focus mode” with a click of a button which would display the current task with a visual banner that expanded with the progress of time.

We also discovered a way to have Chrome popping out of a window that always stays on your screen. This addressed the “out of sight, out of mind” problem ubiquitous to people with ADHD — who happened to be our target user group.

We made mistakes of jumping ahead of ourselves by wanting to build out more features that sounded cool, scalable, or theoretically would bootstrap network effect. The result was a low retention.

Currently, the product was called “Forget” to make it sound less toxic as a productivity tool and more consumer friendly. In the early days, we'd do Reddit launches to share the tool as a way to acquire users. 

However, this was not a scalable strategy and our product didn't have
any moat. Toward the end of the year, Eugene started creating short-form
videos on social media platforms. And now we're seeing this investment
paying off: 1) his Instagram follower counts were growing quickly to
almost 100k and 2) about 30+ new sign-ups to the product everyday.


As we gained more users, I got more and more product feedback. People
wanted all sorts of things. But this was the real danger. If we didn't
have a strong filter to say no to many of the feedback, our product
would look like something we tried not to be: yet another business
productivity tool with cluttered UI and overloaded features.


The product had to be attractive. This was the core of our product
strategy. Design was a first-class citizen that triumph over other
factors whenever there's a conflict. Our thesis was that a beautiful UI
would earn us some free passes to compensate for the stuff we
compromised. This was also true in the real world (just think about the
dating).


### Onward

As of writing, we're preparing to raise a pre-seed round. With the current MVP, we have validated the market and are ready for building out a more refined product. So, I will be spending less time on coding, more on designing and innovating. Eventually, we'd like to have some experienced developers to build out a robust product.

Closing with Scott Gallaway's sign-off: life is so rich. ]]></content:encoded>
        </item><item>
          <title>Year 2025 Reflection: The Generational Scam</title>
          <link>https://xipu.li/posts/year-2025-reflection</link>
          <guid>https://xipu.li/posts/year-2025-reflection</guid>
          <pubDate>2026-02-08</pubDate>
          <media:content medium="image" url="https://xipu.li//images/2025-reflection/last-day-at-icon.jpeg" />
          <comments>Last day at Icon</comments>
          <description>Moved to New York City. An imploded startup. Humans getting ruled by AI.</description>
          <content:encoded><![CDATA[
Twelve months ago, I landed in Seattle with an "ambition": work hard to get promoted to L5 for my new grad job at AWS.

Today I'm in New York, working at a start during the day and running an e-commerce business at night that just shipped a product to DJ Zedd.

In between: I got scammed out of $6,000+, survived the most toxic startup implosion I've ever witnessed, and learned that money is very, very real.

## Amazon

When I landed the role at Amazon Q, the generative AI division, I thought I'd won the lottery. This was the hottest technology of the century, and I was going to be building it at one of the most powerful companies on Earth.

That fantasy lasted about a week.

Amazon is world-class at moving boxes, but they are not world-class at building products. And the gap between the two is enormous when you're trying to compete in a market that moves as fast as AI.

My team had been a YC startup before Amazon acquired them. They'd built something like Claude Code, AI in the command line, made for developers. It was lean and fast and opinionated, the kind of product that only exists when a small team has complete ownership and zero bureaucracy. 

Amazon fixed that. The first order of business post-acquisition was to rip out GitHub authentication and force users through the AWS console. They took a product that developers loved and made it feel like filing taxes.

I worked on the subscriptions team, which was its own special disaster. AWS had never built a subscription product before, so instead of integrating Stripe like every other company on the planet, we built our own version from scratch. The requirements changed weekly, sometimes daily, and the full weight of big-tech process bore down on everything we did. The result was a payment system powered by mountains of bad code, integration tests, tests for the integration tests, and somehow it still broke every month. The ultimate solution was to have engineers manually process refunds. That was the system. The cheap L4s were the system.

What really broke my brain was watching how incentives actually played out at a company like this. Engineering teams were understaffed while product teams were under pressure to ship something, anything, that leadership could put on a slide. So corners got cut but never the corners you'd expect.

I inherited a project after everyone else quit: an automated email system to remind customers to activate their subscriptions. Simple enough, and the business logic made sense. We didn't charge until customers started using the product, so there was real money in getting people to activate faster. But the leadership wanted it shipped yesterday. The interim PM used ChatGPT to translate our emails into foreign languages instead of going through the internal localization team, the people who actually understand cultural nuance and legal liability and the difference between "friendly reminder" and "we're watching you" in Japanese.

When we rolled out to our biggest region, the complaints started pouring in. Enterprise customers saying they never consented to receive these emails. And the thing about emails is that you can't unsend them. It's a one-way door, and we'd already walked through it.

The irony was suffocating. We had processes for everything. Design reviews, security reviews, seventeen approvals to change a button color. But for customer-facing communications that could create legal exposure? Move fast, ship it, figure it out later.

Code reviews barely existed because senior engineers were stretched across so many projects that they'd approve pull requests without really reading them. Who had time? Everyone was underwater.

And then there was the politics. Most of our users were internal Amazon engineers who couldn't use Claude Code or other third-party tools due to privacy concerns, so they used our product instead. Which meant principal engineers, people with titles that commanded automatic deference, would sometimes just build features they personally wanted. They'd vibe-code something over a weekend and open a PR to merge it into production.

I watched talented engineers leave, one by one. Each resignation meant their on-call shifts got redistributed to whoever remained, and within a few months I found myself on three different teams' schedules. I was getting paged at 3 AM for systems I'd never touched, debugging code I didn't write, fixing problems that shouldn't have existed in the first place. And it wasn't just real emergencies. Our outsourced customer experience team in India had access to the on-call tag, and they'd use it to ping the entire engineering team at 2 AM for things like "can you guys take a look at this customer refund request?" Not a system outage. Not a security breach. A refund. Everyone's phones screamed in the middle of the night because someone didn't know—or didn't care—what "on-call" actually meant.

One night, after yet another 2 AM page for something that could have waited until morning, I texted Kevin.

Kevin was someone I'd worked with briefly at a previous startup. He'd been trying to recruit me to Icon, a generative AI ad startup in New York that had recently gone viral on the internet. A few months earlier, when he first reached out, I'd turned him down. I was committed to the Amazon path. I was going to grind it out, get the promotion, do things the right way.

But that was before I ended up on three on-call rotations. Before I calculated my effective hourly rate. Before I realized I was killing myself for a company that couldn't decide what it was building.

"Are you guys still hiring?"

The next day, I was on a plane to JFK. Three days later, after a work trial, I had an offer. I signed it that same night, before I could talk myself out of it. Two weeks notice at Amazon, sold my furniture, packed everything I owned into suitcases. Seattle to New York, just like that.



## The Generational Scam


Sometimes the beginning sets the tone for the rest of the story.

Before I even set foot in New York, I got scammed out of $6,000.

Finding an apartment in the city is its own kind of warfare, especially when you're doing it remotely with two weeks to figure everything out. I found a listing on Xiaohongshu—a Chinese social app that's become a shadow real estate market for people who don't trust Craigslist. The apartment looked perfect. Good price, great location, available immediately. I wired the deposit and first month's rent.

The apartment didn't exist. The landlord didn't exist. The whole thing was a fiction, built just well enough to catch someone who was desperate and moving fast.

I hadn't even started my new job yet, and I was already down six grand. Welcome to New York.

That was the first scam. The second one paid a salary.

The pitch the CEO gave me was intoxicating. He walked me through the numbers: the ARR, the growth trajectory, the vision. He glossed over the 70% churn rate like it was a minor detail. "Generational wealth" was the broad stroke that made everything else disappear. Who cares about churn when you're going to be rich? Who needs work-life balance when you're building the future? It's a magic phrase that turned red flags into minor details and exploitation into opportunity.

I didn't know how equity worked back then. Not really. I understood the concept—you get a percentage of the company, the company gets big, you get rich—but I didn't understand liquidation preferences, or dilution, or how a Series A can wipe out early employees while making founders and investors whole. I didn't know what questions to ask, and they weren't volunteering the answers. It wasn't until much later that I realized how badly I'd been lowballed.

But at the moment, none of that mattered. The founder had a story that was impossible to ignore. He was a 2x founder. His previous company had actually reached product-market fit, but he'd walked away because the market was too small. This time, he said, he was shooting for the moon. And the investors believed him with A-list names like Founders Fund had written checks.

With a halo like that, my initial suspicions felt small and paranoid. This guy doesn't believe in talking to customers? He's against A/B testing? He rejects basically every conventional method of building a product? I dismissed it all. He's a second-time founder with serious backers. He knows what he's doing.

The requirements came top-down, straight from his head, delivered as edicts rather than hypotheses. We'd later find out most of them came from ChatGPT.

But in the beginning, things were okay. The schedule was brutal—seven days a week, mandatory in-person—but I was young and bought into the narrative. Generational wealth. This is what it takes. Food was expensed, rent was subsidized, and I lived in K-Town, where there's a constant flow of high energy day and night. The neon signs and the late-night Korean BBQ spots made it easy to forget that I hadn't had a day off in weeks.

For a few months, I was even happy. I was designing experiments, watching metrics move, feeling like I was building something real. Fast feedback loops. Actual ownership. After the bureaucratic suffocation of Amazon, it felt like freedom.

Most of what I worked on was finding new ways to extract money from customers. Upsells everywhere. Flows designed to deter cancellation, or better yet, trick people into upgrading while they were trying to leave. When customers complained, the response was always the same: "Doesn't move the needle."

The needle. I heard about that needle constantly. I never got a clear answer on what the needle actually was, or how big it was, or what would happen when we finally moved it. But I do know this: when we pivoted to managed services, leadership called it "moving the needle." So apparently the needle was pointing at "become an ad agency" this whole time. 

Instead of charging $39 a month for self-serve software, we'd charge $1,000 or more to make ads manually for clients. Engineers went from being the core of the company to a support function, building internal tools for operators instead of products for users. The interesting work disappeared. But the working condition worsened with mandatory stand-ups added to the weekends, as if seven days a week wasn't enough without also having to justify your existence.

Seven days a week stopped feeling like dedication. It started feeling like a scam.

## The implosion
The first sign of this was the morale degradation. Most engineers no longer work inside of the office. We’d rather go to other parts of the WeWork than getting crammed in a room where the leadership constantly talks about 180-degree changes, how to upsell etc.

This was disheartening to me because a big part of why I signed up for this job was because engineers used to be in the room, trolling each other, crack jokes. Now, work felt like... work.

The last straw was one of our best engineers resigned. People started searching for new jobs. THe CEO sensed this, so he gathered the entire team on a beautiful afternoon in New York, , the kind of day that makes you briefly forgive the city for everything it puts you through, and walked us to Madison Square Park. We sat on benches, confused, waiting for whatever was coming.

He pulled out his phone and started reading.
The speech was written by ChatGPT. He talked about the company's journey, about challenges, about needing people who were truly committed. The irony of an AI startup founder reading an AI-generated pep talk to convince us to stay was almost too perfect.

Then he got to the point: he knew some of us were thinking about leaving. He wanted us to take the rest of the day off and really reflect on whether we wanted to be here.

We dispersed. Some people went home. A few of us went to dinner, trying to process what had just happened, debating what to do next. We talked for hours, going in circles, none of us sure whether to stay or go.

When we got back to the office that night to grab our things, we didn't expect him to still be there.

He was.

The moment we walked in, the air changed. Nobody knew what to say. The silence was thick and uncomfortable, the kind of quiet that feels louder than noise. We avoided eye contact, stared at our phones, shuffled toward our desks without speaking.

The engineer who'd resigned broke the silence. He looked at the CEO and said, almost casually, "Good luck rebuilding your team."

Something shifted in that moment. I could see it in the CEO's face, a kind of hardening. Whatever off-ramp he might have been considering closed off right then.

That night, every engineer got terminated.

The next morning, my phone rang. It was the CEO.

"Why wouldn't you look at me?"

That was his opening line. He wanted to understand why nobody had made eye contact with him the night before. He wanted to know if there was something he could fix. And buried underneath all of that, he wanted to offer me my job back.

I listened, trying to reconcile the person on the phone with the person who had fired his entire engineering team twelve hours earlier because the vibes felt off. This was a man who had raised millions of dollars, who gave speeches about building the future, who demanded seven days a week from his employees in service of his vision. And he blew it all up because people were awkward during an awkward moment.

Some people build companies. Others build monuments to their own insecurity. It's worth learning how to tell the difference before you sign the offer letter.

## The aftermath

Word travels fast in the Valley.

Within two days, my phone wouldn't stop buzzing. Recruiters, founders, investors who wanted to make introductions. I booked thirty interviews for the following week without sending a single application. For the first time in my career, opportunities were chasing me.

It was disorienting. I'd spent years operating from the other side of the table, the side where you send out applications and hope someone notices, where you practice interview questions and try to prove you're worth taking a chance on. Suddenly I had leverage, and everything felt different. Conversations were easier. Negotiations were easier. People returned my DMs.

The experience rewired how I think about careers. The goal is to never have to apply. Build something valuable, whether that's a skill, a reputation, a body of work, or even just a good story. Get good at telling people about it. High-quality opportunities find you when you're worth finding. Casting a wide net and hoping for the best is what you do when you have nothing else going for you.

I don't want to be in that position again.

## I miss the flow state

I used to put on my favorite music, disappear into the code, and spend hours crafting something by hand. Watching changes appear on localhost:3000. Losing track of time because I was so deep in the work that time stopped mattering.

That feeling is getting rare.

Now I command six terminal windows running Claude Code simultaneously. Admittedly, a lot gets done. But I've become an air traffic controller instead of an artist. I'm directing traffic, not crafting anything. The work happens around me, not through me.

We're on a treadmill now, and the treadmill only goes faster. It's increasingly about the result rather than the journey. Ship more. Ship faster. Nobody asks if you enjoyed building it.

The strangest part is how my own expectations have shifted. With [OpenClaw](openclaw.ai), I don't even want to write prompts or provide context anymore. I catch myself wishing the AI could just read my Slack, understand what needs to happen, test the app in the browser, and figure it out on its own. I want to remove myself from the loop entirely.

Will people be happier in a post-AGI world? When all the challenges that were once sources of fulfillment can be outsourced, what's left? The struggle is the point. The struggle is where meaning lives. Take that away, and what do we have?

I think about what humans should focus on when "work" can be done by machines. My guess is that most people will become tool calls, human APIs that some superintelligent system invokes when it needs something done in the physical world. A small percentage will be the ones who own the AI, direct the AI, reap the rewards of the AI. The rest will be utility functions.

It's a strange turning point in human history. And naturally, being a product of this moment, my first instinct is to wonder how I can benefit from it.

Can the activity of making money itself be outsourced? I'm already running experiments. I have a bot making bets on Kalshi. It's working so far. Not life-changing money, but enough to make me wonder what happens when the bot gets smarter and I get more comfortable letting it run.

I'm not sure if this is exciting or terrifying. Probably both.

]]></content:encoded>
        </item>
      </channel>
      </rss>