Thread:
Tweaks, mistakes and ideas.
Man Utd 3 v 2 Liverpool — Tactics #MUFC
----------------------------------------------------------











This did 2 things:
1. created a 3v1 v Shaw.
2. Gave Thiago more space to operate.
#mufc dealt well with PP & MR shifting to cover quick.+ Thiago's long passes were unsuccessful.

More from Sport
I don't think people understand the vital difference between a well-rehearsed (and physical) team vs a collection of individuals with no real understanding - new players, makeshift centre-backs, other players out of position. Make do an mend when missing a ton of quality = v.hard
Add fatigue,with less option to rotate, and big effort in 3 away games in previous 9 days. Team lacks height and heft without VvD, Matip, Fabinho, Gomez. Team lacks pace and goals without Jota, Mané. Lacks pace at back without VvD and Gomez. No senior keeper undermines confidence
Team has been disrupted constantly this ssn. Rarely below 6 injuries, often = 10. Thiago a real bonus after months out, but the proper team is not around him. Even Gini looked knackered yesterday. 5th/6th-choice strikers and centre-backs will always be a big drop from 1st choices
Last night was a bit grim, and Brighton were excellent. But it was a strong XI for them, in terms of usual players and in terms of physicality. LFC full of skilful slower little guys right now - lacking the skilful bodyguards and pace. Kabak should help, but he's young and new
You can read Mentality Monsters or Perched for how much I talk about the unity of a team, the practiced understanding from years of intense training together, knowing each others runs and movements. Right now it's a team of semi-strangers and stand-ins.
Definitely agree BUT, we should still be beating Burnley and Brighton at home.
— PaulShilly \U0001f339\U0001f339 (@shillcock_paul) February 4, 2021
For me, that is in part, a tactical problem.
Add fatigue,with less option to rotate, and big effort in 3 away games in previous 9 days. Team lacks height and heft without VvD, Matip, Fabinho, Gomez. Team lacks pace and goals without Jota, Mané. Lacks pace at back without VvD and Gomez. No senior keeper undermines confidence
Team has been disrupted constantly this ssn. Rarely below 6 injuries, often = 10. Thiago a real bonus after months out, but the proper team is not around him. Even Gini looked knackered yesterday. 5th/6th-choice strikers and centre-backs will always be a big drop from 1st choices
Last night was a bit grim, and Brighton were excellent. But it was a strong XI for them, in terms of usual players and in terms of physicality. LFC full of skilful slower little guys right now - lacking the skilful bodyguards and pace. Kabak should help, but he's young and new
You can read Mentality Monsters or Perched for how much I talk about the unity of a team, the practiced understanding from years of intense training together, knowing each others runs and movements. Right now it's a team of semi-strangers and stand-ins.
You May Also Like
H was always unseen in S2NL :)
Those who exited at 1500 needed money. They can always come back near 969. Those who exited at 230 also needed money. They can come back near 95.
Those who sold L @ 660 can always come back at 360. Those who sold S last week can be back @ 301
Those who exited at 1500 needed money. They can always come back near 969. Those who exited at 230 also needed money. They can come back near 95.
Those who sold L @ 660 can always come back at 360. Those who sold S last week can be back @ 301
Sir, Log yahan.. 13 days patience nhi rakh sakte aur aap 2013 ki baat kar rahe ho. Even Aap Ready made portfolio banakar bhi de do to bhi wo 1 month me hi EXIT kar denge \U0001f602
— BhavinKhengarSuratGujarat (@IntradayWithBRK) September 19, 2021
Neuland 2700 se 1500 & Sequent 330 to 230 kya huwa.. 99% retailers/investors twitter par charcha n EXIT\U0001f602
The YouTube algorithm that I helped build in 2011 still recommends the flat earth theory by the *hundreds of millions*. This investigation by @RawStory shows some of the real-life consequences of this badly designed AI.
This spring at SxSW, @SusanWojcicki promised "Wikipedia snippets" on debated videos. But they didn't put them on flat earth videos, and instead @YouTube is promoting merchandising such as "NASA lies - Never Trust a Snake". 2/
A few example of flat earth videos that were promoted by YouTube #today:
https://t.co/TumQiX2tlj 3/
https://t.co/uAORIJ5BYX 4/
https://t.co/yOGZ0pLfHG 5/
Flat Earth conference attendees explain how they have been brainwashed by YouTube and Infowarshttps://t.co/gqZwGXPOoc
— Raw Story (@RawStory) November 18, 2018
This spring at SxSW, @SusanWojcicki promised "Wikipedia snippets" on debated videos. But they didn't put them on flat earth videos, and instead @YouTube is promoting merchandising such as "NASA lies - Never Trust a Snake". 2/

A few example of flat earth videos that were promoted by YouTube #today:
https://t.co/TumQiX2tlj 3/
https://t.co/uAORIJ5BYX 4/
https://t.co/yOGZ0pLfHG 5/
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.
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.