Slashdot Mirror
Only 36 Percent of Indian Engineers Can Write Compilable Code, Says Study (itwire.com)
New submitter troublemaker_23 quotes a report from ITWire: Only 36% of software engineers in India can write compilable code based on measurements by an automated tool that is used across the world, the Indian skills assessment company Aspiring Minds says in a report. The report is based on a sample of 36,800 from more than 500 colleges across India. Aspiring Minds said it used the automated tool Automata which is a 60-minute test taken in a compiler integrated environment and rates candidates on programming ability, programming practices, run-time complexity and test case coverage. It uses advanced artificial intelligence technology to automatically grade programming skills. "We find that out of the two problems given per candidate, only 14% engineers are able to write compilable codes for both and only 22% write compilable code for exactly one problem," the study said. It further found that of the test subjects only 14.67% were employable by an IT services company. When it came to writing fully functional code using the best practices for efficiency and writing, only 2.21% of the engineers studied made the grade.
We need anti-Indian propaganda to balance out the anti-White prejudice ingrained in IT.
I write code in C, PHP, Python, Pascal, VBA, Common Lisp, Prolog, Assembler (z80, 6502, x86). I can help people with their code in C#, C++, Java, Smalltalk. From a language user point of view I am a Jack of all trades, master of none. I am very reliant on the compiler/interpreter to highlight me where I made syntactic errors or passed the wrong parameters to a function or API because in that language, the order of the parameter is different than all the other languages.
But you will not get me on the evaluation of the complexity of an algorithm. I have written programs/libraries from a wide range of domains (robotics, biology equipment, domain specific compilers, pay, stock management and ordering, automatic packing of orders, display of industrial process parameters, expert system, machine learning). You can really thrust me in software design and algorithmic, but I am still very reliant on my IDE and the compiler/interpreter to help me about typos and showing me that the construct I use is not the correct one for the language I am currently using (my black sheep is the switch/case/select construct).
Some composer were bad at playing instruments like Mahler, Berlioz, Schoenberg, Ravel. Mahler and Berlioz were just good enough to play their own composition to help them in their creative process but not in public. Schoenberg and Ravel used the help of assistants to play them what they have composed.
Best example I've come across personally:
Their proof-of-concept JSON used floating point numbers for dollar amounts. Floating point numbers for currency is a beginner mistake. I flagged it as an issue straight away and asked them to use cents in integers (which would be appropriate in our use-case). They agreed. Sure enough, the final product used floating point numbers for dollar amounts and started charging people incorrect amounts.
As it turns out, they had a data store that was actually using decimals behind the scenes, so it was just a conversion issue. Dollars to cents - simple calculation, right? Just multiply by 100, right? Nope. They converted to a string, replaced the period with the empty string, then parsed the string as an integer. So the specific price in question went from $4.95 to "4.95" to "495" to 495. Which worked right up until the client reduced their price by five cents. Now it went from $4.90 to "4.9" to "49" to 49. They were now charging 49 cents for a product that was supposed to be almost five dollars.
They literally couldn't understand multiplying by 100 to go from dollars to cents, but every step of the way agreed to do it and either didn't bother or completely fucked it up.