sophie alpert
@sophiebits.com
you have the ability to understand things
principal engineer, react person, super gay, still masking
principal engineer, react person, super gay, still masking
h/t @simonwillison.net for writing a lot about AI security
September 9, 2025 at 8:09 PM
h/t @simonwillison.net for writing a lot about AI security
yes! I didn’t realize until this week that it used similar techniques
August 25, 2025 at 3:12 AM
yes! I didn’t realize until this week that it used similar techniques
no need to deviate from the style you use for everyone!
August 23, 2025 at 8:35 PM
no need to deviate from the style you use for everyone!
love it! (btw I use she/her pronouns)
August 23, 2025 at 8:12 PM
love it! (btw I use she/her pronouns)
probably cases where all three make sense! I know some providers eg Materialize also offer subscriptions on top of materialized views so you can have both in the same system
August 23, 2025 at 6:45 AM
probably cases where all three make sense! I know some providers eg Materialize also offer subscriptions on top of materialized views so you can have both in the same system
I wonder why you still need memory turned on at the account level to enable it!
August 23, 2025 at 2:45 AM
I wonder why you still need memory turned on at the account level to enable it!
right now I'm at Clay! hiring mostly in NYC and SF only for now www.clay.com/jobs
Open roles at Clay | Clay.com
www.clay.com
August 23, 2025 at 1:34 AM
right now I'm at Clay! hiring mostly in NYC and SF only for now www.clay.com/jobs
"there’s no way to get at those thinking traces via the API; all you get is silence" — this isn't true, you can pass {"reasoning": {"summary": "auto"}} in Responses API to get similar "thinking summaries" streamed
August 7, 2025 at 5:49 PM
"there’s no way to get at those thinking traces via the API; all you get is silence" — this isn't true, you can pass {"reasoning": {"summary": "auto"}} in Responses API to get similar "thinking summaries" streamed
you gotta say which processes!
July 23, 2025 at 6:02 PM
you gotta say which processes!
if you’re seeing it in screen recordings then it’s probably this
if you’re seeing it IRL then idk maybe something else
if you’re seeing it IRL then idk maybe something else
July 17, 2025 at 9:28 PM
if you’re seeing it in screen recordings then it’s probably this
if you’re seeing it IRL then idk maybe something else
if you’re seeing it IRL then idk maybe something else
(logos are kimi, deepseek, qwen, openai, anthropic, gemini)
July 12, 2025 at 2:22 AM
(logos are kimi, deepseek, qwen, openai, anthropic, gemini)
A provider component like in your screenshot makes this mostly moot.
July 7, 2025 at 4:27 AM
A provider component like in your screenshot makes this mostly moot.
so that if `theme` changes and App rerenders, then it won’t also rerun MainContent and its children and their children, just the descendants that actually listen to the theme.
July 7, 2025 at 4:26 AM
so that if `theme` changes and App rerenders, then it won’t also rerun MainContent and its children and their children, just the descendants that actually listen to the theme.
I’m pretty sure what I meant is like if you have
function App() {
const [theme, setTheme] = useState();
return (
<ThemeContext value={theme}>
<MainContent route={…} />
</ThemeContext>
);
}
then you want MainContent to have a memo()…
function App() {
const [theme, setTheme] = useState();
return (
<ThemeContext value={theme}>
<MainContent route={…} />
</ThemeContext>
);
}
then you want MainContent to have a memo()…
July 7, 2025 at 4:26 AM
I’m pretty sure what I meant is like if you have
function App() {
const [theme, setTheme] = useState();
return (
<ThemeContext value={theme}>
<MainContent route={…} />
</ThemeContext>
);
}
then you want MainContent to have a memo()…
function App() {
const [theme, setTheme] = useState();
return (
<ThemeContext value={theme}>
<MainContent route={…} />
</ThemeContext>
);
}
then you want MainContent to have a memo()…
you’re just like Padparadscha
May 31, 2025 at 3:58 PM
you’re just like Padparadscha
Reposted by sophie alpert
every time you think "maybe I should add a layer of caching in the application", take that energy and make the database faster instead
May 7, 2025 at 12:10 AM
every time you think "maybe I should add a layer of caching in the application", take that energy and make the database faster instead
may not be production ready but github.com/lolopinto/ent
GitHub - lolopinto/ent
Contribute to lolopinto/ent development by creating an account on GitHub.
github.com
May 7, 2025 at 1:34 AM
may not be production ready but github.com/lolopinto/ent
every time you think "maybe I should add a layer of caching in the application", take that energy and make the database faster instead
May 7, 2025 at 12:10 AM
every time you think "maybe I should add a layer of caching in the application", take that energy and make the database faster instead