davipon.bsky.social
Engineering lead @withdipp
36 posts
61 followers
170 following
Regular Contributor
Active Commenter
comment in response to
post
My previous struggle: turn on my PS5, start playing dragon’s dogma 2 for 5 min to recall how to play, and then turn off my PS5 because I was too tired.
This happened three times a week lol. I spend one year to finish the first round.
comment in response to
post
Would love to work on the Svelte integration!
comment in response to
post
With AI, I think it will be easier to perform various related job functions. Let’s see how it goes!
comment in response to
post
I firmly believe that “better DX leads to better UX”.
A few years ago, Svelte enabled me to explore different aspects of a product.
That's why I always see myself as a product engineer.
comment in response to
post
The coolest part, we all agree that I’ll keep coding especially the Svelte part!
comment in response to
post
It's often not the case for startups. Even a CTO may not know when a pivot is necessary, and it’s challenging for a team to change the tech stack every time they pivot.
comment in response to
post
"Easier to recruit" depends on the recruiting process.
From a hiring manager's perspective, an exceptional engineer can quickly learn Svelte.
Imagine a seasoned React developer joining a new team. They need to learn patterns and libraries. The learning curve may be steeper than learning Svelte.
comment in response to
post
100% agree.
Some factors are complex to elaborate on in the article.
In React, the data model layer(which contains many classes) and render engine are separated.
I can’t tell how excited I was when I learned we can use runes in class.
comment in response to
post
Sometimes, comparing the technical differences between X & Y is not enough to make migration happen, so I also wrote about human factors and challenges we faced, and how to communicate with stakeholders as a Svelte evangelist.
comment in response to
post
(I am really bad at crafting engaging tweets.)
After many great conversations during the Svelte Summit, I realize we need to share more migration stories like ours and the one from "hackerman" @bertbengtson.bsky.social to help the community grow.
comment in response to
post
To have a more consistent result, we used cursor rules/ windsurf rules to force the AI to pick up.
comment in response to
post
The first and second options sometimes do not work well. The third option works way better.
comment in response to
post
It’s time to create new recipes for the new @sveltesociety.dev website!
comment in response to
post
When I found out that you would be talking about TanStack at the Svelte Summit.
comment in response to
post
🧡
comment in response to
post
Later 😏
comment in response to
post
Does it include any use cases for nvim or terminal usage? I would love to know!
comment in response to
post
You can try using the resource utility function.
I did implement nested resources before, but I ended up avoiding this situation as much as possible.
comment in response to
post
@tanstack/svelte-query is probably the answer, but it's not Svetle 5 ready.
I'm working on a simple hook utilizing url search params, which can be integrated in the load function.
bsky.app/profile/davi...
comment in response to
post
The utility function in the link is not for isomorphic loaders.
> seed that server data into the client for that same initial query
That's the default behavior of SK loader, but it's not fine-grained if you want to do partial invalidation (not rerun the whole load function).
comment in response to
post
I made this a while ago: runed.dev/docs/utiliti...
Partial loader/ invalidation is likely the ideal solution for SK.
comment in response to
post
+1, restarting LSP is probably the most annoying part. (yet to find a solution)
comment in response to
post
Doc: runed.dev/docs/utiliti...
comment in response to
post
Noice!