What planned obsolescence are you talking about?
~ sent from my iPhone 11 Pro, a 7 year old phone going strong and still supported in the upcoming iOS release
Indonesia still practices slash-and-burn land clearing for farming. Combine that with a lot of carbon-rich peat and the dry monsoon season, and you get the annual smoke out of its neighbors like Malaysia and Singapore. It lasts between one to two whole months. ASEAN generally follows a non-interference policy, plus worry about economic and diplomatic relations, so everyone just huffs pollution for a while every year with no real end in sight.
I recently learned that you can name timers too. Very helpful when you've got more than one going.
The bus! I had forgotten about this, but weddings with busses between the hotel(s) and the venue were great. Not only were they their own little pre and post party, but they absolutely improved safety for the majority of the guests.
Venue helps a lot. The best one I went to was at some farm on a hill, converted of course to a fancy event venue. The neighboring plots were still farms. I vaguely recall one even had some sheep that wandered up to the fence. Up on that hill, with nothing but low farmland all around, the sunset and night sky were fantastic. They had a bunch of comfy chairs and tables set up outside so you could take a break from the dance party, relax with some friends, and enjoy the view.
I fully agree with this.
I had all four wisdom teeth removed in one morning then had a hamburger, fries, and salad for dinner. The dentist gave me a little plastic irrigation bottle to clean the holes after meals. Their only warning was to avoid truly hard foods that won't soften - like peanuts - which could lodge a chunk in the hole that irrigation would not be able to remove.
It'll be a bit trickier with a molar more upfront than a wisdom tooth, but I think as long as OP pays attention and chews on the good side, they're probably fine.
Edit: That said, I'm now remembering a friend who's face swelled up like a chimpmunk for a few days after extraction, so YMMV
I'm sure there have been similar reactions to celebrity deaths in the past (john lennon, Princess Diana, etc.), especially if not by natural causes, though it definitely feels more widespread now.
I'm an elder millennial, and I don't really remember my parents talking about celebrity deaths much beyond dinner table small talk as well. A few things come to mind. TV and movies have expanded so far beyond what my parents grew up with, both in volume and in local->national->global reach. Combined with the explosion in budgets and marketing, they're just more present in people's lives from a young age now. We also saw the normalization of 24-hour newscycles needing to ~beat a dead horse~ fill the time, plus cable tv channels like E! Entertainment Television filling the whole day specifically with celebrity gossip. Millenials in particular seem to be very nostalgic, though it may just be my bubble, so seeing celebrities they "grew up with" die hits them hard. And of course we have The Internet - an insane multiplier of every thought and hot take across the globe with platforms that incentivize more extreme and performative expressions and parasocial relationships, which simultaneously gives the appearance of a stronger reaction and very likely stirs actually stronger reaction in a feedback loop.
Personally, to feel more than a bit of sadness it takes a celebrity who personally made the world a meaningfully better place, far beyond their characters or filmography/discography. Truly great role models and forces for good, like Fred Rogers and Dolly Parton. And even then, personally, they get a teary-eyed remembrance. I can't understand the people mourning as if the celebrity was their parent or sibling or life-long best friend.
Re:Tangent - Totally agree. Now that you've called attention to it, I realize we do this in our own family and household. Seems to work nicely. Keeps things light unless they're serious, encourages proactively checking on each other and offering help, and shows the kids that even adults have these problems.
Re:Non-Tangent - "Pain is weakness leaving the body" is a common military and fitness mantra, possibly originating in the US Marine Corps. I was using it here to encompass all of the toughness-is-superior philosophies - no pain no gain, what doesn't kill you makes you stronger, suck it up and toughen up, don't cry or whine, feelings and fear are for the weak and you should be ashamed, your pain is not real and is not an excuse, just pick yourself up and push on.
This is what I've read in multiple studies, and have seen it first hand multiple times even within the same individual. Kids that could take a rough tumble and get right back to running with their friends as long as any adult response is calm or silly, but later completely break down after the slightest bump if grandma comes running from across the room "oooooh noooo, poor baby! that must have really hurt! are you ok!? let me hold and rock you." The other extreme is "pain is weakness leaving the body" crowd are also messing up their kids coping skills, but it seems most parents in the modern times thankfully don't follow that anymore (at least publicly).
Of course the usual caveats about individual personalities and needs still apply.
Is this new, or maybe newly more consistent? Looking through my email archive, I see Amazon confirmation emails as far back as 2019 with minimal detail. Just "Thank you for shopping with us. We’ll send a confirmation when your items ship." with subtotal/total, estimated delivery date, where it's shipping to, and an order number linked to the status page behind a login. There are some mixed in with more detail, some template changes over the years, and some country/region differences.
That said, I'm torn. On the one hand, as a customer I love the convenience of having all of my order info in emails. A single, "unified" place to search for order history across all vendors, no age limitations, no individual logins, no product data changes reflected. On the other, I've seen how information sitting in inboxes or public "secret" unauthenticated order status links can be found and used by bad actors, and so from a security and privacy standpoint I'm happy to see less information in emails.
I tried this with a fairly stock Firefox and a fairly stock Chrome. I denied any extra permission popups.
Unsurprisingly, Chrome gives away more, and more specifics.
Overall: FF 1 in 135.3 million | Chrome 1 in 146.8 million
I'm shocked that nobody has mentioned this LAN party classic:
Age of Empires II
(yes, technically the modern versions require internet connections for private hosted lobbies, but the original supports true LAN. There are apparently third party / community tools for true LAN with modern versions)
Supports up to 8 people (teams or free-for-all)
Full platform support across Windows/Steam Deck/Mac
Retro - original release in 1999
Strategic and endlessly repayable
I was one of the minority that thought it was great!
From what I can remember, a lot of people use vote count as a proxy for engagement with their posts and comments. A vote means at least someone read what they wrote and thought it was worth something. Without some sort of feedback, short of a full comment reply, they felt like they were shouting into the void.
There's surely a way to provide some loose feedback like that without actual votes. If you're willing to accept some tracking (first party only), you could do some clever things like tracking time-on-screen of a post or comment, normalize it by average reading speed, and then provide some aggregate feedback viewable only to the author like "X users have read your post, Y have skimmed it, Z have skipped it, and N have returned more than once". There's all sort of things you could do here.
Of course the flip side to any feedback with a measurement - votes included - is gamification. Some of that can be mitigated by keeping it all private to the author, so there's no contest, but it can still be a useful tool for a scammer, spammer, or anyone else primarily looking to drive up engagement to their own posts rather than just participate in a community and feel seen.
I also started enjoying coffee in my 30s. I can't speak to @PraiseTheSoup's journey, but mine was having two kids under 2 at the time, and the local coffee in southeast asia being like two thirds coffee (high-caffeine robusta), one third condensed milk and evaporated milk, and a scoop or two of sugar. That jet fuel kept me alive. After drinking it near daily for long enough, I started to actually notice the flavor other than SWEET, and from there tried more coffees. I still prefer tea as my daily hot beverage now that I can sleep again, but I do enjoy a nice coffee if we're out for brunch on the weekend.
I wouldn't be so sure. There's some things I didn't start liking at all until i was in my 30s, some things that I don't like much anymore, and a couple things I loved and later developed allergies. I wouldn't be surprised if they change again as I get older. Tastes and bodies are weird.
The Opening Ceremony of the 2020 Tokyo Olympics isn't a great example. The first segment was a lot of traditional fireworks fired around the entire stadium perimeter, raw and exciting. The drone display was really cool, but a very different feel - more graceful, flowing, and beautiful. @chocobean nailed it.
Do you have any good alternatives? I bought one a few months ago after the long history of rave reviews and was rather underwhelmed
Yeah, you're right, I do still look at the code a bit, which is what the article advocates completely against. That said, I've been looking at it a lot less than when I started, based on what I've actually seen it produce in my situation. In the beginning I was meticulously reviewing every line of code it produced, far more carefully than I would any human PR, even after our extensive interactive planning practically wrote the thing already. Over time, I've still looked, but substantially less, now more like what I would for a colleague's PR who has done well in the past. Mostly a sanity skim, a high level architecture and organization kind of eyeballing, for complex or critical changes. Just a minute or few. Small tweaks and bug fixes I might let pass straight through at this point.
I think the softening has come down to a few things (not just laziness or complacency). I've figured out a workflow that works for me and spends a lot of time planning the details up front with me driving; I've definitely caught things in this stage where it's planning to overbuild or hedge against impossible conditions. My general trust in the tool has improved after using it successfully on both small and large things for months. I've seen how the large, mature code base gives it a lot of prior art to work with that it usually follows. Auto-memories and, much more importantly, my agents files and design docs have explicitly codified a lot of architecture, convention, and more subtle rules, growing and sharpening over time, which help the agent do the "right" thing more often.
I don't think I'll ever go full vibe (I have trouble completely delegating even to humans), but it's trending in that direction.
Always comforting to hear people arrived at a similar usages and conclusions. Either we're doing something right, or we're at least in the same wrong boat together!
Yeah, memories are a bit goofy. They seem to be useful short term, helping to bridge the gap between workdays and task switches, but can come back to bite weeks down the line when they're no longer in sync with the current state of the world. I try to get it to write as much as possible and useful to the plan files, and much more rarely to the agent files after hitting the same problem or deriving the same information over and over again.
For skills and the agent files, I had Claude write the prose, but built them with nearly the same flow as the feature flow. Detailed objective scope and requirements, known bits of information or where to gather them from, desired behavior, etc. up front, iterative back and forth, cold reading reviews by both me and Claude, and tweaks over time based on their performance. I think it's important for people to use the AI tools and harness as vanilla as possible for a while to find what fits you personally rather than cargo-culting a bunch of skills and prompts and agent file "hacks".
Definitely agree about the design docs for large areas of the code base, as well as the boundaries and interactions between code bases if your project has multiple repos/applications. Before I did that, anything non-trivial would either get confused if I didn't tell it explicitly where things lived, or would spend time and tokens poking around every time. For the same reason, I keep a database schema dump on hand so it can do some quick grepping to find most things.
Oh, and I just remembered another tidbit, agents are great with CLI tools. I rarely need to reach for some feature-subset MCP when the thing has a mature cli tool I can install. Plus I don't have to keep authentication info in some plaintext MCP config.
