Agile Project Management: Lessons Learned at Google
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
Tracking change and innovation in the enterprise software development community
Posted by Jon Rose on Jan 22, 2008 06:42 PM
InfoQ.com has covered a number of advanced and intermediate topics on the who, how, and whys of the Adobe Flex development framework, including: Who Is Using Flex, Flex Misconceptions, The Proprietary Nature of Flash, and Open Source Flex Frameworks. Ted Patrick, a Technical Evangelist for Adobe, takes us back to the basics with his blog post, ‘What is Flex?’At the heart of Flex is the ability to create SWF files that run in Adobe Flash Player. Distill all the features down and really it is a development paradigm that compiles to SWF. It really is that simple but often we make the definition much harder. Just like Flash can create SWF files, so can Flex but the way you develop is completely different.He continues by highlighting that Flex is an application development framework:
Flex was not built for animators, writers, accountants; it was written for software developers and the paradigm matches the development methodology you already know.Patrick emphasizes that Flex is for building applications that run in the Flash Player runtime, both in the browser and through the Adobe AIR desktop runtime:
...
Flex has classes, components, a compiler, a debugger, class libraries, and uses XML (MXML) for declarative markup of components. The ActionScript programming language is based on ECMAScript 4 (the language standard behind JavaScript) and has full support for the ECMA XML scripting standard E4X. It also has most of the UI components that you already use (like button, list, datagrid, combobox, and tree) but it also supports containers like HBox, VBox, TabNavigator, TitleWindow and many others.
Flex was built for making rich client side application behavior. It wasn't built for making web pages, banner ads, or server side logic it was built for creating client-side applications that run over the Internet talking to remote servers.Patrick finishes by stressing the fact that Flex builds on the technologies software developers already know:
Flex leverages the tools, servers, and development models that you already know and allows you to write the next generation of software compatibly.To learn more about Adobe Flex checkout the Adobe Flex Developer Center. For Java developer specific resources: http://flex.org/java/
IBM Web 2.0 Developer eKit: Free Tutorials, Webcasts, Whitepapers
Software Quality Survival Guide
RESTful todo list sample tutorial with Groovy & Project Zero
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
IBM Agile Development eKit: Free Articles, Expert Q&A, Educational Resources
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
In this talk from QCon SF 2007, Justin Gehtland explains two open solutions to distributed identity and their Rails integration components: OpenID (using ruby-openid) and CAS (using rubycas-client).
No comments
Reply