sky

The problem you're going to run into after you graduate is trying to sell yourself to companies. You're going to be hired to do a single job, and that is going to be difficult when employers don't know what you can do (if anything). It makes it even more difficult when many large companies do hiring based on automated searches of resumes. If you don't have "electrical engineering" (or substitute any engineering degree) in your resume, then you won't be considered. You might not get the chance to explain your custom designed degree.

It's fine if you just want to do it for fun, but it's not the most practical and employable path. It's the same problem that systems engineers, biomedical engineers, and other interdisciplinary engineers face when graduating. They don't have the depth in knowledge most companies want. Like I said, companies hire you for a specific task, and given a choice between someone with a hodgepodge of classes, or someone with the exact skill set they need, they are going to hire the one with the exact skill set. You need a good foundation to build up, and that's the problem with trying to teach systems engineering at the undergraduate level. In order to be a successful systems engineer, you need to understand the system first. Anyone can write down a schedule on paper, but it's a totally different issue to execute it. It's widely accepted that it's much easier to train a disciplinary engineer to be a systems engineer than to take a systems engineer and teach them to be a disciplinary engineer. A similar problem exists in the biomedical field when trying to hire undergraduate biomedical engineers.

Granted, this issue all goes away when you have sufficient experience. It also sounds like you don't want to practice in the engineering field, so it's probably a moot point for you. However, I don't think a custom designed degree is a good solution for engineers who wish to actually become practicing engineers.