Prolog was the language to be associated with, if you were on the 1980s AI bandwagon (and the Japanese were going to take over the world unless we did something about it, e.g., spend money); this time around, it’s machine learning.

It could be argued that computers have been instrumentalized as assault weapons in a series of philosophical crusades against hermeneutics, from Bense to Moretti as well as in the media theory of Friedrich Kittler. [...] By this virtue of failure, computer science for the first time makes it possible to state more precisely the limits of formal analysis and the necessities of hermeneutic interpretation, as opposed to vague or stereotyped romanticist criteria for assessing the literary or poetic quality of a text.

[N]ewer research shows that stylometry can also apply to artificial language samples, like code. Software developers, it turns out, leave behind a fingerprint as well.

Rachel Greenstadt, an associate professor of computer science at Drexel University, and Aylin Caliskan, Greenstadt's former PhD student and now an assistant professor at George Washington University, have found that code, like other forms of stylistic expression, are not anonymous.

[T]he world of programming languages could be stabilizing a bit after a decade of change.

“The Amazon recruiter on the other end responded with apparent astonishment: ‘Wow I honestly had no idea’.”

Unfortunately, this anti-pattern has been followed by many organisations in an attempt to increase efficiency.

This highly stimulating book is in the first place a new and innovative take on the well-known two cultures debate. Yet rather than stressing the added value of bridging the gap between the two major strands – arts and sciences, alpha and beta – that came out from Western modernization and secularization since the Renaissance, Lennon argues that in some cases – that of philology, the humanist study of language, and that of cryptology, the mathematical and technical science of codes and ciphers –, the two cultures gap is much smaller than we often think.

DevOps is one the offshoots of software abstraction, where this time it was not the hardware, processes or any code complexities that were abstracted — but a way to abstract the IT personnel out (the “Ops” part).

"We may wonder, then, whether the mutations under way in the information economy do not resemble identifiable trends in US private universities, again with the prospect of a turn towards social oligarchy"

The flow of developers starting out with R will slow down, casual R users will have nothing to lose from trying out another language when the right project comes along (another language on the CV looks good and Python is a bigger market). There will be groups where everybody uses R and will continue to use R because that is what everybody else in the group uses. Ten-Twenty years from now R, developers could be working in a ghost town.

“...one staffer told me that their jobs used to be about wrangling cat videos and now they had degenerated into a daily hell of ethics debates about the fate of humanity.”

I occasionally worry that talk of the "humanities crisis" could be a self-fulfilling prophecy. Fortunately or unfortunately, though, the shift seems to have more to do with content than with labels. The social science fields that most closely resemble humanistic ones--sociology, anthropology, international relations, and political science--have also seen serious drops. [...] The big winners in recent years have been health professions, including nursing; computer science and engineering; biological science and to a lesser degree, physical sciences; and what I oddly call "leisure," which includes things like sports management and exercise studies.

Computational capital is thus also racial capitalism, the longue durée digitization of racialization and, not in any way incidentally, of regimes of gender and sexuality.

Over the last few decades the tech industry has built systems so fundamentally insecure, so rotten to their core, that we now have no real choice but to trust its largest and most powerful companies to protect us. I’m all too aware of the grim irony.

On "three interrelated challenges to the post-World War II information order: twenty years of digital technological disruption, the 2008 economic crisis, and politically and economically motivated challenges to the industrial news media."

"The cosy relationship between industry and academia—including the corporate takeover of entire university laboratories, as with Uber and Carnegie Mellon—is seldom viewed with the same scrutiny as, say, the pharmaceutical industry’s interference in medical research."

"Mr. Stamos also said Information Warfare was a new working group at Stanford with about 14 faculty members across academic disciplines."

"In example after example, the toxic combination of filter bubbles, simplistic ranking mechanisms and algorithmic recommendation is seen as clearly in elite networks as in more accessible but supposedly less self-aware groups – but, we are told, the effects really aren’t as bad as we’re being told they are"

Those who can’t be bribed are blackmailed. Thus it is no longer just that the myth of the machine is based on the idea that the megamachine is “absolutely irresistible” and “ultimately beneficial” but that it now includes the idea that to push back is “unforgivably detrimental.”

"I definitely feel like this was a silly chapter in my life. I’m very glad I got to pay off my student loans. But I don’t feel good about the work. In fact I feel pretty embarrassed about it."

"The maker movement is one prominent translation of Digital Proudhonism into a challenge to the contemporary organization of production, with allegedly radical effects on politics and economics."

With the recent growth and popularity of DevOps in industry, practitioner outlets, and publications within the areas of computer science and software engineering, the aim of this paper is to address the question, "Is Information Systems late to the party?" In hopes of shedding light on this question, the authors conducted a thorough and systematic review of the publications contained in the Association for Information Systems eLibrary to examine the current state of DevOps research within the area of Information Systems. By following guidelines established for conducting reviews of literature in Information Systems, the authors identified 42 papers containing the keyword DevOps or Devops. Further analysis of each paper revealed only six papers that directly addressed the topic of DevOps. The authors conclude that Information Systems needs to fully "join the party" and that DevOps represents a fertile ground for increased Information Systems research.

"In its most-developed markets, Facebook is simply running out of people: there are not enough Americans or Europeans alive for the company to double in size again. And on a global scale, Facebook is just as limited by access to the net itself."

“Is there, was there, will there be, a digital turn?”

Tech has a fractal irresponsibility problem: Each small worry reflects in miniature the shape of the industry’s big problems.

The Royal Public Health Society is behind Scroll Free September, which is targeting users of Facebook, Instagram, Twitter and Snapchat.

It believes logging off could improve sleep, relationships and wellbeing.

NHS England said it was right to highlight social media's role in a rise in young people's mental health issues.

It owes that resilience in part thanks to social media burnout. Stankov says search traffic to Inoreader has nearly doubled since 2015, all organically. "RSS readers have not only survived in the era of social media, but are driving more and more attention back to themselves, as people are realizing the pitfalls" of relying too much on Facebook and others, Stankov says.

Things are going unexpectedly wrong. I lean toward this explanation, with sprinkles of the first three. I tend to believe Facebook was caught off guard because of the simultaneous deterioration of user growth, particularly in the U.S. and Canada, which generate most of its revenue; in its revenue growth rate and expectations for a further slowdown; and in its profit-margin forecast.

It had become an article of investor faith on Wall Street and in Silicon Valley: Quarter after quarter, year after year, the world’s biggest technology companies would keep raking in new users and ever-higher revenue. And with that, their share prices would continue to march upward, sloughing off any stumbles.

This week, that myth was shattered.

The ice of AI’s first winter only fully retreated at the beginning of this decade after a new generation of researchers started publishing papers about successful applications of a technique called “deep learning”.

While this was fundamentally a decades-old statistical technique similar to Rosenblatt’s perceptron, increases in computational power and availability of huge data sets meant that deep learning was becoming practical for tasks such as speech recognition, image recognition and language translation. As reports of deep learning’s “unreasonable effectiveness” circulated among researchers, enrollments at universities in machine-learning classes surged, corporations started to invest billions of dollars to find talent familiar with the newest techniques, and countless startups attempting to apply AI to transport or medicine or finance were founded.

As this resurgence got under way, AI hype in the media resumed after a long hiatus.

"They knew armed guards would be required to protect their compounds from the angry mobs. But how would they pay the guards once money was worthless?"

Because the compiler was poisoned with other source code that we didn't have. And that source code, that now existed only in the executable compiler, put those changes back into the compiler source before it compiled it. But this time it didn't modify the /usr/src copy, it copied it to a hidden directory, modified the compiler source, compiled itself from there, and deleted the hidden directory. It took an AT&T tech to find this. The ex-grad student had poisoned the compiler to poison itself when it was recompiled.

The future evolution of C++, Java and Python is being driven by very different interested parties, and it’s going to be interesting watching events unfold over the next 5-10 years.

Not all IT leaders like the term DevOps: Some prefer to just call it the agile way of working. But however you describe it, this style of working – which prizes speed, experimentation, and collaboration, all happening on nimble, cross-functional teams – has taken the enterprise by storm. It has demanded new IT leadership strategies. Above all, it has demanded culture change, as teams ditch old processes, rip down rules between groups, and accept “failures” as quick lessons on how to iterate their way to better products and services.

Ruby has seen the steepest decline in this timeframe, going from the 2nd most popular language in 2011 with over 18% of users to the 11th most popular today with 3.2% of users [...] Ruby has more than 3x the number of active users using the language than in 2011. It just hasn't grown nearly as fast as other languages.