I'm a very slow thinker too. I prep for every meeting, and for design meetings especially, I'll review the design for hours ahead of time. If your team doesn't share designs for review prior to these meetings then your team is probably wasting time going over the basics and not getting deep into the design. If this is the case I'd propose to your leadership that all designs must be shared at least 24h ahead of time. Then make sure to block some time on your calendar to review. Everyone has strengths and weaknesses, it's all about figuring out ways to maximize your strengths and minimize the weaknesses. Moves and counter moves.

@@dvdkliu thanks David. That’s an excellent idea. Otherwise solutioning calls are just high level and people are desperately blurting out whatever they can to sound intelligent lol.

It is rare that I've seen any company accept the Salesforce UI as it stands to build things in. LWC is slow and clunky, along with the rest of Lightning. There are a lot of good reasons to build UIs off platform while keeping the platform all out-of-the- box for internal users. I don't know, the database has a big emphasis. Tell me a use case for LWCs and I'll probably tell you why LWCs are suboptimal.

Degree not necessary at all. Good luck!

That would be a good answer during an interview, especially if you can defend it!

I'm Apex-first and transitioning more of my orgs to Lightning Flows. Ideal use case I've found is for requirements where writing properly structured Apex would be overkill for the need. For example, I have some multi-record operations including cloning child records and using a flow lets me leave the error handling and batching to Lightning. If the data transformations were more complex, the Apex investment would be worth it but given the need, Flow is the ideal tool