Comments on: ★ A website is never done http://akibjorklund.com/2009/never-done web generalist Tue, 21 Jun 2011 07:03:10 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: links for 2009-09-14 | Ip's. http://akibjorklund.com/2009/never-done#comment-14300 links for 2009-09-14 | Ip's. Mon, 14 Sep 2009 12:58:04 +0000 http://akibjorklund.com/?p=1817#comment-14300 [...] A website is never done – Aki Björklund A website is never done. It should be constantly analyzed and developed further. Perfection is a forever moving target. Don’t try to nail everything at once. [...] [...] A website is never done – Aki Björklund A website is never done. It should be constantly analyzed and developed further. Perfection is a forever moving target. Don’t try to nail everything at once. [...]

]]> By: Lasse Larvanko http://akibjorklund.com/2009/never-done#comment-14124 Lasse Larvanko Wed, 02 Sep 2009 21:57:27 +0000 http://akibjorklund.com/?p=1817#comment-14124 Aki I think you have found something golden here. The best results come when the developers (or writers, or editors or marketers) are in love with the site or at least develop it as they would own the site. How to make this feasible in business environment is a different story. Aki I think you have found something golden here.

The best results come when the developers (or writers, or editors or marketers) are in love with the site or at least develop it as they would own the site.

How to make this feasible in business environment is a different story.

]]> By: Aki Björklund http://akibjorklund.com/2009/never-done#comment-14117 Aki Björklund Wed, 02 Sep 2009 12:44:49 +0000 http://akibjorklund.com/?p=1817#comment-14117 I think that you can learn new technologies doing constant development also. If the site is based on a framework or CMS that is still evolving, there naturally are new technologies to explore. But I agree and like I said, the smallest sites are not suitable for this. I think that you can learn new technologies doing constant development also. If the site is based on a framework or CMS that is still evolving, there naturally are new technologies to explore. But I agree and like I said, the smallest sites are not suitable for this.

]]> By: Kennu http://akibjorklund.com/2009/never-done#comment-14116 Kennu Wed, 02 Sep 2009 12:33:07 +0000 http://akibjorklund.com/?p=1817#comment-14116 I guess it depends on how big the project is. Maintaining and developing something like Facebook or Google might be interesting for a long time :-) Personally I tend have a constant need for learning new technologies, which means new projects also need to have new requirements and challenges in scalability or other special stuff. I guess it depends on how big the project is. Maintaining and developing something like Facebook or Google might be interesting for a long time :-)

Personally I tend have a constant need for learning new technologies, which means new projects also need to have new requirements and challenges in scalability or other special stuff.

]]> By: Aki Björklund http://akibjorklund.com/2009/never-done#comment-14115 Aki Björklund Wed, 02 Sep 2009 11:56:20 +0000 http://akibjorklund.com/?p=1817#comment-14115 With this model, you don't have to sell that many new projects. New projects should mostly go to new people (if any). I'm not saying that everybody should just maintain old code, but that there is lots of hidden value in that also. With this model, you don’t have to sell that many new projects. New projects should mostly go to new people (if any).

I’m not saying that everybody should just maintain old code, but that there is lots of hidden value in that also.

]]> By: Kennu http://akibjorklund.com/2009/never-done#comment-14114 Kennu Wed, 02 Sep 2009 11:50:37 +0000 http://akibjorklund.com/?p=1817#comment-14114 Biggest problem is that as more and more new projects appear, how do you maintain motivation, focus and time to work on the old ones as well? There is a strong temptation to just throw the old projects into maintenance mode and outsource as much as possible, while focusing on new stuff. Biggest problem is that as more and more new projects appear, how do you maintain motivation, focus and time to work on the old ones as well?

There is a strong temptation to just throw the old projects into maintenance mode and outsource as much as possible, while focusing on new stuff.

]]>