Thanks for this, had a good laugh reading it! Cooking is my other passion right next to programming and I've worked in kitchens quite a bit, an occasional plung

Thanks for this, had a good laugh reading it! Cooking is my other passion right next to programming and I've worked in kitchens quite a bit, an occasional plunger but mostly a chef, on-and-off since I was 14 (don't ask...). Haven't been back to chef-ing in about 5 years, but I miss it quite a lot for various reasons. It's taught me stuff about handling stress I don't think I could have learnt anywhere else, and making a bad situation fun is definitely a good place to start. I think the tech world lacks this sort of attitude drastically ; I also notice that a lot of people in our sector simply can't handle stress and high workloads very well. That might be part of the reason I did pretty well when I went back to programming. The problem with most jobs requiring a higher level of education (very generally speaking) is that they separate the maker of the product (or at least the person who delivers it) from the client. What it means is that there's rarely any direct feedback either way. Because of the shift in knowledge, you could deliver a sh*t product that your client will love, and vice-versa. In most cases, this wouldn't happen in a kitchen. You most likely wouldn't even be able to get through the first day without communication. Your work would be meaningless without feedback from your clients and your team (good and bad), chances are you wouldn't even have a job any longer. I'm not saying this doesn't apply to tech jobs, but there seems to be a certain latency in and "transformation" of the feedback that's passed around. It basically misses that social and professional rawness which I often miss :)