240 karma · joined July 16, 2017
I was looking for inspiration on requirements engineering practices beyond arc42 & friends that are compatible with (or can be explained to deciders in) larger organisations, and found the Nasa process ideas (expectations - "conops" - requirements) surprisingly flexible
We need to get back to the building times of the 80s in Sweden for nuclear. The korean nuclear plants have the fastest building time these days after the chinese, so no surprise they will be building the new ones in Poland
Even in larger time periods (a year or so), if a country is emotting low co2 (green) then it is either nuclear plus VREs (variable renewable energies) or VRE plus hydro
Consider how meta originally marketed it in a business setting - would the "virtual office" application allow you to check your private messages in between? This can be built in of course, but currently it looks like an afterthought at best.
I talked to some trainers in a company about VR trainings (my previous company produced such a course). Some trainers were interested in VR because it "keeps trainees from looking at their damn phones"
nuclear energy has been largely phased down for political reasons and CO2 emissions are still on a level where EVs might not be much cleaner in comparison, see https://app.electricitymaps.com/map
It is a personal decision in the end, our society allows for mass-producing and killing living beings despite better alternatives. As with other personal choices that are harmful and arbitraty, this is not something I see as worthy of further appreciation, or beneficial for further discussion.
There is a large community around new recipes for this taste profile, e.g. https://seitansociety.com/ .
compared to the logistics (animal farming and slaughter pipelines), artificial inseminations, medical interventions (antibiotics), storage and food safety concerns around meat, plus the incredible daily amount of animal suffering caused by this consumption, I don't see meat as a "natural" product. all the steps in the "production" process can introduce factors that can degrade the quality and be risky to health (e.g. not cooled at appropriate temperature, antibiotics treatments to animals etc), while with plant proteins, you have far less processing steps between field and table. to vegans and people concerned with reducing global warming, the benefits outweigh the different composition by far.
"Veganism is a philosophy and way of living which seeks to exclude—as far as is possible and practicable—all forms of exploitation of, and cruelty to, animals for food, clothing or any other purpose; and by extension, promotes the development and use of animal-free alternatives for the benefit of animals, humans and the environment. In dietary terms it denotes the practice of dispensing with all products derived wholly or partly from animals." https://www.vegansociety.com/go-vegan/definition-veganism
You could make a similar argument about slavery, the reason we abolished it has nothing to do with productivity estimations.
- board structure to aid sorting before a "commitment point", e.g. "Options/New" - Later(6 weeks) - Soon (in the next 7 days)
- Now (usually just the top or highlighted item in "soon") - Done - Closed
- Closed" to place items that are dismissed
- Work in Progress (WIP) - Limits on all columns - maximum number of items
Throughput
- average capacity: number of cards completed or closed in a typical week
- useful to keep track of: when I complete a card, I add a dot somewhere (usually on a "note card") to count it for the week, and add info when blocked by sth
- this number varies, but is a useful indicator how much I can realistically process in a week - for example, 5 items/cards
WIP (Work in progress) limits
- visualize expectations - what can realistically be achieved in this timeframe
- set per column limits - when more cards are in the column, I have to remove some or transfer them to a wishlist
- wip limits determined by average number of cards closed or done per week (throughput); e.g. "Later (WIP 20)"; "Soon" - WIP 5;
Managing Flow / preventing queues
- planning with smaller steps (could each be done in a day) to enable learning
- avoiding a situation when too many things are started but not completed
- understanding the cost of queues: nothing gets done for a long time, and then all at once (unpredictable patterns); or the value diminishes (cost of delay)