That's usually things like caltrain / muni. But I would definitely sponsor a $300/mo waymo subscription if it was like 20 rides a month.

- CDs moving to Mp3s moving to the ipod and finally streaming

- Games moving from 8bit to early 3d graphics to where they are today

- Family computer moving to laptops and eventually to ipads

- Landlines to early cell phones to the iphone today

All of these experiences helped ground the core principals behind this technology. And the pace of these transformations (while rapid) was still something you could keep up with. Everything was built on the same principals.

But today kids go from zero to iPad + AI generated tiktoks by time they turn 2. Sure parents can try to hide the tech, but it doesn't change the fact that it's out there and available as soon as they enter school.

Maybe I'm overindexing on my childhood, but I would love to recreate some abridged history of this for my kids. I think seeing the building blocks helps build a much more healthy relationship with technology.

And let's say that work is correlated with quality. Company A wants to spend 10x less time working, while Company B works 10x more. Company B therefore has a better product than Company A, so eventually Company A goes away. The consumer still consumed the same amount, but they switched to the better product.

In the world where someone can take your cake by working 25% more hours, it's always going to happen.

I think this sentiment applies well to junior software engineers (with mentorship). But imagine the much larger swaths of entry level employees in operations, support, or sales functions. When you have a 400 person team with 20% annual turnover (since people move in / out of entry level jobs frequently), the management + training + monitoring becomes a huge challenge.

I think the typical HN sentiment of "llms aren't deterministic" fails to take into account how non-deterministic giant groups of people are. Every group of 10 people typically needs a manager. And every 10 managers needs another manager. By comparison the engineering work on dialing in your LLM guardrails feels pretty worthwhile.

https://www.construction-physics.com/p/do-us-ports-need-more...

And I wasn't attached to that complex implementation in the way I would be if I architected it from scratch, so it was easy to move on.

But! Because of AI I was able to rapidly hack out like 4 variants of this feature that I didn't like. And felt comfortable throwing them away just as quick.

And unlike speculative investing like VC or public equities, banks lend against fundamentals: cash flow, collateral, debt coverage, repayment history. Their fiduciary responsibility to deploy deposits into relatively safe, income-generating assets.

As long as a fossil fuel business is financially sound (ie the pipeline manufacturer with stable cash flow and strong collateral) it’s hard to expect a bank to categorically refuse them as a customer.

Uber did invest early in self driving back in 2015, but in 2018 there was a fatality which pretty much deleted their whole program. And looks like it's taken them way too long to try picking it back up.

It should just be "marketplace". The term implies the existence of a "one sided marketplace". But isn't that just a business? If I have a bunch of product on my shelves and I'm trying to sell it, I don't call that a one sided marketplace?

Comments URL: https://news.ycombinator.com/item?id=47754611

Points: 4

# Comments: 0

Although now it's a fun battle to see if I can convince my eve to deploy Doom again and block others from overwriting it.

edit: Doom is back and we'll see how long the prompt engineering keeps it there

https://api.eve.new/api/sites/eve-doom/

Not OP's app in particular, but the underlying data from NASA. Nowadays the 360º cameras are $400 and work really well. Obviously we're working off of 2012 tech here.

But it seems like it would be enormously useful to have a full 3d image every 20 feet like google street view. Is this really just a power / bandwidth limitation?

Our set up is:

  packages/

  ↳ server

  ↳ app

  ↳ docs

And the design principals are already pretty well established (accounts, contacts, leads, opportunities, custom object model, stages, etc.). It just needs to be turned into a database boilerplate with a bunch of agent tools. Excited to try this out.

Tech stack: TypeScript | Node | React/Next.js | Postgres | Docker | K8s | LLMs

We’re building the AI-powered infrastructure layer for small-business lending. Banks and fintechs use Omni to automate document collection, financial modeling, public-record research, and ongoing borrower communication.

You’ll work on:

1. Wrangling messy PDFs into usable data (we built a major open-source extraction library: https://github.com/getomni-ai/zerox)

2. Aggregating millions of datapoints from 50+ public sources (UCCs, liens, licenses, tax records) + credit/KYC/AML data

3. Building real-time financial models that combine OCR, LLMs, and rule-based systems into predictable outputs

We’re early, you’ll have a huge impact. Email me (my name at the URL) or apply here: https://www.ycombinator.com/companies/omniai/jobs/Dr0GIaE-fu...