Comments on: 12 Lessons Learned for Getting Better Results from Developers

By: jani hartikainen

jani hartikainen — Tue, 30 Mar 2010 22:04:04 +0000

[...] I would ask is rather why not Doctrine? As far as I know, the Propel project is kinda dead. …Johnny Holland – It's all about interaction Blog Archive …Jani Hartikainen says: December 30th, 2009 at 6:23 pm. As a developer, I can say that you've pretty [...]

By: My daily readings 02/01/2010 « Strange Kite

My daily readings 02/01/2010 « Strange Kite — Mon, 01 Feb 2010 11:32:36 +0000

[...] Johnny Holland – It’s all about interaction » Blog Archive » 12 Lessons Learned for Gettin… [...]

By: Kev

Kev — Mon, 01 Feb 2010 00:52:27 +0000

I have a problem with the phrases “Get into bed with the QA team” and “Get in bed with the business people.” Not every reader will understand the English idiom (taken literally it’s horrible advice!) but even those that do may find it archaic and perhaps offensive. There are better choices.

By: 12 Lessons Learned for Getting Better Results from Developers » Web Design

12 Lessons Learned for Getting Better Results from Developers » Web Design — Sun, 31 Jan 2010 21:01:35 +0000

[...] 12 Lessons Learned for Getting Better Results from Developers [...]

By: Johnny Holland – It’s all about interaction » Blog Archive » 12 Lessons Learned for Getting Better Results from Developers : Popular Links : eConsultant

Sun, 31 Jan 2010 20:16:28 +0000

By: Johnny Holland – It’s all about interaction » Blog Archive » 12 Lessons Learned for Getting Better Results from Developers « Netcrema – creme de la social news via digg + delicious + stumpleupon + reddit

Sun, 31 Jan 2010 18:35:06 +0000

[...] Johnny Holland – It’s all about interaction » Blog Archive » 12 Lessons Learned for Gettin…johnnyholland.org [...]

By: European developer

European developer — Sun, 31 Jan 2010 16:43:09 +0000

Most of your points are good. But I sense a kind of attitude where you only interact with developers regarding the implementation of your design. I think you will get even better results if you talk with them. These are the people who have spent a lot of hours on the application, and will know of ways to improve it. With a developer you get someone who can not only use an application (QA) but also actually know what is possible.

I am someone who likes to dig down in the system and develop (Java), but I also like HTML/Javascript/CSS/PHP. Luckily I can do both in my job, because we are organized around projects and not job titles.

By: Name Wiffheld

Name Wiffheld — Sun, 31 Jan 2010 16:22:33 +0000

How about this advice: Stop sucking everyone’s dick and form your own company. Then do things the right way. Until then, you’re just another whiny, complaining schmuck.

By: Design e Sviluppo: conoscere il conflitto - Alberto Mucignat

Design e Sviluppo: conoscere il conflitto - Alberto Mucignat — Mon, 18 Jan 2010 08:24:06 +0000

[...] leggo da Johnny Holland: 12. Good design is always hard to program I finally realized this after being a developer and then [...]

By: Jonathon Juvenal

Jonathon Juvenal — Tue, 12 Jan 2010 04:53:02 +0000

@Tamim Well said. It does come down to communicating often. Programming is more about numbers and logic, you’re right. But any time you can spend using the materials you are designing for your designs will always be better.

@Richard, sadly it is the case where I live that most of the developers just want to develop. It is a wonderful day when I get to work with the few who think beyond just coding.

@Robi, thanks! Currently I support two dev teams, 5 each.

@Robin, we do use Agile, though it is our own unique flavor of it. The projects are all internal based. Either marketing campaigns or new features for our subscription based website.