Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How Woz Gets Things Done

lifehacker.com

Post reply on HN
Print view View original

11–20 of 23 posts

Re: How Woz Gets Things Done

#11

Post by 10ren »

edw519 wrote: post #7
wallflower wrote: post #5

Earlier quoted context omitted.

Jessica Livingston posted her interview of Woz on the Founders at Work website. It's one of my favorite in the book because you really get a sense of the pure hacker/engineering genius Woz is. If you do not already own it, consider buying the book through edw519's link - it's an amazing trove. I bought my copy at Powell's Bookstore in Portland. http://www.foundersatwork.com/steve-wozniak.html

Thanks for the link, wallflower. I forgot about that. (Buy the book anyway. You just don't know which chapter might change your life.) This pretty much sums it up for me: "When you design with very few parts, everything is so clean and orderly you can understand it more deeply in your head, and that causes you to have fewer bugs. You live and sleep with every little detail of the product."

I was going to object to your "finger on the pulse of every detail of their project", because as complexity increases, it eventually becomes overwhelming and too difficult to understand, and you have to construct intermediate representations to handle the complexity - that is, a form of modularity, not for coding it, but just for understanding it.

But then I saw your quote here, about the need to understand it, and the having very few parts makes that possible, by limiting the complexity.

Re: How Woz Gets Things Done

#12

Post by pgebhard »

jasongullickson wrote: post #4
jcromartie wrote: post #2

> When we first started with Apple computers, it was my dream that everyone would learn to program, and that was how they'd use their computer. Aside from the GTD fluff, this is a great article about Woz :)

I still think this is a valid goal, and would love to explore ways to make it happen.

It's all just a degree of abstraction. Someone could say you were "programming" if you were using Automator. Explain more specifically to what level you think people should be programming their computers, because I think it will never happen to the level of writing actual high-level language source code, ala Python. People like looking at and clicking on/touching/interacting with pretty pictures/icons. I guess you might mean something that allows people to piece together actions (functions) to describe some goal they'd like. For example, "Purchase with CREDIT CARD -> from GROCERY STORE -> LAST WEEK'S GROCERY LIST -> deliver to HOME ADDRESS -> after TUESDAY CLASS TIME". Isn't Ubiquity trying to act as something like natural language processing in Firefox?

Re: How Woz Gets Things Done

#13

Post by ice5nake »

jasongullickson wrote: post #4
jcromartie wrote: post #2

> When we first started with Apple computers, it was my dream that everyone would learn to program, and that was how they'd use their computer. Aside from the GTD fluff, this is a great article about Woz :)

I still think this is a valid goal, and would love to explore ways to make it happen.

Someday, we may simply program by having the computer interact directly with our own brain.

Re: How Woz Gets Things Done

#14

Post by blogimus »

You should read his rationale for using Eudora. Here's a snippet:

Any feature in the menu list, any action there, can be added as a button. I changed it so I have a vertical menu bar, so I can have tons and tons of pre-made buttons saved right where I want them up top, and I learn where those place are. You can script actions to the buttons, too, so I can quickly copy messages to my assistants.

Re: How Woz Gets Things Done

#15

Post by edw519 »

10ren wrote: post #11
edw519 wrote: post #7

Earlier quoted context omitted.

Thanks for the link, wallflower. I forgot about that. (Buy the book anyway. You just don't know which chapter might change your life.) This pretty much sums it up for me: "When you design with very few parts, everything is so clean and orderly you can understand it more deeply in your head, and that causes you to have fewer bugs. You live and sleep with every little detail of the product."

I was going to object to your "finger on the pulse of every detail of their project", because as complexity increases, it eventually becomes overwhelming and too difficult to understand, and you have to construct intermediate representations to handle the complexity - that is, a form of modularity, not for coding it, but just for understanding it. But then I saw your quote here, about the need to understand it, and t…

He says it far better than I. Hell, he does everything far better than I, even dancing. (Does he drink beer or play foosball?)

Re: How Woz Gets Things Done

#18

Post by coglethorpe »

What I'm most impressed with isn't Woz's obvious technical birlliance, it's how he's just a decent human being. He presented his ideas to HP before leaving, rather than letting lawyers sort it out if need be. He sold stock to employees, rather than to a single wealthy investor. How he just wanted to be known for designing something great rather than just grab money. Every public appearance I've seen with him has confirmed that.

Re: How Woz Gets Things Done

#19

Post by jasongullickson »

pgebhard wrote: post #12
jasongullickson wrote: post #4

Earlier quoted context omitted.

I still think this is a valid goal, and would love to explore ways to make it happen.

It's all just a degree of abstraction. Someone could say you were "programming" if you were using Automator. Explain more specifically to what level you think people should be programming their computers, because I think it will never happen to the level of writing actual high-level language source code, ala Python. People like looking at and clicking on/touching/interacting with pretty pictures/icons. I guess you mi…

It's all just a degree of abstraction.

I disagree in that when learning to program in BASIC on the Apple II, you are a mere PEEK and POKE away from the hardware; go any lower than that and you are no longer talking about abstraction (as we refer to it) but hard realities of electrical engineering. One floor down and you are the common denominator that defines everything we refer to as a "computer" (in the modern vernacular) and mastering this will provide you with insight which spans across all contemporary systems and many in the perceivable future.

Setting the "ground floor" of programming at anything above this level narrows your scope and greatly increases the potential of your knowledge becoming obsolete.

Someday this will change, and the basis of future systems will not be rooted in the hardware models of today, and it will be great because then we'll all have something new to learn.

Re: How Woz Gets Things Done

#20

Post by jalammar »

If you enjoyed this interview, you're sure to love his book.

iWoz: Computer Geek to Cult Icon: How I Invented the Personal Computer, Co-Founded Apple, and Had Fun Doing It http://www.amazon.com/iWoz-Computer-Invented-Personal-Co-Fou...

It's a really interesting look into Woz's mind and his life. It's especially endearing to engineers. I couldn't put it down till I finished it.

Post reply on HN