Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Demolishun842633dI see a lot of these posts about some task is deemed not worthy of my time. If it was really low value would it show up as a metric on a managers docket? Businesses are designed around systems theory (not sure the right term). So managers have their own business reasons for doing things. So is this a domain knowledge issue? I am sure a manager would view things that a programmer does as low value if they don't understand the reasoning behind it.
soggybutter7232d@Demolishun the problem with a lot (not all) of the types of things I'm talking about is we often circumvent the actual value-add in order to show up green on a report. Dumb example: We submitted our code for automated testing to our security scanner, just to show up green, because the app itself wasn't supported. Later, there was a vulnerability in a dependency that required us to cut the dependency out of our tests. Again, so we show up green on a report. This was in code that never ran on production infra, that had no security scanning requirements.
Other instances are easier to see at least SOME value-added, but the continued work required to remain in self-imposed compliance is not small.
Demolishun842632d@soggybutter Is there a way to flag items as "not being used" or something? Like a way to inform management of waste or inefficiency (terms they can relate to). I get it, its busy work to satisfy a metric. We have some of that too.
For instance, when taking time off I have to fill out a form with the requested time off. I tell the manager that I want this off and he reminds me that I need to fill out this form. To me it is basically TPS, but to my manager he is using this to track "something". I don't understand that something, but it has value to him for his system (business).
soggybutter7232d@Demolishun Unfortunately there isn't. And after a few discussions about that we were told to just make the report happy so it stopped coming up. The same security tool will fail your project if you don't have any third party dependencies, because it assumes you did something wrong 🤷♂️
I'm sure there are good theoretical reasons for most of the things that get passed down to us. The hard thing is that there's virtually zero nuance when it's a large company. Everyone gets the same blanket requirements even though the projects are extremely varied.