As a way to decompress πββοΈ from work I write a few notes on the way home. Iβll add some details and related links then they get posted to Twitter @iamsteveworsley and collected here for discussion. β‘οΈ
ββ
Updating a design system, consuming pattern/component libraries and consuming micro-frontends sure is tricky. More places it can fall over but hopefully with the code split the impact of the issues will be smaller.
ββ
Anyone else find it hard to provide an immediate and useful update on your work? Or say what you've been doing over the past week if asked out of the blue? Read more
ββ
Lift and Shit: performing a Lift and Shift but leaving the re-platformed code in a worse state than it was originally created. Occurs when a lift is rushed resulting in sudden pain and fumbling of the shift. Disappointment is akin to receiving a damaged parcel through the post which you canβt return because the seller has shut-up shop and retired to a farm to start a greenfield project to breed rare Yaks for their wool.
ββ
A challenge Iβve found with design systems and pattern libraries is finding the time to get competent with the varieties of tooling - beyond just using them as and when needed. Particularly Fractal and Storybook.
ββ
Interesting projects, a desire to help people and fear of missing out make it hard to say no. I had so much on during the run up to Senior it became extremely stressful. So part of my PDP refresh will be around focus, working on one or two discretionary effort style things and saying βno thanksβ more often. Read more on speed and velocity
ββ
Iβve not come across AHA before (Avoid Hasty Abstractions) π but Iβve certainly come across some bat-shit abstractions and probably a few I wrote my self. π The Befuddlement Ratio - Every click through you perform in your IDE your intelligence decreases in percent the number of characters used in the abstracted function name.
ββ
See you next time! π€©
Top comments (0)