Re:Tell HN: I love programming but am sick of the software i...
by giantg2 on Friday June 25, 2021 @10:40AM
(#27631347)
I hate my job.
I see what you mean about resistance to change. I've encountered it, although usually from a process/system/logic perspective rather than straight technology. Stuff like my prior tech lead wanting to build out a complicated screen to rerun jobs/items in the system. The reason for this is the support team needs help with this. The reason they need help with it, is because we don't have documentation on how to handle each issue. So instead of simply creating the documentation and having knowledge transfer, he wants to build out a new screen... which would require additional documentation, maintenance, and knowledge transfer.
I've also seen the other way, where they are too accepting of new technology. It's a constant parade of new stuff on my current team. We have integrations for cloudwatch, splunk, opentelemetry/honeycomb, servicenow, pagerduty, a data lake, tableau, etc. I get that some of these enable specific features, but a lot of them seem are redundant (especially the way we use them) . Can we just pick one alerting system, one logging system, and one reporting system? And maybe we can stick with that system for a few years instead of refactoring to integrate the newest thing into our 5-10 apps almost as soon as we finished the integration of the prior thing. All that churn could be better spent delivering value and just integrate the new service when it's truly compelling. Maybe we could get rid of the prior services that are essentially being replaced to increase the maintainability too and streamline the process.
In my company, the resistence to or over adoption of new tech is really just a facade concealing a bigger issue with the underlying processes of the system itself, the bureaucracy, or the business processes.
I see what you mean about resistance to change. I've encountered it, although usually from a process/system/logic perspective rather than straight technology. Stuff like my prior tech lead wanting to build out a complicated screen to rerun jobs/items in the system. The reason for this is the support team needs help with this. The reason they need help with it, is because we don't have documentation on how to handle each issue. So instead of simply creating the documentation and having knowledge transfer, he wants to build out a new screen... which would require additional documentation, maintenance, and knowledge transfer.
I've also seen the other way, where they are too accepting of new technology. It's a constant parade of new stuff on my current team. We have integrations for cloudwatch, splunk, opentelemetry/honeycomb, servicenow, pagerduty, a data lake, tableau, etc. I get that some of these enable specific features, but a lot of them seem are redundant (especially the way we use them) . Can we just pick one alerting system, one logging system, and one reporting system? And maybe we can stick with that system for a few years instead of refactoring to integrate the newest thing into our 5-10 apps almost as soon as we finished the integration of the prior thing. All that churn could be better spent delivering value and just integrate the new service when it's truly compelling. Maybe we could get rid of the prior services that are essentially being replaced to increase the maintainability too and streamline the process.
In my company, the resistence to or over adoption of new tech is really just a facade concealing a bigger issue with the underlying processes of the system itself, the bureaucracy, or the business processes.