destiny team mailing list archive

[Zach Elko <zachelko@xxxxxxxxx>]

Hi,

I'll address you in this e-mail, Tom.


On Tue, Feb 23, 2010 at 1:01 PM, Mast, Thomas O <tomast@xxxxxxx> wrote:

>  Check. I’ve got pretty thick skin and don’t really take stuff very
> personally most of the time, so don’t ever worry about that. I can
> understand your frustration with me on the communication part over break and
> stuff, but I could definitely tell a few of you guys just stopped responding
> to me the past month or so. The communication thing is something I’ve always
> had issues with in group projects, that’s why I like the team meetings so
> much the first semester—it kind of kept everyone responsible timewise on
> their projects. I realize we don’t have the time capabilities for that this
> semester which blows.
>
>
>
The way I understood the issue about Ian not getting back to you was as
follows: Ian had sent out an e-mail to either everyone, or you specifically,
requesting that you work with him on Sleuths stuff for the last milestone.
The first he heard back from you was 4 days before the milestone was due. At
that point, he didn't reply because there was nothing left to do as he had
been working on it the entire time. He probably should have replied to you,
but regardless, you didn't lose any points for those 4 days of which you
weren't helping him, it was the 3 weeks prior.

That I know of, the only other instances of people not replying to you were
the night before the milestone was due after you finished your FTP code at
around 3:30am asking if anyone else needed help. That's fine, and I'm glad
you did send the e-mail, there just wasn't anyone still awake that needed
help. The other time would be what Doug mentioned. By that time, there
wasn't much to reply to.

Moral of the story is just make it a point to respond within 24 hours. I'm
taking 18 credit hours and working 20+ hours a week, so if I can do it,
everyone else should be able to do it also.


>  I can usually catch Doug/Zach on facebook chat sometimes, but that chat
> is pretty awful. Other than email, do you guys have AIM screennames or
> something that we could use to pop quick questions back and forth? I know we
> sit on our computers a hell of a lot, and it’d be nice to have a quicker way
> of communicating while we’re working on code etc. IRC? Tin cans and string?
> Dunno.
>
>
>
My suggestion for this is that if you need to chat with someone, send them
an e-mail and arrange a way to do so. Most of us aren't on chat all of the
time, but most of us always have access to e-mail. If you need to chat with
me, Doug, Ian, or Andy, send them a personal e-mail (not on the list) and
arrange a medium to have the chat. In my eyes, that's the best solution.


> On the bright side I’m off probation for the horrible horrible crimes I
> commited against society and their blank, boring walls. We can all walk the
> streets safely again. On another note, I’d advise you guys against getting
> drunk and then getting the bright idea to trainhop on a freight headed
> towards Indy in the middle of the night with your friends. You’ll end up
> cold, lost, and smelling pretty awful.
>
>
>
I don't really have much to say to this. Ha.


-Zach


> *From:* destiny-bounces+tomast=bsu.edu@xxxxxxxxxxxxxxxxxxx [mailto:
> destiny-bounces+tomast <destiny-bounces%2Btomast>=bsu.edu@
> lists.launchpad.net] *On Behalf Of *Doug Shook
> *Sent:* Tuesday, February 23, 2010 12:33 PM
> *To:* destiny@xxxxxxxxxxxxxxxxxxx
> *Subject:* [Destiny] Peer Reviews
>
>
>
> Hello everyone.  After our little mini-discussion about peer reviews in the
> hall after class I felt that we didn't quite get everything across the best
> way possible.  This email is primarily intended to justify why I (and I'm
> only speaking for myself) gave out peer reviews in the way that I did, and
> what can be done for those who wish to improve.  I'm sending this to the
> whole mailing list so that we can get everyone's feedback and hopefully
> decide on a solution as a team.
>
> Tom, last semester you were criticized for your lack of communication, and
> it continued even after I brought it to your attention.  I remember one
> point last semester when I had fixed some bugs in your avatar code.  You
> then committed over them after we had told you so many times to always
> update before you make any changes.  I sent an (understandably upset) email
> to you about what you did and didn't receive any reply.  I have to say that
> your behavior in that situation pretty much turned me off to ever trying to
> help you again.  I've seen some attempts on your part to rectify the
> communication issue but they always seem half hearted.  Sending me an email
> that your assignment won't be done until a few hours before its due doesn't
> really do much good at all, especially when you had over a week to do it.
>
> Andy, last time I wrote out an email like this I brought up the fact that
> you were assigned to write a hashing function, which didn't get finished.
> Afterwards you did finish the hashing function, but it wasn't helpful to us
> at all.  There was no way it would've worked with the Login Window that we
> had, and in fact after a few minutes of inspection it was pretty clear to
> see that you ripped a huge chunk of code you found from google and added a
> few lines to it.  Something similar happened with the unit tests, which you
> blatantly copied from my own unit tests.  Its not so much the code
> "borrowing" that I mind as it is that you couldn't even take the time to
> figure out how to adapt the code you borrowed so that it actually did what
> it was supposed to.  I wouldn't have even minded THAT so much if you
> would've found me or Zach or anyone and asked us how to do it correctly
> instead of just hoping that it would since it worked for something else.
>
> Finally, I'd like to discuss the assigned tasks given to the two of you.
> The only reason any tasks were assigned to the two of you in the first place
> is because of the fear that myself and others have had about what would
> happen if you attempted to work on certain parts of the project.  Given the
> above behaviors I don't think that you could blame anyone for not trusting
> you to do things properly, and on a project such as this that's REALLY
> important.  If you want one of us to keep telling you what to work on I can
> continue to do so, but no one ever tells me what to work on.  I've been
> keeping up with this project since day one and I know what has and hasn't
> been finished.  If for some reason I'm not sure then I'll ask someone, or
> just check it myself.  As senior computer science students I don't think
> that this is too much to ask.
>
> I'm truly sorry to have to be writing another one of these emails.  Its
> just as unpleasant for me as I'm sure it is for you, and I hope that neither
> of you take it personally.  I also hope that you weren't truly surprised at
> the grades you got, however, and if you were then I ask you this: how much
> stuff on the repo can you honestly say you contributed to?  I, for one, am
> proud of my work, and I don't think it would be right to give equal credit
> to those who contributed less, period.
>
> All of that being said, I am willing to ignore everything that has occurred
> in the past and start anew.  There is still so much work to be done and it
> will be much easier if we have your help.  So please....help us!
>
> _______________________________________________
> Mailing list: https://launchpad.net/~destiny<https://launchpad.net/%7Edestiny>
> Post to     : destiny@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~destiny<https://launchpad.net/%7Edestiny>
> More help   : https://help.launchpad.net/ListHelp
>
>