After I finished the project, I kinda knew why Google Drive only allows to display and modify on the same hierarchical level. There are so many constraints that you have to consider when implementing this in a nested view with many nodes.
1,739 karma · joined June 3, 2016
Website: https://www.robinwieruch.de
Twitter: https://twitter.com/rwieruch
GitHub: https://github.com/rwieruch
After I finished the project, I kinda knew why Google Drive only allows to display and modify on the same hierarchical level. There are so many constraints that you have to consider when implementing this in a nested view with many nodes.
Fortunately, I wrote bullet points for each content piece when I implemented the software that I want to teach in the course. I know all too well what it means to put together all the marketing material at the last minute when you have no energy left.
However, since this is my first recorded course (I did only written content before), it really takes time and effort to make the videos high quality. That's the biggest struggle for me here, but every day I push through it! For every lesson that I need to record, I have a post-it on a cupboard and every evening I tear one or two of them off with my son :)
Edit: RSC = React Server Components - which come with their own read/write data philosophy.
https://www.amazon.com/Road-learn-React-pragmatic-React-js/d...
One year ago I had to design an API [0] for paginated nodes which also allows nested nodes. Overall there would be more than 100.000 nodes in the database.
On the UI side there would be a tree table to display the nodes. First you would fetch page 0 with 100 nodes and from there you could either perform a paginated fetch for the next page (page 1) or a nested fetch for page 0 for one of the initially fetched nodes. So essentially the API allows paginated and nested fetches where each nested fetch would be a paginated fetch too.
We used cursor based pagination, because there would be added and deleted nodes eventually in a collaborative environment. It was definitely a fun challenge!
I too released my first self-published book The Road to React on HN (initial in wrong English "The Road to learn React" haha) a few years ago and the community helped tremendously to get this project off the ground. Thanks to all of you! And I wish your success continues too :)
Hence I tried to combine async/await with catch for an improved readability [0] two years ago. Turns out I never used this approach, because it's not common sense when working in a team and still feels too verbose. Either one uses then/catch or async/await with try/catch. However, I still feel try/catch still makes code unattractive.
[0] https://www.robinwieruch.de/javascript-async-await-without-t...
- [0] https://vitejs.dev/guide/why.html#why-not-bundle-with-esbuil... - [1] https://vitejs.dev/
Website: https://www.robinwieruch.de GitHub: https://github.com/rwieruch
Mainly React.js for MVP Development, Large Scale Application Development, Workshops, Code Reviews/Audits
One year ago I had to do something similar and used Web Components (https://www.robinwieruch.de/react-web-components). Did you consider using Web Components or a Web Components library such as lit-html in the first place?
NB: Really refreshing how you created this timeline! You should make a (Gatsby) theme out of it :)
For sure, the easiest thing as a content creator is publishing (almost) ever green content (see web applications article). However, most often you are looking for topics that solve actual problems of your readers (see react testing library article) which often leads to bleeding edge technology which isn't document well yet.
For what it's worth, there will always be companies with money who pay people to write content to support their products (e.g. SaaS). This makes it harder every day for individuals like me to sustain their livelihoods. However, I strongly believe in the long run quality trumps quantity.
In a perfect world, there would be (1) one perfect learning material (e.g. official documentation) and (2) one unified learning style (e.g. text, video, both) for all students. But we are not living in a perfect world and therefore people look for resources outside of the box.
The last one I dropped was https://www.robinwieruch.de/web-applications which has more than 5000 words (1/6 of a book) of fundamentals in web development -- which took me 3 workdays of writing without anyone paying me for it. Still it gets less attention on Twitter than some random dev meme or inspirational dev tweet; and will probably not be picked up by HackerNews if anyone posts it ¯\_(ツ)_/¯
I do my best to teach people fundamentals. If they like my content on my blog, people buy my books/courses. This and their feedback (e.g. on Amazon, E-Mail) gives me confidence that I am doing the right thing. Without good content I don't get paid at the end of the month ...
Thanks for the shoutout @Pandabob! :)