🚀 Big news: we’re launching @TelioHQ — AI agents for 24/7 call & text support!
See how we're helping RepairWise manage 1,000+ daily SMS and chat messages from EV owners diagnosing and repairing their cars
Our AI agents are helping @RepairWise_ revolutionize EV repair at scale 🚗⚡
Car owners can diagnose and service their EVs in just a few taps on their phone. How do they handle 1,000+ daily customer SMS & chat messages with just a 9-person team?
🌁 If you are attending the inaugural @sfrubyconf, three current and former members of the AngelList team are taking the stage:
@exAspArk on Building Cloud Data Infrastructure with Ruby
@justinbowen on Building AI agents with Rails
and of course, @og_chamod who will be doing a demo that is a continuation of his talk from earlier this month: from open-source Excel generation to cloud-hosted, graph-modeled financial statements and the AI tooling we’ve built around them.
@criccomini Centralizing data not only improves performance but also agent quality and HA: fewer tokens and tool calls, compact context, better rate limits, etc.
We're building https://t.co/buPObJgDQS using this approach with PG protocol goroutines, in-memory vector indexes, and Iceberg
· I almost can't code offline without GitHub Copilot autocomplete
· Gemini CLI devX is poor because they use React, literally (takes over the terminal)
· NeoVim and terminal are all you need (remains constant)
· I need to vibe-guess when to use AI vs when it's just faster to write by hand
· They often help write 80% of the code, but the final 20% takes 80% of the time
· A useful AI pattern: generate a test file → run it → check the output → fix code → iterate again
@neondatabase@databricks Congrats @nikitabase and the Neon team 👏
> within a few months, over 80% of databases were being created by AI agents rather than humans
This is a crazy stat
📣 We have a brand new Postgres platform with:
Instant Copy-on-Write branching
Built-in data anonymization
Separation of storage and compute
100% vanilla Postgres
It’s for staging/dev environments as well as for production workloads.
Details in 🧵
Depending on the person, they may thrive or struggle with operating in some of these problem-solving modes.
The goal is to align the strengths of the individual team members with the problems the company is trying to solve.
2) Breakthrough problem-solving
This solves problems that have never been solved before at a company. It functions as a bar-raiser.
Examples: unlocking a growth lever, shipping a new feature, etc.
A question to yourself, what’s the most impactful thing I’ve accomplished today?
3) System-building problem-solving
This involves scaling up and automating the existing processes.
Examples: outbound sales, handling 100 TB of data, etc.
The key is not to skip the previous steps in this sequence: make it work → make it useful → make it scalable.
1) Reactive problem-solving
This often solves urgent problems. But it doesn't always have a high impact.
Examples: replying to emails, fixing issues, etc.
Early on, this is necessary because there are no systems in place. The goal is to avoid doing busy work without progress.
My # 1 takeaway from the Isaacson's book about Elon Musk for founders:
You must always try to move faster, no matter how fast you're already going. A maniacal sense of urgency is crucial.