Day 268: good, bad, ugly

good: really feeling browserflow

bad: i’m up again at 4am

good: but i’m working and not being a gold-league starcraft scrub

bad: i told my friend i’d onboard him to browserflow at 10am. rip sleep

good: for some reason, browserflow is running much faster than it was before

bad: it’s running so fast that it’s hitting race conditions in flows

good: i’ve handled a million edge cases and site structures in browserflow

bad: the web is vast and weird enough where there are a billion cases to handle. for each case i solve, i discover 5 new bugs. wish i were exaggerating but nope

ugly: i’m stuck on trying to work with twitter’s ridiculous site structure where dom elements get swapped out as you scroll down and i solved this before when you’re staying on the same page throughout the flow but if you click into each element and come back then the dom elements are removed and added instead of committing a full page load and that’s hugely problematic because there’s no way to know when a single page app is done rendering a page so i have to guess and use heuristics which aren’t working reliably and it’s killing me inside

halp