@yuvalshimoni.bsky.social
Can you explain what is it for?
February 4, 2026 at 8:49 PM
Can you explain what is it for?
Can you share link?
January 26, 2026 at 2:47 AM
Can you share link?
Cursor agents have much better UX for those issues...
January 25, 2026 at 5:41 PM
Cursor agents have much better UX for those issues...
@danabra.mov Could you share how do you setup a project with Claude?
Do you give it to create it alone or strat it manually and after this the baseline you start to prompt?
Do you give it to create it alone or strat it manually and after this the baseline you start to prompt?
January 12, 2026 at 6:16 AM
@danabra.mov Could you share how do you setup a project with Claude?
Do you give it to create it alone or strat it manually and after this the baseline you start to prompt?
Do you give it to create it alone or strat it manually and after this the baseline you start to prompt?
Dan can you share why do use Claude over Cursor?
January 11, 2026 at 4:48 PM
Dan can you share why do use Claude over Cursor?
Can you explain it a bit more?
Which IDE is that?
Which IDE is that?
January 9, 2026 at 4:32 AM
Can you explain it a bit more?
Which IDE is that?
Which IDE is that?
Which e2e test do you use?
January 9, 2026 at 4:28 AM
Which e2e test do you use?
Dan can you share you Claude setup? Recommendations?
Workflows?
How do you keep your brain from stopping learning?
Workflows?
How do you keep your brain from stopping learning?
January 6, 2026 at 2:51 PM
Dan can you share you Claude setup? Recommendations?
Workflows?
How do you keep your brain from stopping learning?
Workflows?
How do you keep your brain from stopping learning?
How do you keep your learning path these days?
January 5, 2026 at 5:07 PM
How do you keep your learning path these days?
Dan, what’s your take on the recent hype around developing without an IDE—mostly with Claude? It feels magical, but I worry it atrophies core skills. The friction of working directly with code and files fuels learning, progress, and real understanding.
Maybe it not important anymore?
Maybe it not important anymore?
January 5, 2026 at 3:43 PM
Dan, what’s your take on the recent hype around developing without an IDE—mostly with Claude? It feels magical, but I worry it atrophies core skills. The friction of working directly with code and files fuels learning, progress, and real understanding.
Maybe it not important anymore?
Maybe it not important anymore?
Great read!!
Want to discuss it more? Would like to chat about it!
Want to discuss it more? Would like to chat about it!
December 27, 2025 at 7:30 PM
Great read!!
Want to discuss it more? Would like to chat about it!
Want to discuss it more? Would like to chat about it!
If that’s the case, what do you think it implies for the developer experience of languages, packages, and frameworks?
In some sense, the DX is no longer in the code — it’s in Claude!
In some sense, the DX is no longer in the code — it’s in Claude!
December 25, 2025 at 6:04 PM
If that’s the case, what do you think it implies for the developer experience of languages, packages, and frameworks?
In some sense, the DX is no longer in the code — it’s in Claude!
In some sense, the DX is no longer in the code — it’s in Claude!
That will be great.
December 25, 2025 at 4:08 PM
That will be great.
Cool. Thanks!
Can you describe a bit the beginning of the process?
Did you describe the stack? The folder structure? How does that looked like?
Can you describe a bit the beginning of the process?
Did you describe the stack? The folder structure? How does that looked like?
December 25, 2025 at 4:07 PM
Cool. Thanks!
Can you describe a bit the beginning of the process?
Did you describe the stack? The folder structure? How does that looked like?
Can you describe a bit the beginning of the process?
Did you describe the stack? The folder structure? How does that looked like?
Cool, so basically you don't do any manual code? Even the changes made thorough prompts?
December 25, 2025 at 2:10 PM
Cool, so basically you don't do any manual code? Even the changes made thorough prompts?
Do you use it through the terminal? How do you review the code and manage the workflow? Do you prompt in the terminal and then check the results in your IDE?
I’ve found it hard to stay involves and verify the output. Compared to Cursor, Claude feels much more vibe coding.. what do you feel?
I’ve found it hard to stay involves and verify the output. Compared to Cursor, Claude feels much more vibe coding.. what do you feel?
December 25, 2025 at 1:43 PM
Do you use it through the terminal? How do you review the code and manage the workflow? Do you prompt in the terminal and then check the results in your IDE?
I’ve found it hard to stay involves and verify the output. Compared to Cursor, Claude feels much more vibe coding.. what do you feel?
I’ve found it hard to stay involves and verify the output. Compared to Cursor, Claude feels much more vibe coding.. what do you feel?
Hey @danabra.mov can you share your development workflow with Claude code?
Form my experience it harder to be involved during the development versus Cursor..
Form my experience it harder to be involved during the development versus Cursor..
December 25, 2025 at 11:42 AM
Hey @danabra.mov can you share your development workflow with Claude code?
Form my experience it harder to be involved during the development versus Cursor..
Form my experience it harder to be involved during the development versus Cursor..
Yes you're right.
Bummer, styled components was such a great tool!
Bummer, styled components was such a great tool!
September 14, 2025 at 5:37 PM
Yes you're right.
Bummer, styled components was such a great tool!
Bummer, styled components was such a great tool!
Josh, I guess you'll find this post interesting www.sanity.io/blog/cut-sty...
Would like to hear your thoughts!
Would like to hear your thoughts!
styled-components maintenance mode: A 40% faster fork | Sanity
After styled-components entered maintenance mode, we forked it with React 18's useInsertionEffect. Result: 40% faster renders for Linear. Open source solution.
www.sanity.io
September 12, 2025 at 2:45 PM
Josh, I guess you'll find this post interesting www.sanity.io/blog/cut-sty...
Would like to hear your thoughts!
Would like to hear your thoughts!
So maybe it’s convenient to think of it like this:
'use client' → browser’s JS
Import me on the server where you need more than just HTML.
'use server' → server JS called via HTTP
Import me on the client where you want to trigger that HTTP call.
'use client' → browser’s JS
Import me on the server where you need more than just HTML.
'use server' → server JS called via HTTP
Import me on the client where you want to trigger that HTTP call.
June 9, 2025 at 8:21 PM
So maybe it’s convenient to think of it like this:
'use client' → browser’s JS
Import me on the server where you need more than just HTML.
'use server' → server JS called via HTTP
Import me on the client where you want to trigger that HTTP call.
'use client' → browser’s JS
Import me on the server where you need more than just HTML.
'use server' → server JS called via HTTP
Import me on the client where you want to trigger that HTTP call.
It's not about continuing the same flow -
It's about reducing the amount of work, and get client/server API out of the box.
It's about reducing the amount of work, and get client/server API out of the box.
June 9, 2025 at 8:01 PM
It's not about continuing the same flow -
It's about reducing the amount of work, and get client/server API out of the box.
It's about reducing the amount of work, and get client/server API out of the box.
On the other hand, 'use server' is more like:
I know I want to call specific server-side code — so instead of creating an API endpoint and calling it with fetch, I just add 'use server', and the bundler handles it for me.
I know I want to call specific server-side code — so instead of creating an API endpoint and calling it with fetch, I just add 'use server', and the bundler handles it for me.
June 9, 2025 at 8:00 PM
On the other hand, 'use server' is more like:
I know I want to call specific server-side code — so instead of creating an API endpoint and calling it with fetch, I just add 'use server', and the bundler handles it for me.
I know I want to call specific server-side code — so instead of creating an API endpoint and calling it with fetch, I just add 'use server', and the bundler handles it for me.
So we start building the *client* on the server (with JSX), and when we hit points that can't be handled on the server, we add 'use client'.
Meaning: "I can't run this code on the server, so when you get to the client — use me there."
Meaning: "I can't run this code on the server, so when you get to the client — use me there."
June 9, 2025 at 7:51 PM
So we start building the *client* on the server (with JSX), and when we hit points that can't be handled on the server, we add 'use client'.
Meaning: "I can't run this code on the server, so when you get to the client — use me there."
Meaning: "I can't run this code on the server, so when you get to the client — use me there."
What I'm trying to emphasize is that RSC enables sending a response that describes client things — an HTML document with JSX.
Want to add interactivity or behaviors to that?
Just add modules that can or should be executed on the client, right where you need them.
It's to continue the same flow!
Want to add interactivity or behaviors to that?
Just add modules that can or should be executed on the client, right where you need them.
It's to continue the same flow!
June 9, 2025 at 7:44 PM
What I'm trying to emphasize is that RSC enables sending a response that describes client things — an HTML document with JSX.
Want to add interactivity or behaviors to that?
Just add modules that can or should be executed on the client, right where you need them.
It's to continue the same flow!
Want to add interactivity or behaviors to that?
Just add modules that can or should be executed on the client, right where you need them.
It's to continue the same flow!