dmitry@echowaves(1)teams · collaboration · AI capacity
NAME
dmitry@echowaves — teams · collaboration · AI capacity
DESCRIPTION
I help engineering organizations absorb agentic software engineering without losing control of what they ship: the practices, the measurement and the handover that let a team run it after I leave.
WHERE THIS APPLIES
- Platform and developer-productivity groups that own a pipeline, a release train or an internal toolchain.
- Organizations running agentic development that cannot yet tell leadership what it changed.
- React Native and Expo teams whose release cycle is the constraint.
- 20 → 10 days
- Release cycle, halved
- 89%
- Employee Net Promoter Score
- <1%
- Annual production defect rate
Dmitry AmelchenkoBoston, MassachusettsGitHubLinkedInDev.toEmail
What I do now
Help engineering organizations get durable gains from agentic software engineering. Not a tool rollout and not a strategy deck: the part where humans change how they build.
- Most teams bought agents and stayed where they were. Output went up; delivery did not, because nothing downstream was built to trust it.
- So the work is the unglamorous half: what a change has to pass before it ships, who owns that, how long trust takes, and what happens when the model changes again in six months.
- I do it inside environments where that matters — insurance, healthcare, anything with a regulator attached — because that is where the problem is hardest and the proof is real.