- A Concurrent Affair - https://www.concurrentaffair.org -

A Summary of COMP 312

Here’s a short summary of this semester’s COMP 312 class: We had the manpower, but not much was done.

Consider the minor projects [1] I had outlined before the class. These are the ones I implemented on my own:

This one was started by other developers, but I finished it:

This one was completed by another developer without my involvement:

And these are the ones we did not finish:

Considering that we had seven developers, with four of them in COMP 312, I had expected to implement every project on this list. Instead, we only finished 6 out of the 10 tasks, and I worked on 5 of them. Only one task was completed without my involvement, and one was partially implemented, but the changes did not cover all aspects of the problem. It is sad that only two minor projects were attacked at all by the COMP 312 developers, and only a single one was completed satisfactorily.

Of the major COMP 312 projects [1], I had hoped that each pair of developers in COMP 312 would finish two projects, perhaps a total of seven projects. In the end, we completed three projects and made good progress on four others, so it looks like we got close to achieving my goals. However, if you consider that I completed two projects on my own, worked on another one alone, and had to finish the only major project that was started by COMP 312 students, then this part of the summary is as bad as the first part.

These were the projects I worked on without anyone else:

This project was started by other developers, but I finished it:

Three other developers worked on these three projects and made good progress, but did not complete the task:

And these major projects were not approached:

Unfortunately, I have no idea what has changed over the last few years and why the last two or three iterations of COMP 312 less successful.

[2] [3]Share [4]