Having a team touch base, followed by a daily standup, followed by a quality initiative meeting, followed by a biweekly support touch base, followed by a demo for a tool your team will never use, followed by lunch and learn session over some AI tool you’ll be forced to use, followed by your biweekly 1:1 with the manager, followed by the department touch base, followed by the company all hands… Aaaaand done with meetings. Finally, some time to get some work done… then your downstream customer wants you to investigate why their counts don’t match yours… “could you run the totals again? Could you run them broken down by hour? By minute? By second? Can you get me a list of each record at these 6 timestamps? Can I get them in a different format? Oops, the problem was on our end.” Great. And it’s 5 o’clock. Scrum master gonna be up my ass about story points tomorrow.
I mean… that is just good design. The main function should be the initializer and orchestrator of the logic. You should be able to look at the main function and tell, at a high level, what the program is doing. It should be usually pretty basic and procedural. Other functions handle the details and complexity.