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! :)
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.
"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.
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.
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.
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.
Don't want to sound ungrateful, really, but sharing a little more info about the book "before" asking for my e-mail would be nice. A table of contents in the book download page, maybe a small summary.
Adding elements just because (and, above it all, just for styling purposes) is wrong, of course. But having - or forcing - a tight coupling between structure (DOM) and layout/styling (CSS) is also wrong. IMHO, standards should try to move in the direction of decoupling; they did the opposite with Flexbox.
Anyway, the most present case for me is really Angular, where DOM elements are usually added because they are needed (and actually beneficial, if you like a component-based architecture and DRYness). Angular 1.x deprecated the `replace` option for element directives a few months ago (i.e. your <my-directive> will be in the DOM). Also, AFAIK, it never supported the `replace` behaviour in components (which are always elements). This means that, currently, Angular and Flexbox don't play very well together...
> Seriously, HN is a gigantic delicious timesink that has probably cost all of us collectively millions.
It's possible, but what you get back from HN is also enormous; from jobs to interactions with very smart people. I mean, Alan Kay was involved in discussions here, just yesterday!
This is horrible, IMHO. Flex containers will layout the flex items, which are by definition its direct descendants. If by some reason [1] you get an extra DOM element between the flex container and the item you intend to layout, then you're in for a rewrite of the CSS and maybe some extra classes.
After reading the trilogy, particularly the first book, I don't think "The Internet Galaxy" will add much. Even the following "big" one from Castells, "Mobile Communication and Society: A Global Perspective", won't add much from a conceptual standpoint (although an amusing read, I think).
My perspective on Castells is biased because it was essentially the backbone of my academic training. I had teachers telling us explicitly that Castells' notion of information society was the framework (in the Kuhnian sense) on which we'd build upon. Having that in mind, I see Castells as a sociologist and his work (sociological) as a view on a society defined by information flows (not exactly computing, although computing and telecommunications are key enablers). Still, he keeps technological determinism at bay by considering the impact of geography, territory, matter - the physical (tangible?) dimension.
What I like quite much about his work is exactly this aspect: he presents a vision of a society dominated by the intangible, while still dedicating rather extensive chapters on the geographical asymmetries of the world. This avoidance of technological determinism, the "information is key but place and physicality still matter a lot, as evidenced by real-world data" notion is why I see Castells as a great reference.
Castells ideas are indeed presented in a very readable manner, most of the times complemented with figures and data. In my "academic" tradition (communication/media sciences meets IT, in continental Europe), Castells is essentially a mandatory reference (even more than McLuhan).
Thinking about it, from a practical perspective, I'd eventually suggest "The Internet Galaxy: Reflections on the Internet, Business, and Society" instead of the trilogy. It should be more readable, definitely smaller, while still addressing most important concepts (for me, it was the spatial configuration in the information society: the space of flows).
I forgot to consider your list as aimed towards the Anderson Consulting people.
Having that audience in mind, wouldn't Manuel Castells' work (mostly, the "The Information Age" trilogy) be a good reference? Probably a little too vast.
"The Shallows: What the Internet Is Doing to Our Brains" by Nicholas Carr might be of interest to you. And, well, to almost everyone here - your symptoms probably already appeared in one way or another to anyone who's reading this.
Personally, while I consider myself pretty disciplined, I feel deeply frustrated (almost angry at myself) whenever I'm actually trying to focus on something and feel the need to also do/see/check/read something else. Not exactly a facebook feed, but I've come to Hacker News while reading. I don't know what's the most commonly accepted definition of addiction, but this certainly feels like it.
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/