I’ll write down my engineering goals and policies for 2018.
Since becoming a development team leader around last fall, and from this year also taking on the role of PM (Project Manager), I’ve set my goals and policies mainly from that perspective.
I’m aiming to recruit at least 2 engineers. So I want to find effective patterns for engineer recruitment as soon as possible.
This is my first time committing seriously to recruitment, so I want to approach it from all directions.
The post I wrote recently, “Started Tech Podcast for Engineer Recruitment Purposes”, is exactly part of that effort as the title suggests.
Starting this year, I’ll also be doing technical consulting for other companies.
I want to deliver results so that clients can feel satisfied and think “It was great to ask for technical consulting.”
I want to focus on determining project priorities from a business perspective.
Since my background is engineering and I still write code and do code reviews, I tend to think about things with an engineering mindset.
My strategy is to lean more toward the business side in management to achieve a good balance between business and engineering - I think this will result in just the right balance.
I didn’t focus heavily on infrastructure management at work last year, so I probably won’t concentrate on that this year either.
However, I’m interested in it, so I plan to work with AWS freely in private projects.
Last year I wrote frontend code using Vue.js at work.
However, since we now have a strong team of frontend engineers, I’ve decided not to focus on it and leave it to the professional team.
I’m still writing code with React.js/Redux in private projects, so I plan to continue coding frontend at my own pace as I like.
That’s all from the Gemba regarding an engineer’s goals and policies for this year.