Comments on: Crummy Freelancers, Coding Guidelines and Actionscript Libraries http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/ A nerd blog about nerdy things by ... nerdy guys? Tue, 20 Jul 2010 20:39:29 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Actionscript coding standards and conventions | Ciprian Caba http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/comment-page-1/#comment-4453 Actionscript coding standards and conventions | Ciprian Caba Sat, 11 Jul 2009 13:29:26 +0000 http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/#comment-4453 [...] The coding standards are also mentioned in the Adobe Edge. Some documents I found on Actionscript coding standards can be found here, here and here(AS2.0). [...] [...] The coding standards are also mentioned in the Adobe Edge. Some documents I found on Actionscript coding standards can be found here, here and here(AS2.0). [...]

]]> By: Mike http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/comment-page-1/#comment-2932 Mike Wed, 29 Aug 2007 04:37:46 +0000 http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/#comment-2932 The larger the team, not only the harder it gets to get everyone on the same page (in style, quality, documentation, etc), but in the Flash world (and I suspect other languages suffer the same narcissistic fate) everyone thinks they're king. Documentation is forgotten on all, except only on the few who stayed awake long enough in some CSE class. Yet how many of the masses utterly depend on the livedocs / API reference? Scores I would assume. Like many sentiments already expressed be diligent, and for the Flex / AS3 world as well as AS2 (see as2doc) with some outside help, use the consistency of JavaDoc style comments, it helps with not only maintaining source, but the continual update to the documentation as well. Where I was last at, I was the only engineer (amongst designers, designer turned developer) and I even took it a step further to create pseudo UML diagrams in visio to convey complex components and frameworks. The larger the team, not only the harder it gets to get everyone on the same page (in style, quality, documentation, etc), but in the Flash world (and I suspect other languages suffer the same narcissistic fate) everyone thinks they’re king.

Documentation is forgotten on all, except only on the few who stayed awake long enough in some CSE class. Yet how many of the masses utterly depend on the livedocs / API reference? Scores I would assume.

Like many sentiments already expressed be diligent, and for the Flex / AS3 world as well as AS2 (see as2doc) with some outside help, use the consistency of JavaDoc style comments, it helps with not only maintaining source, but the continual update to the documentation as well. Where I was last at, I was the only engineer (amongst designers, designer turned developer) and I even took it a step further to create pseudo UML diagrams in visio to convey complex components and frameworks.

]]> By: Simon H http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/comment-page-1/#comment-51 Simon H Thu, 08 Mar 2007 17:06:42 +0000 http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/#comment-51 These guidelines are good. Last time I checked Macromedia/Adobe hadn't updated their guidelines, which still refer to AS1 style syntax(correct me if i'm wrong). I think it's a shift in mindset that's required really, similar to switching from a table based layout approach to css approach. AS1 gave/gives you a lot of freedom to be quite random with code layout, whereas AS2/3, if used correctly, guides you into thinking a different way about how you structure your whole app/game/site as well as code. Flash has always been good at allowing you to get ideas out quickly. AS1 was great for that, putting code in movieclips was great for that. It's difficult, but I wouldn't be too hard on those people who haven't made the switch, some don't need to or even want to. AS2 is, so far, the best thing that's happend to Flash, hopefully those people still using older methods will see the light soon. As for untidy libraries, I can't stand them! They are really my pet hate. Nice to see someone attempting to standardise them (If that's even possible). Good luck with it. These guidelines are good. Last time I checked Macromedia/Adobe hadn’t updated their guidelines, which still refer to AS1 style syntax(correct me if i’m wrong).

I think it’s a shift in mindset that’s required really, similar to switching from a table based layout approach to css approach. AS1 gave/gives you a lot of freedom to be quite random with code layout, whereas AS2/3, if used correctly, guides you into thinking a different way about how you structure your whole app/game/site as well as code.

Flash has always been good at allowing you to get ideas out quickly. AS1 was great for that, putting code in movieclips was great for that.

It’s difficult, but I wouldn’t be too hard on those people who haven’t made the switch, some don’t need to or even want to.

AS2 is, so far, the best thing that’s happend to Flash, hopefully those people still using older methods will see the light soon.

As for untidy libraries, I can’t stand them! They are really my pet hate. Nice to see someone attempting to standardise them (If that’s even possible). Good luck with it.

]]> By: Chris Jenkins http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/comment-page-1/#comment-50 Chris Jenkins Thu, 08 Mar 2007 16:51:51 +0000 http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/#comment-50 You are doing exactly the right thing, I did this some years ago and have never looked back. The really difficult part is keeping everyone on a par with their approach, libraries and guidelines will only get you so far, but you really need to develop or adopt a standardized approach to the whole development process. Flex makes this easier as it is based on a pretty standard OOP methodology which has been around for decades. Id say you can never be too strict, police it like all hell, your company will benefit as it saves time in development costs, your developers will also benefit as they get to go home on time, and having a common approach really helps foster a good community at work, which is important. You are doing exactly the right thing, I did this some years ago and have never looked back. The really difficult part is keeping everyone on a par with their approach, libraries and guidelines will only get you so far, but you really need to develop or adopt a standardized approach to the whole development process. Flex makes this easier as it is based on a pretty standard OOP methodology which has been around for decades. Id say you can never be too strict, police it like all hell, your company will benefit as it saves time in development costs, your developers will also benefit as they get to go home on time, and having a common approach really helps foster a good community at work, which is important.

]]> By: Brian Dunphy http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/comment-page-1/#comment-49 Brian Dunphy Thu, 08 Mar 2007 16:14:00 +0000 http://blog.nobien.net/2007/03/08/crummy-freelancers-coding-guidelines-and-actionscript-libraries/#comment-49 I think it's important when hiring on a resource, whether it be full time or on a contract, that the team lead (or whoever might be in the right position) sit down with said resource and go through coding standards and guidelines, technologies used, etc. The last company I was involved with (first as a freelancer, then as a full time employee) did this quite informally, but it was a great way to get a feel for how they wanted things to be done. Different backgrounds lead to different techniques in programming. It sounds like your resource was a designer turned developer, and maybe some old habits carried over. I think it’s important when hiring on a resource, whether it be full time or on a contract, that the team lead (or whoever might be in the right position) sit down with said resource and go through coding standards and guidelines, technologies used, etc. The last company I was involved with (first as a freelancer, then as a full time employee) did this quite informally, but it was a great way to get a feel for how they wanted things to be done.

Different backgrounds lead to different techniques in programming. It sounds like your resource was a designer turned developer, and maybe some old habits carried over.

]]>