Friday, November 20, 2009

Thoughts, Week 12

There's not too much to say about our Capstone proposal. There's only one new section (Executive Summary), and there's no new content involved. It's just a re-hashing of everything in our proposal so far, or at least the important stuff. We had to give a summary of the problem and solution, include some information about our resources and budget, talk about the dates on the Timeline for the most important things, and I added a bit about the Methodology (what I'm actually doing to complete this project).

Other than that, we've just been working on our Capstones. I think we'll have the rest of the semester to work on them, too. There's going to be a final presentation in early December where we talk about what we've done so far and why we should be allowed to go forward with our project. There was also the Proposal Defense earlier. Even in the Capstone class there's a lot of stuff to do other than Capstone. Heh, I guess that's why we need a portfolio system at CSUMB.

As for my project, I'd say it's going along well. I'm learning about Moodle, and about how to implement all of the things I'm going to need to implement. I hope to have access to the iLearn testing environment soon. Not much to say. Planning is on track.

Friday, October 23, 2009

Thoughts, Week 8

We've had the past two weeks to do two assignments: update our proposal (as usual), and actually start our ILP Portfolio. We were supposed to start it earlier this semester, but now it's actually due. Well, the first part of it anyway. That's a good thing because it means I took some time to flesh it out and make sure all the required content is there. And this way, I've got a head start on the rest of it, since I've got the design and format already done.

The ILP site updating was mostly uneventful. The core MLOs are listed on the ITCD site, and I still had evidence for just about everything. I didn't have as much for my math class (Math 170: Discrete Mathematics), and I showed evidence for Advanced C++ rather than regular C++. (I essentially assessed out of regular C++. I took a similar course at my old college and I convinced the professor that I shouldn't have to repeat the material.) It all works out though.

The two sections we added this time were the Milestones and Timeline. Creating Milestones was good because it forced me to break my tasks down into very small parts. Creating the Timeline after that was easy, it just involved figuring out how to tell Excel to do what I wanted it to do. Putting the Timeline into MS Word was the hardest part, actually. It's hard to make that much information fit on a single page in a visual format. I got it done though, and it still looks okay in my opinion.

Friday, October 9, 2009

Thoughts, Week 6

This week we added the Budget section and the Testing and Evaluation section to our proposals. I liked creating the budget. It wasn't too hard, since we had previous examples to use, and it was fun to see how much a project like this would really cost. It makes me feel like I'm accomplishing something, or at least that I'm going to be.

The budget section still feels a bit short, even though I added in more resources as our instructor suggested. I hadn't thought of things like a computer to use Adobe Dreamweaver, or a testing server. As I found out when I presented, we will have testing servers available to us. It's amazing how many resources students have access to. We can use all the Adobe software for free in the labs, and some labs even have top-end programs like Maya. That costs thousands of dollars usually, but it's all provided by the school. I think CSUMB gets some good deals on it too, but still.

I took some time to add section headers to the early sections of my proposal, and it looks a bit better now, I think. I still haven't done the research I need to about other projects. I should've found time by now, but between work for my other classes and time at my Service Learning site, I haven't.

Friday, October 2, 2009

Thoughts, Week 5

This week was easier than past weeks in some ways, and harder in others. This week I will be presenting my proposed Capstone to the programming teachers. There was no work to do on our Capstone Proposal paper, but I used the time to prepare for the presentation.

It seems a bit unbalanced for the people that presented last week - they had last week's work to do on top of preparing to present.

I think my presentation is strong. I've got all the parts I should have, and a few others just in case. I've got a slide I plan to skip over unless it's asked about. It never hurts to be prepared, right? I've gone through the presentation a few times. I always don't do well when rehearsing, but when I'm presenting I pull it off decently well, I think.

I don't have many pictures in my presentation. I guess I should add a few, but I'm not sure what would be good. A picture of iLearn? Everybody that's going to be there knows what iLearn looks like. Ah well. I've got the information, and that should be good enough.

Friday, September 25, 2009

Thoughts, Week 4

Whew, this week was a lot of work! We had to add the usual two new sections to our Capstone Proposal - Deliverables and Methodology - and we had to create a powerpoint for the Capstone Defense. The Deliverables section was about what we would actually produce - always good to document. I already had a good idea of the elements that would be needed because I did a similar (though much smaller) project for my PHP class (CST 352), but I wanted to be very specific about how the functionality would be divided into different pages. This was also the section to talk about documentation, which isn't a big element of my Capstone, I think. Documentation is obviously important, especially when implementing a new system, but in my case it's built on an already-known system and its functionality isn't especially strange.

Methodology was a lot more specific, and I don't think I have as much content there as I should. I've only got two resources listed, but I'm sure there are more that I'm just not thinking of. I'll probably discover more as I start to work on my project too. There are probably other risks as well. In general, I'm fairly sure I need to expand this section more.

The big thing that took up my time this week was creating the powerpoint. The content was fairly easy to come up with because I was just restating what was in my Capstone Proposal. But a presentation is a lot different than a paper, and working out how to communicate my ideas clearly and succinctly, and still take up 6-8 minutes was a challenge. I need to rehearse my presentation more, and maybe I'll change a few things around a little bit, but I think the structure is fairly well laid out. I'm just glad I'm presenting next week because it means I get another week to rehearse.

I still haven't completed a few things I missed on the previous sections. The main thing is that I haven't adequately researched and documented other similar projects. I know of a few, but I haven't put in the time to write about them. I hope I have time to do that in the coming week, because I didn't this week.

Friday, September 18, 2009

Thoughts, Week 3

This week was all about refining our Capstone proposal. It is now structured, and each section has clearly defined requirements. This makes it much easier to write. I'm glad we started out informally, it makes this feel like a big step. I guess it's partly because our proposal now has a title page and a table of contents (even if there are only two things listed so far).

Now that we've got requirements on each section, I know how to separate my ideas, and what to put in each section. Because of this, my proposal feels more like a proposal now. I had some areas I really needed to expand on. I still do, I guess, but I know what kinds of things should go there. Specifically, I feel like my problem statement needs work. I did a fairly good job of not talking about the solution (have you ever tried it? It's hard - I want to dive into the answer and stop talking about the problem), but that part is a bit empty compared to my solution description. Then again, in addition to general requirements, the solution description is the area to talk about how the solution fulfills the 5 required elements of a Capstone. I guess it makes sense that the solution section is bigger than the problem section, but it still makes the problem section feel smaller by comparison.

I also had to get my advisor contact form signed and scanned, but that wasn't a big deal.

Friday, September 11, 2009

Thoughts, Week 2

This week, web site modification was easy for me. I had to add a paragraph describing my Capstone idea, which was easy once I'd selected an idea and written the 200 more words describing it. I was basically summarizing from a larger document. I also changed the formatting of the assignments a little bit. I'm using my website template from my Web Design class, which has cool stuff like CSS dropdown menus. In that class, I had to talk a bit about each assignment, so each one needed its own page. In this class, the files are self-descriptive, so without a page describing each assignment, I needed to revise the structure of my links.

That's just esoteric stuff though, not what this class is about. Our main goal this week was to select one of our two ideas from last week. I had to think about it a lot. I've had some good times with Tarsier, and I can tell that they're a good group of people, and a good project to be involved with. Still, they're more science-oriented than I am, and the iLearn portfolio system is closer to what I see myself doing once I finish college. I ended up going with that (the iLearn portfolio system, that is).

The other thing we had to do this week was find and talk to a Capstone adviser. My concentration is programming, both of my potential Capstones are mainly about programming, there's only one pure programming teacher at CSUMB, I've taken many classes from him and know him well, and we've been working together this semester for a different class (independent study). Suffice to say, this part wasn't a problem. I didn't even look at this part of the assignment until today, which turned out to be my downfall - we have to get our potential adviser to sign a piece of paper saying we really did talk to them. Oh well, we meet Mondays for the independent study, so I'll do it then.

Friday, September 4, 2009

Thoughts, Week 1

The thing that surprised me most this week was how easy it was to get ideas for a Capstone project. I didn't know we'd have to come up with ideas so quickly, and I didn't have any planned, but I was able to talk to a few people and find ideas that just needed a chance to happen. I knew Tarsier* would be an option, but Eric Tao talked about an iLearn Portfolio, and it sounds like an interesting idea for a Capstone. A background with Tarsier won't help me out in the world, but a background with iLearn definitely might. Lots of people have heard of Moodle/iLearn. On the other hand, Tarsier is a full-featured modeling program, though it's only used by a small group.

Thankfully we can put down two ideas and narrow it down to one by next week, so I can spend a few days thinking of pros and cons for both sides.


* Tarsier is a 3D modeling program used by a few individuals in the Science department. I worked with them a little bit last semester.

Wednesday, December 5, 2007

Class Summary, Nov 29

This week we learned how to give technical presentations. I already knew a lot of this stuff, but not all. In fact, I learned something today that helped me give a better presentation the following week in the lab for this class. That piece of information was that people only remember about 30% of what you tell them, so the best way to give a presentation is to tell them what you're going to tell them (intro; what you'll cover), tell it to them (body), and then tell them what you told them (summary). The teacher for the lab class said she really likes it when people do this.

So, general presentation tips: don't have too much text, don't use just one color, have a background that is more interesting than a single color without clashing with the text, no more than seven things per slide (studies have shown that more than seven things, including pictures and the title, is less effective), and dress appropriately (your audience remembers your presentation, not your attire).

Now for some specific tips. First, for the opening: Establish relevancy to your audience. Give an overview of your presentation - tell them what you're going to tell them. Relate it to the big picture; how will it affect the future, how will it affect their lives, etc. Lastly, thank the people that helped you - they'll appreciate it.

For the body of the presentation: When using a chart to show data, choose the right type of chart. Make sure it doesn't give the wrong impression or convey the data incorrectly. Make sure it's easily readable and appropriate to your data. When designing slides, don't put more than one concept on a single slide. Low-content slides are okay, but two concepts on the same slide is a bad idea. If possible, start the slide title with a verb, because it sounds more active than a noun or other type of word. When going through your presentation, you should take about 90 seconds on each slide. A bit less is okay, but not too much, because with each new slide the audience doesn't listen to you for ~30 seconds while they read/understand it. A bit more is okay, but if you go for too long with a single slide the audience will get bored. Subtle animations are best, so you don't distract your audience from your content.

For the ending: When answering questions, approach the person as you call on them, so they know you're talking to them. Repeat the question to the audience, both so everybody can hear it and to give yourself a few seconds to think. Finally, talk to the audience as you answer it, so they continue to feel involved. There are a few ways of dealing with hostile questions, but the best way is to dodge them.

The most import thing to do, in my opinion, is to not read your own slides. They should be a guide to what you're presenting, but you need to give the meat of the presentation. Otherwise, why not just give the audience the presentation to read themselves?

Thursday, November 29, 2007

Reflection on my 7 habits

Ah, assignments. This one is about the 7 habits from the book Seven Habits of Highly Successful People. The instructions are as follows:

Include a reflection of the 7 habits; do you think they are important for you as a students? Why? Which of the 7 habits that you already have? Which you don't?

Again, those seven habits are:
  1. Be proactive
  2. Begin with the end in mind
  3. Put first things first
  4. Think win-win
  5. Seek first to understand, then to be understood
  6. Synergize
  7. Sharpen the saw (upgrade your physical, mental, social, and spiritual health)


I think those habits are useful for everybody, student and professional alike. The first three are important for personal success. For example, there are many helpful programs in college, but they don't seek out students. Students need to be proactive and seek them out. For college students, beginning with the end in mind is the best way to take classes. I know several friends who take the classes they feel like taking, without any regard for what their overall college education will look like. That's the end, the goal of college - to be educated. How educated do 50 easy classes make a person? Not very educated at all.

The second three habits (#4-7) are important for group projects. In group projects, students need to work together to make sure everybody gets a good grade, and more importantly to make sure everybody learns from doing the project. If one person does it all, the entire group might get a good grade, but they wouldn't learn. That's the purpose of group projects. That's what "winning" means in the context of a group project.

Understanding others is also very important to group projects; both when listening to other people's presentations, and when presenting your own; you need to know the material before you can tell others about it. The last of these habits, synergizing is a very important part of being in a group.

The last habit, sharpening the saw, is perhaps the most important one for students. We're here to learn about our field of choice, but extraneous knowledge matters a lot in life. If we don't know basic things about geography, history, health, etc, we won't get far in life.

Wednesday, November 28, 2007

No Class, Nov 22

Today was Thanksgiving, and we got the entire week off.

Class Summary, Nov 15

Today we didn't have any speakers. Rather, we learned all about Capstones. I've been hearing about them since I came here, but they were never clearly defined. Until now. A Capstone presentation is basically the final presentation before you graduate. It's more about the preparation than the final presentation, so as long as you did the work you should do alright, grade-wise. Capstones are cool because everybody does a different one, so there are all these big projects you can look at. It demonstrates to me that CSUMB students can really produce something.

Well, that's what it demonstrates in general, but it means more than that to me because I like looking at other people's projects, and since everybody does a Capstone there are tons of projects that are all different, all student-chosen. Fun stuff to look through if I ever have a lot of spare time.

The presentations are usually done in the classroom for this class, building 18, room 118. They're also broadcast to a monitor outside, and furthermore they're recorded and stored for 5 years. We can request a copy of 'em too. These things are official.

They're usually PowerPoint presentations, and usually about 10 slides long. Some people do other formats, but that's the norm. The standard Capstone presentation engages the audience, describes a problem, describes some potential solutions, states the chosen solution and why it was chosen, and shows how well it has worked. As usual for presentations, the audience can ask questions at the end. This means that the Capstone projects have to solve a problem. They also need to use sophisticated technology and/or design, and involve a community partner or a client. The intent here is to use our technology to solve problems in the community.

Heh. Salinas/Marina/Monterey must love CSUMB. There are all these helpful projects, done by CSUMB students, for free.

Anyway, Capstones have three classes dedicated to them: CST 400 (choosing a Capstone), CST 401 (doing that Capstone), and CST 496 (working with your Capstone advisor). CST 400 and 496 are taken one semester, then 401 and 496 the next semester. Yes, that means taking CST 496 twice; it ensures your advisor is involved in the entire process.

There are lots of potential Capstones, but there are some requirements. As stated before, a Capstone needs to:
  1. Solve a problem
  2. Use sophisticated technology and/or design
  3. Involve a community partner or a client

A Capstone itself requires:
  1. Complexity (it can't be too easy)
  2. Integration of technology and design
  3. Technology/design excellence (this is a professional project)
  4. Client/community involvement
  5. Project management


Another important thing is that since a community partner is involved, the Capstone needs to be able to be finished if that partner bails from the project. Thus Capstones are usually things developing everything required to set up a database of <something>, rather than actually setting it up. Setting it up would be very easy from the finished Capstone, but it would require buying the computers and software necessary. That part is up to the community partner, and if they choose not to do it the student can still complete his/her Capstone.

Wednesday, November 14, 2007

Class Summary, Nov 8

This week we only had one speaker: Reagan Pollack of WorldMusicLink. He was more of a businessman than most other people we've had, and he had some good advice for people planning to start a business. He recommends we use our class mates for feedback, since it's free and they're always going to be there to help. He also recommends we know a little bit about everything, so we can follow along wherever we are. Apparently a lot of the things he's used haven't been the main things taught in CST classes - his extraneous knowledge has come in handy. A phrase he likes is "think digitally, act analogically". This means we should think through all the possibilities, but only take small steps. I guess it's similar to the phrase "tread lightly".

Reagan and our instructor both mentioned the Marina Technology Center, which is a group in Marina that gives startup funds and space to new companies. If I was starting a company, that would be very useful.

We spent a fair amount of time talking about the book Seven Habits of Highly Successful People. Those seven habits are:
  1. Be proactive
  2. Begin with the end in mind
  3. Put first things first
  4. Think win-win
  5. Seek first to understand, then to be understood
  6. Synergize
  7. Sharpen the saw (upgrade your physical, mental, social, and spiritual health)

1-3 help you succeed by yourself; 4-6 help you succeed when working with other people, and #7 helps balance them all out and keep them going.

The assignment for this week includes a few more things (besides the weekly reflection). The first is to establish our big goals in life. I'd say my biggest goal is to get a secure job in the computer industry. I don't really care what part of the industry I'm in - I do have a specific area in mind, but if my career happened to veer off in another computer-oriented direction, that would be fine. There are other "big goals" in my life, of course, but I'd say a good career is the most important one to me right now.

The second other thing is to plan toward our futures. Ha! That's what the ILPs are for; that's what this class is all about. As Berj of the EOP office says, I've got my plans pretty well laid out. All I have to do is follow them. I haven't secured a position for after I graduate, but I think it would be silly to do so now, since I've got about two years of college left. The industry will change by that time. How much more planning could I possibly do?

The third thing to do is to sharpen our saws - to find a way to improve our physical, mental, social, and/or spiritual health. I think I'm improving on several of those fronts. My social health is definitely improving, mostly thanks to living on-campus for the first time. All this semester I've been meeting people and meeting opportunities. I plan to continue to do that in the upcoming semesters. The more I sharpen this saw, the better I'll get at sharpening it. I am sharpening other teeth of the metaphorical saw, but those are more personal things, and this is enough writing for one blog post.

Wednesday, November 7, 2007

Class Summary, Nov 1

This week we had two guests: Virgil Swamp, from the IT department of the City of Monterey, and Ed Cho, from the design firm Hanna Group. Virgil was a laid back guy who always looked at the big picture. Lately technology has gotten a lot cheaper, and skilled workers have gotten a lot more expensive. Thus the best way to save money is to use a lot of technology and very few workers. If something can be automated, automate it. It may cost something for a programmer to write the code to do it, but once it's done you won't need people to do that task, and technology is always cheaper than workers (these days). Virgil learned this when he was in the arctic working for oil companies. It's especially true there; anything a worker needs has to be flown in. Computers can be put on a task and left to complete it.

Virgil talked a bit about data centers. They seem to be the way large companies are going. A company can put together several data centers, and it'll still be able to function if one of them goes down. A data center needs cheap power, good cooling systems, and accessibility. Without cheap power all the computers will be a lot more expensive to run. Without good cooling, they won't last nearly as long. They also need both physical accessibility to replace parts, and digital accessibility to keep the software working.

Virgil also talked briefly about the internet boom. He described it as "incredible". In 1995, there were 75 websites. Total! There are over 150 million now, and that number is growing every day. The internet doesn't take weekends off.

The other speaker for today was Ed Cho. He was born in Korea, and he's traveled around a fair amount, both physically and in terms of his major. He graduated from Monterey High, then went to Cal Poly and majored in programming. He got burnt out after 3.5 years. He took some business classes to relax a bit, and found he liked business better. He transferred to San Jose State for a business degree, but ended up getting a publication/design degree instead. He worked for a few years, then opened his own printing house. After awhile, he expanded into design as well. He figured he only had one more step to go to be a full service business - marketing - so he expanded into that too.

Ed told us that local people may cost more than overseas workers, but they're worth it because they can respond quickly. It might take a few days to get an overseas designer to change an element of a product, but a local guy can do it and email it back in a few hours, or a day at most.

Ed also advised us to check out fashion magazines to see what colors work lately. Our own color choices shouldn't be the deciding factor - go with what's popular.

Ed shared a story about one student he hired. The student's work screamed "Hire me!" - literally - so he did. We shouldn't be afraid to tell employers that they should give us a chance, that we can prove ourselves worth hiring. We just need to be prepared to live up to this. If an employer hires you and you suck at your job, you're going to get fired. Relatively easy in, relatively easy out.

Wednesday, October 31, 2007

Class Summary, Oct 25

There was no class today, and thus there is nothing to summarize. Dr. Tao also said we don't have homework this week.

Tuesday, October 23, 2007

Class Summary, Oct 18

Today we started with a short Moodle vs Blackboard discussion. Seems most people like Moodle better, for a variety of reasons. For some it gives more detailed information, for others the interface is easier to use.

All the speakers this week were fresh graduates who'd been in the business for a few years at most. Eric Tao says it was planned like this; last week was graduates that had been working in the industry for awhile, this week was fresh ones, and next week will be graduates that have been working for a long time and are in upper-level positions.

The first speaker was Christina Frannie, who did web design. She'd been in the business for awhile before CSUMB, and came here for color/design theory. Her capstone was the site for the Pacific Grove Police Department. She's currently a webmaster/system analyst, but I didn't catch what company she works for. She says that what you know today will not be good enough for tomorrow. She also says that she learns something new every day (I've heard this from a lot of graduates). She recommends we keep up with the industry trends so we continue to be valuable employees. One of the most important things when doing projects is to back up your ideas with examples. She did this quite well for her capstone. She researched a lot of other police department's websites before starting, and had examples for every aspect of the design she proposed.

The next speaker was Francine, a graphic designer. She works on campus in the Alumni & Visitor's Center. We probably won't see her much because she does in-house design for CSUMB. There's quite a difference between in-house design and out-of-house design, and she recommends the latter. She's assured of always having projects to do, but they're always things like "design this flier by 5pm" or "we need this redesigned for 2007 within 2 hours", never long projects. This means she's always doing different projects, and she can't put a lot of effort into any particular one to make it great. Because she's in-house, the school pays for her to work, and she's free to her clients. This makes them feel that her opinions aren't important; she'll say "[based on my years of design education,] I think it'd look better like this", and her clients will insist that she do it their way, even if it's uglier, or wouldn't appeal to the audience. One person's hatred of a particular color could mean that color isn't used, when that color may be the best color for that brochure. Francine can ignore her color preferences thanks to her years of design education, but she's still at the mercy of her clients because she does in-house design.

Margo was the third speaker, and I don't have very much information about her. She majored in art, with only a minor in CST (Computer Science & Technology, I think - the degree is named Telecommunications, multimedia, and applied computing now). She also works in a design firm. Since she's more of an artist than a computer person, she draws out her designs and then transfers them to a computer.

The conversation got around to learning new skills, and Eric pointed out that one great way to keep learning new skills and improve yourself is to keep taking college classes in various things, and most companies have ways set up for you to do this.

Each speaker was asked to give us some general advice. Christina said to talk to students about classes, and specifically don't take Discrete Mathematics and Computer Architecture at the same time - it's too much work. I don't know if that would be true for me; I'm taking Discrete Mathematics, and I find it pretty easy, but then I have a very mathematical mind. Margo said to take extra classes, that way you have more skills to put on a résumé, and you're more valuable to an employer. Francine said to participate in contests and investigate potential jobs before you have to.

Final piece of info from the class: A good mark of success is being able to present your idea to a stranger who doesn't know anything about the field.

Wednesday, October 17, 2007

Class Summary, Oct 11

Today we had graduates come in and talk. The first two were Pauline Sung and Erin Salano. They're married, I think. Pauline is from Hong Kong. She started here as an international student, and she did a custom track that focused on both tech and design. She's currently working for Trofholz Technology, Inc., which does government contracts. Her capstone was a database-driven website for her sister's bridal gown business, back in Hong Kong. It sounds like an unusual capstone to me, but it's got all the elements of a professional website, so it worked. Her advice to us is to study hard and talk to our teachers, especially here, because teachers are so open. I think that's true everywhere. It was certainly true at my old college, College of the Redwoods.

Erin is a military guy, and he's got a military job. He's working at DLI, the Defense Language Institute. He's running a college inside a military base. It sounds like the students are getting a good education - they all get a 30gig iPod and headphones, and a Tablet PC. A lot of the material is in audio and/or video form, so the school gets a lot of use out of their investment in their students. They're also rolling out wireless this year, which is tricky inside a military base because the military doesn't like anything that's potentially insecure. He says the Computer Science textbooks are the same everywhere, and we need to push ourselves through the material. That's not true for me; Computer Science is what I love doing, so working hard at it comes naturally to me.

The third speaker was Caroline, and I never heard her last name. She majored in Instructional Design, Multimedia, and Web Design. Lots of majors. She got a job at the Salinas Valley Memorial Healthcare System, and I can tell she loves it. She's their webmaster - a title they didn't even have when she was first hired. She got hired part-time, and the more she worked, the more they wanted her to do other projects. Everything involved web design, but there are many different things you can do within that field, even for a single organization. She runs six websites now, including a portal for doctors, a portal for patients, and the general website for the organization. She says she learns something new every day in Photoshop or Dreamweaver, and she's worked with those programs just about constantly since she graduated.

Jennifer was the last graduate to talk today. She majored in Instructional Design. She liked CSUMB because there were a lot of real-world projects. Her capstone is a good example of this: she made a flash-based interactive map of a local park's trails. This is the kind of thing that elementary school students could use to explore the park before they take a field trip there. She says the key to capstones is having a group of people. I'm not sure if that means a group to work on the project, or a group of test subjects to help you refine your project. Either way, I can see the benefits.

We had a question-and-answer round, and the first question Dr. Tao asked everybody was what they were looking for when hiring people. Caroline said she was looking for people that overachieved instead of just doing the minimum. Erin said that troubleshooting is very important, as is showing your work to employers. (I could tell that he was good at troubleshooting, and that he knew computers well.) Pauline said people skills were the most important thing. Jennifer said that paying attention and following directions were vital, attitude is everything, and that you should let your talent shine on the job, as well as backing away sometimes and letting other people's talents shine too. Everybody is good at something different.

We also had one staff member talk. His name was John Ittelson. He seemed like a boring old guy at first, but he turned out to be pretty entertaining. He said he was dyslexic - he stays up at night and wonders if there's a dog. He got depressed awhile ago and threw himself behind a bus.

He studied at Chico, which is an infamous party school. He didn't party there though. Ten years after he graduated he went back and taught there. Chico was named a top party school again by Playboy Magazine. He brought a copy into class, held it up, and asked "Where are the parties?"

Somebody in the back row shouted, "Think about it John, you're not invited."

Thanks to that warm welcome, he came to CSUMB and started teaching here.

Wednesday, October 10, 2007

Class Summary, Oct 4

There was no class today, and thus there is nothing to summarize. Dr. Tao also said we don't have homework this week.

Wednesday, October 3, 2007

Class Summary, Sept 27

This assignment is about what I learned in class on September 27, 2007 (last Thursday). This is the only thing I'm posting this week because we don't have many assignments that involve writing.
There's one other one, but that's just finding a job we might go into after graduation, and I already did that for the Critical Response #1 for my CST300L class. I like this job. I don't think that exact job will still be open when I graduate, but that's the type of job I'm looking for.

Anyway, today in class we talked about project management. In order for it to be successful it needs to
  1. produce the correct product,
  2. produce it in a timely manner, and
  3. do it within the budget
We also clearly defined a project - it needs to have a beginning and an end, some goals, and deadlines. Without any of those, it's not a project.

There are a lot of things that can make a project fail: poor communication, disagreements, a chang in the environment or the constraints of the project, people leaving[1], personality conflicts, poor management, poorly defined project goals[2], and a failure to comply with standards and regulations.

[1] In big projects, people always leave. Managers can't stop it, they can only lessen the impact of it happening. Employees should keep good notes, so future employees can read those notes and pick up where the first employee left off. The notes aren't just about what was done, they're also about what was tried that failed. That way those things don't get tried again.

[2] I hate not having poorly defined project goals. I just hate it. I do something, and the person I'm doing it for changes what they want. Now, for every project-like thing I do, I clarify the goals first. That way I can go back and say "no, you said to do it like this".

We were shown several ways to break down our time. I didn't copy them down - stuff like that is intuitive to me. I end up getting it done somehow.

Next we talked a bit about goals. Goals need to be:
  • Specific
  • Measurable - when are we done?
  • Agreed upon
  • Realistic - must be based on the available resources, knowledge, and time
  • Time-framed - Set a clear deadline and stick to it. Specific days like "October 24" are better than general times like "a month from now," because when people learn that something is due "a month from now" that's what they'll remember. In two weeks, it'll still be due "a month from now," and when the deadline comes they'll be suprised because they thought they had almost a month to do it.
We had some speakers come in. We got through 4 speakers today, which is unusual: Dr. Bude Su, Sathya Narayanan, Valerie Landau, and Bobbi Long.

Dr. Bude Su talked to us about capstones. She's got a degree in instructional design, which should really be called instructional technology these days. It involves using different strategies to make education effective. There are jobs all over in this subject; every organization could use effective education. Bobbi teaches CST 400 and 401, which involve designing a capstone and then developing it.


Sathya Narayanan does networking. I first met him in my Math 170 (Discrete Mathematics) class. He gave a presentation to the class about how useful it is for programming. Knowing something about the material, and knowing something about programming, I quite agree. He talked to us today about having a job verses a career (a job is just a source of money, a career is a lifelong place to work and grow), and about how more training means more money in the workplace.

Valerie Landau is a web designer. She used to write the game design documents that graphic artists, programmers, etc use to make games. She's been in the computer industry for quite awhile. She was there for the vaccuum tube -> semiconductor switchover. She's used punch cards. She's working on more modern stuff now though. She's teaching instructional design, and she has a side project developing a keyboard in a glove. It should be ready by January, and she's looking for interns to help with the project. She sounds like a fun person to work with.

The last speaker was Bobbi Long. She does communication design and typography. That stuff is useful for more than just newspaper editors - knowledge of typography inspires good logos and attractive documents. Bobbi knows 5 languages, and she's worked on all kinds of visual things - logos, newspapers, brochures, fliers, etc.

Thursday, September 27, 2007

Time Management Articles

For those not in CST300, this assignment involves going to this site, reading at least the first 5 articles, and talking about 3 things we learned.

In reading those articles, I learned that a little effort goes a long way, if structured right. With good planning, good preparation, and the right mindset, it takes very little time to get things done. I also learned that procrastination is much more dangerous than I previously thought. I've been learning that for myself lately, because I tend to procrastinate. This website lists it very clearly though. The third thing I learned is that a to-do list helps. I've had some experience with this in my own life, but I still don't use to-do lists as much as I probably should. Hmm, I should make a note of that. "Todo: use to do lists more." Hope I remember to check this to do list.