11–20 of 72 posts
I've said it before, and I'll say it again, Woz is the catalyst that pushed me into programming, and that is something I'm perpetually thankful for. I should write him a note...
The Woz model - engineering as a fulfillment of curiousity is powerful. It is often hard to make the leap towards understanding what to commercialize...
"The best things I did in my young years leading up to the early Apple computers were done because I had little money and had to think deeply to achieve the impossible."
On a side note, I think this is why more (and arguably better) hackers come out of Eastern Europe/Asia.
Kudos sir.
Reading from inspiring people like Wozniak makes me wonder how to adopt such advice.
I am wondering about that almost every time I review a pull request. How do you deal with bad code, poor comments or over-engineering when you see it? Of course you can be nice, but then code and product quality would end up affected. How do you balance this thing?? The person being reviewed knows it's not personal, but it too often becomes a battle of egos. I would be really interested to find ways to become a better programmer by being nicer without bending over or compromising on professional integrity. Any suggestions?
Is the upside down signature in the original?
"You are recognized by your own skills and good work, and you don‘t have to criticize others for not doing good work. Just worry about your own skills." Reading from inspiring people like Wozniak makes me wonder how to adopt such advice. I am wondering about that almost every time I review a pull request. How do you deal with bad code, poor comments or over-engineering when you see it? Of course you can be nice, but…
This statement makes me sad... but I cannot articulate exactly why.
Edit: I like the essay in general. It's very motivating. It would have been great advice when in highschool.