News for hackers. Stuff that matters.
Re:Turning Off GitHub Issues (2016) by nperez on Tuesday May 23, 2017 @06:52PM (#14406107)
So you take code you don't understand and don't want to understand, and you use it to power someone else's business? Doesn't sound safe or professional to me. You don't need to understand everything about every dependency, but you should absolutely be willing to dig in a little
Re:Turning Off GitHub Issues (2016) by BugsJustFindMe on Tuesday May 23, 2017 @07:00PM (#14406164)
> So you take code you don't understand and don't want to understand, and you use it to power someone else's business?

This is what we call a strawman. Also, I guarantee that you do exactly what you're glibly dismissing every day of your life.

Re:Turning Off GitHub Issues (2016) by rocky1138 on Tuesday May 23, 2017 @07:58PM (#14406517)
Yeah. I mean, taken to the nth degree, even driving a car is doing that. Surely the parent gets on a bus, drives a car, rides a bicycle, etc.
Re:Turning Off GitHub Issues (2016) by shusson on Tuesday May 23, 2017 @07:01PM (#14406170)
> So you take code you don't understand and don't want to understand, and you use it to power someone else's business? Doesn't sound safe or professional to me

That attitude sounds crippling to being productive. At some point you have to trust code based on usage, brand, peer-reviews etc.

Re:Turning Off GitHub Issues (2016) by makomk on Tuesday May 23, 2017 @07:19PM (#14406303)
Aside from the fact that everyone relies on code that they don't understand, looking at the code probably isn't going to tell you all that much about how it's meant to work, which is rather important when trying to fix a bug.