The Alphabet: Java's Secret Performance Bottleneck

Content Processes Performance App history Startup Users Details Services How to see if a Java program is running 9 Name CPU 66 Memory 0 Disk Java(TM) Platform SE binary 2.7 387.3 MB 0 MBs m Discord (32 bit) (3) 0.6 122.1 MB 0 MBs CE Desktop Window Manager 0.8 99.4 MB 0 MBs Step 1 - Open task manager. Step 2 - Click Memory so the arrow is down Step 3 - Look at the top Ne 0 0.1 0

Content A programmer What people think I do What my parents think I do What I think I do What I really do 0491 Google How to use dates in Javascript Calen CAM ProgrammerHumor.to

Content Dad: Why are your eyes red son? Son: I smoke weed Dad: Don't lie, you're crying because you have been coding in JavaScript Codo

Content The recursive centaur: half horse, half recursive centaur

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 1 Am Devloper iamdevloper Roses are red And so are you Violets are blue Asynchronous operations are great 15:53 14 Feb 19 Twitter Web App 1,993 Retweets 6,207 Likes