570 karma · joined March 23, 2012
(Quite possibly what you meant; I just found “in front of” easy to interpret in either way)
As okl said, it’s arguably terminology, and maybe high and low level requirements would work for you? I prefer to separate out the terms though, so that “requirements” are the thing that the engineering team can’t unilaterally change without upsetting the stakeholders. If I can change a spec item mid-delivery and it doesn’t matter to the customer, then it wasn’t a requirement. If I can’t change it, then it’s a requirement.
Requirements are a precursor to the spec, and are a list of MUSTS, SHOULDS, and WBNIS which need to go into the feature/product.
The Spec is a description of how these requirements are/will be met.
An example for the ‘ls’ command:
Requirement: “the user MUST be able to include or exclude hidden files”
Spec: “by default hidden files are not shown. Including the optional argument ‘-a’ will cause hidden files to be listed alongside non-hidden files”
To my knowledge, they didn’t move forwards with keeping the instruction permanent in peak times, presumably because it’s difficult to implement / ingrain in people.
EDIT: link https://www.shortlist.com/news/holborn-escalator-trial-tube-...
If we try to make a rough calculation from an unknowledgeable starting position, it might be more reasonable to say "just as likely to come from each 1M+ city as to come from each lab [of which there is one]". Then, if we didn't know the geographic origin, the lab probability is ~1% ( = 1/(100 cities + 1 lab)), but knowing the geographic start point you'd get 50%
P(this lab given Wuhan) = P(Wuhan given this lab) * P(lab) / P(Wuhan)
P(this lab given Wuhan) = 1 [this lab is in Wuhan!] * (1/101) / (2/101)
He’s using it to explain reverse logic, and then moves onto the more practical application in a todo list (discussed elsewhere in the comment tree).
I think it started in 2015.
On the AoC website you need to provide solutions for each day in a given year to see the next day’s problem, so you can’t instantly see all the problems from a given year unless you’ve previously completed them.
You may be able to find the problems elsewhere on the net.
“ Although 90% of women report acute breast and nipple pain during the first week of breastfeeding initiation”
“ 30% of women who continue to breastfeed at 2 weeks after birth report persistent breast and nipple pain”
That’s certainly quite different from the suggestion that it’s a year of suffering in the normal case.
Breast feed if you want to, and quit when you want, without worrying about what other people think.
We took a few weeks with child one for mother’s nipples to handle the pain. The biggest issue was psychological for the first 2ish weeks, as we’d been told by some midwives that it will not hurt if you’re latching correctly. Visiting a breastfeeding specialist (for free) at 2ish weeks who told us sometimes the pain is unavoidable but normally goes in 4 to 8 weeks made a huge difference. Weaned completely at 9 months.
With child number 2, basically no pain. Weaned completely at 2 years. Mother is very glad she breastfed both, and was ready to stop when the children were.