Re:Old Code Gets Younger Every Year
by hinkley on Monday June 08, 2020 @06:08PM
(#23461353)
npm is not 'maturing'. It is now regressing.
There is no spec, there is no feature list, and so patches keep breaking behavior and then it gets declared as being on purpose.
I am using several flags for CD builds that are not documented on the npm page (or at least were not when I started using them).
If you are thinking of deflecting by talking about how maybe my builds are too complex then you can save your breath, because I don't want to hear it.
Tinker toy apps won't have any maintenance problems, aren't the sort of things you get paid to work on for years, can be replaced instead of mucked with. And quite frankly, bringing up happy path applications just dates you as a young developer with no field experience (or worse, an idiot).
There is no spec, there is no feature list, and so patches keep breaking behavior and then it gets declared as being on purpose.
I am using several flags for CD builds that are not documented on the npm page (or at least were not when I started using them).
If you are thinking of deflecting by talking about how maybe my builds are too complex then you can save your breath, because I don't want to hear it.
Tinker toy apps won't have any maintenance problems, aren't the sort of things you get paid to work on for years, can be replaced instead of mucked with. And quite frankly, bringing up happy path applications just dates you as a young developer with no field experience (or worse, an idiot).