Writing code is only one part of the work.
When I join a project, I also try to understand how the product works and how the codebase is structured.
During development, I may find an area that could be faster, a solution that risks becoming difficult to maintain over time, or a process that could be simplified.
If I believe it can make a meaningful difference, I discuss it with the team.
Performance, maintenance, builds and deployment are all areas worth addressing when they can materially improve the project.
When needed, I can also contribute to technical decisions and software architecture, not only their implementation.