add all 2016 summaries
Browse files
Blockchain and Hyperledger_summary.txt
ADDED
|
@@ -0,0 +1,29 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
• IBM Blockchain division and Hyperledger Project
|
| 2 |
+
• Anna Derbakova's role at IBM and contribution to Hyperledger
|
| 3 |
+
• Raleigh location of main development team for IBM Blockchain
|
| 4 |
+
• Explanation of blockchain technology and its components (distributed ledger, consensus, blocks)
|
| 5 |
+
• Comparison between blockchain and traditional systems in terms of data modification and tampering
|
| 6 |
+
• Append-only ledger: transactions append at the end and cannot be modified
|
| 7 |
+
• Blockchain technology in finance and supply chains to record transactions and track assets
|
| 8 |
+
• Security features: hard to cheat on blockchain, can trace issues and remove question marks
|
| 9 |
+
• Replacing existing technologies: automating processes, removing inefficiencies, and storing data
|
| 10 |
+
• Integrating with other technologies: IoT, for example, for real-time tracking and monitoring
|
| 11 |
+
• Blockchain types: different implementations (e.g. Bitcoin, Ethereum) with same underlying ideas
|
| 12 |
+
• Versions: not a strict versioning system, but rather evolving technology with new features and capabilities
|
| 13 |
+
• Different blockchain systems and their potential interoperability
|
| 14 |
+
• Role of IBM in the Hyperledger project
|
| 15 |
+
• Structure and projects under the Hyperledger umbrella
|
| 16 |
+
• Challenges and barriers to entry for new contributors
|
| 17 |
+
• Future direction and adoption of blockchain technology
|
| 18 |
+
• Open-source development and community engagement on Hyperledger Slack channels
|
| 19 |
+
• Bluemix offering with blockchain tile
|
| 20 |
+
• Docker images available on Docker Hub for Hyperledger network peers
|
| 21 |
+
• Getting started tutorials and documentation for Hyperledger basics
|
| 22 |
+
• Blockchain concepts explained in Anna Derbakova's talk, covering Bitcoin, data storage, blocks, consensus, and more
|
| 23 |
+
• Overview of Hyperledger, its differences from Ethereum and Bitcoin, and how to get involved
|
| 24 |
+
• IBM Blockchain using Go as a primary language, with other languages like Node.js, Java, and Python also used
|
| 25 |
+
• Separate repo for Node.js SDK, previously part of the main Fabric project
|
| 26 |
+
• Hyperledger Fabric core is written primarily in Go
|
| 27 |
+
• SDKs are being developed in specific languages such as Python and others
|
| 28 |
+
• Anna Derbakova mentions hyperledger.org for more information and Hyperledger Slack channel for questions and help
|
| 29 |
+
• Difficulty navigating documentation can be addressed by joining the Slack channel
|
Exercism and 99 Bottles of OOP_summary.txt
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
• Katrina Owen's early days as an anonymous developer
|
| 2 |
+
• Exercism.io and 99 Bottles of OOP
|
| 3 |
+
• Sandi Metz's background and how she became a well-known speaker
|
| 4 |
+
• Ruby programming language and its creator, Matz
|
| 5 |
+
• Katrina Owen's meeting with Sandi Metz and reading her book in beta form
|
| 6 |
+
• Katrina Owen's experience giving a talk at a conference and being encouraged by others to do more public speaking
|
| 7 |
+
• The confidence boost Katrina Owen received after people reacted positively to her talks
|
| 8 |
+
• Kristina Owen gave a talk called "Therapeutic Refactoring" at a conference
|
| 9 |
+
• The talk was about refactoring as a process that can make you smarter by offloading irrelevant details to tests
|
| 10 |
+
• It used an example from Martin Fowler's book and was told as a story rather than a traditional presentation
|
| 11 |
+
• The talk received positive feedback and helped launch Kristina Owen's speaking career
|
| 12 |
+
• She also got feedback on the early versions of her talk from Sandi Metz, who became a friend and collaborator
|
| 13 |
+
• Kristina Owen later worked with Sandi Metz on POODR and launched Exercism, which was featured in Wired
|
| 14 |
+
• The origins of the 99 Bottles problem in Exercism
|
| 15 |
+
• Sandi Metz's expertise and "expert intuition" in solving the problem
|
| 16 |
+
• The book writing process, including collaboration, curriculum development, and editing
|
| 17 |
+
• The beta release of the first five chapters of the book (99 Bottles)
|
| 18 |
+
• The book by Kristina Owen is compelling and transformative in its approach to coding
|
| 19 |
+
• Conferences can be intimidating but are valuable for meeting people and having real conversations
|
| 20 |
+
• Overcoming initial awkwardness at conferences can lead to deeper connections and relationships
|
| 21 |
+
• Stepping out of one's comfort zone and engaging with others is key to making the most of conference experiences
|
GitHub Product & GraphQL_summary.txt
ADDED
|
@@ -0,0 +1,31 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
• Coby Chapple's background and where he lives
|
| 2 |
+
• Product design role at GitHub: focus on workflows and interactions rather than visual design
|
| 3 |
+
• Biggest single change made to the product: enabling web-based edits to files
|
| 4 |
+
• Importance of creating shortcuts and streamlining processes for users
|
| 5 |
+
• Enjoyment of long-term responsibility for products and seeing how they are used over time
|
| 6 |
+
• Blurring of lines between UI/UX: Coby focuses on what needs to happen rather than labels or silos
|
| 7 |
+
• Code review feature
|
| 8 |
+
• Batching code reviews into a single conversation or document
|
| 9 |
+
• Interface problems with batching code reviews
|
| 10 |
+
• Designing complex technical products for technical users
|
| 11 |
+
• Balance between approachability and technical complexity
|
| 12 |
+
• Importance of discoverability in product design
|
| 13 |
+
• Projects feature: flexible workflows, not dictating process to users
|
| 14 |
+
• Product expansion with the introduction of "Projects" as a new tab/page
|
| 15 |
+
• Relationship between Issues and Projects: flexible and not strictly tied to each other
|
| 16 |
+
• Decision to associate Projects with the repo layer of abstraction, but planning for future changes to allow for multiple repos or organization-level projects
|
| 17 |
+
• Impact on organizational hierarchy and potential for infinite nesting
|
| 18 |
+
• Plans for improving and expanding Projects in the future
|
| 19 |
+
• The concept of "sherlocking" where platform providers copy features created by third-party integrators
|
| 20 |
+
• Projects API integration and the need for basic functionality with flexibility and adaptability
|
| 21 |
+
• GraphQL API adoption, including GitHub's decision to use it and its benefits for developers and customers
|
| 22 |
+
• Reducing risk through dependable APIs that minimize complexity and allow for predictable development and iteration
|
| 23 |
+
• The benefits and challenges of implementing GraphQL for API functionality
|
| 24 |
+
• Caching and performance considerations with GraphQL
|
| 25 |
+
• GitHub Projects' design goals and target audience
|
| 26 |
+
• Comparison to project management tools like Trello and Pivotal Tracker
|
| 27 |
+
• Enterprise customers' needs and the importance of customization within organizations
|
| 28 |
+
• Wrap-up of episode
|
| 29 |
+
• Thanks to O'Reilly for working partnership at OSCON London 2016
|
| 30 |
+
• Upcoming OSCON event in Austin, Texas in 2017
|
| 31 |
+
• Discount code for registration: "changelog20"
|
The JS Foundation_summary.txt
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
• Launch of JS Foundation, merging jQuery Foundation with other projects
|
| 2 |
+
• Kris Borchers discusses his background and moving to Dallas from Chicago
|
| 3 |
+
• Overarching mission: "Innovate together", creating a center for open source JavaScript
|
| 4 |
+
• Supporting 23 projects, providing infrastructure, events, travel assistance, legal help
|
| 5 |
+
• Funding is not typically invested in development, but rather in support and resources
|
| 6 |
+
• Member projects include jQuery, Webpack, Mocha, Moment.js, Node-RED, Interledger.js
|
| 7 |
+
• Comparing the JS Foundation to the Linux Foundation, focusing on JavaScript
|
| 8 |
+
• Discussing funding models, including corporate sponsorship and direct developer funding
|
| 9 |
+
• Exploring concerns about corporate influence over projects through sponsorships
|
| 10 |
+
• Introducing the JS Foundation's mentorship program for maintaining project autonomy
|
| 11 |
+
• Outlining the membership process and requirements for projects and member companies
|
| 12 |
+
• Describing the Technical Advisory Committee charter and application process for new projects
|
| 13 |
+
• Membership model is not pay-to-play and anyone can contribute to projects
|
| 14 |
+
• Open-source JavaScript projects can be accessed through js.foundation/projects
|
| 15 |
+
• Mentorship process helps new contributors get involved and advance in projects
|
| 16 |
+
• Membership levels include top-level members with a seat on the board of directors, middle level with one seat per five members, and an associate level membership that is free for non-profits and academic institutions
|
| 17 |
+
• Top sponsors include IBM, Samsung, Boku, SitePen, SauceLabs, Sense Tecnic, StackPath, and MaxCDN
|
| 18 |
+
• JS Foundation partners with Linux Foundation collaborative project to have a single voice for JavaScript in web standards processes and project mentorship
|
| 19 |
+
• Texas
|
| 20 |
+
• Changelog.com/spotlight
|
| 21 |
+
• Subscription options
|
Welcome to Spotlight_summary.txt
ADDED
|
@@ -0,0 +1,5 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
• Launch of new show "Spotlight" by Changelog
|
| 2 |
+
• Show concept: recording hallway conversations at conferences
|
| 3 |
+
• Unique production style: producing episodes in batches from multiple events
|
| 4 |
+
• Upcoming series based on OSCON, All Things Open, Node Interactive, and other events
|
| 5 |
+
• Discussion of personal experiences with Sandi Metz and other conference attendees
|