I thought this was pretty good, not least because it attempts to explain isolation levels, something I always found pretty tricky when teaching SQL. Mind you, I was only teaching SQL, and so isolation, as part of C and C++ courses so that our clients could do useful stuff, but explaining what levels to use was always tuff.
I used to drink this stuff back in the late 1960s, when my Dad was an RAF pilot based in Cyprus and I was about 15. You had to take it with a Sprite mixer if you wanted to retain your teeth.
I mean literally anything that leverages modern APIs.
WYSIWG Site Builders, text Chat bots, audio Transcription, voice synthesis.
Yeah building from scratch would take longer, but you can slap a UI, a DB/schema around modern APIs and output something that would be science fiction 10 years ago.
WYSIWYG sure builders existed 10 years ago and did not cost billions. Chat bots were a novelty since the NFT bubble hadn't popped yet, and they would invent NFTs to stake the economy on instead. Audio transcription and synthesis existed and did not cost billions.
Borland's debugger (came with Borland C++) was very good, if you can get hold of it. I removed copy protection from several games I owned using it, and actually fixed mouse support for another game.
I think it’s because C++ programmers tend to define themselves by the domain they work in. Game developer, embedded systems engineer, firmware developer, etc.
I feel like it implies "it's harder to make a word out of 'C++' than it is for things that already naturally evolved as words people say like 'Ruby', 'Python', or 'Rust'".
I would guess that you just remember at which file offsets you need to insert what, and which offset ranges you need to delete from the original file — and on file save you just do a single linear sweep to update the file contents on disk.
I wrote a blog about this many years ago: https://latedev.wordpress.com/2011/10/06/simple-windows-dial...
reply