rov14Feedback archive

Mentorship / Field notes

Raw Engineer Feedback

Feedback from engineers I've taught and mentored across the 2025 and 2026 cohorts. Kept close to the original words so you can judge the work for yourself.

DevOps · Systems Design · Platform Engineering · Reliability Engineering

2025 — 2026 · Multiple cohorts · Practical engineering training

See how I teach ↓
Context

What they were being trained to do

The programs are designed around practical engineering rather than passive lectures. Engineers work through real infrastructure and systems problems, make architectural decisions, deploy services, diagnose failures, defend designs, and document the scars they acquire along the way.

  • Systems design
  • AWS and cloud infrastructure
  • DevOps
  • CI/CD
  • Infrastructure as Code
  • Containers and orchestration
  • Platform engineering
  • Observability
  • Reliability engineering
  • Production readiness
  • Incident thinking
  • Ownership and engineering judgment

The curriculum evolves between cohorts, so experiences may differ.

Archive

In their words

2026 cohort · Systems DesignPLACEHOLDER

[Engineer name]

[Role] · 2026 Engineering Cohort

[Feedback entry goes here — this is a development placeholder, not a real quote. Real feedback will be published here once the engineer has reviewed and approved it.]

Systems Design · ReliabilityPlaceholder — awaiting a real, permitted submission.Permalink →
Field note / 002 · DevOpsPLACEHOLDER

[Engineer name]

[Role] · 2026 Engineering Cohort

[Feedback entry goes here — placeholder.]

DevOps · Platform EngineeringPlaceholder — awaiting a real, permitted submission.Permalink →
2025 cohort · ReliabilityPLACEHOLDER

[Engineer name]anonymous

2025 Engineering Cohort

[Feedback entry goes here — placeholder, published anonymously.]

Reliability · DevOpsPlaceholder — awaiting a real, permitted submission.Permalink →
2025 cohort · Systems DesignPLACEHOLDER

[Engineer name]

[Role] · 2025 Engineering Cohort

[Feedback entry goes here — placeholder.]

Systems Design · Platform EngineeringPlaceholder — awaiting a real, permitted submission.Permalink →

Entries marked PLACEHOLDER are development stand-ins. No feedback on this page is invented or attributed to a real person without permission.

Patterns

What engineers say changed

Systems thinking
Moving from completing tasks to understanding how systems behave.
See supporting feedback →
Production judgment
Learning to think beyond “it works” toward failure, reliability, security, and operations.
See supporting feedback →
Ownership
Becoming more comfortable defending engineering decisions and taking responsibility for outcomes.
See supporting feedback →
Debugging
Developing a systematic way of investigating failure rather than guessing.
See supporting feedback →
Confidence
Becoming more comfortable working with unfamiliar infrastructure and complex systems.
See supporting feedback →
Learning moments

The scars matter more than the slides.

Much of the learning happens when something breaks, an assumption turns out to be wrong, or an engineer has to explain why a design failed. I encourage engineers to record those moments rather than hide them.

  1. 01

    The deployment worked locally and failed in AWS.

    What changed: Understanding environment assumptions and runtime dependencies.

  2. 02

    A security group looked correct until one service could reach something it shouldn't.

    What changed: Thinking about network boundaries through negative tests.

  3. 03

    The database index didn't fix the latency problem.

    What changed: Learning to investigate workload shape rather than reaching for familiar fixes.

Provenance

Original submissions

Where permission exists, the original submission can be inspected — written feedback, cohort reviews, articles, LinkedIn recommendations, or submitted forms. Any edit is limited to spelling, formatting, or privacy, and is labelled.

  • [Engineer name]2026 Engineering CohortPlaceholder — awaiting a real, permitted submission.
  • [Engineer name]2026 Engineering CohortPlaceholder — awaiting a real, permitted submission.
  • [Engineer name]2025 Engineering CohortPlaceholder — awaiting a real, permitted submission.
  • [Engineer name]2025 Engineering CohortPlaceholder — awaiting a real, permitted submission.
Mentorship

How I teach

I'm less interested in teaching engineers to reproduce commands than helping them develop judgment. The work is structured around real constraints, difficult questions, ownership, operating failures, and explaining why a system should be trusted in production.

Still learning. Still teaching.

These cohorts are part of an ongoing body of work around developing engineers who can reason about real systems, not just use tools.

← Back to rov14