We are eventually going to stop writing code and focus more on writing specifications.
I don't think this will happen in my lifetime.
We are eventually going to stop writing code and focus more on writing specifications.
I don't think this will happen in my lifetime.
100%. In my opinion, the whole "build your program around your model of the world" mantra has caused more harm than good. Lots of "best practices" seem to be accepted without any qualitative measurement to prove it's actually better. I want to think it's just the growing pains of a young field.
You shouldn't have any warnings. They can be totally benign, but when you get used to seeing warnings, you will not see the one that does matter.
And, you can have pointers to bits!
Algorithms + Data Structures = Programs
Niklaus Wirth
60k rows of anything will be pulled into the file cache and do very little work on the drive. Possibly none after the first read.
Meh. I had a bash job for 6 years. I couldn't forget it if I wanted to. I imagine most people don't use it enough for it to stick. You get good enough at it, and there's no need to reach for python.
Heh, the red alert readme says it currently requires borland for the asm and watcom compiler for the c/c++.
I'm on your side dude. Comments rot. Some are useless. Don't even get me started on doxygen comments.
She already exists! I swear!
To me, Microsoft's entire transition to web technologies is a self inflicted wound. Going native is a massive performance win. They already had that, and went the other way. Just, Why!? Now, Microsoft software is all big, bloated, and slow as fuck. Even the OS. They were literally bragging about a 9 second start up time after some optimizations to Teams. They don't even know what efficiency is anymore. We all essentially have super computers, now, but sure, congrats on your 9 second load time for a fuckin chat program.
Not saying you're wrong because I don't use it, but from the outside, they appear actively hostile toward developers.