Aaron Hammer
@athammer.bsky.social
senior software engineer @Square Payment Links and Ecom Checkout • #buildinpublic • i tweet only about tech and web dev stuff so follow for that
frontend interviews are harder than backend ones.
frontend interviews are often web api trivia or a test to see how fast you can do x not about knowledge.
i absolutely hate it
frontend interviews are often web api trivia or a test to see how fast you can do x not about knowledge.
i absolutely hate it
April 6, 2025 at 1:55 AM
frontend interviews are harder than backend ones.
frontend interviews are often web api trivia or a test to see how fast you can do x not about knowledge.
i absolutely hate it
frontend interviews are often web api trivia or a test to see how fast you can do x not about knowledge.
i absolutely hate it
advancing through software engineering for me is realizing that game code, library code, application code, and research code are all entirely different
once I realized that I stopped wondering why people would always recommend crazy over complicated patterns
once I realized that I stopped wondering why people would always recommend crazy over complicated patterns
March 26, 2025 at 2:31 AM
advancing through software engineering for me is realizing that game code, library code, application code, and research code are all entirely different
once I realized that I stopped wondering why people would always recommend crazy over complicated patterns
once I realized that I stopped wondering why people would always recommend crazy over complicated patterns
scariest thing a developer can see 🫣
February 21, 2025 at 3:13 AM
scariest thing a developer can see 🫣
I see no reason not to use tanstack start, unless your use case screams otherwise.
February 16, 2025 at 8:33 AM
I see no reason not to use tanstack start, unless your use case screams otherwise.
I’m starting to use array prototype methods such as map, filter, reduce less and less in favor of “const for each”
unless I’m chaining them I feel like it’s just more readable.
unless I’m chaining them I feel like it’s just more readable.
February 1, 2025 at 5:39 AM
I’m starting to use array prototype methods such as map, filter, reduce less and less in favor of “const for each”
unless I’m chaining them I feel like it’s just more readable.
unless I’m chaining them I feel like it’s just more readable.
I often try to use non iso dates and always realize it’s just better to use ISO all the way through and derive what you need off of it.
managing two different time formats is just too painful
managing two different time formats is just too painful
January 15, 2025 at 11:40 PM
I often try to use non iso dates and always realize it’s just better to use ISO all the way through and derive what you need off of it.
managing two different time formats is just too painful
managing two different time formats is just too painful
people are really sleeping on atom based state management like Jotai impo.
it’s sooooo good
it’s sooooo good
January 13, 2025 at 1:00 PM
people are really sleeping on atom based state management like Jotai impo.
it’s sooooo good
it’s sooooo good
pair programming is dead with AI for me.
and as it should be honestly. pair programming has way more value when you’re talking about higher level patterns and architecture not “what should I name this variable”
and as it should be honestly. pair programming has way more value when you’re talking about higher level patterns and architecture not “what should I name this variable”
January 1, 2025 at 4:17 AM
pair programming is dead with AI for me.
and as it should be honestly. pair programming has way more value when you’re talking about higher level patterns and architecture not “what should I name this variable”
and as it should be honestly. pair programming has way more value when you’re talking about higher level patterns and architecture not “what should I name this variable”
what HTTP response code to say “there’s nothing for us to do”?
December 28, 2024 at 5:14 AM
what HTTP response code to say “there’s nothing for us to do”?
my incident.io year in review for SEVs 🙂↕️
December 20, 2024 at 3:08 AM
my incident.io year in review for SEVs 🙂↕️
had a dream cursor_ai wouldn’t let inspect element in a browser without paying for premium???
maybe time to stop coding for a bit lol
maybe time to stop coding for a bit lol
December 16, 2024 at 4:26 PM
had a dream cursor_ai wouldn’t let inspect element in a browser without paying for premium???
maybe time to stop coding for a bit lol
maybe time to stop coding for a bit lol
we’re switching from Golang to Kotlin for a lot of things now at work 🙂↕️
I hope Kotlin is a hell of a lot better than Java
I hope Kotlin is a hell of a lot better than Java
December 14, 2024 at 4:56 AM
we’re switching from Golang to Kotlin for a lot of things now at work 🙂↕️
I hope Kotlin is a hell of a lot better than Java
I hope Kotlin is a hell of a lot better than Java
about time to reread the React docs from head to toe given all the recent changes.
Either now or wait for the React Compiler.
Either now or wait for the React Compiler.
December 13, 2024 at 1:55 AM
about time to reread the React docs from head to toe given all the recent changes.
Either now or wait for the React Compiler.
Either now or wait for the React Compiler.
Reposted by Aaron Hammer
PSA: never use Object.entries() (or even Object.keys() really) to create a variant/derivative of an object. Doing this is mind-bogglingly wasteful.
Iterating over object properties is literally a JS language feature (for..in), nothing will ever be as fast as just using it.
Iterating over object properties is literally a JS language feature (for..in), nothing will ever be as fast as just using it.
December 10, 2024 at 3:22 AM
PSA: never use Object.entries() (or even Object.keys() really) to create a variant/derivative of an object. Doing this is mind-bogglingly wasteful.
Iterating over object properties is literally a JS language feature (for..in), nothing will ever be as fast as just using it.
Iterating over object properties is literally a JS language feature (for..in), nothing will ever be as fast as just using it.
to expand on this, I’m wondering if theses fixes are even simplifying the code.
maybe up until the 95% percentile of issues, but after that you’re risking turnings things into a rats nest
maybe up until the 95% percentile of issues, but after that you’re risking turnings things into a rats nest
December 11, 2024 at 12:32 AM
to expand on this, I’m wondering if theses fixes are even simplifying the code.
maybe up until the 95% percentile of issues, but after that you’re risking turnings things into a rats nest
maybe up until the 95% percentile of issues, but after that you’re risking turnings things into a rats nest
engineering isn’t about solving problems but removing them entirely
December 11, 2024 at 12:31 AM
engineering isn’t about solving problems but removing them entirely
just learned the term BFF aka backend for the frontend aka the thing that handles web routes and basic APIs that are not encapsulated by microservices.
amazing term will be using it all the time now.
amazing term will be using it all the time now.
November 26, 2024 at 4:17 AM
just learned the term BFF aka backend for the frontend aka the thing that handles web routes and basic APIs that are not encapsulated by microservices.
amazing term will be using it all the time now.
amazing term will be using it all the time now.
Reposted by Aaron Hammer
This lint rule to ban direct calls to setState in effects should be enabled in every react project everywhere
There's a linter to enforce this: eslint-react.xyz/docs/rules/h...
The whole eslint-react series of rules is great, as it builds the rules based on recommendations from the new react docs 🎉
The whole eslint-react series of rules is great, as it builds the rules based on recommendations from the new react docs 🎉
eslint-react
ESLint React - A series of composable ESLint plugins for libraries and frameworks that use React as a UI runtime.
eslint-react.xyz
November 24, 2024 at 8:51 PM
This lint rule to ban direct calls to setState in effects should be enabled in every react project everywhere
forcing err != nil is one of the best programming patterns ever
November 23, 2024 at 1:11 AM
forcing err != nil is one of the best programming patterns ever
if you want a good example of how tech debt without rewrites can make a product near unusable.
Just look at airline websites versus their apps.
Just look at airline websites versus their apps.
November 15, 2024 at 6:00 AM
if you want a good example of how tech debt without rewrites can make a product near unusable.
Just look at airline websites versus their apps.
Just look at airline websites versus their apps.
Reposted by Aaron Hammer
if you're making npm packages you should prob use pkg.pr.new
November 13, 2024 at 8:01 AM
if you're making npm packages you should prob use pkg.pr.new
I love having my API, Frontend, and Infra defined in the same monorepo for a project
simply unbeatable DX
simply unbeatable DX
November 12, 2024 at 5:02 AM
I love having my API, Frontend, and Infra defined in the same monorepo for a project
simply unbeatable DX
simply unbeatable DX
trying to shave off 10ms by picking an obscure library but not putting the web routing and database on the same continent
November 12, 2024 at 3:56 AM
trying to shave off 10ms by picking an obscure library but not putting the web routing and database on the same continent
making a habit app, primarily for myself but hopefully for others as well.
that’s impo the most fun side project you can do
that’s impo the most fun side project you can do
November 12, 2024 at 2:42 AM
making a habit app, primarily for myself but hopefully for others as well.
that’s impo the most fun side project you can do
that’s impo the most fun side project you can do