-> LinkedIn (linkedin.com/in/ryangglover) and cheatcode.co for business stuff.
-> ryanglover.net for personal stuff
-> LinkedIn (linkedin.com/in/ryangglover) and cheatcode.co for business stuff.
-> ryanglover.net for personal stuff
-> LinkedIn (linkedin.com/in/ryangglover) and cheatcode.co for business stuff.
-> ryanglover.net for personal stuff
You'll be stunned how much working in a peaceful environment changes your ability to come up with ideas and focus on seeing them through.
Don't be a firefighter for fire starters.
You'll be stunned how much working in a peaceful environment changes your ability to come up with ideas and focus on seeing them through.
Don't be a firefighter for fire starters.
www.npr.org/2025/05/20/n...
www.npr.org/2025/05/20/n...
ryanglover.net/blog/chauffe...
ryanglover.net/blog/chauffe...
ryanglover.net/blog/writing...
ryanglover.net/blog/writing...
Where I'm at now:
- Mod CSS framework is mostly ready to go, just needs a bit more browser testing.
- Public beta of Push is rolled out + working
- Migrated DBs to be self-hosted
- Starting new CheatCode site today
Where I'm at now:
- Mod CSS framework is mostly ready to go, just needs a bit more browser testing.
- Public beta of Push is rolled out + working
- Migrated DBs to be self-hosted
- Starting new CheatCode site today
There seems to be a "change fetish" with a lot of OSS stuff.
If it works and there's no practical reason to change it, don't change it.
There seems to be a "change fetish" with a lot of OSS stuff.
If it works and there's no practical reason to change it, don't change it.
Even if you don't know everything you need to know to do something, just start poking around.
I knew a fraction of what I know now before I started building @cheatcodeco.bsky.social. Most was "on the job" learning.
Even if you don't know everything you need to know to do something, just start poking around.
I knew a fraction of what I know now before I started building @cheatcodeco.bsky.social. Most was "on the job" learning.
Love being able to bring my own keys for any model and the approach to reasoning/file editing is really slick.
Also love the cost estimates for individual responses and a total for the entire chat.
Love being able to bring my own keys for any model and the approach to reasoning/file editing is really slick.
Also love the cost estimates for individual responses and a total for the entire chat.
You're an expert, aren't you?
Then why are you letting HR departments determine what tools you use?
Especially when you know, instinctively and experientially that they're low-quality tools.
You can (and should) be the one deciding how things are done. Not HR.
You're an expert, aren't you?
Then why are you letting HR departments determine what tools you use?
Especially when you know, instinctively and experientially that they're low-quality tools.
You can (and should) be the one deciding how things are done. Not HR.
It's okay to not fit in.
It's okay to do things that others won't, can't, or refuse to.
It's okay to not fit in.
It's okay to do things that others won't, can't, or refuse to.
Wish I would have found this a few days ago: github.com/publishlab/n...
Wish I would have found this a few days ago: github.com/publishlab/n...
Wish I would have found this a few days ago: github.com/publishlab/n...
Instead, use the snap package (github.com/nodejs/snap).
The nodesource one is hit or miss and not reliable for production.
Instead, use the snap package (github.com/nodejs/snap).
The nodesource one is hit or miss and not reliable for production.
No custom config formats. No YAML. No other "but I have to do it this way" buffoonery.
Just JSON.
No custom config formats. No YAML. No other "but I have to do it this way" buffoonery.
Just JSON.
Not sure what that means, but interesting to see it happen so fluidly/subconsciously.
Not sure what that means, but interesting to see it happen so fluidly/subconsciously.