Professional development / Notes

Engineering notes.

Short observations drawn from the projects.
The decisions behind the interface and the code.

01 / AI systems

Grounding is a product decision.

A cited answer is only one part of a knowledge system. Source versions, review status, and the ability to trace a claim matter just as much as the final response.

Inside Solvin GraphRAG
02 / Product thinking

The interface should fit the task.

Conversation is useful when context matters. A direct control is often faster for repetitive work. Giving people both can make an assistant more useful, not less intelligent.

Inside Civi
03 / Applied ML

Make the tradeoff visible.

A recall improvement deserves its precision figure beside it. Good ML communication explains what a model gets wrong, what the threshold changes, and what remains unvalidated.

Inside Readmission prediction
04 / Product engineering

Connectivity is a design constraint.

Field software needs to work where the job happens. Capturing actions locally and making synchronization explicit changes the architecture from the beginning.

Inside Oprenta