Hi Ross! Please also check the answer I gave @Basile B. above which sums up the way we keep our curriculum up to date.
We have a lot of freedom to introduce new tech, but as you can imagine a college environment is not the most flexible workplace to be in. It takes time to implement big changes and we can't just become a totally different college degree overnight. Once students are enrolled, we have an obligation to let them complete that program.
I think we go pretty in depth in most of our classes, but sometimes time is limited and you have to work with what you've got in those three years. Three years may seem like a lot of time, but e.g. the last semester is completely dedicated to internships or working in our own internal agency for clients. When you realise that we start from scratch teaching people with mixed skills (some have built websites before, others have never seen a letter of HTML before) it takes a lot of time to build up those skills to where they need to be. Sometimes we can't go as in depth as we'd like to, it's about finding the right balance.
What's difficult is deciding what to teach and what not. For example, when we decide to create a course on AR/VR, there's other stuff we need to let go. Should we jump on whatever is hot right now, or focus more on core skills and let them figure that hip stuff out on the job? It's a constant struggle 😃
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How do you choose what new technologies you should start teaching, or do you only go over the fundamentals in depth?
Hi Ross! Please also check the answer I gave @Basile B. above which sums up the way we keep our curriculum up to date.
We have a lot of freedom to introduce new tech, but as you can imagine a college environment is not the most flexible workplace to be in. It takes time to implement big changes and we can't just become a totally different college degree overnight. Once students are enrolled, we have an obligation to let them complete that program.
I think we go pretty in depth in most of our classes, but sometimes time is limited and you have to work with what you've got in those three years. Three years may seem like a lot of time, but e.g. the last semester is completely dedicated to internships or working in our own internal agency for clients. When you realise that we start from scratch teaching people with mixed skills (some have built websites before, others have never seen a letter of HTML before) it takes a lot of time to build up those skills to where they need to be. Sometimes we can't go as in depth as we'd like to, it's about finding the right balance.
What's difficult is deciding what to teach and what not. For example, when we decide to create a course on AR/VR, there's other stuff we need to let go. Should we jump on whatever is hot right now, or focus more on core skills and let them figure that hip stuff out on the job? It's a constant struggle 😃