Is it solid wood or veneer? Also, anything you would do differently?
2,928 karma · joined November 20, 2008
Is it solid wood or veneer? Also, anything you would do differently?
http://replay.waybackmachine.org/20061108115703/http://infol...
looks like that Google logo was made in MS Word?
antidaily: I'm in Lansing, but would definitely attend an A2-Detroit HN group and have some people I think I could convince to come along. E-mail me.
Pretty crazy that the guy manages to juggle being a founder and a physics professor at the same time.
Oh, and Steve Jobs has already been vindicated by selling billions of dollars of tech.
Please stop complaining that good stories don't fall in your lap for free. Go find them, or build a better way to put important, un-sensationalized stories in front of millions of people while getting effectively compensated for your time.
Here's 10 minutes of checking top news sources:
http://www.washingtonpost.com/world/aftershocks-keep-japanes...
http://www.washingtonpost.com/world/japan-earthquake-and-tsu...
http://www.boston.com/bigpicture/
http://www.seattlepi.com/national/1104ap_as_japan_earthquake...
http://www.usatoday.com/news/world/2011-03-21-japan-earthqua...
http://www.nytimes.com/2011/03/22/science/22predict.html?ref...
http://www.latimes.com/news/nationworld/world/la-fg-japan-ag...
edit to add links
I worked at a newspaper for 5 years, and their editorial system - this would be the software that reporters write their stories in, editors edit the stories in and proof readers and copy editors lay out pages in, not to mention ad placement, classified pagination and much more - was pushing 10 years old when I started. It wasn't integrated with the website content management system. It was slow, outdated and very annoying.
But it worked, everyone new how to use it, and we knew that we would be able to publish multiple publications every day, 365 days a year. The fact that the system wasn't fully integrated with the CMS meant it was difficult to add links to stories, usually requiring going into the CMS and hand-coding links, after waiting for the publishing scripts to grab the story and post it, a process which could take up to 30 minutes, depending. Typically an online editor or copy editor, far removed from the research and work the reporter had done, would manage this for the entire website, since it makes more sense for the reporter to be out on the street doing actual reporting.
So the 'simple' task of adding a link isn't as simple as it seems when placed in the context of a fast moving newsroom. Typically the battle isn't "why isn't there a link to that source document?" but rather "what do you mean you can't get anybody to speak on the record" or "we need a story for the 1A centerpiece now."
And then the next day the same battles start all over again, the process repeats and another newspaper is printed. It's difficult to change the process because the process is so critical to meeting print deadlines to be able to deliver papers on time.
To add to this, newsrooms are getting cut down at the same time they have to do more. My newsroom once had ~60 people at a time when all they did was print the paper. When I left, it was about half that size and we were posting regular online updates, tweeting, linking to stories from facebook, monitoring comments online, posting photo galleries, shooting video and creating interactive flash presentations on top of it all.
So, yea, if the reporter has time, he reads the report. If it's a story about calf length, it's more likely he'll skim it to be able to bang out a space-filling (or traffic driving) story. And since it's a light human interest story, and not something that's likely to get the paper sued, it gets a quick once-over proofread, then posted to the internet ASAP, then printed, and everyone is on to the next big story to feed daily monster that is daily publishing.
I still think some of these organizations will get there. The New York Times is leading the pack, but the slower publishers will take awhile to replace their antiquated systems and change the daily process that has been refined and perfected since the dawn of the printing press. Of the ones that don't, new organizations that can manage the digital realm will replace them.
I think the bit about superiority may be true: it is a way to demonstrate superiority, but I don't believe that immediately indicates low confidence.
I noticed your account is fairly new, if you haven't seen the guidelines for HN yet, I suggest checking them out here: http://ycombinator.com/newsguidelines.html
Welcome to HN!
Expecting every reader of this post to know who Marco is, who he consults for and which of his previous posts references his employment situation is a bit much.
Also, your self-aggrandizing condescension is not appreciated here.
And yes, alignment is a big deal, especially in any kind of information design. Look at magazines, newspapers, good newsletters, business cards, etc. Alignment is all over the place, and most are designed on a fairly strict grid, i.e. many newspapers use a 6 or 12 column grid.
The big concepts I want developers understand are: Alignment, repetition, contrast and proximity. If you understand those, you will be a better visual designer.
http://www.amazon.com/Non-Designers-Design-Book-Typographic-...
It's a quick, easy read and the concepts can really apply to any kind of visual design. Any of her other titles are also excellent.
Many sites are heralded as an example of 'no design necessary' because they lack the eye candy. However, the minimalism of these sites, the layout of results by date (as opposed to alphabetically or something else) the categories they are arranged by, all are part of the design of these sites. Was a designer involved in this? Hard to say, probably not, but were these decisions made intentionally by someone considering alternative choices? absolutely.
I'm not saying designers are the only people who can design. Just that designers are trained and have experience making decisions like the ones I mentioned above. We can - and do - provide value to software.
1. Communication. Developers use a completely different language than designers. If I come in talking about alignment, developers are thinking 'right left or center justified?' When developers start talking about recursion, I go to sleep.
2. Attitude. Often developers seem to think of designers as 'artsy' types, and design as 'nice-to-have,' which is to imply not necessary.
3. Attitude. Designers often get emotionally attached to their work and get discouraged or give up when someone disagrees, has a different idea or wants to go another direction.
4. I can do it myself. A LOT of developers - particularly less experienced ones - think design is something they can, and are, successfully doing themselves. After all, it's just pixels on a screen, who needs photoshop, right?
5. Small changes. Developers often make small changes to designs. 5px extra padding here, no margin there. Blue is blue, right? We'll just use that 10x10 icon the designer did for that page for this 25x25 icon we need on this page. This drives designers insane.
6. Eyecandy. This goes to a lack of understanding of the design profession; many think design is just slick icons and pretty colors. Developers who have worked with talented designers know that designers can improve entire systems, helping streamline work flows and adapt the system to actual users.
7. Bad designers. Oh yea, there's -a few- of us out there that just picked up GIMP yesterday and think a 600 x 600px favicon should be fine. Even designers capable of really good work may not understand why a 2400x1600 image cannot be used thumbnail-size on the page. This is sad, but I've seen it.
8. Lack of trust. Developers may have worked with bad designers in the past. Most likely they have, actually. They'll likely limit the designers interaction to making icons and css rather than involving them in the system design and planning. Designers may not give as much as they could because they don't trust the developers to value their input or even understand and execute their contributions well.
Of course, that's not to say all projects are this way, and in fact, when I've been involved in projects from early-on, this is very much not the case.
However, I've run into the above issues in my professional career more than once, working face-to-face with people. Trying to make the relationship work online, in projects as distributed as OSS projects are, that's very difficult.
But I think it can be done. For distributed design to work, designers need to be brought on board from the beginning, in the planning phases. The initial designer or designers would have to be responsible for creating a clear vision, clear guidelines, and a well-documented style for future contributors to follow. All contributions would have to adhere to those guidelines, and developers would have to be as adept at spotting violations as designers.
Part of the problem here is also making designers aware of projects to work on. Designers generally join different message boards (if they join message boards at all), read different blogs and generally don't run in the same circles as developers, possibly with HN being one of the exceptions. I'm not sure how to change that...
Although I will say I do remember kids taking notes in pencil in the margins.
Also - two textbooks? seriously? I can't imagine any school springing for that added expense, or even parents for that matter.
http://seattletimes.nwsource.com/html/businesstechnology/201...
http://www.fastcompany.com/1727292/apple-ipad-officially-pas...
If you haven't, read Lee Iacoca's autobiography: http://www.amazon.com/Iacocca-Autobiography-Lee/dp/055325147...
He wrote it in 1984, but everything he says applies to the 2008/2009 collapse of the auto industry. For that matter, go back a little further and read John DeLorean's On a Clear Day You Can See General Motors. It's pretty amazing how long these poorly run companies managed to trip along, and these books make it pretty clear it's not just the unions to blame.