How to Find Your Next Stop

How to Find Your Next Stop

Echeruo's new venture is called Love and Magic, a startup studio that helps companies of all sizes maximize their ability to innovate.

For anyone that has an idea they have been hoping to turn into a startup, Echeruo and his collaborators just introduced the Startup School of Alchemy. It's being taught at WeWork and Princeton University. It offers a six-week curriculum designed to help aspiring entrepreneurs find product-market fit.Apply with the code "stackoverflow" and you get $1000 off the course, a 40% discount.

Echeruo says his time working in finance and with Microsoft Excel was what gave him the ability to think of how data from maps could be optimized by an algorithm and built into a useful mobile app.

For those who don't know, our co-founder and Chairmam, Joel Spolsky, was part of the team at Microsoft that built Excel. Here is legendary 2015 talk, You Suck at Excel, where he organizes a spreadsheet to keep track of what he pays his Pokemon, ahem,I mean, uh, employees.

You can take a deeper dive into the backstory of how Chinedu built HopStop below, related in his own words.

I've always had difficulty with directions. When I grew up in Nigeria, I remember getting lost in my own house. It wasn’t like it was a mansion, it was a four-bedroom house.

So you can imagine how I felt when I got to NYC and had to get around with the subway and bus system! I remember walking up once to one of those blown up maps in the subway station. My nose was a feet away from the dust laden map. The subway lines looked like tangled noodles. Complexity galore!

New Yorkers used to walk around with these pocket guides—Hagstrom maps. I was going on a date in the Lower East Side. It doesn’t have the grid like the rest of the city. I got lost and was very late getting to the bar.I can't remember how, the date went but I remember what I did first thing next morning. I walked over to the subway station, grabbed a subway MAP and laid it on the floor and tried to figure it out. There’s driving directions. But there weren’t subway directions. So I was solving my own problems.

I was looking for the complete directions—leave your house, turn left, go into this particular entrance, get on this train, get off at this station, use this exit. Because I was, in a lot of ways, the ultimate user, we ended up building a product that solved the complete problem—get me from where I am now to where I need to be.

I was non-technical, I worked for a hedge fund. I may have been thinking algorithmically, I knew that this was computationally possible. But I didn’t know how to make it a reality. In conceiving the problem, I threw all the data into spreadsheets. I interned at this company when I was in college, where I learned about spreadsheets. I found the work very tedious, but I learned how to think about data, to think in tables. It allowed me to conceptualize complexity.

To conceptualize the first subway data as a spreadsheet, I started by staring at the subway map laid on the wood floor of my apartment. The most obvious features were colors, lines, and stops. So those are the tables I typed into Excel first. Then I realized the lines also represented two train directions so I redid the spreadsheet. Then I realized the stops served multiple subway lines, so I redid the spreadsheet. Then I realized some of the stops would only be active during certain periods, so I redid the spreadsheet. We kept on learning and adjusting. It took us a long time before we had a data model that robustly described NYC's subway system. We even figured out how to automatically account for the frequent weekend NYC subway diversions.

To build the first version of the app, I went to eLance, described to these computer scientists the data set in Excel, routes, stops, exits, entrances, and I sent it in. This developer in Siberia, Russia, emailed me, came up with a solution. But he turned out to be a complete genius, he built the core of the first version of Hopstop. Here I was, a Nigerian, sitting in my apartment using messenger, email, on a laptop. And I never met Alex for four years. We built Hopstop over four years without ever meeting each other.

We ran very lean. Alex did all the coding. I did the subway data and user experience. I'd have to ride to different subway stations to note each subway entrance and exit, etc. When we added the bus system, Rajeev and his data team in India helped input the bus stops and schedules. And four years later, we were purchased by Apple, so quite the ride.

See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Tämä jakso on lisätty Podme-palveluun avoimen RSS-syötteen kautta eikä se ole Podmen omaa tuotantoa. Siksi jakso saattaa sisältää mainontaa.

Jaksot(966)

Partnerships can keep open source sustainable

Partnerships can keep open source sustainable

Ryan welcomes VoidZero’s Evan You and Cloudflare’s Dane Knecht back to the show to discuss Cloudflare’s recent acquisition of VoidZero and what it means for JavaScript development, how partnerships li...

24 Heinä 0s

The future of development is full-stack

The future of development is full-stack

Live from Snowflake Summit, Ryan talks with Snowflake’s Head of Developer Experience Umesh Unnikrishnan about the industry-wide shift from “vibe coding” for quick prototypes to agentic engineering for...

21 Heinä 0s

Developers who move fast still need to do it together

Developers who move fast still need to do it together

At MS Build, Ryan is joined by Cassidy Williams, Senior Director of Developer Advocacy at GitHub and former Stack Overflow Podcast host, to discuss how agentic coding is shifting dev work towards high...

17 Heinä 28min

Your AI is only as responsible as you are

Your AI is only as responsible as you are

Recorded at Microsoft Build, Ryan welcomes Sarah Bird, Microsoft’s Chief Product Officer for Responsible AI, about how we can build and use AI responsibly with the NIST approach, why most irresponsibl...

14 Heinä 28min

Building more than just an agent harness

Building more than just an agent harness

Live from Microsoft Build, Ryan is joined by Jay Parikh, Microsoft’s VP of AI Core, for a conversation on what enterprises need to build, deploy, and run AI agents at scale with demonstrable ROI; how ...

10 Heinä 31min

What's left for infrastructure-as-code after AI moves in?

What's left for infrastructure-as-code after AI moves in?

SPONSORED BY IBMRyan is joined by Rosemary Wang, Developer Advocate at IBM, to explore what infrastructure as code looks like once AI starts writing and deploying it. They discuss why guardrails still...

8 Heinä 30min

Agent orchestration is so two-years ago

Agent orchestration is so two-years ago

Ryan welcomes Saahil Jain, CTO of You.com, to discuss why building agents with a 2024 mindset is a mistake as modern models improve at long-horizon tasks, why heavy orchestration layers can hurt model...

7 Heinä 31min

The good, the bad, and the AI apps

The good, the bad, and the AI apps

Ryan welcomes Benny Chen, co-founder of Fireworks AI, to the show to explore what actually makes an AI application good or not, how to balance qualitative signals with quantitative metrics when evalua...

3 Heinä 25min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
psykopodiaa-podcast
mimmit-sijoittaa
rss-rahapodi
rss-inderes
rss-perho-rajoilla
rss-rahataito-podcast
rahapuhetta
rss-karon-grilli
herrasmieshakkerit
ostan-asuntoja-podcast
rss-10x-finland
rss-tarkeista-asioista-2
rss-40-ajatusta-aanesta
pomojen-suusta
sijoituspodi
hyva-paha-johtaminen
lakicast
rss-porssipuhetta
rss-pinnan-alla-kiehuu