Slipstream: Awaiting the Day When Everyone Writes Software
291928
Too many software programs are ugly: inelegant, unreliable and not very useful. Software that satisfies and delights is as rare as a phoenix.
457664
In this post on the Zend Developer Zone, Cal Evans takes a look at an article published in a recent php|architect issue from Chris Hartjes about how several recent advancements in the PHP community have helped developers think more in "the Rails way" of development.   Chris does a good job of laying out his points. As with any article of this nature, you are going to agree with some of them and you'll disagree with some of them. However, to get to that point you'll have to consider all of them. That's really the point of the article; making developer sit back and think for a minute. It's well worth the read.   Cal also mentions some of the topics presented in the article including more conceptual ideas like "Convention Over Configuration" and "Rapid Should Mean Rapid".
40560
Editors: Shlomo Reifman and Samantha N. Wong Researchers: Joshua Brandt, Fei Mei Chan,  Andrew T. Gillies, Soo Jeong, Edward Knudsen,  Artie Kwok, John Ray and Jody Yen Programmer: Carl Subick
661071
PÃ¡draic Brady continues his series looking at the creation of complex views in the Zend Framework with part six today all about gathering together the thoughts and ideas from the previous articles into a cohesive whole.   Part 6 now takes our previous fragments of theory and attempts to stitch them together into a cohesive whole - a description of a possible end solution. Yes, I know code talks loudly, and we'll get there with an almighty bang in Part 7 (which I promise is no more than a week away). Until then it's more verbosity.   He suggests a list of six terms to help get everyone on the same page when talking about the complex views:   Includes Partials Dispatches Layouts Placeholders Response Segments   Since these terms would mean nothing without proper definitions, he provides a few paragraphs on each explaining what they are and, where necessary, using code to illustrate the point.
682560
It's not perfect yet, but Eclipse marks a new way of developing applications.
19328
Daily progress reports for agile development teams.
140916
Blog: As an industry we are terrible at working on interoperability.  The open source world should be the one to fix this.
653200
An investor's guide to service-oriented architecture
746663
Blog: Software maker says it's ready with a near-final "release candidate" version, which will find its way on to servers later this year.
337538
How far is too far when it comes to the freedom of software? Plus: Palm slipping, Windows sliding.
256798
The O'Reilly Network has a new article posted for all of those out there that are looking to make writing large documentation/publications much simpler.
588152
Russ asks: Where's the OpenSocial container API? I love Russ because he cuts through all the BS and gets right to the core, most basic question, and he doesn't care who he pisses off. That's my kind of developer. You can't lie to the compiler, when the bits hit the road, you gotta know what garbage goes in and what garbage comes out.  (Ahh programmer's humor!) In other words, suppose I wanted to compete with Google, MySpace, Plaxo and LinkedIn, well, where's the spec that shows me how to do that? Well, of course I don't know, they aren't communicating with riffraff like me, but I have some experience with this kind of stuff, so I can hazard a guess. If they publish a spec,all kinds of projects will likely get started to enable the API in (just for the sake of argument): Drupal, WordPress, Twitter, Pownce, Jaiku, Scripting News (why not add widgets to a random blog), CNN, The New York Times, well you get the idea. There might be lots of implementations very quickly. And that would be it for changes. It would be frozen de facto, they'd have to live with what they have, which given how quickly it was thrown together, probably isn't very good. Not the kind of stuff you'd like to support for the next decade or two. Or maybe they would break everyone, something guaranteed to make them a lot of enemies, much the way Microsoft did, and they were good at migration of APIs.  Google is good at doing AJAXy web UIs, they make users happy, but they're not very good at APIs. This one is a loser, for sure. That's the answer to Russ's question. It's probably not malice that keeps them from releasing details to everyone outside their club, it's pragmatism. They have to try to hold on to it to keep it from becoming even more of a mess than it already is. Just my opinion, for what it's worth. I've been wrong many times before.
290330
By JAMES DERK  There was a monumental announcement in the computing world last week that was barely noticed outside of the trade press.
193063
Are Internet users about to suffer from beta-testing burnout?
485277
I've been saying this ever since I started blogging.  When you have a product to announce, start a blog (if you don't already have one) and announce it. Before there were blogs, I wished Infoworld or PC Week would give space to the lead developer of the product, whether he or she is a marketer or technical, even the CEO if they wouldn't assign a former reporter or ad guy to write it, and tell us what you meant when you designed this product. Who were you thinking of and what would they do with it. And where does it go? What does 2.0 look like if it's 1.0 or 3.0 if it's 2.0.  I like it when people like Zuckerberg, Andreessen or Canter write a blog post that tells you without pulling any punches what the intent of the product is, in their own words. I'd like to hear what they said to the team that worked on it. I'd like to use my imagination. That's why I don't like Steve Jobs' keynotes, he's telling you what Eddie Haskell would say about the product to Mrs. Cleaver. You never get the intent when it's filtered by the press. And many of the people that call themselves bloggers, love them and bless them, aren't anything like bloggers, and they're everything like the bored hired writers that used to work at CNET and Fortune. In fact, many of them are exactly like them (because they are them).  We live in the age of DIY, that means if you have something to say, just say it. PS: Here's a picture of three child actors from Leave It To Beaver, taken when they're in their fifties. From left to right, Eddie Haskell, Beaver and Wally. Time Waits for No One.
378431
By Balas, Janet L  Sometimes I feel that I am becoming a technology curmudgeon. I don't just jump on the bandwagon at each announcement of a new technology; instead I wait to see if it has any advantages besides being new.
765964
Delivering the capabilities of traditional EAI products within a light-footprint, standards-based infrastructure supporting incremental integration