4 ms·

You can not beg for forgiveness if you don't have a formal approval to allow your changes into the product. In multi-team environment it's impossible to push yo

by zqna 5y ago

You can not beg for forgiveness if you don't have a formal approval to allow your changes into the product. In multi-team environment it's impossible to push your code into production if you aren't aligned with the rest of organization. There are all types of gatekeeping and quality checks that prevent from any cowboy action. Most of the time that's for good, and sometimes it hurts, because of different views, mindsets and experience of people who are taking those decisions.

strken 5y ago
If the specific change is a 10-hour rewrite that's self-evidently better than the old code, you absolutely can beg for forgiveness once you've written it, since you don't have to merge or deploy it anywhere. You're going to quit anyway, so who cares whether your boss tells you off for spending a day or two attempting to solve a legitimate business problem?
- h4waii 5y ago
  If you're going to quit, why spend 10 hours of your own life solving a legitimate business problem that won't benefit you in any seemingly measurable way?
  - strken 5y ago
    Because most human beings are intrinsically motivated to help people and all things being equal you might as well? I don't really understand what point you're making here.
redshirtrob 5y ago
This. Even if you work in a small shop, SOC 2 Type II Security is starting to become table stakes for any kind of formal business arrangement. This means you have a formal Change Management process which includes peer review and peer testing. If you push your code and ask forgiveness in this environment you're risking your company's SOC2 compliance. The auditors are not going to care about the business impact. Their priority is to make sure you're following the process you wrote. At best you'll get an exception for that control. At worst you'll get a Qualified Opinion. I would not want to be the developer who violated controls and caused the auditors to render a Qualified Opinion. In that case the management response will likely indicate you've been sacked. Peer review is a good thing. Mature organizations have been doing it forever. It was already endemic at my first real job in '98. We're finally seeing that discipline forced on the industry from the outside. By and large we haven't done a good enough job ourselves so now the AICPA is involved. Get used to it.

by zqna 5y ago

strken 5y ago

If the specific change is a 10-hour rewrite that's self-evidently better than the old code, you absolutely can beg for forgiveness once you've written it, since you don't have to merge or deploy it anywhere. You're going to quit anyway, so who cares whether your boss tells you off for spending a day or two attempting to solve a legitimate business problem?

h4waii 5y ago
If you're going to quit, why spend 10 hours of your own life solving a legitimate business problem that won't benefit you in any seemingly measurable way?
- strken 5y ago
  Because most human beings are intrinsically motivated to help people and all things being equal you might as well? I don't really understand what point you're making here.

redshirtrob 5y ago

This. Even if you work in a small shop, SOC 2 Type II Security is starting to become table stakes for any kind of formal business arrangement. This means you have a formal Change Management process which includes peer review and peer testing. If you push your code and ask forgiveness in this environment you're risking your company's SOC2 compliance. The auditors are not going to care about the business impact. Their priority is to make sure you're following the process you wrote. At best you'll get an exception for that control. At worst you'll get a Qualified Opinion. I would not want to be the developer who violated controls and caused the auditors to render a Qualified Opinion. In that case the management response will likely indicate you've been sacked. Peer review is a good thing. Mature organizations have been doing it forever. It was already endemic at my first real job in '98. We're finally seeing that discipline forced on the industry from the outside. By and large we haven't done a good enough job ourselves so now the AICPA is involved. Get used to it.