90 karma · joined January 20, 2015
So, as long as the conversation is about the colour of the sky, (or about green things) you can just answer it.
Homegrown python code (i.e. not a library), very nicely laid out. And would form a good basis for more experiments for anyone interested. I think I'll have a play around later and try and train my intuition.
If the employer can claim back GST (currently 10%) on the original purchase, the formula for G becomes G=1/(1-R)+(1/11)/R. To account for the extra 10%/110% that the employer can claim back.
Still as another response noted, almost all of the examples are success stories of medical science, so I don't know if there is a wider point of "medical science/practice is slow to notice these nuances" or if it is just a collection of cool examples of "hey: sometimes doing a single treatment MOAR/multiple treatments simultaneously has a counter-intuative result, isn't that neat."
At work we tend to create backronyms for/from the cute names which is our way of having our cake and eating it too.
[0] https://youtube.com/watch?v=y8OnoxKotPQ&si=EnSIkaIECMiOmarE
You can also send from any address, but I agree that the UI is a bit hidden. You first choose from the from-address dropdown "*@my-domain.com", and then a new textbox appears where you can type what address to send from. As another commenter pointed out, if you are replying to an email it will automatically fill in the custom from-address, but you can overrule it.
But I have also had the joy of trying to program IronCAD. The parametric solver is not as good as the other programs (who live and die by it). I suspect, though cannot prove, that the little automation system we used to create a base design would have been a lot more stable running on a different system. But it was too much work to completely re-implement (and convert all the old designs etc.). So I had the joy of fixing changes between versions by e.g. swapping the direction of a constraint, or hard-coding an initial offset so that you approach a solution from a particular direction.
Also, adding 2D annotations to create a production drawing were painfully slow and finicky in IronCAD.
I think I agree with the author that history-based editing caused the whole industry to go down a less-efficient path, but I also think it's too late to change the past now.
Lego Star Wars is fun, but is exactly the same game as all the other Lego tie-in games.
If you cast and polish a bronze mirror with raised letters/shapes on the back, the very slight deformations caused by polishing over the different thicknesses will create an image in the reflected caustics, despite the fact that the mirror appears smooth when using it as a mirror.
Prophet solves a broad class of easy problems that a lot of ordinary businesses have: you have several years of basically regular data (sales or page views or store foot traffic) that you know has yearly/weekly/daily (if you have sub-daily data) cycles, and you want to give a reasonable prediction to the business so they can plan for the upcoming week/month/year. And you want to remove the periodic effects so you can see the underlying trends.
Imagine someone, lets call them Bill, who might be called a data scientist, or business analyst or just assistant operations manager, for a medium-large business. Bill has the last 5 years of sales/views/traffic data in the database (anything before that is in a bunch of excel spreadsheets on the share drive), and knows just enough python to be dangerous. Bill can probably explain an R-squared value but is not an expert at statistics by any measure. He wants to fit the data, but has several problems:
1) the weekly trend does not line up with the yearly data, as the year starts on a different weekday.
2) Those damn public holidays, some of them occur on a specific date, some of them on the "first Monday of the month", and some of them seem to change almost randomly year-to-year.
3) The reporting system was down for a couple of weeks in June and Feb last year, and the numbers for the first few years were copied from excel, so sometimes are missing the first or last day of the month.
Prophet comes by default with yearly/weekly seasonality. Prophet comes out-of-the-box with a simple way to import holidays, and even a way to specify your own. Prophet doesn't require any cleaning, or special procedures to deal with missing data. And it is quick and easy to use, and get nice-looking, broadly reasonable graphs out (with the above mentioned, consistent data). And that solves the business problem.
And Bill's probably heard of it because it is (a) popular already, and (b) has Facebook's name attached.
That's my take as to why, even if it is not even close to the most accurate method, Prophet is so broadly popular.
[1] https://hackaday.com/2020/09/02/an-up-close-look-at-the-firs...
The photographer may be in breach of Twitter's ToS for enforcing their moral rights, but that would not _stop_ them from enforcing their rights. In this case, the initial post to twitter was not from the photographer, but someone else. So Twitter likely has nothing to hold against the photographer.
I'm not sure why it is the retweeters, rather than Twitter who are responsible for the automatic cropping that occurs when you retweet. But I neither a Lawyer nor a Japanese Copyright expert.
If names fit well with what a person already knows, they can aid memory and even impart understanding. If names are poorly chosen they can instead confuse.
Can you do better in theory, yes. Have we seen any evidence that various US election bodies can do better through using electronic voting, no. The exact opposite in fact.
It's similar to passwords: writing down all your passwords in a notebook and keeping it in your desk draw is a bad idea. But it's usually significantly harder to break into millions of desk draws than to break any given site's security.
Looking at other comments, it seems that we're a little weird down under and most places don't track the drift.