It's clear now that my role at my new job involves guiding process and determining how the team should optimally build things (as the title "architect" would imply). In my initial thought process about how this will go, I find myself asking interesting questions.
First and foremost, I have to think about efficiency and value. That's something that they used to really beat into us at my last gig, and it's a good thing to think about. You have to get things done and deliver stuff, and solve today's problems. That's not to say that you can't account for the future, but you can't account for it at the expense of delivering value. That's an interesting line to walk.
It also means I get to explore and evaluate technology. That's something I've always done, but mostly out of my own curiosity, not for work. If I'm not doing a lot of hands-on coding, and I doubt I will as the company grows, that leaves time for a lot of experimentation and critical thinking about how new stuff rolls into real life.
Again, I'm cautiously optimistic about this job. It's a lot of responsibility, but in a good way.
No comments yet.