Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Ryan Slobojan on May 21, 2008
In this interview from QCon San Francisco 2007, James Ward discusses Rich Internet Applications (RIAs), Flex and AIR, how Flex helps in the development of RIAs, the changes in ActionScript 3, the Tamarin engine, desktop and offline capabilities, Flex Builder, the Flex developer community, LiveCycle Data Services, the AMF protocol, RIA development trends, and the Flex component model.
Watch James Ward discusses Flex and AIR (29 minutes).
From the interview:
Building Flex applications, the core of the Flex tooling is the Flex SDK. That's a free SDK, it's open source with Flex 3, so that is the core tooling and it provides the compiler, the debugger, all the components that you need to build your application and you can use any editor you want to build your applications and run the compiler. There's ANT compile tasks, there's a command-line compiler, all those sorts of things to actually allow you to compile your application into the bytecode. So that's the core, is a free open-source product called the Flex SDK and then on top of that there is the Flex Builder IDE which is a plugin to Eclipse. And that plugin to Eclipse allows you to more easily build your Flex applications. So it's using that same Flex SDK, but now you have things like code hinting, debugging, design viewer; you can just drag and drop your components onto a canvas to build your user interface. It also provides some great integration with designers; most designers are using Adobe tools, so you can actually take assets that those designers provide you and integrate their designs and their assets into your Flex application or Flex Builder, facilitate some of that. And you can do that without Flex Builder, but just not as efficiently.
On the Flex developer community:
There is a broad range. You can get everyone from the Flash designer that got into some ActionScript coding and started building some stuff with Flex, to the other end of the spectrum -- the hardcore Java developer that's learned Flex and has started building UIs with Flex. So there is a wide spectrum. Right now the place where I'm seeing the most momentum is in the business application space, so it's pretty much becoming the de facto standard for Rich Internet Applications in the business application space, Flex is. We see companies now, like SAP has been a longtime Flex customer, Salesforce.com, NASDAQ, Oracle, just about any large company you can think of is using Flex for their business applications today and that's a trend that's continuing to grow and so we're seeing a lot of momentum there, we're seeing a lot of Java developers pick up Flex and start building their UIs with it, and still of course using Java on the backend. That's of course one of the options you can use. You can build Flex on top of any backend, but the enterprise space, the business application space is pretty much primarily using Java on the backend and Flex on the front-end now, for their Rich Internet Applications.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
18 agile and lean practices for effective software development governance
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
The interview is a little dated now that Adobe have launched Flex 3 and also AIR
br
Reasonably high level discussion. Useful as an introduction to the platform.
This interview provides good information about the purpose of Flex and AIR. For me as a Java developer considering to use Flex as UI for my next web application this presentation was really useful.
There is a mention of the Adobe Livecycle Data Services, the framework provided by Adobe for communicating with remote data services. The interview was done apparently before tools that support the AMF communication protocol were open sourced and became BlazeDS. More info about BlazeDS can be found at: opensource.adobe.com/wiki/display/blazeds/BlazeDS
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
2 comments
Watch Thread Reply