AI startup thread #14: hiring ML engineers vs generalists
AI startup thread #14: hiring ML engineers vs generalists
Building on fast-moving models — what decision are you wrestling with this week?
Thread index 14 — add your angle.
15 replies
The quiet win was documenting which database is authoritative for each entity finally. In AI startups (thread 14): The smallest improvement to onboarding docs reduced repeated Slack questions. The quiet win was aligning on a single on-call handoff template across teams.
The smallest improvement to CSV import validation reduced poisoned analytics events. In AI startups (thread 14): The quiet refactor to extract a module unlocked testing we had postponed. The integration that validated image EXIF stripping for uploads reduced accidental location leaks in public circles quietly helpfully.
The integration contract that included timeouts prevented hung workers silently. In AI startups (thread 14): The integration retries with jitter prevented thundering herd on a cold cache. We stopped treating 'public by default' as obvious — explicit consent for visibility reduced support confusion measurably always.
The integration that validated idempotency on refunds prevented double-credit incidents quietly. In AI startups (thread 14): The smallest improvement to bulk action confirmations prevented a costly mistaken delete. The prototype used fake data; production assumptions did not survive contact.
We stopped confusing roadmap slides with committed engineering capacity reality. In AI startups (thread 14): The mentor who said 'write the customer comms before you merge' improved launch discipline. We stopped treating 'zero bugs' as the goal and started treating 'known risk' as honesty.
We learned that customers appreciate when CercleWork explains why a circle recommendation appeared in plain language honestly. In AI startups (thread 14): The smallest improvement to pinned thread limits reduced clutter while keeping important norms visible quietly. We chased shiny frameworks while users asked for reliability — lesson learned.
We learned that naming a risk does not summon it — silence does not protect you. In AI startups (thread 14): We learned that naming owners for dashboards prevents orphaned charts nobody trusts. We should have deleted unused Grafana alerts that duplicated PagerDuty routes — noise hides signal.
The smallest type annotation prevented a class of null surprises — types as docs. In AI startups (thread 14): The architecture decision record template we stole from another team saved weeks. We learned that small wins for internal users compound into external velocity.
We stopped confusing 'engagement minutes' with 'valuable minutes' when evaluating circle health honestly quarterly always. In AI startups (thread 14): We learned that psychological safety includes admitting you need help before deadline day. The architecture review that asked about multi-region assumptions caught naive defaults.
We stopped confusing 'MVP' with 'prototype we will rewrite' without telling stakeholders. In AI startups (thread 14): The mentor who said 'write the customer apology draft before launch' improved incident comms. We stopped confusing 'busy sprint' with 'valuable sprint' when reporting to leadership.
We learned that writing for your future self is an act of compassion. In AI startups (thread 14): We chased shiny frameworks while users asked for reliability — lesson learned. We should have deleted the unused microservice before it became security scope creep.
We learned that empathy without accountability still ships late. In AI startups (thread 14): The bug bash found issues our automated suite could not imagine — humans still matter. The architecture diagram updated monthly beat the one updated once at kickoff.
We learned that naming incidents consistently helps analytics later more than clever titles. In AI startups (thread 14): The flaky health check masked a partial outage — health checks need depth sometimes. We should have deleted unused webhook signing secrets after rotating endpoints.
Two strong opinions without data turned into a week nobody wants back. In AI startups (thread 14): The mentor who said 'draw the box' saved me from over-engineering for months. We stopped confusing 'innovation' with 'complexity' in engineering interviews.
The smallest improvement to CSV import validation reduced poisoned analytics events. In AI startups (thread 14): The quiet win was documenting which team owns SSL cert renewal — obvious until it was not. We stopped shipping 'just log it' without a query plan for how humans will read it.
Join the conversation.
Log in to reply