--- title: Tool book of a Nuremberg knight from 1505 | daily.dev description: A passion project is transcribing and translating every page of the Löffelholz Codex, a 1505 Nuremberg tool book that has never been fully read in 500 years.... canonical: https://daily.dev/posts/tool-book-of-a-nuremberg-knight-from-1505-te41nuxib twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Tool book of a Nuremberg knight from 1505 | daily.dev og:description: A passion project is transcribing and translating every page of the Löffelholz Codex, a 1505 Nuremberg tool book that has never been fully read in 500 years.... og:url: https://daily.dev/posts/tool-book-of-a-nuremberg-knight-from-1505-te41nuxib og:image: https://api.daily.dev/og/posts/te41nuXib.png og:image:alt: Tool book of a Nuremberg knight from 1505 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Tool book of a Nuremberg knight from 1505 **[Hacker News](https://daily.dev/sources/hn)** · 6 min read · 0 upvotes · 0 comments ## Summary A passion project is transcribing and translating every page of the Löffelholz Codex, a 1505 Nuremberg tool book that has never been fully read in 500 years. The 154-page manuscript, held in Kraków, shows drills, vises, a swivel chair on casters and a disassembled crossbow. 127 pages have been reviewed so far; 27 remain. Engineer Dirk Schornstein uses AI to draft transcriptions and interpretations, then manually checks and corrects them, marking uncertain readings and open questions clearly. He's recruiting readers of Early New High German and craftspeople to help verify the drawings. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What language is the Löffelholz Codex written in? It is written in Early New High German, specifically the written language used in Nuremberg around 1505, with no fixed spelling. The same word can appear spelled two different ways on a single page, a stroke over a letter can stand for an n or m, and many workshop terms do not appear in any modern dictionary. _Readers decoding historical or technical texts can track detailed breakdowns like this on daily.dev._ ### Where is the original Löffelholz Codex manuscript kept today? The original is held by the Biblioteka Jagiellońska (Jagiellonian Library) in Kraków, under the shelfmark Ms. Berol. germ. quart. 132. It has been fully digitized and can be viewed freely through the Jagiellonian Library's digital collection at jbc.bj.uj.edu.pl. _Those researching historical manuscripts can follow ongoing digitization efforts like this one on daily.dev._ ### Who was Martin Löffelholz von Kolberg and why did he write the Codex? He was a Nuremberg patrician and knight who died in 1533, serving 28 years as Pfleger (warden) of the fortress of Lichtenau. Between 1507 and 1509 he was held captive for more than a year, which may explain why shackles and locks take up a strikingly large share of his 154-page tool and machine book, begun in 1505. _People tracing the backstories behind historical engineering works can follow projects like this on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 1 discussion and 64 comments across hackernews (as of 2026-10-25). **TL;DR:** Discussion is dominated by strong pushback against the site's visible AI-generated writing and renderings, which many feel undermines trust and value despite genuine appreciation for the underlying manuscript and project idea. **Sentiment:** 15% positive · 20% mixed · 65% skeptical **The case for** - Some argue AI lets a solo hobbyist accomplish in days what would otherwise take years, making an obscure manuscript accessible at all. - A few note the author is transparent about AI use and that the high-quality source images are genuinely appreciated. - Some point out the manuscript itself and its photographs are valuable regardless of how the accompanying text was produced. **The pushback** - Many feel the prose reads as obvious, low-quality LLM output that signals a lack of genuine care or understanding. - Several argue AI-rendered interpretations of ambiguous drawings risk presenting speculative details as fact, which is especially harmful for a scholarly/historical resource. - Some say visible AI use devalues the scientific/trust value of the project since every claim now needs independent verification. - A few see it as emblematic of broader 'AI slop' crowding out more careful, human-authored work. **By community** - hackernews (heated): A large, contentious thread split between people dismissing the site as low-effort AI slop that undermines trust, and others defending the author's transparent, resourceful use of AI to complete a solo passion project. **Hottest debate:** Whether visible, heavy use of AI for drafting/rendering devalues a historically interesting passion project or is a legitimate way for one person to make an obscure manuscript accessible. **Open questions** - Is the author actually qualified to verify the Early New High German transcriptions and drawings? - How much of the site's prose versus the manuscript's content/images was AI-generated versus human-reviewed? - Would real-life surviving artifacts of these tools be more reliable references than AI-rendered reconstructions of ambiguous drawings? **Highlights** > Lots of comments about the general use of AI here, but in particular I think the AI renderings are counterproductive and especially misleading in this application. The original drawings have ambiguities in them; they are well done but perspective and scale are off, and there are lots of questions about particular details of the drawings. The AI drawings simply take these particular questionable details and render them as "real." There should be real life artifacts for many of these tools. LLMs can just as easily go search the web for images of those as create completely unreliable, fictional renderings of the same. > — [kornork on hackernews · 1 comments](https://news.ycombinator.com/item?id=50232515) > The problem with AI generated content is, it tells me you didn't care enough about the work to do it yourself. To understand it fully, to the point where you don't need or even want to hand the work off to an LLM. Interacting with AI content makes me feel like I'm consuming something that was created purely for engagement farming. Not that human created content wasn't for engagement farming, but noticing an AI tell breaks the suspension of disbelief in a way. It devalues the relationship between creator and consumer, so that genuine care is not being shared. It's like I'm a cow being milked on an industrial engagement farm. > — [gradus\_ad on hackernews · 5 comments](https://news.ycombinator.com/item?id=50231923) > Note that (1) this is just your opinion and (2) that he has put a lot less effort into it than others have put into similar endeavors which as a result have a different level of authenticity. > You are letting your personal biases color your view. That is your right, but check to see if it is making you happy. Why the free psycho analysis? GP just made a statement. > — [jacquesm on hackernews · 1 comments](https://news.ycombinator.com/item?id=50232642) > > But as a single person, I can only take on a project this big with AI as a tool. That's so not true though. One of my uncles did work like this and it usually took a year or two to fully research a project and write a book but it is definitely doable to do this sort of thing - and much better, frankly - as a single individual. AI makes it a matter of days, but it also makes it next to worthless. The biggest contribution here is to an otherwise lesser known book. https://de.wikipedia.org/wiki/L%C3%B6ffelholz-Codex (Couldn't find an English wikipedia page on it) > — [jacquesm on hackernews](https://news.ycombinator.com/item?id=50232717) > I feel that obvious LLM content like this adds value, and I wasn’t entirely put off by this. I see the text as plausible, I just would need to research anything here before repeating it or referring to it in some way. > — [Isamu on hackernews](https://news.ycombinator.com/item?id=50232268) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=50230917) · 121 points · 64 comments ## Similar posts on daily.dev - [Hand-Machined Stake Sharpener Just In Time For Dracula Season](https://daily.dev/posts/hand-machined-stake-sharpener-just-in-time-for-dracula-season-fc9cv5dns) · Hackaday · 0 upvotes · 0 comments - [The Book of St Albans \(1486\)](https://daily.dev/posts/the-book-of-st-albans-1486--jxivrdezj) · Arthur O'Dwyer · 0 upvotes · 0 comments - [Schneier on Security](https://daily.dev/posts/schneier-on-security-btivfoc3r) · Schneier on Security · 0 upvotes · 0 comments - [Artificial Intelligence: Ars Notoria and the Promise of Instant Knowledge](https://daily.dev/posts/artificial-intelligence-ars-notoria-and-the-promise-of-instant-knowledge-fphgptf5y) · Hacker News · 0 upvotes · 0 comments --- Tags: [#open-source](https://daily.dev/tags/open-source) [View this post on daily.dev](https://daily.dev/posts/tool-book-of-a-nuremberg-knight-from-1505-te41nuxib) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Tool book of a Nuremberg knight from 1505","url":"https://daily.dev/posts/tool-book-of-a-nuremberg-knight-from-1505-te41nuxib","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/tool-book-of-a-nuremberg-knight-from-1505-te41nuxib"},"datePublished":"2026-10-25T15:02:07.820Z","dateModified":"2026-10-25T16:18:16.098Z","description":"A passion project is transcribing and translating every page of the Löffelholz Codex, a 1505 Nuremberg tool book that has never been fully read in 500 years....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/97ec7a5aafad562241ad2583e050c578?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/97ec7a5aafad562241ad2583e050c578?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/tool-book-of-a-nuremberg-knight-from-1505-te41nuxib","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Tool book of a Nuremberg knight from 1505"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/tool-book-of-a-nuremberg-knight-from-1505-te41nuxib#faq","mainEntity":[{"@type":"Question","name":"What language is the Löffelholz Codex written in?","acceptedAnswer":{"@type":"Answer","text":"It is written in Early New High German, specifically the written language used in Nuremberg around 1505, with no fixed spelling. The same word can appear spelled two different ways on a single page, a stroke over a letter can stand for an n or m, and many workshop terms do not appear in any modern dictionary. Readers decoding historical or technical texts can track detailed breakdowns like this on daily.dev."}},{"@type":"Question","name":"Where is the original Löffelholz Codex manuscript kept today?","acceptedAnswer":{"@type":"Answer","text":"The original is held by the Biblioteka Jagiellońska (Jagiellonian Library) in Kraków, under the shelfmark Ms. Berol. germ. quart. 132. It has been fully digitized and can be viewed freely through the Jagiellonian Library's digital collection at jbc.bj.uj.edu.pl. Those researching historical manuscripts can follow ongoing digitization efforts like this one on daily.dev."}},{"@type":"Question","name":"Who was Martin Löffelholz von Kolberg and why did he write the Codex?","acceptedAnswer":{"@type":"Answer","text":"He was a Nuremberg patrician and knight who died in 1533, serving 28 years as Pfleger (warden) of the fortress of Lichtenau. Between 1507 and 1509 he was held captive for more than a year, which may explain why shackles and locks take up a strikingly large share of his 154-page tool and machine book, begun in 1505. People tracing the backstories behind historical engineering works can follow projects like this on daily.dev."}}]} ```