I understand where you’re coming from “freaking out”. I didn’t want to write an overwhelming amount in the post. Perhaps that was a mistake. I won’t make new w

I understand where you’re coming from “freaking out”. I didn’t want to write an overwhelming amount in the post. Perhaps that was a mistake. I won’t make new work for people they didn’t sign up for. That isn’t fair. I suggested a lot of changes and change can be scary. I’ve listened and already rotated through around 40% of development teams. There isn’t a wiki or centralized documentation management system, so it’s not the 14th place to contain all docs. The docs that do exist haven’t been updated in years and are hidden away in random locations. Myself and my team will be writing a lot of the docs ourselves. In fact wejust hired 2 technical writers. Scanning repos for secrets is needed because they have a LOT of secrets in their repos. That isn’t good, so I dug into it. The reason why they are there is because the average developer finds it “too difficult” to manage these in cloud. That’s a pain point that we are going to address BEFORE scanning and requiring the end developers to make changes. Linting isn’t going to be turned on and you now have 5000 items to fix. First off, we plan on making essentially automated codemods to fix most of the easy issues. Secondly, we are setting the target state in conjunction with the tech leads on all the teams. Manual fixing of linting issues is nuts when you are talking about millions of loc. The survey will be (max) 15 questions with multiple choice and 1-2 free text maximum. You don’t have to fill it out at all. I also will be hosting “office hours” and plan on being accessible as possible. I have to take some sort of measurement, otherwise how will I know how myself and my team are doing? No one is making you use our templates, but we have already measured better velocity. Everything is opt in and distributed using shared libraries. If you want to do things differently you can either not use my teams stuff, raise an issue and we will see if we can include it or open a PR with a change. Devops is part of devex, I guess we will have to disagree. If people are having trouble with their pipelines and that’s a development pain point, then that is directly in my wheelhouse. I’m not better than the 200 people that have come before me. I’m going to listen and adapt. I just wanted some outside feedback from other engineers. I don’t look at myself as dictating changes, but rather advocating for developers and delivering them QoL changes.