NetLay: Letting the robots audit it
Five automated reviewers, one job each, about seventy five findings, and the first one meant stop sharing this on the network until it is fixed.
Games, apps, and the occasional detour.
Tag
29 posts tagged “Networking”.
Five automated reviewers, one job each, about seventy five findings, and the first one meant stop sharing this on the network until it is fixed.
Still waiting on switch configs, I got the one thing the network team could send quickly, a list of subnets, and it turns out that is enough to know which VLAN everything is in.
Twenty one thousand lines of code with a manual for its users and nothing for whoever opens it next, and three checks that prove three thousand comments changed nothing.
A manual made of screenshots goes stale the day a feature lands, so the robot ran again, and once again the act of taking the pictures found the bugs.
Pinging an address works until DHCP hands it to somebody else, at which point a laptop looks down and a stranger's phone is wearing your printer's name.
The portable folder always listened on localhost and nobody else could reach it, so now it asks one question at startup and deals with the Windows firewall for you.
A model is only as good as the things it refuses, so I spent an evening attacking my own API with every bad idea I could think of, and two of them worked.
Twenty posts of features and no way for a colleague to find any of them, so the app grew a guide, with pictures taken by a script so they cannot quietly go stale.
Two things you only miss standing in a comms room, a picture of the box you are hunting for and a line on the map that follows the route the real cable takes.
After nineteen features, a sense check of the screens rather than the code, driven by a headless browser taking thirty screenshots, and the dozen things it found that no test ever would.