>From my experience: Expecting somebody at 0 to become a software engineer via coursework or a book doesn’t seem reasonable to me. There’s at least a couple years of mentorship and experience required just for the baseline.
JS or Go can get you far without knowing about stack traces, processor constraints like data width, how to use issue trackers and code revision, the importance of error handling, how to write structures (like trees of functions) that are maintainable, type crafting, minimizing code copy-paste, text parsing, code formatting arguing, and other language-agnostic skills. Then there’s navigating people and deadlines. For an experienced software engineer writing code that doesn’t suck requires working on a similar project first. Ideally these projects are written by other software engineers with the specific experience. Go would be a good general purpose foundation language, probably the best, but good mentors are more important than language choices on a professional track, and multiple languages have to be learned for even just the baseline. Matt On Tuesday, January 16, 2018 at 8:20:28 AM UTC-6, Ayan George wrote: > > > > On 01/16/2018 02:10 AM, James Pettyjohn wrote: > > > > Are there tracks of knowledge to take someone from 0 to understanding > > baseline knowledge? > > > > And from there through taking them to a professional grade standard? > > > > I think "Introducing Go" is a great book for someone relatively new to > programming: > > amzn.com/1491941952 > > It is fairly short and gives a really gentle introduction to Go without > (IIRC) complaining about other languages. > > I'd probably recommend the following in order: > > * Introducing Go > * The Go Programming Language > * Concurrency in Go > > -ayan > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
