I’m definitely there too. Used to take every one that applied to me. But there are just so many. I also used to read the results and all the reactions and all the insights. But now it feels like I can’t keep up. Ironically, now is when I’m a position where it might be useful.
November 17, 2025 at 8:11 AM
I’m definitely there too. Used to take every one that applied to me. But there are just so many. I also used to read the results and all the reactions and all the insights. But now it feels like I can’t keep up. Ironically, now is when I’m a position where it might be useful.
Wow! Aamir sounds so excited to write more articles about auto sales that they’re asking the readers if they can write more. Such dedication to quality journalism
November 17, 2025 at 4:23 AM
Wow! Aamir sounds so excited to write more articles about auto sales that they’re asking the readers if they can write more. Such dedication to quality journalism
Caching is way too complicated to use a directive. A wrapper function imported from the framework that has types would be /way/ better. The framework is handling it. I don’t care if it’s a bundler thing, a runtime thing, or a JS thing. I hand Next a function and it /wraps/ it with cache magic
November 5, 2025 at 3:59 AM
Caching is way too complicated to use a directive. A wrapper function imported from the framework that has types would be /way/ better. The framework is handling it. I don’t care if it’s a bundler thing, a runtime thing, or a JS thing. I hand Next a function and it /wraps/ it with cache magic
I like how you explain directives in this thread. And for module scope it’s definitely better. What infuriates me about directives is their limited api. Next has “use cache” but needs cacheLife and cacheTag void functions. Which look like functions but aren’t! Exactly your point.
November 5, 2025 at 3:55 AM
I like how you explain directives in this thread. And for module scope it’s definitely better. What infuriates me about directives is their limited api. Next has “use cache” but needs cacheLife and cacheTag void functions. Which look like functions but aren’t! Exactly your point.
I’d love it if “the composer” wasn’t a full screen experience. Yes take me to the thread first, but let me scroll it while I compose. Just give me small text box above the keyboard and keep the OP in view and thread scrollable
November 1, 2025 at 5:09 AM
I’d love it if “the composer” wasn’t a full screen experience. Yes take me to the thread first, but let me scroll it while I compose. Just give me small text box above the keyboard and keep the OP in view and thread scrollable
It can be a pendulum swing from being overly cautious to overly reckless. Right now in my work we’re overly cautious so I’m feeling it. I just want to stop the pendulum from swinging so far. And ship code again.
October 29, 2025 at 7:13 PM
It can be a pendulum swing from being overly cautious to overly reckless. Right now in my work we’re overly cautious so I’m feeling it. I just want to stop the pendulum from swinging so far. And ship code again.
How do you maintain this after you have your first few major mistakes? I feel like this culture is the ideal and a lot of projects/companies start out this way. Then you get users/clients and you fuck things up for them one too many times and then you have to dial back the speed for safety.
October 29, 2025 at 7:12 PM
How do you maintain this after you have your first few major mistakes? I feel like this culture is the ideal and a lot of projects/companies start out this way. Then you get users/clients and you fuck things up for them one too many times and then you have to dial back the speed for safety.
JSDoc isn’t really anything without Typescript’s LSP. They aren’t competitors, they’re team mates. They build off of each other. If you want to just use JSDoc and no build step then just do it. And then thank the Typescript team for making it good. Don’t complain about its existence.
October 26, 2025 at 1:13 AM
JSDoc isn’t really anything without Typescript’s LSP. They aren’t competitors, they’re team mates. They build off of each other. If you want to just use JSDoc and no build step then just do it. And then thank the Typescript team for making it good. Don’t complain about its existence.
The craziest thing about this study is the exit interviews: “even after experiencing the slowdown, they still believed AI had sped them up by 20%.” This means we can’t trust anyone who says, “well it makes /me/ faster.” Have you measured? Are you sure? How do you know?
October 20, 2025 at 5:45 AM
The craziest thing about this study is the exit interviews: “even after experiencing the slowdown, they still believed AI had sped them up by 20%.” This means we can’t trust anyone who says, “well it makes /me/ faster.” Have you measured? Are you sure? How do you know?
My teammates use it exactly as you described. Nothing major. Some code completion, some pure functions, some boilerplate. Moderate to no gains in productivity. Except the slackers use it too much and in the wrong areas. Easier to pick up code smells actually if it smells like AI Slop
October 16, 2025 at 8:03 AM
My teammates use it exactly as you described. Nothing major. Some code completion, some pure functions, some boilerplate. Moderate to no gains in productivity. Except the slackers use it too much and in the wrong areas. Easier to pick up code smells actually if it smells like AI Slop
I find myself coming back to those research threads because the context already in there is valuable. It already heard my objections to the standard stuff, there errors I hit, and my special considerations.
But my job is to blaze trails and bring new tech to the team. Not the normal use case
But my job is to blaze trails and bring new tech to the team. Not the normal use case
October 16, 2025 at 8:01 AM
I find myself coming back to those research threads because the context already in there is valuable. It already heard my objections to the standard stuff, there errors I hit, and my special considerations.
But my job is to blaze trails and bring new tech to the team. Not the normal use case
But my job is to blaze trails and bring new tech to the team. Not the normal use case
I use it when I don’t know where to start. When I’m first researching a completely new skill/technology. Use it as a jumping off point for further research elsewhere and come back to ask it follow up questions. Then once I’ve decided how to proceed it writes some boilerplate to get me started
October 16, 2025 at 7:59 AM
I use it when I don’t know where to start. When I’m first researching a completely new skill/technology. Use it as a jumping off point for further research elsewhere and come back to ask it follow up questions. Then once I’ve decided how to proceed it writes some boilerplate to get me started
Have you tried @htmx.org? Very minimal, html attribute based, no build, extremely powerful. I don’t actually know the nuanced differences because I’ve never used Alpine. But I know they have the same goals, so if Alpine is interesting to you htmx probably will be as well.
October 14, 2025 at 5:01 AM
Have you tried @htmx.org? Very minimal, html attribute based, no build, extremely powerful. I don’t actually know the nuanced differences because I’ve never used Alpine. But I know they have the same goals, so if Alpine is interesting to you htmx probably will be as well.
I think saying “an SQLite” should get you voted off. Putting the “n” in “an” implies you’re saying “ess”. But then are you saying “ess-cue-light”, or “ess-cue-ell-aight”. I have to know
Or maybe you’re just a maniac and saying “an sequelite” like a weird tongue twister
Or maybe you’re just a maniac and saying “an sequelite” like a weird tongue twister
October 9, 2025 at 7:27 AM
I think saying “an SQLite” should get you voted off. Putting the “n” in “an” implies you’re saying “ess”. But then are you saying “ess-cue-light”, or “ess-cue-ell-aight”. I have to know
Or maybe you’re just a maniac and saying “an sequelite” like a weird tongue twister
Or maybe you’re just a maniac and saying “an sequelite” like a weird tongue twister
This. It just shifts the trust. We already trust our influencers more than the large corps. So why would we trust the signing authority of adobe, canon, Apple, Samsung? It just takes one recognizable face saying “you know they can fake those” to erode all trust in what they already don’t understand
October 8, 2025 at 4:07 PM
This. It just shifts the trust. We already trust our influencers more than the large corps. So why would we trust the signing authority of adobe, canon, Apple, Samsung? It just takes one recognizable face saying “you know they can fake those” to erode all trust in what they already don’t understand