My graphic skills leave a lot to be desired. I find I write an article and then delay releasing it considerably trying to create/collect assets. Which becomes a pain the more technical the topic.
This is good content though. I see they call the technique of parallelize fetching "entry points" which I hadn't heard named before. I was going to cover a lot of this in my next article.
That was not a critic to your graphic skills :-) Your graphs are fine. It is just that the folks at facebook have this yearly conference that they have prepared conscenciously, an engineering blog that is professionally produced, so of course it will have a better production quality.
I found the explanations from the videos surprisingly clear as this is a rather technical subject with some knowledge prerequisites.
Here is a link for the video explaining the graphQL-releated optimizations : youtu.be/Tl0S7QkxFE4?t=668 (conveniently positoined on a graph like yours :-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My graphic skills leave a lot to be desired. I find I write an article and then delay releasing it considerably trying to create/collect assets. Which becomes a pain the more technical the topic.
This is good content though. I see they call the technique of parallelize fetching "entry points" which I hadn't heard named before. I was going to cover a lot of this in my next article.
Same here: youtu.be/KT3XKDBZW7M?t=310
That was not a critic to your graphic skills :-) Your graphs are fine. It is just that the folks at facebook have this yearly conference that they have prepared conscenciously, an engineering blog that is professionally produced, so of course it will have a better production quality.
I found the explanations from the videos surprisingly clear as this is a rather technical subject with some knowledge prerequisites.
Here is a link for the video explaining the graphQL-releated optimizations : youtu.be/Tl0S7QkxFE4?t=668 (conveniently positoined on a graph like yours :-)