Eugene Lazutkin (@uhop) profile picture

Modern software technologies.

Plano, TX
Joined September 2007
Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)Photo by Eugene Lazutkin (@uhop)
Ergonomics and cognitive load — an API exists to be used, so how it feels in use is part of its design. End users never see it, but for developers it makes or breaks an API. With stories from moment.js, Dojo, and jQuery. lazutkin.com/blog/2026-11-17…
17
Open source, honestly — open source promises that anyone can contribute, that any project can be forked, and that more eyes make better code. I've watched those promises meet reality for two decades. Here is the inventory. lazutkin.com/blog/2026-11-10…
1
24
Genericity for free — functional structures let us write an operation once for every container. JavaScript keeps shipping the specialized version instead, and we pay for it in duplicated APIs and glue code. lazutkin.com/blog/2026-11-03…
3
86
Working in the open — most of what I learn on a job stays with that job. What I publish (open source code, posts, talks) comes with me to the next one, and I reuse it more than anyone else does. lazutkin.com/blog/2026-10-27…
1
25
CRUD: REST without the HTTP — strip HTTP out of REST as practiced and a completeness principle is left: create, read, update every valid way, and delete, alone or as a member of a collection. Paging and sorting work without HTTP too. lazutkin.com/blog/2026-10-20…
1
2
34
replace() as an iterator — String.replace() with a global regex and a function has walked the parts of a string since 1999. Rarely the best tool today, it is still in a lot of code: how it works, what it is good for, and what it costs. lazutkin.com/blog/2026-10-13…
1
22
Math-grounded APIs — if a type is a number, a set, or a sequence, math has already written its complete API, with correctness and costs worked out. The work is to recognize it and implement it efficiently. Second in a series on API design. lazutkin.com/blog/2026-10-06…
1
15
The cost of dependencies — adding a package takes one line, and with it we take on its bugs, security holes, release schedule, and its own dependencies. What that costs over a project's life, and the four checks I run before adding one. lazutkin.com/blog/2026-09-29…
1
29
Generalization as discipline — general code comes out better than code cut to fit one job. When we cannot afford all of it: work out the ideal shape first, cut what today does not need, and keep a plan for putting it back. lazutkin.com/blog/2026-09-22…
1
25
Duff's device, part 2: copying within an array — on every Node and Deno we can install today, Array#copyWithin runs 47 to 84 times slower than a plain loop. JavaScriptCore has the fast path, and V8 landed one in June. lazutkin.com/blog/2026-09-15…
1
2
61
Coding tactics: the series — the map of eight posts on ifs and loops: linearize the flow, simplify the conditions, state the invariant, jump when it keeps the code flat, and take the small optimizations on the way. lazutkin.com/blog/2026-09-08…
21
Death by a thousand reasonable decisions — nobody writes bad code on purpose. It accretes from decisions that were each reasonable at the time. Why it happens, and what ownership and a scheduled refactor buy. lazutkin.com/blog/2026-08-25…
16
Fast enough — I worked out from first principles that servers should run compiled languages. The client half held. The server went the other way, and the reasons are better than the prediction. lazutkin.com/blog/2026-07-28…
1
83