I fixed all the bugs our users found in the update to my queuing service I launched Wednesday. I was able to help find some mislabeled data due to another bug. I re-submitted all the dead letters, not a single further error. $dayjob had the strongest month yet last month and this is off to a similar start. Nice progress from the tumult and uncertainty at the start of Summer. #PrincipalEngineerDelights

The zero tolerance approach to noisy logs means that at least half a dozen times, the smaller queuing service has accurately alerted a real problem while the REST service has too high an error floor to be able to spot problems in real time.

Part of my goal with this service is to have it as a positive example to encourage my team to improve our REST service's logs as much as we can. #PrincipalEngineerDelights

I am unsure I was successful with this intention today. In part because $dayjob claimed all of my attention today. I let it rather than try to fight the flow. I did try to practice awareness of creative potential before each moment of debugging as I worked through a post-launch bug bash. If that made a difference, it was mild, but I think it did. Code review was clear and quick I think because of my intention. #PrincipalEngineerDelights

The queuing service I designed and largely wrote with some excellent assists from my team is now fully launched. Not a single transaction was dropped in the transition, mostly because even though $dayjob is mighty it is thankfully still managabley small. #PrincipalEngineerDelights

Late in my day yesterday, I finally got back into coding again for $dayjob after spending over a week wrestling with a series of inscrutable bugs. I realized that in troubleshooting one of those bugs, I inadvertently lost some work in progress. Rewriting from memory always is faster. I think I still came out ahead and definitely am optimistic I'll be able to build on that momentum this coming week. #PrincipalEngineerDelights

I sorted out the last imponderable for $dayjob and received validation of my fix from code review. Things are calm so the extra time hasn't gone amiss. Still I will be glad to dig into fresh work tomorrow. My only meeting is with a mentor. #PrincipalEngineerDelights

My team shared some excellent videos and podcasts today. Now that I have finished the infrastructure and base code for our data pipeline, we are going to all work on the next features.

I watched every video and found them all excellent. I'll share the links in a reply.

To reciprocate, I tried provide some additional context, some community practices I've observed, and some alternatives and when they might make sense. #PrincipalEngineerDelights

The data pipeline I've been building in #Rust since it started as an ETL tool a few months ago successfully completed its first run against our production database. Processed 12 million records in just over an hour and a half. #PrincipalEngineerDelights

@grueproof #PrincipalEngineerDelights

Another half day working on someone else's pull request. I was glad to do it, I used it to test possible fixes to some tech debt in our database. I have an approach now that should be zero risk.

I almost missed dinner catching up on my own work. At least this week was a good mix of helping and flow focused on my own work, mostly in #Rust.

#PrincipalEngineerProblems #PrincipalEngineerDelights