148 karma · joined May 27, 2021
https://www.alprwatch.org/
I see in-person work as one of the only opportunities for scheduled casual interaction. Mandatory fun time is not a real solution, but the fact that exists often speaks to the perception that casual interaction is an essential part of building a team.
I liked the work and really enjoyed getting to be a consultant on many projects. Turnover is massive among the researchers because there are few permanent positions, and most groups are heavy on postdocs since graduate students tended to be primarily on campus (UC Berkeley).
If pay is a concern, look closely for the open databases of salaries. At LBNL there is the "book of tears" at the library under the cafeteria, listing every employee and their salary. The exact amount you get varies wildly with the department: prior to unionization in 2016, the range was from 20k to 125k annual salary for postdocs. I hear they raised the floor to NIH levels at least, but I assume they did not make NERSC take a paycut.
Part of the point of the PhD is learning how to approach problems that have no established solution, and someone who lacks breadth or depth will likely find it challenging to be a professional researcher.
Otherwise, robustness is relatively expensive because it requires the organization to value the long-term quality and function of the system, at the expense of short-term velocity and malleability. If you are competing with others who can hack together an MVP with 90% functionality overnight, then waiting for the engineered product may be problematic.
I treat equity as zero cash value, but that makes it worse because the company is now clawing back something worthless!
That said, I find the whole concept of vesting cliffs to be a bit of nonsense. Vesting I can understand, but why set these cliffs when they are not explicitly tied to regularly-scheduled reviews, performance, or some other checkpoint?
It is sort of like learning C but programming solely in Python: you can get your job done, but when one of your abstractions breaks it is worthwhile to be able to at least identify the root cause and talk to the right people.
Yes, in that that you have to sell yourself carefully. "I solve any problem" is not generally reassuring, because it is always an approximation, and because a specialist might see the pitfalls of a particular approach earlier. Given time you will become a specialist in whatever tool, but that needs to be built into projects or your professional development budget.
One of three in a short period
There are some tools which do this. scite.ai has proven okay for quickly finding some of these citations, sometimes. Nothing beats manually digging in, though.
1. What are the actual claims made by the authors? That is, what do they claim to have found in the study? If you cannot find these, there is a good chance the paper is not particularly useful.
2. For each claim, what were the experiments that led to that decision? Do those logically make sense?
3. Are the data available, either raw or processed? Try reproducing one of their more critical figures. Pay close attention for any jumps in series (e.g. time suddenly goes backwards -> did they splice multiple runs?), dropped data points, or fitting ranges. If the data are not available, consider asking for them. If the code exists, read through it. Does the code do anything weird which was not mentioned in the paper?
4. How do they validate their methods? Do they perform the appropriate control experiments, randomization, blinding, etc? If the methods are so common that validation is understood to be performed (e.g. blanking a UV-Vis spectrum), look at their data to find artifacts that would arise due to improper validation (e.g. a UV-Vis spectrum that is negative).
5. Do they have a clear separation of train and test / exploration and validation phases of their project? If there is no clear attempt to validate the hypothesis for new samples, there is a good chance the idea does not transfer.
That said, I have also witnessed plenty of low-level fraud: changing of dates to match documentation, discarding "outlier" samples without justification or even documentation, etc. Definitely enough to totally invalidate a result in some cases.
Back in the day, Netflix's DVD library was close enough to complete that there was little need to look elsewhere, and their streaming selection was not terrible when it launched. Now that the whole system is fractured, the simple act of finding out who streams your movie is a chore, and in many cases getting it in the original language with proper subtitles is non-trivial.
Create a single point of entry to a high-quality library with minimal friction, and you eliminate the desire to pirate in many people.