Participant code,Background,Years exp,NBR trivial,Is using trivial package Good/Bad?
P1,Full time Independent developer,More than 5 Years, 16 - 20,No
P2,Developer working in the industry,More than 5 Years, 0 - 2,Left-pad isn't trival
P3,Developer working in the industry,Between 1 and 3 Years, 0 - 2,No
P4,Full time Independent developer,More than 5 Years, 3 - 6,No
P5,Full time Independent developer,More than 5 Years, 11 - 15,No
P6,Full time Independent developer,More than 5 Years, 7 - 10,No
P7,Developer working in the industry,Between 3 and 5 Years, 21+,No
P8,Developer working in the industry,More than 5 Years, 0 - 2,No
P9,developer at npm,More than 5 Years, 3 - 6,No
P10,Developer working in the industry,Between 1 and 3 Years, 3 - 6,No
P11,Developer working in the industry,Between 3 and 5 Years, 3 - 6,No
P12,Developer working in the industry,More than 5 Years, 21+,No
P13,Developer working in the industry,More than 5 Years, 3 - 6,No
P14,Full time Independent developer,More than 5 Years, 7 - 10,No
P15,Developer working in the industry,More than 5 Years, 7 - 10,"It's a decision that needs to be evaluated on a case by case basis.  If the package provides tests cases for that ""trivial code"" that you yourself might get wrong, then it's probably not a bad thing."
P16,Developer working in the industry,Between 3 and 5 Years, 3 - 6,"As with many other decisions you can make in development, there is no such thing as a ""good"" or a ""bad"" thing but an ""acceptable"" one given the tradeoffs one needs to make when putting something together. In some cases, a dependency for a trivial task is a ""good"" decision because the risks that come from adopting a third-party library are acceptable and the benefits received outweigh any benefits from writing the tasks yourself."
P17,Developer working in the industry,Between 3 and 5 Years, 7 - 10,"It depends on the needs of the project, the time to build it, the size of it, if there is existing guidelines."
P18,Full time Independent developer,Between 3 and 5 Years, 0 - 2,No
P19,Developer working in the industry,Between 1 and 3 Years, 0 - 2,No
P20,Developer working in the industry,More than 5 Years, 0 - 2,meh. It’s not inherently good or bad.
P21,Developer working in the industry,More than 5 Years, 0 - 2,Yes
P22,Developer working in the industry,More than 5 Years, 3 - 6,Yes
P23,Developer working in the industry,More than 5 Years, 0 - 2,Yes
P24,Developer working in the industry,More than 5 Years, 3 - 6,Depends on the situation
P25,Developer working in the industry,More than 5 Years, 3 - 6,depends on the team expertise
P26,Full time Independent developer,More than 5 Years, 3 - 6,No
P27,Developer working in the industry,More than 5 Years, 21+,No
P28,Developer working in the industry,More than 5 Years, 21+,No
P29,"Inventor of npm and CEO of npm, Inc.",More than 5 Years, 3 - 6,No
P30,Developer working in the industry,More than 5 Years, 7 - 10,No
P31,Developer working in the industry,More than 5 Years, 0 - 2,"""Trivial"" means of little importance.  If the code is of little importance, then it doesn't matter where it comes from.  I do sometimes use packages that are small - but would never say they are trivial."
P32,Developer working in the industry,More than 5 Years, 3 - 6,Yes
P33,Developer working in the industry,More than 5 Years, 0 - 2,No
P34,Developer working in the industry,More than 5 Years, 0 - 2,No
P35,Full time Independent developer,More than 5 Years, 0 - 2,No
P36,Developer working in the industry,More than 5 Years, 0 - 2,No
P37,Full time Independent developer,More than 5 Years, 3 - 6,No
P38,Developer working in the industry,Between 3 and 5 Years, 0 - 2,Yes
P39,Developer working in the industry,More than 5 Years, 3 - 6,No
P40,Developer working in the industry,More than 5 Years, 0 - 2,Yes
P41,Developer working in the industry,More than 5 Years, 21+,No
P42,Developer working in the industry,More than 5 Years, 11 - 15,No
P43,Developer working in the industry,Between 1 and 3 Years, 0 - 2,Yes
P44,Developer working in the industry,More than 5 Years, 3 - 6,No
P45,Casual developer,More than 5 Years, 7 - 10,No
P46,Developer working in the industry,More than 5 Years, 3 - 6,No
P47,Full time Independent developer,More than 5 Years, 7 - 10,No
P48,Developer working in the industry,More than 5 Years, 0 - 2,Depends how mission critical the project is
P49,Full time Independent developer,More than 5 Years, 11 - 15,No
P50,Developer working in the industry,More than 5 Years, 3 - 6,No
P51,Student,Between 3 and 5 Years, 3 - 6,It depends on requirement and time
P52,Full time Independent developer,More than 5 Years, 21+,Yes
P53,Developer working in the industry,Between 3 and 5 Years, 0 - 2,Yes
P54,Developer working in the industry,More than 5 Years, 21+,No
P55,Full time Independent developer,More than 5 Years, 3 - 6,No
P56,Developer working in the industry,More than 5 Years, 7 - 10,No
P57,Casual developer,More than 5 Years, 0 - 2,it depends
P58,Developer working in the industry,Between 3 and 5 Years, 0 - 2,No
P59,Developer working in the industry,More than 5 Years, 3 - 6,Yes
P60,Developer working in the industry,More than 5 Years, 0 - 2,No
P61,Developer working in the industry,More than 5 Years, 0 - 2,"The question is oriented. It depends on the package's description. The implementation may be simple, but the solved issue may seem more complex. And sometimes, I don't inspect the package's code. If I did, I may or would think I can solve it myself."
P62,Developer working in the industry,More than 5 Years, 0 - 2,Yes
P63,Developer working in the industry,More than 5 Years, 21+,No
P64,Developer working in the industry,Between 3 and 5 Years, 0 - 2,Yes
P65,Developer working in the industry,More than 5 Years, 7 - 10,No
P66,Developer working in the industry,Between 3 and 5 Years, 0 - 2,Yes
P67,Developer working in the industry,More than 5 Years, 0 - 2,Yes
P68,Developer working in the industry,Between 3 and 5 Years, 3 - 6,No
P69,Developer working in the industry,More than 5 Years, 0 - 2,No
P70,Developer working in the industry,More than 5 Years, 3 - 6,No
P71,Developer working in the industry,Between 1 and 3 Years, 3 - 6,"Depends - the examples given are indeed trivial and if they are only a line or two, carry no advantage over implementing yourself. However, I think the examples I was provided with (vinyl-buffer and vinyl-source-stream) are less so. Furthermore, I was not even aware they were 'trivial' until this survey made me aware of this - they are standard mentions in any Gulp tutorial, and so I just included them without checking the code - advantages as below."
P72,Full time Independent developer,More than 5 Years, 3 - 6,"No, as long as the trivial lib does not have new dependencies of it's own"
P73,Developer working in the industry,More than 5 Years, 0 - 2,Yes
P74,Developer working in the industry,Between 1 and 3 Years, 0 - 2,Yes
P75,Developer working in the industry,Between 3 and 5 Years, 20+,Yes
P76,Developer working in the industry,More than 5 Years, 3 - 6,No
P77,Developer working in the industry,Between 1 and 3 Years, 0  - 2,No
P78,Developer working in the industry,More than 5 Years, 3 - 6,No
P79,Developer working in the industry,More than 5 Years,10+,No
P80,Developer working in the industry,More than 5 Years,0 - 2,It really depends on the situation 
P81,Full time Independent developer,More than 5 Years, 3 - 6,No
P82,Developer working in the industry,More than 5 Years, 3 - ,No
P83,Developer working in the industry,More than 5 Years, 3 - 6,Yes
P84,Developer working in the industry,Between 3 and 5 Years, 3 - 6,No
P85,Developer working in the industry,More than 5 Years, 3 - 6,Yes
P86,Developer working in the industry,More than 5 Years, 0 - 2,Yes
P87,Developer working in the industry,More than 5 Years, 0 - 2,It depends
P88,Developer working in the industry,More than 5 Years, 0 - 2,Yes