Half-way feedback, fall 2003

In the half-way of  the course students estimated and gave following feedback about the course. 
Feedback has given by: n.n 

1 What I have learnt

C# was a new tool for me, but on the other hand I was programing with VB, C, And Delphi so it was easier to me to start with C#

I learned basics of C#.

I've learnt main ideas about .NET and C#, main idea about handling databases, how to create simple windowed application.

I learnt about a new language - I had not know it before, and I find this language very good for me. ALso, I did not experiences with databases it the sense of using them in the application. This is good for me in this course that I can learn working with db's in the application.

I have learnt how to connect to a database in C# and getter and setter methods.

MSDN usage, DB connections.

2 What has been easy, what has been difficult, has some parts been tought too quickly

Easy

Generally all tasks beside XML task (from 39 week) were relatively easy - I mean they were on such level that after some self studing I was able to write them. According to me this is good level, because it force me to studing the subject, but do not discourage me.

C# seems to be rather simple in comparison to e.g. C++

Easy things: - the C# language itself - the Visual Studio .NET environment

Quite simple so far although tinkering with forms is a bit time-consuming.

Difficult

I haven't been to lesson about database access

I still have problems with handling Object Orinted Philosophy. Such things like abstract classes, polimorphism, interface, fields-propoeries, delegates are unknown for me - if I use Visual function it's difficult to handle to code - on the other hand it's difficult to write all code connected to each part of windowed application - more complicated things with databases

- handling XML (it always threw me exceptions about some "still in Epilog state")

3 What do I want to learn more, so what are most interesting subjects and what shoud I learn more

I would like to know how to programming in 'elegant' way and find out about some 'trick' in programming that are the result of your experience as a programer, because about many thing, functions and solutions I can read from book, but I think it is not the same as experience.

Interests: C# and web

Databases, databases, databases

Handle more complicated windows apps (multi windowes and so on).

DB stuff

Everything...

4 Open questions

Telling the true nothing comes to my mind.

Future of c# and .NET framework. I'm not really sure about application od that solution. e.g ASP+Apache as far as I know is impossible to handle, the same - propblems with handling OpenSource databases - is it good for some science applications - speed?

What tools are there and how to use them to handle XML files?

5 Suggestions, ideas...

no too much time consuming distance tasks, maybe it would be better to do more of them - but easier

The course is running quite fast sometimes but it does not disturb me. This way we can learn more. I find the idea of distance tasks good for learning programming as it forces me to do what I would not probably do if didn't have to.

More teaching from your side - more solutions - not just theory - how to programm well?? - ASP - is it really good solution ?

One suggestion is maybe that when introducing new topic we could see some trics in solving this kind of problems, maybe there are some easier ways to solve some problem that is hard to find in books.

More emphasis should be put on the TOOLS, that is, the existing C# classes one can use to solve the tasks (see XML) and, maybe, how to use them (just like on the last course with this "connecting to a database and making a query" thing. - Or is it a part of the task to figure it out? Sometimes it seems the theoretical part is not in synchron with the practical part (because of the two points above). 

I think everyone here knows the very basics of OO, so it is not needed to talk about that. Maybe it would be enough to talk about C# specific things only if neccessary, since in the basics it is very similar to Java. It would have been a good idea to get some info on our coding backgrounds in the beginning, and not by "OK! Who has coded in Java before?", because knowing the students nowadays, since I am one of them, noone will answer anything even if he/she has done some coding in Java. It should have been done in a written way. 

More things should be done together during the lessons

But anyway, I think it is a very useful subject, a need-to-know to every coder.

 

Brickbats and/or bouquets for the lecturer about...

Back