A project page shows the finished system. These field notes record the decisions behind it: commands, measurements, failed approaches, and checks that proved the result.

Topics I cover

The archive focuses on work I can test and explain:

  • embedded systems, firmware, sensors, and connected-device architecture;
  • Linux, networking, and legal cybersecurity challenges;
  • Flutter interfaces for physical products;
  • robotics and control systems;
  • AI and machine-learning experiments with reproducible inputs and results.

Some entries are short references. Longer walkthroughs include the environment, commands, expected output, failure modes, and files needed to repeat the work.

How I write a walkthrough

A walkthrough should help the reader recognize the problem again. My longer articles follow a consistent structure:

  1. define the goal and constraints;
  2. record the environment and prerequisites;
  3. show the investigation or design process;
  4. explain the working solution;
  5. document common failure modes;
  6. finish with reusable checks or lessons.

A useful technical note gives the reader a method they can apply elsewhere.

Reproducible examples

Commands appear in copyable terminal blocks:

ssh user@example-host -p 2220

I record versions, dependencies, configuration, and expected output when they change the result. Security articles stay within legal labs, owned systems, and defensive learning.

Series in progress

The OverTheWire Bandit walkthrough covers Linux commands and problem-solving in a controlled challenge environment. The Learn With Me series develops practical foundations in Linux, Python, Dart and Flutter, and Git.

The archive grows alongside active engineering and teaching work. If an entry helps another person verify a result or avoid a repeated mistake, it has served its purpose.