Showing posts from August, 2014

So good they can't ignore you

Read an interesting book today titled So Good They Can't Ignore you today. It was particularly interesting for me, because as you can see from this blog, I incessantly write and think about "following your passion", and this entire book is written to argue the point that "following your passion" is bad advice for a majority of people.

I couldn't help but agree with a lot of his points. I myself think it's stupid to "just follow what you love" as a career. People who love weed can't all be marijuana-traffickers. I love videogames - doesn't mean I should just follow that and make videogames for a living (who doesn't love videogames!?).

His main point is that "since great, autonomous and meaningful work is rare, you have to offer rare and valuable skills in return. You need to be so good at a craft so that employers cannot ignore you, and then you can achieve that high level of autonomy, wealth and lifestyle that everyone craves&qu…

Dynamic Future

We live in an exciting period. The solutions to our problems that were traditionally fixed in stone can now be taken apart, improved, upgraded and renewed with technology. We've made new tools to help us explore unknown territory: powerful PCs, smartphones, tablets, wearable tech. No wonder we see all kinds of industry disruptions in the last several years.

And it's only going to get better. Older people who were comfortable with their old ways are going to be shaken awake, and are not going to like it (kinda like what Uber did to the traditional taxi authorities, making them all mad), because new techies will be taking their market share. But it's the way it has to be.

Tech entrepreneurship will be the leading change catalyst in the upcoming decades, and it has already started everywhere. Marrying a problem with the right solution supported by the right technology. It will not only be the Technologists and Engineers in the action, but the people who can think of great ideas…

어둠안에 등불

어둠안에 등불
Fire in the dark

모든 사람들이 주목받고 싶고 인정받고 싶다.
빛속에서 존경받고 싶다.

하지만 가장 빛나는 불은 이미 밝은 곳으로 가면 쓸모가 없다.
가장 어두운 곳에서 빛나는 불이 가장 밝은 법이다.

Everybody wants to be under the spotlight. Recognized.
Respected in bright places.

But the brightest fire is kinda useless at a place that's already bright.
It is because they burn within darkness that they can shine the most.

In an ideal world - Career Change

There's no better way than Trial and Error to define and clarify what you want from a career, because every wrong attempt discarded is just another step forward. And yet, the current system has put a big stigma on "job-switching". "You shouldn't be a job-hopper", they say. 
But how else will you learn? How else will you experience? Researching and thinking about a thing can only do so much. Granted, I would also be very wary of committing to hire a person who hops around new jobs every 3 months. But in the early in our lives, I think it should be a given. It is a rite of passage. It is honing your decision-making muscles. 
I just don't get it. Why does the current society make it so hard for people to switch their career paths? Why should people be punished for a decision that they made around their teenage years, their early 20s, when they were just boys and girls?
Career change should just be expected and as natural as a breeze. In a society that helps m…

Different direction

Today, I let go of any final interviews I had and made the decision to go to a 3-month full-time training program for iOS and Swift development.

Originally, I wanted to tell you a different story. Self-study for 3 months. Get a great front-end web developer job or full-stack Rails developer job by month 4 or 5. Happy, dandy after that. I was pretty naive. 
I started getting burnt out around beginning of August after 3-4 months, and my studying started slowing down. There was also a limit to studying + job-searching at the same time; my brain couldn't handle all the stress. There were a couple internships I qualified for. There were a couple Junior positions where I was border-line qualified. Overall, they demanded more experience. The process was grueling as usual - applications, waiting, interviews, more waiting, rejections, move on, more waiting, etc.
Out of all the chaos, there were some rays of hope. There was this one combo Tech/Analyst position that I really liked (let's ca…

End of my self-education journey (well, the first one out of many!)

Good news is that job-searching for the past 3 ~ 4 weeks gave me great insight into the tech job-market. Also a better sense of my own experience level, and what kind of things I qualify for in the development world. 
The sad news is that with a self-education process, like the one I describe in my web dev log, there's not too many openings I qualify for. I'm still way too Junior. In the coding world, I heard that front-end development has the lowest barrier to entry, and yet, I can barely enter it after 3 months. Granted, I wasn't expecting six-figure salaries but darn -_- 
It's not that it's completely hopeless. There are some junior developer openings out there for sure. You get called back if the hiring manager likes you + if the company is very willing to train people + you rock the interview. A lot of internship openings, but you still have to rock the interview. All in all, it reminds me of my sales days. You make a ton of cold-calls (applications) and hope it…

Programming and Scripting

Compiled Languages
Java, C, C++

They need to be "compiled" or "translated" into machine-readable code (bits and bytes).
Its human-readable form, the code that you write, is not the one that's being run.
Computers can only run the code after compiling.

Ex) "Javac" --> then you run "java"

Scripting Languages
Ruby, Python, PHP, Perl

Don't need to be compiled. They just an "interpreter" to turn into machine-readable code quickly

They both have their pros and cons such as compiled languages being faster after compilation as interpreters take more time. But then again, if you have a bug with Java code, you need to compile it every-time you want to test it so it adds an extra process.

Light and Shadow

나를 못 알아봐주는 사람들이 있으니까

알아봐주는 사람들이 고맙고

나를 인정하지 않는 사람들이 있으니까

인정해주는 사람들이 고맙고

나를 미워하는 사람들이 있으니까

좋아해주는 사람들이 고맙고

나를 떠나가는 사람들이 있으니까

나랑 같이 있는 사람들이 고맙다.

힘든 날들이 있었으니까

즐거운 날들이 고맙고

고통스러운 날들이 있었으니까

편한 날들이 고맙고

바쁜 날들이 있었으니까

한가한 날들이 고맙다

부재는 임재를 강화시킨다.

행복과 고통은 빛과 그림자처럼 언제나 함께한다.

행복이 없으면 고통이 없고

고통이 없으면 행복이 없다

Because of difficult times,

We learn to appreciate pleasing times,

Because of painful experiences,

We learn to appreciate happy experiences,

Because of busy times,

We learn to appreciate leisure times.

Absence makes presence that much more precious.

Happiness and pain thus move together like light and shadow

Without happiness, there is no pain

Without pain, there is no happiness

Find the angle between minute and hour hand when time is 6:50 am

def hour_angle(h, m=0)
return (h%12) * 30 + (m/2)

def minute_angle(m)
return m * 6

def angle_time_calculate(hour, minute)
result = hour_angle(hour, minute) - minute_angle(minute)
return result.abs

puts angle_time_calculate(6, 50)


Brain Teaser - 7 horses, only 3 can race at a time, no timer, what's the shortest # of runs possible to find the fastest 3 horses?

I saw this interview question somewhere and wanted to solve it.

7 horses, Find top 3 problem: 
Let's name those 7 horses like this.
A1 A2 A3 B1 B2 B3 C1

1st run
A1 > A2 >  A3

For the sake of the problem, let's say the 1st run revealed that A1 is faster than A2, and A2 is faster than A3.

2nd run
B1 > B2 > B3

After 2 runs, that's all we know about B horses.  The thing is, we still don't know the relationship between the A and B horses. We try to find that out with the 3rd run by racing A1, B1 and C1.

3rd run
A1 > B1 > C1

So A1 is #1 horse of everybody. So now we can focus on finding #2 and #3.
At this point, we can eliminate B3 because B3 will never be in the top 3 horses. The only top 3 combinations are as follows:
1) A1 A2 A3
2) A1 A2 B1
3) A1 B1 C1
4) A1 B1 B2
5) A1 B1 A2
And with all of these scenarios, the branch never reaches as far as B3.

So the possible horses, when visualized, look like this shape below
A1 B1 C1
A2 B2

Okay, here's the tricky part
4th run --> …

Week 2 of Jr Developer Job-Searching

Things are looking up. Hearing back from a couple places here and there. Granted, they were just exploratory/introductory interviews over the phone but at least they seem interested in my resume. Getting a little tired of recruiters/screeners who talk for 5 minutes and then hang up after finding out that I'm a "self-taught" learner. I"m like "Well, don't call me then?" Bummer. Need some thick skin to survive this time ... 'senior year job-searching' all over again.

Had some time to study up on Node, Express and the MEAN(MongoDB, Express, Angular, Node) stack. It's definitely not easy, but it's very cool. With my understanding of Rails, it's slightly easier to grasp than when I was learning Rails from level zero back 3 months ago but learning MEAN stack well will take loads of time, not just a few weeks. Made a few simple Node/Express apps that dealt with Twitter/YouTube APIs but for the time being, I'm leaning towards sticking wi…

Tough Job-Searching

It's only been really week 1 of starting a "full-time job-searching" mindset but the stress has been getting to me this week. It's funny because it's only been the first week I've been sending out applications, and there's no way I could expect results in such a short amount of time. I guess I'm just anxious and nervous.

I was hoping for a whole lot of junior developer position openings but it seems that it is not the case. I still need to look hard for the ones where that match my skill-set, and even for those positions, I may be competing with a lot of people. It's not going to be easy IMO.

I guess the job-searching part is what people really need their bootcamps for. For the connections and the networking, so that they can go through the job-searching process together. The studying part was doable by myself, but the job-searching process is as stressful as it has always been.

Finding a mentor should be a priority for me, but it hasn't been tha…