Dev Log: April 17 Wrap-up

Overview

Today was a bit of a split-personality day. I spent a good chunk of time obsessing over the visual polish of my personal site, followed by some deep-trench work on our internal workflow builder's logic. It was one of those days where you move between 'this looks cool' and 'why isn't this data binding correctly?'

What I Worked On

Adding some motion to the Portfolio

I decided my 'About' section was looking a little too static. I’ve been wanting to showcase my code snippets in a way that feels more alive, so I built out a 3D scrolling marquee. It’s a nice touch—it lets the snippets cycle through without the user having to manually click through a massive list.

However, I quickly realized that what looks great on a 27-inch monitor feels pretty annoying on a phone. Marquees on mobile can be distracting and hard to interact with, so I had to backtrack and add some logic to disable the effect on smaller screens. Now, it gracefully falls back to a standard vertical list on mobile. It's a reminder that fancy UI shouldn't get in the way of usability. If you're on your phone, you just want to read the code, not chase it across the screen.

Debugging the Workflow Engine

On the professional front, I had to tackle a pesky issue with how our internal HTTP request nodes handle session data. We needed a way to manually override session resources during testing, which meant exposing a new input handle on the node itself.

The real challenge wasn't just adding the handle—it was making sure it worked for nodes that were already created. I had to write some logic to retroactively inject this handle into existing configurations so users wouldn't have to delete and recreate their entire workflow just to get the update. I ended up using a setTimeout hook to ensure the inputs sync up correctly after the initial mount. It’s a bit of a 'hacky' necessity when dealing with dynamic forms, but it gets the job done without breaking the state.

Wrapping Up

It’s funny how the 'simple' task of adding a scroll effect ended up taking more thought regarding responsive design than the actual implementation of the animation. Tomorrow, I’ll probably dive back into the workflow builder to see if there are any other legacy nodes that need this retroactive treatment. Catch you then.