"I'm not gonna create a very complicated administration panel"
This sounds more like feature creep or miscommunication within the team, no?
"I think creating our own Tab/Panel/Popup component was a waste of time"
Sure, if a library already does the job (and it is sufficiently flexible and/or has an active developer team), it's a good starting point. I find, I often end up writing light-weight wrappers on top of most libraries just to remove a lot of the boilerplate. This way, 80% of the library's usage (hopefully) ends up streamlined toward one or two specific approaches, rather than having everyone on the team trying things out and then ending up with a mess of mis-used features and squares squeezed into circular openings. I guess, this approach might apply to teams mostly consisting of Juniors who would appreciate the additional guidance, not necessarily to more experienced dev teams.
"Duplicating code x2 or maybe 3 times is ok. But at the 3rd time..."
"we dedicated 10-20% for tech debt reduction"
Good ideas and sounds like numbers to play around with. I will certainly incorporate that into future planning!
All in all, you are bringing up great stuff! Thanks for the quick forth-and-back.
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.
Thanks for the reply!
This sounds more like feature creep or miscommunication within the team, no?
Sure, if a library already does the job (and it is sufficiently flexible and/or has an active developer team), it's a good starting point. I find, I often end up writing light-weight wrappers on top of most libraries just to remove a lot of the boilerplate. This way, 80% of the library's usage (hopefully) ends up streamlined toward one or two specific approaches, rather than having everyone on the team trying things out and then ending up with a mess of mis-used features and squares squeezed into circular openings. I guess, this approach might apply to teams mostly consisting of Juniors who would appreciate the additional guidance, not necessarily to more experienced dev teams.
Good ideas and sounds like numbers to play around with. I will certainly incorporate that into future planning!
All in all, you are bringing up great stuff! Thanks for the quick forth-and-back.