There was discussion about what the NYC subway announcements should say instead of “ladies and gentlemen”.

My vote was “listen up you little shits, [this train is going express until canal Street or whatever]”

I think they went with “everyone”, however.

Depends on the app. Some let you see all versions, I think.

Editing is a power not all people should be trusted with.

You all know at least one person (or are the person) who would text a yes/no like “Did you see Dave today?” and then when you write “yeah” edit their message to “Can I borrow your car?” or something you wouldn’t have said yes to.

Sometimes I still see job postings that are like “MUST KNOW OBJECT ORIENTED PROGRAMMING” and I’m wondering who in 2026 isn’t at least passably familiar with it.

But then again I also see job posts that are like “must know Java or JavaScript”

Well, we were literally walking in Manhattan when it came up, and couldn’t take the euclidean straight path. We could only walk on the grid of streets.

(This is setting aside factors like waiting to cross, or a busier street)

I’m the kind of guy who will look stuff up. I think it’s really important to admit when you’re wrong and the other person was right. Don’t move goal posts or claim you misunderstood. Just own it.

Like I was having a debate with my partner about if it was faster to go all the way up and over, or make a lot of turn-right then turn-left. I thought the ladder was faster because it approximates a straight line. She was like no that’s crazy. Eventually I found that’s called Manhattan distance and she was right, and I fully admitted defeat.

Ooh I remember that. That game was really popular in my friend group around 2008-ish. It spread to my work, too. Someone put a post-it note about the game by the time clock, and someone else invented a hand signal for it.

People are emotionally driven. Admitting something scary is more emotionally taxing than pretending it’s fake.

Oh! That’s what I’ve been doing. Works out fine and is easy to stick with.

It’s not really that different from like

my_get_mock = Mock(side_effect=Some exception("oh no"))
result = some_func(http_getter=my_get_mock)

There’s many ways of writing bad code and tests, but mocks and patches aren’t always a bad tool. But sure, you can definitely fuck things up with them.

Javascript has mocking with jest: https://jestjs.io/docs/mock-functions

There’s an example there of mocking our axios (a common library for network requests, a la python requests)

It’s been a long time since I’ve used java, but mockito exists: https://site.mockito.org/javadoc/current/org/mockito/Mockito.html#2

(Usage note for anyone unfamiliar, but despite the name java and JavaScript are radically different languages.)

I vaguely remember Java also has mocking libraries, as does JavaScript. (Though JavaScript isn’t a language I’d hold up as the ideal.)

with patch("some_file.requests.get", side_effect=SomeException("oh no")):
  result = func_using_requests()

Though not every language makes mocking as easy, and multiple responsibilities in a single function can quickly get messy.

I used to be better at math and coding. If I pulled up my old project euler solutions I’m not sure I’d understand them anymore.

Do you think the people that send junk like “hi” or “quick chat?” get annoyed when they’re the recipient? Or they just think it’s normal?

I feel like this topic somehow aligns with the form of a 2017 Twitter screenshot posted on tiktok posted on Lemmy.

I had a guy do this once when I was struggling to get my laundry bag into my cart. He just used his free hand to steady the cart for me, but didn’t stop his phone call.

Turning off almost all notifications, running adblock , and ditching social media (except Lemmy, if that counts) , seems to really limit the damage.

Oof. I’ve had places that the pipeline was getting long. At one of my previous jobs I made it so all the tests could run locally, and we were keeping the full build as slow as possible.

We also didn’t do any browser tests (eg: selenium) because those tend to be slow and most people are bad at making them stable.

It’s important to know whats worth testing.

There’s a lot of fear at my job about changing code. I’ve been trying to tell them to start writing automated tests. Or at least a linter to check for syntax errors. They’re all like “ooh that sounds hard maybe next quarter”

Meanwhile, a trivial change requires a whole day because the developer has to manually test everything.

I just unilaterally added checks to code I have ownership over, but anything shared I’m getting “maybe in two quarters we can prioritize this” from management.