Recap
Tried to use mdx, it was a slight nightmare. I realize now that I rather just be able to write and not have to worry about writing and coding at the same time. I have some strong feelings with regards to software/libraries that focus on a business use. I’ve reverted it, and I am keeping the posts that I made during that time.
Instructional design
Instead of giving spurts of motivation in the course, I want it to be well established at the beginning and maintained throughout the course. You’ll never have to wonder why you are doing something, because I’ll tell you the implications in a context.
I think I want to do something like SAM for design. The idea is to get the lessons out in front of people, for free, early on. Then once the course has been made, making revis…
Recap
Tried to use mdx, it was a slight nightmare. I realize now that I rather just be able to write and not have to worry about writing and coding at the same time. I have some strong feelings with regards to software/libraries that focus on a business use. I’ve reverted it, and I am keeping the posts that I made during that time.
Instructional design
Instead of giving spurts of motivation in the course, I want it to be well established at the beginning and maintained throughout the course. You’ll never have to wonder why you are doing something, because I’ll tell you the implications in a context.
I think I want to do something like SAM for design. The idea is to get the lessons out in front of people, for free, early on. Then once the course has been made, making revisions/adjustments from comments, and then packaging it up and selling it. This way I can focus on learner value on a video/lesson basis, and it would allow me to grow and iterate throughout the process of creating the course.
Learning goals
- I want people to be able to use textual SysML in a variety of contexts.
- I want people to be able to describe unfamiliar areas with textual SysML.
- I want people to begin to be able to prescribe system structure with textual SysML.
Audience
- Makers
Constraints
Video hosting
- File size
- Video length
- Formats
Course platform (someone elses website)
- Content ownership and copyright
- Prohibited materials
- External promition limits
- Course-setup and bonus-lecture rules
- Behavior & communication
- Quality review process
- License & exclusivity terms
If I wanted to do the SAM thing and get feedback on platforms it would constrain what platforms I could use. I could either get feedback and potentially make it better, or I could sell it. I could probably make my own LMS using open source stuff, but that would put more time and effort into something I don’t know is going to be worth it.
Moodle seems pretty neat, I think I might try that. The bare requirements are 200MB disk space, 1GHz processor, and 512MB for RAM. The t4g.nano satisfies the processor and ram requirements for 3.07 $/month at 100% usage. For the disk space you can use EBS, but the minimum is a GB, and it is at 4.64 $/month. This ignores the domain name cost, but the total is about 7.71 $/month to have a server running the bare minimum for moodle (except for disk space). If I were to sell a course a month at $10 per, that would cover the expenses associated with it. I could use content marketing as a means of marketing, which I already am doing (kinda), and that would help with the cost associated with the course.
Persona
I’m using Lumo to help me with the persona stuff for a maker.
Domain Expected Knowledge
Electronics
- Basic circuit theory (Ohm’s law, voltage dividers, PWM) • Ability to read schematics and datasheets for common components (sensors, LEDs, motor drivers) • Experience soldering and wiring breadboards/PCBs
Programming
- Proficiency in at least one embedded language (C/C++ for Arduino, MicroPython, or JavaScript for Node‑RED) • Familiarity with version control basics (clone, commit, push)
Mechanical Design
- Ability to model simple parts in CAD (extrude, revolve, fillet) and export STL files for 3D printing • Understanding of tolerances, material properties, and post‑processing (sanding, annealing)
Rapid Prototyping
- Comfortable iterating designs: build → test → refine • Knowledge of common prototyping workflows (breadboard → perfboard → custom PCB)
Tool Ecosystem
- Awareness of major maker platforms (Adafruit, SparkFun, Seeed Studio) and where to source parts • Ability to set up and troubleshoot development environments (IDE, driver installation)
Community Practices
- Uses online resources (forums, Stack Exchange, GitHub) for troubleshooting • Shares project files, documentation, and licensing information (often open‑source licenses)
Safety & Ethics
- Understands basic safety (electrical, laser, chemical) and follows best practices • Recognizes intellectual‑property considerations when reusing designs or code
Finally doing a brief persona by Lumo
Attributes
Name
- Mark Rivera
Age
- 28 – 45
Location
- Urban or suburban area with easy access to makerspaces, hardware stores, and online component suppliers
Occupation
- Engineer, designer, hobbyist entrepreneur, or student (often with a STEM background)
Primary Goals
- Turn ideas into tangible prototypes quickly • Learn new tools/technologies on the fly • Share projects with a community for feedback and collaboration
Motivations
- Curiosity and the joy of problem‑solving • Desire for self‑expression through physical objects • Potential to monetize a prototype or open‑source it
Frustrations
- Inconsistent documentation for hardware/software combos • Long lead times for parts • Over‑complicated interfaces that hide the “how”
Typical Activities
- Designing circuits on breadboards or PCBs • 3D‑printing parts and enclosures • Programming microcontrollers (Arduino, ESP32, Raspberry Pi) • Using CAD software (Fusion 360, Tinkercad) • Participating in hackathons, meet‑ups, or online forums
Preferred Channels
- YouTube tutorials, maker blogs, and subreddits • Discord/Slack maker communities • Local hackerspaces and fab labs
Tools & Platforms
- Open‑source hardware (Arduino, ESP‑series, Raspberry Pi) • CAD/CAM software (Fusion 360, Blender) • Version control (Git/GitHub) • Cloud‑based IoT dashboards (ThingSpeak, Adafruit IO)
Personality Traits
- Hands‑on, iterative, and comfortable with trial‑and‑error • Collaborative but also enjoys solo “garage” projects • Resourceful – often repurposes existing parts
I think I am going to create a git repository for the course to help keep it all together, and something that is going to go into it will be the persona with various domains with experience levels. I was really wanting to create a course outline, and maybe even get the first lesson written, but that will have to wait until later.