Tim T Joe
@timtjoe.bsky.social
Developer building with TS, Zig, Rust, Python. OSS, OS & Programming language development enthusiasts. | https://github.com/timtjoe
Pinned
i discovered atproto.com when i read @danabra.mov article early this early. yesterday i saw @moja.blue post about APT spec, i thought this was a good time to try an attempt at creating an explorer for trending and popular things on bsky.app
here is my result: timtjoe.github.io/atprotosy/
here is my result: timtjoe.github.io/atprotosy/
I haven't touched this project in two years, yet it still works perfectly. Even though JavaScript gets a bad rap for being messy, this app has remained bug-free for nearly four years. It’s a testament to the fact that when you craft code with longevity in mind, the language really shines
February 12, 2026 at 6:59 AM
I haven't touched this project in two years, yet it still works perfectly. Even though JavaScript gets a bad rap for being messy, this app has remained bug-free for nearly four years. It’s a testament to the fact that when you craft code with longevity in mind, the language really shines
Last Tuesday, I shared my attempt to develop an explorer for the ATProto.
I've since refined and enhanced it, lending it a more polished appearance.
CC:
@danabra.mov and @moja.blue
URI: timtjoe.github.io/atpx
I've since refined and enhanced it, lending it a more polished appearance.
CC:
@danabra.mov and @moja.blue
URI: timtjoe.github.io/atpx
February 10, 2026 at 5:56 PM
Last Tuesday, I shared my attempt to develop an explorer for the ATProto.
I've since refined and enhanced it, lending it a more polished appearance.
CC:
@danabra.mov and @moja.blue
URI: timtjoe.github.io/atpx
I've since refined and enhanced it, lending it a more polished appearance.
CC:
@danabra.mov and @moja.blue
URI: timtjoe.github.io/atpx
By all means, start your project with knip.dev. I added it to my project; I was both frightened and aroused because of what it did.
I highly recommend it.
I highly recommend it.
Declutter your JavaScript & TypeScript projects
Project linter to find unused dependencies, exports and files
knip.dev
February 9, 2026 at 6:17 PM
By all means, start your project with knip.dev. I added it to my project; I was both frightened and aroused because of what it did.
I highly recommend it.
I highly recommend it.
The "On-Edge Behavior" (Flaky Tests): A codebase that constantly triggers false positives or intermittent errors keeps the engineering team in a state of hyper-vigilance, preventing deep work and creative problem-solving.
February 6, 2026 at 9:32 PM
The "On-Edge Behavior" (Flaky Tests): A codebase that constantly triggers false positives or intermittent errors keeps the engineering team in a state of hyper-vigilance, preventing deep work and creative problem-solving.
The "Shutdown" (Code Stagnation): When developers are too afraid to touch a module because "it might break everything," the project has entered a state of shutdown. Innovation stops because the system no longer feels safe to modify.
February 6, 2026 at 12:14 PM
The "Shutdown" (Code Stagnation): When developers are too afraid to touch a module because "it might break everything," the project has entered a state of shutdown. Innovation stops because the system no longer feels safe to modify.
The "Meltdown" (System Outage): High-stress environments often lead to catastrophic failures. These aren't just one-off events; they are symptoms of a system that can no longer handle the load it was built to carry.
February 6, 2026 at 6:43 AM
The "Meltdown" (System Outage): High-stress environments often lead to catastrophic failures. These aren't just one-off events; they are symptoms of a system that can no longer handle the load it was built to carry.
Give your technical choices time to mature. Watch for the small wins, like a slight decrease in latency or fewer bug reports on a specific module. Celebrate the tiny shifts in performance. They add up. A resilient system is built on small, consistent commits, not constant pivots.
February 5, 2026 at 12:01 PM
Give your technical choices time to mature. Watch for the small wins, like a slight decrease in latency or fewer bug reports on a specific module. Celebrate the tiny shifts in performance. They add up. A resilient system is built on small, consistent commits, not constant pivots.
Developers, I see it all the time: you try one framework, one design pattern, or one library, and before it has a chance to prove its value, you jump to the next. Stability doesn’t happen overnight. Your application’s architecture and its data flow need time to settle, integrate, and scale.
February 5, 2026 at 6:07 AM
Developers, I see it all the time: you try one framework, one design pattern, or one library, and before it has a chance to prove its value, you jump to the next. Stability doesn’t happen overnight. Your application’s architecture and its data flow need time to settle, integrate, and scale.
✅ Migrate project from vanilla TS to react.dev. Now I can like React on npmx.dev.
✅ Improve the UI. Though it's not the final result, but that will do for now.
Check it out here:
🔗: timtjoe.github.io/atpx
✅ Improve the UI. Though it's not the final result, but that will do for now.
Check it out here:
🔗: timtjoe.github.io/atpx
some update to timtjoe.github.io/atpx
done:
- renamed project from atprotosy to atpx
- create new logo
todo:
- migrate project from vanilla TS to react.dev
- redesign UI
done:
- renamed project from atprotosy to atpx
- create new logo
todo:
- migrate project from vanilla TS to react.dev
- redesign UI
February 4, 2026 at 11:26 PM
✅ Migrate project from vanilla TS to react.dev. Now I can like React on npmx.dev.
✅ Improve the UI. Though it's not the final result, but that will do for now.
Check it out here:
🔗: timtjoe.github.io/atpx
✅ Improve the UI. Though it's not the final result, but that will do for now.
Check it out here:
🔗: timtjoe.github.io/atpx
Only one person knows how the system works, and they are too busy to explain it?
Create READMEs and architecture diagrams to distribute system knowledge.
Create READMEs and architecture diagrams to distribute system knowledge.
February 4, 2026 at 7:52 PM
Only one person knows how the system works, and they are too busy to explain it?
Create READMEs and architecture diagrams to distribute system knowledge.
Create READMEs and architecture diagrams to distribute system knowledge.
some update to timtjoe.github.io/atpx
done:
- renamed project from atprotosy to atpx
- create new logo
todo:
- migrate project from vanilla TS to react.dev
- redesign UI
done:
- renamed project from atprotosy to atpx
- create new logo
todo:
- migrate project from vanilla TS to react.dev
- redesign UI
February 4, 2026 at 4:54 PM
some update to timtjoe.github.io/atpx
done:
- renamed project from atprotosy to atpx
- create new logo
todo:
- migrate project from vanilla TS to react.dev
- redesign UI
done:
- renamed project from atprotosy to atpx
- create new logo
todo:
- migrate project from vanilla TS to react.dev
- redesign UI
The system requires frequent manual restarts or "scaling up" just to handle idle load?
Use profiling tools to identify and fix memory leaks or inefficient queries.
Use profiling tools to identify and fix memory leaks or inefficient queries.
February 4, 2026 at 1:41 PM
The system requires frequent manual restarts or "scaling up" just to handle idle load?
Use profiling tools to identify and fix memory leaks or inefficient queries.
Use profiling tools to identify and fix memory leaks or inefficient queries.
The "test suite" is either non-existent or ignored because it's too slow/flaky?
Establish a unit testing baseline for core business logic.
Establish a unit testing baseline for core business logic.
February 4, 2026 at 10:41 AM
The "test suite" is either non-existent or ignored because it's too slow/flaky?
Establish a unit testing baseline for core business logic.
Establish a unit testing baseline for core business logic.
i discovered atproto.com when i read @danabra.mov article early this early. yesterday i saw @moja.blue post about APT spec, i thought this was a good time to try an attempt at creating an explorer for trending and popular things on bsky.app
here is my result: timtjoe.github.io/atprotosy/
here is my result: timtjoe.github.io/atprotosy/
February 4, 2026 at 10:01 AM
i discovered atproto.com when i read @danabra.mov article early this early. yesterday i saw @moja.blue post about APT spec, i thought this was a good time to try an attempt at creating an explorer for trending and popular things on bsky.app
here is my result: timtjoe.github.io/atprotosy/
here is my result: timtjoe.github.io/atprotosy/
Changing one line of code causes unexpected breaks in unrelated modules?
Prioritize decoupling and enforcing strict interface boundaries.
Prioritize decoupling and enforcing strict interface boundaries.
February 3, 2026 at 9:28 PM
Changing one line of code causes unexpected breaks in unrelated modules?
Prioritize decoupling and enforcing strict interface boundaries.
Prioritize decoupling and enforcing strict interface boundaries.
Deployments are manual, high-stress, and often require immediate rollbacks?
Implement CI/CD pipelines to automate testing and release cycles.
Implement CI/CD pipelines to automate testing and release cycles.
February 3, 2026 at 7:27 PM
Deployments are manual, high-stress, and often require immediate rollbacks?
Implement CI/CD pipelines to automate testing and release cycles.
Implement CI/CD pipelines to automate testing and release cycles.
Stop the Bleeding: Before adding new features to a broken module, wrap it in tests to ensure current behavior is understood.
February 3, 2026 at 4:01 PM
Stop the Bleeding: Before adding new features to a broken module, wrap it in tests to ensure current behavior is understood.
Identify the Bottleneck: Don't refactor everything at once. Find the one service that causes 80% of your production incidents.
February 3, 2026 at 12:46 PM
Identify the Bottleneck: Don't refactor everything at once. Find the one service that causes 80% of your production incidents.
Modularization, automated testing, load balancing, and consistent refactoring help shift the system out of emergency maintenance and back into feature delivery. Performance doesn’t come from shipping faster, it comes from creating the right internal environment for your infrastructure to scale.
February 3, 2026 at 11:03 AM
Modularization, automated testing, load balancing, and consistent refactoring help shift the system out of emergency maintenance and back into feature delivery. Performance doesn’t come from shipping faster, it comes from creating the right internal environment for your infrastructure to scale.
When a system is constantly patching, resources get diverted away from optimization, refactoring, new features, and performance. The result is slow build times, crashing after minor updates, memory leaks, and a codebase that feels brittle no matter how many developers you add.
February 3, 2026 at 6:06 AM
When a system is constantly patching, resources get diverted away from optimization, refactoring, new features, and performance. The result is slow build times, crashing after minor updates, memory leaks, and a codebase that feels brittle no matter how many developers you add.
Developers often forget that anything sent to the browser is public territory. When you let a "grown-up" API key or database credential sit in a frontend component, you're inviting a breach. Keep your secrets in the environment variables and your logic behind a secure middleware.
February 2, 2026 at 6:27 PM
Developers often forget that anything sent to the browser is public territory. When you let a "grown-up" API key or database credential sit in a frontend component, you're inviting a breach. Keep your secrets in the environment variables and your logic behind a secure middleware.
Just because a library is popular doesn't mean it’s safe to be integrated into your core. I’ve seen production environments get absolutely wrecked because a developer allowed an unvetted, third-party dependency to have full access to the application’s execution context.
February 2, 2026 at 12:02 PM
Just because a library is popular doesn't mean it’s safe to be integrated into your core. I’ve seen production environments get absolutely wrecked because a developer allowed an unvetted, third-party dependency to have full access to the application’s execution context.
Just because a piece of code is part of your app doesn't mean it needs access to everything. Only give your components the specific data they need to function. When you give a simple button access to your entire database, you're creating a massive security hole that's just waiting to be exploited.
February 2, 2026 at 9:01 AM
Just because a piece of code is part of your app doesn't mean it needs access to everything. Only give your components the specific data they need to function. When you give a simple button access to your entire database, you're creating a massive security hole that's just waiting to be exploited.