u/Antique_Target3076

I just finished S4E7, and holy effing s-balls. It was beautiful. One of my faves so far. I'm crying. Also feel so full of love and gratitude. Felt like I had to share some thoughts.

Hats off to the >!actress playing Tiff, Gillian Jacobs!!< God damn. >!That last scene where she's dancing with Richie and holding back years?!< Pure magic.

I feel like the whole episode was building towards that moment in the end >!with the two of them.!< The point of this episode really seems to be that it's important to show up for the people in our lives. Even if you're busy and you can't stay for long, even if it's inconvenient and you have other shit going on in your life, even if you're just not sure, just show up. It matters when you show up. And you don't know what someone's going through - so showing up might matter more than you expect. It lets people know that they matter to you - that they aren't some isolated, solitary rock in a sparse, featureless garden. They belong to something, or as Unc so reassuringly said it, >!"You'll be a Bear forever. My condolences."!<

So, so beautiful. And refreshingly honest - I feel like a lot of TV weddings are just about the couple and how madly in love they are, and how great that they found each other, etc etc. And, at least in my experience, that isn't how weddings feel like in the real world. I mean, sure, there's some of that, but there's also so much else. So much drama. So much family stuff. Gossip. Old wounds. New connections. Weddings can be big, sprawling, chaotic, beautiful, draining events. The scope really isn't limited to just the couple. And this episode felt kind of like going to a real wedding, where you show up because it matters, especially when life gets messy.

Also, >!Claire Bear looks so pretty,!< no?

Asking because this question has some personal relevance to me. Would love to hear your experiences ❤️

View Poll

Hey love, goodnight.

I'm posting this on reddit instead of sending it to you because we haven't used the L-word yet (god, will we ever stop sounding like teenagers when it comes to relationships?)

Anyway.

I can't wait till I see you again. Hold you again. Kiss you again. I can't wait to see where this story goes. And I hope I'm right about how it ends.

Hugs and kisses,

X.

PS I think you have my yellow umbrella.

In our younger years, we have the freedom and the recklessness to act on our infatuations and crushes and feelings. And yes, it's all very exciting and passionate and clumsy and innocent. But we all grow up.

In our thirties, we're a bit more practical and a bit more scarred. We consider practical matters like finance, kids, marriage, place-of-living, etc. I suppose we also start thinking about looks differently, having aged a little ourselves.

I personally feel cautious when dating at my age now (30). I feel like I can't afford to get close to the wrong person, because time is running out. So, I'd love to know: how did you know that your partner is right for you? What do you wish someone had told you when thinking about this?

It's one of those exchanges which really captures the Boyle-Holt dynamic in my opinion. After working on some side quest, Boyle says something, and Holt's reply is:

"Well... we're off topic now."

That's all I remember :/

I know, it's not a lot. But any help would be really appreciated!

Another "is this normal/common?" post.

I work in a Python/JS team developing internal tools that other teams use. Some of these are quite critical.

Some of these critical tools depend on just a single person. No one else has contributed to or reviewed the code. They work most of the time, which is certainly a credit to the maintainers.

However, things break (inevitably). And sometimes they break when their sole maintainers are unavailable, making things difficult for the users and the rest of us trying hopelessly to hotfix things without enough information.

I've repeatedly told management and the PO that each repo needs to have at least 4 eyes on them. They shrug and agree, but never enforce any incentives or rules regarding code review and/or number of maintainers. I suspect they think that AI will come along soon enough to deliver us from the evil of bugs.

What do I do? In my view the management here is just asleep at the wheel. They don't have a tech background, so maybe they don't know how problematic this can be. But I don't quite buy this excuse: it's >!@#?!-ing!< obvious that you should not have single points of failure in your system.

Anyone here with experience in a similar situation, or can relate to my frustration/alarm?

I really like American TV shows - and I was looking up the most watched show episodes in history. I see that the finale of MASH is far and away the highest viewed broadcast among TV series. The only broadcasts with comparable viewerships are Super Bowls.

What was so special about MASH? Is it because there were fewer other options back then? Or the show was a cultural phenomenon unlike anything that came after it?

I haven't seen MASH, so I'd also love to hear from people who've watched the show. Does it still hold up?

Background

I started my Python journey roughly 4 years ago; when I was locked into a low-paying job with no prospects and looking for a way out. The hard work did pay off, and a few months later I landed what a tech job.

The first few months were rough, and there was a lot to learn. 3 years later, I felt like I was hitting my stride: Python started feeling like a native language. Never mind decorators and list comprehensions, I was making my way through asyncio and descriptor protocols. I was squashing more bugs than Mortein, and make more features than Karan Johar :P

Story

Cut to last week. I picked up a refactoring project to prepare an app for some upscaling. I thought it would be smooth sailing; but it was brutally painstaking, difficult work. My confidence was a little shaken.

In hindsight (refactoring nearing completion), I see that most of my time was spent in trying to decide about the new architecture of the app. What should the different components be? Where do you draw the line between separation-of-concerns and simplicity? What is more testable? Readable? Lowest latency?

Takeaway

Working on this tough refactoring really helped me develop a personal sense of what is good, scalable design. This sense/judgement, I realise, can only be developed through experience. It is what separates juniors from seniors. If you ever read an important PEP or Guido's newsletters, pay attention to how easily and clearly they are able to justify their choices, e.g. for f-strings, against labelled loops, etc.

With the rise of LLM-assisted programming, I feel like it's easier than ever to leapfrog over this kind of design-level thinking and just have code that somehow works. Consequently, one might never develop judgement or taste or clarity when it comes to designing software. It stunts growth.

.

.

.

TL;DR: Experience helps us become better coders/engineers by helping us hone our judgement. By using too much AI, we may never exercise that muscle and remain prompters.

Genuinely curious what y'all think, especially senior devs?

Edit: Formatting.