Thomas Vignoli Portfolio
Tech Lead · DevOps & Cloud
A tech lead who writes about his own infrastructure: dated case studies on a homelab firewall and alerting, plus a public lab that watches what bots do to a server with no defences on purpose.
Location
Didn't say. We're respecting the mystery.
Skills
What makes it work
A breakdown of the choices that make this portfolio stand out.
Writing from the infrastructure he runs
The three dated articles on the homepage cover a firewall that locked out its own network, defence in depth behind a consumer router, and alerting that notices when it breaks. Each comes from the home setup.
A public lab that publishes its own data
The lab page shows live observations of bot traffic, with the update schedule shown on each panel, rather than a summary written later.
What DevOps Engineers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Write up a failure in your own setup with the cause and the fix, the way the firewall case study does.
Publish the measurement you run on your own system so a reader can check what you say about it.
Case studies
Three dated articles and one live lab. The lab is an observation project with no end date.
Case study: an IPv6 firewall that locked out its own LAN
A case study of an IPv6 firewall ruleset that blocked the home network it was meant to protect, published as a written post-mortem.
A written account of a self-inflicted outage tests the reasoning an on-call engineer needs, which a tutorial does not.
Written up as a case study with its own tags
Covers IPv6 and nftables rules on a home network
Published alongside two related articles on the same setup
Defense in Depth Behind a Consumer Router
An article on layering security behind a consumer router, tagged Security, Networking, IPv6 and Homelab.
Layered controls on a constrained network show judgment about where each control belongs.
Tagged Security, Networking, IPv6 and Homelab
Published as part of the same run of homelab write-ups
Silent Failures: Alerting That Notices When It Breaks
An article on alerting that detects when the monitoring itself has stopped working.
Monitoring that watches itself is a reliability problem most alerting setups skip, and the article addresses it directly.
Tagged Observability, Alerting and Reliability
Written from the same homelab setup as the other case studies
Projects
Lab: honeypots, canary tokens and live bot traffic
A public lab that watches what bots do to a server with no defences on purpose, with fake keys left in places where they are found.
The observations are published as they are collected, so a claim about bot behaviour can be checked against the data on the page.
Live observations of bot traffic on a server with no defences
Decoy AWS keys with time-to-first-use shown
Panels updated hourly, every five minutes, or nightly, as labelled on the page
More DevOps Engineer portfolios
Ready to build your portfolio?
Follow the DevOps Engineer roadmap — skills, projects, and timeline to get hired.