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

I don't expect my architect to know the ins and outs of Go, I expect them to have a strategy that is forward thinking a few years out. Plans on cloud integration, ci/CD requirements, updating legacy systems to be containerized, managing kube clusters, etc. They should know the pros and cons related. They don't need to write a for loop.

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