2 parts:

1) Questions about memory management. ARC vs MRC, Thread Safety (deadlock, racecondition), Blocks, Weak vs Strong references. I missed keeping strong refs to weak items during the block statement life cycle.

2) Coding question. I quickly realized it was a permutation function and went strait to the recursion.

Sounds pretty good right? Wrong. I completely lost my noodle on part 2. I explained everything I wanted to do which checked out but everytime I went to write something it came out wrong. Perhaps it was interview anxiety. Immediately after the call I was so frustrated that I went ahead and finished the recursive problem myself.

written by jackson | comments(0)

I was looking around for some cool canvas text effects and found this page which is pretty great to find some canvas based text inspiration

written by jackson | comments(0)

I've found debugging to be tricky with Node, until today. Running with the `--inspect` flag is pretty cool, mind you it's "experimental" and "may be disconued at any time" !

Recap: `$ node --inspect yourFile.js`

Then node will give you a CHROME-ONLY url to debug your script. I highly recommed enabling the auto-break feature in the inspector tools. If you're not familiar that, look at pausing on exceptions in chrome.

Also, here's a good tip for reusing the same web debug session without have to copy/paste the inspection url every time

written by jackson | comments(0)
Syndicate content