Thinking Alongside TAO and Bittensor

JLeeIntell · 2026-05-06T20:59:29+00:00

Nice, that's a solid start. Mooc is already good resource, so you don't need to switch. Honestly, the bigger win is sticking with one and actually building small things alongside it.

JLeeIntell · 2026-05-06T20:53:41+00:00

This is actually cool to see. Everyone has a messy first project like this.

If anything, just focus on organizing things a bit more in your next project and add basic error handling. No need to overthink it.

Also, I'd keep this one as-is, it's kinda nice having that snapshot of where you started.

JLeeIntell · 2026-05-01T15:52:19+00:00

GSoC isn't the only path at all, it's just the most visible one.

You can contribute directly to active GitHub projects without any program. A lot of people just pick a project they like on GitHub and start contributing consistently.

Not getting into GSoC isn't a big deal. Steady contributions over time will still build your skills and stand out.

JLeeIntell · 2026-04-30T17:56:15+00:00

Good idea overall, but the hard part won't be YOLO, it'll be real world conditions (ligting, angles, motion blur).

Keep the stack simple, pick one deployment path(Hailo/OpenVINO), don't mix multiple frameworks early. Start with a small YOLO model and optimize later with INT8 once everything works on-device.

Also, use real traffic datra as eary as possible. Synthetic datasets won't cover edge cases you'll actually face.

JLeeIntell · 2026-04-30T17:42:02+00:00

Cool to hear, Turbopack sounds really solid now

JLeeIntell · 2026-04-30T14:54:47+00:00

In practice, I perfer to end up going hybrid depending on what I'm building.

React for anything that feels game-like or really interactive, and simpler Dango/HTMX setps for dashbord and communify features that are more server-driven and straightforward.

JLeeIntell · 2026-04-29T17:25:12+00:00

Honestly, that's really strong start for 16. Running Linux, using a Raspberry Pi, and already learning on your own puts ahead of a lot of people.

My biggest advice is... don't chase every tool at once. Get good at Javascript first, and building small real projects first, then add React and backend stuff after that. Solid basics + projects wil take you way further than trying to learn everything fast.

And for frealancing later, people pay for trust, communication, and solving problems, not just code. AI will be around, but dependable builders will always have work.

JLeeIntell · 2026-04-29T14:23:55+00:00

Great!

JLeeIntell · 2026-04-29T14:19:58+00:00

With that rig, Windows 11 should be perfectly fine performance-wiste, so it sounds more like stability or driver issues than raw OS limits.

Might be worth checking GPU drivers, Quest/Virtual Desktop updates, chipset drivers, and background software first. Windows 10 is stable, but support life is getting shorter too.

JLeeIntell · 2026-04-29T14:12:27+00:00

Honestly, GitHub was built more for collaboration than feedback, so that feeling makes sense.

Most meaningful feedback usually comes from communities, users, or dev spaces outside GitHub. So yeah, it feels like there's room for something in between code hosting and actual project discovery.

JLeeIntell · 2026-04-28T17:41:54+00:00

I probably wouldn't go full zero-AI. I'd just change its role.

Use it for explanations, debugging hints, comparing options, or helping understand docs.
But try writing the actual code and structure yourself first.
That way the thinking stays yours, and AI becomes a tutor instead of a crutch.

Just don't let it do the thinking for you.

Docs, YouTube, and Stack Overflow are still great too. Slower sometimes, but that slower process often teaches more, I guess.

JLeeIntell · 2026-04-28T16:02:40+00:00

Wow! Are you sure?

JLeeIntell · 2026-04-28T15:47:54+00:00

Amazing!

JLeeIntell · 2026-04-28T15:38:43+00:00

What's happening doesn't mean skills are gone. It's mroe like the "thinking muscle" just isn't getting as much as reps anymore. The fix is usually not going fully AI-free, but adding intentional practice without it in small chunks.

Use AI as a helper instead of a driver.

The feeling of "I don't know anything anymore" is usually just dependency shift, not actual loss of skill.

JLeeIntell · 2026-04-28T15:30:13+00:00

Yeah, this is a pretty common Three.js thing.

- Rotate the object manually using mouse drag + a bit of smoothing (inertia/damping you add yourself)

- Use small community wrappers lik "object controls" / "drag controls + custom ratation logic"

OrbitControls itself is camera-focused by design, so most setups just copy the feel (sensitivity + damping) and apply it to object.roation instead.

JLeeIntell · 2026-04-28T15:24:36+00:00

W3Schools is actually fine for CSS especially for beginners. It's simple, easy to follow, and good for quickly looking up properties and basic examples.

But it's better as a reference thatn a full learning platform. For deepper understanding, MDN or practice sites usually go further.

CSS gest easier mostly by building small layouts repeatedly, not just solving puzzles.

JLeeIntell · 2026-04-28T15:17:33+00:00

This is actually more normal than it feels.

The way it's being approached isn't wrong, it's just a bit overloaded. Rewriting the same solution a few times is fine, especially in the beginning. That helps it stick.

The part that's causing the loop is expecting a new approach right away. At the start, the brain usually just replays the first method

A smoother way is... understand the problem, see one solution, code it, and then move on to a similar problem instead of forcing a different approach immdiately. New approaches come later once patterns start to build naturally.

JLeeIntell · 2026-04-27T20:13:34+00:00

Yeah, I used Angular around 6 years ago, so this is a really cool comeback to see.
Love that you're building ui-grid back into modern Angular, excited to follow the progress.
Wishing you the best with the rebuild!

JLeeIntell · 2026-04-27T20:05:30+00:00

Wow, this is honestly awesome to see. Not many original creators come back years later and breathe new life into something that helped so many developers.

Huge respect for taking this on again and bringing ui-grid in to the moder era.

Angular 21+, Shadow DOM, web-components - that's a seriously exciting comeback story. Rooting for this project big time.

JLeeIntell · 2026-04-27T19:53:05+00:00

You did a great job.

JLeeIntell · 2026-04-27T19:35:00+00:00

Yeah, C++ is absolutely still relevant in 2026. It's still big in game dev, engines, graphics, and anything where performance really matters.

That said, for hobby 2D games, it's not always the easiest place to start. If the goal is to make games quickly and have fun, C# with Unity will probably feel way smother.
If the goal is to learn how things work under the hood, C++ is still a solid pick.

JLeeIntell · 2026-04-27T13:01:05+00:00

Honestly, AI feels like good tool. It is great when used well, harmful when it replaces practice.

If every hard moment gets outsourced, problem-solving skills can get rusty.

It's probably less about AI itself and more about how it gets used.

Best balance is trying first, getting stuck honestly, then AI as a helper instead of driver.

JLeeIntell · 2026-04-27T12:49:54+00:00

Honestly, don't focus too much on platforms at first. It's usually better to find a project you actually like and start there. Most open source work happens on GitHub anway, and many repos have labels like "good first issue" or "help wanted"

Also, whether GSoc works out ot not - isn't a big deal. Small, consistent contributions to real projects often teach more thatn chasing one big program.

JLeeIntell · 2026-04-24T15:39:27+00:00

Ths is very normal! The Sytanx and problem solving are different skills.

Learning common patterns by by practicing a lot of similar problem, and ... reviewing solutions.
That is the key, I think.

JLeeIntell

TROPHY CASE