skip to main |
skip to sidebar
- An advanced article on Spring Security regarding namespaces.
- A few pros/cons on when you'd want to use Amazon's EC2, Google's App Engine or maybe RackspaceCloud.
TweetDeck uses GAE (Python) for some parts of their system, e.g sending emails, in combination with EC2.
- John Resig on improving the Javascript in your web app. Video & full transcript, including new features now available in jQuery 1.4. Mentioned are: delegation, live events, html fragments, javascript from CDN, additional header in Ajax calls, custom events, special events, themeability and customizability, i18n, and IE6 support.
- An older but still interesting PDF on Scrum and XP experience in a project of 40 people. They experimented for about a year on different team sizes, different sprint lenghts etc.
- Expected that Mozilla uses Agile everywhere, and definitely on its flagship Firefox? Think again, only recently they started to combine Agile and more traditional Waterfall as their new development model, dubbed "Lorentz".
- Tips for hardening your Tomcat installation. Other implementation guides, not only limited to Tomcat (also for example WebLogic) tips from U.S. DOD DISA (Defense Information Systems Agency) can be found here.
- Always interesting to at least quickly browse through: a review of the 1993 code of Doom. And more "today": the code of Doom for the iPhone reviewed.
- Think you know Javascript? Try one of these quizes!
- Spring's Web Flow 2 now lets you use JSF as view technology. It addresses a couple of the existing JSF issues and already some features only present in JSF 2.0.
- Microsoft (yes yes, don't stop reading immediately ;-) has published a How-To Design Using Agile Architecture guide which "will help you start the process of designing your application. It discusses the six main steps you should follow, and then discusses the issues involved in making logical choices. It also provides checklists to help you ensure that the proposed design will meet your requirements", including patterns, best practices and agile considerations. This is a quick summary of the guide.
- A tiny bit off-track, but still interesting to point out: of course you know Google's GWT, in which you can create a Javascript web front-end application in Java. But now this is also possible in Python (recently releasing version 3) with Pyamas! Pretty cool!
- Talking about software architecture, how would you document that correctly? Here's a bunch of good tips trying to answer that. It is a good high-level overview of what you should document in an application architecture. Focus is on UML 2.0, but what should be in the documentation is valid for any notation format.
- Here's the first list (and maybe last :-) I'll post on looking back @ 2008: on overview of what happened with Java in 2008.
- Interesting recent long discussion (with a bit of framework flame-war in between) and tips on when to pick what web client framework. Tapestry, Wicket, Stripes, GWT, Flex seem to jump out.
- Interesting Javascript optimizer: Razor Optimizer. It dynamically analyzes the runtime profile information, trying to load each Javascript function only when needed, potentially creating 60-90% savings. It does require a client and server component. The question is: are you prepared to take a (small?) risk that your Javascript is dynamically modified?
- Good article that explains why Scrum often fails as implementation of Agile. Lots of times Scrum is only seen as fast Sprints and Scrums. But: "Don't leave out the 'regular' agile good engineering practices". Check also the comments for good tips.
- A good introduction to RESTful webservices.
- Great, soapUI 2.5 now also suppports testing RESTful webservices. It includes testing JSON output.
- Check the elaborate 95 slides comparison of Javascript libraries at the bottom of this post. It's a presentation by John Resig, Mr JQuery. The presentation is very objective. Compared are: Prototype, jQuery, Yahoo UI, Dojo and Mootools. Another short comparison of 14 RIA/Ajax/Javascript frameworks shows jQuery as the winner, as seen by the User eXperience reviewer. Great news for jQuery this week anyway: both Nokia and Microsoft are adopting it as part of their official application development platform.
- Can't get enough of these RIA frameworks comparisons? Here's another one, which is a short comparison/intro of three Rich Internet Application frameworks: Adobe AIR, Google Gears and Silverlight. See also my (bit older) post here, which also includes JavaFX.
- Summary of an article by Martin Fowler on how Agile can be used in building SOA implementations. The answer: yes you can quickly get value out of it. The biggest proof is the internet: loosely coupled and many unexpected changes.
- Quick-start JSF book free for download. Only 65 pages. Beginners level, step-by-step. With some mixed "infomercials" about the soon to be open source Eclipse IDE extension Exadel Studio Pro, but not in an annoying way.
- Key API design points from Joshua Bloch, Chief Java Architect at Google
- An explanation why a canonical message model (CMM) is a "good thing" in SOA and ESB.
- How to manage and lead geeks in a team. For technical and non-technical teamleaders.
- An interview with leads of PHP, JavaScript, Ruby, Perl, Python, and Tcl on the state of these dynamic scripting languages.
- Interesting technical development: IE8 and Google Chrome are putting tabs in new processes instead of threads. The main reason for creating threads used to be that it takes a relative long time to create a new process and inter-process communication is slow. But, these days the processor speeds are so fast (following Moore's Law etc), creating processes is a piece of cake/can be done really fast.
- How do individualism and teamwork go together in an Agile development project. Why type of roles should you have and what to expect from those roles.
- A short comparison of 8 java web frameworks: Struts 2, Spring MVC, Wicket, Tapestry, MyFaces, JSF, Grails and Rife.
- Patterns-based Evaluation of Open Source BPM Systems: jBPM, OpenWFE, and Enhydra Shark. Report's conclusion: "Overall one can conclude that the open source systems are geared more towards developers than business analysts. If one is proficient with Java, jBPM may be a good choice, although if not, choosing jBPM is less advisable. Similarly, whilst OpenWFE has a powerful language for workflow specification in terms of its support for the workflow patterns, we postulate that it will be difficult to understand by non-programmers. Finally, Endydra Shark’s minimalistic support for the workflow patterns may require complicated work-arounds for capturing nontrivial business scenarios."
- As part of their EC2 offering, Amazon introduced this week their Elastic Block Store, enabling you to mount an EBS and format it or setup a database on it. S3 is not really intended for database-like storage. Here's another introduction, including a link to an article on how to setup MySQL on EBS. Here's ESB explained, including some diagrams.
- Article on the succesful execution of a large project (20 man years, 100.000+ lines of code) with an Agile approach using Scrum, with developers from India and The Netherlands. Includes lessons learned. Technologies used: Java, Spring, Hibernate, WebLogic, Oracle, Swing (UI) and Flex (for the displays) and Bamboo (continuous integration).
- Handy short comparison between LWUIT (recently open sourced by Sun) and JavaFX Mobile. Here's another comparison from Sun.
Del.icio.us
DZone
Reddit
Digg
