-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6eb0f60
commit a008395
Showing
3 changed files
with
144 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| { | ||
| "timestamp": "2024-09-21T13:53:30.696359", | ||
| "user_prompt": "what's the best book for engineers", | ||
| "rephrased_query": "What is the best book for engineers?", | ||
| "docs_retrieved": [ | ||
| { | ||
| "pageContent": "The Art and Doing Science of Engineering, by Richard Hamming (the dude who invented the Hamming Codes...oh, and he helped program the computers for the Manhattan Project in 1945). It's a fantastic book about engineering, how it's evolved, how you can think of it like an art to solve interesting problems creatively.", | ||
| "metadata": { | ||
| "title": "What are some books that every engineer should read?", | ||
| "url": "https://www.reddit.com/r/engineering/comments/4vjr0a/what_are_some_books_that_every_engineer_should/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "The old books are still very valuable, but since you know them, here's a list of books released quite recently (10 years top): Modern Software Engineering, Dave Farlay. Software Engineering at Google, Lessons Learned from Programming Over Time, Titus Winters (also available for free in html format) The DevOps Handbook. The Phoenix Project.", | ||
| "metadata": { | ||
| "title": "Looking for modern books on software engineering", | ||
| "url": "https://www.reddit.com/r/softwaredevelopment/comments/14bsl0b/looking_for_modern_books_on_software_engineering/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Examines the history of precision and accuracy in engineering and manufacturing. By all means it should be a pretty dry read but it's actually really poetic in a way. Winchester writes each section of the book as a precision and it gets more and more advanced as the book continues.", | ||
| "metadata": { | ||
| "title": "What are some good books you think every mechanical engineer ... - Reddit", | ||
| "url": "https://www.reddit.com/r/MechanicalEngineering/comments/12rd6x8/what_are_some_good_books_you_think_every/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Shigley's Mechanical Eng Design - For if you ever intend to design mechanical parts and assemblies. It goes along with Machinery's Handbook. For summary databooks, check out Engineers' Practical Databook.I tried the IMechE (Clifford Mathews) one but sadly it was a waste of money, as more than 50% was written waffle geared towards undergraduates and fresh graduates.", | ||
| "metadata": { | ||
| "title": "Mechanical design engineers - Which books would you recommend?", | ||
| "url": "https://www.reddit.com/r/MechanicalEngineering/comments/k8wze1/mechanical_design_engineers_which_books_would_you/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Ignition, John D. Clark (humorous book about the history of rocket fuels) . QED, Richard Feynman (An absolutely amazing book boiling the core elements of QED down to examples and diagrams that a non-theoretical physicist can understand) . Engineering infinity (a collection of sci-fi short stories that question the direction of different scientific advancements.)", | ||
| "metadata": { | ||
| "title": "What are the best books for Mechanical Engineering : r ... - Reddit", | ||
| "url": "https://www.reddit.com/r/MechanicalEngineering/comments/95bcsm/what_are_the_best_books_for_mechanical_engineering/", | ||
| "img_src": null | ||
| } | ||
| } | ||
| ], | ||
| "llm_answer": "If you're interested in essential literature for engineers, several noteworthy books have been highlighted across various discussions on Reddit. Here’s a compilation of recommendations and their insights:\n\n### Core Engineering Texts\n- **The Art and Doing Science of Engineering by Richard Hamming**: This book emphasizes the creative aspects of engineering and how it can be likened to an art form. Hamming's reflections on engineering present it as a discipline that evolves through innovative problem-solving [1].\n \n### Recent Publications in Software Engineering\n- **Modern Software Engineering by Dave Farley**: This contemporary book focuses on the latest methodologies and practices in software development.\n- **Software Engineering at Google by Titus Winters**: It shares lessons learned from programming over time at Google, making it both practical and insightful (available for free in HTML format).\n- **The DevOps Handbook and The Phoenix Project**: Both texts delve into the practices and principles behind successful software engineering and operations management [2].\n\n### Mechanical Engineering Favorites\n- **Shigley's Mechanical Engineering Design**: This reference is vital for those involved in the design of mechanical parts and assemblies. It is often paired with the well-known *Machinery's Handbook* for a comprehensive understanding of design capabilities [4].\n- **Engineering Infinity**: A collection of sci-fi short stories that explores potential directions for scientific advancements, offering imaginative perspectives relevant to the field of engineering [5].\n\n### Historical and Conceptual Reads\n- **The History of Precision and Accuracy in Engineering and Manufacturing**: This book is noted for its poetic approach, incrementally advancing the complexity of its topics related to precision in engineering [3].\n- **Ignition by John D. Clark**: This humorous take on the history of rocket fuels serves to engage readers with a light-hearted look at serious engineering themes while also being informative about the subject matter [5].\n- **QED by Richard Feynman**: Aimed at a wider audience, Feynman distills complex concepts of quantum electrodynamics using accessible examples, bridging the gap for non-theoretical physicists [5].\n\nThese texts collectively provide a rounded foundation for both new and experienced engineers looking to deepen their understanding of their field. Whether you're inclined towards practical manuals or conceptual discussions, this list should cater to a variety of interests within engineering disciplines." | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| { | ||
| "timestamp": "2024-09-21T13:56:06.477205", | ||
| "user_prompt": "what's the best book for engineers", | ||
| "rephrased_query": "What is the best book for engineers?", | ||
| "docs_retrieved": [ | ||
| { | ||
| "pageContent": "The Art and Doing Science of Engineering, by Richard Hamming (the dude who invented the Hamming Codes...oh, and he helped program the computers for the Manhattan Project in 1945). It's a fantastic book about engineering, how it's evolved, how you can think of it like an art to solve interesting problems creatively.", | ||
| "metadata": { | ||
| "title": "What are some books that every engineer should read?", | ||
| "url": "https://www.reddit.com/r/engineering/comments/4vjr0a/what_are_some_books_that_every_engineer_should/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "The old books are still very valuable, but since you know them, here's a list of books released quite recently (10 years top): Modern Software Engineering, Dave Farlay. Software Engineering at Google, Lessons Learned from Programming Over Time, Titus Winters (also available for free in html format) The DevOps Handbook. The Phoenix Project.", | ||
| "metadata": { | ||
| "title": "Looking for modern books on software engineering", | ||
| "url": "https://www.reddit.com/r/softwaredevelopment/comments/14bsl0b/looking_for_modern_books_on_software_engineering/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Examines the history of precision and accuracy in engineering and manufacturing. By all means it should be a pretty dry read but it's actually really poetic in a way. Winchester writes each section of the book as a precision and it gets more and more advanced as the book continues.", | ||
| "metadata": { | ||
| "title": "What are some good books you think every mechanical engineer ... - Reddit", | ||
| "url": "https://www.reddit.com/r/MechanicalEngineering/comments/12rd6x8/what_are_some_good_books_you_think_every/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Shigley's Mechanical Eng Design - For if you ever intend to design mechanical parts and assemblies. It goes along with Machinery's Handbook. For summary databooks, check out Engineers' Practical Databook.I tried the IMechE (Clifford Mathews) one but sadly it was a waste of money, as more than 50% was written waffle geared towards undergraduates and fresh graduates.", | ||
| "metadata": { | ||
| "title": "Mechanical design engineers - Which books would you recommend?", | ||
| "url": "https://www.reddit.com/r/MechanicalEngineering/comments/k8wze1/mechanical_design_engineers_which_books_would_you/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Ignition, John D. Clark (humorous book about the history of rocket fuels) . QED, Richard Feynman (An absolutely amazing book boiling the core elements of QED down to examples and diagrams that a non-theoretical physicist can understand) . Engineering infinity (a collection of sci-fi short stories that question the direction of different scientific advancements.)", | ||
| "metadata": { | ||
| "title": "What are the best books for Mechanical Engineering : r ... - Reddit", | ||
| "url": "https://www.reddit.com/r/MechanicalEngineering/comments/95bcsm/what_are_the_best_books_for_mechanical_engineering/", | ||
| "img_src": null | ||
| } | ||
| } | ||
| ], | ||
| "llm_answer": "If you're looking for notable books in the field of engineering, several recommendations stand out across various branches of engineering disciplines. Here’s a compiled list of influential titles:\n\n### General Engineering\n- **\"The Art and Doing Science of Engineering\" by Richard Hamming**: This book offers insights into the evolution of engineering and emphasizes creative problem-solving, likening engineering to an art form. Hamming is well-known for his contributions to computer science and engineering, making this book a valuable read for any engineer [1].\n\n### Software Engineering\n- **\"Modern Software Engineering\" by Dave Farley**: This book provides contemporary approaches and methodologies essential for software engineering.\n- **\"Software Engineering at Google: Lessons Learned from Programming Over Time\" by Titus Winters**: This is a practical guide that shares experiences and lessons learned from programming at Google. It is also available for free online.\n- **\"The DevOps Handbook\" and \"The Phoenix Project\"**: These titles focus on the integration of software development and IT operations, providing frameworks for effective collaboration [2].\n\n### Mechanical Engineering\n- **\"Shigley's Mechanical Engineering Design\"**: This is a critical resource for anyone involved in designing mechanical parts and assemblies. It is often paired with **Machinery's Handbook** for comprehensive understanding.\n- **\"Engineers' Practical Databook\"**: Provides practical data necessary for engineers, although specific recommendations may vary based on personal experiences — some find other databooks less useful [4].\n- **\"Ignition\" by John D. Clark**: This humorous book covers the history of rocket fuels and offers an engaging perspective on a niche aspect of mechanical engineering.\n- **\"QED\" by Richard Feynman**: It breaks down quantum electrodynamics into understandable terms for non-specialists, making complex science accessible [5].\n\n### Other Notable Mentions\n- **\"Engineering Infinity\"**: A collection of sci-fi short stories that explore philosophical questions about the direction of scientific advancements, which may inspire engineers to think beyond conventional boundaries [5].\n\nThese titles reflect a blend of foundational theory, practical advice, and innovative thinking, making them essential reads for both aspiring and established engineers across disciplines. Whether you are looking to enhance your technical skills or gain insights into the creativity inherent in engineering, these books provide a well-rounded foundation for further exploration." | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| { | ||
| "timestamp": "2024-09-21T14:15:11.271273", | ||
| "user_prompt": "what's better, x11 or wayland? why?", | ||
| "rephrased_query": "What are the advantages and disadvantages of X11 compared to Wayland?", | ||
| "docs_retrieved": [ | ||
| { | ||
| "pageContent": "advantages of Wayland is that its faster. That's a strange advantage to list. On most systems, the difference is that wayland is tear-free by default and it's faster than tear-free X11. on a single user pc its mostly a \"security circus\". I disagree.", | ||
| "metadata": { | ||
| "title": "X11 vs Wayland : r/linuxquestions - Reddit", | ||
| "url": "https://www.reddit.com/r/linuxquestions/comments/hh9v6z/x11_vs_wayland/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Main advantages of Wayland: Core protocol is tiny and easy to implement (not that it would matter for a user), protocol extensions are optional and pretty well-thought-out. Main disadvantage of Wayland is that some apps are not compatible with it, and XWayland has issues (like broken HiDPI, subpar performance, etc).", | ||
| "metadata": { | ||
| "title": "What's the diference/benefits of using wayland vs X11?", | ||
| "url": "https://www.reddit.com/r/linuxquestions/comments/m4fzbb/whats_the_diferencebenefits_of_using_wayland_vs/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Advantage: In Wayland, the rendering is not done at the network's server, more similar to a stand alone PC like Windows OS. Disadvantage: Still under development ... If you want a in depth discussion about wayland advantages, there is this talk. 12 votes, 13 comments.", | ||
| "metadata": { | ||
| "title": "What are the advantages and disadvantages of wayland over x11?", | ||
| "url": "https://www.reddit.com/r/wayland/comments/q99lhp/what_are_the_advantages_and_disadvantages_of/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "Wayland is more secure. A program only gets access to keystrokes and mouse movements if its window is actually focused. A keylogger in x11 is litterally just a few lines of code. Wayland is being maintained and developed. I do not even know if someone is still maintaining x11, fixing vulnerabilities and such. 90.", | ||
| "metadata": { | ||
| "title": "Why use wayland over x11? : r/linuxquestions - Reddit", | ||
| "url": "https://www.reddit.com/r/linuxquestions/comments/w16jh4/why_use_wayland_over_x11/", | ||
| "img_src": null | ||
| } | ||
| }, | ||
| { | ||
| "pageContent": "My undergraduate dissertation was on comparing X11 and Wayland display server protocols in full-screen applications. As you may know if you e.g. play games on Linux, the X11 compositor imposes a performance penalty on the game as it introduces unnecessary steps in the graphics stack. You can usually increase video game performance by disabling ...", | ||
| "metadata": { | ||
| "title": "Comparing Wayland and X11 Display Server Protocols in Full ... - Reddit", | ||
| "url": "https://www.reddit.com/r/linux/comments/ca60wg/comparing_wayland_and_x11_display_server/", | ||
| "img_src": null | ||
| } | ||
| } | ||
| ], | ||
| "llm_answer": "Wayland is a modern display server protocol that offers several advantages over its predecessor, X11. Here's a breakdown of its key benefits and drawbacks:\n\n### Advantages of Wayland\n\n- **Performance Improvement**: Wayland typically provides faster rendering than X11, mainly because it operates more efficiently and is tear-free by default [1]. This is particularly noticeable in environments where visual output is crucial, such as in gaming or high-performance applications [5].\n\n- **Security Enhancements**: One of Wayland's notable features is its improved security. Applications can only access keystrokes or mouse movements when their window is focused, reducing the risk of keyloggers, which can be easily implemented in X11 [4]. This controlled access helps in limiting the potential for malicious activities.\n\n- **Simplified Architecture**: The core protocol of Wayland is quite small and straightforward, making it easier to implement. Optional protocol extensions are also well-designed, contributing to its adaptability and ease of use [2].\n\n- **More Similar to Standalone Systems**: With rendering handled locally rather than through networked servers—as seen in X11—Wayland operates more like desktop environments in Windows or macOS. This model can lead to improved user experiences in standalone applications [3].\n\n### Disadvantages of Wayland\n\n- **Application Compatibility Issues**: A significant concern with Wayland is compatibility. Some applications may not work seamlessly with Wayland, necessitating the use of XWayland, which can exhibit problems such as HiDPI issues and overall performance degradation [2]. This can be a drawback for users relying on specific applications.\n\n- **Development Stage**: While Wayland is actively maintained, it is still under development. There may be features or stability issues that are not yet fully addressed, which could affect user experience [3].\n\n- **Limited Community Support for X11**: There is uncertainty regarding the ongoing maintenance and security updates for X11, which could discourage users from relying on it as a long-term solution [4]. \n\nIn summary, while Wayland possesses several compelling advantages, particularly in performance and security, users should be aware of its limitations regarding application compatibility and the ongoing need for development. The transition from X11 to Wayland could lead to better performance and enhanced security, albeit with some potential compatibility challenges." | ||
| } |