Sorry to jump into your dialog but you know how in SublimeText, VSCode or maybe even VS there is a keyboard shortcut CTRL+P to find files (fuzzy search) in a project?

Would it be complicated to implement this functionality that it would focus on Code Explorer and on Search... field?

I would press CTRL+P, start writing, it would filter classes/Moduls/Forms/Functions.

I thought if I remap CTRL+P to focus CodeExplorer then press TAB, it would go to the Search... field but I have to use mouse for this. Tab is doing nothing.

Out of the head, I would say more comments in the code or more (simpler AND advanced) examples.
But that's mainly just me. I learn the most from working examples. I go through them, understand them and apply them to my problem.

If someone just tells me "how", I have a hard time to understand that. (Or just snippets of code. I need to "see" a working complexity).

For example when I teach my padawans at work Python or C# MVC models and so on, I grab A4 paper, do a few squares with code in them/arrows, what affects what and when I start the program, what's the order of functionality to "show…

One more thought came through my mind.

This is just an example how I like to teach. Not a tip on how to write a blog post about that (because I didn't do that ever)

When I propose a functionality and a padawan understands it, I add "and how do you thing the code changes when I want to add another item"
Or "What if I don't want to parse to the object 1 item but 100 items"
Or "And what happens if this happens"

It's hard to explain. Without an example.
But I go through 5-10 different "cases", nuances, and generally this is the thing that checks the "now it tiks for me, now I understand, tha…