“they are the same picture” -my wife

My thoughts on it are: as a developer, if you flag the issue for your management, and they want to move forward, then you’ve done your part.

Maybe put an extra comment in the code for posterity’s sake.

It’s not ultimately your problem and what else are you going to do? Work unpaid nights and weekends to fix it for some guy who might run into a problem 8 years from now?

Why did you get kicked out?

I can’t tell if ops joke is “intentionally confusing buffers with registers” and everyone is playing along or if people aren’t making the distinction between the two in this thread.

Which is ironic and humorous…potentially by accident.

Lmfao. This feels so tone deaf

There are different audiences for demos though. It should be that way at the “working level”. When you start moving up the chain with more senior leadership in your org, it starts to make more sense to have the PM do the demos/briefs.

Usually devs don’t particularly care or want to and sometimes they aren’t really qualified to–its not their skillset. But if it’s a good PM, that’s where they shine. That’s the value they bring to the project. They (should) know the politics, landmines, things that specific leaders would care about (and to highlight for them), and how to frame it to current business needs. They have the context to understand when a seemingly innocuous question is actually pointed. They might not know the intricacies of your code, but they (should) know the intricacies of the organization. That’s not something most developers know, and why should they? That’s not their job.

Sometimes it even involves groundwork meetings and demos to make sure you have support from other key components in your org-- like getting your CTO excited because one of his performance goals was x and your project is the first real implementation of x. Now, you have the CTO ready to speak on your behalf in front of the CIO. As a PM you know that the CIO has been getting flack from the CFO because there hasn’t been a good way to capture costs for Y, but your system starts the org down the path to fix that. Now they are both excited about the project and in your corner. Etc etc

As a former PM/PO who has moved up the chain, your PM is full of shit and you should look around. Looking out for your top talent is how you succeed as a PM.

I said this a while ago but you know how we have “pre-atomic” steel? We are going to have pre-LLM data sets.

Cobol devs that we had (while we spent insane money to retire their systems) we’re getting 300-500k/year.

I’m sure companies are trying to rip off any young new entrants but 90k seems super low.

How many widgets have we transferred to acme this year?

Simple enough question right?

But then when you look at the data, each region works with acme’s local offices differently. Some transfer using one method, some offices mark the transfer in the system as “other firm”. Oh, and we don’t even get a data feed from the north west region because they still haven’t upgraded their shit so I can request a spreadsheet but it’s in a different format than everything else.

Then inevitably Acme has a different number of widgets that have been transfered. Because if a transfer gets kicked back or cancelled, it’s easier to just create a new transfer rather than go fix an old one because that process is laborious and requires tons of approvals so they just create a new transfer and send it over.

But yea, 20 minutes should be enough time to get you that before your meeting with Acme.

That’s exactly how you should respond. I’ve been on the requester for some of these and if my team gave me that as a response I’d just say “let me know what you find out or when you know more.”

It’s not a bad thing. I was just saying that’s probably why they are doing it.

Everyone is getting super protective about “their” data now.

Oh yea, GitHub copilot is pretty nice too. (trained on all those repos!)

I realize this is a “hate on GitHub” thread so I’m gonna get downvoted for this post too but it does everything I need it to do, the documentation is fantastic, and it’s the “defacto” repo for a lot of stuff.

I like GitHub. Microsoft has been a pretty good steward of it since they bought it. This change isn’t a big deal to me. They are probably doing it to limit AI LLM bots from hoovering up the code theyve already hoovered up.

GitHub pages is really nice too.

Lol. I doubt the inventors of regex know all of regex

This is dumb.

You have to think of new MacBooks like new cars. Each year BMW makes a new M3. It’s always a little better than last year. But who is buying a new M3 every year? Not most people. They are upgrading from their 10 year old M3 that’s finally kicked the bucket. And you know what? The newest m3 is a massive upgrade from that.

Now, pretend this midrange m3 chip is replacing someone’s old Intel MacBook pro from 6-7 years ago. It’s a huge fucking upgrade.

These dumb hot take articles are tiring.

There was a leaked OPM memo that was going to require DC govt workers to RTO. It obviously made a bunch of waves and they backed way off of it.

This is probably their compromise solution. Because the DC mayor and all of those poor unfortunate corporate commercial landlords were losing money. And businesses weren’t getting the foot traffic from office workers anymore.

The talented govt folks would walk. They already don’t get paid what their equivalents do in the private sector. RTO would have screwed the administrations ability to get things done.

That’s why theyve made infrastructure as code! So it’s all the easy part!

Hahaha I love that this is real.

Nano is a fantastic default editor for gui-focused distros. If you aren’t a command line wizard, nano is a better default because it’s a lot more straightforward.

That said, nano is incredibly limited and if you have any experience with vi/vim/nvim, it’s the best solution full stop. It’s so much faster and more powerful but hot damn is it unintuitive for noobs.