Sourav Kumar Nanda
0 followers · 8 following · 828 views
on the atlas · 37
- Understanding useMemo and useCallback2 savers
- Making Sense of React Server Components3 savers
- We migrated 50,000 lines of code to React Server Components1 savers
- The Fermi Paradox11 savers
- Why We Eat Popcorn at the Movies1 savers
- How To (Really) Become Better At What You Do Every Single Day | by Tim Rettig | The Startup | Medium1 savers
- A Contrarian’s Guide to Hiring - by Mario Gabriele1 savers
- You're probably wrong about how things have changed3 savers
- Absolute Success is Luck. Relative Success is Hard Work.1 savers
- Search My Site - Browse Sites1 savers
- Map of my Internet7 savers
- Blogroll - Dan MacKinlay2 savers
- Tending to My Digital Garden | Tania Rascia2 savers
- Threaded thinking instead of linear thinking • Mental Nodes2 savers
- interoperable visions1 savers
- Navigating the future of frontend1 savers
- What kind of software engineer should I become?1 savers
- Why T-shaped people?. A T-shaped person is capable in many… | by Jason Yip | Medium1 savers
- XMTP Support – frames.js1 savers
- Anything wrong with Express? What's so good about hono.js? : r/node1 savers
- Profile: surprisetalk | Hacker News1 savers
- blogs.hn1 savers
- taylor.town4 savers
- Ye Olde Blogroll - Blogroll.org2 savers
- ooh.directory6 savers
- flashcasts1 savers
- Hono v4.0 | Hacker News1 savers
- Nadia Asparouhova | Explaining tech's notion of talent scarcity17 savers
- Ask HN: Is it better to generalise or specialise as a developer? | Hacker News1 savers
- Wanted: Smart Generalists2 savers
- Networked Thought22 savers
- Post 34: Learning how to learn — Neel Nanda20 savers
- My website is a shifting house next to a river of knowledge. What could yours be? – The Creative Independent14 savers
- Internet as Practice - by Dan Hunt - Becoming Storyless11 savers
- Reading Comprehension: How to Retain More of Every Book You Read7 savers
- README - A story of magic6 savers
- Rediscovering the Old Internet Vibe — Noisy Deadlines2 savers
highlights · 92
The main thing that React does is keep our UI in sync with our application state. The tool that it uses to do this is called a “re-render”.
Understanding useMemo and useCallbacksemantic HTML principles
Making Sense of React Server ComponentsServer Components don't run on the client, their code isn't included in our JavaScript bundles.
Making Sense of React Server ComponentsAs a general rule, if a component can be a Server Component, it should be a Server Component.
Making Sense of React Server Componentswe can't use effects because effects only run after the render, on the client, and Server Components never make it to the client.
Making Sense of React Server Componentsa big chunk of React's API is incompatible with Server Components. For example, we can't use state, because state can change, but Server Components can't re-render.
Making Sense of React Server ComponentsServer Components never re-render. They run once on the server to generate the UI.
Making Sense of React Server Components“Function components can't be asynchronous! And we're not allowed to have side effects directly in the render like that!”
Making Sense of React Server Componentsmost SSR/SSG approaches send all the JavaScript used to generate the page to the client, where the client then runs it all again and marries that HTML with the JavaScript that just booted up. (This marriage, by the way, is called hydration — a term you’ll see a lot in this neck of the woods.)
We migrated 50,000 lines of code to React Server ComponentsTypically, React applications need to be compiled, transforming JSX into plain ol’ JavaScript, and bundling all of our modules. What if, during that same process, we “pre-rendered” all of the HTML for all of our different routes?
Making Sense of React Server ComponentsServer Side Rendering was designed to improve this experience. Instead of sending an empty HTML file, the server will render our application to generate the actual HTML. The user receives a fully-formed HTML document.
Making Sense of React Server ComponentsOnce the JS has been downloaded and parsed, React springs into action, conjuring all of the DOM nodes for our entire application, and housing it in that empty .
Making Sense of React Server Components“Server Side Rendering” is an umbrella term that includes several different rendering strategies. They all have one thing in common: the initial render happens in a server runtime like Node.js, using the ReactDOMServer APIs. It doesn't actually matter when this happens, whether it's on-demand or at compile-time. Either way, it's Server Side Rendering.
Making Sense of React Server ComponentsUser visits myWebsite.com. A Node.js server receives the request, and immediately renders the React application, generating the HTML. That freshly-baked HTML is sent to the client.
Making Sense of React Server ComponentsA server generates the initial HTML so that users don't have to stare at an empty white page while the JS bundles are downloaded and parsed. Client-side React then picks up where server-side React left off, adopting the DOM and sprinkling in the interactivity.
Making Sense of React Server ComponentsHydration is like watering the “dry” HTML with the “water” of interactivity and event handlers.
Making Sense of React Server Componentsinstead of conjuring all of the DOM nodes from scratch, it instead adopts the existing HTML. This process is known as hydration.
Making Sense of React Server ComponentsOne company, also per Smithsonian, accidentally proved the point: “a Dallas movie theater chain [ . . . ] installed popcorn machines in 80 theaters, but refused to install machines in their five best theaters, which they considered too high class to sell popcorn. In two years, the theaters with popcorn saw their profits soar; the five theaters without popcorn watched their profits go into the red.”
Why We Eat Popcorn at the MoviesIn 1929, though, that began to change. The Great Depression gripped American society and like everyone else, movie theaters were feeling the pinch of lower demand. Unless they modified their business models, they’d be at risk of bankruptcy.
Why We Eat Popcorn at the MoviesPopcorn allowed the movie theaters to survive.
Why We Eat Popcorn at the MoviesIn 1885, a Chicago inventor named Charles Cretors developed a way to pop kernels using steam and without the need of a kitchen
Why We Eat Popcorn at the Movieswhose idea was it to sell popcorn in movie theaters?
Why We Eat Popcorn at the MoviesAbsolute success is luck. Relative success is choices and habits.
Absolute Success is Luck. Relative Success is Hard Work.A tool’s capability is its ability to express ideas.
Navigating the future of frontenda “t-shaped person” is an expert in at least one thing but also somewhat capable in many other things.
Why T-shaped people?. A T-shaped person is capable in many… | by Jason Yip | MediumCross-protocol frames are supported by frames.js
XMTP Support – frames.jsfast = fast routing / throughput lightweight = small code size web standards = not node apis (fetch, not http.createClient, etc.) runs on any JS runtime = runs in deno/node/bun/workers/etc
Hono v4.0 | Hacker NewsStatic site generation (SSG) would mean certain routes compile at build time and the worker won't compute them on the edge. Client components means they now support client side rendering (CSR), before Hono was only used for server side rendering (SSR). File-based routing is instead of coding your paths, the folder structure is used for routing, similar to Next which mimics how traditional http web serving works.
Hono v4.0 | Hacker NewsThey added 3 major features: - Static Site Generation - Client Components - File-based Routing
Hono v4.0 | Hacker Newsyou can't run traditional http servers in edge sandbox worker environments
Hono v4.0 | Hacker Newsit's a much faster, leaner, express.js on the edge.
Hono v4.0 | Hacker News“Writing about something, even something you know well, usually shows you that you didn’t know it as well as you thought.”
Super Specific Feedback: How to give actionable feedback on work outputIt’s much easier to share feedback with an annotated screenshot than trying to describe via words alone.
Super Specific Feedback: How to give actionable feedback on work outputIf you’re not sure what the change should be, but know there’s something awkward about the work, add a comment and ask them to take another look
Super Specific Feedback: How to give actionable feedback on work outputWhenever you have an insight or think something could be better, get used to sharing it out loud.
Super Specific Feedback: How to give actionable feedback on work outputIf what you get is far from what you expected, do not give line edits. Give structural feedback first.
Super Specific Feedback: How to give actionable feedback on work outputBe direct with both constructive and positive feedback.
Super Specific Feedback: How to give actionable feedback on work outputDon’t just say "This doesn't work." Share your explanation of the improvement that needs to be made, and also the bigger thinking behind the “why” and “how.
Super Specific Feedback: How to give actionable feedback on work outputIf you haven’t been giving a lot of feedback and start to all of a sudden, folks might wonder where this is coming from.
Super Specific Feedback: How to give actionable feedback on work outputSuper Specific Feedback is extremely concrete feedback primarily on work output, such as writing, product flows, marketing assets, and design. The goal is to strengthen the work product to get it closer to ship ready, and to help the feedback recipient improve their craft and judgment over time.
Super Specific Feedback: How to give actionable feedback on work outputIt’s extremely valuable to be a player-coach. A player-coach is a leader who can actually do the job, not just shout instructions from the sidelines.
Super Specific Feedback: How to give actionable feedback on work outputComputers and subsequently the internet started as machines for answering questions: first, “1+1 = ?” and then, “Where’s the closest Walmart?,” “Give me directions to Fenway Park,” and now, “ChatGPT, write a 20-line poem on the nature of capitalism in the style of Robert Frost.”
Internet as Practice - by Dan Hunt - Becoming StorylessWhenever you stumble upon an interesting thought on another site, write about it and link to it.
Into the Personal-Website-Verse · Matthias Ott – User Experience Designerhow about adding a little section or page to your site that does exactly the same? Link to the personal websites of people you respect and appreciate, maybe with a little description?
Into the Personal-Website-Verse · Matthias Ott – User Experience DesignerPersonal websites are the backbone of the independent Web of creators.
Into the Personal-Website-Verse · Matthias Ott – User Experience DesignerAlso, don’t hesitate to write about little ideas and observations that might seem too small or unimportant to share. We all have our unique perspectives and even the smallest experience is worth sharing.
Into the Personal-Website-Verse · Matthias Ott – User Experience DesignerA home on the internet. A place to tell your story.
Into the Personal-Website-Verse · Matthias Ott – User Experience DesignerNow imagine, for a moment, an environment where a decentralized fabric of connected personal sites allows everyone to publish their own content
Into the Personal-Website-Verse · Matthias Ott – User Experience DesignerThe personal website. It’s a place to write, create, and share whatever you like, without the need to ask for anyone’s permission.
Into the Personal-Website-Verse · Matthias Ott – User Experience DesignerYour content is one of your most valuable assets and thus owning it is invaluable.
Into the Personal-Website-Verse · Matthias Ott – User Experience Designer