Professional Documents
Culture Documents
Ingles III
Ingeniería de Sistemas
Word Order
Docente: Alumno:
“Even the printing press, even the printing press was assumed to be a tool that was
going to enforce Catholic intellectual hegemony across Europe. Instead, what we got
was Martin Luther's 95 Theses, the Protestant Reformation, and, you know, the Thirty
Years' War. All right, so what all of these predictions of world peace got right is that
when a lot of new ideas suddenly come into circulation, it changes society. What they
got exactly wrong was what happens next. The more ideas there are in circulation, the
more ideas there are for any individual to disagree with. More media always means
more arguing. That's what happens when the media's space expands. And yet, when
we look back on the printing press in the early years, we like what happened. We are
a pro-printing press society. So how do we square those two things, that it leads to
more arguing, but we think it was good? And the answer, I think, can be found in things
like this. This is the cover of "Philosophical Transactions," the first scientific journal ever
published in English in the middle of the 1600s, and it was created by a group of
people who had been calling themselves "The Invisible College," a group of natural
philosophers who only later would call themselves scientists, and they wanted to
improve the way natural philosophers argued with each other, and they needed to do
two things for this. They needed openness. They needed to create a norm which said,
when you do an experiment, you have to publish not just your claims, but how you did the
experiment. If you don't tell us how you did it, we won't trust you. But the other thing they needed
was speed. They had to quickly synchronize what other natural philosophers knew.
Otherwise, you couldn't get the right kind of argument going. The printing press was clearly the
right medium for this, but the book was the wrong tool. It was too slow. And so they invented
the scientific journal as a way of synchronizing the argument across the community of natural
scientists. The scientific revolution wasn't created by the printing press. It was created by
scientists, but it couldn't have been created if they didn't have a printing press as a tool.”
“So I study social media, which means, to a first approximation, I watch people
argue. And if I had to pick a group that I think is our Invisible College, is our generation's
collection of people trying to take these tools and to press it into service, not for more
arguments, but for better arguments, I'd pick the open-source
programmers. Programming is a three-way relationship between a programmer,
some source code, and the computer it's meant to run on, but computers are such
famously inflexible interpreters of instructions that it's extraordinarily difficult to write out
a set of instructions that the computer knows how to execute, and that's if one person
is writing it. Once you get more than one person writing it, it's very easy for any two
programmers to overwrite each other's work if they're working on the same file, or to
send incompatible instructions that simply causes the computer to choke, and this
problem grows larger the more programmers are involved. To a first approximation,
the problem of managing a large software project is the problem of keeping this social
chaos at bay. Now, for decades there has been a canonical solution to this problem,
which is to use something called a "version control system," and a version control
system does what is says on the tin. It provides a canonical copy of the software on a
server somewhere. The only programmers who can change it are people who've
specifically been given permission to access it, and they're only allowed to access the
sub-section of it that they have permission to change. And when people draw
diagrams of version control systems, the diagrams always look something like this. All
right. They look like org charts. And you don't have to squint very hard to see the
political ramifications of a system like this. This is feudalism: one owner, many
workers.”
“Now, that's fine for the commercial software industry. It really is Microsoft's Office. It's
Adobe's Photoshop. The corporation owns the software. The programmers come and
go. But there was one programmer who decided that this wasn't the way to work. This
is Linus Torvalds. Torvalds is the most famous open-source programmer, created
Linux, obviously, and Torvalds looked at the way the open-source movement had
been dealing with this problem. Open-source software, the core promise of the open-
source license, is that everybody should have access to all the source code all the
time, but of course, this creates the very threat of chaos you have to forestall in order
to get anything working. So most open-source projects just held their noses and
adopted the feudal management systems. But Torvalds said, "No, I'm not going to do
that." His point of view on this was very clear. When you adopt a tool, you also
adopt the management philosophy embedded in that tool, and he wasn't going to
adopt anything that didn't work the way the Linux community worked. And to give you
a sense of how enormous a decision like this was, this is a map of the internal
dependencies within Linux, within the Linux operating system, which sub-parts of the
program rely on which other sub-parts to get going. This is a tremendously
complicated process. This is a tremendously complicated program, and yet, for years,
Torvalds ran this not with automated tools but out of his email box. People would
literally mail him changes that they'd agreed on, and he would merge them by hand.
And then, 15 years after looking at Linux and figuring out how the community worked,
he said, "I think I know how to write a version control system for free people.And he
called it "Git." Git is distributed version control. It has two big differences with traditional
version control systems. The first is that it lives up to the philosophical promise of open-
source. Everybody who works on a project has access to all of the source code all of
the time. And when people draw diagrams of Git workflow, they use drawings that look
like this. And you don't have to understand what the circles and boxes and arrows
mean to see that this is a far more complicated way of working than is supported by
ordinary version control systems.”
Link:
https://www.ted.com/talks/jeff_bezos_the_electricity_metaphor_for_the_web_s_future/tr
anscript?subtitle=es
Sentences