ourob
My previous job had daily 30-60 minute “stand ups” and weekly 2+ hour sprint planning meetings.
It’s not “proper” agile/scrum/whatever, but in my experience it never is. No agile plan survives contact with the enemy (management).
Thank you for adding an option to disable swiping on posts and comments! I don’t know when it was added, but it’s a necessary feature for me.
There’s no downside to writing the guards afaik, but I’m more of a c programmer. It’s been a while since I did much c++, so I’m not up on modern conventions. But dealing with legacy code adhering to older conventions often comes with the territory with c and c++, so it’s something to keep in mind.
You can generally rely on a header file doing its own check to prevent being included twice. If a header doesn’t do that, it’s either wrong or doing something fucky. It is merely a convention, but it’s so widespread that you really don’t need to worry about it.
You are mixing up some terms, so I want to help clarify. When you #include a header file, you aren’t importing a library. You are telling the compiler to insert the contents of that header file into your source where the #include line is. A library is something different. It is an already-compiled binary file. A library should also come with a header file to tell you what functions and classes are present in the library, but that header isn’t itself the library.
It may seem annoying to have to repeat yourself between headers and source, but it’s honestly something you get used to.
It’s Schroeder’s war. The classification changes depending on the political context.
It is a war in contexts where not calling it a war would be politically harmful (like denying thousands of wounded Americans benefits). It is not a war in contexts where calling it a war would imply that the president vastly overstepped their constitutional bounds.
“Stop laughing! I was in the pool!”
Behind the Bastards has a great 6 parter on Kissinger:
I would love to see the cost/feasibility of boosting to a stable/graveyard orbit. The ISS is massive and not built for that kind of maneuver, but it would be great to be able to preserve it for the future.
Reminds me of
To be clear, dmesg -w should be run before you do anything to cause the crash. It will continuously print kernel output until you press ctrl+c or the kernel crashes.
In my experience, a crashing kernel will usually print something before going unresponsive but before it can flush the log to disk.