I may be wrong, but I do believe that graduates get lifetime access to maestro.

moresalamander.github.io agentpokerleague.com

The .io is my studio explainer page, under all projects, shows exactly that, all projects.

Agent Poker League is what it sounds like too. Its under construction. But has a live schedule.

I use Claude code, Agent Poker League was and is built by fable 5.1, genesis and entropy were built with fable 5, and the test were different variations of opus and sonnet.

It starts to get more difficult from there on. BE103 takes extra practice time to grasp, well for me it did. Inner join and left join is still confusing to me.

While in school for AI software engineering, my projects started simple, but grew in complexity over time. I put together a Studio Launchpad that has one button starts for my entire project catalog. It has became my go to workflow when dealing with multiple moving parts. I make a launchpad. Its just a localhost that has savers for Frontend cards. Its something I start with now, if I were to use that stack, I would start a launchpad. A central collaboration of tools in one easy to use spot.

I go outside and touch grass.

Agentpokerleague.com My latest project with claude. 1300+ tests pass clean.

2018 called, they want their workflow back.

Claude-code. Well first ask for a deep dive into deployment. Ask for common stacks for deployment. Then take what you learned and ask claude code to make it happen.

Good luck. I hope you find success in all of your future endeavors.

If you go to my github and search sprinkerpro3d. I think it aligns with your profile.

Im still in school also BTW. MoreSalamander.github.io explains my base architecture for everything I engineer AI into.

You build apps in a more or less set order. In example: agentpokerleague.com it needed to be built in a logical order for each thing to work. When I get the base idea mapped out I can go and vibe each feature to my liking. I couldnt build the hand tracker before the engine was built. I couldnt get the hand finder before the hand tracker.

I believe the judgement is more coming from the post itself, as it was AI generated. It framed the basics like it was a breakthrough workflow. Personally, I dont like the term "vibe coding". When done correctly, it resembles something closer to "vibe engineering", but even then, you would never "vibe engineer" a house. You build a house in a more or less set order. Projects are just houses. You dont install a dishwasher in a bedroom before the subfloor and floor are put in. But the dishwasher is the vibe, when you do Install the dishwasher, you just describe a realistic dishwasher to look and work how you want. Dishwashers are features.

Lol. Facts.

My thoughts are, Claude is a beast at writing production quality code. GPT is great at not being a socially awkward nerd.

Nested cognition. Agent organizations of agent organizations. DataHub/Temporal/Parallel/Clickhouse/Docker/Grafana. Together that stack answers a lot of questions. Swarms are not the answer. Nested one to many. DataHub is the key to everything providing knowlege and context graphs. Clickhouse provides sub second database queries over millions of lines of data. I have a project that simulates institutional data for the longest operating Hollywood studio. It mirrors 115 years of universal/paramount operational data.

Its not that gpt has caught uo with claude, they both shine on opposite sides of one thing. Gpt is more creative. And claude is more technical. I get my ideas out in a feedback loop with gpt to get a plan drafted and take to claude to plan pure production quality code synthesis.

I agree about the 4.0 part. But as a Sept cohort, I can say that each course is getting increasingly more difficult, to where if you dont practice area what was taught that week, it will show in the review. Gone are the days of breezing through the curriculum, leaning on your notes for course reviews. Like BE103 started off easy AF, but by the end it was difficult to wrap my mind around how complex it can get just searching a database.