I am not so sure that the schools necessarily should make it their problem. Sure, compulsory primary schools should try pretty damn hard to drag pupils along. However, once one gets to the tertiary level of education, one should (1) have the academic credentials/prerequisites needed for the chosen program of study (otherwise the admission process has failed or the grades have been inflated/made up) and (2) desire to learn.
Of course, be a good human and reach out a helping hand to those that seem to struggle but, if you have students who truly do nothing, want nothing and try nothing then just move on? If they fail in their first semester then they are not there the second.
Maybe colleges shouldn't have accepted these kids in the first place or shouldn't move them along. But I think the author is raising a different alarm -- the number of kids who "do nothing, want nothing, and try nothing" seems to have spiked significantly. Public schools, at least, have a mandate to care about this.
I think the problem of student motivation is much broader than this author's college; I've heard it echoed by so many professors lately, but never as poignantly.
Is that not because there is not much to do, and therefore people use .unwrap() — because crashing is actually quite sane?
Correctness trumps ergonomics, and the default should definitely be poisoning/panicking unless handled. There could definitely be an optional poison-eating mutex, but I argue the current Mutex does the right thing.
If we are talking about BNW, which was written in 1931, then that book predates benzodiazepines by 25 years or so. Perhaps you are thinking about barbiturates?
Oof! Thank you for the correction. I should have checked the publication date. I thought it was from the late '50s; I was wrong.
(By contrast, turns out 1984 -- which is always paired with BNW -- came out later than I thought, in '49. Yet BNW seemed more forward-looking. I always imagined it was written partially in response. It wasn't.)
There goes my benzo theory.
Though they remain what I imagine when I read about soma.
Ah, sweet memories. Grumpy German border guards boarding to loudly demand papers, but if you were slow to pull the ID card out they just kept walking. Semi-open border policy ;)
During the Cold War, the train on the Trelleborg-Sassnitz ferry went to West Berlin ... throughEastGermany with no getting on or off over that stretch.
BTW. I was on the Hamburg-Copenhagen train on the Puttgarten-Rødby ferry in 2015 during the height of the Syrian refugee crisis. I had changed my booking to earlier trains because of expected delays. It and connecting trains were packed, as were the train stations, also with immigration officials and volunteers. Brings tears to my eyes to this day.
Have been sketching on what sounds like some of your concepts: recipes as trees with actions done to ingredients with timing and so on. I will sign up as a beta tester! :)
The initial intention was actually not to build it in this way. I ended up with this design by trying something simple, finding limitations that prevented scaling to new features, changing the design, rinse and repeat. A much simpler design can solve 80% of all needs, but I have been obsessed with the last 20% over many years. Of course all features won’t be there at launch, but I know they are possible to do in a nice way with this design.
Food is incredibly diverse and each country, language, culture etc have a different way of doing the same thing. I don’t know what this app will be in 1 year, but I know that the foundation is like clay that can be molded into what it needs to be, even different experiences for different users. I wasted so much time and energy on food and found no recipe app (tried 50-60) that worked for me, that I figured someone should solve this issue once and for all. Humans should not deal with these issues anymore.
I believe Kastanj will make it easy for beginners to start cooking really good food without spending too much effort on everything that goes into it. I also believe it will scale well to more advanced users that needs more of a reference, and not the same help. The idea is that the app will be a tool that helps people regardless of their experience level, and get out of the way when they don’t need the same help. This internal graph design is the only design I have encountered that managed to adapt to these diverse use cases.
There are a long list of use cases a recipe app could cover:
- some people track their calories.
- some people follow certain diets
- some people have allergies
- some people live in regions where certain ingredients are hard to find or seasonal.
- some people want to reduce their climate impact
- some people want to save money, budget cooking
- some people only cook for 2, some cook for 30
- some people prefer certain units, even in metric Europe there is variation.
- people are picky with what they eat and don’t eat.
- sometimes guests with allergies come over and you have to cook something you never cooked before, and it must work on the first try
- and so on
Food is complex, people are even more complex and have complex preferences. All of these cases adds complexity with various edge cases. These cases are the last 20% a recipe app should solve. Very high effort but most people can live without it (diminishing returns). I believe Kastanj will solve these issues + many more. I believe it will enable people to start cooking and still help those that already know how to cook. The current design have adapted really well so far even for use cases I didn’t imagine. Now let’s hope it was worth the effort. It makes me happy to hear that you also imagined a design like this :)
How is that hard? They put 90% of their estimated revenue as net revenue (post-McK tax) in the budget? Seems about as hard as the underlying problem, which is guessing ("forecasting") the revenue.