ECMAScript is an order of magnitude more complicated than Go by virtually every measure - length of language spec, ease of parsing, number of context-sensitive keywords and operators, etc.
All of the recording I did for my friends back in college is stuck in Nuendo/Cubase projects with a bunch of long-obsolete plugins used for mixing and mastering. Going forward I'm going to print every individual track to PCM so that I have a "digital tape" of the entire session to avoid this problem.
I live in San Diego and can watch planes come and go from my apartment rooftop. I've also walked to and from the airport to stretch my legs before and after flights.
Somewhere I have a GoPro video of me on my motorcycle waiting for a freight train at a crossing in traffic while a 747 flies overhead ("Planes, Trains, and Automobiles"). It's a pretty transportation-dense area.
100% thought this would be about eating jellyfish (which I'm completely on board with because they've stung me upwards of a dozen times and that old Klingon proverb that says that revenge, much like jellyfish, is a dish best served cold).
Apropos of stinging plants though both of my parents are supposedly very allergic to poison ivy. I maintained an immunity to it until I was around 27-28 when it began to affect me very slightly. Now if I graze it I can get away without ill effects merely by washing the urushiol off with dish soap within a half hour or so. I've heard of gardeners and outdoorspeople eating it in small quantities to maintain their resistance to it. While I'm not particularly keen to try this there is something poetic about it.
Eh, jellyfish isn't really any good. For the money, there's many better things to eat. I should admit I've only had it the once, but that's enough for me.
This was specific to Web Forms, a now-deprecated framework that did a lot of implicit state management that necessitated POSTing to the server with an encrypted client-side state called the ViewState.
Its modern replacement ASP .NET MVC works much more like traditional web frameworks.
Scrum is like Spaghetti Carbonara in America. The ingredients are simple and there's a tiny bit of technique involved that anybody can figure out after a few tries. For some reason though almost everybody that makes it decides that they know better than the people that invented it and so adulterates it with peas and onions and garlic and cream and cream cheese and Italian seasoning and parsley and chives until it ends up being Olive Garden Alfredo. If they wanted Carbonara then they would have cooked the Carbonara, not the waterfall with a bunch of JIRA workflows and four-hour meetings layered on top. They just did what they would have done anyway while attempting to sound fancy via obfuscation.
I've not noticed them feeding back while listening but it happens whenever I put them in the case together for a split second. I also get a drop-out every time I walk past certain spots in my apartment building hallway because of what I'm guessing are ultrasonic sensors on fragrance dispensers or light fixtures. Definitely buggier than the previous version but the improvements in sonic accuracy and noise cancellation are well worth the inconvenience IMO.
I’m going to try and find a good source on it but the short version is that Bungie was in deep financial trouble and approached Apple for an acquisition. Jobs didn’t want a video game company as part of their core business as it was not the future he saw for the company, but Microsoft was willing to make that deal, so Bungie went with that for the security. Jobs was pissed but ultimately he passed on an acquisition they felt was necessary for survival.
And Jobs was probably right. Apple was a bad fit for Bungie (and games in general). There is a reason Marathon is virtually unknown when it was one of the best "Doom clones" of the era.
Yeah I agree with it too - plus they were hurting financially, that’s a lot of risk to assume. And frankly what we got with FPS halo seems way better to me anyway. It’s hard to imagine the Apple version would’ve been a better game, but admittedly I am speculating.
Shaggy dog story: when I was 9 my teacher assigned us homework that entailed writing an instructional essay on how to make the infamous PB&J sandwich. At the time I was a budding "programmer" and had recently seen a skit on a TV show that employed hijinks similar to
> * I brought a serrated knife and ketchup packets. When they said put the jelly on the bread with the knife, I gripped the serrated end and pretended my fingers bled (ketchup works great as blood).
> * I brought in vaseline AKA petroleum jelly. When they said put jelly on the bread, I contemplated aloud "Well, you said JELLY, and this says JELLY!"
...and so went into great prescriptive detail about exactly how I'd make said sandwich. After turning it in my teacher chose my essay specifically to repro onto a transparency and place on the overhead as an example of bad writing. Apparently being explicit about choice of ingredients, removing things from packaging, holding the bread, etc. was antithetical to the assignment and dismissed with laughter and eye rolls because "everybody knows" to do these things.
This was a bit of a blow to my fragile ego but in retrospect it was an important lesson in several concepts that you touch on later in your post such as good communication (the importance of considering one's audience), asking clarifying questions (because requirements are hard), and interactions with authority figures.
I say all of this to say that you should absolutely emphasize this less technical side of things. Soft skills are at least as important as technical aptitude when it comes to career mobility and emphasizing them early would give students a real leg up. While considering edge cases and assumptions is clearly important for computers it's also crucial to keep in mind how people understand processes and systems, i.e. when to be explicit and when to avoid patronizing those on the other end of your comms.
> teacher chose my essay specifically to repro onto a transparency and place on the overhead as an example of bad writing
Oh man, regardless of how "bad" someone's writing is, this is terrible terrible teaching. Public shaming in front of peers, especially on something subjective like this? Some people should not be teachers. I'm sorry you had to go through that.
The web already had terminology for this in online enthusiast forums: WTB (Want to Buy), FS (For Sale), FT (For Trade), etc. The slow death of the open web in favor of platforms has evidently caused a lot of rework like this. Other notable examples include backwards emoticons (: and DM instead of PM.
