5 ms·

So what? I've worked places with lots of regulation. Part of every development job is learning the product domain. In that case devs become comfortable with

So what? I've worked places with lots of regulation. Part of every development job is learning the product domain. In that case devs become comfortable with reading standard/law/regulations and anticipating when software implementation might interact with the areas covered. Sure there were people who's job was to offload as much compliance work from everyone else; by turning it into internal requirements, participating in design discussion and specializing in ensuring compliance. But trying to isolate the development team from it is just asking for micromanagers.

bayindirh 1y ago
> So what? Think before you act. The machine has no brain. Use yours. > Part of every development job is learning the product domain. Yes. > In that case devs become comfortable with reading standard/law/regulations and anticipating when software implementation might interact with the areas covered. This is what I'm saying, too. A developer needs to think whether what they are doing is OK by the regulation they're flying against. They need to ask for permissions by asking themselves "wait, is this OK by the regulation I'm trying to comply?". > But trying to isolate the development team from it is just asking for micromanagers. Nope, I'm all for taking initiatives, and against micromanagement. However, I'm also against "I need no permission because I'm doing something amazing" attitude. So own your craft, "code responsibly".
- dogleash 1y ago
  Oh, I thought you were disagreeing with hamandcheese's point that every little decision doesn't need to go through a product owner before anything happens.
  - bayindirh 1y ago
    No, not at all. by "the book", I meant regulations, not the management. :)
    - mike22 1y ago
      But it happens to be that product managers know (or at least about) and keep tabs on the relavent regulatory environment. I think it’s not scalable if every SWE in the team is going to legal to understand things. Like why we actully do need to hard delete data when customers click the Delete button.
      - bayindirh 1y ago
        If you force every SWE to go to legal for every technical decision, or ask for permission, it's not scalable, yes. On the other hand, if the team is in the long haul of developing this kind of regulated applications, the knowledge will get accumulated over time, and it'll trickle down from product managers to seniors to juniors. This is the kind of tribal knowledge you want to spread among a development team, and if a collaborative document of "Why it's done this way" can be propped up with pointers to relevant sections of the regulation, it'd be a very good thing. Not unlike NASA's global Lessons Learnt document.

bayindirh 1y ago

> So what? Think before you act. The machine has no brain. Use yours. > Part of every development job is learning the product domain. Yes. > In that case devs become comfortable with reading standard/law/regulations and anticipating when software implementation might interact with the areas covered. This is what I'm saying, too. A developer needs to think whether what they are doing is OK by the regulation they're flying against. They need to ask for permissions by asking themselves "wait, is this OK by the regulation I'm trying to comply?". > But trying to isolate the development team from it is just asking for micromanagers. Nope, I'm all for taking initiatives, and against micromanagement. However, I'm also against "I need no permission because I'm doing something amazing" attitude. So own your craft, "code responsibly".

dogleash 1y ago
Oh, I thought you were disagreeing with hamandcheese's point that every little decision doesn't need to go through a product owner before anything happens.
- bayindirh 1y ago
  No, not at all. by "the book", I meant regulations, not the management. :)
  - mike22 1y ago
    But it happens to be that product managers know (or at least about) and keep tabs on the relavent regulatory environment. I think it’s not scalable if every SWE in the team is going to legal to understand things. Like why we actully do need to hard delete data when customers click the Delete button.
    - bayindirh 1y ago
      If you force every SWE to go to legal for every technical decision, or ask for permission, it's not scalable, yes. On the other hand, if the team is in the long haul of developing this kind of regulated applications, the knowledge will get accumulated over time, and it'll trickle down from product managers to seniors to juniors. This is the kind of tribal knowledge you want to spread among a development team, and if a collaborative document of "Why it's done this way" can be propped up with pointers to relevant sections of the regulation, it'd be a very good thing. Not unlike NASA's global Lessons Learnt document.