It’s okey to use additional storage/iterate over array multiple times or even to code an O(n 2) algorithm instead of O(nlogn). Big-Oh computation complexity is less important.Never write a single function (like you’d usually do on a whiteboard). Your code better work! Use compiler/interpreter/error messaging from your programming language as a friend and write an error-free program!. Here are a few ground rules for doing well in these interviews: Like we said before, live coding interview questions are fundamentally different from whiteboarding. In this next part of the series, we are going to give a similar demonstration of coding up an interactive Minesweeper game! Read on… In previous posts, we saw how to code a small interactive text-based Tic-Tac-Toe game, especially within time limit of a technical interview, and with unit tests.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |