One reason for the success of DMX Coding is in part due to its relationships it has with other companies and organizations. I've made some key connections that have proven very useful in creating successful software for my clients. These relationships have allowed me to push the envelope, and have given me the ability to broaden my skill set. In my portfolio, I have listed both consulting and employer relationships I've had in software development. One might argue that a portfolio should consist of consulting projects, leaving work done for an employer strictly on a resume. I disagree. Your work is always a part of you, whether you do it for yourself, or for someone else. Whether working for an employer or consulting for a client, the skills you have benefit both situations. A portfolio is not a repository for code, but a gallery of your skill set. I am able to leave DMX Coding outside of my employments, and vice versa. And yet they both benefit from the other.