3 ms·

We have one of these and it is just a terrible internally developed framework, but we are stuck with it because all teams use it. If there was more freedom on t

We have one of these and it is just a terrible internally developed framework, but we are stuck with it because all teams use it. If there was more freedom on the team level to pick better solutions, then the whole company would have likely standardized on something better by now.

yeukhon 9y ago
But the argument is you have a poor framework which was internally developed. This is considered a technical debt, and not a fault of sticking with one framework. I don't think people are arguing for only one framework is allowed, but rather the point is to establish a platform approved list of software/libraries. If you have reasons to believe moving to another framework is better in the long run, talk and bring up a plan how to address it. But I will say often people (both developers and managements) will dismiss rewrite / attempt to replace components because they think it's better off to leave things alone. This is a double sword: low morale and excitement to work on a project despite the product is unstable, but fear of failure after replacing / rewriting. strong technical leadership is often absence. This is actually quite important from both licensing and security point of view, and having such list available encourages discussions. I'd like to write one of my services in Go, but does my company have the resource to maintain Go application after I depart? What are the strong technical reasons that the service must be written in Go rather than in Python or in Java? If Go is approved, then I need to make sure management offers training / materials for developers to learn Go, and that I am available to train others (have good documentation, brown bag sessions and what not).
- quantumhobbit 9y ago
  "I don't think people are arguing for only one framework is allowed" Read the post I replied to. It advocates requiring a single framework. Yes I am worse off because the framework sucks but there is no incentive for it to improve because everyone is forced to use it. I would love an approved list as you suggest because at least that would allow some choice, but even better than that would be working at a place that trusted me as an engineer to make those decisions myself.
rco8786 9y ago
Sounds like you just need to fix the tools you have. I'm not sure how allowing everyone to choose whatever they want would somehow end in standardization.

yeukhon 9y ago

But the argument is you have a poor framework which was internally developed. This is considered a technical debt, and not a fault of sticking with one framework. I don't think people are arguing for only one framework is allowed, but rather the point is to establish a platform approved list of software/libraries. If you have reasons to believe moving to another framework is better in the long run, talk and bring up a plan how to address it. But I will say often people (both developers and managements) will dismiss rewrite / attempt to replace components because they think it's better off to leave things alone. This is a double sword: low morale and excitement to work on a project despite the product is unstable, but fear of failure after replacing / rewriting. strong technical leadership is often absence. This is actually quite important from both licensing and security point of view, and having such list available encourages discussions. I'd like to write one of my services in Go, but does my company have the resource to maintain Go application after I depart? What are the strong technical reasons that the service must be written in Go rather than in Python or in Java? If Go is approved, then I need to make sure management offers training / materials for developers to learn Go, and that I am available to train others (have good documentation, brown bag sessions and what not).

quantumhobbit 9y ago
"I don't think people are arguing for only one framework is allowed" Read the post I replied to. It advocates requiring a single framework. Yes I am worse off because the framework sucks but there is no incentive for it to improve because everyone is forced to use it. I would love an approved list as you suggest because at least that would allow some choice, but even better than that would be working at a place that trusted me as an engineer to make those decisions myself.

rco8786 9y ago

Sounds like you just need to fix the tools you have. I'm not sure how allowing everyone to choose whatever they want would somehow end in standardization.