StackOverflow Importer – Import code from Stack Overflow as Python modules

Post by andybak » Fri, Nov 04, 2016, 10:04 AM UTC

Biganon wrote: post #61

guelo wrote: post #39

This might be a joke but everybody does it manually for real. Whenever I copy-paste some tricky function from SO I like to add a code comment with the url pointing to the stackoverflow.com answer. This allows future maintainers to refer back to SO and see if a better answer has surfaced or read comments about any issues.

I never, ever copy paste code, unless it's really long. I always end up rewriting everything myself, so I have the time to think about what's happening.

Post by noescape » Fri, Nov 04, 2016, 10:34 AM UTC

Alupis wrote: post #41

noescape wrote: post #36

Earlier quoted context omitted.

What if, somehow, there was a guarantee that the code can't harm your machine -- would you use it then? This isn't a joke.

It's not just about harming your machine - it can harm your* data, or data passing through your* system! * Where "your" can mean you, your employer, your customer, another company, etc.

Post by denfromufa » Fri, Nov 04, 2016, 11:28 AM UTC

drathier wrote: post #72

denfromufa wrote: post #45

Stackoverflow-driven development (SDD): https://goo.gl/images/xXCZrx

Did I just render that book obsolete?

Post by dustinmoris » Fri, Nov 04, 2016, 1:27 PM UTC

Post by clifanatic » Fri, Nov 04, 2016, 2:16 PM UTC

guelo wrote: post #39

This might be a joke but everybody does it manually for real. Whenever I copy-paste some tricky function from SO I like to add a code comment with the url pointing to the stackoverflow.com answer. This allows future maintainers to refer back to SO and see if a better answer has surfaced or read comments about any issues.