I just spent a fair bit of time on this question last week and here is my new setup. (Previously I used a mixture of mendeley with goodnotes and an Ipad pro with apple pencil).
Currently what I have moved to is using zotero on the desktop as the master store. This works well with the chrome and firefox plugins to auto add papers.
I use feedly to monitor RSS feeds for each journal from my phone, and then pull them up on the desktop once every so often to add to zotero. On the ipad pro with apple pencil I use papership to interface with the zotero library. It's annotations are usually good enough, but if I really need to do something fancy, I'll export it to pdfexpert, annotate it, then move it back in.
I disagree. Yes most of what each person says will not apply in any given case, but discussions like this where everyone is just kind of throwing it at the wall can be useful to try and pick out large trends. Plus as people discuss specifics of their workflow, individual threads can become more interesting.
Also the more esoteric workflows can be interesting to hear people describe to put our own systems into context.
While there are some very real issues at Hanford, the issue this week has been vastly blown out of proportion in the media (I work fairly near to the the location). There is a massive amount of work that has gone into detection of any kind of nuclear leak around here.
I think it may depend a lot upon the candidate. I personally feel like I make a pretty good salary, and with many jobs I would otherwise consider applying to, I don't feel like it's worth the time to go through the interview process just to find out their max salary they can offer is a pay cut for me. Similarly if there is a job that looks interesting to me, but advertises it's range and it's in the ballpark of what I want, I would be MUCH more likely to apply.
It also provides a lot of information about what the job will be expected to do. With what I do, people are not going to be willing to give me the salary I want, while also wasting my time on remedial work when they could get someone much cheaper that could do those tasks. So by keeping my interest in higher salary jobs, I can try to limit it to jobs which hold more interest for me personally.
If you google matplotlib viridis there is a discussion of the issue. Using perceptually uniform colormaps(not to mention ones that translate to gray scale correctly) is normally the correct thing to do, but not always. Sometimes you want to highlight particular conditions. For instance, jet with radar data tends to nicely separate different atmospheric conditions if set up right. The same perceptual colormap version feels somehow lacking.
This is interesting, but not as groundbreaking as they make it out to be. People are already using GPS signals to calculate things like available liquid water. For instance, see http://www.suominet.ucar.edu/ .
One of the main problems with something like this is that you get an integrated quantity, with no easy way of backing out the exact elevation this occured at. If you get a dense enough network, sure you may be able to work it back out, but you also don't really get a sense of the drop shape.
For comparison, the most advanced satellite weather system we have is the Global Precipitation Measurement(GPM) constellation. This uses a series of radiometers and radars to provide a much more detailed picture, that also includes 3d data. See http://www.nasa.gov/mission_pages/GPM/main/ for more information.
If you stick to ground radar, you can get even more impressive by using polarization. By transmitting dual polarized signals, we can actually get a measure of the shape of the raindrops(based on the difference in power returned by the two polarizations). The US NEXRAD network recently upgraded it's radars to be dual polarization capable(finally). This also provides us with the ability to differentiate between ice and rain(Something we couldn't, strictly speaking, do before). We can also separate out the signals caused by bugs(which can be a huge issue), as well as other sources of signal contamination.
Maybe not the most sophisticated of pages, but sometimes it is good to get a brief reminder of what might be asked, especially for those of us that are not considered senior yet.
There are two possible scenarios here. Either you are above him on the organizational chart, in which case you probably have the authority to let him go.
More likely(As you're not sure what his contributions are), you are lateral to him on the chart. Possibly try to engage him in what you're working on. Maybe he's not particularly self driven and would value the guidance from someone more senior. If he turns it down, either just ignore it and move on(if it is not affecting you), or if his failure to do work impacts you directly, then complain to your manager. T
Check out northern Colorado. Between Denver, Fort Collins, and Boulder there is a fair bit of tech, cost of living is decently low(outside of Boulder), and you can live right next to a national forest.
I doubt it. You'd have to know the update strategy, as well as the key. Theoretically it's impossible to get the secret out of the device(though in actuality, I doubt that is true).
The M.S. does, but as stories like this become more common, non-namebrand MS programs will start to lose some luster. Being able to point to a publication, or a project you run, or something genuinely useful to at least someone, goes a long way to distinguish you from the people who went to school, but never programmed in their free time, and do it purely as a job. Passion as a buzzword is very overrated in this community, but at least a little bit of it is required to make you stand out.
I'd imagine this goes doubly so for the startup world.
Also the me should be an I, and listed after the others. Though to be honest, most people make the same mistake. Your English is at the level where you can pass off as a native from an English speaking country so I would not worry too much. Everyone has at least a few mistakes in almost everything they write.
I'd say if you can do it in two years, including deficiency courses, and without publishing, you're probably not getting your moneys worth and yes it will be looked down upon. Three years(take a lot of courses) and/or a publication or two will look much better. Of course, if you think you can do extra curricular activities to create a portfolio(github projects, contributing to open source, create a product), then it might not matter how well the MS is looked upon, if you show you have a track record of delivering.