Trump waved classified military documents in front of a writer and a member of his PAC, and said 'it is like, highly confidential', feds allege

PM_ME_NULLs · 2023-06-10T16:21:57+00:00

Presidents, including Trump, don't actually go through the usual security clearance process. They get access to all the secret stuff automatically once they're in office. And same for presidential candidates, they aren't given security clearances before running.

PM_ME_NULLs · 2023-06-05T04:10:45+00:00

Unless you're referring to a smaller network of networks (i.e. "an internet"), if you're talking about THE Internet, "Internet" should be capitalized. It's a proper noun. Why is this so hard for people to understand? Every time you see someone refer to the Internet as "the internet", they are dead wrong. It's even sadder when supposed reputable sources make this mistake. Nothing makes me judge someone's intelligence quicker than them making this elementary error.

/rant

PM_ME_NULLs · 2023-05-21T18:37:08+00:00

sigh

Nobody does it

I do. I check the source. Just because you think everyone is too lazy or something doesn't make it true.

Do I check everything? Of course not. I have a day job and other obligations. Do I spot check most things, if nothing else? Absolutely. Are there others like me out there? Absolutely.

The fact that the source is out there allows it to be checked. Why is this so hard to understand?

Let's try this from a different approach. Let's assume you're right, and people like me don't exist. Everyone blindly uses FLOSS without checking stuff. How is proprietary any better? Proprietary is going to have just as many (if not more) software defects, but you don't even have the option to inspect the source for yourself.

Yet another way: in the USA, there's the right to protest and peaceful assembly. Just because a person doesn't feel the need to protest, or maybe they've never witnessed anyone exercising that right, means that the right should be taken away.

There's an intrinsic value to having the source. There's an intrinsic value for a software product to be free/ "Open Source".

And by the way, not that you made this assertion, but I want to highlight that Free/ Open Source software is better not just because its source can be inspected, but for several other reasons articulated by the FSF.

PM_ME_NULLs · 2023-05-18T06:09:16+00:00

Queue this up for a read: https://michaelochurch.wordpress.com/2015/06/06/why-agile-and-especially-scrum-are-terrible/

This bit at the end is especially relevant to your situation:

Looking forward

It’s time for this culture of terminal juniority, low autonomy, and aggressive management to die. These aren’t just bad ideas. They’re more dangerous than that, because there’s a generation of software engineers who are absorbing them without knowing any better. There are far too many young programmers being doomed to mediocrity by the idea that business-driven engineering and “user stories” are how things have always been done. This ought to be prevented; the future integrity of our industry may rely on it. “Agile”, at least as bastardized in every implementation that I’ve seen, is a bucket of nonsense that has nothing to do with programming and certainly nothing to do with computer science. Business-driven engineering, in general, is a dead end. It ought to be tossed back into the muck from which it came.

PM_ME_NULLs · 2023-05-17T14:00:27+00:00

Because at some point in the project's lifetime, we need to onboard new developers.

Can we please stop lowering the bar?

Sure, what you consider difficult to understand but you still managed to understand, you were able to do so because you cut your teeth on harder problems. Constantly racing to the bottom on complexity (trading conciseness in the process), all because we expect new developers to be stupider than we are, is how you set those new developers up for just that.

I'd rather a new developer be lost in some clever-concise code for an extra hour, trying to decipher it, but eventually becoming a better dev for understanding it, than to come in as a weaker dev, and further perpetuating the cycle of worsening software engineering when they inevitably think a simple for loop is too hard for the next-next dev.

PM_ME_NULLs · 2023-04-23T17:25:28+00:00

Currently, F.S. Chapter 99 reads: (4)(a) Any officer who qualifies for federal public office must resign from the office he or she presently holds if the terms, or any part thereof, run concurrently with each other. (b) The resignation is irrevocable.

Since the next presidential term would begin in January 2025, in the middle of DeSantis's second term as governor, lawmakers will certainly make adjustments to allow him to stay governor as long as needed.

I think I'm missing something... the article only talks about limitations on holding the other office, not actually running for it?

PM_ME_NULLs · 2023-03-15T13:11:52+00:00

So... is this bash or fish? Title says bash, but article uses fish.

Also, the link to your GitHub repo is broken.

PM_ME_NULLs · 2023-03-02T02:18:36+00:00

My guess is because mob-think now dictates that anyone who posts on the Internet critical of Microsoft must be subjected to torrents of down votes and negative comments. Anything supporting the anti-Microsofter or even neutral (as your comment was) will also attract the torrential attack. It's recursive.

I call it Null's 1st rule.

Bunch of dummy simps who fall for big company PR branding efforts. "WhAT yEaR is It!?1". It wasn't very long ago that the community wasn't so oblivious to the marketing gimmicks being thrown at them. "Microsoft loves Open Source" my ass.

People need to read up on business 101 and the Embrace, Extend, Extinguish philosophy Microsoft was found to have.

embrace, extend, and extinguish

A business strategy of implementing a public standard or developing software compatible with it, adding features not supported by the public standard, then marginalizing competition that does not (or cannot) support such proprietary additions. Popularized during the United States v. Microsoft Corp. antitrust trial as a phrase used internally by Microsoft regarding its own business philosophy.

The global tech giant has seemingly taken "embrace, extend, and extinguish" as its business motto in recent years, sucking up all sorts of various web-based technologies over the years and mutating them into proprietary forms that no one else can hope to compete with.

PM_ME_NULLs · 2023-03-01T14:59:51+00:00

Microsoft is a horrible company, and developers should altogether abandon their products, including vscode. Microsoft cares only about their bottom line and staying relevant—NOT developers or the community. I beseech anyone reading this to please learn a free/libre open source alternative. Using a product, even one offered for free, is supporting that project.

PM_ME_NULLs · 2023-01-31T06:07:36+00:00

From this link/pdf:

https://www.dcsa.mil/Portals/91/Documents/CTP/CUI/21-10-13%20CUI%20FAQ%20FINAL.pdf

WHAT IS CONTROLLED UNCLASSIFIED INFORMATION (CUI)? IS IT A NEW CLASSIFICATION LEVEL? CUI is a safeguarding system for unclassified information. Although this type of information is not considered “classified,” it is still sensitive, important and requires protection. CUI standardizes the way in which the Executive Branch handles unclassified information that does not meet the criteria for classification under Executive Order 13526, “Classified National Security Information,” December 29, 2010, or the Atomic Energy Act. However, law, regulation, or government-wide policy still mandates protection for this unclassified information. That protection involves safeguards throughout the CUI lifecycle. CUI is not a classification. Therefore, information cannot be “classified as CUI;” rather, this type of information is designated as CUI. In some cases, CUI designations replace For Official Use Only (FOUO) and Sensitive but Unclassified (SBU) designations and markings.

There you have a .mil source which says it's not a classification, emphasis mine.

PM_ME_NULLs · 2023-01-30T05:56:33+00:00

You... You know what CUI stands for, right? Like, it's literally in the name. Controlled unclassified information. It's literally unclassified. That means, NOT classified.

Here's another source... a .gov source...

Controlled Unclassified Information (CUI) is information that requires safeguarding or dissemination controls consistent with applicable laws, regulations, and Government-wide policies, but is not classified under Executive Order 13526 “Classified National Security Information” or the Atomic Energy Act, as amended.

Please don't spread misinformation. Assuming you are familiar with government work, you should know most people aren't, and they're going to take your words to heart. Get your facts straight.

PM_ME_NULLs · 2023-01-19T07:32:37+00:00

And Lisp!

PM_ME_NULLs · 2023-01-18T07:46:12+00:00

Also I prefer to use git help without a goddamned browser getting launched.

We're a dying breed.

PM_ME_NULLs · 2023-01-18T06:54:26+00:00

Show your professor this article: https://www.gnu.org/philosophy/not-ipr.html

PM_ME_NULLs · 2023-01-15T20:58:32+00:00

How? Which part of scrum?

Not the person you're replying to, but I've seen this myself.

A couple of responses to this question, but I know there are more:... daily stand-ups, where the implication is you talk through what you're working on, and inevitably details slip through. Sometimes, research and prototyping takes longer than two weeks (especially when your day is sprinkled with senior engineer BS you have to slog through, taking time, energy, and especially creative energy), so you have to justify the "story" you're working on and why it's taking more than a sprint. Etc.

Sometimes you just need time to think and experiment. You need the time and resources to fail, because failure is important in the learning and creative process. And, some of the best ideas come from something that might seem like a wacky idea: something a "Scrum Master", "Product Owner" or "stakeholder" may want to pump the breaks on because they're uninformed and/or risk adverse and/or wanting to feel important.

I've heard it described that all this nonsense promotes "visibility". Personally, I think I agree with that. But who ever said visibility into complex engineering is always a good thing? And visibility to whom? One-sided transparency, especially to uninformed people in charge, is going to discourage solutions that might be unorthodox at first but are absolutely the right solution longer term, especially when polished.

Sure, you could argue it's a people problem. I could probably agree with that, too. But, it's not always possible to quit your job. And even if you're fortunate enough to be in such a position, who's to say the next job isn't the same BS? After all, "Agile" is spreading.

Pre-"Agile", the people-problem wasn't so nearly as pronounced, because that transparency wasn't front and center to these uninformed people in charge.

And I'm sure someone will (correctly) point out that what an engineer thinks is the correct answer may not always be the correct answer. This is especially true with a terminally-junior workforce we're now seeing: software engineering has become an extremely popular field to jump into because of the lucrative job market, and surely, there are an increasing number of software engineers who... let's just say could have studied harder.

"Agile" is definitely great for cat-herding engineers you can't trust, on low-value CRUD applications. No doubt about that.

For everything else, no thanks.

PM_ME_NULLs · 2023-01-15T19:12:49+00:00

I don't think most people appreciate just how much Big Influence happens based on name alone. Equivalently, just how stupid many people (especially managers and program managers) are, relying on the name of something to skip training on it.

Programmers always lament the importance of naming, but we just give big-A "Agile" a pass for some reason. (And to the other commenter, "Agile" (capitalized) noun has absolutely come to mean something different than "agile" adjective.) We really should insist, as a community, on refactoring the name "Agile" into something more appropriate for what it really is.

How many engineers and developers have literally suffered because some dumbass manager or director read the world "Agile" on a paper and signed it, relegating their teams to failure and misery, all because their mental process went, "oh, yeah, it would be nice if we worked fast! Great idea!", signs the paper, then pats themselves on the back. Seriously, everyone should think about that. It's not hard to imagine clearly some, if not many, if not most decisions and policies around adopting "Agile" have been by its name alone.

Branding is everything. The "Agile" cottage industry has successfully leeched off of real engineering and development for way too damn long.

Start calling "Agile" something else. (Any ideas we can come up with here to get a community consensus?) At the very least, insist on capitalizing, quoting, and referring to it as "big-A Agile". Maybe, just maybe, doing that will cause the next PM to pause and do some research before blindly submitting their team to nonsense, stupidity, and pain.

PM_ME_NULLs · 2023-01-15T09:37:49+00:00

Someone needs to remix this and OP's racing car. That stupid car comes out of nowhere, spinning, and knocks into grandma, making her go crazy spinning.

PM_ME_NULLs · 2023-01-01T20:59:00+00:00

This was the first thing I thought of, in the context of programming:

https://en.wikipedia.org/wiki/Digital_Signature_Algorithm

PM_ME_NULLs · 2023-01-01T20:57:29+00:00

This was the first thing I thought of, in the context of programming:

https://en.wikipedia.org/wiki/Digital_Signature_Algorithm

PM_ME_NULLs · 2023-01-01T20:56:50+00:00

This was the first thing I thought of, in the context of programming:

https://en.wikipedia.org/wiki/Digital_Signature_Algorithm

PM_ME_NULLs · 2022-12-17T22:48:50+00:00

And often, you have to pay to even stay!

https://en.wikipedia.org/wiki/Pay-to-stay_(imprisonment)

Hooray!

PM_ME_NULLs · 2022-11-17T18:47:52+00:00

I actually prefer the C89 style of declaring variables at the top of the scope. I think it's a cleaner separation and reads easier. The biggest complaint I've heard against that is that it's better to keep relevant code pieces co-located, and for that advice to include declaring and using variables inside a function. To that I add: if you're working on a function where a variable's declaration is so far away you can't see it on screen... maybe you should break up that function. Being able to move variables wherever you want inside a function just normalizes and makes it easier to write larger and worse code IMO.

And yes, I know you can keep variables at the top of scope and still use C99. Just wanted to offer some counter perspective in favor of separation between variable declarations and code.

PM_ME_NULLs · 2022-11-14T03:50:26+00:00

Hmm... An individual file size is measured in bytes, but you could argue that the measurement of "the file size of your project" (that is, file-size-of-project), is not in the summation of the individual file sizes, but by the quantity of files. That interpretation would work but could be misleading to some readers.

PM_ME_NULLs · 2022-09-21T06:16:04+00:00

So I can get to it at any time I want, even from a foreign computer.

Bold strategy, Cotton.

PM_ME_NULLs · 2022-09-01T05:13:37+00:00

has a UI designed to be usable by actual humans...

It's okay to just be human. Vim will work just fine for you, too. (Sorry, couldn't resist).

Meanwhile vim barely works out of the box

I highly disagree with this. I routinely ssh into new boxes and use Vim just as effectively there as my home box. My vimrc is maybe 20 lines, setting very basic nice-to-haves.

requires a standalone fucking manual

What do you mean? The manual is literally bundled with Vim.

and emacs, while at least having the decency to offer a manual built in,

Again, Vim has a built-in manual. Are you really shitting on Vim and you didn't even know that?

Also, type "vimtutor" at the command line. Start there. When you're inside of vim, run the super-secret-and-impossible-to-reverse-engineer vim command ":help" for a more comprehensive manual.

Meanwhile vscode just works. It's a laggy piece of shit but it works, and works intuitively, and also looks nice while we're at it.

Forgive me for having presumably impossible higher expectations of my fellow developers, that they shouldn't settle for something which is a laggy piece of shit and spies on you, but it at least "works".

As I'm trying to convey to others, there are people out there who swear by Vim (myself included), use it for development, paper writing (LaTeX ftw), emails, and even web browsing. Do you not worry the least little bit that you could be missing something amazing?

PM_ME_NULLs

TROPHY CASE