Visual Basic is a fun little programming environment/language. It's good for creating quick prototypes or making a simple interface to perform repetitive tasks in a Windows environment. I'm sure you could do big, fancy stuff in VB, but generally you'd use a more powerful language for big projects that need to be optimized or run in cross-platform environments. Something that is neat about it is that it's the language used to write macros in MS Office. So if you have a great reason to use a macro, you'll want to know a little VB. Please don't use macros if you have anything less than a great reason.
Given the quick and dirty nature of it, it's no surprise that it's the language taught to business students who need to understand a bit of programming but don't need to be able to create their own compiler or operating system. One thing I liked about this course was that of all the programming courses I've taken, it was one of the few actually taught by faculty in my department. I worked in the Computer Science department for 5 years and don't have anything against CS faculty at all, but there's a greater connection having someone from your own department teaching a course.
As a case in point, look at this particular course. When I took it, it was the last semester that just one undergraduate version of the course was taught. The whole semester, the professor who taught it would bag on accounting students or other non-MIS business majors who didn't know anything about computers or programming. They were in the same section as the students with more technical majors, because there wasn't another option. All we heard about was how the professor wanted to move on to all these advanced concepts but couldn't because of the accounting students holding us back. This, of course, was the same thing I heard as an MIS student in CS classes, how we weren't real programmers like the CS students. So CS bags on MIS; MIS bags on accounting; maybe accounting bags on human resources or marketing? At least marketers have a handle on social media, so it's probably HR that's the bottom of the technology food chain.
However the pecking order goes, the next semester would see two versions of the course, for technical and non-technical business majors. I don't know how much they lightened the load in the non-technical version, since VB is already a junior version of programming.
For an example of a quick program I wrote in VB several years later, I created a small program to automate common tasks in the testing center I used to run. I created a map of the lab with a button for each computer and for common actions. You would select the computer and then click the button for the action you wanted to perform: view the screen, reboot it, shut it down, turn it on, or mark that it was being used to take a certain test. It even had an option to cancel the shut down command if you accidentally selected the wrong computer and realized it within 5 seconds. Students get freaked out for some reason when their computer shuts down on them in the middle of a test. The funnest options were to start up or shut down all the computers at the same time. It was like a race to see which computer would boot up first, and the silence when all the fans came to a stop was so peaceful.
The program was pretty simple and was very inelegantly written but saved a ton of time for those working the lab. An employee of mine sought to improve on my design and write a fancy version 2.0 with all kinds of customization options to work in other computer labs, but quick and dirty won the race. As long as he worked on it, he never got version 2.0 working.
Friday, January 6, 2012
Friday, December 23, 2011
Database Management
I really enjoyed this course. It was a good foundation of database skills, which I have used in multiple jobs. It was also fundamentally well designed, building from basic terminology to practicing part tasks to a final project of our own choosing. I would throw out there the random made-up statistic that half the spreadsheets that exist in the world would be much simpler if created as a database instead. I wish everyone could take this class.
We started out learning the basics of databases. What's a table, row, query, DBMS, join, etc.? Unlike the class I had taken where I should have learned some of these introductory concepts, it was actually clear this time around how they would be used.
We progressed from basic concepts to writing simple queries to create tables, load data into them, and query their contents. From there we got into various types of joins and the dreaded subquery. We did some relatively complex things, but nothing too out of control. For our tests, we could bring a single page cheat sheet (that I still have a copy of) with whatever example SQL syntax we wanted to include. So like you might have reference material in a real world situation, we could have some to remind us of the basics, but you still had to be able to understand the examples well enough to modify them so they would do what you had to do quickly on the test. Of course, as Mike Seaver learned in the classic Growing Pains episode, you learn the material better by making the cheat sheet in the first place. (Just don't let your teacher see the bottom of your shoe if it's not allowed and that's where you wrote it.)
We had plenty of time in class to practice our new SQL skills on our own and in groups, learning from mistakes and celebrating successes. Ultimately the course built up to a culminating project. It had to have a database of some kind involved, obviously. Other than that, it was up to us to determine what we would implement based on the other technical skills we had. I don't remember what my project was other than I worked like crazy on it, and it ended up close but never functioned quite right. Thinking back on it, I doubt the professor spent much time actually using our final projects and checking in depth how well they worked, as long as our documentation was in order and it looked like we had done something big enough, but it was motivating to be able to choose our own project and figure out how to make it work.
We started out learning the basics of databases. What's a table, row, query, DBMS, join, etc.? Unlike the class I had taken where I should have learned some of these introductory concepts, it was actually clear this time around how they would be used.
We progressed from basic concepts to writing simple queries to create tables, load data into them, and query their contents. From there we got into various types of joins and the dreaded subquery. We did some relatively complex things, but nothing too out of control. For our tests, we could bring a single page cheat sheet (that I still have a copy of) with whatever example SQL syntax we wanted to include. So like you might have reference material in a real world situation, we could have some to remind us of the basics, but you still had to be able to understand the examples well enough to modify them so they would do what you had to do quickly on the test. Of course, as Mike Seaver learned in the classic Growing Pains episode, you learn the material better by making the cheat sheet in the first place. (Just don't let your teacher see the bottom of your shoe if it's not allowed and that's where you wrote it.)We had plenty of time in class to practice our new SQL skills on our own and in groups, learning from mistakes and celebrating successes. Ultimately the course built up to a culminating project. It had to have a database of some kind involved, obviously. Other than that, it was up to us to determine what we would implement based on the other technical skills we had. I don't remember what my project was other than I worked like crazy on it, and it ended up close but never functioned quite right. Thinking back on it, I doubt the professor spent much time actually using our final projects and checking in depth how well they worked, as long as our documentation was in order and it looked like we had done something big enough, but it was motivating to be able to choose our own project and figure out how to make it work.
Tuesday, November 22, 2011
Meta Blogging
In September, I started a series of blog posts on college courses that I've taken. I wrote a post every day and got through about four or five semesters' worth, depending on how you count it (one year was quarters, plus some AP classes from high school). I haven't stopped but have slowed way down. Between not wanting so spam my (3) loyal readers and not having the time to keep up a post a day, I couldn't maintain that kind of production.
I don't know how the NaNoWriMo people do it. Well, I do know that of the hundreds of thousands of people who sign up, the average number of words written per person is just under 15,000. They're supposed to write 50,000. About one in five finish, which means about two in three write nothing.
I did write a post for every day that one month, which is something I wanted to try, and I have kept up my streak of at least one post a month for the past four years. Interestingly enough, I pulled in a little over 15,000 words in September, which means I beat a lot of NaNoWriMo people.
Something else I have let slip is my RSS reader. I had close to a thousand unread posts in there from all around the web. I unsubscribed from the feeds for a MOOC I stopped participating in, which dropped a few hundred unread posts off. I marked the posts from the You Are Not a Photographer blog, because everything is in there twice and they keep doing weird things with their feed that makes old stuff I've already read show up as unread again. I may end up just unsubscribing, since it looks like they stopped including the picture in their RSS feed, so you have to actually visit the site to make fun of how bad people are at photography. I've been considering unsubscribing from the Freakonomics blog for awhile now, but every once in awhile a post comes along that makes it all worth it.
I finally unsubscribed from Larry Ferlazzo's blog. I'm sorry, Larry. I tried to keep up. I really did. I subscribed when I found several interesting posts related to Bloom's Taxonomy, which I was reading about at the time. Seven posts a day is too much for me, especially if I get a couple days behind. To give you an idea of the volume here, he has well over 500 "most popular" posts. I have no idea how many unpopular posts he has. I was going to maybe suggest that he try Twitter, since his blog posts are mainly lists of interesting site related to teaching a given topic, and Twitter is great at sending out links to people. Of course, I should have known; he's got more than 30,000 tweets. That means that over 3 years on Twitter, he averages 27 tweets a day. Given an average of about 12 words per tweet, that's almost 10,000 words per month, so he's not much off the NaNoWriMo average and doing better than most would-be authors just on Twitter.
One thing I do need to do is go back and fix the pictures in my September posts. I didn't add a picture to every post, but for the ones that I did, I got lazy. I just randomly googled images and grabbed stuff wherever I found it. Normally I use photos licensed with Creative Commons on Flickr. When I use their photo, I will link back to their Flickr stream and leave a comment on the photo I used with my thanks for their sharing and a link to the post where I used it. The bus up there is just a random openly licensed photo I found that kind of popped out at me. Thanks for sharing but not sharing too much.
photo by didbygraham
I don't know how the NaNoWriMo people do it. Well, I do know that of the hundreds of thousands of people who sign up, the average number of words written per person is just under 15,000. They're supposed to write 50,000. About one in five finish, which means about two in three write nothing.
I did write a post for every day that one month, which is something I wanted to try, and I have kept up my streak of at least one post a month for the past four years. Interestingly enough, I pulled in a little over 15,000 words in September, which means I beat a lot of NaNoWriMo people.
Something else I have let slip is my RSS reader. I had close to a thousand unread posts in there from all around the web. I unsubscribed from the feeds for a MOOC I stopped participating in, which dropped a few hundred unread posts off. I marked the posts from the You Are Not a Photographer blog, because everything is in there twice and they keep doing weird things with their feed that makes old stuff I've already read show up as unread again. I may end up just unsubscribing, since it looks like they stopped including the picture in their RSS feed, so you have to actually visit the site to make fun of how bad people are at photography. I've been considering unsubscribing from the Freakonomics blog for awhile now, but every once in awhile a post comes along that makes it all worth it.
I finally unsubscribed from Larry Ferlazzo's blog. I'm sorry, Larry. I tried to keep up. I really did. I subscribed when I found several interesting posts related to Bloom's Taxonomy, which I was reading about at the time. Seven posts a day is too much for me, especially if I get a couple days behind. To give you an idea of the volume here, he has well over 500 "most popular" posts. I have no idea how many unpopular posts he has. I was going to maybe suggest that he try Twitter, since his blog posts are mainly lists of interesting site related to teaching a given topic, and Twitter is great at sending out links to people. Of course, I should have known; he's got more than 30,000 tweets. That means that over 3 years on Twitter, he averages 27 tweets a day. Given an average of about 12 words per tweet, that's almost 10,000 words per month, so he's not much off the NaNoWriMo average and doing better than most would-be authors just on Twitter.
One thing I do need to do is go back and fix the pictures in my September posts. I didn't add a picture to every post, but for the ones that I did, I got lazy. I just randomly googled images and grabbed stuff wherever I found it. Normally I use photos licensed with Creative Commons on Flickr. When I use their photo, I will link back to their Flickr stream and leave a comment on the photo I used with my thanks for their sharing and a link to the post where I used it. The bus up there is just a random openly licensed photo I found that kind of popped out at me. Thanks for sharing but not sharing too much.Friday, November 4, 2011
Business Communication
Business Communication was a great class. I enjoyed it and still use things I learned in it. One great thing about it was that it was a night class taught once a week. I like the extended time less often, because it seems that you can get into deeper conversations given the extra time. I like night classes a lot more than early a.m. classes, since I'd rather stay up late than get up early.
The content of the course was useful. We learned a ton of grammar, which I really appreciated. My spelling and grammar have always been pretty good anyway, but there were things I learned in this class that I had never grasped before. I do purposely break certain rules for various reasons, but it always is for a reason when I do. I do occasionally start a sentence with "And" but almost exclusively on my blog and only for added emphasis. The unfortunate thing about this class is that they have since removed the grammar component. Given my AP and ACT scores, I'd have qualified to skip the grammar pretest and never had to learn any of the rules that I actually appreciate having learned in this class.
A couple examples:
When using conjunctions such as and, because, but, and or, you only put a comma before the conjunction if what follows the conjunction could stand alone as a complete sentence. I raked the leaves and emptied all the garbage cans. No comma since "emptied all the garbage cans" is not a complete sentence. I had previously always used a comma before a conjunction.
You can tack two complete, related sentences together with a semicolon and no conjunction. I will pick up dinner at Pizza Pie Cafe on my way home; they are having a sweet sale right now.
Something I'll always remember about this class was the overhead slides. No, the weird part isn't that the professor used overhead slides instead of computer-based slides, although that was a little strange, too. This was and is one of my favorite professors of all time but for whatever reason had a strange method for displaying the overheads: lay slide on overhead, turn on overhead, talk about slide, turn off overhead, lay slide on overhead, turn on overhead, etc. The overhead projector was turned on and off for every single slide. I remember joking with my classmates that any electricity savings from the two seconds it was turned off while picking up the next transparency off the pile would surely be lost by having the replace the worn out power switch before its time.
I also recall that the final paper for this class had to be cancelled. It was supposed to be a research paper, which we'd write with all our new-found communication skills. The problem was that when you do research, you have to get IRB approval, even if it's a simple survey to ask people about their parking behaviors, which ours was. IRB approval usually takes months, and while there are provisions for blanket IRB approval for class-based research projects in certain situations, it was too late for that process as well. Being the go-getters that we were (and since I was writing a paper about the same topic in my English class the same semester), we already had our research collected by the time the sad news was delivered. We ended up writing and turning in our paper anyway for extra credit. The extra credit should have been reversed, since we threw a bunch of screen beans into it, and that flies in the face of any kind of professional communication which we had been learning about. It's too bad I couldn't have taken some of that extra credit and applied it to the grade in my English class, for which I was using some of the same content.
The content of the course was useful. We learned a ton of grammar, which I really appreciated. My spelling and grammar have always been pretty good anyway, but there were things I learned in this class that I had never grasped before. I do purposely break certain rules for various reasons, but it always is for a reason when I do. I do occasionally start a sentence with "And" but almost exclusively on my blog and only for added emphasis. The unfortunate thing about this class is that they have since removed the grammar component. Given my AP and ACT scores, I'd have qualified to skip the grammar pretest and never had to learn any of the rules that I actually appreciate having learned in this class.
A couple examples:
When using conjunctions such as and, because, but, and or, you only put a comma before the conjunction if what follows the conjunction could stand alone as a complete sentence. I raked the leaves and emptied all the garbage cans. No comma since "emptied all the garbage cans" is not a complete sentence. I had previously always used a comma before a conjunction.
You can tack two complete, related sentences together with a semicolon and no conjunction. I will pick up dinner at Pizza Pie Cafe on my way home; they are having a sweet sale right now.
Something I'll always remember about this class was the overhead slides. No, the weird part isn't that the professor used overhead slides instead of computer-based slides, although that was a little strange, too. This was and is one of my favorite professors of all time but for whatever reason had a strange method for displaying the overheads: lay slide on overhead, turn on overhead, talk about slide, turn off overhead, lay slide on overhead, turn on overhead, etc. The overhead projector was turned on and off for every single slide. I remember joking with my classmates that any electricity savings from the two seconds it was turned off while picking up the next transparency off the pile would surely be lost by having the replace the worn out power switch before its time.
I also recall that the final paper for this class had to be cancelled. It was supposed to be a research paper, which we'd write with all our new-found communication skills. The problem was that when you do research, you have to get IRB approval, even if it's a simple survey to ask people about their parking behaviors, which ours was. IRB approval usually takes months, and while there are provisions for blanket IRB approval for class-based research projects in certain situations, it was too late for that process as well. Being the go-getters that we were (and since I was writing a paper about the same topic in my English class the same semester), we already had our research collected by the time the sad news was delivered. We ended up writing and turning in our paper anyway for extra credit. The extra credit should have been reversed, since we threw a bunch of screen beans into it, and that flies in the face of any kind of professional communication which we had been learning about. It's too bad I couldn't have taken some of that extra credit and applied it to the grade in my English class, for which I was using some of the same content.
Friday, October 7, 2011
Microeconomics
A strange turn in this class I took was that I had one professor for the first half of the semester and another for the second half of the semester. The first professor delivered a baby halfway through, so they assigned someone else to teach after her baby was born. C'est la vie.
While Macroeconomics is more about a top-down look at the economies of countries across the world, Microeconomics is about the choices of individual companies and people. They are highly related, since government tariffs and quotas obviously affect the motivation of individuals to produce or cut production of affected products.
For example, Haiti used to be a rice-exporting nation. It was their main product. Their people have always been poor due to the policies of foreign governments, corruption of their own government, and frequent natural disasters. But they always had rice. At a macroeconomic level, you could look at the amount of rice they sold to other countries and the policies of various governments that facilitated that. In the 1980s, cheap (or sometimes even free) rice from the U.S., AKA Miami rice, flooded our island neighbor to the point where it was no longer profitable to grow rice. Macroeconomic conditions led to the overabundance of Miami rice. Microeconomic principles led to individual farmers halting production of Haitian rice.
An interesting topic they talk about in Microeconomics is one of monopolies. A monopoly, of course, is a situation where one company controls the supply of a particular product or service to the point that they can engage in unfair practices. They are often highly regulated to avoid problems. Or even more drastic action may be taken as was the case when our phone system a few decades back was split up into several smaller regional carriers.
Interestingly enough, the way the phone systems have evolved over the years since, several of those Baby Bells combined back together, and with the market changes due to mobile phones, we actually find a small number of companies controlling the market. They compete, yes, but to some extent they collude to keep prices high. Take text messaging, for example, which is disturbingly expensive relative to the actual costs. It actually costs more to track and bill text message usage than it does to deliver the messages, so when you pay for texting, you're really paying for them to bill you for texting, not for the delivery of the actual messages. This type of situation is called an oligopoly. Verizon, Sprint, AT&T, and T-Mobile can't make any huge moves to totally disrupt the market because of the market share of the other companies, but they don't want to either, because they're all sitting pretty if they can maintain the status quo. The potential buyout of T-Mobile by AT&T would actually serve to start tipping the monopoly scale if approved by regulators, so I don't think it's likely.
While Macroeconomics is more about a top-down look at the economies of countries across the world, Microeconomics is about the choices of individual companies and people. They are highly related, since government tariffs and quotas obviously affect the motivation of individuals to produce or cut production of affected products.
For example, Haiti used to be a rice-exporting nation. It was their main product. Their people have always been poor due to the policies of foreign governments, corruption of their own government, and frequent natural disasters. But they always had rice. At a macroeconomic level, you could look at the amount of rice they sold to other countries and the policies of various governments that facilitated that. In the 1980s, cheap (or sometimes even free) rice from the U.S., AKA Miami rice, flooded our island neighbor to the point where it was no longer profitable to grow rice. Macroeconomic conditions led to the overabundance of Miami rice. Microeconomic principles led to individual farmers halting production of Haitian rice.
An interesting topic they talk about in Microeconomics is one of monopolies. A monopoly, of course, is a situation where one company controls the supply of a particular product or service to the point that they can engage in unfair practices. They are often highly regulated to avoid problems. Or even more drastic action may be taken as was the case when our phone system a few decades back was split up into several smaller regional carriers.
Interestingly enough, the way the phone systems have evolved over the years since, several of those Baby Bells combined back together, and with the market changes due to mobile phones, we actually find a small number of companies controlling the market. They compete, yes, but to some extent they collude to keep prices high. Take text messaging, for example, which is disturbingly expensive relative to the actual costs. It actually costs more to track and bill text message usage than it does to deliver the messages, so when you pay for texting, you're really paying for them to bill you for texting, not for the delivery of the actual messages. This type of situation is called an oligopoly. Verizon, Sprint, AT&T, and T-Mobile can't make any huge moves to totally disrupt the market because of the market share of the other companies, but they don't want to either, because they're all sitting pretty if they can maintain the status quo. The potential buyout of T-Mobile by AT&T would actually serve to start tipping the monopoly scale if approved by regulators, so I don't think it's likely.
Friday, September 30, 2011
Business Spanish
Business Spanish was different than any other Spanish class which I have taken in that there was a point to it. I say that kind of flippantly, of course. I have enjoyed the various classes I have taken over the years, but most of them lack a real context of learning a language for a specific reason.
I remember in one of the earlier classes I had taken having a discussion about why we were learning the words we were learning. What's the big deal about learning the words for family relationships, food, types of vehicles, and rooms in the house? We did come to the conclusion that it's probably because those are common things around us in everyday life. You don't go very far without encountering a door, needing to eat, or having to find a bathroom.
In learning a language for a business context, there were reasons for learning more advanced, nuanced words and phrases other than a laying-around-eating-apples-by-the-pool-in-your-cousin's-backyard context. One of the most useful skills would have to be writing an appropriate business letter, which is hard to do in any language.
This class would actually be followed up the next semester by a Business Communication course (in English), which was also very helpful in learning many rules of grammar and writing business correspondence. It's sort of interesting that it's the first course I've ever taken in another language before taking the same course in my native language.
Something more applicable to my college career generally is that this was the first, and only, course I've ever taken as Pass/Fail, if that wasn't the only option. I had learned about the Pass/Fail option long after it would have been really useful to me. I still don't understand why that isn't one of those things they train freshman on in university orientation.
I was enjoying this class. I thought I was learning a lot. The teacher was tough, but it was interesting. Then the midterm hit. It destroyed us. Everyone in the class just bombed it. The professor was not happy about it. Everyone was stressed out about it. I think a few people dropped. I looked into the option to change to Pass/Fail, and it looked like it might work. I talked to everyone I could find in the department to make sure they would still accept the course for my minor in Spanish if it was not graded.
Everyone agreed I could, so rather than fight with my grade in the class, I changed to Pass/Fail. The tricky thing is that it's technically P/D/F, not just Pass/Fail, so if you earned a D, you'd still get a D on your transcript. By this time, I had recovered from my freshman year and had a decent GPA going, so even a B would pull me down, and it seemed worth the switch. I was pretty certain I wasn't going to get a D, but above that I had no idea.
In the end, I totally don't know if it was worth it. I mean, it was, because it caused me a lot less stress, but I have no idea what grade I would have earned in the class. I have no idea what grade my fellow classmates earned. I don't know if she applied any type of curve or graded it straight. All I knew is that I got some peace of mind, and I got to try out the Pass/Fail option.
I remember in one of the earlier classes I had taken having a discussion about why we were learning the words we were learning. What's the big deal about learning the words for family relationships, food, types of vehicles, and rooms in the house? We did come to the conclusion that it's probably because those are common things around us in everyday life. You don't go very far without encountering a door, needing to eat, or having to find a bathroom.In learning a language for a business context, there were reasons for learning more advanced, nuanced words and phrases other than a laying-around-eating-apples-by-the-pool-in-your-cousin's-backyard context. One of the most useful skills would have to be writing an appropriate business letter, which is hard to do in any language.
This class would actually be followed up the next semester by a Business Communication course (in English), which was also very helpful in learning many rules of grammar and writing business correspondence. It's sort of interesting that it's the first course I've ever taken in another language before taking the same course in my native language.
Something more applicable to my college career generally is that this was the first, and only, course I've ever taken as Pass/Fail, if that wasn't the only option. I had learned about the Pass/Fail option long after it would have been really useful to me. I still don't understand why that isn't one of those things they train freshman on in university orientation.
I was enjoying this class. I thought I was learning a lot. The teacher was tough, but it was interesting. Then the midterm hit. It destroyed us. Everyone in the class just bombed it. The professor was not happy about it. Everyone was stressed out about it. I think a few people dropped. I looked into the option to change to Pass/Fail, and it looked like it might work. I talked to everyone I could find in the department to make sure they would still accept the course for my minor in Spanish if it was not graded.
Everyone agreed I could, so rather than fight with my grade in the class, I changed to Pass/Fail. The tricky thing is that it's technically P/D/F, not just Pass/Fail, so if you earned a D, you'd still get a D on your transcript. By this time, I had recovered from my freshman year and had a decent GPA going, so even a B would pull me down, and it seemed worth the switch. I was pretty certain I wasn't going to get a D, but above that I had no idea.
In the end, I totally don't know if it was worth it. I mean, it was, because it caused me a lot less stress, but I have no idea what grade I would have earned in the class. I have no idea what grade my fellow classmates earned. I don't know if she applied any type of curve or graded it straight. All I knew is that I got some peace of mind, and I got to try out the Pass/Fail option.
Thursday, September 29, 2011
Legal and Ethical Environment of Business
This course, also known as Business Law, was really a great class. It was hard, but not too hard. It was interesting, but not too interesting. Just kidding. It was just the right amount of interesting, though.
Here we learned the basics of the legal system. We talked about the differences between civil and criminal proceedings. In criminal proceedings, to be convicted, it has to be beyond reasonable doubt. The prosecution has to make the tough case. In civil litigation, however, it's a plaintiff rather than government prosecutor going after the defendant, and judgment is made on a preponderance of the evidence. Basically, throw the evidence in one of those Lady Justice scales, and whichever way it tips, no matter how slight, that's the side that wins.
We talked a lot about land and things like adverse possession, trespassing, and liens. Our professor told us about how he was able to get a piece of land for basically nothing by filing certain paperwork and paying the taxes on a piece of land for a certain number of years, and it became his for only the cost of the taxes. I'm not sure if that makes me want to be a lawyer or not want to be one. I think I'd enjoy doing stuff like that a little too much.
One of the things I liked most about the class was not related to the content (well, slightly related) but more to its administration. Specifically, the administration of tests. I generally subscribe to the belief that tests should be well written. Item analysis should be done to ensure questions are measuring what they purport to measure in a valid way. Garbage or joke answers should be avoided, because they don't add anything and throw off the answer statistics. The only point I can see to those obviously incorrect joke answers on a multiple choice test is that it may serve to reduce some test anxiety for some students.
So the questions on the tests for this class were terrible. But terrible in a good way. They were written by a random graduate assistant or something, not the professor. If they had actually be written by a lawyer that was worth anything, they would have been tight like I would expect them to be. Having such ridiculous questions actually served a purpose, though.
After taking the test, we would get our copy of the test back, and we could go back through everything that night and come back to class the next day prepared to fight for points. If there was a bad question, okay, when there was a bad question, you would be prepared to explain why the answer you chose was right or why none of the answers was correct or all of the answers were correct, or something else. With a page number and a quote from the book, you argued your case. If you had a preponderance of the evidence, you got the point back. Sound familiar? He gave us garbage so we would go through it, analyze every word on every line, become an expert on that item, and hold him accountable for the mistake in the way of compensatory points back.
I also had one of those real life versions of that nightmare that we've all had of showing up completely unprepared for a test. I don't know what was going on that I showed up to one of the midterms and wondered why so many people were there early sitting on the ground outside waiting for the previous class to finish up, until I saw everyone madly skimming through their textbooks. Oh, it's test day! Last minute cramming. I flipped my book open, and got in about 5 minutes' worth before the class started. Luckily, it was one of those classes where you could drop one test. Unluckily, that meant I'd have to take the comprehensive final, which I was looking forward to skipping and dropping the 0.
Here we learned the basics of the legal system. We talked about the differences between civil and criminal proceedings. In criminal proceedings, to be convicted, it has to be beyond reasonable doubt. The prosecution has to make the tough case. In civil litigation, however, it's a plaintiff rather than government prosecutor going after the defendant, and judgment is made on a preponderance of the evidence. Basically, throw the evidence in one of those Lady Justice scales, and whichever way it tips, no matter how slight, that's the side that wins.We talked a lot about land and things like adverse possession, trespassing, and liens. Our professor told us about how he was able to get a piece of land for basically nothing by filing certain paperwork and paying the taxes on a piece of land for a certain number of years, and it became his for only the cost of the taxes. I'm not sure if that makes me want to be a lawyer or not want to be one. I think I'd enjoy doing stuff like that a little too much.
One of the things I liked most about the class was not related to the content (well, slightly related) but more to its administration. Specifically, the administration of tests. I generally subscribe to the belief that tests should be well written. Item analysis should be done to ensure questions are measuring what they purport to measure in a valid way. Garbage or joke answers should be avoided, because they don't add anything and throw off the answer statistics. The only point I can see to those obviously incorrect joke answers on a multiple choice test is that it may serve to reduce some test anxiety for some students.
So the questions on the tests for this class were terrible. But terrible in a good way. They were written by a random graduate assistant or something, not the professor. If they had actually be written by a lawyer that was worth anything, they would have been tight like I would expect them to be. Having such ridiculous questions actually served a purpose, though.
After taking the test, we would get our copy of the test back, and we could go back through everything that night and come back to class the next day prepared to fight for points. If there was a bad question, okay, when there was a bad question, you would be prepared to explain why the answer you chose was right or why none of the answers was correct or all of the answers were correct, or something else. With a page number and a quote from the book, you argued your case. If you had a preponderance of the evidence, you got the point back. Sound familiar? He gave us garbage so we would go through it, analyze every word on every line, become an expert on that item, and hold him accountable for the mistake in the way of compensatory points back.
I also had one of those real life versions of that nightmare that we've all had of showing up completely unprepared for a test. I don't know what was going on that I showed up to one of the midterms and wondered why so many people were there early sitting on the ground outside waiting for the previous class to finish up, until I saw everyone madly skimming through their textbooks. Oh, it's test day! Last minute cramming. I flipped my book open, and got in about 5 minutes' worth before the class started. Luckily, it was one of those classes where you could drop one test. Unluckily, that meant I'd have to take the comprehensive final, which I was looking forward to skipping and dropping the 0.
Wednesday, September 28, 2011
Principles of Business Information Systems
While the Science Orientation course I took was technically my last orientation course, I'm not sure it's totally accurate to claim that. The Principles of Business Information Systems course I took was probably more accurately labeled a BIS (now MIS) Orientation course. Yes, it's meant for other business majors, too, so they can have a basic understanding of what the IS people do, but that still screams orientation to me, whether or not you're talking to students who will actually major in that field.
The part that was weird was that this was a 300-level course. It's something I never understood. Apparently other people didn't understand it either, because they have since changed it to a 200-level course.
I just never really got it and still don't. If they would change it to a 1 credit 100-level orientation course, I'd totally understand. What are some career options? What do IS professionals contribute to the business environment? Basic terminology related to hardware and software. Trends in the field. Professional organizations. I remember writing a two page paper about my brother in law's business, selling calculators and cables, since back in the 90s, this crazy new e-commerce thing was a pretty big deal.
They actually added some Excel and HTML/CSS to the course. Yes, when they dropped it down from a 300-level to a 200-level course they added more stuff to it. That may have been to keep them from having to drop it to a 100-level course.
The part that was weird was that this was a 300-level course. It's something I never understood. Apparently other people didn't understand it either, because they have since changed it to a 200-level course.
I just never really got it and still don't. If they would change it to a 1 credit 100-level orientation course, I'd totally understand. What are some career options? What do IS professionals contribute to the business environment? Basic terminology related to hardware and software. Trends in the field. Professional organizations. I remember writing a two page paper about my brother in law's business, selling calculators and cables, since back in the 90s, this crazy new e-commerce thing was a pretty big deal.
They actually added some Excel and HTML/CSS to the course. Yes, when they dropped it down from a 300-level to a 200-level course they added more stuff to it. That may have been to keep them from having to drop it to a 100-level course.
Tuesday, September 27, 2011
Data Communication and Networking
Something I really liked about the Data Communication and Networking course was that it was in the late afternoon one day a week. That was a far cry from my Chemistry class at 8:30 every morning my freshman year.
Something I still wonder about to this day was the deal with the McDonald's cup my instructor would be sipping on every class. It was one of those jumbo paper cups, not a mug, and they don't last that long, so I'm sure it was a new one every time. It made me wonder if he just ate out on days we had class or if he ate at McDonald's every day. Maybe he did just save that same cup and reuse it all the time.
On the first day of class, we took a pretest. We were promised that anyone who received higher than a certain score (maybe 70) could receive an automatic A in the class and wouldn't have to attend the rest of the semester. The test was basically a preview of the final exam, and it was hard. Nobody came anywhere close. It does make me wonder what he did with the test results. I don't know if he used the results to actually determine where we were knowledgeable and where we lacked in aggregate to guide his lectures. I've always thought it was a great idea but have never seen anyone else start off a class this way.
This class covered the basics of the OSI model and various network configurations and equipment. It was a pretty basic intro to get us familiar with all kinds of networking terminology but not to a point that we could actually do much with it, especially given that many of the technologies we talked about were old and not used much anymore, except in legacy environments. For what it was, it was a reasonable introduction to networking.
Something I still wonder about to this day was the deal with the McDonald's cup my instructor would be sipping on every class. It was one of those jumbo paper cups, not a mug, and they don't last that long, so I'm sure it was a new one every time. It made me wonder if he just ate out on days we had class or if he ate at McDonald's every day. Maybe he did just save that same cup and reuse it all the time.
On the first day of class, we took a pretest. We were promised that anyone who received higher than a certain score (maybe 70) could receive an automatic A in the class and wouldn't have to attend the rest of the semester. The test was basically a preview of the final exam, and it was hard. Nobody came anywhere close. It does make me wonder what he did with the test results. I don't know if he used the results to actually determine where we were knowledgeable and where we lacked in aggregate to guide his lectures. I've always thought it was a great idea but have never seen anyone else start off a class this way.
This class covered the basics of the OSI model and various network configurations and equipment. It was a pretty basic intro to get us familiar with all kinds of networking terminology but not to a point that we could actually do much with it, especially given that many of the technologies we talked about were old and not used much anymore, except in legacy environments. For what it was, it was a reasonable introduction to networking.
Monday, September 26, 2011
Survey of Accounting II
The second accounting class I took was more interesting than the first class I took. We had gotten past the endless writing of debits and credits on T charts and started doing some interesting things. It covered topics such as cost accounting, budgeting, and standard cost variances.
Sure those topics sound boring, but this is where you start getting to a point where the accountant can actually help a business make important decisions. By breaking down fixed and variable costs to determine the true price of, let's say, an item you are manufacturing, you can determine the price you need to sell it at to cover all your costs. The accountant becomes a key member of the management team who helps everyone else understand where the money is coming from and where it is going. If I had to be an accountant, I would go into cost accounting.
Something I remember from this class was going to my professor's office to review my tests with him. I was always able to get a few points back by going in and talking to him. I would write notes all over my test paper, but the scantron only records if the bubble you selected is right or wrong. I would go look through the questions I missed, look at the notes I had written to see where I went wrong, and show him how I had maybe just flipped something right at the end, so I was really close to getting it. He gave me back partial credit on several questions like that.
It was in this class and the Microeconomics course I also took during my second semester as a business major that I would hone my craft of estimating my grade on a test. I take multiple choice tests relatively quickly. I'm pretty good at figuring out that type of question, generally. One testing technique I learned early on is that the longer you spend on a question, the more likely you are to miss it. Just answer it and move on. Your first guess will more often be right. If you get through quickly and have one of those professors who likes to lecture after the test instead of just letting you go, you sit around with nothing to do for several minutes while the over-analyzers are working hard at changing their correct answers to the incorrect answers, so you have to find something to do.
The technique I would use is this. Go through the test and count the answers that I just straight up felt confident about. I know it. One point. For questions that I didn't feel as confident about, I would count a percent for how sure I felt I had it right. If I totally guessed, 25%, assuming 4 potential answers. If I had ruled out 2 possible distractors (test item analysis lingo for wrong answers) and guessed between the remaining 2, I counted 50%. Add up the points and divide by the number of questions, and there you have it.
Sure those topics sound boring, but this is where you start getting to a point where the accountant can actually help a business make important decisions. By breaking down fixed and variable costs to determine the true price of, let's say, an item you are manufacturing, you can determine the price you need to sell it at to cover all your costs. The accountant becomes a key member of the management team who helps everyone else understand where the money is coming from and where it is going. If I had to be an accountant, I would go into cost accounting.
Something I remember from this class was going to my professor's office to review my tests with him. I was always able to get a few points back by going in and talking to him. I would write notes all over my test paper, but the scantron only records if the bubble you selected is right or wrong. I would go look through the questions I missed, look at the notes I had written to see where I went wrong, and show him how I had maybe just flipped something right at the end, so I was really close to getting it. He gave me back partial credit on several questions like that.
It was in this class and the Microeconomics course I also took during my second semester as a business major that I would hone my craft of estimating my grade on a test. I take multiple choice tests relatively quickly. I'm pretty good at figuring out that type of question, generally. One testing technique I learned early on is that the longer you spend on a question, the more likely you are to miss it. Just answer it and move on. Your first guess will more often be right. If you get through quickly and have one of those professors who likes to lecture after the test instead of just letting you go, you sit around with nothing to do for several minutes while the over-analyzers are working hard at changing their correct answers to the incorrect answers, so you have to find something to do.
The technique I would use is this. Go through the test and count the answers that I just straight up felt confident about. I know it. One point. For questions that I didn't feel as confident about, I would count a percent for how sure I felt I had it right. If I totally guessed, 25%, assuming 4 potential answers. If I had ruled out 2 possible distractors (test item analysis lingo for wrong answers) and guessed between the remaining 2, I counted 50%. Add up the points and divide by the number of questions, and there you have it.
Subscribe to:
Posts (Atom)