ourob
I couldn’t tell you what my blood type is, but you can load up Contra and stick an NES controller in my wrinkled hands when I’m 90, and I’ll input the 30 lives cheat without hesitation.
I’d say I’ve got my priorities straight.
If you have another pc, ssh from it to the problem machine and run sudo dmesg -w. That should show kernel messages as they are generated and won’t rely on them being written to disk.
Behind the Bastards has a great 6 parter on Kissinger:
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.
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.
Well, your fyre fest won’t have the name recognition that burning man does, so that alone probably won’t be enough to strike gold. You’ll need another hook.
Like, you’ll want to announce the world’s first AI-powered blockchain festival that will kickoff an entirely new industry of scam festivals. That should bring in the money.
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.
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).
Reminds me of