Related
Does anyone have any evidence of TDD being used at any big technology companies - e.g. Apple, Microsoft, Facebook?
Perhaps there's someone that's worked in one of these big companies that can shed some light on how TDD is used there.
Plenty of evidence is here, I started a site just about that. WeDoTDD.com, hope you enjoy!
It's not only evidence, it's recent evidence and includes stories behind the teams doing it at those companies. The list will just keep growing so revist it often.
There has always been quite a few companies that TDD, you just didn't know about them. Well now everyone can discover this a little bit easier on our site.
Check out this paper
"Realizing quality improvement through test driven development: results and experiences of four industrial Teams"
http://www.msr-waypoint.net/en-us/groups/ese/nagappan_tdd.pdf
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
As a front-end developer, I would like to develop nice and good usability web applications. However, normally developers are good at coding. So, I would ask how to get started with learning some UI design knowledge? What's your recommended books or courses for a newbie to learn? Basically for graphic design, fonts and colors etc etc.
As a UI/UX developer myself, graphic design techniques are questions related to Photoshop, Illustrator, color theory, typography, etc. Usability is related to UI/UX, coding and web architecture. Graphic design and web usability are two very distinctive fields.
What is User Experience Design? - Wiki article on UX
User Experience is any aspect of a person's interaction with a given
IT system, including the interface, graphics, industrial design,
physical interaction, and the manual.
What is graphic Design? - Wiki article on Graphic Design
"Graphic design is the art of communication, stylizing, and
problem-solving through the use of type and image."
Resources #Nathan provided are great, I would also add this to your reading arsenal, education and inspiration:
Open University classes
University of Washington - Visualization
MIT - Drawings & Numbers
USQ - Multimedia
Berkeley - Computer Graphics
Sites & Inspirations
OnePageLove
Responsive.ly
A List Apart
Awwwards
Css Tricks
Tuts plus
Can I use
As with any other skill set, to way to get better is practice, practice, practice. I would just keep building projects as case studies and learn the skill sets as you venture through different types of web applications.
Best of luck on this journey.
Books are good, but to stay upfront and get aware of what is happening the latest and what tools and techniques are in, I suggest you to actively participate on webistes like
Smashing Magazine,
Sitepoint &
Web design Ledger
to name a few, but top quality resources. To know more about the books, you can refer to
Apress Books for front end development
for start to ninja resources.
Hope this helps.
Build on the shoulders of those who have gone before. To be a great developer, you have to know your stuff. In the same way, to be a good designer requires understanding of some basic foundational guidelines. Some of it may seem pretty simple and tedious, but understanding the proper principles of typography, color theory, grid systems and so on can help you a lot. A few resources to get you going are:
Universal Principles of Design
The Elements of Typographic Design by Robert Bringhurst
Thinking with Type by Ellen Lupton
Grid Systems: Principles of Organizing Type by Kimberly Elam
The Design of Everyday Things by Donald Norman
Don't Make Me Think: A Common Sense Approach to Web Usability by Steve Krug
Microinteractions: Designing with Details by Dan Saffer
That list should generate it's own follow-on books / websites reading list for you.
Ask questions. Find some designers you really like and ask questions. Try to understand why they made the decisions they did. Most people are pretty willing to talk about their own work. Asking questions helps you to understand why designers use (or don't use) certain design principles in their work.
Actually design (and seek out constructive criticism.) Like anything you do in life, reading and learning can only take you so far. At some point, you have to start practicing. Find a small circle / community of more senior designers who can review your designers and give you some brutal, but constructive criticism. Your stuff will suck at first. Everyone's work does. Designers spend hours upon hours honing their talents and skills. Don't get discouraged by it. Just like anything you can gain mastery in, it takes time. Having people in your life who can give constructive feedback is a huge help.
Have a look at WebAwwards never let me down yet... Great selection and new websites added every day
I'm looking to find any articles/books on usability. I'd like to get a handle on best practices when designing a UI, this can be anything from which user controls are more intuitive to a new user, to how to phrase text that is displayed to the user to avoid confusing dialogs. I mainly do Windows desktop applications, but most usability standards, I assume, would stand true regardless of the platform.
As an example, here's an MSDN article about the Windows User Experience Guidelines:
http://msdn.microsoft.com/en-us/library/aa511258.aspx
Try reading this book: Don't Make Me Think. While it's focused on web usability it is applicable to all facets of UI design.
The Design of Everyday Things by Donald A. Norman is a standard book on general usability considerations that can be applied to just about everything in day-to-day life. It's not specifically about software, but it's worth it to read it.
Universal Principles of Design is a recommended textbook for my university's Engineering Methods of Software Usability course. Myself, and others who have taken this course, have found this book to be more useful than the required textbook. There appears to be an updated version, called Universal Principles of Design, Revised and Updated: 125 Ways to Enhance Usability, Influence Perception, Increase Appeal, Make Better Design Decisions, and Teach through Design, but I can't speak about that one.
Designing for People Who Have Better Things To Do With Their Lives
by Joel Spolsky (one of the guys behind this site)
when designing UI, please do consider accessibility as well. it's mostly relevant for web sites, but could also be applicable for rich client (desktop apps).
so, these links has a lot of info on the subject, though it's not pure usability info.
a good resource on usability and accessibility:
Design Guidelines for Electronic Publications, Multimedia and the Web
you might find this check list useful:
Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0
and also this tool that will check your web site accessibility:
web aim
Designing Interfaces by Jenifer Tidwell is pretty good.
Well, a long-standing favorite specifically for user interface design is Alan Cooper's About Face. It should touch most important topics when designing Windows desktop applications.
Then there are also various UX patterns which are well-presented in Quince (needs Silverlight).
Jef Raskin's The Humane Interface is also rather good, but very radical in his ideas. Still, this book points out many fallacies in modern UI design. If you need to stick to the WIMP world, then following his suggestions might be a little hard as he tends to suggest to overthrow everything we're used to. But well-written and good for provoking thoughts, even if you don't follow all his advice.
As for books/articles on usability in general or on slightly different topics:
Jakob Nielsen's website useit.com. While not particularly fancy-designed it is a trove of thoughts and advice on usability in general.
Steve Krug's Don't Make Me Think. Web usability, but also a very good read.
Donald Norman's The Design of Everyday Things. Usability in general and has many pointers on how to think about usability without going into specific technologies. It's applicable to desktop application usability anyway, though.
Regarding articles, try Boxes and Arrows
Designing Visual Interfaces by Mullet and Sano provides a great foundation for different layout-related issues. Not a book on usability per se but still relevant, I'd say.
As for web resources, try:
useit.com: Jakob Nielsen's Website
Usable Web
A List Apart on usability
For book inspiration, see Suggested Readings in Human-Computer Interaction (HCI), User Interface (UI) Development, & Human Factors (HF) (and all the great answers in this thread).
My favorite usability blog contains very well-constructed, insightful and thoughtful posts, by David Hamill.
You can find his blog at goodusability.co.uk
Enjoy.
I read articles from http://ui-patterns.com/ and http://www.uxbooth.com/. Those have been helpful for me.
I would like to second uxbooth.com - we recently had an article published there which might be what you are looking for - check it out at http://www.uxbooth.com/blog/usability-testing-dont-guess-test/
usefulusability.com
is another good site, they regularly have good articles up there.
Oh, and another article we had published recently:
www.1stwebdesigner.com/development/usability-ux-pitfalls-howto-avoid/
I think this one provides some pretty good examples of issues that frequently pop up, and how to avoid them.
And if you are looking to run a simple usability test, what not check us out at IntuitionHQ.com
Good luck!
I know this is not a technical question, but this is something I believe could be best answered by the technology community. I've been in software development for ~2 years now, but most of the time, it has been a learn as is needed experience. I was recently asked by a friend on how to go about getting a strong foothold on technology so as to be able to easily adapt to new technology that comes up every day.
I'm not sure how to answer his question as my way of approaching this situation has been learn as you need. How would you suggest someone proceed if they were getting into Microsoft technologies today? Where would they start, and how would they proceed? To be able to expand their knowledge to the new advances we see everyday (linq, silverlight, entity framework, mvc framework and the ever expanding list).
Basically I think my question is a mix of both "how to be a better programmer" and how to get to the "next level" in technology (where you are no longer an intermediate programmer, but able to see the whole picture and easily assimilate new technology)
Thanks in advance.
One thing I enjoy is to listen to technology podcasts while I commute, exercise or do household work. You will net become an expert alone by listening to podcasts, but you will get a lot of input. In particular I enjoy .NET Rocks! but Stack Overflow also has a podcast to name a few.
Read, do and try new things. Do that for a few years you'll eventually end up an experienced programmer.
I think this post by the Misfit Geek could help you out a bit. I think it gives some great tips and gives some good advice on how a respected technologist has stayed up on technology.
How did you learn what you know
Hope these help. I also agree that podcast are a great source of info, at least to point you to the best new technologies. I listen to .Net Rocks, Hanselminutes, HerdingCode, and DeepFriedBytes just to name a few. I also follow some good .net releated blogs such as CodeBetter, Devlicio.us, and Los Techies.
Good luck!
I spend at least 1 hour a day just reading blogs, and listening to podcasts. You cant possibly get involved in everything new that comes along, but having knowledge of what's new is just as important as trying new things out.
If you want to specialise in one thing, then that's fine, but always try to include new technologies into your projects, and look for better solutions to things you have done in the past.
You need to follow what the technical community is interested in. Blogs are the best way that I've found to do this. Pick at least 50 that cover a wide range of topics, and you'll know what is coming down the pipe.
Keep involved in podcasts and blogs. Set aside at least 15 minutes a day to ready them or listen to them. Take their ideas, find which ones apply to you or are interested and add it to your personal development plan to learn them.
Here are a few previous posts regarding these:
Podcasts
OR
c# blogs
Interesting project + new technology = motivated learning.
There is no alternative to getting your hands dirty. Take one of the ideas you've had rolling around in your head and implement it using buzzword technologies. Be prepared to realize many hyped technologies are mostly just hype. Hopefully you will find some real gems, change your perceptions of what is possible, and add some tools to your toolbox all while achieving a goal.
Here's the list of Top 200 blogs for software developers. Try to read some of them and subscribe to what you like or find useful.
Blogs are great for spotting trends and finding some advice about the newest technologies, but if you want to learn something in-depth, you need books. Try to read 3 or 4 every year.
Finally, local user groups. Find and meet your fellow developers face-to-face and find out what they're doing and what's on their minds.
Attend meetings of local user groups.
Although I'm a programmer looking to explore social software patterns, I'm also interested in their psychological and sociological origins.
My proposed format is to limit each reply to ONE reading with a short summary of why it's important.
The idea is that we will then be able to see which particular readings are most important. Since community wiki posts don't count towards one's reputation, hopefully there won't be too many complaints.
I've read a few papers and a few books myself, so I'll get the conversation started...
Shirky: Community, Audiences, and Scale
A 2002 essay arguing that communities don't scale, since humans have a finite capacity for connections with other people, and that those connections are what make communities useful. I agree.
designing for the social web
Author Joshua Porter is a web designer so the writing has advice in how to design social web applications; however, there is plenty of psychological and sociological analysis here that leads up to the advice. You may also be interested in this NY Times article on ambient intimacy.
The Delicious Lesson
The Del.icio.us Lesson, from Bokardo, is that personal value precedes network value in social applications. In other words, you shouldn't expect your users to contribute meaningfully to the health of a group function. What you can and should do, is to assume that users will act in their own self-interest, and then try to learn from what they do. That derived information is what's useful to the group.
Anyway, that's what I take from it. There's also a bunch of talk about the merits of tagging in general, but the reason this reading is important is for the lesson outlined above.
The Lessons of Lucasfilm's Habitat
The principle developers of Habitat, a "multi-user online environment" write about their experiences and lessons learned. Habitat was a virtual community that can be thought of as a very early precursor to Second Life. In the paper, the authors declare some guidelines for social software, some of which are widely accepted today. Some of the guidelines, such as the assumption that bandwidth will always be a scarce resource, were prescient. The authors spend a lot of time trying to say, I think, that complexity in social software should come from the users, not the programmers.
In another feat of foresight, the authors warn administrators of social software to try to "work within the system". I've seen a good number of social apps get a lot of negative attention when they censored a user's action for reasons that seemed unjust. Flickr and Digg come immediately to mind. The authors might have recommended that the moderators of flickr and digg attempt to discourage unwanted behavior without pulling the adminstrator card and wiping out user content.
Like the LambdaMOO paper, there's an implicit warning against assuming any sort of higher-mindedness from the users of your software. Assume that online identities will display every baser behavior that offline humans do. The authors remind us that real people are behind those avatars.
There's also an extensive bibliography at the end of this paper, although the listed material is by now quite dated.
Shirky: A Group is Its Own Worst Enemy
In 2003, Clay Shirky (shirky.com) gave a speech at The O'Reilly Emerging Technology Conference about social software, and this article is essentially a transcript. Borrowing from Experiences in Groups by W.R. Bion, he begins by talking about ways groups, online and offline tend to self-destruct.
This is a wide-ranging article in which Shirky explains many of the typical problems in social software design, lists assumptions that designers of such software should make, and outlines solutions to common pitfalls.
Overall, it's a fantastic read. If you're thinking about writing some new social software offering, I suggest you read it periodically to stay on track.