1. The applications I write don't have a GUI. They typically don't run attached to a console either, except maybe during initial debugging. Depending on the job I did, their inputs may be signals from sensors (e.g. direct TTL input from a battery of OPTO-22 switches), serial, UDP or TCP data, tables from a database, data files, etc, and their outputs may be signals to motors and other hardware, update statements to databases, writes to files, ports, or network.
2. Business apps, Science or Mathematical thingy apps, others
3.
Do you code every second (except for break time)? |
No, although there have been a few crunch times when I had to code "every second" (no break time, through the night, with high-ranking managers supplying coffee and pizza). Maybe a day every five years on average.
Is there a day passed by without doing anything? |
Not really, although there have been kickback days (especially when I worked for a smaller company) when I could finally pay attention to all those old low-priority tasks or update the non-essential documentation.
are you just sitting there waiting for the boss or whatever to ask you or your team to make the following program? |
New projects don't start every day, and don't come to hard deadlines every day either. Daily job is to look at your open tickets/tasks/requests/whatever the company calls them and work on whatever has the highest priority.
Your mileage may vary, by a very wide margin. For example, all the jobs I had for the last 10 years, have me 24/7 on-call, so there's always the chance that I would have to log in at 4 am from a resort hotel to fix something (done that many times actually).. Depending on where you work, this may never be a part of your everyday life.