To All the Jobs I Had Before
Took a read through her notes, I kind of like them. Short, concise, a bit all over the place but in a way that feels 'authentic'. It also helps that I'm not being sold anything - I feel like everything and everyone is doing that nowadays, and it's exhausting.<p>> I learnt how constraints affect the system as a whole. If the elevator or any other part of the system was too slow, the entire production would grind to a halt. You truly grasp the concept of work flow when it is physical. Boxes clogging the conveyor belts, pallets queueing up with no floor space, lines of people literally just having to wait because their work stations are blocked from progress.<p>Really liked this paragraph, was very easily visualizable. Factory lines at a standstill because some cog in the machine is broken - tonnes of smelly fish sitting around, frustrated workers yelling about, clanging of machinery and the waves of the sea in the background.<p>In software we work with things that are just so _abstract_, it's nice to just be able to understand a system and it's flaws at a glance. It's nice to be able to see/hear/smell/touch what is wrong, what is right - in software, the most common way we get data is through text. Sometimes we even see a 2D image that (usually badly) represents some complex concept.<p>But it's not the same. I wonder if there is a way to change this.