Firecracker

Totally understandable! hah I did like three loops through the different definitions to straighten myself out before I got the confidence to reply back. Tricky and inconsistent definitions indeed.

I'd also like to celebrate that we can have learning exchanges like this on HN! That's awesome. Thanks for all the great things you've brought to the conversation rojeee!

Plus, nothing like that with a dose of zero-indexed irony :) Looks like CS isn't alone in the zero-indexed world.

Looks like the bitcoin comment got killed, but I want to revive an interesting point at the heart of it:

Big monetary swings like this do bolster the case for it as an inflation-resistant value store...like gold (or stocks), both of which have risen quite a bit this year.

Great question! It does indeed.

If you want to see, can click the gear in the upper right on the site. Then format. Then check the log box. No URL scheme, unfortunately, or I'd link it for ya.

Three reasons often given:

(1) Gives an incentive to deploy money. "Use it or lose it." This stimulates investment and consumption.

(2) Some prices are "sticky down," like wages; people respond much better to nominal wage increases than pay cuts. Inflation lets these prices be adjusted down more easily if needs be.

(3) Stealth tax, not only on the holders of dollar-denominated wealth but also because inflation (a) pushes people into higher tax brackets and (b) creates more taxable "capital gains". If you're a politician, it's nice to be able to pass repeated tax cuts, even as government expenditures continue to grow as a fraction of GDP.

All that said, relatively stable price levels are important. Without them, contracts get tricky, particularly around inventory or agreements into the future.

Absolutely! Countering the deflationary pressures to keep price levels stable (and fixed contracts reasonable), would be another way of looking at it, I think. They're doing their job!

The question is, politically, can they be so responsible in contracting the money supply thereafter? Hopefully!

Doesn't M1 exclude bank reserves?

Edit: Indeed. M1's definition: "M1 includes funds that are readily accessible for spending. M1 consists of: (1) currency outside the U.S. Treasury, Federal Reserve Banks, and the vaults of depository institutions; (2) traveler's checks of nonbank issuers; (3) demand deposits; and (4) other checkable deposits (OCDs), which consist primarily of negotiable order of withdrawal (NOW) accounts at depository institutions and credit union share draft accounts. Seasonally adjusted M1 is calculated by summing currency, traveler's checks, demand deposits, and OCDs, each seasonally adjusted separately.

I agree with this line of argument for the 2008 era quantitative easing! But my read is that M1 explicitly excludes bank reserves, so the M1 created can't be locked-up reserves, right?

Indeed!

Definitely a good factor to know about, but there's also been a huge surge in things like Monetary Base (currency in circulation+reserves) [0]. Looks to me like there's a lot of (effectively) money printing behind this, not just an artifact of M1's definition?

[0] https://fred.stlouisfed.org/series/BOGMBASE

Would Read the Docs suit your needs?

https://docs.readthedocs.io/en/stable/

Hey HN Friends,

I'm posting this because I was shocked when I saw this graph. I hadn't previously appreciated just how much of an unprecedented explosion in the money supply there'd been this year.

In particular, it seems to quantify a lot of potential for long run inflation and a very expansionary monetary policy move required to prop up the economy during the pandemic. But I'm not an expert here; I'm hoping we can put our heads together. I'd be very curious to hear general discussion and insights into the dynamics. Let's go, community of systems thinkers :)

While the M1 measure of money shows the change most dramatically, other ways of looking at the same data (dollars printed, M2, MZM, etc.) seem to tell the same story. There have also been some news articles written, but I thought that for HN, we'd go directly to the numbers.

Thanks for taking a look!

My friend and I hacked on something like this for a while, and eventually got something pretty accurate for measuring heart rate. Shipped on iOS as [0].

It did indeed require a lot of additional tweaks and benchmarking. Honestly don't think any part of our original algorithm or the tricks in the paper made it into the final version. Just doing a Fourier type thing works rarely (~20%), but the principle does work; you can get it working ~90% of the time. That said, I'd be surprised irregular heartbeat were doable in a short recording period. But I'd love to be surprised!

[0] Hands Free Heart Rate Monitor (free, private) https://apps.apple.com/app/id1457939511

Fluffy, could I ask you to give a few more details about how you set this up? Sounds interesting!

Just wanted to say: This is the best, most thoughtfully worded mod guidance I’ve read anywhere on the web. Thank you!

We've tested across quite a few--and it should control for constant, weird lighting.

But there are definitely edge cases that are hard to control for--a faint, pulsing red light would probably be the worst one.

Stanford requires such a course!

Counteracting some of the comments below:

My experience using buckaroo in a large project over the past year has been extremely positive, and I'd say addresses most of the problems raised here. It's far and away better than anything else I've used.

NVIDIA has mac drivers for their whole consumer line. For example https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10...

My best experience with a build tool has been FB's Buck (buckbuild.com), half for it not limiting you to just C/C++, and half for buckaroo (buckaroo.pm) making installs of common packages--like protobuff--easy.

I find that the second limiting factor I hit is being able to easily interop with other languages and to cross-compile for other platforms. Buck makes that super easy, too.

Any word on why the Stanford class is marked as closed to signups?

Try going to makegameswith.us! That's where I learned.

Right, but particle effects and all the other scenery look better in motion too... You're right though. It would certainly be better to show only the edges of it so it looks less like a pattern.

Thanks Matt! I'd like to think that I'm putting what they taught me to good use.

I actually ended up using Kobold2D for the final app since it uses automatic reference counting. It works pretty well, but in my experience with tilemaps, somethings can be broken and require workarounds.

It has actually only been out for a few days. It was free for the first couple, and the app made it into the top 50 puzzle games in the US and onto charts in some other countries. Following that, I decided to make it paid. The numbers for paid downloads are still rolling in, but it looks promising.

I connected with makegameswith.us through high school. I first learned to program in a class freshman year.

With regards to this project, I'm considering making a sequel and an iPad version. Otherwise, I'm pretty busy at the moment, but I have an idea for a bigger mobile project that I'm not ready to unveil just yet...

Both the founders are alumni from my high school, so that's the connection that started us working together. I was one of their alpha testers, so I got 100%. Even so, I would say that 30% is more than reasonable considering that they provide the art and promotion. It would be easy to get lost in the sea of apps already out there, and their promotion really helped my game get noticed.

Thanks! The app store really is an awesome marketplace for creations that might otherwise go unnoticed.

For sure! They helped guide us through the process of learning Objective C with Cocos2D, and lent a hand if we ever got too stuck. Also, they provided the art to complement our code and published the game out on the app store.

I got help with the art and with learning Objective C from makegameswith.us They were awesome in making the whole thing possible.

Roughly 3-4 months. I was taking classes at the same time, so I worked about an hour a day.