HN user

jamest

3,334 karma

Current:

  - Helped start + Board @ CharmIndustrial.com

  - Co-Founder @ Kradle.ai
Past:
  - Co-Founder/CEO at Firebase (YC S11)

  - Co-Founder @ CovidActNow.org 

  - Partner @ HF0

  - Built the product team @ Chainlink
Posts53
Comments95
View on HN
kradle.ai 1mo ago

Lying is Best. The Most Honest AI Won Anyway.

jamest
6pts2
github.com 2mo ago

Raindrop Workshop: Local OSS agent debugger

jamest
9pts6
twitter.com 5mo ago

Tasklet's 6 year "overnight success"

jamest
2pts0
firebase.google.com 2y ago

PostgreSQL comes to Firebase

jamest
32pts4
www.shortwave.com 2y ago

Meet your AI Executive Assistant

jamest
49pts21
www.daffy.org 3y ago

Build charitable giving into your app

jamest
21pts1
www.shortwave.com 3y ago

Shortwave: A GPT-3-powered front end for Gmail

jamest
74pts66
blog.covidactnow.org 6y ago

Announcing the CovidActNow.org API

jamest
19pts3
covidactnow.org 6y ago

State projections for Covid-19

jamest
254pts269
firebase.googleblog.com 7y ago

Google Cloud Firestore Is Now Generally Available

jamest
6pts1
techcrunch.com 7y ago

Google beefs up Firebase for the enterprise

jamest
4pts0
firebase.googleblog.com 7y ago

Open Sourcing the Firebase Android SDK

jamest
5pts0
techcrunch.com 8y ago

Fantasmo is a decentralized map for robots and augmented reality

jamest
7pts0
www.blog.google 8y ago

Resonance Audio: Multi-platform spatial audio at scale

jamest
41pts11
fly.io 8y ago

One Hostname to Rule Them All

jamest
5pts1
opensource.googleblog.com 9y ago

Open sourcing the Firebase SDKs

jamest
204pts73
firebase.googleblog.com 9y ago

Working Closer with Google Cloud Platform

jamest
20pts0
techcrunch.com 9y ago

Firebase gets better analytics, crash reporting and more

jamest
130pts64
medium.com 9y ago

Welcoming James Tamplin and Jack Groetzinger to Founder Collective

jamest
2pts0
library.launchkit.io 9y ago

Exciting news about LaunchKit

jamest
1pts0
techcrunch.com 10y ago

Axway Acquires Mobile App Development Platform Appcelerator

jamest
11pts8
medium.com 10y ago

Google Is No Longer Forcing RouteBuilder to Shut Down

jamest
4pts0
developer.atlassian.com 10y ago

Going (way) beyond slash commands with Uber and HipChat

jamest
5pts0
medium.com 10y ago

Big data stories in seconds: Hacker News

jamest
2pts0
www.firebase.com 11y ago

ReactFire 0.5.0

jamest
6pts0
www.firebase.com 11y ago

Vulcan: Inspect your database in your browser

jamest
42pts7
www.erica.biz 11y ago

My Experience at YC Hacks

jamest
132pts16
www.firebase.com 12y ago

Introducing Firebase Hosting

jamest
220pts75
www.firebase.com 12y ago

Firebase turns two today

jamest
30pts5
hazard.typepad.com 12y ago

If I were a Founder

jamest
3pts0

I’ve been using this local debugger for the last ~week.

Seeing traces in real-time (and Claude seeing them too) is so so good. The velocity speed up is hard to understate.

Request for the Raindrop team: I wish your eval support was better. It’s not great having it completely disconnected from my CI system.

They actually deliver on the promise of "relational queries && real-time," which is no small feat.

Though, their console feels like it didn't get the love that the rest of the infra / website did.

Congrats on the 1.0 launch! I'm excited to keep building with Instant.

It was not on my bingo card to see the Shell Grotto on HN.

I loved this place as a kid and would marvel at the patterns.

The air of mystery around who made it and why invites some fun speculation.

Genie 3 is super impressive -- but you can't manipulate it programmatically like Minecraft.

We've built our infra so that we can plug in any simulation environment. If an AI-generated world starts being programmatically modifiable (and has really solid object permanance :) then we'd happily use it!

Hi HN -

Minecraft has a DSL that lets you manipulate the world. We've piggy-backed on that, along with a K8s infra to run N worlds in parallel, to let you create simulations of arbitrary complexity.

We think simulations are the best way to test frontier AIs due to their degrees of freedom and expressivity.

AMA!

I built an app (HN Clone, of course) with Instant's MCP hooked up to Claude Code.

The experience was brilliant.

Pros:

+ Fast

+ Easy

+ "Vibe coding on steroids" basically

+ The sense of 'wow' that comes very rarely with new tech

Cons:

- It used Instant as the database/backend, but I wasn't sure what it had done / how exactly it worked and had to spend a bunch of time asking Claude + reading the code to get it. It seemed reasonable, but if I were doing a prod system vs a PoC, this is where the time would be spent. ("Vibe coding lets you create tech debt 10x faster")

Net-net: This is the way for prototyping / validating. This is probably the way for production systems in N months too once the toolchain + agents get better.

[Firebase founder] The thing I'm excited about w/Instant is the quad-fecta of offline + real-time + relational queries + open source. The amount of requests we had for relational queries was off-the-charts (and is a hard engineering problem), and, while the Firebase clients are OSS, I failed to open source a reference backend (a longer story).

Good luck, Joe, Stopa and team!

The satire in the title is reminiscent of how Firebase was born.

We were previously working on a chat system called Envolve (https://www.envolve.com), that was 'Facebook Chat for any website'. A game that was using us for in-game chat created channels, used display: none on them, and passed game state through the chat.

We scratched our head, asked them why, and learned they wanted to focus on the frontend, not to deal with realtime message passing.

This led us to create a 'headless version' of our chat infra (re-written in Scala) that became the Firebase Realtime Database.

[Firebase founder]

I no longer work at Firebase / Google, but two points:

1. There may be issues with the GCP integrations & UX/DX, but GCP integration is good for many customers and necessary for the future of the business.

One of the common failure modes for the 2011-2014 crop of Backend-as-a-Service offerings was their inability to technically support large customers. The economics of developer tooling are a super-power-law. So, if you hope to pay your employees you'll need to grow with your biggest customers.

Eventually, as they become TheNextBigThing, your biggest customers end up wanting the bells and whistles that only a Big Cloud Platform provide.

This was a part of the reason we chose to join Google, and why the Firebase team really really really pushed hard to integrate with GCP at a project, billing, and product level (philosophy: Firebase exposed the product from the client, GCP from the server) despite all the organizational/political overhead.

2. I'm excited to see the current crop of app platforms emerge. It has been 10 years since we launched (https://news.ycombinator.com/item?id=3832877) and there are now some great innovations in the space. I like the way Supabase (https://supabase.com/) has exposed Postgres and InstantDB (https://www.instantdb.com) graphdb+realtime is really promising.

Those words are far too kind!

Most of the credit goes to my co-founder, Andrew, and the whole team who gave nothing short of everything to build it.

Killed by Google 4 years ago

This over-dramatizes a bit. For example some of the “deaths” were consolidations that’s were well implemented:

Eg. Fabric’s products were rolled into Firebase with continuity for developers. AngularJS was replaced by Angular.

I was surprised to see this on HN! A story, if you'll permit...

I visited two of Ackerman's caves (Spring Valley and Temple of Doom) in May of 2002. It was a few days shy of high school graduation and summer was starting to arrive in Minnesota.

My future Firebase co-founder, Andrew, and our high school classmate, Bob, made the drive down there one Saturday. Bob had been a sort-of pupil of Ackerman's, helping him explore and map the various caves he had found.

The day started innocuously enough with a visit to the main Spring Valley Cave that the article references as being previously owned and equipped to give tours. Bob took us off the steel gantry-ways and into some side passageways and chambers that were rarely trafficked.

It was the second cave, Temple of Doom, that was the more, ah, interesting experience. It has only recently been discovered and wasn't fully mapped yet. We popped open a man-hole cover in the middle of a corn field and dropped down a ~50 foot steel ladder. From there the cave descended in a spiral, with the passageway barely able to fit a human. Bob, typically the most composed human I knew, occasionally burst into fits of expletives, followed by silence. "Uhhh... Bob, everything OK?". Descending a 20-30 degree downward slope with inches to spare on every side, occasionally getting stuck, and with no way to turn-around was hair-raising.

After some undetermined period of time we finally got to the bottom of the spiral. At this point, Bob announced we could either brace ourselves between two sheer, very wet, rock faces and climb up ~100 feet without ropes, or go back the way we came. So... up the rock faces we went. Fortunately nobody slipped.

I can still viscerally feel the elation of emerging into bright afternoon sun of the corn field, grateful and relieved to be uninjured.

This was one of the several intense and bonding experiences Andrew and I had together, and perhaps contributed to why we kept working together despite some early startup failures.

As for Bob, he kept on spending time with Ackerman, until one day he was buried alive by a cave entrance collapse. Ackerman dug him out with a backhoe, but he was a little more wary of caving after.

Case and death data is pulled in daily. We are working on getting real-time feeds for ADT (Admission / Discharge / Transfer) for ICU and Hospital Beds.

The model is run (and so forward projections are updated) once every 3 days at the moment.

Hi HN - I’m one of the team working on Covid Act Now. We’re hoping this API is a useful input into COVID efforts (response planning, reopening initiatives, data visualization, etc).

Our model is only scoped to the USA (I wish we could include more countries, as this is a global pandemic. We haven’t had the time to expand yet).

I’m sure the API could be improved in the next version. For example, we had some lively discussion around whether OBSERVED_INTERVENTION was intuitive enough variable name. (It uses an inferred R0 based on actual observed deaths, cases, and hospitalizations to generate forward projections).

If you have any feedback, let us know and we’ll try and make it better in V2.