Post B6Mh6EHzPPLalahbiy by munin@infosec.exchange
 (DIR) More posts by munin@infosec.exchange
 (DIR) Post #B6Mh6E2kK59c0JZQxs by munin@infosec.exchange
       0 likes, 0 repeats
       
       RE: https://infosec.exchange/@SecureOwl/116584747509188880I always start my answer by asking what granularity they want and where in the stack they want me to start, because I -will- go into -excruciating- detail at levels I know they are not prepared to engage with.RT: https://infosec.exchange/users/SecureOwl/statuses/116584747509188880
       
 (DIR) Post #B6Mh6EHzPPLalahbiy by munin@infosec.exchange
       0 likes, 0 repeats
       
       "Oh, you choose" buddy you need to specify your scope of work better; this is a failure on your part and I am judging your competence as a project manager accordingly.
       
 (DIR) Post #B6Mh6EYIQmOJaAKd8q by munin@infosec.exchange
       1 likes, 0 repeats
       
       tho one time I did get an interviewer who -did- realize the need to scope after I specified the way in which the buckling-spring mechanism of a model-M keyboard made electrical contact and was converted into a USB HID event* and started going into how that bus was connected into the system and would be interpreted by the OS.* it's a Unicomp variant. love that keyboard. it's very loud.