Louis
@lkapp.bsky.social
Cognitive Science 🧠 | Software Engineering 👨💻 | Former CTO of 4EIGN Talents ✈️
This is severely disturbing but I can't say I'm surprised
January 5, 2025 at 7:31 AM
This is severely disturbing but I can't say I'm surprised
I would argue that
1. recording a *good* video often takes longer than restructuring your commits before filing a PR.
2. having atomic and linear commits simplifies reviewing a subset of changes that are relevant to a specific context (commit msg).
Narrow scoping is hard and sometimes impossible 🤷♂️
1. recording a *good* video often takes longer than restructuring your commits before filing a PR.
2. having atomic and linear commits simplifies reviewing a subset of changes that are relevant to a specific context (commit msg).
Narrow scoping is hard and sometimes impossible 🤷♂️
November 28, 2024 at 7:34 AM
I would argue that
1. recording a *good* video often takes longer than restructuring your commits before filing a PR.
2. having atomic and linear commits simplifies reviewing a subset of changes that are relevant to a specific context (commit msg).
Narrow scoping is hard and sometimes impossible 🤷♂️
1. recording a *good* video often takes longer than restructuring your commits before filing a PR.
2. having atomic and linear commits simplifies reviewing a subset of changes that are relevant to a specific context (commit msg).
Narrow scoping is hard and sometimes impossible 🤷♂️
That's cool! Didn't know about this
November 28, 2024 at 7:23 AM
That's cool! Didn't know about this
Are you are calling this for every (re-)render of every component?
In React, this would be via a `useEffect` for every component or in some wrapper component, right? (I'm coming from Svelte, don't know much about React - pardon my noobness)
In React, this would be via a `useEffect` for every component or in some wrapper component, right? (I'm coming from Svelte, don't know much about React - pardon my noobness)
November 8, 2024 at 4:11 PM
Are you are calling this for every (re-)render of every component?
In React, this would be via a `useEffect` for every component or in some wrapper component, right? (I'm coming from Svelte, don't know much about React - pardon my noobness)
In React, this would be via a `useEffect` for every component or in some wrapper component, right? (I'm coming from Svelte, don't know much about React - pardon my noobness)
Convince more people to switch onto here from X!
Prime would probably do great 😁
Prime would probably do great 😁
November 8, 2024 at 3:23 PM
Convince more people to switch onto here from X!
Prime would probably do great 😁
Prime would probably do great 😁
Love Sentry btw, keep up the great work!
November 4, 2024 at 9:57 PM
Love Sentry btw, keep up the great work!
Yes, definitely tough because the other SDKs use the same method name 😄 Changing it just for Svelte could lead to confusion. I'll just stick with aliasing when importing.
`import { setContext as setSentryContext } from '@sentry/sveltekit';`
`import { setContext as setSentryContext } from '@sentry/sveltekit';`
November 4, 2024 at 9:57 PM
Yes, definitely tough because the other SDKs use the same method name 😄 Changing it just for Svelte could lead to confusion. I'll just stick with aliasing when importing.
`import { setContext as setSentryContext } from '@sentry/sveltekit';`
`import { setContext as setSentryContext } from '@sentry/sveltekit';`
Only something annoying with the SvelteKit SDK: `setContext` having the same name than Svelte's method for the Context API.
November 4, 2024 at 3:10 PM
Only something annoying with the SvelteKit SDK: `setContext` having the same name than Svelte's method for the Context API.