I wish this idea would take hold in academia. So many papers seem to bury simple and often powerful ideas in jargon.
1,478 karma · joined September 25, 2018
I wish this idea would take hold in academia. So many papers seem to bury simple and often powerful ideas in jargon.
This would get close to python try/catch with even lighter syntax.
This would cut so much boilerplate hand carrying error up the stack.
This does 4 good things and one bad one. Good: 1. It fills up my calendar, which gives me a better chance of getting time to do things. 2. It teaches me to say No to something when the calendar is full, or at least acknowledge the trade-off from saying Yes. 3. It helps me negotiate with people who I am willing to show my crazy to. "Ok which stuff on my calendar is your ask more important than?" 4. My phone reminds me to do all this stuff.
And the bad: 1. Every single night I have to rearrange items that I inevitably miss.
Rearranging is self-punishment, but it has a value. I rarely drop a commitment, and I am better at managing what commitments I make.
By giving away higher and higher quality models, they undermine the potential return on investment for startups who seek money to train their own. Thus investment in foundation model building stops and they control the ecosystem.
Call it.... Sustainability engineering if you will.
Where Scrum wiggles its way into relevance is schedule. Most businesses need to be able to commit to some deadline with customers or coordinating teams, and scrum lets managers convince themselves that they can project 3-6 months of work into sprints.
The reality of course is that the requirements and deadlines are constantly moving and never match what was predicted, but you need _some_ prediction to coordinate large projects. So scrum just ends up being a hack to generate time pressure on the component tasks.
What's the right solution? So far in my life it comes down to Kanban and focus for engineers, plus an experienced leader that can guess reasonably well, pad for uncertainty, and renegotiate requirements to make that guess come true.
The problem with deplatforming and censorship is that even the savviest users are unable to discuss what they have no way to ever see.
Subreddits are the closest thing to an implementation of what I want today. Let me go to moderated subsets of the content on a platform without taking away my right to expand my view at any time I wish.
Twitter et al allow you to do some moderation with blocking and follows. But opaque recommendation engines and new accounts present challenges for both.
Now we need a team of smart folks to identify tearing or other processing anomalies in universe-scale simulations.
I believe the term that you're looking for is "chilling" not "spillover" effect. This not a novel effect of censorship by deplatforming.
Why would a nebula not produce _every_ possible size of object over its billions of years?
Maybe this is how stars actually form, gas accretes into chunks of icy matter similar to what happens in Saturn's rings. Then those small objects gravitationally meet and sometimes coalesce into moons, then small planets, big planets, brown dwarves etc. finally when enough stuff has coalesced, the gravity is strong enough to cause fusion and boom you have a star.
I think the older Boeing planes through 737-900 are as safe as ever. 737-MAX+ and 787 seem to be where the design process went awry. Even then, there seem to be known workarounds to the bugs.
For what it's worth, I still fly on them all, I just remember to tell my family I love them before takeoff when the safety card has MAX on the label.