@zachlloydtweets Meanwhile I switched away from Warp cause I wanted it do more for me. Adapt more to my workflows cause it already has base ingredients to be a great IDE plus cli, but the focus seems to be elsewhere.
@rauchg Do you see a need UI elements/components as an artifact or output of having conversation with natural language? Are you limiting this just to input or output also. i.e Generative UI
@kenwheeler I vibe code with @Replit and when I can’t anymore I switch over to @cursor_ai, the code that get’s generated is so hard to grasp. But never in my life have I ever been able to build sth and test it with actual users this fast whilst keeping a 9-5. This is still a huge win.
@mattpocockuk@AdamSuskin File by file on a large project is unattainable and leaves room for complacency. Go for one full sweep and retrospectively fixing and adding types over time imo works better.
@AdamRackis You can use Signals I believe in React but probably on your own peril https://t.co/pyuesN02fk
Read somewhere that it is patching some of the internals of react and never looked further or thought about using it.
@bella_artur@kettanaito@_MichaelMusil@jon_neal Ppl are assuming everyone runs vitest on a Mac, give it a whirl in windows and that's a separate kind of pain. We tried, we failed and now we are burnt
@cnakazawa I normally formulate a rough plan for the day, whilst working out in the morning, seems to work 90% of the time as you can carry the energy from your workouts into the day and have a set plan for the day in your head. The other 10% of time life happens.
@t3dotgg You can do full stack type safety if people are using graphql without having to write server side code. So maybe it's just ppl who don't like types.
@grabbou I tried this but YouTube and Twitter are overall value added, the rest definitely are built to grab and take hold of your attention mindlessly. Although I could do with blocking shorts on YouTube. Short form videos are where the attention pitfalls are.
@LadyBluenotes I have written something similar, this pattern is used in quite a few open source libraries when inferring types of nested properties in an object. I don't think there is any way around the problem hence you end up with this. It's simple yet overwhelming.
@evanyou Honest feedback we saw the same issue with vite, usage of React Lazy helped. The subsequent reloads were better but the initial load was no different to our webpack setup. Obviously the caveats being there could set up issues on our end, but that was reality for us.
@bjeaurn@mattpocockuk If you turn the strictness all the way up, it requires a shift in how you write code, so fixing would probably add only more tech debt. The best bet I have seen so far is to turn strictness all the way up on new files with a plugin, and tackle old features along. Messy IMHO