21. May 2011

aDevCamp Prague – slides and links

Box2D Engine: Box2D, Lee Brimelow – GotoAndLearn()

Web: aDevCamp.cz

17. May 2011

Smooth workflow for mobile development

World of mobile devices is quite complex. Increasing number of operating systems and platforms is spliting market and making it harder to implement app that works across different devices.

Thankfully there are some good solutions. Flex development team made a huge step forward and  they prepared tools for whole workflow.

If you’re interested in mobile development take a look at this video from Edge newsletter.

I’ll show part of this workflow also this week in Prague at Android Dev Camp. So feel free to stop by. We can discuss many topics related to mobile and Flex/AIR. 😉

17. May 2011

Quality in Flex/ActionScript development

Sergei Sokolov wrote article about Using automated tools across the lifecycle to develop higher quality Flex applications.

He explained some tools and approaches how to build better Flex based software.

I’d like to add some of my notes to this topic:

1. The key factor for reaching good quality of Flex products is learning. Flex is platform and it is evolving. Therefore it is imperative to learn new approaches to solve some problems.

2. Automation is very important. Flash Builder is bundled with support for Ant. That is not enough. Continuous integration should be implemented via tools like Maven using FlexMojos. Without this point everything is useless, because you’ll end up with mixing different versions of Flex SDK with your framework. Thanks to Jenkins and FlexMojos you reach stability in SW production. We already launched Jenkins CI for open source ActionScript projects – you can find some details at corlan.org.

Here is small example how to use FlexMojos.

3. Teach developers how to use FlexUnit. Companies tend to buy cheaper version of Flash Builder which has no support for FlexUnit. Investing few more bucks could give them very handy tool. See lynda.com or tv.adobe.com for lecture about FlexUnit. There are also other helpful tools like FlexMonkey, etc.

4. Different tools. Flash Builder is great, but real development power comes with combination of Flash Builder with IntelliJ Idea Ultimate. Those two tools together could speed up development and improve code quality. Also test automation has good implementation in IntelliJ Idea.

5. Flex PMD. This could help team which deals with new developers. Often it is hard to guess level of skill of new developer in the team. Using Flex PMD could help with measuring and detecting anomalies in his code style

6. Get rid of Not Invented Here Syndrome. There are many small useful frameworks which could help to improve Flex productivity, like Swiz, RobotLegs. Knowing those frameworks could save hundreds of development hours. So give a space to developers to learn new approaches.

I prefer small frameworks with less singletons inside. Some Flex frameworks are overflowing with singletons. Do not use sw with too much singletons, it will bite you and maintainability of your Flex product will drop to zero. Just a friendly warning at the end 🙂

In my opinion this is the core of producing real good and stable Flex software.

2. May 2011

21.5. 2011 – Prague – androidDevCamp

I was invited to give a talk about development based on Adobe AIR platform for Google Android. 🙂

This is my favorit topic. AIR platform has been here for several years and it is quite mature. It provides solid framework for large range of applications. AIR platform is good for developing small apps or even the big enterprise systems.

Flex/AIR framework is open source. Flash Builder IDE based on Eclipse is very useful tool for developers.

You can find more details about this event at aDevCamp.cz.

It’s great opportunity to meet people from Android community.

20. April 2011

Productivity in software project drops at least to 1/2 after handover

It is quite clear that productivity in software project will fall down “little bit” when you hand over the project to somebody else.

New team does not have all the knowledge of original author and it takes longer time to solve project issues.

The problem is that this loss in productivity is not quantified and project managers relay just on some fuzzy feeling.

I found interesting talk given by Audris Mockus about Digital Software Archeology. He made deep research in the topic of productivity in software development and he defined several useful terms.

Audris formulate very interesting result of his research: Productivity after handover dropped to 1/2. This is quite important to realize. It affects project planning and resource allocation.

 

  • Quick search

  • Links

  • Twitter

    Follow @jurajmichalek on twitter.

  • Comments

  • Tags

  • Topics