Some companies like to pose certain programming questions as part of their interview process.<\/p>\n\n\n\n
I’ve run into a variety of these. They’ve been SQL related questions, code writing, and algorithm descriptions. Some were fairly straight forward. Some less so.<\/p>\n\n\n\n
One of the best I heard was a series of “How would you write this code if you had to write it …” with varying restrictions put on things. And the code was pretty simple. Write code to count all the upper and lower case letters in a string of ASCII characters.<\/p>\n\n\n\n
First write the code however you wanted. Loops, if then else, select case.<\/p>\n\n\n\n
Depending on which branching style you used the first time then the follow on was to write it using the other. If you first used a massive if then elseif statement then switch to using a select case. <\/p>\n\n\n\n
And of course take into account that Xojo IS not case sensitive with string comparisons.<\/p>\n\n\n\n
And finally to not use a branching type at all. This requires some out of the box thinking. Literally “count all the upper and lower case ASCII letters without the use of IF, SELECT or any other branching control.” All you have to use is a loop (while\/wend, for\/next whatever you wanted)<\/p>\n\n\n\n
This first two bits are fairly straight forward.<\/p>\n\n\n\n
The third however is still one of my favourite “thinking out of the box” approaches.<\/p>\n\n\n\n
Anyone care to take a guess at how to achieve that one ?<\/p>\n","protected":false},"excerpt":{"rendered":"
Some companies like to pose certain programming questions as part of their interview process. I’ve run into a variety of these. They’ve been SQL related questions, code writing, and algorithm descriptions. Some were fairly straight forward. Some less so. One of the best I heard was a series of “How would you write this code … <\/p>\n