I write all my own posts. Expect typos.
Some stuff I work on: https://github.com/kyleect
Rarely updated: testingrequired.com
This house would be terrible to live in. Building software isn't hard. It's designing it to be livable and maintainable, that's the hard part.
Sure it had an Axum API but it's reusing the functions and types already in place. My initial design for that stuff just worked and that feels fucking great.
Sure it had an Axum API but it's reusing the functions and types already in place. My initial design for that stuff just worked and that feels fucking great.
I mean making your app more accessible to more users is already a huge win but holy hell it makes automation a fucking breeze.
I mean making your app more accessible to more users is already a huge win but holy hell it makes automation a fucking breeze.
github.com/testingrequi...
github.com/testingrequi...
I mean making your app more accessible to more users is already a huge win but holy hell it makes automation a fucking breeze.
I mean making your app more accessible to more users is already a huge win but holy hell it makes automation a fucking breeze.
I mean making your app more accessible to more users is already a huge win but holy hell it makes automation a fucking breeze.
I also recognize it has many downsides that have to be accounted for.
Let me tell you, it really sucks resolving merge conflicts.
I also recognize it has many downsides that have to be accounted for.
Let me tell you, it really sucks resolving merge conflicts.
DM me
DM me
I have a use case where I'm firing a mutation off and I need away to call an "onSuccess" callback that I don't have at mutation definition time.
I have a use case where I'm firing a mutation off and I need away to call an "onSuccess" callback that I don't have at mutation definition time.
I've seen the genre make a little bit of a comeback but they've haven't felt like TW2, the gold standard of the genre, to me.
I was working on this game a few years back and thinking of reviving it.
I've seen the genre make a little bit of a comeback but they've haven't felt like TW2, the gold standard of the genre, to me.
I was working on this game a few years back and thinking of reviving it.
We'll see how this goes 😅
Image credit: www.reddit.com/r/Unity3D/s/...
We'll see how this goes 😅
Image credit: www.reddit.com/r/Unity3D/s/...
But simpler solutions often require *more* thought. Complexity's easy. You just keep typing.
That's why I call over-complicating "under-engineering".
But simpler solutions often require *more* thought. Complexity's easy. You just keep typing.
That's why I call over-complicating "under-engineering".
Make the change easy, then make the easy change.
It's rarity correlates to our massive amount of tech-debt.
#professionalism #passion
Make the change easy, then make the easy change.
It's rarity correlates to our massive amount of tech-debt.
#professionalism #passion
Digging in to language design and actually implementing some programming languages definitely changed my view on this.
I actually like the syntax for index access on an array being the same as a function call.
arr(idx)
Digging in to language design and actually implementing some programming languages definitely changed my view on this.
I actually like the syntax for index access on an array being the same as a function call.
arr(idx)
Nope! This is a myth! QA doesn’t create the bottleneck — they reveal it! 👇
Nope! This is a myth! QA doesn’t create the bottleneck — they reveal it! 👇
If an abstraction is flaky (different from leaky) it pulls you back into the details to understand if it abstracted the thing in the way it should've abstracted.
If an abstraction is flaky (different from leaky) it pulls you back into the details to understand if it abstracted the thing in the way it should've abstracted.
"We are pushing to production. Any uncommitted changes will be lost."
"uncommitted changes will be lost"
"uncommitted changes"
Investor demos were later THAT DAY.
This house would be terrible to live in. Building software isn't hard. It's designing it to be livable and maintainable, that's the hard part.
This house would be terrible to live in. Building software isn't hard. It's designing it to be livable and maintainable, that's the hard part.