Too clever
By DamnGurl - 12/02/2021 02:58 - United States - Kula
By DamnGurl - 12/02/2021 02:58 - United States - Kula
By Anonymous - 20/09/2023 16:00 - United States
By Anonymous - 25/07/2014 02:04 - Canada - Burnaby
By Anonymous - 05/05/2024 12:00 - United States - Seattle
By smellslikeahangover - 29/07/2015 02:55 - United States - San Francisco
By Anonymous - 10/09/2021 14:30 - India - Thane
By Bummed - 12/06/2016 19:44
By The Bosnian - 15/10/2020 02:02 - Sweden - Solna
By Anonymous - 30/06/2020 05:02
By Me - 05/01/2010 07:16 - France
By Anonymous - 16/03/2023 10:30 - India - Vijayawada
Wouldn't your compiler warn you about unused variables during the build phase, and give you a chance to delete them? Having extraneous variables shows you might not have a real grip of the problem.
Yeah what they want is for you to be direct and understand the problem specifically; A self-reflective con that can actually harm you is being overly-divulsive and complicating things when the answer is actually simple.
We don't know the programming language. Could be one without compilers or build phases, or where extra variables are no big deal (are they a big deal in any modern language anyway?) Sounds to me like you dodged a bullet there, OP. Requiring a by-the-book solution in a creative environment with muliple possible approaches to a problem seems like a rigid workplace.
Employers want you to solve problems quickly and efficiently. It's called the KISS method. So next time this happens, remember; Keep It Simple Stupid Or, if you ever watched MythBusters, follow the Hyneman's examples.
Damnit, Dwight!
Keywords
Wouldn't your compiler warn you about unused variables during the build phase, and give you a chance to delete them? Having extraneous variables shows you might not have a real grip of the problem.
Yeah what they want is for you to be direct and understand the problem specifically; A self-reflective con that can actually harm you is being overly-divulsive and complicating things when the answer is actually simple.