Program sucks at something it was not designed to do.

surprisedpikachu.gif

The requirements have always been the same. Only now they’re reflected more accurately in your docs.

Doesn’t matter if the mechanism that checks the repo and sends the trigger message to the runner is down.

The fewer magic blackboxes are around, the

• (happy variant) easier it is to train new people and the less mental burden there is on existing staff
• (sad variant) easer it is to fire people.

I marvel at the proficiency with which Microsoft tears down every piece of software it touches nowadays.

Sending “temporary” changes into your CI pipeline isn’t even stupid, it’s borderline malicious.

No? “Hey customer, I’ve deployed the changes you requested to the staging area. Is this what you had in mind? Keep in mind it only looks good and isn’t fully functional yet.”

That means that the HR account thinks what the employee account wrote is bad, too. Both posts are bad extremes.

As an employee, if i find a prospective colleague who doesn’t ask about what they’re supposed to be doing at all, I’d be wary of them, too.

Depending on the configuration, a linter may cause the compilation or a CI pipeline to fail.

Yes, I’d rather have 35 different IDEs for every task I need to do. Much better than One To Rule Them All.

Recall stores an image every few seconds. 5 minutes is indeed much worse. Think of all the content they’re missing!

The navbar has an annoying left border.

multiple people edited my question to change the grammar and take out the thanks and smiley at the end

Well, the Welcome Tour tells you that SO is about “just questions and answers”. This facilitates finding a question that’s written as concise as possible, checking its answer, and leaving. SO is deliberately not like a forum.

SE seems too heavily focusing on helping a “generic public” rather than the actual people asking the questions.

This is just another consequence of not being a forum. Of course SO wants questions to be helpful to as many people as possible. I don’t see how that is a bad thing.

If you want a laxer approach to handling quality, consider if you’ve ever found useful information on yahoo answers.

I was going to list a whole bunch of things the DETAILS tag doesn’t allow, but it seems that none of these issues actually appear. So either it has evolved since I’ve looked at it last time or I was stupid.

Either way, thanks for talking back.

What’s a native HTML element that mimics Bootstraps Collapse?

It also has lots of UI widgets like collapsing elements, modals and alerts. Sure, you could code all these by hand, but why bother?

There’s therapy programs where children can read books to dogs (RTD).

RTD involves children reading to a registered dog with benefits to well-being and reading outcomes thought to arise because of the unconditional positive regard and non-critical listening bestowed on the child by the dog.

https://onlinelibrary.wiley.com/doi/full/10.1111/lit.12345

This has little to do with the image, I know.

JavaScript has types and it does have type errors, for instance

> null.foo
Uncaught TypeError: null has no properties

Please stop spouting nonsense on issues you know nothing about.

I find both horrifying.

This is how I’d want to read it:

			{
				emit differentFiles(
					ckFile.absoluteFilePath(),
					otherFile.absoluteFilePath(),
					FileCompareWorker::FileComparisonParams{
						FileComparisonParams::FileNameMatch,
						(ckFile.size() > otherFile.size())
							? FileComparisonParams::File1IsLarger
							: FileComparisonParams::File2IsLarger
					}
				);
			}

Email to all:

“Due to budget constraints, resources will shift from $oldThingy to $newThingy. As a result, $oldThingy’s availability can no longer be maintained at the previous level.”

Then randomly kill oldThingy for more and more hours each day.

https://xkcd.com/703/