…Or, What is a Tech Stack and How to Write Software Without Actually Being an Engineer. (Don’t forget to read part 1, part 3, and part 4!)
***
💡Building Innovation From Ideas is a new series where I’ll document the process of building a brand-new platform for nurses.
⚙️Part 2: The Nurse’s Tech Stack
(If you missed part 1, click here.)
I’m building an opportunities platform for nurses and I’m not an engineer.
Before I show you what I’m actually using, you need to understand several concepts. You may already know this… but for learners’ sake.
In part one I said it’s important to get the boring foundation right before you touch the fun part. This is that.
Hardware and software
Hardware is the thing you can drop. Your laptop. Your phone. The Pyxis. The Alaris pump. The workstation on wheels.
Software is the instructions running on it. Epic is software. So is Cerner, and so is whatever charting system you’re using.
Same machine, different software, different job.
What a tech stack is
It’s the list of software you picked to work together to make one thing run. They call it a stack because the pieces sit on top of each other and each one depends on the one underneath.
Think about admitting one patient.
- A bed gets assigned
- A chart has to exist
- Orders go in
- Pharmacy sees the order
- The family needs a way to reach the unit
No single system does all of that. It’s five or six systems that have to talk to each other, and somebody picked each one. That set of picks is a tech stack.
Every app on your phone is somebody’s tech stack. Instagram. Your bank’s app. Doximity.
Three reasons to care even if you never write a line of code:
- What you pick in week one decides what you’re allowed to do in year two.
- A bad pick is cheap to undo now and expensive to undo later.
- Most of these tools are free until you’re big, and nobody tells nurses that.
Stack or tool
Not everything I’m going to show you is stack. Some of it is software I used once.
So ask one question. If this disappeared tomorrow, does my platform stop working?
Yes, it stops. That’s stack.
The phone book disappears and nobody can reach my site. The database disappears and every nurse record goes with it.
No, it keeps running. That’s a tool.
The trademark search website you’d use to identify if a business name may be claimed already… if it disappears your business/personal website or platform can still run exactly like it did.
Across this series, I’ll likely name 20+ pieces of software. Some are part of my tech stack. Some will be tools.
It changes what you do about it.
With stack you worry about getting stuck, what it costs at ten nurses vs ten thousand nurses, and/or what happens if the company folds.
Your stack is the equipment the unit can’t run without. Your tools are what’s in your pockets. And both matter.
Eight terms or concepts you’ll need to recognize…
Domain. Your address on the internet. You don’t own it, you rent it, usually a year at a time.
DNS. The internet’s phone book. It turns the name a human types into the numbered address of the computer that answers. It’s the unit directory. You know the charge nurse’s name, the directory tells you which extension actually rings.
Database. Rows and columns, like a very serious spreadsheet a lot of people can use at once without overwriting each other. Every account, every profile, every record or every “contact” or person on a platform lives in one.
Hosting. The real computers (servers), sitting in a building, that hand your website to a visitor when they ask for it. Somebody’s machine is always on so yours doesn’t have to be.
Free tier. The version of a paid product that costs nothing until you get big. Almost everything in this series is free at my size.
Vendor lock in. When your stuff is stuck inside one company’s product and you can’t get it out. The most expensive mistake to potentially make, and why I ask before I sign up for anything: can I leave?
Open source. The instructions behind the software that are published for anyone to read. If the company folds or turns on its users, the software doesn’t vanish, because somebody else can run the same thing. It’s a fire exit.
AI. Software trained on enormous amounts of writing that can now produce writing, including code. It isn’t thinking and it isn’t checking itself.
Vibe Coding…
This is how I’m building probably 95% of my new platform for nurses.
Vibe coding is essentially describing what you want in plain English to AI and the AI writes the code.
It’s you having a conversation with your AI BFF. (Mine is Claude, at the moment).
Think about it this way…
It’s the difference between writing the order and knowing how to compound a drug.
You still have to know what you want, why you want it, and whether what came back is safe. You don’t have to be the one mixing it.
Claude is an AI assistant. Claude Code is the version that can read and change the real files on my computer instead of just talking to me in a window.
A chat window hands you text that you can copy somewhere else. Claude Code makes the change in the project or folder on my desktop (or in the cloud) and I can see exactly what changed.
So in essence, I describe the problem. It writes the code.
As a nurse, I’m skipping the syntax, not the judgment. And 6 weeks in, I’ve caught it confidently wrong more than once. About my own project. About something it had done itself.
So think of it like this…
AI can draft the note. You still sign it. Your license is still on it.
If you can’t explain what a tool does to another person in one sentence, you don’t understand it well enough to depend on it yet.
And if you’ve been sitting on an idea because you don’t know how to code, that reason has now expired.
What you still need is the part the AI can’t bring, which is you knowing the problem.
Five questions I ask before I pick anything
- Is the free tier real or is it a trap? Real means generous now and expensive only once you’re making money. A trap is cheap for twelve months and then triples.
- Can I leave?
- What does this cost at ten thousand nurses/people on the platform, not at zero? Do the math for where you’re going.
- Am I putting too many eggs in one company’s basket? Next week you’ll watch me split two things across two companies on purpose and pay a little more for it.
- If this company (the stack or tool company) disappeared tomorrow, what breaks in my software/platform?
Refresher… and before next week
Hardware is what you can drop. Software is the instructions running on it.
A stack is the set of software you picked to work together, and vibe coding means you can direct it without being an engineer.
Claude Code, the one piece of software I named today, is a tool. My platform runs fine without it. I just couldn’t build without it.
Three questions for you.
- What’s the idea you’ve been sitting on because you thought you had to learn to code first? That reason is now gone. So what’s the real reason?
- Look at your own unit. How many separate systems does one admission touch? That’s a tech stack and you already know how to think about one.
- If the company behind your favorite app disappeared next month, what would you lose?
Tell me in the comments.
I’ll chat soon,
Marsha
