Location: Philippines
Remote: Yes
Willing to relocate: No
Technologies: React.js, Next.js, Typescript, Prisma, Tailwind CSS
Résumé/CV: https://www.linkedin.com/in/jopsima
Email: [email protected]
I'm primarily a frontend-leaning developer, but I've got solid experience on the backend too. Unlike the average junior who requires constant hand-holding, I'm quick to pick up new technologies. You could throw me into the deep end, and I'd figure out how to swim in no time.
I'm currently building a project using App Router. Here are my thoughts so far:
1. In React Server Components, you fetch data at the component level instead of route level. You can pass the data down as props if it's a client component.
2. I'm not sure if HMR is faster in Pages, but in App Router it tends to be slow. I always use --turbo to see changes quickly, but it can still be a bit buggy.
3. I just found out that using "use client" directive isn't actually sending 100% javascript to the client. It's just a replacement of serverSideProps. The component is rendered both on the server and the client, which can be confusing at first. You can disable SSR using dynamic imports.
4. I actually like Route Groups, best feature by far.
I rarely see SQL Server being used alongside Next.js. But Prisma is quite popular in js land. There's also DrizzleORM, which is still relatively new. I'd recommend spending some time exploring both to see what fits you best :)
I'm primarily a frontend-leaning developer, but I've got solid experience on the backend too. Unlike the average junior who requires constant hand-holding, I'm quick to pick up new technologies. You could throw me into the deep end, and I'd figure out how to swim in no time.
My projects are available on my GitHub profile (https://github.com/jahriko)