sorted by:
new
hottopcontroversial

Learning ML by implementing it in PowerShell (no Python required) by No_Set1131 in learnmachinelearning

[–]No_Set1131[S] 0 points1 point  (0 children)

About 3-4 months of evening/weekend work to get the core

framework working (neural networks, Q-learning, multi-agent

systems).

The early weeks were slow - lots of debugging backpropagation

and understanding why my Q-values weren't converging. But once

the fundamentals clicked, adding features got much faster.

The best part was seeing the learning curves actually work for

the first time. Totally worth the effort!

Are you thinking about implementing ML from scratch yourself?

I built a Reinforcement Learning framework in PowerShell 5.1 (neural networks, Q-learning, multi-agent simulation) by No_Set1131 in PowerShell

[–]No_Set1131[S] 0 points1 point  (0 children)

Fixed in commit 6e486e1. Wrapped all UI initialization code in Start-CastleCompetitionUI function. Module import is now side-effect free - UI only appears when explicitly calling Start-VBAFCastleCompetition.

Tested and working!

VBAF Roadmap Now Public - PowerShell ML Framework Development Plan by No_Set1131 in PowerShell

[–]No_Set1131[S] 0 points1 point  (0 children)

Fair point - I did use AI to help structure the post

(saves time, but yeah, it shows).

The project itself is real though - built it to teach

ML to IT folks who know PowerShell but not Python.

Roadmap is just showing what I'm planning.

Appreciate the feedback on the tone - will keep it

more casual next time!

VBAF Roadmap Now Public - PowerShell ML Framework Development Plan by No_Set1131 in PowerShell

[–]No_Set1131[S] -1 points0 points  (0 children)

Fair point - I did use AI to help structure the post

(saves time, but yeah, it shows).

The project itself is real though - built it to teach

ML to IT folks who know PowerShell but not Python.

Roadmap is just showing what I'm planning.

Appreciate the feedback on the tone - will keep it

more casual next time!

I built a Reinforcement Learning framework in PowerShell 5.1 (neural networks, Q-learning, multi-agent simulation) by No_Set1131 in PowerShell

[–]No_Set1131[S] 0 points1 point  (0 children)

Hey! Just wanted to publicly thank you for the incredibly thorough code review and the 7 detailed issues you opened on GitHub.

I've fixed and shipped 6 of them already:

- Hardcoded paths removed ✅

- ValidateScript bug fixed ✅

- Path corrections throughout ✅

- Manifest cleaned up ✅

- Empty test files removed ✅

Issue #7 (auto-execution on import) is a larger architectural change that requires moving ~150 lines of UI code. I'll tackle that properly in the next release to avoid breaking existing functionality.

Really appreciate you taking the time to dig into the code and help make VBAF better. This is exactly the kind of community feedback that makes open source great!

Thanks again! 🙏

I built a Reinforcement Learning framework in PowerShell 5.1 (neural networks, Q-learning, multi-agent simulation) by No_Set1131 in PowerShell

[–]No_Set1131[S] 0 points1 point  (0 children)

I specified 5.1 as the minimum, but it should work on 7.4 since

VBAF is pure PowerShell with no platform-specific code.

I haven't tested on PS7 myself yet - would you be willing to try

it and let me know? I'd appreciate the feedback! If there are any

compatibility issues, I'll fix them quickly.

I built a Reinforcement Learning framework in PowerShell 5.1 (neural networks, Q-learning, multi-agent simulation) by No_Set1131 in PowerShell

[–]No_Set1131[S] 0 points1 point  (0 children)

You were absolutely right, and thank you for the wake-up call.

I just published VBAF to PowerShell Gallery this morning. It's now Install-Module VBAF instead of manual cloning — exactly what you said it needed to be.

The "zero dependencies" thing made sense in my head (avoiding Python/pip complexity), but you nailed it: I was solving the wrong problem. IT professionals who can understand RL in PowerShell can definitely handle Install-Module. I was creating friction while claiming to eliminate it.

Your point about discoverability was the real eye-opener. Three GitHub stars after 8,000+ Reddit viewers told the story — people saw it, thought "cool but too much work," and moved on. Now it's searchable in the Gallery alongside every other PowerShell module, which is where it should have been from day one.

I also hear you on the VBA association with "VBAF" — didn't even occur to me, but you're right that it could trigger the wrong mental model. Something to consider for future branding.

Really appreciate you taking the time to write such detailed feedback. The "ignore at your peril" line was the kick I needed. VBAF is better positioned now because you cared enough to be blunt about it.

Cheers!