Not the person you were replying to, but... I don't use SO much, either. My professional work (presently) consists of two things: 1. Writing web services (ca

Not the person you were replying to, but... I don't use SO much, either. My professional work (presently) consists of two things: 1. Writing web services (can't go into much more detail) 2. Developing (what will soon be released as) an open source framework for service orchestration (also can't go into much more detail) This is all written in Go. Technologies used: MongoDB, Kafka, gRPC, REST/HTTP I'm familiar enough with the semantics/specification of the above tech, so most of the unknowns boil down to (occasional) lack of familiarity with the libs used. In that case, I'll occasionally read the documentation; more often I'll read the generated godocs; and most often I'll just grep/peruse through the code for a couple minutes, and then I'm set for the next couple weeks. Granted, I have used SO more in the past. In those cases, it was because of stuff like futzing around with Grunt/Gulp in a JS project, or dealing with APIs trying to be too cute via metaprogramming (Ruby, I'm looking at you), etc. It calls to mind a quote[1] that resonates quite well with me: "One reason people's skills plateau is because they try to master simplifying extrinsic complexity, and not intrinsic complexity." [1]: https://twitter.com/shajra/status/746334265051226119 https://twitter.com/shajra/status/746334265051226119