No not at all. Software Engineering is about building systems to the appropriate quality level.
For projects I'm usually involved in: this means being disciplined, writing good quality tests, keeping code clean, documentation and following the various practises and conventions. This, if you're doing it properly, means you'll be able to ship code much faster than if just "programming".
I use scrum by choice; but you can deploy a lightweight version that cuts a lot of the bullshit if you have a good team.
If you're re-architecting things then that's a huge red flag. Unless the underlying assumptions have changed enormously or you're working for a start-up who had inept "programmers" (like myself 20 years ago) YOLO'd V1 then what you're doing ain't engineering.
For projects I'm usually involved in: this means being disciplined, writing good quality tests, keeping code clean, documentation and following the various practises and conventions. This, if you're doing it properly, means you'll be able to ship code much faster than if just "programming".
I use scrum by choice; but you can deploy a lightweight version that cuts a lot of the bullshit if you have a good team.
If you're re-architecting things then that's a huge red flag. Unless the underlying assumptions have changed enormously or you're working for a start-up who had inept "programmers" (like myself 20 years ago) YOLO'd V1 then what you're doing ain't engineering.