Note the section you’re in at that doc link: “Claude for Work (Team & Enterprise Plans) ->
Team & Enterprise Plan Features
-> Project visibility and sharing”
The killer feature for me is if you could tell it when you throw something in the bottom of the freezer or back of the pantry and it reminds you do do something with it in two months
"The function checks if it is the first click, and that the square being clicked is a mine. It then tries to move the mine to the upper-left corner. If unsuccessful it tries the square to the right of it. If all of the first row is occupied by mines, the function tries to put the mine in the leftmost square of the row below, and so on."
Jokes aside, I love it how in a group of software engineers someone can always think of an even more unlikely, but somehow realistic edge case.
For me, one of the marks of a senior engineer would be to then either go "we'll just not allow the board to be filled with entirely mines in the builder", or "well, if that ever happens: just let it crash". A practical solution to a theoretical case.
Whereas the more junior engineer would spend the next few days researching and refactoring the algorithm to address this case. Obv. "it depends", letting my insuline pump "just crash" isn't cool, but minesweeper, meh.
IIRC in WWII the UK settled on 'fife' and nine, while the US went with five and 'niner'. Arthur C. Clarke's novel Glide Path described the adoption of fife.
reply