One more fun thing. We have a store to load data and handle updates. It even has a caching mechanism to minimize requests. The colleague? Loads everything as local state so the data exists multiple times in memory.
ngl I missed this kind of programming. Most applications I work on are pretty much just different frontends to insert, read and delete data from a database.
Who would've thought I'd have to think about memory management in a JS application? (We use WeakRefs as cache and I have to make sure objects persist when they're needed in the current view)
My boss likes to do if/else/for/etc without braces if it's only a single line. It drives me crazy because this is such an unnecessary source for errors.