CRNRSTN :: ABOUT

Philosophy ::

In ancient times, a home could be constructed using large stone pieces to provide key support to the structure at the foundation, corners and top. A cornerstone (or chief or head cornerstone) is the joining stone that rests above and connects and holds together two walls of a house.

Pro Tip (Christian) :: When Jesus came (when the eternal God became a finite man), He came as the reality of the cornerstone (the real cornerstone) joining the "wall" of the Jewish believers and the "wall" of the gentile believers together into one house in the building of the church. Jesus is the Cornerstone (Eph. 2:20, 1 Peter 2:6) in the building of the Father's house...the church...joining all of God's people together in Himself. According to the footnote 3 on Eph. 2:20 in my Recovery Version study Bible, when the Jewish builders rejected Christ, they rejected Him as the cornerstone (Acts 4:11; 1 Pet. 2:7), the One who would join the Gentiles to them for the building of God's house.

Well, to liken the act of building a house to the process of coding a web application...or should I say rather...in elegantly correlating a tool satisfying web application requirements for codebase portability under rigid release to manufacturing (RTM) processes to the simple illustration of a cornerstone properly joining the "wall of the server environment" to the "wall of application codebase", I have taken a modern technology staple and cast it under the warm analogue glow of the ancient world of house building.

Purpose ::

When I entered the workforce as an HTML developer (after the start up companies), I used PHP on the side to put together various portals and tools for quality control...heck...even web services. Sadly, I never had the time to carve out for myself a PHP class library for the gaining of efficiencies in product maintenance, development and deployment. While working at Moxie, I really could have used an out-of-the-box/plug-n-play class library with the capability of facilitating an application's compliance with a mature development shops' RTM processes.

I needed a class library that would support and standardize fundamental architectural and operational requirements. It also needed to be capable of performing flawlessly (read as fast and light) in some of the most brutal hosting/traffic environments known to man.

Since transitioning out of the agency job, I have had the opportunity (and the time) to roll up my sleeves and jump knee deep into the code. I put this project together so that I could have a mature development framework...a proper starting place...for all of my web development (LAMP stack) projects. So, as a result of years of contemplative thought, many hours spent in application testing & development, countless cups of coffee and a hint of marijuana...I humbly present to you the CRNRSTN Suite ::.