Decoding The Java Technical Interview Process
Have you ever gone through a Java technical interview only to realize how horribly broken the process is? Do we really need to know the Big-O runtime of our code on a day-to-day basis, or is there a more practical way we can test this knowledge?