Recently, I ran a Claude Code foundations workshop for non-developers.
What I realised: the knowledge gap between developers and non-developers can be quite wide. Things I thought were obvious were not obvious to some learners.
What I realised: the knowledge gap between developers and non-developers can be quite wide. Things I thought were obvious were not obvious to some learners.
One example: the UI of an IDE.
In the workshop, I used Zed. The benefit of an IDE is you get a file browser, editor, viewer, and terminal in one app. But to a non-developer, the same UI can be confusing.
I thought it would be good to write a post to walk through the 4 panels before starting.
—
- Project Panel (the file browser)
On the left. It shows the files and subfolders in your project folder in a hierarchy. Many non-developers are not used to this tree view of folders.
In most non-developer apps, you open a file. In an IDE, you open a project folder. The tree view allows you to see what files and subfolders are in the folder.
Double-click any file to open it in the Editor Panel.
—
- Editor Panel (where you edit files)
Top right. This is where you read and edit a file.
Unlike most non-developer editors, your edits are not autosaved. You must press Cmd+S (macOS) or Ctrl+S (Windows) to save regularly.
—
- Terminal Panel (where you run commands)
Middle right when first opened, before launching Claude Code. This is where you run various commands.
We will not use the Terminal directly most of the time. Usually we just open it to launch claude, or use it when Claude needs our help to run a command with admin permissions, or a command that needs interaction.
—
- Terminal Panel after Claude Code is launched (the prompt box)
Bottom right. This is where you prompt Claude Code to do things.
Watch carefully for the difference between this and the Terminal Panel above. The prompt box is bordered top and bottom. The plain terminal is not.
I have seen a few learners paste their prompt into the terminal above instead of the prompt box. The two look almost identical.
—
For developers, all of this feels too obvious to walk through. But that is the curse of knowledge.
As a seasoned developer conducting workshops for non-developers, I have to constantly observe the knowledge gap to deliver my workshop effectively.
If you are a non-developer, hope this helps you.
If you are a non-developer wanting to learn the foundations of Claude Code, check out my workshop at https://lnkd.in/e9r8kScw. The next run is on 21st May.
#ClaudeCode #AI #VibeCoding
Enjoyed this? Subscribe for more.
Practical insights on AI, growth, and independent learning. No spam.
More in Vibe Coding
I caught Cursor trying to be lazy.
The AI agent couldn’t solve the typing error, so it cast the variable to 'any' to suppress the error, just like a sloppy software engineer would.
UX/UI and naming matter more than capability for adoption.
Recently, everyone on LinkedIn is talking about learning Claude after the demo of Claude Cowork.
Claude Code is for software developers, and OpenClaw is more for business users.
A learner said this to another learner during a recent workshop. I think this is the most common and most dangerous misconception about these two tools.
The votes are in for Cohort 4.
Congrats to Yasmeen Khan, the winner of the portable monitor from my Foundations of Claude Code workshop.
Claude Code Foundations: 5 Lessons from Cohort 1
To the learners who signed up as "guinea pigs", thank you. The first cohorts are always the messiest, as the course content and timing have not yet been test...
I was doing vibe coding and saw AI generated this code.
Notice anything?
I caught Cursor trying to be lazy.
The AI agent couldn’t solve the typing error, so it cast the variable to 'any' to suppress the error, just like a sloppy software engineer would.
Claude Code is for software developers, and OpenClaw is more for business users.
A learner said this to another learner during a recent workshop. I think this is the most common and most dangerous misconception about these two tools.
Claude Code Foundations: 5 Lessons from Cohort 1
To the learners who signed up as "guinea pigs", thank you. The first cohorts are always the messiest, as the course content and timing have not yet been test...
UX/UI and naming matter more than capability for adoption.
Recently, everyone on LinkedIn is talking about learning Claude after the demo of Claude Cowork.
The votes are in for Cohort 4.
Congrats to Yasmeen Khan, the winner of the portable monitor from my Foundations of Claude Code workshop.
I was doing vibe coding and saw AI generated this code.
Notice anything?