What is XCJS?
I often get asked what exactly “XCJS” means. It, along with the nature of technology, has changed a little over time.
I immediately observed how conceptually different these languages are and pursued improved methods of structuring code, both on the server and on the client.
From that came XCJS – a simple, four-letter domain I could call my own. I could experiment, provide a compelling portfolio, and maybe share what I find exciting about technology.
What else can you do?
My education provided a basis in .NET technologies, including C#, Visual Basic.NET, and ASP.NET Web Forms. With that came basic experience using the browser-based technologies mentioned by name above and data persistence with relational databases.
These early efforts proved to me that code should be better organized and provide a SOLID platform for whatever future updates may come.
I independently studied design patterns and architecture, hoping I could combine these many disparate tiers in ways that allowed for flexible, responsive solutions.
I wanted to automatically test my software to ensure my code was dependable and behaved as expected, and I wanted deployment solutions paired with continuous integration so my software steadily improved over time with as few risks as possible.
I wanted to learn everything, and while I doubt that would ever be possible, I have learned much. Hopefully I can share some of my knowledge here.