Reply to thread

Message

<blockquote data-quote="kigmatzomat" data-source="post: 9534536" data-attributes="member: 9254">That or you can make the case that it will make more money or can plausibly avoid a material loss.&nbsp; I spent a lot of time on risk mitigation projects.Which is something WotC should have done to avoid those canceled accounts.Off topic[Spoiler]My life got both easier and harder when I became the &quot;best friend&quot; of the corporate lawyer who was involved in those government audits.&nbsp; Easier as the budget got freed up PDQ.&nbsp; Harder because I got shifted into other processes that were related but not in my primary domain. Risk mitigation projects kind of suck as on one hand they require really big numbers to justify (or jail time) and then they are usually not materially impactful other than averting those big numbers (or jail time).&nbsp; So low level of accomplishment with high stress.&nbsp; You almost want one or two &quot;near misses&quot; where someone else in the company screws up but your process catches it before a regulator does.&nbsp; Almost.I &quot;downsized&quot; my stress by going from running a team of 8 developers to being an application architect in a different industry where the corporate impact is both more direct and less authoritative.&nbsp; [/spoiler]</blockquote>

[QUOTE="kigmatzomat, post: 9534536, member: 9254"] That or you can make the case that it will make more money or can plausibly avoid a material loss. I spent a lot of time on risk mitigation projects. Which is something WotC should have done to avoid those canceled accounts. Off topic [Spoiler] My life got both easier and harder when I became the "best friend" of the corporate lawyer who was involved in those government audits. Easier as the budget got freed up PDQ. Harder because I got shifted into other processes that were related but not in my primary domain. Risk mitigation projects kind of suck as on one hand they require really big numbers to justify (or jail time) and then they are usually not materially impactful other than averting those big numbers (or jail time). So low level of accomplishment with high stress. You almost want one or two "near misses" where someone else in the company screws up but your process catches it before a regulator does. Almost. I "downsized" my stress by going from running a team of 8 developers to being an application architect in a different industry where the corporate impact is both more direct and less authoritative. [/spoiler] [/QUOTE]

Verification