top | item 32993259

Ask HN: If you could have your tech team know one new thing

9 points| zemariagp | 3 years ago

I'm a FE at a growing e-commerce startup. We have a small but experienced team of engineers. I was asked to present something at our tech meeting (can be anything). If you could make all your colleagues aware of ONE new or less known concept/tool/lesson, what would it be? Could range from one terminal command to a new team methodology...

11 comments

order

solardev|3 years ago

Next.js. In 20 years of web dev, this is the single technology that's made me the happiest. It's the reason I chose to specialize in the FE and gave up the backend.

Coupled with a headless CMS (GraphQL is nice but not mandatory), this makes React a dream to work with, the pages super fast, the routing super simple, and the dev ex super fun.

One push to Vercel and you have a fully functional website, no AWS, Docker, Kubernetes, DNS, HTTPS, etc. to configure. It really is magic.

zemariagp|3 years ago

Yes, it’s a central part of our stack so I guess this one I can’t talk about, thanks anyway!

patatino|3 years ago

Which headless CMS do you prefer?

solardev|3 years ago

I learned about git "worktrees" the other day, which lets you have different branches of the same repo checked out at the same time. So, for example, you could have different node_modules/ folders (one per branch) and not need to reinstall them every time you switched. https://git-scm.com/docs/git-worktree

Sadly, the IntelliJ support for them was very weak (they worked, sort of, but project configurations etc. weren't copied over... it was essentially treated as a different project altogether).

I'm still not 100% sure how it's better than just checking out the same repo in different folders to begin with. But then again most of Git is totally confusing, lol.

zemariagp|3 years ago

container queries dude