Curious about how the business responds to workers leaving/joining. I expect that a worker wanting to leave needs to find someone to buy in, and the new worker has to be approved by the collective. This sounds like a recipe for inflexible departure.
Next, expansion. I expect expansion is a tricky proposition because it means dilution, which is both a hard sell and a risk to the workers.
The worker leaving doesn't have to find someone else to buy in. They just leave and receive the value of their investment. The cooperative finds someone else to buy in. Usually there are lots of people looking to do so.
People save up for years so they can apply to buy in and work at Mondragon.
Trulia Rentals | Real Estate, Payments | Senior Full-Stack Software Engineer | ONSITE (SF) VISA | Full-time | Salary Equity Full Benefits
We're a nimble team building brand new services in the rentals space designed to make the process of renting your home easier for renters and landlords. Or, demystifying as described by the Verge: https://www.theverge.com/2018/7/31/17634762/zillow-apartment.... We develop products to delight our users, and I think the numbers speak for themselves: 56 million visits over the last 6 months as reported by SimilarWeb.
I had a similar experience. I wouldn't say it directly led to my career (but certainly influenced) as a software engineer, but it did shape the way I view the world.
Ultima IV: The Quest of the Avatar taught me about an alternative set of ethics. While too simple for real use, it was aspirational enough to get me thinking about alternatives to what I'd been taught.
Ultima VI: The False Prophet led me to acknowledge good and evil typically are informed by individual (or group) point of view.
Ultima VII: The Black Gate taught me to look at religion critically, to see that beyond the surface message there are often other messages that go unnoticed.
There's no question that Garriott tapped into something deep inside me that is still coming out to this day.
I discovered TiddlyWiki almost a year ago when I was looking for a way to replace my tabletop RPG notes system. I was blown away how with how useful it is for my workflow. Friends picked it up for the same purpose, and others. Kudos team.
But isn't a large amount of debt that isn't transitioning whether by getting paid back or written off by the creditor bad for the economy? I'm no economist but my intuition is that these unmoving debts represent money that should exist but doesn't. Since student debt is unusual in that it can't be discharged by bankruptcy it will stay in limbo longer than other kinds.
It's reasonable to think that in time much of it will get paid back but there are other kinds of investments that would perform better, and hence the economy would have been better off had these loans not been made and the money were spent on something else.
Also to your comment about sabbaticals and other less productive activities, is that really the common case? I believe that underemployment via career choices and local demand for skills would be more common.
> I won't meta-program for tests, but I will do things like make a list of classes, or symbols or whatever, to pass to a loop. Just keep it simple.
This is a case where metaprogramming for tests came in handy.
I had a bug recently that involved someone making a change that violated an invariant property of a class. To codify this invariant, I was tempted to do what you did, to make a list of symbols to feed into my test to ensure the invariant was obeyed. However this bug was caused precisely by someone adding a new symbol, a method, that didn't obey this property. The test using this design wouldn't catch this failure. I instead opted to do some introspection (it's Python, so it was dead simple) on the class to ensure all of its methods obeyed this invariant. It took a little extra time to implement but in the end it worked.
With the caveat that I haven't invested the full amount of time necessary to strongly state this opinion publicly, I do feel that metaprogrammed tests are a case of adding abstraction unnecessarily (which, incidentally, is why I haven't taken the time to try to extensively use them on a project.)
A test should be dead simple to read and understand when someone else new to the project needs to understand what it tests. Further, when a test fails, the output should clearly indicate exactly on what line of code an error occurred.
Metaprogramming tests feels to me like a case of a desire for or predilection for cleverness getting in the way of what the task is actually for.
Tests should tell a story. They should not be subjected to the same methods of abstraction used in the code they themselves are supposed to test and verify.
In an environment like ours where the split between genders is so drastic small bits of humor like this do less to make people laugh and more to help people who already feel excluded feel even more excluded.
Indeed! There are also people who choose to not get married because of tax reasons. I will write another article on the tax benefits and tax disadvantages on getting married. Stay tuned!
Next, expansion. I expect expansion is a tricky proposition because it means dilution, which is both a hard sell and a risk to the workers.