1,172 karma · joined January 21, 2010
John Cleese gave a related talk which I found very interesting: http://www.youtube.com/watch?v=zGt3-fxOvug
It's like complaining that a Lamborghini sucks because the cupholders are hard to reach. I'm sure it would bother some people, but it's not really worth discussing, is it?
Obviously whether foregoing a paper resume is okay depends on the company.
- The logo looks small and isolated from the rest of the page.
- The text in the navigation tabs looks strange, maybe it should be centered?
- The boxes with the slight shading are missing vertical borders, which looks unfinished.
- The circles with the prices are not ordered numerically, which was confusing at first glance. Also the text labels in the image are too small.
- The font size for the description paragraphs is too small; looks like fine print.
- The colors for the Buy/Learn buttons at the top are badly chosen; when I hover over one, it looks like they're both active or inactive since they're the same color. There should be four different colors or they should be identical.
- Not sure why "Required" was abbreviated to "Req'd" when adjacent cells have much more text.
Where can I find more information about this sort of thing?
Now I try to remember specifically what excited me. Not as a bullet point, but as a vision. What was the cool task I imagined accomplishing? What was I thinking of when I felt like I had the right answer? Usually that's enough to get me back in the same state of mind.
But keep talking yourself out of ideas. That's the only way to get rid of bad ones. Just don't forget the good parts. Ideas evolve; let natural selection run its course.
"In retrospect I realize that in almost everything that we worked on together, we were both amateurs. In digital physics, neural networks, even parallel computing, we never really knew what we were doing. But the things that we studied were so new that no one else knew exactly what they were doing either. It was amateurs who made the progress."
I was just saying that you can't apply a technique you don't know.
(2) It seemed obvious, and moreover too trivial a point to merit more than just pointing it out. I apologize if I've caused any offense.
* To clarify, I don't consider "find a new technique" to be a technique, which is why I said to look at the arrows.
There is a typo on the list monad example; "x <- ys" should be "x <- xs".