Forget technologies; forget grades. At best, they will get you in the door for an interview. They won't make your a productive employee.
If you can produce working, deployable software on your own, then you will succeed. Not that many people can, honestly. If you aren't sure if you can hack, then pick a problem and solve it. If at the end of a week you can give your software to someone else and have them use it successfully, you should be fine.
Everything else is fluff, and can be learned on the job. If you can hack, you'll do fine.
Thats what I am hoping for. It can just become overwhelming for a young-buck (such as myself) when seeing all these frameworks and libraries and trying to figure out which ones my future employer will want used. In my CS studies, we have focused on a lot of 'whats under the hood' (aka linked lists, binary trees, etc,.) and so when I see these frameworks, I cannot help but think "which one do I use? Can't I just write the algorithm myself?!"
If I am understanding you correctly, if I can do this (know what is going on under the hood), then the rest of the cards will fall into place (?).
Forget technologies; forget grades. At best, they will get you in the door for an interview. They won't make your a productive employee.
If you can produce working, deployable software on your own, then you will succeed. Not that many people can, honestly. If you aren't sure if you can hack, then pick a problem and solve it. If at the end of a week you can give your software to someone else and have them use it successfully, you should be fine.
Everything else is fluff, and can be learned on the job. If you can hack, you'll do fine.