Overleaf builds modern collaborative authoring tools for scientists --- like Google Docs for Science. We have over six million registered users from around the world. Our primary product is an online, real-time collaborative editor for papers, theses, technical reports and other documents written in the LaTeX markup language.
We are looking to hire an enthusiastic Product Manager to join one of our new multidisciplinary teams. You will take ownership of researching, understanding and developing a part of our customer journey, shaping up its roadmap and defining how to measure success. You will also lead on projects related to your area of expertise from start to finish.
Some reasons you'd enjoy working with us:
- We’re very much user-centric. We use mixed-methods research to inform our product decisions, assess our solutions and, in general, to keep in touch with our user base
- You will have autonomy whilst being part of a cross-functional team of designers and developers, with whom you will work closely to help our users create their best work on Overleaf.
- Working hours can be flexible to your needs. Our core hours are 2pm--5pm UK time. Applicants in the US, Canada and UK/EU are preferred.
- Remote is a first class citizen; even before the pandemic, all founders and employees worked remotely. When we can do so again, we'll get everyone together in London a few times a year for valuable face to face time.
Much like IanDrake said, this is super cool but kind of "primes" the user into thinking that he'll be able to play around with the code while paused. It'd be great if you supported that, e.g. by doing a "fork" into local storage.
Anyway, the project is really great and impressive! :)
"1. Calories in, calories out is the golden rule."
Yes, but I'd argue it's not a very helpful rule. As it has been said before, it's pretty much like saying that the golden rule to get rich is "money in vs. money out". Correct, but not very helpful.
How is it unhelpful to be told what you need to do?
Are you saying you need more specifics?
If you want to improve your financial position, either earn more money (get a side job, take a higher paying job with more responsibility), or spend less money (buy beans and rice in bulk, prepare your own meals, sell your luxury car to get rid of the payments and drive a paid-for beater, take public transit and read a book on your commute instead of driving a car).
Similarly, to lose unhealthy weight, either reduce calories in (stop drinking sweet sodas and eating candy bars, order 500-800 calorie items from appetizer menus instead of 2000 calorie entrees) or increase calories out (exercise, take the stairs instead of the elevator, walk instead of ride, lift weights to improve resting calorie burning.)
But it's hard to come up with specifics that apply to everyone, since everyone is different. That's why we just say the general rule, instead of assuming people have an expensive car to sell or go through a 2 liter of Coke a day.
Sure, you're right. I just meant that the real challenge is how to skew (and keep) the balance in the direction you want, in a sustainable, significant and achievable fashion.
That is the worst analogy I think I've ever heard. A better analogy is, if you want more hard drive space, stop installing stuff and/or delete more stuff than you install.
This is not complicated. The calories are listed on everything you eat. Eat fewer of them until you start losing weight.
Had some experience with it in BigCorp™. I don't love it, but it works. It's just a plugin that will install node (and npm), run `npm instal` and then run the specified gulp task.
The good part is that it's not that bad to fit within the company infrastructure, particularly if it's a BigCorp kind of thing. It's interesting because it allows you to play well with CI processes and quality rules - I'm thinking about tests here. With this kind of setup, you can make the front-end build fail if e.g. code coverage drops below a given threshold, using the same setup you use for other components.
The boring part is that it's yet another place to put config info. A particularly ugly one which reeks of over-engineering IMHO. Also it's XML; XML isn't quite the song of the front-end people, at least config-wise. :)
In Portugal, it seems to be coming from the rental market. In the sense that there's been an increase in tourism and the increased demand for short-term accommodation is being fulfilled with properties which were previously for longer rentals.
> In Portugal, it seems to be coming from the rental market. In the sense that there's been an increase in tourism and the increased demand for short-term accommodation is being fulfilled with properties which were previously for longer rentals.
This has happened in Ireland, and especially Dublin as well. With rents increasing by 10% per year, AirBnB is blamed by some for reducing the stock of privately rented accomodation.
If using the :target approach, I actually think it's an appropriate use of CSS and HTML. It's not a stretch to consider a tab as a fragment of the document, which can be accessed using the fragment identifier of the URI. After this, hiding the other fragments while showing the target one can also be considered a style choice which is, adequately, achieved via CSS.
Probably people will end up using JS for this, and that's OK, but I really think this approach actually fits the way standards "define" HTML and CSS.
In Portugal, we have some "theoretically" restrictive labor laws, supposedly very protective towards the employee. Still, everyday you'll hear about someone being told that he/she should feel lucky to even have a job, let alone a salary (because, yes, unpaid stuff is also common).
My point being: labor laws are fundamental, but they don't trump a) on one hand, a bad economical situation; and b) on the other hand, a die-hard culture of constantly finding ways around the law.
This, especially the second point. It does not really matter how protective labour laws are when specialist market is small enough for the option of not signing mutual contract termination agreement and waiting to be laid off by employer would be too risky and detrimental to further career path. Word of mouth is very powerful ally for higher pay grade specialists.
Personally, I thinks it's way, way past any acceptable measure to improve positive thinking and engagement. It's closer to a shock tactic than to any new-age/*spiritual "put life into perspective" thing.
Overleaf builds modern collaborative authoring tools for scientists --- like Google Docs for Science. We have over six million registered users from around the world. Our primary product is an online, real-time collaborative editor for papers, theses, technical reports and other documents written in the LaTeX markup language.
We are looking to hire an enthusiastic Product Manager to join one of our new multidisciplinary teams. You will take ownership of researching, understanding and developing a part of our customer journey, shaping up its roadmap and defining how to measure success. You will also lead on projects related to your area of expertise from start to finish.
Some reasons you'd enjoy working with us:
- We’re very much user-centric. We use mixed-methods research to inform our product decisions, assess our solutions and, in general, to keep in touch with our user base
- You will have autonomy whilst being part of a cross-functional team of designers and developers, with whom you will work closely to help our users create their best work on Overleaf.
- Working hours can be flexible to your needs. Our core hours are 2pm--5pm UK time. Applicants in the US, Canada and UK/EU are preferred.
- Remote is a first class citizen; even before the pandemic, all founders and employees worked remotely. When we can do so again, we'll get everyone together in London a few times a year for valuable face to face time.
Apply here: https://apply.workable.com/overleaf/j/F8E83AAD79/