elonvolo

Paying for 8 hours of my electric bill.

I made a debugging/tracing tool called logitall that adds a console.log() to every line of a Javascript codebase. It’s helped me figure out numerous complex codebases and fix bugs much faster

https://github.com/ElonVolo/logitall

I wrote my own print debugging tracer. It’s now my goto for debugging most things.

https://github.com/elonvolo/logitall

YAGNI, YAGNI, YAGNI

Is the battle cry of losers

Who say “don’t bring that gun to the knife fight”

And ignore their opponents’ bazookas.

We’re not detecting signals from aliens because, in all likelihood, everybody but the Terrans are using quantum entanglement communication for vast distances, and no one’s seriously used radio signals since the time of their great, great, great, great, great, great grandad.

Interesting footnote: I’ve used logitall on logitall to debug logitall.

There’s a lot of social status and perception-shaping tied up in who gets to do what innovation.

I’ve noticed that the very same ilk of leadership/managers who would balk at the complexity of adding a linter or json schema validation and cite “someday, that would be nice, but for now we’ve got to get quick wins and ship features” would not hesitate to let a golden-boy architect who’s also a drinking buddy add a CQRS microservice written in Go communicating in some hand-rolled bespoke protocol—-just because it wins some folks cool points.

The dirty little secret is that a software project with two different native codebases is often cheaper, with a faster time-to-market, than a cross platform browser-tech based solution that had just one codebase.

The BS of the browser tech world compounded over time and a million edge cases eventually eats up all the one-codebase, cross-platform savings.