Depends on what your intentions are, as a debugger replacement for the simple things, I would not recommend it, but if you must, make a list of actions (step in, view locals, step out, etc.) that you usually do in your debugger of choice, then map these to windbg commands. More interesting things to use it for is crash investigations, memory leaks, kernel debugging, and then data or stack collections acquisition thru windbg scripting.
For day to day debugging, I would strongly advise against using windbg, windbg will try its best to get in your way and slow you down at every step, so unless you need it for some tricky debugging, don't touch it, you won't be very productive. Anyway, my personal advice, take it with a bit of salt