It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Vue or React are next-project goals. In an existing codebase, introducing a frontend framework like that is a rewrite level effort.
But you can still use npm/yarn/etc! At the end of the day, you're serving a bunch of JavaScript files. A package manager can take care of getting thirdparty dependencies in one place to be served. Bundlers can help you manage your own code. None of this necessitates renovating your entire frontend.
Selling this kind of initiative as a junior member of the team means you need to have an answer for the question "how will this start making our lives better in the very near future?". It's not unlikely that the manual approach has had painful effects: dependency scripts in different places, having to track something down through spaghetti in order to use it, multiple versions of jQuery kicking around, that kind of thing. Look for those. If you have a solution in search of a problem, shelve it for next time.
Your feedback definitely aligns with what I was thinking, and what others are saying as well. I will avoid big changes, like a front-end framework, and focus on smaller, easier to digest improvements.
I am going to start looking into how something like NPM could improve some of the problems we face today. I agree 100% that the best approach to all of this is to focus on delivering value to my team as quickly as possible. That can get the snowball rolling, and from there we can explore more and more options.
Thank you for your feedback!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Vue or React are next-project goals. In an existing codebase, introducing a frontend framework like that is a rewrite level effort.
But you can still use npm/yarn/etc! At the end of the day, you're serving a bunch of JavaScript files. A package manager can take care of getting thirdparty dependencies in one place to be served. Bundlers can help you manage your own code. None of this necessitates renovating your entire frontend.
Selling this kind of initiative as a junior member of the team means you need to have an answer for the question "how will this start making our lives better in the very near future?". It's not unlikely that the manual approach has had painful effects: dependency scripts in different places, having to track something down through spaghetti in order to use it, multiple versions of jQuery kicking around, that kind of thing. Look for those. If you have a solution in search of a problem, shelve it for next time.
Hi Dian!
Your feedback definitely aligns with what I was thinking, and what others are saying as well. I will avoid big changes, like a front-end framework, and focus on smaller, easier to digest improvements.
I am going to start looking into how something like NPM could improve some of the problems we face today. I agree 100% that the best approach to all of this is to focus on delivering value to my team as quickly as possible. That can get the snowball rolling, and from there we can explore more and more options.
Thank you for your feedback!