Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Since we just work with mostly simple CRUD, there isn't many downsides. Also we use SQL queries for most of our logic, so SQL knowledge is the real barrier

I usually ask them to read gobyexample.com, but they can start working on projects on the first day.

CRUD project with Go makes it easy to add new endpoints and simple features, so we can focus on hiring frontend devs and smoothly turning them into "fullstack CRUD devs"

I am sure this can be achieved with other languages, but for our use case (software-house) Go just fits really well because it provides a low cognitive overhead for juniors and even interns to make sense of the project and contribute

It fits pretty nicely in an "assembly line" style development, but maybe the downside is that it is boring and makes devs want to leave because they feel like they're always hitting the mark and "mastered" development and want to climb to the next level. It seems reasonable for them, but the turnover is tiresome (around 6 months) for me



Thanks - interesting perspective.

I do think that we (or me!) hold ourselves to too high a standard in terms of mastering all aspects of a language, especially given some languages have got too big. It's refreshing to hear an approach that focuses on knowing just enough to get the job done!




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

Search: