Interested in Software Architecture? Twin Cities resident? On Monday, August 16th 2004 from 6:30 to 8:30 PM, Cris Ross, CIO of United Behavioral Health will be delivering a presentation on "The Secrets of ROI for Architects" for the Twin Cities Chapter of the International Association of Software Architects (TC-IASA). The meeting'll be hosted by Intertech Training in Eagan, MN.
The return of an aboriginal blogger
I decided it was time to validate the HTML on my site, but wanted an integrated solution that would flag problems during the build process.
It's begun to dawn on me how little is actually understood about software architecture. What is it? Where did it come from? Where's it going? As a software developer, why should you be concerned with software architecture? I can't answer all these questions but at least I can offer a starting point for Java developers interested in learning more about software architecture.
Since I wrote the "elephant" article just over a week ago, my mailbox has been flooded. Sure, some of the mail was hate-mail. But a whole lot of you understood the spirit of the article, and it got us talking.
I just landed my dream job as a developer and consultant working with a small Open Source consulting business called Open Technology Systems. I get to work with Open Source technology in a company dedicated to our movement and help them build solutions for small and midsized companies in the local community. I can't think of a more perfect job.
Everyone knows you can't easily write unit tests for EJB components. Or can you? I just wrote an article on testing EJBs in-container, and if you work with EJB technology you might want to take a look at it. A lot of the complaints about EJBs have focused on how difficult they are to unit test, and frameworks have begun to spring up that simulate the EJB container and server environments for testing purposes. I've recently stumbled upon a technology that has given me a very compelling reason to reconsider my EJB unit testing strategy.
So far I've discussed some cultural conflicts, differences in vision and how the Java and Microsoft communities differ in their relation to small clients, small vendors and the Open Source community. Today I'm going to divert a bit from this track and discuss a family of architectural principles I learned at TechEd, and how I think they might help J2EE architects and software developers continue to improve their productivity.
Today I look into how the .NET and Java communities differ on their approach to and support of Open Standards and how Open Source fits in the big picture.
Thank you very much, but I already have a job.
Day two of TechEd 2004 began with Microsoft CEO Steve Ballmer's keynote address, and marked my reentrance into the world of Microsoft web development technologies. I'm still slightly reeling from culture shock, but day two of the conference reaffirmed my belief in the Java platform and the need for enterprise-scale systems. Today I began to encounter more of the division between the .NET and Java developer cultures. Also, I ran into deep misunderstandings about the nature of Open Source and how it differs from Free Software. I'll stub out my thoughts on these areas, and then probably return to them in the days and weeks to come.
After a fairly grueling morning of plane-hopping, I arrived in sunny San Diego for the Microsoft TechEd 2004 conference. Here are some of the observations from my first day of immersion in the .NET user community.
What if there were a Shockwave Community Process, so that Macromedia could extend the same invitation to the industry at large to participate in the future of Shockwave that Sun has extended with regards to Java?
It's conference season. All winter we tinker in our little labs, bent over our laptops like overgrown, caffeine-saturated gnomes, coke-bottle classes beaded up with perspiration as we hack away at our latest and greatest JSR implementation or pet project. And then, before we know it, the cherry trees are in bloom on the boulevards, and we find ourselves scurrying around in anticipation of the almighty Conference. Printing up cheap business cards at Kinko's and pecking away at travel sites in search of hotel discounts, do we ever stop to consider how much we resemble cicadas? These thoughts and more have crossed my mind this week, as I prepare for the biggest conference I'll attend all year. But it's not JavaOne. This year I'm not going to JavaOne. I'm going to Microsoft's TechEd.
Continuing my series about my mistakes and successes on running a profitable website. This time, I talk about content.
"The possibility of creating an XML-driven, Flash-based, online product configurator would be virtually impossible without Flex.--Macromedia spokesperson
Guess what? I need a job too.
Social networking systems, despite being the new Hot Technology to grab the attention of Valley venture capitalists, are lately being subjected to a healthy dose of criticism: for systems designed to help people interact, why cant any of the systems interact? And why have the systems overlooked some of the most obvious functionality a user or developer might want?
Has Sun been paying too little attention to Microsoft. Or too much?
How long will corporate America put up with the high prices and low quality of the software industry? A handful of major corporations have decided "enough is enough" and have banded together to form their own "software co-op". What impact will this have on our industry?