This is a list of stuff that the average software developer does from week to week
- Code design
- Refactoring
- Algorithms
- Profiling
- Code reviews
- Building frameworks
- Evaluating frameworks
- API Design
- Learning programming languages
- Design patterns
- Logging
- Bug diagnosis
- Data Access frameworks (CRUD)
- Manual ad hoc testing
- Test scripting
- Manual test script runs
- Unit tests
- Testing on mobile devices
- Integration Tests
- Wireframing
- Color matching
- HTML, CSS, XAML, etc.
- UX workshops
- Graphics and animation
- Version control
- Using IDEs efficiently
- Problem tracking systems (Jira, DevOps, etc)
- Spreadsheets, word processors, presentations
- Wikis
- Machine learning / AI APIs
- Recording and editing videos
- Forums like Stack Overflow
- Meetings
- Messaging
- Phone/Video Chat
- Writing specs
- Interpreting specs
- Debates
- Mentoring
- Collecting user feedback
- Talks
- Deal with difficult coworkers
- Writing and interpreting user stories
- Designing databases
- Querying data
- Categorising data structures (unstructured, structured)
- Storing / retrieving blobs
- Business Intelligence
- Analyzing Telemetry
- Data importing / mapping
- Data cleansing / validation
- Cloud portals (Azure, AWS, Google, etc.)
- Diagramming
- Cost estimation
- Template management
- Domain boundaries
- Scripting
- Time/cost estimation
- Marketing
- Time management
- OSs (Linux, Android, iOS, macOS, Windows, watches etc)
- Networking (Http, TCP/IP, etc)
- Follow or manage Agile, Scrum etc.
- Management
- Technical Support
- Tweet Gists from Github
- Business analysis
- Researching technology
- Typing
- YAML, PowerShell, Bash
- Octopus, Team City, etc.
- Cloud deployment
- Release / SDLC management
Developers do so many things, but I think it all depends.
One person can't cover all the processes. I'm just a beginner, and I do very simple and basic things to get more experience and skills. But I also spend some time online looking for different sites of developers, case studies, and so on just to get inspiration. Some time ago, I came across this case study where I read about creating a CRM for the banking sector, and I was impressed. I can just imagine how complex that work was and how many different processes it had. It's good from time to time to read something like this, especially for future developers or for someone who needs to have something like this for business.