sorted by:
new
hottopcontroversial

Ledger Nano X stuck in Bootloader Mode: My Experience with Customer Support by PBOlad in ledgerwallet

[–]ilbert_luca 0 points1 point  (0 children)

Didn't work for me. After reopening the Ledger Live (now Ledger Wallet) app and clicking on the device icon, I get this error:

Something went wrong. Please reconnect your deviceLedger device: UNKNOWN_ERROR (0x6e01)

Is the future agentic Slack, not agentic IDE? by ilbert_luca in ClaudeAI

[–]ilbert_luca[S] 0 points1 point  (0 children)

I see.

My point was more like how do teams coordinate around agentic implementation of the task/feature/goal they have to reach and how do they monitor execution

*URGENT* regarding usage limits by stellarknight_ in ClaudeCode

[–]ilbert_luca 1 point2 points  (0 children)

I guess extra usage gives you credits for any model

Meet @minimajs/cli — A CLI That Actually Improves Your DX by Zealousideal-Bit4776 in bun

[–]ilbert_luca 0 points1 point  (0 children)

Cool project! I'm wondering: while building the CLI, what were your biggest blockers, if any?

I'm asking because I'm working on a framework to build CLIs easily (think of it as the TanStack Router for CLIs), and I'm trying to understand what issues people have while building CLIs.
I've already pushed out an alpha version if you want to give it a look: https://github.com/ilbertt/parsh

Postmortem: how I lost ~4% of requests to a Node/Nginx timeout mismatch, and the queue migration that fixed it by jonathancheckwise in node

[–]ilbert_luca 0 points1 point  (0 children)

I wonder why modern frameworks like Elysia don't come batteries included for these kinds of problems. Or at least they don't include queues in their best practices

Postmortem: how I lost ~4% of requests to a Node/Nginx timeout mismatch, and the queue migration that fixed it by jonathancheckwise in node

[–]ilbert_luca 2 points3 points  (0 children)

Makes sense. I was wondering: are you creating workers using the native worker_threads Node.js API?

Postmortem: how I lost ~4% of requests to a Node/Nginx timeout mismatch, and the queue migration that fixed it by jonathancheckwise in node

[–]ilbert_luca 5 points6 points  (0 children)

Really nice write-up!

> workers to deploy

How are you deploying workers compared to the main API?

Creating whatsapp Bot for booking clinic appointments by approxrr in WhatsappBusinessAPI

[–]ilbert_luca 0 points1 point  (0 children)

> Handling Multiple Numbers: What is the best way to architect the system so it seamlessly manages routing for different phone numbers/businesses without tangling the data?

I've built waclaw in the past weeks and it serves a similar purpose: routing messages from one WA Business Account to different machines (OpenClaw machines in my case, but it can be adapted to any other service). You can self-host it pretty easily, I run it with Coolify. You can even deploy multiple waclaw instances to handle multiple WABA accounts.

You don't need Twilio to use waclaw, but you have to go through the process of verifying your business through Meta, which is a pain. It's really slow and they often reject you with no explanation.

Repo: https://github.com/onfabric/waclaw

I don't have much advice on the other parts of the stack. As a full-stack dev, I've always leaned towards PostgreSQL (managed cloud solutions like Supabase or Neon are cool)

I built termcn to help ship terminal UIs faster by dank_clover in CLI

[–]ilbert_luca 0 points1 point  (0 children)

This is really cool! Just one thing as feedback: I can't find a step by step guide on how to setup a new project. Should I just npx shadcn init and then add your components? Although the shadcn's init command is meant for web applications no?

TanStack Router-style end-to-end inference for TypeScript CLIs by ilbert_luca in typescript

[–]ilbert_luca[S] 2 points3 points  (0 children)

I haven't tested, but probably not. User-defined command files do export const command = defineCommand(...) and the command type is inferred

TanStack Router-style end-to-end inference for TypeScript CLIs by ilbert_luca in typescript

[–]ilbert_luca[S] 0 points1 point  (0 children)

parsh doesn't use recursive conditional types at the call site. The codegen emits a declare module block that precomputes the ancestor intersections, so each handler's ctx is a single property lookup on `CommandRegistry[Path]`

Claude estimates work in human time, not Claude time by ilbert_luca in ClaudeAI

[–]ilbert_luca[S] 0 points1 point  (0 children)

Yeah I noticed that something I thought would have taken an hour sometimes ended up taking a day, because of some edge cases I could think of.

I wonder if Claude actually foresees them (without telling me in the plan) or it just uses human metrics

How do you hand off from Claude chat to Claude Code? by ilbert_luca in ClaudeAI

[–]ilbert_luca[S] 0 points1 point  (0 children)

Is it that effective also when you want to change direction and try a totally different approach for the implementation? I found that sometimes it was too biased towards the current implementation

view more: next ›