for now. Still at the same house that I've been at for the past 18 years, but that might change. I guess we'll see what happens.
And, yes, I do take the time to read and approve comments on this blog. It might take me a while to approve them, but I do get to them eventually whenever I remember to log into Blogger. The ones that seem somewhat spammy won't get approved, but there have definitely been some good contributions from visitors, especially in regards to my posts about Coleman College / Coleman University. I approve comments whether they're good or bad. I think it's important for people to know the good and bad in order to make a better decision about something that could affect their future. Education isn't cheap and I want people to spend their money wisely. I think almost every post about Coleman has a comment, so definitely read the comments because I think some of them are even more helpful than what I wrote.
Here are the links for anyone that needs them:
A review of Coleman College's / Coleman University's CIS Program Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7
Since those are my most commented posts, I thought I'd revisit the subject and reflect a little more on the entrance process than on what happens once you're in (because I already wrote about that in the posts above).
My interests have somewhat changed from programming and are more along the lines of internet/affiliate marketing, social media, SEO, and whatnot. Still computer related, but not really anything that has much to do with creating software/scripts/apps.
If I were to go back to school for CS/CIS, I really don't think I would go to Coleman at all. I think I would take courses from UCSD Extension, as mentioned in one or more of the comments. Or even go back to a community college. At least I really felt like I was learning something when I went to Palomar. Whereas, when I went to Coleman, it just felt like with each mod, we'd start all the way at the basics again. I wanted the mods to get progressively challenging and build upon what I've learned, but that wasn't my experience at Coleman. You could probably even learn more from tutorials online, seriously.
Thinking back on the whole process on how I ended up there, it's pretty much just one big sales funnel. If you didn't realize it already, admissions officers = glorified salesmen. From working in the offices at Coleman (not in admissions, but in career services, but it was all pretty close quarters), the admissions officers do seem to have some sort of quota that they need to meet of appointments that they need to set to get potential students. I heard the same pitch that they gave to me told to other people over and over throughout my time working there... so much that I knew what they were gonna say and when.
So, they get you to come in for an interview and tell you more about the school then they give you their silly little logic test to see if you'd be a good fit for the program you want to go through. I think you get two chances at passing it, and they really want you to pass, otherwise their time would be wasted and they'd get no money. They even show you some questions from the test beforehand... probably the ones that are most missed so that you get the answers correct when you take it. It's pretty much the same as the ungraded quizzes before the test that give you the actual test questions - that's what makes it easy for anyone to pass and continue onto the next mod. I passed my math/logic test on the first time, but from working there, I know that there are some people who actually don't pass the first time and they do whatever they can to help you pass.
You passed the test? Great! You're one step closer. It's not really until then that they want to talk money. They don't want to scare you off by talking about that first, so they make you feel good about yourself by giving you a little ego boost from passing their test and then they hand you off to financial aid. They really pushed getting a loan with Wells Fargo. I don't know why, maybe that gets them more money? So I think most people end up getting loans whether they want one or not. After that, you're in... see you next mod!
Once you're in, they were really concerned about attendance. 6 or more absences and you'd fail. They want bodies in those chairs just so they don't lose whatever accreditation they have... because then I don't think they'd be able to call themselves a college/university without it. A former instructor who commented on part 2 of my review could give you more details about that.
Like I said, I don't feel like I really learned much until maybe mod 7, but even then it didn't seem like much.
Showing posts with label coleman university. Show all posts
Showing posts with label coleman university. Show all posts
Monday, August 8, 2011
Friday, May 11, 2007
A review of Coleman College's / Coleman University's CIS program, part 7
7/6/09 UPDATE: Coleman College is now known as Coleman University - this review was written for their classes that I took in 2005-2006, so some things in their curriculum may have changed since then.
Sorry it's been a while since part 6, but finally, here's part 7.
The final mod of Coleman College's CIS program. The capstone project - I don't remember the names of the actual classes at the moment and we always just called the last mod the "capstone" anyway, so that's all I'll be referring to it as. This is where the networking students and the programming students combine once again to build a system.
The networking side will build a network to house the application that the programmers create.
The first part of the class covers all the steps to systems design and implementation. The instructor I had would try to cover that as fast as possible so that we could dedicate the rest of our time to actually building the system itself.
For the programmers, the afternoon class was VB2. During lecture we were taught things like databinding, using a datagrid, and just all kinds of things relating to our application and how it would access our database. This was because in VB1, we didn't use a database at all in our projects, just text files and arrays. Databases make it much easier to navigate through your records. I absolutely loved the whole project. We were given specs and just left to program everything from scratch. I like these types of projects because it really tests what you've learned. The only thing is, I wish it had been in a different language than Visual Basic .NET - I would have enjoyed it more if our project was coded in either C++ or C#.
And since we got our project done early, we had time to get into some ASP .NET stuff. That was kind of neat, but it really wasn't a lot of time to learn it that much. I think a class with just ASP .NET would be great. Coleman College has probably started one by now since their curriculum always tries to stay current, but I don't really know what kinds of things they teach there now since I haven't been back there since I graduated.
Anyway, so what's the big deal about the capstone?? Well, at the end of it all, we have to do a big presentation of our entire system. Students are required to dress up in business attire and basically present it as if they were presenting it to a board of directors of a company. We have to cover things like feasibility, scalability, and all other kinds of -ilities and whatnot. Then we demonstrate how the system works - the networkers talk about their backup plans, data storage, security; the programmers give an overview of the program and show what it does - what data it collects, where it's stored, and give a quick runthrough of the application from beginning to end. It's at least a 40 minute presentation, and they invite the entire school to come and watch it - all the other classes and even the graphics department; and they entice people with snacks so that people will come and see it.
So if you're one of those people who hate public speaking in general, the capstone presentation is a killer - especially if you have a really small class or sometimes you may even be the ONLY person in your class. And you really have to know your stuff in case there are any questions. So if you don't like public speaking, consider yourself lucky if you have at least 3 people in your class since that way you won't have to talk as much. And consider yourself unlucky if you're the only person in your class. But, hey, once it's all over with, you're done because the final for both the morning class and the afternoon class is a piece of cake compared to giving the presentation.
So that's the capstone. I really loved the VB2 project in the class the most. Like I said before, I would have preferred if it was in a different language than VB, but I really have no control over that. ASP .NET - eh, I would have not wanted it covered at all if we really weren't going to delve that much into it, but I guess it was a nice little bonus. The presentation - mine went fine and I was less nervous during it than I thought I was going to be; everybody in my group got full points for it.
Overall, would I recommend Coleman College's CIS program?? Well, yes and no. Yes, if you know absolutely nothing about computers at all - you'll really learn a lot here. No, if you've already self-taught yourself some programming through online tutorials, books, or training videos, or even community college classes. If you already know how to write programs that work, you really don't need Coleman at all because I felt like with every mod, I was just always learning the basics of every language all over again. And it always seemed like there was not enough time to get into the more advanced things or not even enough time to write something that wasn't a CONSOLE or mostly text-only, non-GUI application. If you're already familiar with computers but don't know anything about programming at all, you'll find the first couple of mods a bit boring. But Coleman is a great way to go if you want to learn a lot of the basics (plus some advanced things here and there) of several programming languages quickly - in about 7 months, if you take classes during the day.
If you don't have the money to spend thousands of dollars (you can get a loan, but who wants to pay back loans?? They definitely push for loans in Coleman's financial aid department), you can always go to a community college. It'll take you longer to get your degree, but it's much cheaper and you'll probably learn more than just the basics of each language.
For me, I kind of wish I had gone the community college route and saved myself some money, but it's kind of annoying to do that when not all of the classes I need are offered every semester. Sometimes they rarely offer them at all. With Coleman, you don't really have to worry about stuff like that because they're required to provide the classes that you need, at least for the core program. Really though, Coleman is only worth all the money if you just want something fast-paced and are a quick learner. The teachers there are excellent - always willing to help you out no matter what, at least the teachers that I had.
If all you want is a Computer Science degree and don't care how long it takes you to get it, a community college would be your best option. It's a lot more affordable and your credits would transfer anywhere if you'd want to get a bachelor's degree at any other school. If you go to Coleman, you can only transfer your credits to other ACICS accredited schools. So if you go to Coleman, you're stuck with having to complete your Bachelors and Masters Degrees with them too... which would cost you even more $$$.
That's it for my review of the CIS program. I hope I've helped someone in making a decision. I might go into some non-CIS related stuff in the future, but that's all I have to say (for now) about their CIS program.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Sorry it's been a while since part 6, but finally, here's part 7.
The final mod of Coleman College's CIS program. The capstone project - I don't remember the names of the actual classes at the moment and we always just called the last mod the "capstone" anyway, so that's all I'll be referring to it as. This is where the networking students and the programming students combine once again to build a system.
The networking side will build a network to house the application that the programmers create.
The first part of the class covers all the steps to systems design and implementation. The instructor I had would try to cover that as fast as possible so that we could dedicate the rest of our time to actually building the system itself.
For the programmers, the afternoon class was VB2. During lecture we were taught things like databinding, using a datagrid, and just all kinds of things relating to our application and how it would access our database. This was because in VB1, we didn't use a database at all in our projects, just text files and arrays. Databases make it much easier to navigate through your records. I absolutely loved the whole project. We were given specs and just left to program everything from scratch. I like these types of projects because it really tests what you've learned. The only thing is, I wish it had been in a different language than Visual Basic .NET - I would have enjoyed it more if our project was coded in either C++ or C#.
And since we got our project done early, we had time to get into some ASP .NET stuff. That was kind of neat, but it really wasn't a lot of time to learn it that much. I think a class with just ASP .NET would be great. Coleman College has probably started one by now since their curriculum always tries to stay current, but I don't really know what kinds of things they teach there now since I haven't been back there since I graduated.
Anyway, so what's the big deal about the capstone?? Well, at the end of it all, we have to do a big presentation of our entire system. Students are required to dress up in business attire and basically present it as if they were presenting it to a board of directors of a company. We have to cover things like feasibility, scalability, and all other kinds of -ilities and whatnot. Then we demonstrate how the system works - the networkers talk about their backup plans, data storage, security; the programmers give an overview of the program and show what it does - what data it collects, where it's stored, and give a quick runthrough of the application from beginning to end. It's at least a 40 minute presentation, and they invite the entire school to come and watch it - all the other classes and even the graphics department; and they entice people with snacks so that people will come and see it.
So if you're one of those people who hate public speaking in general, the capstone presentation is a killer - especially if you have a really small class or sometimes you may even be the ONLY person in your class. And you really have to know your stuff in case there are any questions. So if you don't like public speaking, consider yourself lucky if you have at least 3 people in your class since that way you won't have to talk as much. And consider yourself unlucky if you're the only person in your class. But, hey, once it's all over with, you're done because the final for both the morning class and the afternoon class is a piece of cake compared to giving the presentation.
So that's the capstone. I really loved the VB2 project in the class the most. Like I said before, I would have preferred if it was in a different language than VB, but I really have no control over that. ASP .NET - eh, I would have not wanted it covered at all if we really weren't going to delve that much into it, but I guess it was a nice little bonus. The presentation - mine went fine and I was less nervous during it than I thought I was going to be; everybody in my group got full points for it.
Overall, would I recommend Coleman College's CIS program?? Well, yes and no. Yes, if you know absolutely nothing about computers at all - you'll really learn a lot here. No, if you've already self-taught yourself some programming through online tutorials, books, or training videos, or even community college classes. If you already know how to write programs that work, you really don't need Coleman at all because I felt like with every mod, I was just always learning the basics of every language all over again. And it always seemed like there was not enough time to get into the more advanced things or not even enough time to write something that wasn't a CONSOLE or mostly text-only, non-GUI application. If you're already familiar with computers but don't know anything about programming at all, you'll find the first couple of mods a bit boring. But Coleman is a great way to go if you want to learn a lot of the basics (plus some advanced things here and there) of several programming languages quickly - in about 7 months, if you take classes during the day.
If you don't have the money to spend thousands of dollars (you can get a loan, but who wants to pay back loans?? They definitely push for loans in Coleman's financial aid department), you can always go to a community college. It'll take you longer to get your degree, but it's much cheaper and you'll probably learn more than just the basics of each language.
For me, I kind of wish I had gone the community college route and saved myself some money, but it's kind of annoying to do that when not all of the classes I need are offered every semester. Sometimes they rarely offer them at all. With Coleman, you don't really have to worry about stuff like that because they're required to provide the classes that you need, at least for the core program. Really though, Coleman is only worth all the money if you just want something fast-paced and are a quick learner. The teachers there are excellent - always willing to help you out no matter what, at least the teachers that I had.
If all you want is a Computer Science degree and don't care how long it takes you to get it, a community college would be your best option. It's a lot more affordable and your credits would transfer anywhere if you'd want to get a bachelor's degree at any other school. If you go to Coleman, you can only transfer your credits to other ACICS accredited schools. So if you go to Coleman, you're stuck with having to complete your Bachelors and Masters Degrees with them too... which would cost you even more $$$.
That's it for my review of the CIS program. I hope I've helped someone in making a decision. I might go into some non-CIS related stuff in the future, but that's all I have to say (for now) about their CIS program.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Thursday, April 26, 2007
A review of Coleman College's / Coleman University's CIS program, part 6
7/6/09 UPDATE: Coleman College is now known as Coleman University - this review was written for their classes that I took in 2005-2006, so some things in their curriculum may have changed since then.
Here we go with part 6 of my sort of review, but not really much of a review.
The classes I had for mod 6 were C++ and UML. It is so disappointing when there are things you really want to learn, but when you finally have the classes, you don't learn that much from them. That's how I felt about C++. I really wanted to learn the ins and outs of C++, but I learned barely anything new (since most of the concepts were similar to Java), yet I still got a 100 since it was so easy. The MFC applications we made were interesting, but again not really much of a "real world" type of application. Well, at least it wasn't more yo-yos and fireworks.
My class was also grouped together with students who were in mod 4 & 5, so our class was huge. And it kind of hindered our progress when not everybody understood the material as well because, for the people who were only in mod 4, it was their first object oriented programming class. I found myself being asked for help a lot in this class by other students (a lot more than in previous mods). People knew that I knew what I was doing and could help them out. So I did get a bit of debugging experience with trying to find the problems in other people's codes.
Okay, so the afternoon class... I don't know the official name of the class, but we learned UML. Zzzzzz. Barely anybody could stay awake for this class. It was just nothing that any of us were interested in. We all would just rather be writing programs than diagraming them.
I understand the importance of modeling a system before you go ahead and get to work on it. The beginning phases of a project are the most important part of the systems development life cycle. Because if you don't spot your errors early on, it costs more and more the later you get in the development cycle to fix them. Stuff like UML helps you to see how your system will work, and if the systems analysis phase missed any sort of requirements. But UML is just so boring when you'd rather be coding. But this class is helpful in helping you understand how to read UML diagrams.
So, this mod was just... meh. I really wished I could have learned a lot more C++ instead of spending most of my time looking through other people's code to fix it. And UML... eh, maybe that should be combined with part of the capstone or should be left as an elective. I'll get into the capstone in part 7.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Here we go with part 6 of my sort of review, but not really much of a review.
The classes I had for mod 6 were C++ and UML. It is so disappointing when there are things you really want to learn, but when you finally have the classes, you don't learn that much from them. That's how I felt about C++. I really wanted to learn the ins and outs of C++, but I learned barely anything new (since most of the concepts were similar to Java), yet I still got a 100 since it was so easy. The MFC applications we made were interesting, but again not really much of a "real world" type of application. Well, at least it wasn't more yo-yos and fireworks.
My class was also grouped together with students who were in mod 4 & 5, so our class was huge. And it kind of hindered our progress when not everybody understood the material as well because, for the people who were only in mod 4, it was their first object oriented programming class. I found myself being asked for help a lot in this class by other students (a lot more than in previous mods). People knew that I knew what I was doing and could help them out. So I did get a bit of debugging experience with trying to find the problems in other people's codes.
Okay, so the afternoon class... I don't know the official name of the class, but we learned UML. Zzzzzz. Barely anybody could stay awake for this class. It was just nothing that any of us were interested in. We all would just rather be writing programs than diagraming them.
I understand the importance of modeling a system before you go ahead and get to work on it. The beginning phases of a project are the most important part of the systems development life cycle. Because if you don't spot your errors early on, it costs more and more the later you get in the development cycle to fix them. Stuff like UML helps you to see how your system will work, and if the systems analysis phase missed any sort of requirements. But UML is just so boring when you'd rather be coding. But this class is helpful in helping you understand how to read UML diagrams.
So, this mod was just... meh. I really wished I could have learned a lot more C++ instead of spending most of my time looking through other people's code to fix it. And UML... eh, maybe that should be combined with part of the capstone or should be left as an elective. I'll get into the capstone in part 7.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Monday, April 23, 2007
A review of Coleman College's / Coleman University's CIS program, part 5
7/6/09 UPDATE: Coleman College is now known as Coleman University - this review was written for their classes that I took in 2005-2006, so some things in their curriculum may have changed since then.
So I've covered mods 1 through 4 of Coleman College's core Computer Information Systems program.
Mod 5 for me was Software Testing and Visual Basic 1. I'm not sure if those are the actual names of the courses in the Coleman College catalog, but that's what we covered. Software testing wasn't really anything exciting - we learned the terminology like black box vs white box, different ways and methods of testing (load testing, acceptance testing, equivalence partitioning, etc.) and thinking (having the right mindset to go about testing and debugging a problem), and just the fact that it's impossible to test everything, bugs follow bugs (where you find one, you'll probably find another related to it), etc. Just a lot of conceptual stuff.
The reason they do Software Testing and VB in the same mod is because the application that you develop in VB (.NET) is (crap, I can't remember the specific terminology they used for it) a GUI application where your user can do things (click on the wrong things, etc) that you wouldn't normally expect them to do. I don't really know why software testing was the 8 unit class this mod when we spent more time in VB.
So in VB1, we made an application that would store customer information into a text file (later on in VB2, it would get more in-depth and use a database). We started off small, not saving any information, just being able to enter it, update it, and delete it. And then we would go around and try to break each other's programs to see how much we learned in software testing.
VB is really easy to learn, but can be used for complex applications. Overall, this was a very easy mod. I really loved all of the lab time that we got to work on our VB applications. The less lecture, the more hands on the better - I learn a lot better that way.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
So I've covered mods 1 through 4 of Coleman College's core Computer Information Systems program.
Mod 5 for me was Software Testing and Visual Basic 1. I'm not sure if those are the actual names of the courses in the Coleman College catalog, but that's what we covered. Software testing wasn't really anything exciting - we learned the terminology like black box vs white box, different ways and methods of testing (load testing, acceptance testing, equivalence partitioning, etc.) and thinking (having the right mindset to go about testing and debugging a problem), and just the fact that it's impossible to test everything, bugs follow bugs (where you find one, you'll probably find another related to it), etc. Just a lot of conceptual stuff.
The reason they do Software Testing and VB in the same mod is because the application that you develop in VB (.NET) is (crap, I can't remember the specific terminology they used for it) a GUI application where your user can do things (click on the wrong things, etc) that you wouldn't normally expect them to do. I don't really know why software testing was the 8 unit class this mod when we spent more time in VB.
So in VB1, we made an application that would store customer information into a text file (later on in VB2, it would get more in-depth and use a database). We started off small, not saving any information, just being able to enter it, update it, and delete it. And then we would go around and try to break each other's programs to see how much we learned in software testing.
VB is really easy to learn, but can be used for complex applications. Overall, this was a very easy mod. I really loved all of the lab time that we got to work on our VB applications. The less lecture, the more hands on the better - I learn a lot better that way.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Friday, April 20, 2007
A review of Coleman College's / Coleman University's CIS program, part 4
7/6/09 UPDATE: Coleman College is now known as Coleman University - this review was written for their classes that I took in 2005-2006, so some things in their curriculum may have changed since then.
This is the mod where the programmers and the networkers branched off into their separate classes. We wouldn't be in the same class again until our final mod, mod 7.
Mod 4, for me, was Java and Oracle. Java was my first look into object oriented programming. They used a great book for this class and I really learned a lot from it by doing the exercises as I read through the book. I can't remember what the book is right now, but I can try to go back through my manual for this mod to see if it's listed in there.
One nice thing about Coleman College's core program is that they provide you with the books - you don't get to keep them, just check them out during the mod. But after the core program, you have to buy your own books. So during the core, you don't have to spend any money on textbooks at all. Which is great since you don't have to deal with going to the bookstore, getting the right books, and whether or not you'll be able to sell them back at the end of the class.
Anyway, Java... I learned a great deal about classes, objects, polymorphism, inheritance, swing, awt, Graphics classes, interfaces, threads, applets, exception handling, using Java with HTML, and oh my gawd... API's (anyone who took this class with me will probably have the same hatred of doing the API assignments).
It was a great introduction to Java, but I wished that we had more real world types of assignments instead of making stupid yo-yo programs or fireworks.
I wish that I had started at Coleman two or three mods after when I did start. Those guys who came after me really got the kinds of projects that I wanted to have. Especially the people who started three mods after me. Their websites for their internet programming classes were awesome. They had someone from the graphics department teaching them the kind of advanced CSS that I wanted to learn. And when they got to Java, they weren't making fireworks or yo-yos.
There were some other useful applications that we made like the pizza ordering one where you'd pick your size and toppings and whatnot. But the fireworks and yo-yo projects were just silly. Sure, you learn about threads and animation, but the apps themselves were pointless.
The 4 unit class for this mod was Oracle. For a 4 unit class, it seemed a hell of a lot more like it was 8 units. The work was way more than any other 4 unit class I took at Coleman. We learned PL/SQL, working with Oracle forms, triggers, stored procedures, exception handling, the LOV wizard, transferring data from form to form, what a boilerplate is, and a whole lot more.
The projects for Oracle were sweet - this was the kind of stuff I wanted. An application that uses some sort of GUI. Not just some console application with plain text. Seeing the finished project after all the work you put into it was really gratifying, especially since sometimes Oracle can be a pain in the ass to work with.
That's mod 4. Stay tuned tomorrow for mod/part 5.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
This is the mod where the programmers and the networkers branched off into their separate classes. We wouldn't be in the same class again until our final mod, mod 7.
Mod 4, for me, was Java and Oracle. Java was my first look into object oriented programming. They used a great book for this class and I really learned a lot from it by doing the exercises as I read through the book. I can't remember what the book is right now, but I can try to go back through my manual for this mod to see if it's listed in there.
One nice thing about Coleman College's core program is that they provide you with the books - you don't get to keep them, just check them out during the mod. But after the core program, you have to buy your own books. So during the core, you don't have to spend any money on textbooks at all. Which is great since you don't have to deal with going to the bookstore, getting the right books, and whether or not you'll be able to sell them back at the end of the class.
Anyway, Java... I learned a great deal about classes, objects, polymorphism, inheritance, swing, awt, Graphics classes, interfaces, threads, applets, exception handling, using Java with HTML, and oh my gawd... API's (anyone who took this class with me will probably have the same hatred of doing the API assignments).
It was a great introduction to Java, but I wished that we had more real world types of assignments instead of making stupid yo-yo programs or fireworks.
I wish that I had started at Coleman two or three mods after when I did start. Those guys who came after me really got the kinds of projects that I wanted to have. Especially the people who started three mods after me. Their websites for their internet programming classes were awesome. They had someone from the graphics department teaching them the kind of advanced CSS that I wanted to learn. And when they got to Java, they weren't making fireworks or yo-yos.
There were some other useful applications that we made like the pizza ordering one where you'd pick your size and toppings and whatnot. But the fireworks and yo-yo projects were just silly. Sure, you learn about threads and animation, but the apps themselves were pointless.
The 4 unit class for this mod was Oracle. For a 4 unit class, it seemed a hell of a lot more like it was 8 units. The work was way more than any other 4 unit class I took at Coleman. We learned PL/SQL, working with Oracle forms, triggers, stored procedures, exception handling, the LOV wizard, transferring data from form to form, what a boilerplate is, and a whole lot more.
The projects for Oracle were sweet - this was the kind of stuff I wanted. An application that uses some sort of GUI. Not just some console application with plain text. Seeing the finished project after all the work you put into it was really gratifying, especially since sometimes Oracle can be a pain in the ass to work with.
That's mod 4. Stay tuned tomorrow for mod/part 5.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Thursday, April 19, 2007
A review of Coleman College's / Coleman University's CIS program, part 3
7/6/09 UPDATE: Coleman College is now known as Coleman University - this review was written for their classes that I took in 2005-2006, so some things in their curriculum may have changed since then.
I covered what mod 2 of Coleman's core CIS program yesterday. Today, I'll delve into mod 3.
Mod 3 was UNIX and Operating Systems Installations
UNIX - this class was very similar to learning DOS commands. My original class was now grouped with the class that was one mod behind us. We learned how to use edit and the Vi editor. We also learned some shell scripting, using the magic number line. How to send mail and a whole bunch of other stuff that I really can't remember right now. Shows how much I really retained it, huh?
OS Installs - this class was mostly a bunch of labs installing various operating systems from DOS, Windows 98, NT, 2000, XP, and Fedora. And the instructor would also teach us some Windows maintenance stuff... like going to My Computer > Manage and doing a defrag and whatnot. And installing anti-virus and anti-spyware software. How to use Windows Update. Whoopdie-doo... big deal.
Overall, this was the most boring mod ever. Who needs to learn how to install outdated operating systems? Oh, and the computers in the install lab were absolute crap... soooo damn slow. For a school where you're supposed to learn about the latest in computer technology, you'd think they'd have better computers... especially with all of the money you're paying them to go there.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
I covered what mod 2 of Coleman's core CIS program yesterday. Today, I'll delve into mod 3.
Mod 3 was UNIX and Operating Systems Installations
UNIX - this class was very similar to learning DOS commands. My original class was now grouped with the class that was one mod behind us. We learned how to use edit and the Vi editor. We also learned some shell scripting, using the magic number line. How to send mail and a whole bunch of other stuff that I really can't remember right now. Shows how much I really retained it, huh?
OS Installs - this class was mostly a bunch of labs installing various operating systems from DOS, Windows 98, NT, 2000, XP, and Fedora. And the instructor would also teach us some Windows maintenance stuff... like going to My Computer > Manage and doing a defrag and whatnot. And installing anti-virus and anti-spyware software. How to use Windows Update. Whoopdie-doo... big deal.
Overall, this was the most boring mod ever. Who needs to learn how to install outdated operating systems? Oh, and the computers in the install lab were absolute crap... soooo damn slow. For a school where you're supposed to learn about the latest in computer technology, you'd think they'd have better computers... especially with all of the money you're paying them to go there.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Wednesday, April 18, 2007
A review of Coleman College's / Coleman University's CIS program, part 2
7/6/09 UPDATE: Coleman College is now known as Coleman University - this review was written for their classes that I took in 2005-2006, so some things in their curriculum may have changed since then.
Yesterday, I covered mod 1 of Coleman College's core program in Computer Information Systems. Today, I'll be giving a few details about mod 2, or at least what I took during mod 2 (they often mix mods around because they don't have enough teachers or classrooms - so you'll be grouped with students that need the current class you're taking, but may be a mod ahead or behind you).
My mod 2 consisted of Internet Programming and SQL. Before I get into that, what I didn't mention before was that for day classes (which is what I took), mods last for 5 weeks - 7 hours a day, Monday through Friday.
Ah, Internet Programming, I was really looking forward to this class because I've always wanted to learn PHP and MySQL in-depth. I sure was disappointed. Why? Because we mostly spent our time learning HTML. For someone who already knew HTML, this was such a drag for me that I had to start back with the basics of HTML. Booooooooorrrrring! HTML isn't even programming! So we focused on nothing but that for about 3 weeks of the mod. But I guess that's the beauty of Coleman if you know absolutely nothing about computers, then you'll definitely learn a lot here.
Then after HTML, we learned a little bit of CSS. I really wish we could've gone more in-depth with that, but it was really just a basic overview. What I'd like to see is using CSS for layouts (more than what the tutorial covered), menus, curved text, using styles for web and print, etc. After CSS, we spent a little bit of time with JavaScript, just using it for form validation - that was the main thing we used JavaScript for, so we didn't really get into anything more you can do with it. Then came PHP... woohoo! But what a letdown. All we did here was just a really simple shopping cart - I'm talking about this cart with only 5 products and you'd pick how many you want, it would calculate your totals and the JavaScript would validate your info. It didn't even e-mail the order to anywhere or put it in a database, it just gave the user their total saying their submission was a success.
During our last few weeks, we got to use Dreamweaver to make our pages. That was even more boring than learning HTML. As much as I like Dreamweaver (even though I still prefer writing my HTML manually), I've already learned it before! I took a class on it a few years before learning it again at Coleman. For me, if I'm not learning at least one new thing, having to relearn things sucks! But I had to do it because it's part of the curriculum and I had to turn in all of my assignments to get my easy A - you can't challenge or waive any classes (like you can at other schools if you can show competency in the subject) because you need to take all of the core requirements in order to get the degree. I think this is all part of how Coleman makes its money, by making you waste your time in classes even if you already know the shit backwards and forwards.
So, the other class in this mod was SQL. Since I knew very little SQL to begin with, this class was great for me; I was learning something new and very useful to know in programming since a lot of programs will often interact with a database. The teacher made it seem like the concepts were going to be extremely difficult, she kept saying how much project 2 would be "a killer" and after we did it, me and the rest of the people in my class just all looked at each other and asked, "What was so hard about that?" Again, we must have all been very bright individuals. I don't think either one of us ever got less than an A in anything the entire time we were at Coleman. Me and one of the guys who started at the same time as me both graduated with a 4.0. So that's either saying Coleman is way easy or their screening process really works. I never mentioned it before, but you have to take a math/logic test to get into Coleman - I think you get two chances to take it and if you don't pass the second time, you're not admitted. The test itself is really easy though, at least I thought it was.
So in SQL we learned stuff like: normalization, creating tables, adding data, deleting tables or individual records, writing queries to get information from tables, joining tables, views, using functions like date, max, min, count, sum. Lots of stuff I learned here. We also learned a little bit of using PHP with MySQL which was pretty cool to use a web app to update a database. I wish they would've tied both classes together a bit more. Like have us make a database in our SQL class and a website in our Internet Programming class that would interact with our database. Maybe they've improved it by now, but I kind of doubt it.
As usual, tests for both classes were on Papa Bear. Extremely easy tests.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Yesterday, I covered mod 1 of Coleman College's core program in Computer Information Systems. Today, I'll be giving a few details about mod 2, or at least what I took during mod 2 (they often mix mods around because they don't have enough teachers or classrooms - so you'll be grouped with students that need the current class you're taking, but may be a mod ahead or behind you).
My mod 2 consisted of Internet Programming and SQL. Before I get into that, what I didn't mention before was that for day classes (which is what I took), mods last for 5 weeks - 7 hours a day, Monday through Friday.
Ah, Internet Programming, I was really looking forward to this class because I've always wanted to learn PHP and MySQL in-depth. I sure was disappointed. Why? Because we mostly spent our time learning HTML. For someone who already knew HTML, this was such a drag for me that I had to start back with the basics of HTML. Booooooooorrrrring! HTML isn't even programming! So we focused on nothing but that for about 3 weeks of the mod. But I guess that's the beauty of Coleman if you know absolutely nothing about computers, then you'll definitely learn a lot here.
Then after HTML, we learned a little bit of CSS. I really wish we could've gone more in-depth with that, but it was really just a basic overview. What I'd like to see is using CSS for layouts (more than what the tutorial covered), menus, curved text, using styles for web and print, etc. After CSS, we spent a little bit of time with JavaScript, just using it for form validation - that was the main thing we used JavaScript for, so we didn't really get into anything more you can do with it. Then came PHP... woohoo! But what a letdown. All we did here was just a really simple shopping cart - I'm talking about this cart with only 5 products and you'd pick how many you want, it would calculate your totals and the JavaScript would validate your info. It didn't even e-mail the order to anywhere or put it in a database, it just gave the user their total saying their submission was a success.
During our last few weeks, we got to use Dreamweaver to make our pages. That was even more boring than learning HTML. As much as I like Dreamweaver (even though I still prefer writing my HTML manually), I've already learned it before! I took a class on it a few years before learning it again at Coleman. For me, if I'm not learning at least one new thing, having to relearn things sucks! But I had to do it because it's part of the curriculum and I had to turn in all of my assignments to get my easy A - you can't challenge or waive any classes (like you can at other schools if you can show competency in the subject) because you need to take all of the core requirements in order to get the degree. I think this is all part of how Coleman makes its money, by making you waste your time in classes even if you already know the shit backwards and forwards.
So, the other class in this mod was SQL. Since I knew very little SQL to begin with, this class was great for me; I was learning something new and very useful to know in programming since a lot of programs will often interact with a database. The teacher made it seem like the concepts were going to be extremely difficult, she kept saying how much project 2 would be "a killer" and after we did it, me and the rest of the people in my class just all looked at each other and asked, "What was so hard about that?" Again, we must have all been very bright individuals. I don't think either one of us ever got less than an A in anything the entire time we were at Coleman. Me and one of the guys who started at the same time as me both graduated with a 4.0. So that's either saying Coleman is way easy or their screening process really works. I never mentioned it before, but you have to take a math/logic test to get into Coleman - I think you get two chances to take it and if you don't pass the second time, you're not admitted. The test itself is really easy though, at least I thought it was.
So in SQL we learned stuff like: normalization, creating tables, adding data, deleting tables or individual records, writing queries to get information from tables, joining tables, views, using functions like date, max, min, count, sum. Lots of stuff I learned here. We also learned a little bit of using PHP with MySQL which was pretty cool to use a web app to update a database. I wish they would've tied both classes together a bit more. Like have us make a database in our SQL class and a website in our Internet Programming class that would interact with our database. Maybe they've improved it by now, but I kind of doubt it.
As usual, tests for both classes were on Papa Bear. Extremely easy tests.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Tuesday, April 17, 2007
A review of Coleman College's / Coleman University's CIS program, part 1
2/4/13 UPDATE: I appreciate all of the comments from fellow alumni and prospective students. Hopefully they've helped someone who's trying to decide the best way to spend their money towards an education. I approve all non-spam comments (whether people say good things or bad things - I'm sure visitors who read them appreciate the honesty), but it sometimes takes me months to approve them because I don't use Blogger as much as I used to. So if you post a comment, please don't be offended if it doesn't show up right away.
========
7/6/09 UPDATE: Coleman College is now known as Coleman University - this review was written for their classes that I took in 2005-2006, so some things in their curriculum may have changed since then.
========
ORIGINAL POST:
If you live in San Diego county, you've probably seen the commercials for Coleman College... "the fast track to a career in computers" or something along those lines.
You might be wondering, is it worth it?
As a Coleman alumni, I'm here to give you my thoughts about it. Depending on what path you choose, you go through different core programs. Each core program consists of 7 modules or mods, with two classes per mod. One class is 4 units and the other class is 8 units, or you may even have 3 4 unit classes in one mod.
I first started off wanting to learn the Computer Networking side of things. Since the first three mods of the core program for both Networking and Programming are all the same classes, I got to experience the programming side and ended up switching my major to CIS after mod 3 (a lot of people at my campus ended up switching from Networking to Programming).
Mod 1 - Intro to Programming (using C), Intro to PCs and Networks
Intro to Programming gives an overview of how to program using the C language. Here you'll start off with learning pseudocode, proper C syntax, and then learn about variables, conditional statements, loops, arrays, multidimensional arrays, references, structures, etc. The programs you write are a simple calculator, then a more advanced calculator, a temperature conversion program, an interview program. I enjoyed this course a lot because my teacher was excellent at teaching the subject. You could tell that she really had a passion for programming in general and would do her best to help anyone understand it. She wouldn't give up on debugging anything, so you'd never be left on your own if you really needed help.
I don't know if it's just because the way my teacher taught it that made it seem easy or if it just really was easy, but it really didn't seem that hard at all. The other people in my class also thought it was pretty easy - maybe we were all just a smart group.
Intro to PCs and Networks was just that - an introduction. So if you already know a lot about how to use a computer, Windows, and Microsoft Office, then this will be a really boring class for you. They have this class because some people who go to Coleman have NEVER used a computer before. So that's why it's the way it is... and the instructor has to stick to the curriculum. He can't skip anything, even if the whole class already knows it. You learn all about computer hardware and how to put a PC together, the boot sequence, IRQs, DOS commands, Windows, Microsoft Office, and different types of networking. This class was just a big snooze fest for me and the other people in my class.
Before I move on to mod 2, let me take a moment to talk about tests. Tests are a complete joke. Sometimes there might be a written test, but 99% of the tests you take will be done on computer by logging into Coleman's "Papa Bear" system. Most of the questions are multiple choice, but some will be fill in the blank. You usually get two ungraded quizzes before taking a test and the quizzes will have the same questions as what's on the test. The quizzes are taken in groups, so that everybody has a chance to see more of the questions that are in the test pool. So all you really need to do to pass a test is memorize the answers that were on the quizzes. If you don't have a good memory or you weren't paying attention to anything in class, then you'll probably do bad at tests. Almost everybody does pretty well on tests... that's why they're such a joke.
I'll cover more of the mods in more parts of this review later.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
========
7/6/09 UPDATE: Coleman College is now known as Coleman University - this review was written for their classes that I took in 2005-2006, so some things in their curriculum may have changed since then.
========
ORIGINAL POST:
If you live in San Diego county, you've probably seen the commercials for Coleman College... "the fast track to a career in computers" or something along those lines.
You might be wondering, is it worth it?
As a Coleman alumni, I'm here to give you my thoughts about it. Depending on what path you choose, you go through different core programs. Each core program consists of 7 modules or mods, with two classes per mod. One class is 4 units and the other class is 8 units, or you may even have 3 4 unit classes in one mod.
I first started off wanting to learn the Computer Networking side of things. Since the first three mods of the core program for both Networking and Programming are all the same classes, I got to experience the programming side and ended up switching my major to CIS after mod 3 (a lot of people at my campus ended up switching from Networking to Programming).
Mod 1 - Intro to Programming (using C), Intro to PCs and Networks
Intro to Programming gives an overview of how to program using the C language. Here you'll start off with learning pseudocode, proper C syntax, and then learn about variables, conditional statements, loops, arrays, multidimensional arrays, references, structures, etc. The programs you write are a simple calculator, then a more advanced calculator, a temperature conversion program, an interview program. I enjoyed this course a lot because my teacher was excellent at teaching the subject. You could tell that she really had a passion for programming in general and would do her best to help anyone understand it. She wouldn't give up on debugging anything, so you'd never be left on your own if you really needed help.
I don't know if it's just because the way my teacher taught it that made it seem easy or if it just really was easy, but it really didn't seem that hard at all. The other people in my class also thought it was pretty easy - maybe we were all just a smart group.
Intro to PCs and Networks was just that - an introduction. So if you already know a lot about how to use a computer, Windows, and Microsoft Office, then this will be a really boring class for you. They have this class because some people who go to Coleman have NEVER used a computer before. So that's why it's the way it is... and the instructor has to stick to the curriculum. He can't skip anything, even if the whole class already knows it. You learn all about computer hardware and how to put a PC together, the boot sequence, IRQs, DOS commands, Windows, Microsoft Office, and different types of networking. This class was just a big snooze fest for me and the other people in my class.
Before I move on to mod 2, let me take a moment to talk about tests. Tests are a complete joke. Sometimes there might be a written test, but 99% of the tests you take will be done on computer by logging into Coleman's "Papa Bear" system. Most of the questions are multiple choice, but some will be fill in the blank. You usually get two ungraded quizzes before taking a test and the quizzes will have the same questions as what's on the test. The quizzes are taken in groups, so that everybody has a chance to see more of the questions that are in the test pool. So all you really need to do to pass a test is memorize the answers that were on the quizzes. If you don't have a good memory or you weren't paying attention to anything in class, then you'll probably do bad at tests. Almost everybody does pretty well on tests... that's why they're such a joke.
I'll cover more of the mods in more parts of this review later.
Here are the links to all of the parts: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, more thoughts
Subscribe to:
Posts (Atom)