History of IT

Part I: From four to eight

I like to read the memoirs of people who observed the computers taking first steps in their countries. They always have something romantic about them. Usually, such memories are greatly influenced by the circumstances of that encounter with his first computer: it could be the workplace, or education establishment, it could be just an unexpected and random thing.

Like many of my friends, I was lucky to see the end of that special romantic period, when computer makers were not trying to please the regular users. They were creating the devices with distinctive and unique features they thought were right for some of reasons. This approach is clear to see in both software and hardware. Such features were making the device to sell in millions or be a commercial failure.

It all started differently for different people. Some of them were working with buzzing massive computers that could fill an entire room, the others had desktop-style home computers. There were people, who made their first computer themselves using specialist magazine publications. Different types of computers created the variety of specific traditions, interests and subcultures.

Successful startups often emphasize their grassroots aspects. In part one of this series, we talked about the origins of startup culture and the DIY attitude that is prevalent in the tech industry. However, there’s more to modern startup culture than that. Today, it is in many ways defined by the innovation infrastructure that got things started and allowed the tech space to blossom, and that is the focus of this article.

In one of our previous articles, we took you on a tour of the university’s optoelectronics lab. This time around we’ve got something more public, but no less exciting in mind: The Optics Museum.

Bandwidth warning: lots of photos below!

Cyberpunk has become an integral part of our pop culture. Everyone is familiar with at least some works in the genre and their particular flavour of dystopian technologically advanced universes. But science fiction is always evolving. In this piece, we’ll be taking a look at cyberpunk’s successors and the futures they envision — from pan-African empires to shopping culture gone amok.

Video conferencing systems, so familiar to us today, have come a long way — more than a hundred years passed from fantastic ideas inspired by belief in unstoppable technical progress to the first mass implementation of video conferencing systems. A lot of dramatic events have come along the way. The way to success wasn’t easy at all.

I decided to make an interview with one of my American friends — Rob Vugteveen. He was working as a FORTRAN programmer back in 1980s, so it's quite a unique experience.


Rob Vugteveen, Carson City, Nevada, USA

K: Hi Rob. I've heard you were working as a Fortran programmer many years ago. Is that right? How the industry was looking back then?

R: Good morning, Kirill.

In the 1980s I made my living as a FORTRAN programmer in the mining industry, primarily in the processing of exploration data and presenting it graphically. We were using VAX minicomputers from Digital Equipment Corporation. This was a time when desktop PCs were growing in popularity, and procedural languages like FORTRAN were being challenged by object-oriented languages. Also, graphics display systems were shifting away from character-cell terminals to X-window-based displays.

FORTRAN (“FORmula TRANslation”) was built for computationally intensive programs, and it did not have its own graphic libraries to display information. There were companies that sold large FORTRAN subroutine libraries to provide that capability. These were not yet designed for the growing popularity of X-window technology.

When we were forced to move from expensive VAX computers to cheaper PCs, we had to write hybrid programs using FORTRAN for computations and C++ for display. It was a bit messy at first. I left that job for something completely different (building a mining museum) and haven’t really done any programming since.

FORTRAN is still used today in scientific research for computationally intensive work, but I’m sure it’s been adapted to work with graphical display systems through external subroutines written in object-oriented code.

SXSW is a festival of culture and technology held every spring in Austin, Texas. It’s a global phenomenon, with hundreds of thousands attending the event every year and millions more following the media coverage. Even if you’ve never heard of it, you’ve certainly felt its influence on our culture.

But it wasn’t always that way.

In the late 1930s, two Stanford students, William Hewlett and David Packard, were inspired by their professor’s plea to turn the Bay Area into the national capital of high tech. Operating out of the cheapest property they could find — a garage in suburban Palo Alto, they built their first commercial product, the HP200A oscillator. Now a private museum and a California Historic Landmark, this place is a living monument, commemorating the birth of the Silicon Valley startup culture.

This event preceded the similar and widely publicized success stories of Microsoft and Apple by more than 30 years. But it nonetheless perfectly defines the startup culture as we know it today. How come?

Entrepreneurs are constantly looking for new tools and possibilities to develop their businesses and enrich their knowledge. One of the ways of doing this is visiting themed events — meeting colleagues in real life, exchanging experiences, and communicating with potential investors.

In fact, there are thousands of tech-focused events taking place annually. The important thing is to pick the best, most useful and easily accessible ones to optimize your time and expenses.

Techstars Startup Digest solves this problem by sending its subscribers an email newsletter with a curated list of relevant and reasonably priced events for entrepreneurs. Currently, Startup Digest consists of more than 700 curators, is approaching 700K subscriptions, and is available in more than 300 cities all around the world. Today, I’d like to share its history, how the founders came up with the idea, what it looked like in the initial stages, and what it’s going through right now.

This post is a continuation of the first, the second, the third, and the fourth parts of the real story of Android Robotics describing the field from the beginning up to 2019.

This post is a continuation of the first, the second, and the third parts of the real story of Android Robotics describing the field from the beginning up to 2019.

This post is a continuation of the first and the second parts of the real story of Android Robotics describing the field from the beginning up to 2019.

This post is a continuation of the first part of the real story of Android Robotics describing the field from the beginning up to 2019.

Quite a long time ago, seven years ago to be precise, i wrote a series of posts describing the state of android robotics in the world. At the time i was a high school student, with a keen interest in android robotics, who absorbed a bit of knowledge from English, Japanese, Chinese, Korean and Russian internetz and wanted to spill it somewhere.

While the posts were not too professional, and not to my standards of today, they were worthy enough to get stolen and even get translated by unapproved English Habrahabr mirrors, and to this day, appear in searches.

After those posts were written, Habrahabr got split. Removal of everyone outside of pure coding who were considered «not cake enough» to Geektimes felt like an insult and so i left the platform. Yet, the website was reunited last year, and much to a personal surprise, fairly recently an English version of Habrahabr was released.

During all these years i managed to be kicked from one university, finished another with a thick thesis on «Usage of Robotics in Disaster Conditions», lived in the Republic of Korea for half a year, and most importantly, not only expanded my knowledge of android robotics in such ways that the Robotics folder on the main hard drive is now more than 300GB in size, but also expanded the knowledge via journeying and personally meeting projects of the past and present, creating quite a decent archive on Youtube and met not only with the robots, but the engineers and scientists as well.

While i am still nowhere to be a robotics engineer, (and in the daily life i attempt to be a traditional slice-of-life artist), i feel that my tiny gigabytes of knowledge might be worthy of sharing, and today on Habr i'm publishing the real story of Android Robotics from the beginning up to 2019.

Probably, there are not so many users on Habr who have never heard about the «Internet Archive», a service that searches and stores the digital data that is important for all mankind, whether it be the Internet pages, books, videos or other type of information.

Who manages the Internet archive, when it appeared and what is its mission? Read about it in the today's «Inquiry».

Author of the original post in Russian: HotWaterMusic

The history of the world's gamedev knows quite a few curious bugs that had to be tackled by developers. In fact, judging from the story that Media Molecule's CTO Alex Evans shared on his Twitter page this past weekend, many legends are still waiting to be heard. Evans is famous for his part in a demoscene performance of late 1990s and his work on the LittleBigPlanet game series and on Rag Doll Kung Fu.

The case I am referring to in this article took place ten years ago, in 2008. While working on the first part of LittleBigPlanet — an original puzzle platform video game that was to be released exclusively for PlayStation 3 — the company's developers came across a really hard-to-catch bug.

Normally, for a game to get the green light to be released for consoles, it needs to pass a certification process, i.e. meet a set of requirements predefined by the platform owner. The certification may also include more specific requirements, such as the game running smoothly without crashing for 24 hours.

The development of LittleBigPlanet was at its last stage, with just two weeks to final deployment and distribution. Suddenly a tester from the company's QA in Japan reported that the game was consistently crashing when left overnight. Now the release was evidently out of question unless the bug was fixed.