I wish people paid this close attention to federal workers and their agencies all the time.
Quite a few people do. Most of them just have editors who fact-check things prior to publication.
A DOGE staffer appears to be posting DOGE work on his public GitHub
151–160 of 404 posts
Re: A DOGE staffer appears to be posting DOGE work on his public GitHub
#152Earlier quoted context omitted.
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 optimiz…
I agree that there should be "why" comments. Those are great to have in any codebase. However, that does not preclude descriptive comments. Obviously, the best way to make code self-documenting is to wrap logic in a method whose name clearly describes its intended function. For one-liners however this can lead to overabstraction, and leaving a "what" comment can be entirely appropriate if the engineer decides it is.…
Every word of the comment is in the code except "the". That level of redundancy is always bad. Yes, always.
Re: A DOGE staffer appears to be posting DOGE work on his public GitHub
#153A surprisingly large amount of data one might think is classified is not at all. In this case all the examples listed are from freely available public data outside of the Twitter thing which seems to be just setting up the environment for some local tool. Here are the sites: --- datacatalog.worldbank.org opendata.arcgis.com mrdata.usgs.gov / www.usgs.gov --- Sharing things like this isn't very useful because it just…
While this is the lede there are other activities posted. If there were true transparency with nothing to hide Mr. Wick would not have taken the repos private but just ensured that that all avenues of harassment were disabled. More of concern to me is the potential for a focus on the union status - though with just the screenshots it is quite difficult to tell what is really going on.
Giving the benefit of the doubt to the author... finding the quickest and easiest way to stop harassment and backlash is what I would have done too. The author is a mere human, likely not equipped with the mental fortitude to deal with the magnitude of armchair bullies that are likely aimed at them.
Re: A DOGE staffer appears to be posting DOGE work on his public GitHub
#154A surprisingly large amount of data one might think is classified is not at all. In this case all the examples listed are from freely available public data outside of the Twitter thing which seems to be just setting up the environment for some local tool. Here are the sites: --- datacatalog.worldbank.org opendata.arcgis.com mrdata.usgs.gov / www.usgs.gov --- Sharing things like this isn't very useful because it just…
Usually: actually a third world is real. As constructed in your narrative there is a difference in the deltas between the two worlds and the third (i.e. one is more real).
Re: A DOGE staffer appears to be posting DOGE work on his public GitHub
#155A 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…
> my understanding is, they will do literally anything to make sure DOGE succeeds, because a failure is basically unacceptable.
Not sure I buy that. My general expectation is that once there’s a big, major problem which annoys the general public, Musk will be thrown to the wolves. See Trump’s previous go round; very few of his people stayed in favour for the whole administration.
Re: A DOGE staffer appears to be posting DOGE work on his public GitHub
#156Earlier quoted context omitted.
He's not looking at, he's gathering
I gather things like this all the time. I'm against DOGE as much as 90% of the US is, but collection of open data for curiosity and interest is really not a thing to focus on.
That's completely fair.
However, i am let's say, at least dubious about the whys of an agency which is wreaking so much havoc need to collect data on us sensitive infrastructure. If you were dealing with drugs, and you told me you buy codeine based pharma products in bulk, i wouldn't think you caught a cold
There are companies that are making bucks selling satellite photos of russian army storage(s) so that it is possible to calculate how much of remaining tanks are in storage. While a single photo of a single storage wouldn't matter on its own, having a clear picture of every russian storage can give you an idea of how many tanks were refurbished and remain in stock
Re: A DOGE staffer appears to be posting DOGE work on his public GitHub
#157Re: A DOGE staffer appears to be posting DOGE work on his public GitHub
#158Earlier quoted context omitted.
idk try to make a FOIA request
DOGE moving under the presidents executive office instead of as a separate agency seemed to be done for the purpose of shielding DOGE From FOIA and only subject to President Records Act
And Trump's history with that act suggests it'll go to the highest bidder, foreign or domestic
Re: A DOGE staffer appears to be posting DOGE work on his public GitHub
#159Earlier quoted context omitted.
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.
I'm sorry, but a code comment does not demonstrate lack of expertise, although such a perspective certainly brings your own expertise into question. Perhaps we should all assume a little less?
Yes it clearly does. A comment that is 100% noise and adds no value whatsoever to the codebase demonstrates a lack of expertise. I would expect undergrads and very junior engineers to write comments like this and then very quickly stop when told why these sorts of comments are a straightforwardly bad thing.
Comments are good. I am a huge proponent of more comments over fewer comments. I have written functions where 80% of the lines are comments. But this is a bad comment for very simple to understand reasons.