I think someone needs to update that old “if programming languages were weapons”. JavaScript is a cursed hammer.
I think someone needs to update that old “if programming languages were weapons”. JavaScript is a cursed hammer.
Apple is a strange beast. I was at their space ship HQ getting interviewed, and the guy kept pointing random facts about it. Like, this particular wood was harvested in the winter so that made it better, or that entire segments can be siloed off, or that the full height glass walls of the cafeteria can be opened on pivots, and there was just so much effort in making sure things worked just right.
Meanwhile [this team] had to test software fixes for their product by provisioning ancient Mac mini’s in a closet lab because they wanted to test the “full experience” and so every patch and update they had to do was painful and horribly tested. They all hated each other (which was obvious to me just from my time in their interviews, so it must have gotten really bad during the workday I imagine). Everyone seemed on edge all the time. Even the people in the hallways. But they were all super excited that they could order lattes from the iPads tethered to the break room countertops. And they had an apple orchard I guess. The idea of changing how they do what they do was completely unentertainable.
The whole experience felt surreal, like I had stepped into the world according to The Onion.
It was very much a product of its time. It was alright.
Oh for sure, and some of those are not ok with swapping the interpreter out 🤣
It is, and it’s a valid complaint. Go and Rust have handled it differently than Python or JavaScript, and all of them have their faults and bonuses.
It’s a load bearing S.
https://en.m.wikipedia.org/wiki/PyPy
Their greatest mistake was not naming it Ouroboros.
Implement doesn’t mean “manifest from the aether with zero work”. It means do every step until it’s done. This is like step 5 of a lot.
They started at Java’s build system and set a course for Hell.
Have you considered multiple inheritance. It’s an upgrade. All upside, literally no downside. I’m trustworthy. Trust me.
There are so many more, and better!, options than testing in prod, but they take time, money, and talent and ain’t no company got time for that (for a business segment that “doesn’t generate revenue”)
Abraham Lincoln: Secretary of Ghosts
The “Big Boys” use tests to gauge when code is production ready, they don’t rely on a typing system and call it a day. I’ve seen monoliths made out of bash serve their purpose for years without a glitch, thanks to tests.
Oh hell yes it was amazing.
I once hallucinated after being poisoned by lunch from a Torta truck in Mexico, somewhere south of Monterrey. I was in a cinder block shitter a mile down the road until the sun went down that day.
Oh, and for some reason, literally every ihop I’ve ever been to has smelled like sewer, had terrible service, and has food that tasted a day old. They can’t all be like that right?
That might be the most satisfying up vote anyone has ever given.
I used to work at a place that required daily progress reports on tasks (this was before agile took off so ‘daily standup’ wasn’t a thing.). So I wrote a script to schedule my git commits throughout the week (so that I had at least one a day), and every afternoon it would pull my git history, generate a summary, and email it to my manager.
He knew it was automated and hated me for it but I had the most consistent and detailed reports. On the upside, it really trained me to make good commit messages. On the downside It really instilled me with a strong “burn the building down” kind of vibe that persists to this day.
It took me a year but I broke my team of this habit. The trick was to remind them that the parking lot shouldn’t be scheduled. The whole point is that you continue conversations organically so that it’s more like the beginning of a working session instead of the end of a meeting.