Hacker Newsnew | past | comments | ask | show | jobs | submit | more oolongtea's commentslogin

Lumicks B.V. | C++ Developer | Amsterdam, NL | Full Time | ONSITE | lumicks.com

Lumicks is unlocking the tools of single-molecule biophysics for researchers worldwide. With our easy-to-use C-Trap and AFS systems, scientists can visualize life at the level of single molecules, while at the same time applying tiny mechanical forces. This is key to understanding the complex biological processes that are at the root of many challenging diseases.

We're an academic spin-off from a research group at VU University Amsterdam. Having sold the first dozen instruments to opinion-leading labs in Harvard, Rockefeller University, ShanghaiTech, Max-Planck, and others, we are now expanding the software team. We care deeply about providing our users with easy-to-use, reliable software that actively supports Open Data and Reproducible Science.

Our team is small, and you'll have the opportunity to work across the stack. Keywords: C++11/14/17, Qt 5, Python 3. We're a high-energy workplace with an informal culture.

Full job description available at: https://lumicks.com/c-software-developer-job-opening/


Fair question --- colleague of agom here, BTW. I just discussed extensively with one of the people here at Lumicks, as I was wondering the same thing.

I think it's meant as a proxy for "enjoys a startup, not a 9-to-5 mentality, as we're still very much in an early growth phase, where people need to be a bit flexible". I may try to push for us to drop the "recently" bit, as I'm not convinced it's a proxy that's fair to use for this position.

So personally, I wouldn't take that particular adjective too seriously.

Thanks for reaching out!


ANI/Plaid reminded me of the LabVIEW visual dataflow language, which is quite widely used in the branch of physics I used to work in, for data acquisition and instrument control. While I've often longed for a text-based alternative that plays better with modern version control and my favorite text editors, I have to say that having everything laid out for you in a visual way does make it easier to reason about the execution flow. That is, after a few years of working with it --- initially, this paradigm shift was rather a painful stretch of the nerves.

If every language has its own specific dark patterns and bottlenecks, LabVIEW's is definitely the "brightly-colored spaghetti" structural breakdown of an advanced beginner's code :-)

Incidentally, why do we, as programmers, tend to focus on a language's bottlenecks so much, in such an emotionally charged way? Any psychology-of-programming people out here? You might consider LabVIEW an excellent case study in getting on people's nerves...


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

Search: