Live data from Hacker News

A DOGE staffer appears to be posting DOGE work on his public GitHub

twitter.com

41–50 of 404 posts

Re: A DOGE staffer appears to be posting DOGE work on his public GitHub

#41
A bit tangent, and since I’m an outsider who doesn’t live in the states and have no skin in the game — my understanding is, they will do literally anything to make sure DOGE succeeds, because a failure is basically unacceptable. I can’t even imagine how you can backtrack this, and fix stuff up. They obviously prepared for it months in advance. Targeting ex-employees of successful product companies and putting them in charge (especially the ones with a lot of money, but a bit lost because they want can’t find meaning in life) is also kinda funny.

That being said, if it doesn’t succeed, they will start doing the usual — pretending that it was successful. And that’s when the team-sports based politics come into play. If you’re so deep into supporting one side that you can’t objectively see failures, the narrative pushers will keep winning. It applies to both sides, by the way. But burden of proof lies on the government in power.

Good luck to you, guys!

Re: A DOGE staffer appears to be posting DOGE work on his public GitHub

#42

Earlier quoted context omitted.

I don't care about the twitter DM thing, I care about gathering ton of open source sensitive data by an organization which is disemboweling the bureaucratic apparatus from within

Posting linked in followers seems egregious to me. Guilt by association publicized for people to troll or harass people? What happened to pretending or trying to be better than the people you hate? Why sink to their level? Gathering open source data is a problem? lol it’s open!

You can buy soil fertilizer and other things online, but with a specific combination of purchases 3 letters agencies will think you're building a bomb.

The same way, an agency who is led by a pathoilogical liar, who is not following pre existing guidelines to make the state apparatus more efficient, (and i could go on for hours) who has a worker who compiles an extensive list of sensitive infrastructure, even if publicly available, makes my spider sense tingle

Re: A DOGE staffer appears to be posting DOGE work on his public GitHub

#44

A bit tangent, and since I’m an outsider who doesn’t live in the states and have no skin in the game — my understanding is, they will do literally anything to make sure DOGE succeeds, because a failure is basically unacceptable. I can’t even imagine how you can backtrack this, and fix stuff up. They obviously prepared for it months in advance. Targeting ex-employees of successful product companies and putting them in…

> Good luck to you, guys!

Unfortunately I think we're going to need a lot more than luck.

But I appreciate the sentiment.

Re: A DOGE staffer appears to be posting DOGE work on his public GitHub

#46
post #19
post #18

This tells me all I need to know: # Read the CSV file df = pd.read_csv(csv_file) Thanks for the explanatory comment Jordan /s

You can even tell that's ChatGPT rather than, say, Claude. Redundant obvious comments are a stylistic signature of their models.

I get redundant obvious comments from Claude Sonnet 3.5 and 3.7 all the time.

Re: A DOGE staffer appears to be posting DOGE work on his public GitHub

#47
post #19

Earlier quoted context omitted.

You can even tell that's ChatGPT rather than, say, Claude. Redundant obvious comments are a stylistic signature of their models.

I make comments like this all the time because I write code for people to read, not robots. Well-commented code allows you to skim very quickly, and gives a sanity check, allowing others to ensure a line or block of code does what it is expected to do.

That's not well-commented code, that's just noise. When you are calling a function named "read_csv()", you do not need to add a comment that says "Read the CSV file". These sorts of comments make code harder for humans to read.

The hill that I will die on is that if you need to comment what your code is doing, your code is either a) bad and should be rewritten to be clearer, or b) the result of tricky, clever optimization that you needed to do after profiling.

Comments should tell readers why you're doing something, when it's not obvious based on the code itself.

Re: A DOGE staffer appears to be posting DOGE work on his public GitHub

#48
post #19

Earlier quoted context omitted.

You can even tell that's ChatGPT rather than, say, Claude. Redundant obvious comments are a stylistic signature of their models.

I make comments like this all the time because I write code for people to read, not robots. Well-commented code allows you to skim very quickly, and gives a sanity check, allowing others to ensure a line or block of code does what it is expected to do.

This is a bad comment. It adds nothing to clarify anything, since the function in the line below is "read_csv." This would be a textbook example of a comment that is not useful to improve legibility by humans and it demonstrates a lack of expertise among the people who are currently dismantling our government.

Re: A DOGE staffer appears to be posting DOGE work on his public GitHub

#49

if you don't want to open twitter, here is xcancel link which i should have put as the og link https://xcancel.com/SollenbergerRC/status/189560929481046439...

The first thing I wondered is why you'd post this information on Twitter of all places, to be honest.
Post reply on HN