| |
Topic |
Replies |
Author |
Last Post |
|
Code Generation: The Real Lesson of Rails
In an article introducing Ruby on Rails' Active Record, Bruce Tate suggests that Java could enjoy some of the benefits of Rails by taking a wrapping rather than a mapping approach to persistence. I think this misses the point. What Rails really demonstrates is the benefit of code generation.
[Page:
1
2
3
]
|
42
|
Bill Venners
|
Apr 6, 2007 12:21 PM
|
|
Fun With Automated Characterization Test Generation
This is the fourth installment in the "Working Effectively With Characterization Tests" series. This time we look at how automation can help you create and/or improve your characterization tests using JUnit Factory, a free, web-based, experimental characterization test generator (and my pet research project).
|
6
|
Alberto Savoia
|
Apr 3, 2007 3:50 PM
|
|
Back at OOPSLA
For the first time since 1989, I'm attending OOPSLA. Some things have changed, others have not. Here are a couple of reflections...
[Page:
1
2
3
4
]
|
48
|
Jim Waldo
|
Mar 29, 2007 9:25 AM
|
|
Refactoring 2.0
What automated refactorings would you like to see?
[Page:
1
2
]
|
24
|
Michael Feathers
|
Mar 28, 2007 8:24 PM
|
|
What's on Your Java Learning List?
Since we have limited time each day to learn new languages, language features, and APIs, we must decide where to focus our learning efforts.
|
11
|
Frank Sommers
|
Mar 22, 2007 7:53 PM
|
|
Deterministic Software Development
As long as we believe that it's possible to deterministically control the development of software, deterministic solutions will be the only ones that we can entertain. Only by letting go of the idea of determinism can we open up to other, less perfect ways of influencing the process.
[Page:
1
2
3
4
]
|
45
|
Bruce Eckel
|
Mar 22, 2007 2:43 AM
|
|
Working Effectively With Characterization Tests - Part 3
In this 3rd part of the series, we put our newly created characterization tests to work, and we see how even the simplest and most innocent code changes can cause unexpected and unwanted changes in the behavior of our code. Fortunately our characterization tests are there to protect us.
|
0
|
Alberto Savoia
|
Mar 15, 2007 2:55 PM
|
|
Working Effectively With Characterization Tests
This is the first installment in a series of short articles I plan to write on characterization testing. Characterization testing is an important concept and an essential tool for software developers working with legacy code (i.e. most of us) and it deserves broader exposure and more attention.
|
3
|
Alberto Savoia
|
Mar 14, 2007 7:48 AM
|
|
Motivation behind open source
Why do people develop open source software?
|
8
|
Rahul Chaudhary
|
Mar 14, 2007 4:36 AM
|
|
PyCon 2007 Review
My impressions of the Python Conference 2007 in Dallas, Texas, written up on the plane home while it was still fresh in my mind.
|
11
|
Guido van van Rossum
|
Mar 13, 2007 4:07 PM
|
|
Do We Need a Threading Maturity Model?
Almost every program we write today will execute in a concurrent computing environment. But to what degree do developers really have to be aware that their programs run on concurrent hardware?
|
8
|
Frank Sommers
|
Mar 13, 2007 7:40 AM
|
|
Subduing CLASSPATH
Setting CLASSPATH for directories and jars driving you crazy? I finally decided to do something about it.
[Page:
1
2
]
|
26
|
Bruce Eckel
|
Mar 11, 2007 3:40 PM
|
|
Custom Search Engine for Programming Languages
I've recently discovered the Google custom search engine service (the so-called Google co-op) and I've used it to build a search engine service dedicated to programming languages.
|
10
|
Christopher Diggins
|
Mar 11, 2007 2:29 PM
|
|
Recording of Java/Flex eSeminar
James Ward and I just finished an eSeminar, which was recorded as we gave it. The URL is available here, so you can listen to and view the recording.
|
2
|
Bruce Eckel
|
Mar 8, 2007 12:12 AM
|
|
Developer Testing Masters and Brain Surgeons
Testing is tough for most programmers, but without some amount of developer testing delivering quality software is even tougher. We propose a new software specialization and position – Developer Testing Master – to help software organizations fill the horrifically expensive testing gap between development and QA.
[Page:
1
2
]
|
23
|
Alberto Savoia
|
Mar 6, 2007 11:37 PM
|