the fact git has lasted this long (20+ years) is bonkers. statistically, something you wouldn’t expect to see in your lifetime. the messi of software.
a testament to good engineering practices. an extremely careful set of maintainers
& most of all: the C programming language.
was asked today what’s a good first programming language. I always answer python, since it’s practical, but realized today that doesn’t matter in the same way now.
didn’t have a great answer. but after awhile, said, honestly: Lisp. almost had an existential crisis.
@antirez seems right to me. 90% of the inertia and resistance to advanced integration testing is how much of a pain it is to reliably setup the testing ground; this is mostly solved (as long as auth works!)
salvatore points the right way, as usual. we are in a transitional era.
in an era like this, things will be weird! half-done things. the twilight of an era. this has happened before, in the early renaissance.
There are projects where I don't look anymore at the code at all, but only control the design ideas and the "product" itself (DS4). There are other stuff where I check every line and modify (mostly saying how and not myself, sometimes myself) every detail, like for Redis Arrays. Let's say that for 80% of the projects to check the code no longer makes sense, but checking the ideas / algorithms / code structure even only by prompting is, I believe, a good idea. While providing the right design decisions is not just a good idea, it is essential to do great work.
been noodling and editing and fixing; and I have something I don’t mind for a 1.1 edition of High Performance Git
https://t.co/1w1DgDZS7Q
free to the world
a lot better will come so stay tuned for 1.2
@jorandirkgreef@curlykoder@antirez my old friend Salvatore may disagree but I don’t think “code as poetry” or craft-fetishism in 2026 is the right move either.
the point is how to maintain quality under new limits! not romanticize ourselves