Context for people unfamiliar: this is a video-assisted intubation. The white bit on the screen is the larynx (vocal cords), and the fold below it is the opening of the esophagus.
(Edit: I was just looking at this and that is the fanciest portable defib/resus pack I have ever seen. The ones I’ve used were jank as heck and only had a screen for the EKG readout and vitals.)
You say that, but have you ever met a Sandhill Crane? They started coming back, and people think they’re wonderful and majestic. Then they get too close, and find out they’re feathery balls of pure hate with pointy beaks that will send you to the emergency room.
I tried to read through the Wikipage, but it was just too dense for me so I asked an AI to summarize which I think it did pretty well:
The Book of Enoch, also known as 1 Enoch, is an ancient Jewish apocryphal text attributed to Enoch, the great-grandfather of Noah. It is not considered canonical by most branches of Judaism or Christianity but is significant in the study of early Jewish thought and the development of Christian theology.
The book is divided into several sections:
The Book of the Watchers: This section describes the fall of the Watchers, a group of angels who descended to Earth and took human wives, leading to the birth of the Nephilim, giants who caused chaos. Enoch is chosen to intercede on behalf of the Watchers, and he receives revelations about the coming judgment.
The Book of Parables (or Similitudes): This part contains three parables that focus on themes of judgment, the coming of a messianic figure, and the fate of the wicked. It emphasizes the importance of righteousness and the ultimate triumph of good over evil.
The Astronomical Book: This section provides detailed descriptions of the movements of heavenly bodies and the calendar, reflecting an interest in astronomy and timekeeping.
The Book of Dream Visions: Enoch recounts two visions that symbolize the history of Israel, including the judgment of the wicked and the reward of the righteous.
The Epistle of Enoch: This final section contains exhortations to righteousness, warnings about the coming judgment, and reflections on the fate of sinners.
Overall, the Book of Enoch explores themes of divine judgment, the nature of evil, and the hope for redemption, making it an important text for understanding early Jewish and Christian eschatology.
I appreciate the insinuation that I don’t know how to read an article… no, I skimmed and dived as much as I normally would but realised that topic was too complex for a full dive and that the abstract was too sparse for a good overview…
Apocryphal for most sects. Heretical for Rabbanic Judaism.
The most interesting thing about it I think is that it was thought lost for centuries, but there was a well-known translation in Ethiopian. When the greater Christian population heard about it, it was assumed to be a forgery, but it was still studied and translated.
It wasn’t verified as “authentic” until the discovery of the Dead Sea Scrolls in the 1950s, where ancient Greek and Aramaic copies were discovered that match the Ethiopian translation, establishing the provenance of the Ethiopian version.
You spent all those years down in the trenches implementing bullshit designs an architect came up with, positive you could do better if you just got the chance. Then you go to graduate school to get the qualifications companies say you need to be an architect. You receive a masters degree. You’re your companies leading expert on software design. You get promoted to architect.
That’s when you find out the truth. All those previous architects left for the same reason you someday will. It wasn’t the previous architects making the terrible decisions that frustrated you. It was the marketing team and the CEO telling the CTO that the software product must have certain buzzwords present in the design. Those buzzwords offer no value to what your software product is meant to accomplish. But if you don’t put them in the designs, they’ll fire you and hire someone who will play their games.
Eventually, you can’t take it anymore. Having interfaced with the upper levels of your company, and having the understanding of systems engineering you do, you realize that every software firm will be this. There is nowhere you can go that will be better. You start saving.
Your goal is to save enough money to purchase a small plot of land and put an organic farm on it. Your convictions for this farm are simple: it must be able to feed your family. This may not be exclusively what you envision for it, and you may not even intend for it to be the only source of food for your family, but it will help you be less reliant on the kinds of corporation you’ve come to know and come to see as irrevocably evil.
And then sometimes, you get people like this in the post. Who find enough success farming to focus their energy on it exclusively.
If you give a shit about your work and the product you’re working on, then don’t work in a big company. In big companies, people are there for the money and maybe for a good looking entry on their resume, so they’ll only do what they’re being told to do, after all they’ll be elsewhere in 2 years tops.
If you have ideals and don’t just work for money, don’t work in the corporate world. Small to mid-size employers come with a lot less bs and more engaged co-workers.
Just try being uneducated and working in a dead end factory job while having hated life all your life anyway!
Much fun! -46/10 would never recommend!
I wish I was forced into programming… I tried on my own and just don’t have the mind for it, I find it incredibly boring. All my friends are in the field and all work from home wherever the hell they want to live. I’m stuck in a VHCOL area with shit income and 0 potential to increase it :(
Yeah well I was „forced“ into it by an injury and one my parents working at the university. I never finished my degree so in that sense I’m also uneducated.
I didn’t have the mind for Uni stuff either esp. the maths stuff. There are so many areas. I just liked doing webdev stuff in my freetime and that landed me a few jobs.
I’m sorry you’ve had to suffer an injury! From what I understand, your experience now and your interest outside of work counts for more than the paper degree so if you do choose to continue that path I wouldn’t worry too much about being uneducated. Good luck, I hope you find happiness in whatever you do!
Thank you very much! Yess school has never been for me but I’ve only been diagnosed with adhd when I was 21. so I’ve always struggled. I don’t know if it’s the perfect place for me, I’m still struggling from time to time, but let’s be honest who doesn’t. I never thought I could work 8 hours when I was younger. But here we are. So hopefully you can also find something you enjoy doing. And I wish the best for you too. Thanks again!
Yeah that sounds way more enjoyable, but first you need the 250k and up salary that a principal engineer at MS makes for 20 years, then you have plenty of equity to focus on whatever your hobby is
I think MS like other big tech companies has started to run out of “senior” positions without paying more so many people just end up as “senior” principal engineers which is basically “this is as far as you can go if you don’t want to get involved in management”
“this is as far as you can go if you don’t want to get involved in management”
Yes. That exactly. This typically comes with a nice perk: Principals are supposed to have the same clout as lower-level managers. Which is to say they usually report to Directors or even the CTO in some organizations.
Another one is “Independent Contributor” which is similar but, as the name would suggest, is very self sufficient and does not work on (or for) a team. They’re basically one-man engineering shops and are expected to perform well everywhere in the company’s tech and talent stacks. As a result, ICs are very rare.
My grandfather is/was an electrician for over 60 years. Worked on very important projects in New York City. This rubbed off on me growing up. I spent much of my childhood taking things apart, figuring out how they worked, and putting them back together how I liked. I’ve been working on both hardware and software since I was 11. Had the privilege to study CS formally in high school, and Computer Engineering in university.
Good timing mostly got me into farming, especially since interest rates fell to the floor during the pandemic. Had enough to buy the acreage I wanted, and the wife was interested in helping out. We grow a variety of things now, and not just plants. For example we sell Honey, Soaps, Walnuts, and Mushrooms. It can be hard on the body to be so active all the time, but it is more satisfying than a monitor staring back at you at 3am because of some small incident.
I continue to tinker, and assist startups in my spare time, I can’t imagine I will ever stop programming.
Yeah, after 22 years at Microsoft in a senior position, you should be able to retire and do whatever the fuck you want as a hobby. I very highly doubt this guy will ever make significant money from goose farming.
Yes, those are the Game Engine Black Books (Doom|Wolfenstein) by Fabien Sanglard. Highly recommended for anyone interested in games, programming, and history. They are amazing time capsules of those games and the development environments that produced them. I think/hope he’s working on GEBB: Quake and I’m so excited for him to eventually release it!
Oh you’re going to be in heaven, it’s one of my favorite books! He really gets into everything: how the game is structured, how different subsystems work (BSP trees, enemy ai, sound, music, every detail), and even gets into peripheral things like how the game was distributed, how the (old) console ports came about, and so much more. The copy on my shelf is actually my third because i keep giving them away to people.
I wholeheartedly agree, I’ve been going down the pipeline myself and this has been my approach. Recently I’ve been working with family and neighbors to get a community garden going.
The other pivot point is The Pragmatic Programmer, which is totally understandable.
That book does a good job of grounding the reader through examples and parables from everywhere else but IT. By the end, you realize that good software engineering makes the best of general problem-solving skills, rather than some magical skillset peculiar to computing. You wind up reaching a place where you can begin to solve nearly any problem through use of the same principles. So @codex here, perhaps effortlessly, went on to management instead.
Thanks for reminding me about Art of Shen Ku. Friend had a copy years and years ago and from time to time I would remember reading parts but could never remember the title. Cheers!
lemmyshitpost
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.