Absolutely agreed. If your code line by line isn't clear, then the code is the problem.
Commenting before a block of code (a function / algorithm or whatever) explaining what it is meant to do, absolutely that's great though, saves time when revisiting.
I just put "software engineer", or "senior programmer". It's all the same to me.
Software Architect is an altogether different thing, although in my career I've had to do a bit of it, it was never a principal task. And these days that job is often driven by "Tech Director" or "Tech Lead" or the 20 other titles that don't mean that much.
After 15 years as a "Programmer", I've done architecture, design, programming, debugging (so much debugging), instrumentation and iteration, integration, build management, team management, and lead/director tasks. Don't care what my title is, just pay me what I'm worth, and let me code.
My take is that no matter which language you are using, and no matter the field you work in, you will always have something to learn.
After 4 years of professional development, I rated my knowledge of C++ at 7/10. After 8 years, I rated it 4/10. After 15 years, I can confidently say 6.5/10.