[Haifux] [W2L] Call for lecturer + "Linux guru"

[Eli Billauer]

OK, I think this is a good time to express my view regarding the 
"Development tools" lecture. It's purpose, as I see it, is to give the 
students a nice start with the "right" tools for developing code, as 
needed for their exercises. If their experience is good, they'll stay. 
If not, they'll soon use the alternatives.


If you want to give a lecture about any other subject, as a 
Stay-in-Linux or mainstream lecture, by all means come forward. But 
let's try to get some focus on the initial lecture.


Correct me if I'm wrong, but a student is not likely to go beyond a 
project which runs on a single platform, having a few source files, and 
with no more than two or three persons involved. Hence autotools are 
irrelevant, and so are version control systems. Tarballing all sources, 
and sending to your partner with comments, is as much version control as 
you need in these situations.


Eclipse doesn't belong to the "right" tools, in my opinion.


I would therefore set the following goals to a CS development tools 
intro lecture:


1. Being able to compile the sources (objects and executable), including 
math libraries and such, with reasonable flags (optimization, debug 
info, -Wall etc) with gcc.

2. Using make properly. No crazy tricks, just getting the actions and 
dependencies right.

3. Using vi/vim/emacs (show both, explain why both are good). I wouldn't 
bother showing many keystrokes, just demonstrating and pointing at where 
you can get a good reference for them.

4. Use ddd for debugging. It's worth mentioning that it's based upon 
gdb, and that gdb commands can be given directly (demonstrate?) but 
using gdb to start with is not convincing at all.


More is less. My $.02.


   Eli


Tzafrir Cohen wrote:

> On Thu, Oct 15, 2009 at 05:14:50PM +0200, boazg wrote:
>   
>> as a side note, a seperate lecture on git for CS students, and how to use it
>> with t2 would be a good idea.
>>     
>
> Why git?
>
> While I think git is a handy tool, did you have in mind "developement
> tools"?
>
> Other tools that come in mind:
>
> gcc
> make
> vi / vim
> gdb
> autotools
> emacs
> kdevelop
> eclipse
>
> (Just a list of tools from the top of my head, I don't intend to start a
> flame war on the exact content of a non-existing lecture)
>
>   


-- 
Web: http://www.billauer.co.il

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://haifux.org/pipermail/haifux/attachments/20091015/7cdc671a/attachment.html