My name is Caleb, and I'm quite excited to post for the first time on this platform. I'm currently finishing up several bachelor's degrees in computer science, software engineering, digital forensics, and mathematics (the last of which is a minor). Eventually I hope to earn a Master's degree and a PhD focusing on artificial intelligence and malware analysis.
My background is in "forced interoperability," a term that I'm using to describe the development of software that forces two other pieces of software to work together that wouldn't normally perform as such. For the most part, I've utilized forced interoperability during my time as a software engineer in the healthcare space, but I've moved on from healthcare to smart contract development and node maintenance on EOS.IO blockchain instances for EOS BlockSmith, an EOS Mainnet block producer candidate.
In addition, I serve as the founder and chair of the Edmond ACM Chapter (ACM Central), the only professional chapter of the Association for Computing Machinery in Oklahoma. Computer programmers are in high demand, and so it was always astounding to me that my peers in college had such a difficult time launching their careers. The issue was, of course, that often times computer scientists lack the social skill necessary to make the connections required to enter the work force. Our organization works to help professionals (and aspiring professionals, i.e. exiting students) make network connections by working together on bleeding-edge technologies.
Though the course of my academic and occupational career I have found that the saving of code snippets, project workflows, and various programmatic nuances has been very helpful in both cutting down the time it takes to develop new pieces of software and increasing the quality of the produced work. I am certainly not the best writer in the world, but I hope that in addition to providing a place for me to put my thoughts on various topics in the computing disciplines, this blog serves to assist others who are conducting research to complete their work in a more timely fashion.
Note that unless otherwise specified, the examples in this blog may be used as the reader sees fit. However, in the spirit of academia, I would encourage the reader to learn from the content herein so as to apply it dynamically instead of simply utilizing the "copy-paste technique." Furthermore, I must note that all opinions in this blog represent my own opinions, and are not necessarily the opinions of EOS BlockSmith, the Association for Computing Machinery, or any other organization that I work with.