Unfortunately, StackOverflow is difficult-to-avoid nowadays… • Hacker News Board

Re: Unfortunately, StackOverflow is difficult-to-avoid nowadays…

#21

Post by vgy7ujm » Wed, Feb 28, 2018, 7:59 AM UTC

smsm42 wrote: post #20

Flimm wrote: post #16

I was curious, and I did a search for "deleted:1 user:me" to see if any of my posts had been deleted, and six had, almost all of them I had deleted myself. For context I have posted around 200 posts on Stack Overflow. Being able to see deleted posts is indeed an eye-opener, and I also wish more people had this ability, but for a different reason. It makes you aware of the amount of very low quality posts that get pos…

Yes, I see candidates for deletion in review queue, and most of it is either garbage or "I have this complex problem, please solve it for me after I give you the most vague description of it". Like the one I just saw recently where somebody has a huge pile of legacy Perl code and has trouble figuring it out (and that's all, no specific Perl question). I can feel their pain, but what can be done here except giving the…

What about hiring an actual Perl programmer?

Re: Unfortunately, StackOverflow is difficult-to-avoid nowadays…

#22

Post by megaman22 » Wed, Feb 28, 2018, 8:05 AM UTC

commandlinefan wrote: post #3

I've lost count of how many times I've googled a question, had the first hit be SO, and the top answer to the question be "Have you ever heard of Google, n00b"? (Thread locked).

For me, it's alway Jon Skeet or Stephen Cleary with a well-written, correct answer that highlights some gotcha that is incredibly non-obvious in the official documentation. Where these guys find the time, I don't know...

Unless it's something to do with Skype or Lync. Then it's abandon all hope, ye who enter here.

Re: Unfortunately, StackOverflow is difficult-to-avoid nowadays…

#23

Post by smsm42 » Wed, Feb 28, 2018, 11:05 PM UTC

vgy7ujm wrote: post #21

smsm42 wrote: post #20

Earlier quoted context omitted.

Yes, I see candidates for deletion in review queue, and most of it is either garbage or "I have this complex problem, please solve it for me after I give you the most vague description of it". Like the one I just saw recently where somebody has a huge pile of legacy Perl code and has trouble figuring it out (and that's all, no specific Perl question). I can feel their pain, but what can be done here except giving the…

What about hiring an actual Perl programmer?

I've been a Perl programmer once, and I assure you given a pile of legacy Perl code, written in a good old style with good old "everything accesses everything", no comments and clever use of tricky Perl constructs, most people would be inclined to yell for help. It's not specifically Perl's fault, but a constellation of Perl being at the top of its popularity when thinking about who will support it 20 years later didn't exactly enter the mindset of most programmers.