Hope I'm not the only see this

Content rprogrammer Posted by uI - "2 hours ago vote If you read documentation you aren't a real programmer Reading documentation is basically just copying someone else code. You can figure out everything you need with simple arithmetic and loops. 2 Comments " Award ( Share Comment as PlasticAd7436 What are your thoughts? Markdown Mode Comment Sort By: Best Y PlasticAd7436 just now rProgrammerHumor 1 Saves samara o ProdrammerHumor.io rprogrammer A community for programmers; discussion of programming and programming news. Join us on Discord - httos:discord.gg TB6HZ74ndm Created Oct 21, 2008 9.1k Members h Online Joined Community options rprogrammer Rules 1. Low-Effort Post

Content I've interviewed a lot of people over the last year (Java), and my favorite test is to throw a Stack Trace at them and ask them to figure out what the problem is. The answer is actually quite clear, however. Half of them don't know it's called a stack trace. Some don't know what they're looking at (BYE!). Several focus on the wrong section of proprietary code. Some ask to "open a debugger". however the answer is right there in plain english if you just read the method names. Many don't realize the line numbers are RIGHT THERE, and then start focusing on the lines ending with "Compiled Code". Then there are the ones who work their way up from the bottom, starting with the application container code, and lose their minds. Some who figure out what is happening don't have a solution to prevent it from happening. No, I'm not sharing the trace; suffice to say it's been reviewed by more than 5 of my peers and they all passed. Like Reply 1h Edited I mean, it isn't hard to eliminate people with a coding question. Do you find it impossible to teach people how to read text stack traces, or is this a skill without which they will be unable to do anything of use, or do you just not want to hire anyone? 1 am serious. 1 can come up with dozens of useful programming skills I can test a candidate on that most perfectly skilled programmers would fail. Start with eliminating people who can't code at all. Then find out what they can do that could be useful. If I have 5 people who can already take a printed out stack crash dump, I probably don't need another, and if I do, a qualified candidate can be taught that skill by someone who knows it in under a week. Then again, maybe you work for Stack Trace Inc, and your entire job is looking at stack traces. If so, by bad. Like Reply 22m

Content I can't believe I get paid to do this! DEVELOPERS WRITING CODE CodeBantery Why am I doing this?? DEVELOPERS WRITING DOCUMENTATION

Content Never has been wait it's not really random Math.random (0) ingflip.com

Content Our team is very Agile Do you plan future work months in advance? It's not a simple answer because Do you have hour-long standups involving 30 people where every ticket spans multiple sprints? Yes, however Thank you.

Content Ah! With my programming skills, I will always have a job! Breaking News: Machine Learning researchers managed to get an Al to write code