I’m rather sympathetic to the view that IT Architects Must Write Code — or at least should be capable of writing prototyping code.
I find A Conversation with Werner Vogels quite an inspiring picture of what we might be able to build at UC.
- Rice University and IBM will collaborate on the development of an open-standards-based, service-oriented architecture (SOA) that will help higher education institutions tie together their increasingly diverse academic software applications. The collaboration is supported in part by IBM’s Shared University Research award program, created to exemplify the deep partnership between academia and the industry to explore research in areas essential to innovation. Through the award and software from the IBM Academic Initiative, IBM has donated IBM BladeCenter hardware technology, software for an SOA platform and related services valued at $700,000.
Bubble redux? Perspectives CNET News.com:
- You won’t find the big ideas that ignited breakthrough developments during this phase. With all due respect to their inventors, mashups don’t represent the apex of Silicon Valley’s creative genius. The truly exciting stuff still waits over the horizon. That’s where things are going to get more interesting.
MIT to try Python for introductory CS course (AMK’s Journal):
- Philosophically, the material tries to follow a “practice-theory-practice†model: First, a task is presented and students work on it. Then, students learn the theory that underlies the problem presented, and finally the students tackle the problem again, given these better techniques, Kaelbling said.
- My personal belief is that mashup style software development, as ecosytems go, will easily overtake most other software development ecosystems in number of developers and applications. To help acclerate that process, ZDNet, in conjunction with Mashup University (the event) now brings Mashup U directly to you, on your desktop at no cost to you.
- So, should we not use mash ups because they are easy to design and then hard to work with? No. They are part of the normal development process. “Pieces parts” or “Frankenstein” systems (now called “mash ups”) typically break ground in a new area. Once the paradigm is established the “vertical solutions” that are easier to maintain move in and take over. Mash ups (or what ever their next “nom de querre” will be) move on to break new ground in a new area. It’s all part of the cirle of life…
Possible alternatives to jython:
Nelson’s Weblog: tech / bad / whySoapSucks:
- As someone who bears some past responsibility for well used SOAP services (Google’s APIs for search and AdWords) let me say now I’d never choose to use SOAP and WSDL again. I was wrong.
Post a Comment