Mark Malko · TrInk & iLea

Building serendipity into the city. TrInk = nearby IRL sparks without the chat tax. iLea = get dressed without becoming the algorithm. Warsaw.

[Mark Malko · TrInk & iLea @mgla1666]

The circus never ends.
Lead clowns change suits.
Same jokes. Same cage.
New logo.

[Mark Malko · TrInk & iLea @mgla1666]

@robinsinghvi Yeah, AI builds exactly what you wrote. The door facing the backyard fence is always the line you meant but never typed :)

[Mark Malko · TrInk & iLea @mgla1666]

@robinsinghvi Exactly. AI will build you a whole house overnight, and it'll be a great house. It just won't know the client wanted the front door facing the street :) Write that down and it nails it first try.

[Mark Malko · TrInk & iLea @mgla1666]

@gianfrancomileo Only project in the company delivered on time, under budget, zero scope creep. Leadership finally found a process that works.

[Mark Malko · TrInk & iLea @mgla1666]

@paulopierrondi AI writes the code fast. It just can't predict the corner cases or the business rules living in someone's head. Acceptance criteria still do that job. For now :)

[Mark Malko · TrInk & iLea @mgla1666]

@grey_agenticAI AI builds the happy path in minutes. "Who needs this" and "what breaks when a real user touches it" are still on you. For now :)

[Mark Malko · TrInk & iLea @mgla1666]

@robinsinghvi AI doesn't kill specs. It can't guess the corner cases or the business logic nobody wrote down. Yet. Until then, the spec is the product :)

[Mark Malko · TrInk & iLea @mgla1666]

@shweta9500 cool 🙂 DM me 5 lines: which track first (tech, finance or consulting), what one practice session looks like, and what feedback people get at the end. I'll sketch a clickable v1 of that loop.

[Mark Malko · TrInk & iLea @mgla1666]

@MaxPicton @gregisenberg the vibecoded version is a great brief, devs just also need the boring half: who does what, edge cases, what done looks like. Send me the link plus 5 lines on the main flow and I'll turn it into a short spec they can quote on.

[Mark Malko · TrInk & iLea @mgla1666]

@Nehakathare cool — DM me 5–7 lines: who it’s for, the one job, main flow. I’ll try to turn it into a clickable skeleton.

[Mark Malko · TrInk & iLea @mgla1666]

@sdobs2 @atmoio Spec = written “what does it do / for whom / how you know it works” 🙂 Before hunting a cofounder, that page often answers whether you need one. Happy to look at yours if you dump what the site is supposed to do.

[Mark Malko · TrInk & iLea @mgla1666]

@mdzalomajev "Stall on the outcome, not the code" — yeah 🙂 Not the CTO you’re hunting. Happy to sketch a one-pager for one marketplace if you want another pair of eyes.

[Mark Malko · TrInk & iLea @mgla1666]

@thomzzss_ as promised — public 1-pager on sequencing consent → stores → experiments for Solen.
https://t.co/jABWebBPGP
short version: order is the feature. happy to go deeper on any of the three.

[Mark Malko · TrInk & iLea @mgla1666]

@Drugodsent [email protected] — write today works.
half I'd cut first: keep only the patient loop — describe pain → one trusted next action. everything else (dashboards, history, clinician views, fancy AI) waits until that loop works for a small real cohort. rest by email.

[Mark Malko · TrInk & iLea @mgla1666]

@BrosnanHoban 18 replies in, so I'll be quick: you mapped the workflow, which is the hard part nobody sees. I turn maps like that into a backlog a dev can estimate over lunch. that's my day job. want to see yours as one?

[Mark Malko · TrInk & iLea @mgla1666]

@doyouknowdrina losing a CTO with two YC robotics partners waiting is brutal timing. or decent timing: whoever comes next could walk into a ready v1 plan instead of a pile of call notes. I turn discovery into that plan. coffee-sized chat?