Posts

Reading06: I, Robot

Ahh, the classic "how do I speedrun retirement" conversation we had a few weeks ago. Startups do  seem like a "get rich quick" scheme...if you do it right. Find a gap, start to fill it, and (hopefully) get bought. While there aren't any rules on what one is  or is not  allowed to pursue, the wealth that comes with developing technology has most definitely polluted the waters with more "robots," leaving fewer True Hackers. "When people care enough about something to do it well, those who do it best tend to be far better than everyone else." I read Outliers  by Malcolm Gladwell for a class in high school and ever since, the 10,000 hour rule has always stuck with me: all of the pros have put at least 10,000 hours into perfecting their craft. The  Beatles played 10000 hours worth of practices/gigs together before they solidified themselves as greats. Bill Gates spent 10,000 hours tinkering with computers to fully understand them. While I don'

Reading05: Lost in Translation

" Consider Cobol." I HAVE NO IDEA WHAT COBOL IS. Maybe this is a me problem, but this language was referenced way too many times for me to draw any meaning from those points. Also, it's been a little weird trying to wrap my head around 2003 Python. I'm assuming it's a much different (younger) language than it is today. "The reason Latin won't get you a job is that no one speaks it. If you write in Latin, no one can understand you. But Lisp is a computer language, and computers speak whatever language you, the programmer, tell them to." I've always wondered what the real  difference between languages was aside from use-case. Why isn't there one language that can do everything  well? I guess that's what Python aims to do, especially with its massive support as an open-source language. As Graham stated, you should always use the most powerful language or, if this doesn't best fit your use-case, find the one with the greatest library supp

Reading04: Back to Business

Reading Graham's essays were honestly such a breath of fresh air. This dude is writing exactly what I'm thinking--I completely resonate with his perception of the hacker and, more importantly, what the hacker sets out to do. "And then at the other extreme you have the hackers, who are trying to write interesting software, and for whom computers are just a medium of expression, as concrete is for architects or paint for painters. It's as if mathematicians, physicists, and architects all had to be in the same department." If anything, these writings make hacking more  desirable. When I was a senior in high school, my teachers would (naturally) ask me what I wanted to study in undergrad. "Computer science." They would laugh, "there's no world in which you sit in a cubicle and write code all day--you talk too much." I took this as a compliment. For context: I was a theater kid. While I've always enjoyed being a creative-type, there was, and

Reading01: My First Hack

When asked during the first lecture what my greatest 'hack' was, I realized that I either a) have a bad memory or b) have never created anything for fun. When reading about twelve-year-olds writing compilers and building ping-pong robots, I realized that it might be too late for me to do anything original in my life. If every reading puts these thoughts in my head, this is going to be a fun class. "There were enough obstacles to learning already--why bother with stupid things like brown-nosing teachers and striving for grades?" The first part of Hackers  makes it very clear exactly what a 'hack' is. If there has been one common theme across these seven chapters, it has been the loss of self that hacking requires. Three distinct qualities are needed to be a "True Hacker:" Motivation to create something new Willingness to give your full self to your hack Selflessness, knowing your hack is not privately owned but instead an open-source contribution to t