RonSijm

No. I know this because a couple of times my license expired, and 30 days before it does you'll just get a little warning in the IDE - or in tools like Resharper. After that it just stops working.

I remember this post like it was yesterday, and she didn't have her shit together at all.
All she had was a Z-sphere dragon in ZBrush poorly photoshopped on top of a lumion render, and an overambitious idea

Sure, but testing usually purely relies whether your assumptions are right or not - whether you do it automatically or manually.

Like if you're manually testing a login form for example, and you assume that you've filled in the correct credentials, but you didn't and the form still lets you continue, you've failed the testing because your assumption is wrong.

Like even if the specs are wrong, and you make a test for it, lets say in a calculator Assert(Calculate(2+2).Should().Equal(5) - if this is your assumption based on the specs or something, you can start up the calculator, manually click through the UI of the calculator, code something that returns 5, and deliver it.

Then once someone corrects you, you have to start the whole thing over, open up the calculator, click through the UI, do the input, now it's 4, yay!

If you had just written a test - even relying on a spec that was wrong, it's still very easy to change the test and fix the assumption.

Also, lets say next sprint you'll have to build a deduct function in the calculator, which broke the + operation. Now you have to re-test all operations manually to check you didn't break anything else. If there were unittests with like 100 different operations, you just run them all, see they're all still good, and you're done

He's already pointing out the problems himself:

The difference is that Spotify is a for-profit corporation. And they have to distribute profits to their stockholders before they pay the musicians. And as a result, the musicians complain that they're not getting very much at all.

Yea, so at Spotify the profits are distributed "equally" - meaning Taylor Swift with 1 billion listens per month gets 99.9999% of the profits, [[Obscure metal band]] with 100 listens gets $0.001. However, if I only listened to [[Obscure metal band]] and nothing else, shouldn't my entire $5.99/month go to [[Obscure metal band]]? And not be pooled with stuff I didn't listen to?

How would this work with a "Post-Open software administrative organization"? Ubuntu has 1 billion installs, my [[Obscure open source library]] is used by a couple of companies, and it's the only "Post-Open software" that those companies use - Do I get that 1 percent of their revenue? Or does administrative organization siphon it away, keep 0.1%, and send the other 0.9% to the top 10 "Post-Open Projects"..?

Companies would have to publish which "Post-Open software" software they're using, and to what extend. For example, if Ubuntu would be Post-Open-software, it uses loads of inner projects and libraries, which again use more and more libraries, some might being Post-Open software. You'd have to create a whole financial dependency tree per company to determine how to distribute their revenue fairly

I manually redraw my service architecture because I can create higher quality documentation than when trying to auto-generate it.

But you can get a baseline depending on which Cloud you use. For example, in AWS you can use workload discovery - that generates a system overview.

Bonus (optional) question: Is there a way to handle schema updates? For example generate code from the documentation that triggers a CI build in affected repos to ensure it still works with the updates.

Yes, for example, if your build server exposes the API with an OpenAPI scheme, you can use the build server to generate a client library like a nuget or npn.

Then in the API consumer you can add a build step that checks if there are new version of the client library. Or setup dependabot that creates PRs to update those dependencies

I don’t know when it happened or if it was always like this

Well it happened when Unity changed their license to a money grab license that everyone hates. So now the meta is just fuck-everything-unity

It's not really a rug-pull in the usual sense though - of "all of a sudden you cannot use this product anymore"

You can still use it up to the commit where they changed the license. And then people just make a fork from there and the community moves away from the initial project to the fork

The month before Dwarf Fortress was released on Steam (and Itch.io), the brothers Zach and Tarn Adams made $15,635 in revenue, mostly from donations for their 16-year freeware project. The month after the game's commercial debut, they made $7,230,123

So about $16k on a 16-year project = $1k a year. He seems to be doing well after the paid release. So not really a success of "free software"

Well TAI stands for International Atomic Time and "international" generally pertains to Earth-bound locations.

Coordinated Universal Time sounds like it has a bigger inclusivity scope

Otherwise we'd have to rename TAI to "Intergalactic Atomic Time"

Sure, we can compromise; they can have their own timezone, but it has a constant time value.

const moonTime = DateTime.Utc.MoonTime

Cool thanks, I never heard of that one before, I'll try it out

Get Sourcetree