About Me


My name is Arthur Weborg (/wê·borg/ not to be confused with /web·org/); I am a Software Engineer. (However, if we are being honest /web·org/ happens to be more favorable to my work.) I currently work for The Medical College of Wisconsin developing software used in whole exome and whole genome sequence analysis. I am happily married to my wife, Kate. We have no kids yet, but 10 years from now we expect a full house. Fingres crossed for three-of-a-kind and/or pairs.

Now that I have the formal introduction out of the way; I LOVE TO PROGRAM! This site was not made using blog software... it was self generated using code, a system I both designed from scratch and wrote. Because of this, it's very easy to maintain, change and add new content too... still working on expanding functionality.

On the note of making software easier to maintain and use, let's be honest here, I despise crummy software! Me being accused of a bug in released code is like Marty from Back to the Future being called a chicken... I'm working on not getting upset, just like Marty I am able to handle the the claim. At that, it took me a good 4 years of bugs and stacktrace errors before I decided I was done hacking fragments of code together. That and stack-traces 5 minutes before project deadlines for my Software Engineering courses at MSOE brought me to tears on 1 too many occasions. Around the end of my Sophomore year of college I started diligently improving my processes to develop code.

One of the most mutually hated classes at MSOE in the Softare Engineering track on PSP (Personal Software Process) brought to light a method to the "madness". We were taught how to track our development practice and even predict how and when bugs would occur! Being able to predict also allowed for means of avoiding the bugs altogether! Now, bugs still happen, but the goal is to catch them all before releasing the software!

Now that we've all graduated most of my peers also mutually agree that having a structural process is needed to producing, maintaining, and validating quality code is the way to develop software. To re-iterate, far less bugs occur when you have a plan, and are constantly evaluating and improving your process.

Now for the fun stuff to talk about! College around the end of my Sophomore year also started getting more difficult. I realized I did not have enough time to do school, track, church, and play video games. After that I did what anyone in my situation would do; I wrote software to play video games for me so I could focus on church and track. Oh yeah, school... my focus on school remained the same. Wish I could go back, I missed graduating on the Dean's list by .03 on my GPA.

Fast forward through several years of developing software for a clinical genomic diagnostics lab that is HIPPA, CAP and CLIA certified.

I've come to love and grow my software development into a practice of Software Engineering. I enjoy challenges, as Adidas framed it, "Impossible is nothing." However, as I see it "To God nothing is impossible" and I put my trust in Him to give me the answers to the questions and problems that I have no idea how to solve. He has not failed me, have been privilaged to develop some ridiculous software because of Him.

At some point in time I will formally switch over to contracting and consulting. If you ever have any requests for software or are interested in learning more about a topic of software development, please contact me! I would love to hear from you :)

Developed by Arthur Weborg

r2msoe@gmail.com