122 karma · joined June 7, 2019
In short rigidity on the part of individuals combined with countervailing organizational goals to combatting same is the issue.
Ok: the rest of the article was great. Thanks
One more is all we're asking for.
But alas this piece is a bunch of cheap symbolism.
Op whatever is on your mind, spit it out and stop the bs.
This article is a rant. Not an engineering take down of go. There's just not much of substance here. Were I to care about windows (I don't) for serious cross platform os interaction, go isn't your hammer of choice.
I've turned to go recently for some I/O heavy apps of a micro-service type which it is fine for. I also turned to go because of God awful c++ build times and bad build systems in the sense that they assume all code is in a single branch. By switching to go I also prevent less experienced programmers from linking in legacy c++ libraries and the evil that comes with them.
Go has delivered. My needs are such that protobuf/flatbuffer are good enough for types and go's lack of generics is irrelevant. I'm pushing bytes across a network pipe in which each message admits simple transforms/operations.
Now I am keeping my eye on three things that I think go could burn me on:
- garbage collection
- channels ... cool but slow
- something unixy/multicore/close to the bare metal ... Like kv store
Those things I'd be reticent about doing in go.
Folks, we need 2-4 languages with their connections to libraries and tool chains in our toolbox.
While we remain dominated by c++ (a complex beast of a language) I am looking to add a functional language to my kit (ocaml/Haskell). Btw good engineers need a formal language too. I recommend tla+ and there's a guy in hacker news here that's got good books on it. Recommended! Highly concurrent code ought to modeled in tla+ first before leaving your app language gun and taking the canolli.
Cheers
L. Pachter and B. Sturmfels. Algebraic Statistics for Computational Biology. Cambridge University Press 2005.
G. Pistone, E. Riccomango, H. P. Wynn. Algebraic Statistics. CRC Press, 2001. Drton, Mathias, Sturmfels, Bernd, Sullivant, Seth. Lectures on Algebraic Statistics, Springer 2009.
Or more like:
Watanabe, Sumio. Algebraic Geometry and Statistical Learning Theory, Cambridge University Press 2009.
My understanding (I do not do AI or machine learning) that AI is distinct from these more mathematical analytic perspectives.
Finally, might we argue that generally AI/ML is more easily suited to data that's already high quality eg. CERN data, trade data, drug trial data as opposed to unconstrained data eg. Find the buses in these 1MM jpegs?
Among the major arguments,
* The single biggest obstacle to good teamwork (well defined therein) is rigidity on the part of individuals
* Rigid individuals are unchanging because the person's self esteem is threatened. Teams are busted by individuals who don't change behavior.
* And ultimately the biggest problem in the long run for human organizations is lack of openness.
* The book explains why this is so.
The background and impetus for this work (Schutz was Harvard trained) came out of WWII Navy experience dealing with battle conditions. The Navy realized a major impediment to better performing battle execution was that the bridge officers could resolve conflict well. It's not that conflict exists; this is intrinsic to any open ended, unconstrained problems in an evolving environment.
To respond the Navy post war completely revamped training. They chose physically fitter officers, smarter, and trained them harder. The results however under test exercises were random: sometimes teams worked and sometimes they didn't. The Navy couldn't predict when or why.
Schutz was asked to consult on this problem and through this work and in corporations subsequently this work was born.
If you work in an environment where office BS reins, and where management of teams really amounts to people tinkering with a Markov like hidden variable random process until something works, this book is for you.
- ask for task heartbeat
- make sure nodes in cluster pingable
- run N copies of task on reachable hosts
That's it.
Meanwhile, a university professor,
- isn't mom/dad by pseudo punishing students removing phones
- isn't moonlighting as pseudo pysch researcher who guessed phones were the problem
- isn't a cool guru by wowing kids into wisdom with this unexpected ploy
If your students did bad on their exam
- make improvements as a teacher if you feel some responsibility lay with you (there's no need to gas on about this to students)
- leave the grades unchanged
- stop confusing the issue with stupid exercises then self marketing it into media