OverTheWire
Bandit Walkthrough
Each entry explains the level goal, investigation, working command, Linux concept, and a way to verify the result.
- DraftOverTheWire Bandit: A Better Way to Document the Journey
Field notes / reproducible methods
I document the commands, design decisions, tests, and failure modes behind embedded systems, Linux, cybersecurity, Flutter, and AI work.
Choose the Bandit walkthrough or a Learn With Me track. Drafts stay marked as drafts until the complete article is public.
OverTheWire
Each entry explains the level goal, investigation, working command, Linux concept, and a way to verify the result.
Learn With Me
Connected lessons build useful habits in Linux, Python, Dart and Flutter, and Git.
Shell use, permissions, processes, networking, and system troubleshooting.
No public lessons yet.
Programming foundations, automation, data work, and engineering scripts.
No public lessons yet.
Dart foundations and Flutter interfaces for mobile and connected products.
No public lessons yet.
Version-control habits, safe recovery, branches, and team workflows.
No public lessons yet.
Digital logic, circuit analysis, PCB concepts, and hardware experimentation.
No public lessons yet.
Cybersecurity concepts, information security practice, and legal challenge labs.
No public lessons yet.
Image processing pipelines, machine learning experiments, and AI-assisted engineering.
No public lessons yet.
Search published articles by subject, tool, or category.
Editorial queue / evidence first
Questions worth answering with calculations, project evidence, and reproducible tests. Cards become articles only after the answer is complete.
A practical path from requirements and signal flow to a bench prototype, with checkpoints for interfaces, power, firmware, and evidence.
A decision guide for connectivity, provisioning, storage, updates, and failure recovery before an ESP32 prototype becomes a maintained product.
A trace through EIRP, path loss, antenna gain, system noise, bandwidth, and required Eb/N0 that shows where a weak link actually loses margin.
A system-level review of command loss, stale telemetry, motor authority, emergency states, and the tests that expose unsafe assumptions on the bench.
A comparison based on data volume, explainability, latency, lighting variation, maintenance cost, and the failure cases each approach handles well.
A design method for inputs, assumptions, diagrams, sensitivity, units, and interpretation so a calculator improves judgment instead of returning one unexplained number.