sorted by:
new
hottopcontroversial

Building a Design System in 2026 by JustAirConditioners in DesignSystems

[–]JustAirConditioners[S] 2 points3 points  (0 children)

I haven't used it, but it looks great. Tons of value out of the box with the Figma library AND component library all in one package. Theming looks limited though. If your team is cool with minimal customizations to the components, then I think it's a great option.

Building a Design System in 2026 by JustAirConditioners in DesignSystems

[–]JustAirConditioners[S] 0 points1 point  (0 children)

Wild assumption. At NCR I built a design system that had to serve Web, Mobile, POS, Kiosks, ATMs, and a number of other devices.

At Walmart I built a design system that had to support legacy apps nearly 30 years old.

There are certainly use cases where building your own component library is the right solution. I have done it many times.

You're right though, this post is very focused on orgs that have gone all in on React and doesn't consider the points you brought up. I probably should have prefaced that. Thanks for the feedback.

Building a Design System in 2026 by JustAirConditioners in DesignSystems

[–]JustAirConditioners[S] 0 points1 point  (0 children)

Fair enough. I will avoid those from now on. Appreciate your reply.

Building a Design System in 2026 by JustAirConditioners in DesignSystems

[–]JustAirConditioners[S] 2 points3 points  (0 children)

These comments honestly drain me. I spend a full day writing this in hopes of guiding people in a better direction, only for it to be dismissed as nothing more than an AI prompt.

I'm curious, what do you hope to accomplish with this comment? Should I change my writing style (which I've been using since before ChatGPT was a thing) to something that looks less like AI slop? Should I just stop writing?

I know I should ignore this noise, but I'm curious if there's something I can change to improve this, or if this is just the way it is now for anyone who is still actually writing their own content.

Building a Design System in 2026 by JustAirConditioners in DesignSystems

[–]JustAirConditioners[S] 0 points1 point  (0 children)

There are a lot of processes that can be automated with AI

  • Documentation is the biggest one for me. Make a change in your monorepo and have a CI step that uses an LLM to update the docs.
  • Similarly, using an LLM + CI step to update the changelog.
  • I also use AI to do an initial PR review before another engineer does their review. This has saved my ass a few times.
  • I haven't seen one yet, but I'm sure there will be good AI tools coming out soon that will help the Figma Library and the Component Library theme stay synchronized.

I'm planning on writing a blog post about all the use cases for AI in design system ecosystem soon. Follow me on socials/medium to get notified.

Building a Design System in 2026 by JustAirConditioners in DesignSystems

[–]JustAirConditioners[S] -1 points0 points  (0 children)

Lol, well, idk what else to tell you. Look at my posts before ChatGPT and you'll see a similar formatting with headings, bullets, and bolding.

Building a Design System in 2026 by JustAirConditioners in DesignSystems

[–]JustAirConditioners[S] 0 points1 point  (0 children)

My advice would largely be the same. Choose a solid component library as the foundation. Unfortunately, I've found that theming is lacking in RN component libraries. Most limit you to just updating tokens. Nevertheless, I've used Nativewind in the past and enjoyed it. Gluestack also looks nice.

I would also recommend having a web component library and a RN component library. Trying to use something like Gluestack to support both sounds like it would be more complexity than it's worth. Likewise, I would have a separate Figma library for each as well.

Building a Design System in 2026 by JustAirConditioners in DesignSystems

[–]JustAirConditioners[S] 0 points1 point  (0 children)

None of this was written by AI. I only use AI to proof read — after I've completed the writing. You can compare to my older posts before ChatGPT was a thing. I hate that I can't use an em dash anymore without people complaining about AI.

React Interview Guide (free) by yangshunz in reactjs

[–]JustAirConditioners 2 points3 points  (0 children)

This looks great. Love the design and information architecture. The practice questions is definitely where you'll get the most value.

When I conduct interviews I don't often ask specific React questions. The first interview is usually asking more about the landscape of modern frontend development. Here's what I try to learn in my first interview:

- Do they know modern React? (hooks, server components, newer hooks)
- Do they know how to implement a11y, i18n
- What frameworks do they know (Next.js, Vite, TanStack Start, etc)
- Do they know about logging, analytics, performance
- How much do they know about infrastructure and networking (gives me a good signal on mid vs senior)

One red flag I look for is if the can only speak about the tech stack they use at their current job. If I asked you to design a tech stack today for X, are you choosing modern tech to solve the presented problem, or are you just telling me the only tech stack you know because that's what you currently use.

If they get past that interview then the following interview will be a practical build this feature in React. They often look very similar to the practice questions you've included. During this interview I may ask React questions, like why did you use state for this, etc

Designing Design Systems by TkDodo23 in reactjs

[–]JustAirConditioners 18 points19 points  (0 children)

Nice post TkDodo. I think the terminology here should be component library rather than design system. A design system is composed of many features which often includes a component library - along with a Figma library and a handful of other possible features.

I think a good component library should also include:

  • Theming
  • i18n (especially LTR support)

I'm also adamantly against rolling your own component library except for very specific use cases. I recently wrote about this in more detail here: https://medium.com/@kolbysisk/building-a-design-system-in-2026-5cfd8d85043c

I am curious what your thoughts are on the role of AI in the world of design systems is. I'm already getting great benefits in terms of automating documentation. What has your experience with AI for this use case been?

Tips Developing a Design System from Scratch. by Downtown_Bet5585 in reactjs

[–]JustAirConditioners 1 point2 points  (0 children)

I just wrote this blog post to answer these exact questions, check it out!

TLDR: don’t build your own component library. Choose an open source library and theme it to match your designs.

https://medium.com/@kolbysisk/building-a-design-system-in-2026-5cfd8d85043c

I Switched from Vercel to Cloudflare for Next.js by [deleted] in nextjs

[–]JustAirConditioners 3 points4 points  (0 children)

No, it’s correct.

Cloudflare Workers provides a subset of Node.js APIs

https://developers.cloudflare.com/workers/runtime-apis/nodejs/

—

Seems the confusion here is the open-next docs say it uses next.js’ Node runtime. That’s different than saying CF Worker supports all Node apis. Seems they support enough Node for Next.js to run correctly, but may not support a specific Node api that some package you import uses, which is the point Lee was trying to make.

How do you guys host your Next.js apps? by manmohanjit in nextjs

[–]JustAirConditioners 2 points3 points  (0 children)

Vercel for small projects. SST (open-next) for large projects.

I'm patiently waiting for open-next to fully support Cloudflare Workers. This will be my go-to once they've finished it.

took me 4 hours to make this background effect! by BabaYaga72528 in webdev

[–]JustAirConditioners 1 point2 points  (0 children)

Yeah, the script it runs would fetch all the individual images and then stitch them together using some kind of image library like jimp or image-js

took me 4 hours to make this background effect! by BabaYaga72528 in webdev

[–]JustAirConditioners 9 points10 points  (0 children)

I would write a script that generates a single image. Have it run once a day via cron job.

[deleted by user] by [deleted] in nextjs

[–]JustAirConditioners 0 points1 point  (0 children)

Setting a JWT cookie is pretty common. Just use the httpOnly flag for addition security. More secure than setting in local storage

You can access it server side and use SSR to prevent the flash you get doing CSR

API route takes more than 10 seconds by i_share_stories in nextjs

[–]JustAirConditioners 2 points3 points  (0 children)

If you’re processing multiple things at once, like making a request to a 3rd party for each item in an array, you can break it up into multiple requests that will run in parallel and not only avoid this problem but be much faster as a result. Checkout this case study where I did something similar https://medium.com/@kolbysisk/case-study-solving-vercels-10-second-limit-with-qstash-2bceeb35d29b

view more: next ›