[team33] Re: [implementation] work work and work
- From: Fredrik Stenberg <frest167@xxxxxxxxxxxxxx>
- To: team33@xxxxxxxxxxxxx
- Date: Sat, 13 Nov 2004 22:52:10 +0100
Sunday evening I might be able to do some work, will yuo be at the computer
rooms then?
/F
----- Original Message -----
From: Fredrik Stenberg <frest167@xxxxxxxxxxxxxx>
Date: Saturday, November 13, 2004 10:41 pm
Subject: [team33] Re: [implementation] work work and work
> hEy,
>
> I was a bit surprised when I read the mail this afternoon
> (saturday). The planned meetings and work for the weekend I did
> not think we had decided on.
> I guess I don't have any main area of responsibility for this
> project, nor am I responsible for any of the reports. But I do
> think I have contributed by for example working on the
> requirements report, doing the design with markus, attending
> meetings with the architects in visio) etc.
> But I will try to work harder.
>
> Moving on, I have some suggestions for the database design. Some
> of the tables in the design report were in my opinion not
> satisfactory. I have posted suggestions for improvements at the
> repository:
> http://svnhosting.org:8000/svn/SoftEng/Design/Database/
> the document: "Suggestions fordatabase design.doc"
>
> I would have commented this sooner, but i only saw the new design
> this Friday....
>
> I thought, after talking to Markus, we had decided to do a start
> of implementation on monday. I'm able to work from 8 to 12, and
> about 15.30/16 to all night(?).
> I saw the time for the meeting at 13. Unfortunately, I have a
> doctor's appointment at that time, just my luck.
>
> Well, I'll see you all
>
> /Fredrik
>
> ----- Original Message -----
> From: Alexei Kounine <aleko379@xxxxxxxxxxxxxx>
> Date: Saturday, November 13, 2004 12:13 pm
> Subject: [team33] Re: [implementation] work work and work
>
> > ok man, you're right!
> > Ye it's maybe true that setting obligatory meetings on sunday is
> > not a
> > very nice solution!
> > As you said meetings are of course not mandatory, and people
> have the
> > choice of coming or not. it's just that i felt like the
> motivation was
> > lacking a little bit in the team, this is why i used the word
> "must",> which actually sounds a bit too agressive now that you
> made the
> > remark.But i guess it will change by itself, without me giving
> > orders to people
> > about their presence!
> > Thanks a lot for the remark!
> > I'm waiting for others!
> >
> > See you soon
> >
> > /Alex
> >
> >
> >
> > On Fri, 2004-11-12 at 20:22, Yusuf Hasanogullari wrote:
> > > Hi!
> > >
> > > Ok Alexei, here comes some criticism. Don't take it personally
> > as I'm
> > > just doing it because I want the project to flow better and
> for
> > you to
> > > get even better than you already are.
> > >
> > > I didn't know if it was better to send this to you personally
> or to
> > > the whole group. In the end I think it is better if we are
> open
> > so I
> > > will send it to the whole group and then maybe we can all
> contribute> > with coming up with a solution. Also, since the
> criticism is
> > done in a
> > > friendly tone there is no problem with sending it to everyone
> I
> > think.>
> > > You are doing a great job, much better job than the project
> > leaders in
> > > other groups from what I have heard from my friends. I really
> > > appreciate (and I am sure the others in our component group
> do as
> > > well) the way you always help if something is unclear, you do
> a
> > lot of
> > > work, you always know what is going on and what the next thing
> > to do
> > > is, what steps need to be taken care of for the project to be
> as
> > good> as possible, you know which persons are best suited for
> > which tasks so
> > > therefore you assign people to tasks that fit them and you
> also make
> > > sure everybody works equally much. But this small change in
> attitude> > is something you need to make to be even better:
> > >
> > > Problem is, you don't seem to realise that this is not the
> only
> > course> that most of us have. I for example have three other
> > courses, and when
> > > setting up meetings like you did in your last mail, sometimes
> it is
> > > impossible for me (and probably others) to attend. There is of
> > course> nothing we can do about this problem, but I would like
> you
> > to know
> > > that this is the case and realise that you cannot expect us to
> > come to
> > > some of the meetings. You cannot say something like "you must
> > come to
> > > the meeting tomorrow" because sometimes we have lifes of our
> own
> > after> schooltime and sometimes we have other classes to attend.
> > >
> > > If I don't attend a meeting, I read the new stuff added to the
> > > repository and make up for it that way, and I am sure the
> others
> > do as
> > > well.
> > >
> > > Now as I said, there is nothing we can do to solve the
> > > not-attending-problem, but just realising this will probably
> > help you
> > > plan better and not expect us to be able to attend some of the
> > > meetings.
> > >
> > > I will come tomorrow so we'll see each other then.
> > >
> > > /Yusuf
> > >
> > >
> > > On Fri, 12 Nov 2004 14:16:07 +0100, Joachim Reuss
> > > <i00joare@xxxxxxxxxxxxx> wrote:
> > > > Great job with the design report guys! I will definitely
> come
> > to the meet=
> > > ing
> > > > tomorrow. I've started writing on the test report, but at
> this
> > point it's
> > > > not very clear what should be in it. But we can discuss it
> > tomorrow.> >=20
> > > > See you!
> > > >=20
> > > > Joachim
> > > >=20
> > > >=20
> > > >=20
> > > > ----- Original Message -----
> > > > From: "Alexei Kounine" <aleko379@xxxxxxxxxxxxxx>
> > > > To: <team33@xxxxxxxxxxxxx>
> > > > Sent: Friday, November 12, 2004 1:27 PM
> > > > Subject: [team33] [implementation] work work and work
> > > >=20
> > > > Ok now that the report is handed in, listen carefuly to what
> > happens> > next.
> > > >=20
> > > > The plan says that next week we have a "First Integration
> > milestone"> > (Martin you should have warned us with this! Next
> > time send an email to
> > > > the whole team about the incoming deadlines, milestones and
> > > > presentations, ok?), meaning that we will have to try to put our
> > > > components together with the GUI and Algorithm. This is
> quite
> > a big
> > > > problem since the implementation is at its lowest level: we
> > just started
> > > > writing some classes, nothing more.
> > > > We will have to really move our asses this week end.
> > > >=20
> > > > One big problem in our team is that work isn't shared
> equally.
> > I wanted
> > > > to tell you about this at a meeting, but time is short, so
> > i'll do it
> > > > now. I am not the only one to think that some people did
> much
> > less job
> > > > than the others. By this i mean that Rama, Fredrik and Yusuf
> > (who still
> > > > did a bit more than the 2 others) don't have any specific
> task
> > such as a
> > > > report to hand in. All the others have written, or will
> write
> > a report.
> > > > Now if you disagree with what i said, please tell me, i
> might
> > be wrong.
> > > >=20
> > > > Time has come for you guys to invest more time in the
> project. The
> > > > coding part starts right now.
> > > > -First i want you to read carefully the Design document and
> > understand> > it (same for the other team members, especially
> > Joachim and Jonas).
> > > > -Our way of implementing interfaces really sucks, and
> actually
> > the whole
> > > > internal structure of classes must be modified to allow
> > synchronization> > of multiple connections to the mysql
> database.
> > This will probably be
> > > > done with the help of a ConnectionPool class shared at the
> > same time by
> > > > the GUI and us. I will discuss it today with the other
> project
> > leader,> > and we'll try to clarify that.
> > > > -tomorrow i want you to come at 13.15 at Java caf=E9 (the
> GUI
> > team will b=
> > > e
> > > > there as well) to start coding. While i will be discussing
> > interfaces,> > you guys will start writing the sql queries and
> > methods that the others
> > > > will use (take a look at retrieveLinks(), retrieveArcs()).
> > > > -What i don't want to do is telling you every word you need
> to
> > write.> > You will have to think about it yourself. (Otherwise
> > it's much easier
> > > > for me to do it myself. I don't want this). But don't worry
> > too much
> > > > about it, i will still give you some information tomorrow.
> > > > -You two will be responsible for having something which
> looks
> > more or
> > > > less like a complete system until tuesday.
> > > >=20
> > > > Did you get it?
> > > > Please answer, and tell me if you come (you must).
> > > > Chatting by mail about code is very difficult, this is why i
> > want you to
> > > > come.
> > > >=20
> > > > For everyone. I think that you don't give enough feedback to
> > Jonas. Once
> > > > again the experience report is important, don't forget it.
> > What i
> > > > usually do is: when something goes wrong or if i'm not happy
> > with our
> > > > work, i write a mail to Jonas. Same for the case where i'm
> > satisfied for
> > > > something. So please do the same. Send him a mail for
> > anything! Ok?
> > > > And Jonas, i know that you're sick now. When it gets better
> > can you
> > > > start developping these first months in the report,
> including
> > meetings,> > reports from everyone concerning the hours, the
> > general working
> > > > athmosphere and stuff like this?
> > > >=20
> > > > Joachim, you can start planning the testing. By this i mean
> > just create
> > > > a new document, and start filling in the squeletton with
> > stuff, without
> > > > thinking about the implementation of testing programs. All
> > right? I
> > > > don't want to be as late as we were with the design!
> > > > Is it clear?
> > > >=20
> > > > Yusuf, as you're the one who is close to the requirements
> now,
> > you have
> > > > to help Joachim with planning the testing, which will be
> based
> > on the
> > > > requirements. I want you to participate more to the
> meetings,
> > and get a
> > > > clear idea of the state of the project right now, so that
> you
> > can give
> > > > ideas about testing. I think this work is the most
> difficult:
> > building> > programs for testing if the requirements are
> > fulfilled. Contact Joachim
> > > > for that, and if you don't agree with my idea, please reply!
> > > >=20
> > > > Ok guys! Don't be shy criticising also what i do. I'm also
> > experiencing> > this kind of work for the first time, and
> > therefore i must do mistakes
> > > > somewhere! So really if you want to say something mean,
> fight
> > with me or
> > > > even offer me a beer, just do it!
> > > >=20
> > > > I wish you Good luck! And i really count on you to do your
> > respective> > jobs.
> > > >=20
> > > > /Alex
> > > >=20
> > > > --
> > > > --------
> > > > Alexei Kounine
> > > > Email:
> > > > <alexei.kounine@xxxxxxx>
> > > > <aleko379@xxxxxxxxxxxxxx>
> > > > Site:
> > > > http://anciensdeferney.free.fr/intouch
> > > >=20
> > > >
> > --
> > --------
> > Alexei Kounine
> > Email:
> > <alexei.kounine@xxxxxxx>
> > <aleko379@xxxxxxxxxxxxxx>
> > Site:
> > http://anciensdeferney.free.fr/intouch
> >
> >
> >
>
>
>
Other related posts:
