Sponsorised links
This year
Guidelines for Writing JSR-168 Portlets
by holyver
& 1 other
(via)
JSR-168 is a collection of Java APIs for portlet developers. There are a number of reasons to design JSR-168 portlets that adhere to the specification. Portability is an obvious benefit. Code written according to the specification will be easier to move to among portal servers. The majority of Java-based portal servers support JSR-168 portlets.
Another benefit is easier federation. Exposing JSR-168 Portlets via Web Services for Remote Portlets (WSRP) producers is easier when portlets adhere to the JSR-168 specification. WSRP provides a standard to federate portlet content via Web services. JSR-168 and WSRP 1.0 portlet capabilities are tightly coupled. JSR-168 to WSRP portlet bridges utilize JSR-168's URL rewriting APIs. This article illustrates best practices for developing JSR-168 portlets for portability.
Brad Abrams : Internal Coding Guidelines
by ERSWeb
& 1 other
Design Guidelines, Managed code and the .NET Framework
Sponsorised links
2007
Reference Architecture: The best of best practices
by nhoizey
(via)
A reference architecture is a resource containing a consistent set of architectural best practices for use by all the teams in your organization. This article describes the benefits of using reference architectures and describes how to create, use, and maintain them.
2006
Classrooms@Work
by knann
& 1 other
Four sample projects that are models of effective technology integration
Bulletproof HTML: 37 Steps to Perfect Markup
by marco
This article highlights and answers some of the most frequently asked questions about HTML. HTML is the foundation of the Web, and both developers and designers need to understand it.
SOA Best Practices: The BPEL Cookbook
by nhoizey
(via)
Learn advanced BPEL concepts and best practices for development, deployment, and administration from the architects implementing them in real-world applications.
2005
Dog Food
by nhoizey
(via)
"Eating your own dog food" is a metaphor for a programmer who uses the system he or she is working on. Is it yet functional enough for real work? Would you trust it not to crash and lose your data? Does it have rough edges that scour your hand every time you use a particular feature? Would you use it yourself by choice?
Particletree · The Hows and Whys of Degradable Ajax
by nhoizey
& 6 others
we decided that we wanted to create a flawless user experience for all users without having to sacrifice the added user interface benefits provided by Ajax goodness
Rockford Lhotka - Should all apps be n-tier?
by nhoizey
& 1 other
(via)
There’s a huge difference between logical tiers and physical tiers. Personally I typically refer to logical tiers as layers and physical tiers as tiers to avoid confusion.
Little Nybbles of Development Wisdom
by nhoizey
& 1 other
(via)
Software is more an art or skill than a science or engineering discipline. The most effective means of becoming a great programmer is through an apprenticeship (even if self-directed). There is no substitute for coding a big system that evolves over time. It seems to take about 2 to 3 years before somebody absorbs the important lessons.
Thinking and Making
by nhoizey
& 4 others
(via)
Recent interest in rich, asynchronous, web applications drove many designers and developers to quickly implement javascript widgets to a wide variety of web applications. While the excitement has fueled inspired innovations, the race has left behind several emerging best practices for using javascript.
