Showing posts from February, 2015

Process-Driven Life vs. Outcome-Driven Life

When you are obsessed with outcomes, as many young, ambitious people tend to be, you tend to live an outcome-driven life. "I will be happy once I get that job". "I will be happy once I get that salary". "I will be happy once I pass that milestone and have some amazing accomplishment under my belt".

I used to be one of those people. I thought I didn't deserve to be happy until I became the next Steve Jobs, Bill Hicks, Mark Zuckerberg. ... My sense of "happiness", and my future, for a very long time, depended on my job title, my resume, my accomplishments, things I could show off to other people.

Then I recently read about a different approach to life: a "Process-Driven" mindset from a book called "The Confidence Gap". It's actually a pretty common concept across eastern philosophy.

A process-driven mind means that you enjoy each day, each hour, each minute as it comes, and derive maximum enjoyment from every little thing …

When you are starting out and trying to learn something new

Just like anything else, I think good planning and "pre-execution" research pays dividends when it comes to you picking up a new skill.

For example, when I started out teaching myself web dev last year, I got seriously involved with multiple chapters of Adobe Dreamweaver tutorials. Must have been at least 30-40 hours I spent on those video tutorials.

Now, I hardly use Dreamweaver because it's clunky and I find it easier to work directly with Sublime text editor. I could have avoided that altogether if 1) some mentor were there to direct me toward another direction or 2) if I had done more research and inquired around the community to really pinpoint my direction and outline my own curriculum before plunging deep into a series of video tutorials.

I think it's easy to fall into these pitfalls when you are a beginner because you hardly know anything, and all you know are keywords like "Dreamweaver" or "XML" or whatever, and you just wanna learn anything…

Finding yourself

I quit my last job in sales in June of 2014, 7 months ago. If you've read my posts from then, you could tell that I was a typical product of the job market recession back in 2010, 2011. Another underemployed college kid, confused and frustrated.

I wanted to change. I wanted to learn something new. So I started learning how to code.
It's really unbelievable to think that now I am officially a full-time iOS Developer.
I never felt so personally how valuable it is to learn and pick up a new skill. Knowledge. Human capital. It's literally transformed my life.

It's been a rocky road since then: quitting my job, teaching myself web development for 3 months at home, discovering an iOS bootcamp in NYC and then studying for another 3 months - followed by an intense month of job searching and interviewing.

To be completely honest, and with no intention to brag about myself, it was a really daunting process with many difficult choices along the way. For example, early in this process,…

Thoughts on job-searching after a bootcamp experience

Most coding bootcamps out there advertise a 3-months program. Study for 3 months and you will get a nice job. In reality, it's a lot more complicated than that.

Sure, you can accomplish a lot in 3 months, and most of my learning came from those intense 3 months in the beginning - late nights studying OOP concepts, doing group assignments, hackathons and so on. But generating job leads, interviewing and waiting for an offer is more like to net you at least 2-3 months after your bootcamp curriculum. Sometimes, I've seen people graduate the 3 months program, and stay at the school for almost 1 year before finalizing a full-time offer. 
It's understandable. Job-searching is one of the most stressful things that people go through, and just because you learned how to code, doesn't mean someone is going to hand you an offer on a silver platter.  So be ready for that. Don't be so naive as to think "Hey, I can code now. I built some cool things. Now give me a six-figure …

Compilation of possible iOS technical interview questions

Sources include raywenderlich, stackoverflow and some were directly asked during my own interviews.

I used to think that sharing interviewing tips for others on the internet could only raise the bar and end up not helping anybody. For example, if everyone learns these questions, wouldn't interviewers eventually adapt and ask harder questions? Or if everyone learns these questions, wouldn't it just make the market more competitive and make it harder for me and my friends to stand out?
But then again, I realized the only reason I was able to learn web development and gain valuable free knowledge all over the web (through places like SO) was because people are willing to give advice and help others for free. So I'm going to try to adopt the mindset of helping others for no reason and paying it forward. 
ARC vs MRC Difference between ARC and Garbage Collection What is the difference between the strong & weak & assign references? Which is the default? How would you declare NS…