NSSec

4 ms·

1. 1.▲
   by NSSec 8y ago

   I agree. I shouldn't have added 'were hacked'. It distracts from what I'm trying to say. Your conclusion that I'm saying is a recipe for putting off work is exactly opposite of what I'm trying to say. My point
2. 2.▲
   by NSSec 8y ago

   I'd say OKR work is/should be all work. Each task should be aimed toward moving forward on the goal. It doesn't mean however, that you can directly link one specific task to the OKR. It's just part of the strategy to ach
3. 3.▲
   by NSSec 8y ago

   IMO, you don't. Operational security isn't (or shouldnt be :)) a specific _ business goal_ for a company. With that I mean it's not a specific objective to achieve: it should be a base principle that should be part of your
4. 4.▲
   by NSSec 8y ago

   | "Write an integration test for xyz" is not really what OKRs are designed for. This gets it backwards. This is a task. Why are you performing this task? Especially without being tied to specific development? If you can't jus
5. 5.▲
   by NSSec 8y ago

   Not immediately obvious from the text indeed, but I'm certain they mean (the joy that is) XMLSEC and JWS here. Not sure about JWS but XMLSEC certainly has similarities to the format described here: you define exactly what parts are inc
6. 6.▲
   by NSSec 8y ago

   Sorry buddy, us dutchies got them too. Also, I think 'wascloths' aren't as special as you think.