- [[English Lesson]]
	- warmup
		- who **got to unplug**? (=managed to relax cutting down on your screen time)
		- how is your friend’s **refurb coming along**, Matthias? 
		  full steam ahead
		- who didn’t **get enough** sleep last night? 
		  pull through
		- has it been **overcast** where you are right now? (=with clouds in the sky and therefore not bright and sunny)
		  to clear up = [speaking of the sky] become bright again
		- who **did the weekly shop** over the weekend?
	- Wood fibers - Holzfasern
	- tiles - Fließen
	- **to talk shop** - talk about (matters concerning) your work
	- do the shopping (grocery shopping) vs **go shopping** (activity implying a dose of entertaiment)
	- I would sooner ... = I'd rather
	- the till = checkout area
	- use get instead of buy
		- mill, grain (what, rye...) -> flour
		- it went on for a year ... the subscription expired/lapsed
		- to go to waste
		- to have one's hands full = be very busy
		- to use sth up
	- pick up/snap up (informal)
		- Can you just pop in the shop and pick up some eggs? (=buy)
		- It was such a good deal, I snapped it up. [=AS IF quickly and enthusiastically, usually because it is a good deal]
	- a token git
	- a bargain price
	- in a bulk = make supplies of
	- limited edition flavours
- https://www.chefkoch.de/rezepte/1481031253346883/Schwaebischer-Salzkuchen.html [[Rezepte]]
- API Questions:
	- What guarantees are given on the data on the events endpoint? Is ID increasing all the time (in increments of 1)?
		- Event IDs a strictly monotonically increasing. We don't guarantee  increments of 1 though. The gaps in the offsets are due to the exactly once semantic processing of our kafka stream computing the events.
		- https://stackoverflow.com/questions/54636524/kafka-streams-does-not-increment-offset-by-1-when-producing-to-topic/54637004#54637004
			- The only guarantee you get is, that each offset is unique within a partition.
	- What about the missing event ID 119434986? Is that a bug or can events have missing IDs in the increasing series?
		- Not a bug. As stated above it is due to the kafka stream.
	- What is createdAt referring to? (I assumed it’s the time the event happened, but then later IDs should have higher timestamps) Why can it be decreasing in events with later IDs. How does it relate to the document timestamps (we established in earlier conversations that document updatedAt can differ from event createdAt because they are different processes)
	  How am I supposed to know if I got all events if there are missing ones and timestamps and/or IDs are not monotonically increasing?
		- Ich glaub bei dem Beispiel das er anführt hatten wir die Probleme mit Kubernetes im RZ und da ist dann beim Neustarten der Event Verarbeitung auch der Offset wieder auf einem alten Wert gelandet. Beim Check der letzten 24310 Events (139470000 -> 139494310) gab es den Effekt nicht. Die Annahme von Ihnen stimmt also im Normalfall.
	- Also if you replay events, do you also replay data, so is e.g. document 7a233a97-1f18-3792-b287-c7b35f601f0b also not yet updated on the documents endpoint and we need to wait 15 minutes from some timestamp (in that case no idea how to figure that out instead of retrying for some time) for this to update?
		- Versteh ich nicht. Wir replayen typischerweise kein Dokumentveränderungsevents, sondern haben wie oben nur den Fall gehabt, das wir aus dem globalen Topic nochmal die Kundenevents selektiert haben.
- Find My IP Adress
	- https://www.maxmind.com/en/locate-my-ip-address
	- https://ifconfig.co/
	- http://ifconfig.so/