Bump uri from 1.0.2 to 1.0.4

Gemfile.lock

@@ -46,6 +46,8 @@ GEM
     faraday-net_http (3.4.0)
       net-http (>= 0.5.0)
     ffi (1.17.1)
+    ffi (1.17.1-x86_64-linux-gnu)
+    ffi (1.17.1-x86_64-linux-musl)
     forwardable-extended (2.6.0)
     gemoji (4.1.0)
     github-pages (232)
@@ -90,7 +92,7 @@ GEM
       liquid (= 4.0.4)
       mercenary (~> 0.3)
       minima (= 2.5.1)
-      nokogiri (>= 1.18.9, < 2.0)
+      nokogiri (>= 1.16.2, < 2.0)
       rouge (= 3.30.0)
       terminal-table (~> 1.4)
       webrick (~> 1.8)
@@ -270,7 +272,7 @@ GEM
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
     unicode-display_width (1.8.0)
-    uri (1.0.2)
+    uri (1.0.4)
     webrick (1.9.1)
 
 PLATFORMS

about.html

@@ -22,9 +22,11 @@ <h2>Work experience</h2>
 <p>
   <em>(Since 2022)</em>:
   <strong>Principal Software Engineer at <a href="https://midokura.com/">Midokura</a></strong>.
-  Contributing to Sony's Edge AI sensing platform. We build systems to
-  manage fleets of edge devices, deploy AI vision models, and stream
-  real-time inferences to the cloud. Some notable projects:
+  We build systems to orchestrate, monitor and manage GPU servers and
+  high-bandwidth network fabric for AI workloads, deployed in private
+  datacenters. On an earlier project, I worked for ~3y on Sony's Edge AI
+  sensing platform. We build systems to manage fleets of edge devices,
+  deploy AI vision models, and stream real-time inferences to the cloud.
   <ul>
     <li>
       Re-architected core backend systems (based on MQTT, Kafka, and
@@ -44,11 +46,15 @@ <h2>Work experience</h2>
   <em>(2020-2022)</em>:
   <strong>Principal Software Engineer at <a href="https://newrelic.com/">New Relic</a></strong>.
   Embedded in internal platform teams managing entity inventory (hosts,
-  containers, services, etc.), metadata and relationships. The platform
-  is a foundation for most of New Relic's observability experience (we
-  were regularly in the critical path for ~50-75% of top-level company
-  OKRs.) Highlights:
+  containers, services, etc.), metadata and relationships. 
   <ul>
+    <li>
+      Maintained a foundational platform for most of New Relic's
+      observability experience. We were regularly in the critical path
+      for ~50-75% of top-level company OKRs, and critical for New
+      Relic's 99.8% user-facing <a
+        href="https://docs.newrelic.com/docs/licenses/license-information/referenced-policies/service-level-availability-commitment/">SLAs</a>.
+    </li>
     <li>
       Led the implementation of a high-throughput system that inspected
       every telemetry datapoint flowing through New Relic (millions/sec),
@@ -69,8 +75,8 @@ <h2>Work experience</h2>
       <li>
         We created developer tooling before commercial
         equivalents appeared (e.g. automated dependency propagation, developer
-        metrics platform, etc.). Generated traction organically, with
-        measurable productivity gains.
+        metrics platform, etc.). Generated traction organically, from 0
+        to hundreds of users and measurable productivity gains.
       </li>
       <li>
         Consolidated Infrastructure-as-a-Service projects