Domain: ambysoft.com
Stories and comments across the archive that link to ambysoft.com.
Comments · 5
-
Re:Actual Software Engineering
But I must also point out that for every example you can give with a success story like Flickr, there are 99 abject failures that show how difficult it is to be flexible this way, it demands discipline. Maybe it is even so that the more flexible and agile you are the more discipline you need to have.
I agree completely. Without smart, experienced people with the discipline to envision a process, follow it, and adjust as needed, I think any project is screwed.
The thing that kills me about a lot of the formal, high-ceremony, high-documentation methods out there is that they are sold as something to do instead of getting great people and being disciplined. Many people cater to the dumb manager's desire to believe that if they only follow some magic recipe, great software comes out at the end no matter how screwed up your organization is.
Not that some agile process proponents don't also over-promote, but the Agile Manifesto makes it clear that process isn't the answer, which does help limit the damage. :-) -
some arguable classics
I keep a bunch of "classic" bookmarks around. Some are undisputed gems, others are, well, to my taste. Bytes being cheap here's a batch.
- Ars Technica: The PC enthusiast's resource
- AmbySoft Inc. White Papers: Scott Ambler's Online Writings
- windows.oreilly.com -- Deep Inside C#: An Interview with Microsoft Chief Architect Anders Hejlsberg
- TQ
- The Rise of ``Worse is Better''
- A Whirlwind Tutorial on Creating Really Teensy ELF Executables for Linux
- Theist Hall of Shame
- Internetworking Technology Overview
- Software Technology Review
Eric Weisstein's World of Mathematics - P.S.: More Than Just Words
- Welcome to the On-Line Encyclopedia of Integer Sequences
- John McCarthy
- Slashdot | Net Translations of Dead-Tree IT Classics
- advICE
- 0xdeadbeef archives
-
O/R Mapping Layers?
One interesting compromise is to use O/R mapping layers; you put all your data in a traditional SQL database and describe a mapping to objects.
A couple of interesting open-source ones are Castor and Osage. I haven't had the chance to use either one in a serious project yet, but as a NeXT refugee I'm looking forward to using a good O/R mapping layer again. Do people have any recommendations?
For those interested in the topic, there is useful information at Scott Ambler's site, including his white paper The Design of a Robust Persistence Layer for Relational Databases. -
O/R Mapping Layers?
One interesting compromise is to use O/R mapping layers; you put all your data in a traditional SQL database and describe a mapping to objects.
A couple of interesting open-source ones are Castor and Osage. I haven't had the chance to use either one in a serious project yet, but as a NeXT refugee I'm looking forward to using a good O/R mapping layer again. Do people have any recommendations?
For those interested in the topic, there is useful information at Scott Ambler's site, including his white paper The Design of a Robust Persistence Layer for Relational Databases. -
SQL vs OO by Scott AmblerScott Ambler at AmbySoft has written quite a lot about this, especially when it comes to using relational databases in an object oriented system. Check out http://www.ambysoft.com/onlineWritings. html
Despite the fact that many old SQL folks get very upset when they see things like the complete absence of stored procedures and triggers, I know from personal experience that (many of) his recommendations work just fine.
/Basic