I suspect I'm going to learn a lot about what not to do through this experience. Really, I just wanted to know if golang's concurrency features could be used to make search faster in this vaguely defined scenario and maybe if it makes sense to. The latter part of the question will be determined months down the road I suspect.
On Tuesday, March 27, 2018 at 3:16:12 PM UTC-7, Drew Derbyshire wrote: > > As Andre noted, I don't think you have provided sufficient information. > > I'd go further: *Stop*, Determine what you (and your developer) need to > know. > > Decide what you want, and write a specification. If you have to ask > "specification for what", make a list what you don't know. Does the > specification need to be long? No, but it has to define your problem(s) > and solution(s). > > You can do the specification writing or the contractor can -- but if you > have questions after reading it, get them written down and answered in the > specification. You are just asking for trouble to ask a remote developer > (across town or across the sea) to write a complex application backend if > you don't understand what you asking for. > > -ahd- > -- 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.
