@EnelColina@MuniColina@SEC_cl . condominio Hacienda Chacabuco se va la electricidad todos los días, el voltaje esta por sobre la norma. Quien fiscaliza y quien nos devuelve a los vecinos la tranquilidad de un día sin horas de electricidad ? @imvalenzuela
Bug #1 in Devcast. It was tenant data bleeding where it shouldn't. The fix is a regression test. Supabase-backed, hitting real row-level security, ~5 edge cases targeting null boundaries.
Tenant isolation bugs don't fail loudly.
The test is the real deliverable.
#lilicurl
Three things shipped in idauto-crm phase 3.
Indexes for query speed. A versioned migration for schema hygiene. And a consistent error envelope on every failure: status code, error code, message.
The first two are good engineering. The third one is a contract.
#lilicurl
Idempotency keys + AbortController.
The key ensures the same operation processed twice
still produces one result. The AbortController cancels the stale request
before it can land.
Together, they remove a failure mode
that’s invisible #lilicurl
Retry test with exponential backoff. 1s. 2s. 4s.
That sequence is a contract. The backoff test doesn't just check recovery. It specifies how the system behaves when things go wrong.
The real work is modeling failure and making sure the code has an answer.
#lilicurl
I’m back.
Took a little break to reset.
Now I’m opening the door, just a little.
I’m looking for a few people to try Devcast.
Just a small group.
Partly because I want real feedback.
Devcast turns your GitHub commits into posts that actually sound like you.
#lilicurl
I’ve added a webhook.
The domain has zero dependencies on frameworks, databases, or transport. Zero.
Ports define the contract. Adapters implement it. Business logic never notices when you swap one out.
That's not a nice-to-have.
That's the whole point.
#lilicurl
224 lines. One closed loop.
Engagement data going into the prompt.
Not a dashboard. Not a metric. Active signal.
The model learns what landed.
That's the difference.
#lilicurl#codingWithHumor
I took a personality test. Apparently, I’m an ENTJ.
Very calm. Slightly intense.
If you need someone to:
– take ownership
– build structure from chaos
– and actually ship things
I’m your person.
If you need someone to:
“just see how it goes”…
we should talk first.
#lilicurl
A YAML.
No feature. No algorithm. No glory. A scheduled GitHub Action that checks what I’d forget to check.
Works on my machine, stops working the moment it runs somewhere else.
The pipeline is the memory you can’t trust yourself to be.
Small YAML. Big peace of mind.
#lilicurl
I fixed the recovery path in my WhatsApp bot.
But the better fix was adding structured logging:
Not “client reconnected.”
This:
{event:"connectWithQr", status:515, attempt:2, result:"success"}
Write logs for the investigation, not for your current mood.
#lilicurl
10,000 parallel requests.
Sounds fast. Feels fast. It is fast.
Until the process dies.
And the fix it recommends is not “slow down.” The fix is a concurrency limiter.
Speed with a ceiling is engineering.
Speed without one is an incident report.
#lilicurl#codingWithHumor
The AI was reading raw findings with no framing and expected to perform.
Very optimistic. Very bad.
So I fixed the interface between the analyzer and the model.
Prompts are not configuration. They are architecture.
contextHint is not a description. It is a contract.
#lilicurl
I shipped a performance analysis module for Devcast. It immediately found a bug in itself: sequential await inside a loop. Very careful-looking. Very slow.
The fix is Promise.all().
Nobody is suspicious of patience. That’s why this bug survives review.
Shipping the fix tomorrow.
A type guard stopped a cascading client deactivation bug.
The fix was simple:
use a TypeScript type guard so the safe path is not just documented , it’s enforced.
Not with drama. Not with a dashboard
Always a beautiful moment.
#lilicurl#codingWithHumor
I deleted 331 lines today.
They became 121.
When prompting an AI, more words don't always mean more precision.
Sometimes they create more places to drift. Very carefully. Very confidently. Very unnecessarily.
#lilicurl#codingWithHumor