Code specific, "understanding event sourcing..." unlocked some ideas around Event Modeling (the design activity) and some new views on implementation details that are working well for me after trying them out.

While they are not types I'd usually go for, "Apple in China" and "Careless People" really got me hooked and thinking (and interested in more of the genre).

Reading Careless People has me thanking the EU for all the regulations and wishing for more.

The boundary move on the quadrants is such a good idea

Comprar, hoje, sim. Ter... Talvez seja injusto. Até há algum tempo atrás, para a generalidade, creio que esse argumento não estava na mesa. Na verdade, seria das poucas soluções elétricas que faziam sentido.

Livrar-se disso agora talvez seja demasiado difícil.

Agora, para novas matrículas ...

A really good example to consider, due to frequency and post simplicity:

Improveandrepeat.com

Practice, comments (so you can search) and maybe blogging / explaining it to others.

Yes. But be aware that even within the country, as small as it is, there's a ton of different accents.

North, center (Aveiro), interior, Alentejo in the south... Not big differences but just enough to notice.

Still, closest to where you are/will be is naturally going to help being understood.

...or getting the freakin' name of a type on a generic abstract class. The amount of print statements to get to

get_args(self.__orig_bases__[0])[0]

I'm a python noob, so I keep trying to do things I'm used to in other languages...

Yesterday was a ton of time trying to trace call sequences in a class hierarchy in unit tests, for instance...

capsys.readouterr() seemed to have been swallowing print calls which made it soooooo much worse.