⭐️ What We Learned ⭐️

1: 2020, a thread. Like everyone, B4B faced countless curve-balls in 2020. Here are some things we learned, that helped us increase our influence in the toughest year we have lived through /

2: Act quickly: As Covid fears grew, we had a contingency plan ready by March 2, long before lockdown was a threat. By March 12, work from home was a thing, and on March 15 we closed the office completely /
3: Put the team first: In a crisis, you need the team more than ever. We got our staff from overseas back home early, trialled work-from-home early, put health (inc mental health) and working policies in place early, so everyone was clear what was happening /
4: Use the tech. Our team was already using Zoom, Slack and various other tools but they really came into their own to do the heavy lifting of working remotely, before the Covid nervousness became a full-blown crisis /
5: Keep the team vibe: Daily team Zooms – a huddle to get things going in the morning, an update in the afternoon, & always a willingness to use some of the time for social chit-chat & the small-talk that we take for granted in an office. /
6: Don’t wait for the Govt to act: a) Because, you know, sloooowness b) You’ll find yourself in a mad rush with everyone else in the Last Minute Lounge /
7: Spot the opportunities: With Westminster bars and coffee shops shuttered, everyone was trying to find a ‘new normal’. We worked hard to become part of that new normal /
8: Look out for each other: It’s good to talk, as they say. And, when it’s your turn to struggle a little, work should ease the pressure, not ramp it up /
9: Have a support network: If you work by yourself anyway, all of the above applies, but of course you‘ll need to have an external support network – FB groups, regular work contacts, whatever it takes not to disappear into a communications hole /
10: Biscuits: They’re the answer to so many problems /ends

More from Society

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.