Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Getting Started with Stratos - an Open Source Cloud Platform
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
There is an online article that states that Java developers just do tools for each other but not good apps for users. The article exaggerated to be doutrageous, but it contains lots of truths.
If you Java-ified Ruby, we will have more developer-tools and more e.g ant, maven, other many just for 'making'.
And fewer and fewer apps/
How many Java forums to challenge PhpBB, Moodle etc? Wikis?
george
ethicminds.blogspot.com
There is an online article that states that Java developers just do tools for each other but not good apps for users.
-----------------------------------
can you tell me the url of the article?thanks in advance
Hi,
I read that article about 3 years ago, and right now I cannot find it on Google.
I want to apologize if I've sounded like a troll here.
(1) I have nothing against the author/Enebo or the project.
(2) I am not even against JRuby. I am even agitating the use of JRuby in my local Ruby user Groups. I am all for calling Java/C++/Lisp from Ruby.
What I can't stand is what I would call Java-ism. esp. DOWN WITH THE SUN!
(1) When Bruce Tate talked about bloat in his "Faster, Lighter, Better Java," I don't agree.
(2) When DHH and team separated out a lot of stuff from Rails core, I don't agree.
I like bloat. We need bloat. e.g. Why don't DHH team take out ActionMailer from core? Go ahead email is not core to MVC, right?
Every popular/useful language/framework grows. We welcome it. But how it grows can often rub us the wrong way. eg. Java Swing, JMX API, EJB, JDO, so many API's made in SUN! May SUN rest in Peace!
Suppose, if I design Rails 34.56, I would like it to include modules for
(1) rendering views in iPhone platform
(2) rendering views in Symbian platform
(3) rendering views in Android platform
(4) rendering views in some other unknown mobile platform
...
(56) integrating with popular CMS like Plone, Zope, Joomla etc
...
(78) Calling Erlang
(79) calling Thrift
...
What is wrong with that?
We are not mono-cell amoebas. How did we grow our eyes, ears, legs, limbs?
The more complex, the better! The more bloat, the higher up in the food chain!
Go argue with Evolution, with Biology.
But, Evolution didn't work like SUN architects. When you get your left toe hurt, you suddenly don't get a headache or an eye blur or a stomach ache. What I am talking here is MODULARITY from the user's perspective. IS THAT TOO deep to understand for SUN/Java API designers?
SUN is declining, or we may have to learn EJB 12.56 etc. How many Java API's have gone down the drain?
Joel Spoloky says we programmers don't read, not even our own industry's history.
No time for Biology and Evolution?
Fine, please read Robert Glass, at least.
IF I SOUND arrogant/angry, please bear with me. I AM JUST TYPING IN A rush.
I love you all ;-)
george
ethicminds.blogspot.com
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
3 comments
Watch Thread Reply