2,750 karma · joined February 2, 2011
I almost think this was a deliberate choice. Makes the services sound more important than what they are. At any rate, many engineers I know love to smugly use this acronym soup.
I.e. a link to "synthesizers" on a page about FM synthesis could lead to a generic article on synthesizers, or to a list of FM synthesizers released up to date.
And that's just the most obvious example. Having different "linking contexts" would allow to add more links without turning the original document into a mess.
Again, using Wikipedia as an example, you could add another "context" to the page by linking various paragraphs to citations. That would be much more user-friendly than what they do right now with bracketed numbers.
We had 20 years of doubling of computing power before Lee Sedol match. In those 20 years there were many other AI programs that have beaten various world champions at other board games (and no one cared). There were other good Go engines before Alpha Go. They would beat most human players in the world.
Why AlphaGo of all other programs is seen not as increment, but as some giant leap forward? It doesn't solve a new class of problems and it doesn't use any fundamentally new algorithms.
In 2016 Google made a system that was better at any person at playing Go. Go has roughly 130,000 moves possible at any point. That's approximately equal to 400 * 2^9.
Moore's law states that the number of transistors (which is a proxy for computing power) in CPUs doubles every year. 2016 - 1996 = 20 years of computing power growth.
In short, after our computing power has increased roughly by a factor of 2 ^ 20 someone made a system that plays a game that's 2 ^ 9 time more complicated than chess. Why is this seen as some giant, surprising leap forward?
The guy the article about says as much.
“I’ve stopped giving general advice to other researchers,” said Dickmanns, now 82 years old. “Only this much: One should never completely lose sight of approaches that were once very successful.”
I really feel for those researchers. Seeing how your life's work is ignored by people who brute-force their ways through the problems you've already solved must be rather depressing.
People wouldn't waste time researching neural network visualization tools, coming up with adversarial examples and developing alternative (more explainable) machine learning models if that was the case.
F = G (m1 * m2) / r^2
Newton's theory of gravitation identified the relevant variables and their relationships. It had no junk variables or parameters. You can do algebraic transformations on it and use the formula outside of the original context. It was not fully correct, but it made exact predictions. People were able to notice the discrepancies it had with orbits of some celestial bodies, which helped in identifying general theory of relativity.
All of this would have been lost of the formula was a state vector of a large neural network.
Let's say someone used a neural network to predict planetary positions as a function of time, mass and so on. They made a network with several hundred parameters, trained until it stopped converging and published their final state vector.
Would that ever lead to gravitational theory?
How does this invalidate the notion of interpretability?
A model can be both wrong/misapplied and fully interpretable.
Are there any applications/websites where this can be seen in action? It's increasingly hard to judge how good state-of-the-art really is from research papers.
I've worked on moderately interesting problems in some positions, and I've also worked in positions where everyone with experience was sucked into fixing infinite streams of fuck-ups from junior developers and contractors, who end up doing all the actual development.
IMO, it mostly boils down to control. If you have control and you are knowledgeable, you can solve "boring" problems in interesting and fulfilling ways. If you don't have control over how you do your job, programming can quickly turn into glorified data entry.
This isn't about behavior. This is about product management. As a reminder, Microsoft's current products include TFS (and I don't mean just TFSVC) and Teams.
Which ones? As far as I can see, it's all manual right now. Service integration is probably the largest area of IT at the moment and it sucks in more and more engineers every year. So maybe the notion of "web services" and "APIs" simply aren't the right ways to go about it.
There are wast continents of mostly unexplored or abandoned territory in IT. Moreover, some of them are well documented. Some of them were documented in 1970s. The fact that IT professionals today don't know about them and can't imagine anything more significant than "AI" for pizza ordering, is unsettling. Just to name a few things Alan Kay often talks about:
- Automated system integration or tools for generalized interconnection of applications available to end users.
- WYSIWYG for the Web.
- Constraint-based problem-solvers accessible to mere mortals.
- Agent oriented programming with UI simple enough for normal people to use.
- Dynamic simulations in "normal" software (not CADs)
I am absolutely sickened by the fact that the most common response to this list is "nobody needs this". As far as I'm concerned, each of those things is needed orders of magnitude more than a haircut-scheduling AI.
Not when you are literally writing code on it.