I've worked as a Developer, Technical Lead (in charge of a small team), and a Senior Analyst Programmer (doing the scoping and requirements gathering as well as the solution development).
The day to day depends on what kind of team you're a part of and what industry you work in. A lot of companies have moved towards SCRUM/AGILE development.
In an AGILE work environment you come into work and usually start the day with a SCRUM or daily stand up meeting. This is the chance for the tech leads and project managers set and check priorities for the day/week/release. Everyone has a voice, but the objective of this meeting is to be quick and a quick information session. This usually spawns other breakout meetings or 1 on 1's with other coworkers to go into more detail if needed.
On a standard day I'm doing one of a few things. I'm either researching/designing, coding, code reviewing, or demoing functionality.
Research/Designing - Researching the requirements and asking questions if the requirements are not clear. This can be using a whiteboard to draw out the problem and the touch points. This can be just talking to coworkers to have someone else hear the idea/design.
Code Review - is when you review other coworkers code. Rarely do we code as a one-person team. We do code reviews just to provide a second set of eyes. Sometimes you can catch silly mistakes or sometimes you have some experience with the functionality that the other coder hadn't considered.
Demoing - depending on the job, you might have to demonstrate your code. This is a great opportunity to show off your work. You will learn a lot in these sessions because you start to figure out what the end users (the people using your programs) really care about and how they use the software.