What's Missing in learning or Teaching SQL?

I enjoy this sub but it feels like most posts are the same. "I created tutorial/course/practice/etc." Or "how do I learn/practice/projects/etc." It's good. A really active sub.

What I'd love to know, is what do people who are learning SQL want? For instance, I've taken a different approach. Over the past year I've worked on tooling to make creating courses and practicing more efficient. Other's have worked on more scenario-based learning (always a good idea). Some have gamified learning and that's a lot of fun.

My real question is for those of you learning or teaching. What is missing? Is there something you wish you had that doesn't exist?

In my perfect world, learning SQL would feel more like working in a business environment. Large, complex data warehouses, where you learn the data and SQL over time. Lot's of problem solving and judgement when there is ambiguity. Something that feels more like doing real work.

Would having more tools available to make it easier to create courses, practice, etc. be useful? Would having more realistic environments to learn in be useful? Is it something else completely? In short. What's missing?

reddit.com
u/leogodin217 — 1 day ago

Odd Fellows Monthly Breakfast Buffet Was... Delicious!

Finally got a chance to catch the Odd Fellows breakfast I heard about on this sub. Food was really good. Friendly people running it and I even met a fellow Redditer. Add in a challenging hike on Bald Mountain Loop and I'd call it a great morning.

reddit.com
u/leogodin217 — 4 days ago

Have We Gone Too Far Away From Role Identity?

I get that "You are a super duper expert product manager who scales companies 10X" works against you, but I see a lot of comments where people say role identities should be avoided altogether. "It only makes it worse". "It will be more confidently wrong." etc.

While I agree about the super duper and expert parts, role identity can definitely shape output. Start two sessions with "You are the software architect" and "You are the product owner". Then ask each one to design a feature. The output will likely be very different. The first will design it from a technical perspective and the second from a functionality perspective. Then create one without a role. You will probably get a third and very different output.

I still use roles for specific purposes and it seems to make a big difference. Am I missing something? My processes have a template for features and a description of what a good feature contains and doesn't contain, but setting the role up front still shapes the output.

Any thoughts?

reddit.com
u/leogodin217 — 1 month ago

Sonnet 5 Is a Really Good Orchestrator

Anthropic said Sonnet 5 was intended for agentic workflows, and now I believe them. Sonnet <5 was not good at orchestrating subagents and following processes. I had to use opus for what seems like simple work of routing requests to subagents. Out of curiosity, I tried /implement-sprint (long-running code changes) with Sonnet 5 and it was flawless.

No more, "Let's stop here." Aren't getting, "Step 3 is done, do you want to continue to step 4?" Just completing the process and recovering when things go wrong. One thing I noticed is it doesn't seem much faster than Opus on the same thinking levels anymore. But that's just going on feel. I haven't tested.

[Edit] This repo is pretty old and I've optimized a lot of this stuff, but the general pattern still holds /arch-design -> /arch-review (usually multiple) -> /create-sprint -> /implement-sprint -> /fold-pending. The process works really well for me. Once a project's architecture is set, adding features is usually really smooth.

https://github.com/leogodin217/leos_claude_starter

u/leogodin217 — 2 months ago