1,519 karma · joined March 21, 2010
http://lars.yencken.org/
I want to agree with something you didn't quite spell out: the incentives are not really properly aligned in this kind of industry. You get paid up front, when people are at maximum motivation, but progress takes a long time and many people drop off along the way. Some kind of business model where you get a half-refund for non-usage would be a reasonable compromise for everyone, but I've never seen it in action.
Speaking for the people I know who are involved in this work, they are not cynical. They do this kind of work, instead of other work, since they genuinely want to help people. Our product worked if you stuck at it, so we spent a lot of time encourage people to come back each day and work at their goal. You can take my word about this, or not, as you like.
Something even a cynic would celebrate: there seems to be a push in some parts of the US health system to pay for outcomes (e.g. confirmed weight loss; stopping smoking) rather than processes (e.g. access to an app for losing weight; access to a quit smoking program). That's a really welcome development, it aligns everyone's incentives nicely.
This a pretty cynical and unproductive way to think of meetings, management, and the essential task of coordinating people's efforts.
Isn't it also your responsibility, increasing with seniority, to make sure that the team's time is used well?
As someone who's leaned into Nushell deeply, I can tell you that the tabular and hierarchical data output is the major selling point of Nushell. For me and my team, who work with data and metadata constantly, it's an incredible productivity boost.
The major pains with Nushell are debugging pipelines that are too slow, having to learn the new language constructs, and process overhead for going in and out of Python for other pieces.
That suggests that some of the extra wealth effect in the US is balanced by social safety nets in Europe, when it comes to life satisfaction.
https://ourworldindata.org/grapher/happiness-cantril-ladder?...
All of these countries are pretty wealthy in the scheme of things: https://ourworldindata.org/grapher/gdp-vs-happiness
But... as a lead, I've struggled to train speed before. Some people I've worked with have had it, junior or senior, and some have not.
Has anyone had good experience helping others become faster at their work?
I find it occupies a weird niche where I can do a bunch of data wrangling with it, and some basic exploration, but hit a ceiling where what I've done is less persistent than an ETL and less exploratory than a notebook.
I think a simple personal ETL system based on nu would be awesome, and likewise I want to add cell magic to Jupyter for it so that you can quickly get data into Pandas or data viz of some kind.
It's also magical when you summarise the understanding you've reached back to it, and it can confirm or tweak it for you.
In other ways it's also nice to just pay for it and then to be in an advertising free space.
One critique is that when you ask it to compare things it's often too balanced or too positive/enthusiastic ("both are great for different reasons!") when what you want is a more sober analysis. But you can usually do some prompt management to adjust it back to a reasonable range.
Children are so different, from so early, it's not at all obvious what outcome for a particular kid is because of different strategies taken and what comes from their individual natures, or other aspects of their environment.
Co-sleeping's known to increase the SIDS risk, so it's another reason people are sometimes reluctant to do it, even if it would make the baby more comfortable.
It sounds like the main concern would be starting sleep training too early (sub 6 months), or using it in unusual situations where there are already attachment issues.
At Our World In Data, our mission is to make the world's biggest problems understandable, so that we can take effective action on them. We publish research and data on crucial topics like poverty, disease, hunger, inequality, war and climate change.
The way we do this is especially through our data visualisation framework Grapher (https://github.com/owid/owid-grapher), which powers our interactive charts and our explorers for larger datasets. We're now looking for a senior engineer to join our team and take ownership over this visualisation framework.
We are a remote-first team that spans EU and US East timezones. As a team, we're also passionate, talented, and driven to do work that makes a difference.
Feel free to ask any questions you might have about the role. You can also learn more apply here: https://ourworldindata.org/senior-data-visualisation-enginee...
We're a non-profit that aims to make data on the world's most important problems understandable and accessible to everyday people. During the Covid-19 pandemic, we assembled the reference dataset on Covid-19 vaccinations used even by the WHO. Our typical focus areas are poverty, hunger, disease, war, climate change and existential risk.
We're looking for an experienced product and design leader to join our leadership team and help shape Our World In Data as a publication and data visualisation space.
Read more here: https://ourworldindata.org/head-of-product-and-design
My biggest gripe is the conflicting warnings between mypy and pyright. Language servers use pyright by default in the editor, but I strongly believe a Python project shouldn't require nodejs as part of its required CI toolchain. So all my projects use mypy in strict mode in CI. Basically this means that mypy is the standard to meet, and that there are persistent warnings in the editor which I have to ignore.