Right, so there's probably a discussion that needs to be had with your enterprise architecture team on why said stack was used (irrespective of skill sets available) when certain features are available "for free" (e.g. the DesignSystem)
I'll have a wild stab in the dark in saying that if the stack is really tightly coupled, that there's extra labour required by the dev team to meet the Digital Service Standard. Which is, really speaking, unnecessary public expenditure.
You are preaching to the choir here mate. Keep in mind we have over 60 developers, and over 100 single page applications under development/support.
The frameworks we are using have been in use here since 2014 (pre-dating the DesignSystem). It is not an easy matter to switch over to these components, especially considering the only framework supported is React.
As far as unnecessary public expenditure... I could probably write 1000 pages on it and not make a dent.
svict4|7 years ago
I'll have a wild stab in the dark in saying that if the stack is really tightly coupled, that there's extra labour required by the dev team to meet the Digital Service Standard. Which is, really speaking, unnecessary public expenditure.
deadcat|7 years ago
The frameworks we are using have been in use here since 2014 (pre-dating the DesignSystem). It is not an easy matter to switch over to these components, especially considering the only framework supported is React.
As far as unnecessary public expenditure... I could probably write 1000 pages on it and not make a dent.