Cumulative Layout Shift is out of control and in the case of Lufthansa it’s so ridiculous I had to vibe an article about it. Do you think shifting is not a big deal? How would you improve the solution suggestions? Thanks
No, that is not how this works. Doing the due diligence of writing the article would force you to think about how you express yourself or present the information.
How do you know there are 4 teams at Lufthansa that are responsible for those different parts of the page? Maybe you do, but the article never states why. A citation here is a must, even if the citation is insider knowledge from yourself. How do you even know they have a micro-frontend architecture? Even if you do know this, your article doesn't state how you gathered that information.
The same cumulative layout shift could just as easily happen if a single team was responsible for the frontend. All it requires is client side rendering and staggered data fetching.
You don't even think the topic is important enough to communicate it properly with the world. If this investigation did take a considerable amount of time to put together, then doing the final step of writing ~800-900 words to share your investigation is not a big commitment.
I think 'vibe' suggests that you haven't really read or edited the result. That might not be what you meant, but on that understanding, it is fair to ask why someone else should read your article if you have not properly read and edited it.
Why not have an integrated frontend instead of Micro frontends?
Because it's a much bigger org change with lower probability of happening
Cumulative Layout Shift is out of control and in the case of Lufthansa it’s so ridiculous I had to vibe an article about it. Do you think shifting is not a big deal? How would you improve the solution suggestions? Thanks
Why would I take the time to read an article you haven't even taken the time to write?
Because IMHO it's an important topic and I did take considerable time to do it. Please check out the image then. Thanks
No, that is not how this works. Doing the due diligence of writing the article would force you to think about how you express yourself or present the information.
How do you know there are 4 teams at Lufthansa that are responsible for those different parts of the page? Maybe you do, but the article never states why. A citation here is a must, even if the citation is insider knowledge from yourself. How do you even know they have a micro-frontend architecture? Even if you do know this, your article doesn't state how you gathered that information.
The same cumulative layout shift could just as easily happen if a single team was responsible for the frontend. All it requires is client side rendering and staggered data fetching.
You don't even think the topic is important enough to communicate it properly with the world. If this investigation did take a considerable amount of time to put together, then doing the final step of writing ~800-900 words to share your investigation is not a big commitment.
/rant
I know because it’s obvious by looking at the loading experience.
> My source is that I made it the fuck up
Thanks, added clarification that it's one possible explanation.
I think 'vibe' suggests that you haven't really read or edited the result. That might not be what you meant, but on that understanding, it is fair to ask why someone else should read your article if you have not properly read and edited it.
I have read and edited it multiple times.
I believe you. I would suggest not using the word 'vibe' in that case.