Click here to Skip to main content

Arjan Einbu - Professional Profile

978
Author
365
Authority
234
Debator
3
Enquirer
274
Organiser
246
Participant
0
Editor
Arjan is working at KodeCompagniet AS in Norway, creators of the DemiCode line of components.
 
His job is in programming, architecture and training where his main focus is on C# and MS SQL Server.
Arjan holds several certifications including MCT, MCSD/MCSD.NET, MCAD, MCDBA and MCSE.
 
When he is not programming, he is probably taking a trip on his Honda Varadero.
Member since Wednesday, March 5, 2003 (9 years, 2 months)

For more information on Reputation please see the FAQ.
 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   


Advertise | Privacy | Mobile
Web01 | 2.5.120529.1 | Last Updated 30 May 2012
Copyright © CodeProject, 1999-2012
All Rights Reserved. Terms of Use
Layout: fixed | fluid

You must Sign In to use this message board. (secure sign-in)
 
Search this forum  
  Refresh
Generaldb4o Pin
Monday, September 10, 2007 11:06 PM
DataBase for Objects looks good!
Removes many of the shortcomings of Bamboo Prevalence written about before.
Look here to download db4o[^] and have a look at the tutorial. It's really easy to get started!
 
GeneralTest First Development / Unittesting Pin
Saturday, September 13, 2003 11:20 PM
An other thing I'm trying to get better at is Unittesting and the main concept in Test First Development: Always create a failing test. (If a test never has failed. It's not worth anything.)
 
A failing test is proof that test is actually running, and only then can the unittest be seen as a verification or proof of that the method beeing tested is really doing its job.
 
When the test is created upfront, you don't know the exact implementation details of the solution you are testing. You only know how it is supposed to behave. (Either since you know the output from a method, the state of an object or the exceptions it should throw.) This is a good thing!
 
After the test has failed atleast once (with the empty solution) you can start programming on the solution. When the tests work, your solution is done. (Or you start creating more test for new functionality. Next iteration of the project.)
 
Unittesting is part of what's called the Agile methodologies. I've learned them from one specific branch of this, named XP, or eXtreme Programming.
NewsVS.NET2005 PinmemberArjan Einbu12:08 11 Oct '05  
Interesting...
Looking back at my old entries here...
Unittesting...
Now, 2 years later, Microsoft includes it in their latest .net offering... Cool!
 
Visual Studio.NET 2005 comes with a unittesting framework built-in, really good integrated.
 
GeneralPrevayler / Bamboo Prevalence Pin
Saturday, September 13, 2003 9:41 AM
This is a very exiting topic that I'm looking into at the moment...
 
A real RDBMS killer: Object Prevalence means keeping all your objects in memory at all times, and still persisting them in a way that ensures no data get lost...
Bamboo Prevalence is a framework library that helps you implement this model in your programs...
 
Does this sound interesting? Then, have a look at these links:
http://sourceforge.net/projects/bbooprevalence/[^]
http://bbooprevalence.sourceforge.net/[^]
http://www.prevayler.org/[^] (They also have a "sceptical FAQ" there.)[^]
 
From my POV, the main thing here is that you can free your objectmodel design from the RDBMS way of storing data. Thus:
- Lets you implement REALLY object oriented design... Easier...
Some other good points are:
- No licence costs for the RDBMS.
- Extremely fast.
- Easier to implement than a RDBMS DAL Layer...
 
Any views, anyone?
GeneralRe: Prevayler / Bamboo Prevalence PinmemberArjan Einbu9:37 18 Oct '03  
GeneralRe: Prevayler / Bamboo Prevalence PinmemberArjan Einbu10:39 10 Nov '03