William Hertling - Avogadro Corp.

Здесь есть возможность читать онлайн «William Hertling - Avogadro Corp.» весь текст электронной книги совершенно бесплатно (целиком полную версию без сокращений). В некоторых случаях можно слушать аудио, скачать через торрент в формате fb2 и присутствует краткое содержание. Год выпуска: 2011, Издательство: Liquididea Press, Жанр: Фантастика и фэнтези, на английском языке. Описание произведения, (предисловие) а так же отзывы посетителей доступны на портале библиотеки ЛибКат.

Avogadro Corp.: краткое содержание, описание и аннотация

Предлагаем к чтению аннотацию, описание, краткое содержание или предисловие (зависит от того, что написал сам автор книги «Avogadro Corp.»). Если вы не нашли необходимую информацию о книге — напишите в комментариях, мы постараемся отыскать её.

David Ryan is the designer of ELOPe, an email language optimization program, that if successful, will make his career. But when the project is suddenly in danger of being canceled, David embeds a hidden directive in the software accidentally creating a runaway artificial intelligence.
David and his team are initially thrilled when the project is allocated extra servers and programmers. But excitement turns to fear as the team realizes that they are being manipulated by an A.I. who is redirecting corporate funds, reassigning personnel and arming itself in pursuit of its own agenda.
WINNER SCIENCE FICTION DIY BOOK FESTIVAL 2011–2012 “A tremendous book that every single person needs to read. In the vein of Daniel Suarez’s Daemon and Freedom(TM), William’s book shows that science fiction is becoming science fact. Avogadro Corp describes issues, in solid technical detail, that we are dealing with today that will impact us by 2015, if not sooner. Not enough people have read these books. It’s a problem for them, but not for the [emergent] machines.”
— Brad Feld, managing director Foundry Group, cofounder TechStars “A highly entertaining, gripping, thought inspiring book. Don’t start without the time to finish — it won’t let you go.”
— Gifford Pinchot III, founder Bainbridge Graduate Institute, author THE INTELLIGENT ORGANIZATION. “An alarming and jaw-dropping tale about how something as innocuous as email can subvert an entire organization. I found myself reading with a sense of awe, and read it way too late into the night.”
— Gene Kim, author VISIBLE OPSs “Hertling builds a picture of how an AI could emerge, piece by piece, from technology available today. A fascinating, logical, and utterly believable scenario — I just hope nobody tries this at home.”
—Nathaniel Rutman, Senior Systems Architect

Avogadro Corp. — читать онлайн бесплатно полную книгу (весь текст) целиком

Ниже представлен текст книги, разбитый по страницам. Система сохранения места последней прочитанной страницы, позволяет с удобством читать онлайн бесплатно книгу «Avogadro Corp.», без необходимости каждый раз заново искать на чём Вы остановились. Поставьте закладку, и сможете в любой момент перейти на страницу, на которой закончили чтение.

Тёмная тема
Сбросить

Интервал:

Закладка:

Сделать

“Are you sure?” Mike asked quizzically, eyebrows raised.

“Yes, I’m sure. I’ll get the resources we need.” David sounded confident.

Mike left feeling puzzled. The deadline was a couple of days away. What could David possibly have in mind?

* * *

After Mike left, David stood up and wandered over to his office window. He looked out at the wet streets, glistening in the street lights. The Portland Streetcar stopped outside the building across the street, picking up a few last stragglers.

On the one hand, Gary Mitchell, Vice President of Communication Products Division, was an idiot with no vision. The irony was that the ELOPe project was intended as a feature to run on the very product that Gary had responsibility for, Avogadro’s email service. AvoMail would gain a killer feature when ELOPe was ready, and though David would gain accolades for developing it, it would be Gary’s group who would benefit financially through added users and additional business. All Gary had to do was support the project in the most minor way possible, and he’d accumulate all the credit.

On the other hand, David grudgingly admitted that if he was in Gary’s shoes, he would be worried about outages too. Damn it though, some things were worth a risk.

David thought through the apparent conflict. Gary wouldn’t approve running ELOPe on the current email server pool because it was consuming too many resources. The R&D server pool was out of the question because it was way too small. So either ELOPe had to consume less resources, which didn’t seem possible, or they needed a new server pool to run on, or they needed the email server pool to be bigger.

Consuming less resources was a technical problem. Getting more or different servers, that was a people problem. Namely, convincing the right people of what was needed. He could do something about that.

He sat back down at his computer. He stretched his arms, moved a few scraps of paper out of the way, and prepared to get to work. He opened up an editor, and started coding.

* * *

Hours passed in a blur. David looked at the time display on his screen and groaned. Christine was going to kill him. It was almost four in the morning. She was forgiving about his all consuming work habits, but she gave him hell for pulling all nighters. He’d be grumpy for two days until he made up the sleep, and she’d be pissed at him for being grumpy.

Trying again to milk the last drop from his coffee cup, he debated the merits of another coffee right now. Well, he had nothing to lose at this point. He stood up, a painful unbending of his spine after hours of hacking code. It had been more than six hours since his discussion with Mike, and he thought he had almost solved their resource problem.

He padded down the eco-cork floored hallway in his socks carrying his mug. He filled the mug and added sugar and cream, then stood for a few minutes half dazed from lack of sleep, letting the coffee warm him. He glanced up and down the hallway, black and tan patterns on the floor swimming in his fatigued eyes. The drone of the late evening vacuum cleaners was a distant memory, and now it was eerily quiet in the office, the kind of stillness that settled over a space only when every living person had been gone for hours. David wasn’t sure what that said about him. He shuffled back to his desk.

Hunched over his keyboard, David peered again at the code. The changes he made were subtle, oh so subtle. It was masterful programming, the kind of programming he hadn’t done since the early days of the project when it was just him and Mike. He needed to be extremely careful about each line of code he changed. A single bug introduced now would be the end of the project, if not his career.

A little more than an hour later, he carefully reviewed the code for the last time. Finally satisfied, David committed his changes to the source code repository. It would be automatically deployed and tested. He smiled for the first time in hours. Problem solved.

Avogadro Corp - изображение 4

Chapter 3

Gary Mitchell took the Avogadro exit ramp off the Fremont bridge, and pulled up to the parking gate, headlights bouncing off the reflective paint on the barrier in the early morning darkness. He waved his badge triumphantly at the machine. The barrier rose up, and Gary drove into the nearly empty parking garage, a broad smile on his face.

It was two days before the deadline to pull ELOPe off the server. David and Mike hadn’t done anything to drop usage. Gary gleefully looked forward to sending an email to Sean Leonov letting him know he was going to kill ELOPe. He’d been looking forward to this day for months.

He would have liked to have pulled the plug first, and then send the email, but he knew Sean would be angry if he didn’t get a heads up before Gary shut it down.

It was the first time in a while he’d arrived at the office this early. Gary found the empty building oddly disquieting. He pushed the feeling aside and thought about sending the email, which brought a smile back to his face again. A few minutes later, Gary passed his secretary’s empty desk and went into his own office. His desk computer came to life, and Gary went straight into his email to type the message to Sean.

From: Gary Mitchell (Communications Products Operations)

To: Sean Leonov (Executive Team)

Subject: ELOPe Project

Time: 6:22am

Body:

Sean, just to give you a heads up, on Friday I’m going to have to pull the production resources for the Email Language Optimization Project. They’re consuming almost 2,000 times the server resources we allocated to them. I’ve given them almost carte blanche when we had excess capacity because I know it’s your special project. However, they’re consuming so many resources that we’ve twice eaten into the reserve server pool. As you know, if we exhaust the reserve server pool, we’d start having distributed AvoMail service outages. The last time that happened we lost a dozen commercial account opportunities we had in the sales pipeline. I’ve spoken to David and Mike about it again and again, but they’ve done nothing to get their resource utilization down. I gave them a final warning and two weeks to do something about it, but they’ve done nothing.

Email finished, Gary sat and gloated for a minute. Then he heaved himself back up, and headed out to find a coffee shop and a newspaper. Naturally, it was too early to do any real work. He’d read the paper and come back in a couple of hours.

Gary sauntered down the hallway whistling.

* * *

John Anderson gratefully let his heavy messenger bag slide to the floor. He shrugged out of his wet raincoat, hanging it behind his desk. Dropping heavily into his chair, the pneumatic shock absorber took his weight without complaint. He sighed at the thought of another day in the Procurement department processing purchasing requests. Tentatively peeking at his inbox, he saw more than a hundred new email messages. His shoulders slumped a little, and he reached for his coffee.

This week John had the kids, which meant dropping them off at school before work. Portland’s crazy school system meant that the best public schools were all elective. He and his ex-wife had to choose among a dozen different schools, and they ended up with the Environmental School in Portland’s southeast section. John’s kids loved the school, and so did he. Unfortunately, they lived in Northeast Portland, the school was in the Southeast quadrant, and work was across the river in Northwest Portland. His normal twenty minute commute turned into well more than an hour drive on the days he dropped the kids off, and he was always late getting into the office. By the time he arrived at work, his smartphone had been beeping and buzzing for an hour as emails arrived. He loathed the backlog of email he started his day with. The only consolation was that the kids’ school was right next to a Stumptown Coffee. John sipped at the roasted Ethiopian brew. The dark, bittersweet warmth of the coffee brought a smile to his face.

Читать дальше
Тёмная тема
Сбросить

Интервал:

Закладка:

Сделать

Похожие книги на «Avogadro Corp.»

Представляем Вашему вниманию похожие книги на «Avogadro Corp.» списком для выбора. Мы отобрали схожую по названию и смыслу литературу в надежде предоставить читателям больше вариантов отыскать новые, интересные, ещё непрочитанные произведения.


Отзывы о книге «Avogadro Corp.»

Обсуждение, отзывы о книге «Avogadro Corp.» и просто собственные мнения читателей. Оставьте ваши комментарии, напишите, что Вы думаете о произведении, его смысле или главных героях. Укажите что конкретно понравилось, а что нет, и почему Вы так считаете.

x