====== A Computer Workplace for Engineers ======

This page is addressed to what the author claims to be an indispensable set of software for an engineer's workplace PC, mainly but not exclusively to electronic engineers.

===== Recommended Platform =====

An optimal computer workplace for engineers shall provide a Unix-like working environment.

<wrap help>Why should engineers be familiar with a Unix-like working environment.</wrap> :TODO:

==== Native Unix-like working environments ====

The preferred Unix-like operating system may be a Debian based Linux.

  * www.ubuntu.com/desktop
  * www.debian.org

If your boss/company insists in using a Micro$oft Windows OS, urge them at least to equip your workplace PC with an
 [[engineering_workbench|Unix-like working environments for M$-Windows]].

===== Recommendet Computing Skills =====

  * [[http://www.iu.hio.no/~mark/unix/unix.html|The unix programming environment]]
  * [[wpde>Unix-Kommando]]
  * [[http://www.fibel.org/linux/lfo-0.6.0/node139.html|Textfilter]]
  * [[http://sed.sourceforge.net/sedfaq.html|The SED FAQ]] -- Frequently Asked Questions about sed, the stream editor

==== Scientific Computing ====

This section was inspired by an article of [[http://www.americanscientist.org/template/AuthorDetail/authorid/1571|Gregory V. Wilson]] presented by the [[http://www.americanscientist.org|American Scientist]]. Although I am not a pure scientist, I've got a Déjà-vu when reading this article. Only too well G.V. Wilson's experiences matches those I've made at my work as engineer.

  * **[[http://www.americanscientist.org/template/AssetDetail/assetid/48548|Where's the Real Bottleneck in Scientific Computing?]]**\\ //Scientists would do well to pick up some tools widely used in the software industry.//

Wilson's Software Carpentry provide a set of recommended lectures to overcome this.\\

  * [[http://www.swc.scipy.org|Software Carpentry]]

=== Engineer's Sentiments ===

<blockquote>
From: Dan McMahill <dan@mcmahill.net>
To: gEDA user mailing list <geda-user@moria.seul.org>
Subject: Re: gEDA-user: Why use gEDA?

> Sadly, most students are not comfortable with Unix and command lines. If
> providing a more familiar GUI approach to using the tools is possible,
> and doesn't detract from the core flexibility which benefits gEDA, I'm
> all for it. It will help us compete with commercial tools - which (IMHO)
> are not that good in terms of usability anyway.

It is sad that most are not comfortable with command line tools.  I'd
list awk and perl near the top of my "must have" tools for work.  I
can't imagine getting the job done without a decent computing
environment (i.e. if I were forced to use windows).  But then again, I
also realize that my view is biased by the types of projects I work on.
</blockquote>

<blockquote From: al davis [ad136@freeelectron.net]
To: gEDA user mailing list [geda-user@moria.seul.org]
Subject: Re: gEDA-user: Why use gEDA?>
On Sunday 25 February 2007 16:28, Dan McMahill wrote:
> It is sad that most are not comfortable with command line tools. I'd
> list awk and perl near the top of my "must have" tools for work. I
> can't imagine getting the job done without a decent computing
> environment (i.e. if I were forced to use windows). But then again, I
> also realize that my view is biased by the types of projects I work on.

When a school uses an all MS, all GUI environment, they prevent their
students from getting those jobs.

I recall, at Bell Labs, a bunch of years ago ...  The analog designers,
doing chip design, were all good programmers.

I can't imagine any real EE job without good programming skills.

Advise for prospective students looking for a school:  Look at their
computers. If it is all Microsoft, stay far away.  If CS is all Microsoft,
run away as fast as you can.

Comment on the gEDA port to Windows:  It is not for the schools.
It is for industry where they are stuck with it.  Any school that uses
the "It must run on Windows" excuse won't use it anyway.
</blockquote>