One Article Review
| Source |  NoticeBored |
|---|---|
| Identifiant | 1570352 |
| Date de publication | 2020-02-26 20:23:36 (vue: 2020-02-29 05:00:23) |
| Titre | NBlog Feb 26 - a good day down the salt mine |
| Texte |  The remaining items for the recycled InfoSec 101 module are falling rapidly into place. It will be a bumper delivery with fifty (yes, 50) files already in the bag.One of the regular end-of-month jobs involves matching up the awareness items - the files - with the contents listing and their descriptions in the train-the-trainer guide. Years back I came up with a simple numeric naming scheme to make it easier to get the files in order and link them with the listings. Good thing too: this afternoon I came across one listed item that I've decided to drop from the module, and about three additions that need to be listed and described. There's still a little time left before delivery to change things further and renumber, again, if we need to ... which emphasises the value of these final quality checks before packaging and despatch.Another part of the quality assurance process is to open and review the content of all the files. This is our last chance to spot speling mishtakes, errror, omissons and half-finishedI've already made a couple of passes through the materials: the first pass often reminds me of things I've brought up in one item that ought to be repeated or reflected in others, so there's a bit of back-and-forth refinement ... but the looming deadline means eventually I have call a halt to the spit-n-polish phase. It's tough for me to stop when the materials are 'good enough' rather than 'perfect' but I console (or is it delude?) myself by thinking that nobody but me will spot most of what I consider to be the remaining errors, while it's unlikely I will ever a some further tranche of errors due to my inherent blind spots.So I keep calm and carry on.In risk terms, I'm consciously making a trade-off. I could carry on checking and refining the content indefinitely but I'd blow the delivery deadline. Alternatively I could stop right now and deliver the module as-is, but I'd be distraught to discover significant problems later on ... which does happen sometimes when I re-read stuff I have written, checked and published some months or years earlier. Some of the problems that catch my beady now are genuine boo-boos that I should really have spotted corrected at the time. Some are things I would put differently now because I've changed and the infosec world has mov |
| Envoyé | Oui |
| Condensat | 101 about accepted across activities additions afternoon again all almost already also alternatively although another appreciate are assurance awareness back bag beady because before best bit bleed blind blow boo boos born brought bumper but call calm came can carry case catch certainly chance change changed check checked checking checks consciously consider console content contents correct corrected cost costs could couple customers customise day deadline decided deliver delivery delude described descriptions despatch despite differently discover distinctly distraught does don down drop due each earlier easier efforts embarrassed emphasises end enough errors errror etc eventually ever evidently factual falling feb fifty files final finished finishedi first forth from further genuine get good guide half halt happen has have honest human impacts indefinitely industry/business information infosec inherent involves issues item items jobs keep last later learn left link listed listing listings little live looming made make making matching materials materials: means might mine mishtakes mistakes module month months more most moved myself naming nblog need needs new nobody now numeric obvious off often omissons one only open order organization others ought packaging part pass passes perfect perfection phase place plan polish problems process published put quality quite rapidly rather read really receipt recycled refinement refining reflected regular remaining reminds renumber repeated repeatedly review rework right risk risks salt same scheme should significant simple situation some sometimes specific speling spit spot spots spotted stop stuff suit terms than that them there these thing things think thinking three through time too: tough trade train trainer training tranche unlikely value what when which whom will world would writing written wrong years |
| Tags | |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.