I could buy this laptop only for that, even if with Linux I'll probably have to wait the next laptop before the touchscreen is of any use. But no, the RAM is capped at 16 GB and I'm using 32 GB on my HP laptop (several projects for several customers, each one with a different language and environment.)
However my 15" laptop has a useless (for me) number pad with the result that I have to shift it half to the right to be able to keep my hands in front of me and not skewed to the left, which would probably do nasty things to all my upper body. This is the norm for all 15" laptops and I wonder if their designers stopped at the cover page of Norman's "The Design of Everyday Things", with the famous teapot for masochists, and deluded themselves into believing that this is the right way to build stuff.
Both focus on more than website design, but they helped me understand how users interact with my user interfaces. I'm sure there are also a ton of great blog posts out there too, but I found these books the most helpful.
This is going to sound cliched, but the best way is to start your own company or project from scratch and apply the concepts you learn from these resources.
Here are some "bestsellers", apart from http://startupclass.samaltman.com and PG's essays are
* Design Sprints by Google Ventures: https://www.youtube.com/results?search_query=design+sprints
* Startup School Office Hours: https://www.youtube.com/results?search_query=startup+school+...
* Interface Design for Startups https://courses.platzi.com/classes/interface-design-startups...
* The Design of Everyday Things: http://www.amazon.com/Design-Everyday-Things-Donald-Norman/d...
* Don't make me Think: http://www.amazon.in/Dont-Make-Me-Think-Usability/dp/0321344...
* Objectified: http://www.imdb.com/title/tt1241325/
* Either Rework or Getting Real by 37 Signals
1. The Lean Startup: http://theleanstartup.com/book
2. Lean Analytics: http://leananalyticsbook.com/
3. Business Model Generation: http://www.businessmodelgeneration.com/
* How to Win Friends and Influence People
* The Hard Thing about Hard Things: http://www.amazon.com/The-Hard-Thing-About-Things/dp/0062273...
* The Startup of You: http://www.thestartupofyou.com/
* Build an audience before you launch the product - like 37Signals, Jeff Atwood and Joel Spolsky, Hubspot
* Traction Book: http://tractionbook.com/
* Be Creative - Each startup is different. There's no silver bullet
The sales course by Steli Efti: http://close.io/free-sales-course/
Dave McClure: https://www.youtube.com/results?search_query=dave+mcclure+st...
Founder Interviews, stories:
* PandoMonthly: https://www.youtube.com/results?search_query=pandomonthly
* Stanford ECorner: ecorner.stanford.edu
Consistency is an important tool. In the absence of obvious visual affordances, it's even more important.
* Be obvious
* Avoid extraneous "ornaments" in the interaction
* Understand what your user needs
Of course those three bullet points do not make the book (either of them, I assume) justice, but you might want to read Donald A. Norman's book first. Another book you might be interested in is Don't Make me Think, which is specifically related to software UI design.
I agree with the point that using smartphones for everything is a step back. Having touchscreens in cars is also a step back. We went from having controls that could manipulated without taking the eyes on the road to fancy futuristic UIs that require either for you to be parked, to have a companion or do something potentially dangerous.</rant>
> modern web design has much more in common with product and industrial design than it has with print or graphic design.
His examples of industrial design flaws that look snazzy are bang on, and replicate problems often found in web designs. You gotta USE a thing to know if it's designed well. The Design of Every Day Things should really be required reading for designers charged with designing for the web.
One of the best ways of knowing whether your design is effective is to watch people use it. The assumptions you made about how your audience will use your design will likely be blown away, and watching them try to accomplish the site's goal will lead you towards designs that help them do that more effectively.
Designed for Use: Create Usable Interfaces for Applications and the Web by Lukas Mathis [http://www.amazon.com/Designed-Use-Create-Interfaces-Applica...]
Don’t Make Me Thing by Steve Krug would have been my third.
I don’t believe any of these emphasize minimalism, and I’m not sure what help you’re looking for in that regard?
Being modularised allows the basic user experience to be kept very simple. It does not need to grow into something like an IDE. Hell, according to Packages  even tools like find-and-replace have been modularised so I do not think it follows that Github would carelessly decide to create a big ball of mud!
And additionally this tool has removed barriers that previously existed before.
Since it was created by Github they will be able to expose APIs to create features which are currently not possible.
Likewise the UI being implemented with WebKit means that the user interface can tightly represent what a user is used to seeing at different stages of their development process.
You might have read "The Design of Everyday Things"  before. There are certain elements which you need to control to create a good user experience: (1) discoverability, (2) feedback, (3) the conceptual model, (4) affordances, (5) signifiers, and (6) mappings. Without ease in changing the UI, and the possibility that Github will have self-interest in exposing extra APIs, it would be a lot more difficult to control for each of these.
It's just an opportunity to try new ideas. I'm not suggesting that this would be preferable to everybody.
It was not written with software in mind, but the core respect for the user translates enormously well. If you can't tell whether you should push or pull a door to open it, it's the fault of the door designer, not the door opener. This translates very deeply into interface (user or technical) design.
A resume, when design:
1. Use both knowledge in the world and in the head.
2. Simplify the structure of tasks.
3. Make things visible.
4. Get the mappings right.
5. Exploit the powers of constraints-Natural & Artificial.
6. Design for Error.
7. When all else fails, standardize.
There's a lot of books in the matter of UI but they can fall either in the philosophy side or either the personal taste of the writer.
Also, the Dont Make Me Think book should've really been a two-pager pamphlet, it is really thin on a material. While the center idea is fundamental, it is very easy to explain and to understand.
If we are talking about 10000 ft perspective of the design and its fundamentals, I would raise you The Design of Everyday Things. This is a very good beginners book and it's also an interesting read for those who already know a thing or two.
- It's cliche, but read "The Design of Everyday Things" by Donald Norman . It gives you a good sense of design's place in the greater world. The best design principles are as at home in a product development firm as they are in the software world.
- I own "Design for Hackers" by David Kadavy and I think it's pretty good. The content may or may not be "obvious" depending on your skill level, but he phrases things in a way that is understandable and reassuring to the engineering set. 
- There's a guy on HN (Jarrod Drysdale) who produced an eBook called "Bootstrapping Design". I haven't pulled the trigger on a purchase yet, but I need to. I've read his sample chapter and am subscribed to his newsletter and I think he's an excellent coach. 
- I keep a bookmark folder called "design inspiration" and when I find really cool sites or apps I save them here. You might also want to keep a clipping diary or something where you can keep notes for yourself about what you like and don't like about certain things.
- There's nothing wrong with imitation, within reason. EVERYONE stands on the shoulders of giants and the guy who designed that awesome site or app probably started by shamelessly copying existing stuff. In fact, I recommend that you spend some time trying to EXACTLY copy things you like. You'll start to get a feel for how to accomplish certain affects and, in general, you'll get design a little more "in the fingers".
- Have a project. Have a project. HAVE A PROJECT. It's very difficult to just "learn design", just as it's very difficult to just "learn programming". Unless you're just a natural autodidact, you can read all the tutorials and books and whatever but, when it comes time to do something on your own, you'll just be sitting there staring at a blinking cursor (or an empty Photoshop document) unless you have some place to start.
I hope this all helps, and don't be afraid to share stuff on HN with us. There are plenty of folks who would love to give you positive criticism and feedback.
Obviously it doesn't only deal with UI design but I really recommend it if you're looking for a place to jump off from.
Be warned, once you read it you'll find yourself becoming extraordinarily annoyed by certain types of doors.
1) reinvent the wheel over and over, each time with a new interface, shinier and more limited than the one before it
2) cater more to our hypothetical grandmas instead of our children ... which ironically are able to write HTML in Notepad just fine, if taught how to do that
Users don't like our convoluted, hard-to-use
systems and have abandoned them for products
that are easier to use
People all over Europe have learned to drive cars with manual transmissions - because after the initial pain, the vegetative nervous system kicks in and the wheel, the pedals, the gear switch, all of them become a natural extension, of which you don't think about anymore, just like breathing. And if automatic transmissions are great too, that's because they stay out of your way.
The UI of modern software is nothing like that. Nothing is logical anymore, nothing is designed anymore to be an extension of you. Normal users have to think about their every action, they have to visually search for clues in the UI for every stupid thing they do, they have to rote learn the paths they have to take for the software to take them from some point A, to some other point B. I saw users that have notes on the actual clicks they have to make for certain common actions. I don't know about you, but to me this is freaking painful to watch ;)
Btw, for some good user-experience guidelines, check out The Design of Everyday Things: http://amzn.to/ryfiuI (the link does contain my affiliate code) ... the one thing I took away from this book is that simplicity is a complex topic.
Why won't people do more work ...
setting up their own blogs
Really, step down from your high horse, it's not like you yourself are not guilty for the current state of our industry. We all are.
It is not sufficient to make you an experienced designer, but it is a serious start towards thinking more critically about what makes a given design good or bad.
For those that are also interested: http://www.amazon.com/Design-Everyday-Things-Donald-Norman/d...
Also, I'd throw in The Design of Everyday Things -- see http://www.amazon.com/Design-Everyday-Things-Donald-Norman/d.... It was written long before anyone ever thought of web usability; instead, it focuses on the usability of things you interact with daily in real life. Let's just say that you'll never look at teapots or door handles the same way again...
The Design of Everyday Things (http://www.amazon.com/Design-Everyday-Things-Donald-Norman/d...)
The Humane Interface (http://www.amazon.com/Humane-Interface-Directions-Designing-...)
Contextual Design (http://www.amazon.com/Contextual-Design-Customer-Centered-In...)
I've dabbled in this field in my job, but I don't have any real training, so I've had to teach myself.
The classic text in this field is _The Design of Everyday Things_, by Donald Norman. Also very useful is _Interaction Design_. The first is a very quick read (it's only about 200 pages, and not very technical), while the second is a textbook intended for use in university courses on HCI.
I've found both very valuable in trying to figure out how users approach things without any formal cognitive science or HCI training.
Also, the article you're thinking of is probably either this book:
Or an article about it. (The push/pull door things is a classic example out of that book.)
It's a really great book, and something I would consider a must-read for serious UI designers/developers. While the book was written in the 80s, and talks about things like ring slide projectors, VisiCalc, the original Macs, the ideas about what constitutes good and bad design are salient to this day.
The Design of Everyday Things
and Design of Everyday Things