As I get more experienced with ergonomic languages like Ruby, the sharper, stupider parts of Java are coming into sharper relief for me. Fortunately, at least some of these problems are cultural rather than technical, and and can be corrected by simple changes in practices. A great example of this is java package structures.

On a design team, one major challenge is simply keeping track of the design artifacts generated by your designers. Whether you're taking digital photos of a whiteboard or crafting ray-traced buttons in PhotoShop, a few weeks of visual design work can generate hundreds of files, making it difficult to keep track of what the current design is, let alone track progress and changes that have been made, or make sure that critical work isn't lost.

Are engineers from Mars, and designers from Venus? Communication between the two groups is famously fraught with difficulty: they speak different vocabularies, often have different cultural values, and may not even have a tremendous amount of respect for each other's chosen profession! However, simply being literate in each other's design deliverables can go a long way towards bridging the gap between these two groups. Engineers can read interaction design deliverables: it is now up to designers to become literate in technical design deliverables.