• I start with a small, testable goal.
• I document what I learn (so others don’t have to repeat the same mistakes).
• I iterate: prototype → feedback → improvements.
• I’m especially interested in projects that are useful for real workflows.

If you open an issue and describe what you’re trying to do, I’m much more likely to respond quickly.

I enjoy building clean UI prototypes and experimenting with UI patterns.

• HTML / CSS / JS experiments
• Login demos & site prototypes
• Responsive, “works on mobile too” builds

My learning path is hands-on: routing, caching, and tunneling concepts—then turning them into tools.

• Reverse proxy + caching ideas
• Config-focused experimentation
• Benchmarks / tests to understand performance

I like developer tools that are easy to use and easy to extend.

• small utilities
• docker-friendly setups
• readable docs

Below are a few repos I’m proud of. If any of these match what you’re working on, feel free to fork, star, or open a discussion.

• Proxy Bench — https://github.com/turtleboyagain120/proxy-bench
• AI-GPT Tester — https://github.com/turtleboyagain120/ai-proxy-tester
• VPN / Speedtest tools — (see Proxy Bench + related repos)

• Clash UI Config — https://github.com/turtleboyagain120/boring-clash-ui
• Clash / Sing-box UI experiments — https://github.com/turtleboyagain120/sing-box-ui

• Learn Proxys — https://github.com/turtleboyagain120/Learn-proxys
• boring-proxy / related lab builds — https://github.com/turtleboyagain120/boring-proxy

• quick-viral-projects — https://github.com/turtleboyagain120/quick-viral-projects

• More web tools and UI demos (clean UX, practical features)
• Proxy/network learning projects with clearer docs
• Experiments that teach concepts without turning into guesswork

Instead of being secretive, I treat learning like a progression.

One of my recurring themes: learn proxies the “build it yourself” way.

I’ve been experimenting with ideas that combine:

• reverse proxying
• caching concepts
• tunneling/VPN chaining (learning-focused)

It’s not just theory—my goal is to understand the moving parts so I can build tools that are reliable and easier to configure.

I’m always open to friendly collaboration.

If you want to work together, here are the best ways:

• ⭐ Star a repo you like
• 📝 Open an issue with your goal (what you want + what you tried)
• 💬 If there’s a discussion thread, join it—no need to be formal

• GitHub: https://github.com/turtleboyagain120
• Issues: https://github.com/turtleboyagain120/issues

I test how different licenses behave in real repo setups—so people understand what they can reuse.

• License-testing — https://github.com/turtleboyagain120/License-testing
• didactic / license-related experiments — tiny lab repos for learning + clarity

I experiment with the text and structure of terms (EULA-style), mainly to understand how projects communicate rules.

• IET — https://github.com/turtleboyagain120/IET

Some repos are archived or carried forward—still useful as learning references and “what changed” history.

• Archived-work-from-turtleboyagain120 — https://github.com/turtleboyagain120/Archived-work-from-turtleboyagain120

I create learning resources meant for students and educators—simple, readable, and focused on practical concepts.

• School_quality — https://github.com/turtleboyagain120/School_quality
• The-Classroom — https://github.com/School-quality-studios/The-Classroom

A collection of “starter-like” projects, templates, and examples meant to explain how things work step-by-step.

• School-info — https://github.com/School-quality-studios/School-info
• turtleboyagain120.github.io — https://github.com/turtleboyagain120/turtleboyagain120.github.io

Short repos where I test ideas, languages, and small Git learnings—focused on experimentation and documentation.

• Git-learning — https://github.com/turtleboyagain120/Git-learning
• Lobotomy-un- — https://github.com/turtleboyagain120/Lobotomy-un-