01 / discover
Start with what pulls you in
We figure out which parts of technology you already enjoy, what you keep wondering about, and what kind of thing you would be excited to make.
Mentorship & Community
Mentorship for weird builders, future engineers, and curious friends.
I started mentoring friends who wanted to understand technology better or make a career change into tech. Instead of handing everyone the same roadmap, I start with the part of technology that already excites you and build a custom learning path around something you actually want to make.
That can mean lesson plans, homework, pair-debugging, architecture sketches, or an informal Discord session when you get stuck. The format and pace adapt to how you learn; the goal is for you to understand the system and keep moving without me.
Why I mentor
A clearer, more personal way into tech
I started mentoring friends who wanted to understand technology better or make a career change into tech. Most were not missing curiosity or ability. They were missing a path that made the material feel relevant, achievable, and worth coming back to.
Built for different brains
Many of the people I mentor are autistic or otherwise neurodivergent; many are also furries, and some have learning disabilities. I never assume one explanation, pace, or format works for everyone. Different learning needs change the route — not what someone is capable of learning.
02 / shape
Build a path around it
I turn that interest into a custom lesson plan, project milestones, and homework that moves you toward something you genuinely want.
03 / practice
Learn by making something real
Assignments produce working code, a safer homelab, a documented design, or another tangible result — not busywork detached from your goal.
04 / adapt
Change the explanation, not the learner
If something does not click, I change the example, medium, pace, or amount of structure until we find a route that does.
05 / support
Stay available without taking over
I provide context, questions, debugging help, and feedback at each step while keeping the decisions and hands-on work yours.
06 / connect
Turn progress into direction
We connect what you built to the next useful skill, a portfolio story, or a clearer idea of which technical career paths fit you.
What I help with
The stuff sessions tend to cover
A starting menu, not a syllabus — we go wherever your project or curiosity leads.
Programming fundamentals
The why under the syntax — data, control flow, and how code actually runs, so a new language stops feeling like magic.
Project scoping
Turning a big, vague idea into a first version small enough to actually finish.
Debugging
Reading the error, forming a hypothesis, and chasing a bug to its root instead of guessing.
Software architecture
How the pieces fit — boundaries, naming, and when "simple" beats "clever."
Cybersecurity basics
Plain-language threat modeling and the boring-but-right habits that keep you safe.
Infrastructure & homelab concepts
Servers, containers, and networking — with the homelab as a low-stakes place to learn ops.
AI-assisted development
Using AI as a tutor and pair without outsourcing your understanding — knowing what it got wrong, and why.
Career-change planning
Finding the technical paths that match your interests, then choosing projects that build skill and credible proof of work.
How mentorship usually works
Your interests become the curriculum
There is a plan, but it belongs to you — we change it whenever a different explanation, pace, or project would help more.
- 01
Find the spark
We start with what interests you, what you want to change, and what kind of project would make learning feel worthwhile.
- 02
Shape a real project
I turn the idea into a custom sequence of lessons, milestones, and homework small enough to keep moving.
- 03
Build with support
You do the hands-on work; I help with context, questions, debugging, and the places where being stuck stops being useful.
- 04
Review and adapt
We look at what clicked, what did not, and what to try next — then adjust the pace, format, or project as needed.
Good topics to bring
If any of these sound like you, you're in the right place
Not sure it counts? It counts. Bring the messy version.
-
“I want to move into tech, but I have no idea which path fits me.”
-
“My first real project — where do I even start?”
-
“This error has beaten me for two days.”
-
“Is my code structured sanely, or am I painting myself into a corner?”
-
“How do I keep my accounts, keys, and home network safe?”
-
“I want to self-host something — what do I actually need?”
-
“How do I learn with AI without copy-pasting answers I don't understand?”
-
“I understand the explanation, but I cannot make it stick.”
What I care about teaching
The things worth walking away with
Tools change fast. These are the parts that keep paying off.
Fundamentals
Understanding beats memorizing — get the why and the how becomes reusable.
Accessibility
Different brains need different routes. The explanation and structure should adapt to the learner.
Safety
Good security habits picked up early save a lot of pain later.
Architecture
Systems thinking — seeing how the parts connect — is the skill that compounds.
Confidence
Knowing you can figure things out matters more than knowing any single answer.
Curiosity
The weird tangents are where a lot of the real learning hides.
Reach out
Bring me a stuck project, a career change, or a weird idea
You do not need a polished goal or the right technical words. Tell me what sounds fun, what you want to be able to do, or where learning keeps breaking down, and we will find a useful first step.