It is day 3 and… I dove right in!!! Kroll did a dangerous thing: They let me into the code! Haha. OK, so maybe it is not THAT dangerous, but I am having a blast going through it all! They are VERY structured… a place for everything and, for the most part, everything in its place. The good thing is that you can really find things throughout all of the solutions and namespaces… the “not-so-good” thing is that there is a LOT to remember, or have readily available to reference.
At Kroll, it’s a totally different code world than school or Deloitte. They are a true Object Oriented (OO) shop with control over just about everything… at the part of Deloitte in which I operated, you were good if you used parameters and a stored procedure or two. At MTSU, we touched a little-bit on objects and practically wrote our queries in the “Button-click” event. Here, everything is so explicitly defined into objects and everything from the Databases is retrieved/stored using stored procedures.
-= Techno-babble Offshoot - For those that may read this with limited, or no, OO or Database knowledge, an Object is essentially a defined collection of data that can be passed from one method, or procedure, to the next as a complete entity. For example, instead of passing employee personnel attributes (name, address, phone, email, and fax) individually, an object allows for the aggregation of those attributes into a single entity, lets name that entity “Employee” or something similar. Once aggregated, that collection of attributes now makes up an Object; that Employee Object can be passed as one entity rather than the 5 individual attributes mentioned above. It is so much easier to pass objects than the individual attributes. When passing data from one method to the next, ( a Method is a sequence of commands to achieve a desired result) the order in which the data is passed matters, and minimizing the “things” required at the time of a pass is a huge way or reducing error and debug time. (Debugging is when you step through the code to make sure the code is achieving the desired result – it is also used in troubleshooting errors.) A Query is a block of structured text that allows for data to be retrieved from a data store , or database, based on selection criteria. A Stored Procedure is essentially a method used to retrieve a pre-determined grouping of data from a database. A Stored procedure accepts a parameter and acts as a barrier between the UI (User Interface) and the DB (Database). Stored Procedures prevent malicious text from being pinned onto a query as well as allow for a more controlled interface to the database. - End Offshoot =-
It’s a different world here, and I am glad that I understand how they are doing things…. And I am 
REALLY HAPPY that a majority of the “things” that I am seeing in their code is something to which I have already been exposed.
::COMING SOON::
nickel4free.com | a Nickel’s worth of FREE information about the Technology I use and my opinions about the coming technology trends and products. Be on the look out for new upcoming articles!
Well… back to my analysis of the programs at work!
-=brett=-
