carreer opportunities

[Bruno Medeiros]

eao197 wrote:
> On Wed, 27 Jun 2007 08:26:14 +0400, John Demme <me at teqdruid.com> wrote:
> 
>> Don't become a D programmer.  Don't become a C++ programmer.  Don't 
>> become a
>> C# or a Java programmer.  You really don't want to become a Ruby or 
>> Python
>> programmer.
>>
>> Just be a programmer.  (Or engineer, architect, designer.. whatever)
> 
> It looks like: "Don't become a stomatologist. Don't become a surgeon. 
> Don't become a oculist or a otolaryngologist. You reallu don't want to 
> become a cardiologist or a neurologist. Just be a doctor!"
> 
> If someone want to be a good D programmer (or C++, or C#, or Ruby) -- 
> let it be. Almost any language has a lot of dark corners, idioms and 
> best practices which a developer need to know to write efficient and 
> bug-free programs. And it is very good if there is a language guru in 
> your team who can help in searching bugs or bottlenecks.
> 
> Obviously, the good knowledge of some language (or even languages) is 
> not enough to be a good specialist. To be good specialist one needs good 
> knowledge of his problem domain (embedded real-time software, very large 
> databases, compilers, telecommunications, etc). Switching from one 
> domain to another is not an easy task now. It's harder that ten years 
> ago and will be much harder in the future.
> 
> But at starting point in the start of career becoming a D programmer is 
> much better than becoming abstract 'problem solver'.
> 

Developers do specialize, but it's not in programming languages where it 
is relatively easy to transition to another language (especially in 
static, imperative style languages).
Specializations for computer scientists/engineers are stuff like network 
administration, web applications development, game development, embbeded 
systems development, telecommunications, etc., where there is a lot of 
area-specific knowledge to be learned.

-- 
Bruno Medeiros - MSc in CS/E student
http://www.prowiki.org/wiki4d/wiki.cgi?BrunoMedeiros#D