9,188 karma · joined July 27, 2009
mali at akmanalp dot com
Gutenberg link: http://gutenberg.net.au/ebooks09/0900131.txt
We're a research center (https://growthlab.cid.harvard.edu/) that focuses on the question: “Why do some countries grow while others don’t?”, and we study issues of economic development. We have people from a wide set of backgrounds, including economics, public policy, computer science, mathematics. Our center often works directly with counterparts in different government organizations across the world. Our software team is a is a small one (5 and growing) embedded within the larger organization of researchers and data scientists. Our audience is policy makers, researchers and economists.
Our data visualization tool (http://atlas.cid.harvard.edu) just got shortlisted in the Information is Beautiful awards, and we're working on an even larger new section that adds a storytelling-style profile for every country in the world, where we guide you through the process of what your country currently makes and what it could be making in the future, while making some of the more technical concepts more approachable.
Frontend stack: React / Typescript / Webpack / Node / D3
Details here: https://sjobs.brassring.com/TGnewUI/Search/Home/Home?partner... or E-mail annie_white at hks dot harvard dot edu
https://fred.stlouisfed.org/series/MEHOINUSA672N
The story here is quite different - only a 19% increase, and much more unstable over the years. Most of the increase happened before 2000. Almost no change since then.
It's 5-6 lines of code per chart for most examples here, with a few more lines for interaction (e.g. selection and linked brushing across graphs).
That said, I understand it sucks to build on top of someone else's code only to have it be discontinued, but honestly it only takes a few minutes to judge a project's maturity. Here are some very easy rules of thumb. Don't write a lot of important code relying on a library that:
- Is younger than 3 years old. - Has less than 3-4 major contributors and 20 overall contributors. - Has lost steam: a lot of issues and pull requests open and stale with no triage tags, no discussion or responses. - Doesn't seem to have any automated testing / packaging infrastructure set up. - Doesn't seem to have a regular ongoing cycle of releases, be it long or short. - Doesn't have nicely laid out documentation. - Doesn't seem to have a user base, as indicated by a preponderance of questions and answers on stackoverflow, etc. - Just posted their "we made a cool new thing" post on HN a few weeks ago.
Yes, the cutoffs are arbitrary (and flexible!), but this hasn't failed me yet. The python world is filled with many wonderful and mature libraries. It just also has a lot of up and coming, promising young ones. Use whichever!
[0] https://atscaleconference.com/videos/scale-2018-run-your-dat...
Well - sorta. Cluster FS just means disk I/O is now network I/O (EBS is a bit like this). Now you push the hairy problem to a different area: your network topology starts to matter a lot. You might end up having to think about not scheduling too many I/O heavy jobs behind the same switch or something. AND disk I/O is now competing with network I/O. AND it might now be hard to predict the destination of where all that I/O is going to be when scheduling the job, whereas previously it used to just be local.
So the problem doesn't go away. But maybe you say it's just easier to wire everything up with gigE / infiniband so that you're massively under-capacity, and call it a day, and that might be a fair tradeoff.
a) Just like with a paper, you can present scientific or mathematical ideas with accompanying visualizations or simulations. From the REPL side, as a bonus, you get interactivity, and the reader can pause and experiment with the examples you're giving to improve their understanding or test their hypotheses. If I change this variable, how will the system react? You can just try it!
b) Just like with a REPL, you can type in and execute commands step by step, viewing the output of the previous command instead of running the whole thing at once. From the document side, as a bonus, you get nicer presentation (charts, interactivity, nice and wide sortable tables, etc) than you would in a shell, which comes in handy when doing things like data exploration or mathematical simulation.
It's decidedly NOT there for you to type all your code in like an editor and make a huge mess. It's apples and oranges w.r.t and a poor substitute for something like PyCharm or VS Code or vim. It is there for you to a) try things out yourself, and whatever you discover hopefully eventually make it into proper python modules b) make interesting ideas presentable and explorable for others. That's all!
When I see stuff like "out of order execution is confusing", I don't disagree, but it does make me wonder how long and convoluted the notebooks these people work with are - probably a ripe candidate to refactor stuff out into python modules as functions. When I see stuff around notebooks for "reproducibility", I'm a bit confused in that notebooks often don't specify any guidance on installation and dependencies, let alone things like arguments and options that a regular old script would. In that regard I think it's barely an improvement over .py files lying around. When I hear "how do I import a notebook like a python module", I'm very very scared.
Granted, I've seen huge notebooks that are a mess, so I understand the frustration, but it's not like we all haven't seen the single file of code with 5000 lines and 10 nested layers of conditionals at some point in our lives.
Article #2 (doi 10.1097/jcp.0000000000000615) is a meta-analysis that seems to not have Kasper in the author list, but then if you read the full article you'll see that every single one of the studies they analyze minus one are all Kasper's!
Isn't this super shady? How is any of this kosher????
----
And the Kasper meta-analysis I mention above was funded by the makers of Silexan:
> The research presented in this paper was funded by Dr. Willmar Schwabe GmbH & Co. KG, manufacturer of Silexan, who was also the sponsor of the trials included in the meta-analysis. The statistical analysis plan for the meta-analysis was conceived and the analyses were performed by the biostatistical department of Dr. Willmar Schwabe GmbH & Co. KG under the responsibility of co-author SS. The company also provided the raw data of the trials included into the analyses. A first draft of the manuscript was prepared by Andreas Völp, Ph.D., an independent medical writer who was reimbursed by Dr. Willmar Schwabe GmbH & Co. KG, who also independently performed the risk of bias assessments. Open access funding provided by Medical University of Vienna.
And of the other authors:
> Hans-Jürgen Möller has received grant/research support, consulting fees and honoraria within the last years from AstraZeneca, Bristol-Myers Squibb, Eli Lilly, GlaxoSmithKline, Janssen Cilag, Lundbeck, MSD, Novartis, Organon, Otsuka, Pfizer, Schwabe, Sepracor, Servier, and Wyeth. Hans-Peter Volz has served as a consultant or on advisory boards for Astra/Zeneca, Eli Lilly, Lundbeck, Pfizer, Schwabe, Janssen, Otsuka, Merz, Wyeth, neuraxpharm and has served on speakers’ bureaus for Astra/Zeneca, Eli Lilly, Lundbeck, Schwabe, Janssen, Merz, Wyeth, Lichtwer, Steigerwald, Hormosan, neuraxpharm and Bristol-Myers Squibb. Angelika Dienel and Sandra Schläfke are employees of Dr. Willmar Schwabe GmbH & Co. KG, manufacturer of Silexan. Siegfried Kasper received grants/research support, consulting fees and/or honoraria within the last 3 years from Angelini, AOP Orphan Pharmaceuticals AG, AstraZeneca, Eli Lilly, Janssen, KRKA-Pharma, Lundbeck, Neuraxpharm, Pfizer, Pierre Fabre, Schwabe and Servier.
[0] https://link.springer.com/article/10.1007/s00406-017-0852-4
Update: OK, weirdly enough, Tisserand seems to be highly involved in the aromatherapy industry per their own website, and the study [0] seems to involve researchers from the "Research Institute for Fragrance Materials" which sounds suspiciously like an industry-related group - is this reputable at all??
[0] http://journals.sagepub.com/doi/abs/10.1177/1091581812472209
a) The code editing story was a bit nicer (better resolution / builtin support for external editing and reloading etc)
b) If there was some kid-specific introductory game programming content for it (even "type all this in and play around with it after" worked for me as a kid)
Also you might also like tahin pekmez - which I haven't seen around at all yet: 3/4 tahini and 1/4 molasses mixed together for a spread - on toasted bread. Best warming winter / snowy weather comfort food ever! :-)
Classical Turkish Cooking by Ayla Algar is, well, a classic. People often think the recipes aren't descriptive enough. But also it's quite comprehensive and has a lot of history too.
Aegean Flavors by chef Didem Senol is a wonderful take on aegean cuisine in Turkey - highly related to greek food.
Oklava by chef Selin Kiazim is a bit more of a modern / upscale restaurant take - she runs one.
Claudia Roden's book is not only about Turkey but quite great.
Hope this helps!
Just don't get the boxed stuff, and get a lot of variety of flavors. Also I seem to be the only person who hates the rosewater, but maybe that's just me.
For baklava, it's really a labor of love and there's a lot of great old and small shops. Gulluoglu used to be great and is still quite OK, but feels a but mass produced now. Smaller options are Köşkeroğlu, kafadaroğlu etc, but I don't know if it's worth seeking out especially - just duck into whatever small shop that seems busy during the day.
Probably what might be a better experience is trying /unfamiliar/ desserts: Kunefe is crispy shredded puff pastry with cheese in it, doused in syrup, served HOT with pistachio on top. Tulumba is the turkish take on churros. Halva is made of tahini and sugar, and is getting more popular in the US. Kazandibi is pudding that's been caramelized / burnt at the "bottom of the pan" - traditionally the gelatin in it comes from chicken breast (you can't taste it). More often it's now the "fake" version, still delicious. Lokma is turkish fried dough. Kabak tatlisi is made of pumpkin. There's so much to try, just get the stuff which you don't know what it is.
One thing to remember is that Turkish sweets are quite sweet - you're only meant to have one small piece. Of course that won't stop many of us from getting a whole plate :-) Usually you can ask for a half portion at a shop.
Finally if you're near Kadikoy, hit up Ciya too - regional foods from across Turkey that you can't find in many other places.
Hope you enjoy your trip!
Iraq http://atlas.cid.harvard.edu/explore/network/?country=108&pa...
vs
Vietnam http://atlas.cid.harvard.edu/explore/network/?country=239&pa...
Each node here is a specific product being exported "significantly" for a country of that size.
---
So by a similar argument you could look at how similar the population that goes in and out of unemployment (seems likely to me) is every year, and what that implies about policies and job opportunities in the US.
e.g. the BLS already releases all manner of alternative unemployment statistics (see "discouraged workers"): https://www.bls.gov/news.release/empsit.t15.htm
e.g. for income inequality, a crude but well known measure is the Gini index which measures how dispersed incomes are in a population: https://fred.stlouisfed.org/series/SIPOVGINIUSA#0
e.g. Consumer price index is another approach measuring access to basic goods: https://www.bls.gov/charts/consumer-price-index/consumer-pri...
Household net worth is another one that the article mentions.
The matter of which number is chosen as the official measure of "goodness" is the real issue and that is a political matter, and because depth of public (and shockingly often policymaker!) discourse on the matter is stuck at "did the thing go up or down". I'm dubious that switching to a different indicator will solve the problem per se - perhaps make it harder to game.