Just released Bonded, a track inspired by the bond between me and my Golden Retriever, Mëllon. Now streaming on all platforms. ✨ https://t.co/l8tuxxn9x3
@Soul0Engineer Travel would expose one to other perspectives, and one could be surprised at how pleasant new perspectives are, and choose to stay.
Innovation would facilitate traveling, but what variable would be the equivalent to traveling?
@zancan Money, which is “preventing” you to take the leap, will stream in as a powerful river once you get the right conditions around you. As long as you stay in a toxic home, it will remain a trickle. Get out of the toxicity and live the life you’re meant to.
@zancan Mike, for everyone’s sake: get the f out of there. It’s not worth it. I was a kid of an alcoholic father, and all I can fantasize about is how better my childhood would’ve been if my mum just left. She didn’t, and the darkness got darker, and we’re not better for it! Do it.
@CollinRugg@HannahPThomas Old man getting older. Nothing to see here. But ppl at this rank should pass the basic cognitive tests. Answering questions should be one of them.
@wintercounter1@housecor@ApiMocking I also tend to put everything in one config. When values aren’t secret, I write unit tests for the most crucial values, which is a way to avoid breakage.
@sathvikcheela@housecor@ApiMocking I see a caveat. Say you’re using ‘user.getById’ and ‘product.getById’ concurrently and want to deconstruct, you won’t be able to use both ‘getById’ at the same time. Minor detail, though.
@AdamRackis@samijaber_ createServerContext is not what you think it is, but let’s not get into that as it doesn’t help with the case you’re describing.
import { cache } from “react” is the way to go. However, let’s dig into why that is the way to go and how it works. I’ll refer to it as cache()
React: The Most Common Mistakes in 2023
I'm presenting this talk at @kc_dc in July!
The list:
State:
Needless state
Global state overuse
Syncing state via useEffect
Reading state after setting it
Multiple setState calls in a row
Putting state in the wrong spot
Storing related data in separate pieces of state
Http:
Not caching
Fetching in useEffect
Not using modern libraries
Workflow:
Not using a framework
Not using Tailwind
Not using TypeScript
Not mocking
Ineffective testing
Not using custom dev tools
Poor folder structure
Few/poor reusable components
Weak ESLint rules
Weak error handling
What else would you put on this list?
I use @playwrightweb or @Cypress_io to write 2 types of tests:
1. End-to-end tests
Goal: Load each page to assure the app works against the real APIs. Don't assert specific data. Be deliberately high-level. Think "smoke test".
2. Integration tests
Goal: Assure each feature works as expected and displays the right data in the right spot. Run the app against mock APIs via msw so it's reliable and fast. These tests are thorough and specific.
With a heavy heart, we are sunsetting Windi CSS and recommending new projects to seek alternatives. We are grateful to the entire Windi CSS community for your unwavering support, enthusiasm, collaboration, and sponsorship. Thank you 🙏
https://t.co/BIifcVhf9X
@dan_abramov GROQ, by @sanity_io, is pretty ingenious. Not as simple as it would seem at first, but the queries combined with the speedy responses makes @GraphQL a bit envious