The Cross-time Engineer

The Cross-time Engineer
Author :
Publisher : Del Rey
Total Pages : 259
Release :
ISBN-10 : 0345327624
ISBN-13 : 9780345327628
Rating : 4/5 (24 Downloads)

Book Synopsis The Cross-time Engineer by : Leo Frankowski

Download or read book The Cross-time Engineer written by Leo Frankowski and published by Del Rey. This book was released on 1986-01-01 with total page 259 pages. Available in PDF, EPUB and Kindle. Book excerpt: Accidentally plunged back in time to Poland in the year 1231, Conrad Schwartz is determined to build up the country before the Mongol invasion that will come ten years later


The Cross-time Engineer Related Books

The Cross-time Engineer
Language: en
Pages: 259
Authors: Leo Frankowski
Categories: Fiction
Type: BOOK - Published: 1986-01-01 - Publisher: Del Rey

DOWNLOAD EBOOK

Accidentally plunged back in time to Poland in the year 1231, Conrad Schwartz is determined to build up the country before the Mongol invasion that will come te
The Cross-Time Engineer
Language: en
Pages:
Authors: Leo A. Frankowski
Categories:
Type: BOOK - Published: 1998-12-01 - Publisher: Del Rey

DOWNLOAD EBOOK

Ellie, Engineer
Language: en
Pages: 119
Authors: Jackson Pearce
Categories: Juvenile Fiction
Type: BOOK - Published: 2018-01-16 - Publisher: Bloomsbury Publishing USA

DOWNLOAD EBOOK

"Look out, Junie B. Jones! Ellie the engineer is thinking, making, creating, and showing enthusiasm and brilliance with her creations!" -School Library Connecti
Knife Engineering
Language: en
Pages: 282
Authors: Larrin Thomas
Categories:
Type: BOOK - Published: 2020-07-16 - Publisher:

DOWNLOAD EBOOK

An in-depth exploration of the effects of different steels, heat treatments, and edge geometries on knife performance. This book provides ratings for toughness,
Site Reliability Engineering
Language: en
Pages: 552
Authors: Niall Richard Murphy
Categories:
Type: BOOK - Published: 2016-03-23 - Publisher: "O'Reilly Media, Inc."

DOWNLOAD EBOOK

The overwhelming majority of a software system’s lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that softw