It is maddening how little stock game makers put into things like reset times, load times, and so forth. If you build a hard game that expects me to die a lot, don’t make we wait 45 seconds after each death to get back into the game. A big component here is the load times you talk about.

It makes sense, you aren’t telling sql server how to do something, you just tell it what you want and it figures it out. You aren’t even doing procedural stuff at that point.

I like the RAD tools being qualified as 4GLs as I haven’t really thought of them that way but again it makes sense.

Also screw PowerBuilder. I am sorry if anyone in this thread likes it…but it is seriously awful.

Edit: Before people jump me, I do know that you have some influence over execution plans with join orders, hints, etc… but by and large you don’t tell SQL Server how to do it’s job.

The - works with git branching as well for those who didn’t know. git checkout - will switch to the previously checked out branch so it effectively toggles between your two most recent branches.

This is a huge one for me. For those who don’t know, this brings up the rev-i-search utility which allows cycling from most recent to oldest commands executed. It also supports partial finds so if you did ‘cd’ it would cycle the most recent change directory commands.

The forward search (in case you’re somewhere in the history stack) is ctrl+s and operates the same except crawls the command history forwards.

I use these constantly in my normal workflow and they save a ton of time.