Hacker News new | past | comments | ask | show | jobs | submit login

Yours is an interesting situation. I would suggest the following:

1) Read code and spend an hour a week keeping up with developments in your immediate field. Understand the most used frameworks, learn how they work, what each one's pros and cons are, the lingo, the discussions.

2) Understand what your manager cares about and what he wants from you. Ask him what would be a success and what would be a failure.

3) Make sure you understand and implement best practices. Do you have a golden set? Tests? Monitoring - Do you know how much data runs through your pipeline, what your error rate is? What wakes you up when the pipeline fails in the middle of the night? Who needs to be notified, what are the downstream effects?

4) After you have a couple of projects under your belt - that may already be the case if you've been there for a while - consider hiring an experienced contractor for a week to review your code and architecture. You said you're responsible for hiring, I'm guessing you have a budget for subcontracting. Like with all contracts, make sure you have well-defined scope for what you're asking for.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: