Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sounds like what I want to be doing. I'm curious if you have additional insight on taking on this path, I want to keep all of my options open and instead of say just pursue embedded/real-time systems and find out that the field is too narrow. What do you recommend to study as opposed to CRUD web-apps,

C/C++, ML, data analysis with Python/R or learn more domain specific knowledge such as Bioinformatics or graphics or quant finance? Much appreciated, thanks.



It depends a lot. This is opinion, but I would say that there are three big categories of software development skills. Of course most jobs are a mixture of these.

1. Web development (transport-level and higher networking, HTML/JS/CSS, PHP/Perl/Python/Ruby, using databases, etc.)

2. Enterprise software design (domain modeling, OO programming, system architecture, scaling, security)

3. High performance (algorithms, advanced data structures, C/C++, memory management, DB internals, internet-layer and below networking, cryptography)

It sounds like you want to get into 3. A good way to start is algos/data structures. Almost all the fields the parent listed benefit from a very strong foundation in computer science: discrete math, linear algebra, algorithms, advanced data structures, etc.

Data analysis with python/R is more for scientists and mathematicians, not software developers. If you are being paid to analyze data as a programmer, usually you are analyzing very large data sets and you will be using a much more performant language or possibly even a highly parallelizable paradigm like MapReduce.


The easiest path into a nr 3 job here is to find a job with an engineering product company, ie a company that sells a high-tech product that is not software.

My current job mixes those three categories nicely and I love it :)


I'm not clear if you're saying you do or don't want to be in embedded, if you do then try hanging out in:

  comp.arch.embedded
for a few weeks, find mags related to embedded.


I am a database developer in a sequencing center. I would not recommend bioinformatics if you have any passion for good quality code.

There are some decent bioinformaticians out there, but most of them write crap 100 line scripts, and have very little desire to learn more than the basics. I am getting increasingly frustrated, as I can see I am clearly writing significantly smarter software then these people (most of them are just counting things and plotting the counts on a graph). I am seen by management as being the same kind of skill level / skill set.

If of course you are really interested in the research, then you may like it, but do not expect your coding skills to be valued.


hi collyw, thanks for your message. I'm indeed really interested in Bioinformatics. I've had experiences in undergrad similar to what you described (e.g., a folder with 50 Perl scripts that does a variation of the same thing).

I don't really mind the management slights as it's an occupational hazard of a programmer. What bothered me about academic research was how the doors were shut for you if you did not pursue the traditional PhD/post-doc path of life sciences research. Also that pure Bioinformaticians even with academic pedigree was considered lower in the pecking order in comparison to "wet-lab" folks.

As crazy as it sounds, I really miss the days of writing Perl scripts (Python probably now); running BLAST and plotting Information Theory graphs. How do you like your current gig and what do you recommend for someone who is looking to jump back into it?


My current gig has ups and downs. I like getting to code things from scratch in the technology of my choice, but too often we are using the quickest crappiest solution to get things done (uploading database data using excel - supposed to be a temporary solution, but has been going on for two and a half years).

Apparently most labs have a shortage of bioinformaticians (at least that's what I hear here in Europe).

Yes, having a PhD will be helpful if you are looking towards a more research oriented side of things. If not you are more likely to be more of a technician, and your work will be a bit more production like.

My advice would just be to look at institutes that you would be interested in working at - their job pages. I am sure you could start with more production style things and move into a more research oriented role.

Here is the jobs page for science park I work in in Barcelona (pay doesn't sound much compared to the US). Not much up there just now, but I know we are hiring more people soon.

http://www.pcb.ub.edu/homePCB/live/en/p2466.asp




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: