592 karma · joined July 29, 2012
gmail: jdleesmiller github: https://github.com/jdleesmiller/
My last submission was with a new title based on feedback in that discussion thread (that CTO was misleading).
Also, can you clarify how you got to 6? Two of those links are the same, and one of them does not seem to work.
Also, it seems from the comments that github pages (where this is hosted) was down while this was on newest, which seems like pretty bad luck. At least now I know that it may get a second chance without me having to do anything, thanks!
It think it's worked pretty well so far, though we have had a few difficulties:
- Particularly in the early stages of development, we've been changing dependencies a lot, and that requires a lot of image rebuilds. They are very consistent, but also a bit tedious.
- For those of us on macs, using docker machine for development hasn't been all that great, because inotify doesn't work for automatic code reloading (watchify, nodemon, etc.). However, they're hard at work on that with the new Docker for Mac.
I'm hopeful that technologies like kubernetes will make it easier to deploy these containers, too, but I haven't really got there yet. Maybe another article some day!
[1] https://en.wikipedia.org/wiki/Principle_of_least_privilege
It was a somewhat different problem, but FWIW I had more success with the Cross Entropy Method than with Simulated Annealing [1,2]. Maybe one for future research :)
[1] http://jdlm.info/thesis_v11_hyperref.pdf [2] https://www.overleaf.com/articles/minimizing-average-passeng...
I've written several papers in LyX, and I think it was a great way to get started with LaTeX. The main trouble I had with it was collaboration --- since it was a desktop app that not many (possibly none?) of my colleagues used, I couldn't really get anyone else to contribute, except by asking for them to provide text and then mostly manually inserting it back in to LyX.
In the end, they convinced me to just write LaTeX source into an EtherPad, which was fine once I got used to it. And Overleaf is basically just a refinement of this idea.
I hope that Overleaf's rich text mode also helps people climbs LaTeX's notoriously steep learning curve, and I hope it saves them from some of the collaboration problems that I had when I was doing the same. We have some evidence that it is helping, such as these high school students who somehow managed to write a 300 page report in LaTeX using Overleaf [1]. I think that's amazing!
[1] https://www.overleaf.com/blog/289-the-nano-ninjas-building-r...
Freeze Pirates! - DAPS
DSME launched its new pirate alert system 'DSME Anti-Piracy System (DAPS). ... DAPS is a total ship security system for recognizing and eradicating piracy. By using the ship's radar signal, the DAPS is able to analyze image information. This system automatically judges suspected targets based on the analyzed information. If suspected pirate ships approaches [sic], DAPS will warn the target through a high output speaker and sound an alert on the ship. If the pirate comes closer, a sound cannon or water cannon will be used to incapacitate the pirate.
--
In many ways, that is more impressive (and scarier).
Overleaf.com: We build awesome ways for scientists to collaborate and communicate. We're looking for full stack engineers — your projects will span our database (PostgreSQL), web app (Rails, Node), front end (React, Backbone) and infrastructure (Docker, Heroku, EC2, GCP) layers. We also have projects for mobile, if you're into Android or iOS.
To apply, go to https://www.overleaf.com/jobs or drop us a line a jobs@overleaf.com :)
Isolation is definitely one of the main benefits for us. Compared to e.g. a chroot, docker also lets us disable networking and restrict memory etc. for the process in the container. It's another important layer of security.
Another benefit is that the Dockerfile also makes it a lot easier to manage installation of all the LaTeX packages, fonts and various scientific software that we have installed.
The overheads seem to be very low --- less than 100ms extra startup and tear down time, and no significant difference in runtime speed.
I can't say I've used many of the community images. We generally just use the base OS images and install packages as needed. The Dockerfile makes it pretty easy to do.
You can see how it's set up in the github repo for the slides: https://github.com/jdleesmiller/ds-docker-demo
About Us:
We're building 'Google Docs for Science', making science and R&D faster, more open and more transparent by bringing the whole scientific process into the cloud, from idea to writing to review to publication. Our users have already created more than 1,000,000 documents on writeLaTeX, and it is being used in hundreds of universities worldwide for teaching and research.
We're a London-based startup, supported by Bethnal Green Ventures (http://bethnalgreenventures.com/) and founded by two mathematicians who were inspired by their own experiences in academia to create a better solution for scientific collaboration and communication.
We're looking for a full stack engineer:
You'll be working closely with our team to build new and awesome ways for scientists to collaborate and communicate. We're looking for full stack engineers — your projects will span our database (PostgreSQL), web app (Ruby & Rails, Node.js, Meteor), front end (HTML, CSS, Javascript) and infrastructure (Heroku, Linux on Amazon EC2, RackSpace) layers. We also have projects for mobile, if you're into Android or iOS.
You're an independent thinker and fast learner. You're resourceful and knowledgeable, but you ask questions when you get stuck. You take pride in your work, and you ship it early and often, because you love to see it out there in the real world. You learn new programming languages and techniques for fun, and you contribute to open source.
If this sounds like you, send your CV, current salary, and a link to your profile on github/bitbucket to jobs@writelatex.com. We'll get in touch to arrange an informal interview in person if possible, otherwise via Skype/Google Hangout.
This is an immediate vacancy for a permanent position with a two month probationary period. Working arrangements are flexible. The primary place of work will be at our London office.
We look forward to meeting you!
In the mean time, we try to auto-detect which engine to use, so if you load the fontspec package, for example, we'll automatically use XeLaTeX.
It's also worth noting that you can use accented characters with pdflatex: adding \usepackage[utf8x]{inputenc} at the top of your preamble will usually do the job.
If none of that helps, feel free to send us the link to the doc via https://www.writelatex.com/contact and we will have a look.
EDIT: english
https://www.writelatex.com/examples/chinese-a-visit-to-qiant...
https://www.writelatex.com/templates/deedy-resume/sqdbztjjgh...
I've made a few minor mods to get it compile on Linux --- mainly using Liberation Sans instead of Helvetica Neue, and a few other minor fixes.
Matlab: it takes way too much Fortran code to solve Ax=b
Octave: Matlab is closed-source (and expensive)
Julia: Matlab was designed by people who knew a lot more about numerical analysis than programming language design
Python + SciPy: you don't actually need a whole new language just to solve Ax=b
TeX: it's taking too long for people to typeset my books