I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.
So below I made a list of leetcode problems that are as close to grokking problems as possible.
This gist is a fork of the gist from this blog post.
Source: http://blog.8thlight.com/uncle-bob/2013/09/23/Test-first.html
| “This is your life. Do what you love, and do it often.” Holstee Manifesto | |
| “Overthinking ruins you. Ruins the situation, twists it around, makes you worry and just makes everything much worse than it actually is.” Unknown | |
| “Don't let the noise of others' opinions drown out your own inner voice. Have the courage to follow your own heart and intuition.” Steve Jobs | |
| “The greatest mistake you can make in life is to be continually fearing you will make one.” Elbert Hubbard | |
| “Don't let someone who gave up on their dreams talk you out of going after yours.” Zig Ziglar | |
| “The secret to happiness is freedom. And the secret to freedom is courage.” Thucydides | |
| “Courage doesn't always roar. Sometimes courage is the quiet voice at the end of the day whispering, 'I will try again tomorrow.'” Mary Anne Radmacher | |
| “Sometimes life hits you in the head with a brick. Don't lose faith.” Steve Jobs | |
| “The journey is the reward.” Steve Jobs | |
| “If you find yourself constantly trying to prove your worth to someone, you have already forgotten yo |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
| import java.io.FileDescriptor; | |
| import java.io.FileOutputStream; | |
| import java.io.IOException; | |
| import java.io.OutputStream; | |
| import java.io.PrintStream; | |
| public class HelloWorld{ | |
| private static HelloWorld instance; | |
| public static void main(String[] args){ | |
| instantiateHelloWorldMainClassAndRun(); |
| import code; code.interact(local=dict(globals(), **locals())) |
git clone https://github.com/rasa/vmware-tools-patches.git
cd vmware-tools-patches
curl -O https://softwareupdate.vmware.com/cds/vmw-desktop/fusion/6.0.5/2209127/packages/com.vmware.fusion.tools.linux.zip.tar
for i in {0..6}; do sudo mkdir -pv /etc/init.d/rc${i}.d; done
sudo pacman -S net-utils
./untar-and-patch-and-compile.sh
The three design patterns (Adapter, Facade and Bridge) all produce the result of a clean public API. The difference between the patterns are usually due to a subtle context shift (and in some cases, a behavioural requirement).
The primary function of an Adapter is to produce a unified interface for a number of underlying and unrelated objects.
You will notice this pattern being utilised in many applications. For example, ActiveRecord (the popular Ruby ORM; object-relational mapping) creates a unified interface as part of its API but the code underneath the interface is able to communicate with many different types of databases. Allowing the consumer of the API to not have to worry about specific database implementation details.
The principle structure of this pattern is:
