As I grow older, I've found out that I value tools, processes and organization/conventions more than the code itself. These days it is very strange for me to lo

As I grow older, I've found out that I value tools, processes and organization/conventions more than the code itself. These days it is very strange for me to look at some piece of code and think "that's amazing". Part of that is because I keep finding out that the best code is as simple and "to the point" as possible. Great tools (I'm counting stuff like good type systems, good meta-programming, etc. in this category) combined with good architecture/conventions are the real enablers of this kind of code. Once the former is worked out (which is the really hard part), the latter should just come naturally given a sensible coder. As a reuslt, I'm excited about Rust and its "zero-overhead" abstractions. I'm excited about the Elm architecture, and how it permeated/influenced the javascript ecosystem (react/vue/whatever). I'm excited (and amazed!) about the RDBM's we have available (sqlite, mysql, postgres), and the awesome cache/in-memory ones (redis), and the strongly consistent distributed systems (etcd/zookeper/etc.), and the web servers (apache, nginx), and the "application servers" (jetty, uwsgi, php-fpm), and the load balancers (haproxy), and the heaps of testing tools we have, and I could go on and on... Almost none of these things existed when I started coding. Databases got corrupted frequently, client/server programs were almost mythical monsters, etc.. These were the days when clever code was king (to pack stuff tighter in memory, to shave off some computation through clever operations, etc.). Nowadays these hacks are hardly ever necessary anymore, and I couldn't miss them less. If you want to see me excited, explain to me how your system works and why it won't break. This is my takeaway, not your actual code...