Integrating the compiler with unit testing
•Download as PPT, PDF•
0 likes•248 views
The document discusses integrating compilers and unit testing by treating the compiler as part of the programming language. It mentions reasons why the Lisp programming language is effective, including compiler macros and directives that allow separating ideas from implementation details. The document also raises the problem that provably correct optimizations are difficult but suggests a solution is trial-and-error testing that can serve as both proofs and benchmarks for compiler correctness and evolution.
Report
Share
Report
Share
![Integrating the compiler with unit testing [email_address]](https://image.slidesharecdn.com/compilersunit-tests-091129042457-phpapp02/85/Integrating-the-compiler-with-unit-testing-1-320.jpg)
Recommended
Rational Functional Tester
This document certifies that Ravi Anand has successfully completed the IBM Certified Solution Designer program requirements for Rational Functional Tester for Java. It recognizes his commitment to achieve professional excellence and is signed by the Senior Vice President of IBM Software Solutions Group and General Manager of Rational Software.
RFT - Ashish Mathur
This document discusses new features in IBM Rational Performance Tester Version 8.1. It describes enhancements that help with performance testing in agile environments, for performance test specialists, and for performance analysts. Key updates include improved definition and reporting of performance requirements, enhanced test case development features, and new analysis capabilities for monitoring resources and viewing run-time data.
Regression Tests with Symfony - Example
This document discusses tools and techniques for building regression test suites in Symfony projects. It covers using the BehatBundle to write functional tests with the Gherkin language and defining scenarios with keywords like Given, When, Then. It also discusses the MinkBundle for integrating different browser drivers like Zombie JS, Sahi, and Selenium to run the tests. The BehatBundle maps Gherkin features and scenarios to PHP test classes and methods.
Performance Regression Analysis: Accomplishments and Challenges
My invited talk at the The Fifth International Workshop on Large-Scale Testing (LT 2016, co-located with ICPE).
Git code reviews
Code reviews improve code quality and transparency by providing a discussion platform to foster continuous self-improvement. They reduce bug fixing and new feature implementation times by catching issues early. GitFlow workflow with merge requests enables code reviews. Developers start a feature branch, push commits to the central repository, and create a merge request for review. Reviewers test the code locally, check for bugs, quality, and style. They discuss improvements in the merge request before accepting it to merge into the main branch.
An exploratory study of the state of practice of performance testing in Java-...
The document summarizes an exploratory study of performance testing practices in 111 Java-based open source projects. The study examined performance testing from five perspectives: developers involved, extent of testing, organization of tests, types of tests, and tools used. Key findings include that performance tests are done by a small group, suites are typically small, and there is no standard organization. The implications are that there is a lack of tools for performance testing, it is not a popular task, and developers want support for quick testing.
Software testing
This document discusses various software development life cycle (SDLC) models. It describes the waterfall model, prototype model, incremental model, spiral model, RAD model, V-model, and agile model. For each model, it provides an overview of the process flow and highlights advantages and disadvantages. It also discusses different testing techniques used at various stages like unit testing, integration testing, documentation testing etc. Overall, the document provides a comprehensive overview of different SDLC models and testing approaches used in software engineering.
Ping-Pong Programming
Ping Pong Programming is a game where two players collaborate to write code by passing a serve back and forth. Player A serves by writing a test case. If the test fails, Player B implements the code to pass the test. If refactoring is needed, Player A performs it and scores a point. The goal is to maintain focus, foster learning, fail and refactor quickly, and produce fully tested code.
Recommended
Rational Functional Tester
This document certifies that Ravi Anand has successfully completed the IBM Certified Solution Designer program requirements for Rational Functional Tester for Java. It recognizes his commitment to achieve professional excellence and is signed by the Senior Vice President of IBM Software Solutions Group and General Manager of Rational Software.
RFT - Ashish Mathur
This document discusses new features in IBM Rational Performance Tester Version 8.1. It describes enhancements that help with performance testing in agile environments, for performance test specialists, and for performance analysts. Key updates include improved definition and reporting of performance requirements, enhanced test case development features, and new analysis capabilities for monitoring resources and viewing run-time data.
Regression Tests with Symfony - Example
This document discusses tools and techniques for building regression test suites in Symfony projects. It covers using the BehatBundle to write functional tests with the Gherkin language and defining scenarios with keywords like Given, When, Then. It also discusses the MinkBundle for integrating different browser drivers like Zombie JS, Sahi, and Selenium to run the tests. The BehatBundle maps Gherkin features and scenarios to PHP test classes and methods.
Performance Regression Analysis: Accomplishments and Challenges
My invited talk at the The Fifth International Workshop on Large-Scale Testing (LT 2016, co-located with ICPE).
Git code reviews
Code reviews improve code quality and transparency by providing a discussion platform to foster continuous self-improvement. They reduce bug fixing and new feature implementation times by catching issues early. GitFlow workflow with merge requests enables code reviews. Developers start a feature branch, push commits to the central repository, and create a merge request for review. Reviewers test the code locally, check for bugs, quality, and style. They discuss improvements in the merge request before accepting it to merge into the main branch.
An exploratory study of the state of practice of performance testing in Java-...
The document summarizes an exploratory study of performance testing practices in 111 Java-based open source projects. The study examined performance testing from five perspectives: developers involved, extent of testing, organization of tests, types of tests, and tools used. Key findings include that performance tests are done by a small group, suites are typically small, and there is no standard organization. The implications are that there is a lack of tools for performance testing, it is not a popular task, and developers want support for quick testing.
Software testing
This document discusses various software development life cycle (SDLC) models. It describes the waterfall model, prototype model, incremental model, spiral model, RAD model, V-model, and agile model. For each model, it provides an overview of the process flow and highlights advantages and disadvantages. It also discusses different testing techniques used at various stages like unit testing, integration testing, documentation testing etc. Overall, the document provides a comprehensive overview of different SDLC models and testing approaches used in software engineering.
Ping-Pong Programming
Ping Pong Programming is a game where two players collaborate to write code by passing a serve back and forth. Player A serves by writing a test case. If the test fails, Player B implements the code to pass the test. If refactoring is needed, Player A performs it and scores a point. The goal is to maintain focus, foster learning, fail and refactor quickly, and produce fully tested code.
Bootstrapping in Compiler
The document discusses tombstone diagrams, which use puzzle pieces to represent language processors and programs. It then explains bootstrapping, which refers to using a compiler to compile itself. This allows obtaining a compiler for a new target machine by first writing a compiler in a high-level language, compiling it on the original machine, and then using the output compiler to compile itself on the new target machine. The document provides examples of using bootstrapping to generate cross-compilers that run on one machine but produce code for another.
Python Programming | JNTUA | UNIT 2 | Fruitful Functions |
This document discusses Python programming concepts including fruitful functions, return values, incremental development, nested functions, Boolean functions, recursion, and type checking. Fruitful functions allow a function to return a value that can be used. Return values terminate function execution, and code after a return is dead code. Incremental development adds and tests small amounts of code at a time to avoid long debugging sessions. Nested functions allow one function to be called within another through composition. Boolean functions return True or False values. Recursion and type checking with isinstance are also covered.
Agile testing - Reducing time to Market
This document discusses agile testing and how it can help reduce time to market. It covers agile methodologies like Scrum and Kanban. An agile tester works with the agile team to focus on quality and customer needs. Testing in agile is a shared responsibility. The document discusses iterative testing, unit testing using test-driven development, functional testing, and non-functional testing. It also covers risk-based testing and transforming legacy applications to agile.
Test Driven Development #sitFRA
This document discusses test driven development (TDD) in ABAP. It introduces TDD and its advantages such as improved software architecture and quality. It describes tools for TDD in ABAP like ABAP Unit for writing unit tests. Examples demonstrate using TDD for data access and business logic. Challenges of TDD with legacy code and SAP standard extensions are also addressed. Dependencies must be mocked or replaced to enable isolated unit testing.
Testing 1, 2, 3, ...
A set of slides showing some examples for different types of testing. As presented at Agile 2019, Washington DC
C programming
This document provides an introduction to C programming, including:
- A brief history of C's development in the 1970s and subsequent standardizations.
- The benefits of C like efficiency, portability, and structured programming.
- Common terms for programmers like compiler, interpreter, assembler, linker, and loader.
- An overview of the compilation process from source code to executable program.
- The session objectives are to cover the history of C, common benefits and terms, and the compilation process.
Aspect oriented architecture
Aspect Oriented Architecture (AOA) is an effective agile development method that involves breaking down functional components into parts of the software architecture. AOA tools like AspectJ, join points, advice, and pointcuts are used to address cross-cutting concerns. AOA was applied to the Capella online learning system case study to increase workflow processes and provide a positive customer experience. While AOA allows for effective review of programming mechanisms and better understanding of cross-cutting concerns, potential disadvantages include modifications due to inconsistent tools, performance issues with some applications, and limited reuse of aspects.
Test Driven Development
This document discusses test-driven development (TDD) and acceptance test-driven development (ATDD). It defines TDD as a process of first writing a test, then code to pass the test, and refactoring code while relying on tests. ATDD helps ensure correct external features by defining tests for customer requirements. The document outlines benefits like reduced bugs and increased confidence. It also discusses tools that support TDD/ATDD like unit testing frameworks, FitNesse for acceptance tests, continuous integration, and code coverage tools.
Solid principles
SOLID is a mnemonic device for 5 design principles of object-oriented
programs (OOP) that result in readable, adaptable, and scalable code.
S - Single Responsibility Principle.
O - Open Closed Principle.
L - Liskov Substitution Principle.
I - Interface Segregation Principle.
D - Dependency Inversion Principle.
Agile engineering practices – a short overview
This document provides a short overview of agile engineering practices, including Scrum, XP, Kanban, FDD, and DSDM. It summarizes key practices such as pair programming, test-driven development, behavior driven development, acceptance testing, exploratory testing, polyglot programming, domain specific languages, continuous integration, continuous testing, static code checking, agile databases, lightweight domain modeling, and continuous delivery. Each practice is briefly described in one slide with information on feedback time, styles, and challenges.
Testing in agile
The document discusses testing approaches in Agile development. It outlines Agile core values like prioritizing working software over documentation. It compares the Agile Testing Pyramid model which emphasizes more lightweight unit and integration testing over manual UI testing to the traditional Testing Ice Cream Cone model. It also discusses the Agile Test Quadrants framework and how test automation fits into Agile at different levels including unit, integration/service, and UI testing while maintaining a balance between development and testing. The document provides recommendations for test automation in Agile like starting small and incrementally, balancing automation costs and ROI, and keeping feedback cycles quick.
03 the c language
This document discusses the history and evolution of the C programming language from its origins in the 1970s through the development of the ANSI C standard in 1989. It covers key topics including the original K&R C style, the standardization of C by ANSI and ISO in 1989, differences between older K&R C and ANSI C, new features introduced in C99, and the importance of understanding older C styles when maintaining legacy code.
Productive and Cost Effective Development Feedback Loops Within Continuous De...
This document discusses how continuous development and deployment pipelines can be optimized through faster feedback loops. It recommends that software engineers write unit tests to thoroughly test code, that test engineers focus on integration and negative testing across environments rather than duplicating unit tests, and that pipeline engineers implement features like automatic retries and capturing metrics to improve pipeline efficiency. Together, optimizing each part of the development process can create the fastest feedback loop to enhance productivity.
Tech talks #1- Unit testing and TDD
The document discusses unit testing and test-driven development (TDD). It introduces unit testing and TDD, explaining their benefits and how they can improve quality. It also provides an overview of JUnit for unit testing in Java and the red-green-blue process for TDD. The document concludes with a live demo of TDD and suggestions for implementing TDD and acceptance test-driven development.
End-to-End delivery in flexible and multi-vendor environment
The document discusses end-to-end delivery in flexible multi-vendor environments. It proposes moving from traditional organization structures with separate teams for each component to feature teams that work on entire features across components. It also discusses moving from traditional project scoping focused only on delivery throughput to include product management and customer value. Finally, it outlines changing multi-vendor schemas from separate client-vendor teams to integrated teams across vendors to improve collaboration.
Testing automation in agile environment
Testing automation is important in agile environments to allow for frequent testing of software increments without relying solely on manual testing. In agile, testing automation is treated as part of the development process from the beginning by including automation activities in the backlog and having automation developers work closely with the entire scrum team. Testing automation executes after each code delivery and the results are analyzed by the whole team to help keep the code clean and move the project forward through ongoing automated testing as part of the agile way of life. This differs from the traditional waterfall model where testing automation was more isolated, focused only on regression testing, and had lower priority and integration with the development team.
Test Driven Development
Test-driven development (TDD) is a software development process that employs short cycles of writing a test, making it fail, then writing code to pass the test. This helps improve code design and reduces defects. Each new feature starts with writing a test case, then coding just enough to pass the test, and refactoring the code without changing external behavior. TDD produces test code documentation and allows reversible changes by starting over from the last stable state if new code causes errors.
Win at life with unit testing
This document discusses the benefits of unit testing and how to implement it. Some key points covered include:
- Unit testing helps ensure code works as intended, finds problems earlier, and increases developer confidence. It is especially useful for code involving money, code that has broken before, or code that is tedious to test manually.
- There are two main types of tests - unit tests that isolate small parts of an application and functional tests that ensure components work together. Mock objects are important for writing isolated unit tests.
- Benefits of testing include finding problems earlier, tests can be automated, and it ensures requirements are met. Challenges include the time needed to write tests initially.
- Continuous integration servers
DIG1108C Lesson 7 Fall 2014
This document discusses different types of software testing and test-driven development. It defines functions and how to pass arguments to functions. It describes assertions as true-false statements to check conditions and preconditions and postconditions to define the expected state before and after code execution. It lists different types of testing including unit testing, integration testing, and regression testing. It explains test-driven development as a process of writing automated tests before code to define desired functions and improvements and repeating testing and coding until passing all tests.
Unit testing with Jasmine
Unit testing provides the fastest quality feedback, allows refactoring by preventing regressions, and improves code design. Tests should be written for individual code units using test-driven development, testing during development, and having a comprehensive test suite. Tests help document code behavior and structure and should outnumber lines of code at a ratio of 3:1.
Marvin the paranoid laptop by his owner snim2
Marvin the paranoid laptop -- an Internet of Things enabled laptop, which you can chat to at http://pachubelaptop.appspot.com/
A&D Conf Northrop Grumman
Steve Pedigo of Northrop Grumman gave a presentation about potential partnerships between the company and Arizona's aerospace, aviation, and defense community. Northrop Grumman focuses on areas like C4ISR, cybersecurity, unmanned systems, and logistics. The presentation encouraged companies doing innovative work in STEM fields or with experience in Northrop Grumman's focus areas to meet with them to discuss further collaboration. Representatives from Northrop Grumman invited attendees to several upcoming conferences.
More Related Content
What's hot
Bootstrapping in Compiler
The document discusses tombstone diagrams, which use puzzle pieces to represent language processors and programs. It then explains bootstrapping, which refers to using a compiler to compile itself. This allows obtaining a compiler for a new target machine by first writing a compiler in a high-level language, compiling it on the original machine, and then using the output compiler to compile itself on the new target machine. The document provides examples of using bootstrapping to generate cross-compilers that run on one machine but produce code for another.
Python Programming | JNTUA | UNIT 2 | Fruitful Functions |
This document discusses Python programming concepts including fruitful functions, return values, incremental development, nested functions, Boolean functions, recursion, and type checking. Fruitful functions allow a function to return a value that can be used. Return values terminate function execution, and code after a return is dead code. Incremental development adds and tests small amounts of code at a time to avoid long debugging sessions. Nested functions allow one function to be called within another through composition. Boolean functions return True or False values. Recursion and type checking with isinstance are also covered.
Agile testing - Reducing time to Market
This document discusses agile testing and how it can help reduce time to market. It covers agile methodologies like Scrum and Kanban. An agile tester works with the agile team to focus on quality and customer needs. Testing in agile is a shared responsibility. The document discusses iterative testing, unit testing using test-driven development, functional testing, and non-functional testing. It also covers risk-based testing and transforming legacy applications to agile.
Test Driven Development #sitFRA
This document discusses test driven development (TDD) in ABAP. It introduces TDD and its advantages such as improved software architecture and quality. It describes tools for TDD in ABAP like ABAP Unit for writing unit tests. Examples demonstrate using TDD for data access and business logic. Challenges of TDD with legacy code and SAP standard extensions are also addressed. Dependencies must be mocked or replaced to enable isolated unit testing.
Testing 1, 2, 3, ...
A set of slides showing some examples for different types of testing. As presented at Agile 2019, Washington DC
C programming
This document provides an introduction to C programming, including:
- A brief history of C's development in the 1970s and subsequent standardizations.
- The benefits of C like efficiency, portability, and structured programming.
- Common terms for programmers like compiler, interpreter, assembler, linker, and loader.
- An overview of the compilation process from source code to executable program.
- The session objectives are to cover the history of C, common benefits and terms, and the compilation process.
Aspect oriented architecture
Aspect Oriented Architecture (AOA) is an effective agile development method that involves breaking down functional components into parts of the software architecture. AOA tools like AspectJ, join points, advice, and pointcuts are used to address cross-cutting concerns. AOA was applied to the Capella online learning system case study to increase workflow processes and provide a positive customer experience. While AOA allows for effective review of programming mechanisms and better understanding of cross-cutting concerns, potential disadvantages include modifications due to inconsistent tools, performance issues with some applications, and limited reuse of aspects.
Test Driven Development
This document discusses test-driven development (TDD) and acceptance test-driven development (ATDD). It defines TDD as a process of first writing a test, then code to pass the test, and refactoring code while relying on tests. ATDD helps ensure correct external features by defining tests for customer requirements. The document outlines benefits like reduced bugs and increased confidence. It also discusses tools that support TDD/ATDD like unit testing frameworks, FitNesse for acceptance tests, continuous integration, and code coverage tools.
Solid principles
SOLID is a mnemonic device for 5 design principles of object-oriented
programs (OOP) that result in readable, adaptable, and scalable code.
S - Single Responsibility Principle.
O - Open Closed Principle.
L - Liskov Substitution Principle.
I - Interface Segregation Principle.
D - Dependency Inversion Principle.
Agile engineering practices – a short overview
This document provides a short overview of agile engineering practices, including Scrum, XP, Kanban, FDD, and DSDM. It summarizes key practices such as pair programming, test-driven development, behavior driven development, acceptance testing, exploratory testing, polyglot programming, domain specific languages, continuous integration, continuous testing, static code checking, agile databases, lightweight domain modeling, and continuous delivery. Each practice is briefly described in one slide with information on feedback time, styles, and challenges.
Testing in agile
The document discusses testing approaches in Agile development. It outlines Agile core values like prioritizing working software over documentation. It compares the Agile Testing Pyramid model which emphasizes more lightweight unit and integration testing over manual UI testing to the traditional Testing Ice Cream Cone model. It also discusses the Agile Test Quadrants framework and how test automation fits into Agile at different levels including unit, integration/service, and UI testing while maintaining a balance between development and testing. The document provides recommendations for test automation in Agile like starting small and incrementally, balancing automation costs and ROI, and keeping feedback cycles quick.
03 the c language
This document discusses the history and evolution of the C programming language from its origins in the 1970s through the development of the ANSI C standard in 1989. It covers key topics including the original K&R C style, the standardization of C by ANSI and ISO in 1989, differences between older K&R C and ANSI C, new features introduced in C99, and the importance of understanding older C styles when maintaining legacy code.
Productive and Cost Effective Development Feedback Loops Within Continuous De...
This document discusses how continuous development and deployment pipelines can be optimized through faster feedback loops. It recommends that software engineers write unit tests to thoroughly test code, that test engineers focus on integration and negative testing across environments rather than duplicating unit tests, and that pipeline engineers implement features like automatic retries and capturing metrics to improve pipeline efficiency. Together, optimizing each part of the development process can create the fastest feedback loop to enhance productivity.
Tech talks #1- Unit testing and TDD
The document discusses unit testing and test-driven development (TDD). It introduces unit testing and TDD, explaining their benefits and how they can improve quality. It also provides an overview of JUnit for unit testing in Java and the red-green-blue process for TDD. The document concludes with a live demo of TDD and suggestions for implementing TDD and acceptance test-driven development.
End-to-End delivery in flexible and multi-vendor environment
The document discusses end-to-end delivery in flexible multi-vendor environments. It proposes moving from traditional organization structures with separate teams for each component to feature teams that work on entire features across components. It also discusses moving from traditional project scoping focused only on delivery throughput to include product management and customer value. Finally, it outlines changing multi-vendor schemas from separate client-vendor teams to integrated teams across vendors to improve collaboration.
Testing automation in agile environment
Testing automation is important in agile environments to allow for frequent testing of software increments without relying solely on manual testing. In agile, testing automation is treated as part of the development process from the beginning by including automation activities in the backlog and having automation developers work closely with the entire scrum team. Testing automation executes after each code delivery and the results are analyzed by the whole team to help keep the code clean and move the project forward through ongoing automated testing as part of the agile way of life. This differs from the traditional waterfall model where testing automation was more isolated, focused only on regression testing, and had lower priority and integration with the development team.
Test Driven Development
Test-driven development (TDD) is a software development process that employs short cycles of writing a test, making it fail, then writing code to pass the test. This helps improve code design and reduces defects. Each new feature starts with writing a test case, then coding just enough to pass the test, and refactoring the code without changing external behavior. TDD produces test code documentation and allows reversible changes by starting over from the last stable state if new code causes errors.
Win at life with unit testing
This document discusses the benefits of unit testing and how to implement it. Some key points covered include:
- Unit testing helps ensure code works as intended, finds problems earlier, and increases developer confidence. It is especially useful for code involving money, code that has broken before, or code that is tedious to test manually.
- There are two main types of tests - unit tests that isolate small parts of an application and functional tests that ensure components work together. Mock objects are important for writing isolated unit tests.
- Benefits of testing include finding problems earlier, tests can be automated, and it ensures requirements are met. Challenges include the time needed to write tests initially.
- Continuous integration servers
DIG1108C Lesson 7 Fall 2014
This document discusses different types of software testing and test-driven development. It defines functions and how to pass arguments to functions. It describes assertions as true-false statements to check conditions and preconditions and postconditions to define the expected state before and after code execution. It lists different types of testing including unit testing, integration testing, and regression testing. It explains test-driven development as a process of writing automated tests before code to define desired functions and improvements and repeating testing and coding until passing all tests.
Unit testing with Jasmine
Unit testing provides the fastest quality feedback, allows refactoring by preventing regressions, and improves code design. Tests should be written for individual code units using test-driven development, testing during development, and having a comprehensive test suite. Tests help document code behavior and structure and should outnumber lines of code at a ratio of 3:1.
What's hot (20)
Python Programming | JNTUA | UNIT 2 | Fruitful Functions |
Python Programming | JNTUA | UNIT 2 | Fruitful Functions |
Productive and Cost Effective Development Feedback Loops Within Continuous De...
Productive and Cost Effective Development Feedback Loops Within Continuous De...
End-to-End delivery in flexible and multi-vendor environment
End-to-End delivery in flexible and multi-vendor environment
Viewers also liked
Marvin the paranoid laptop by his owner snim2
Marvin the paranoid laptop -- an Internet of Things enabled laptop, which you can chat to at http://pachubelaptop.appspot.com/
A&D Conf Northrop Grumman
Steve Pedigo of Northrop Grumman gave a presentation about potential partnerships between the company and Arizona's aerospace, aviation, and defense community. Northrop Grumman focuses on areas like C4ISR, cybersecurity, unmanned systems, and logistics. The presentation encouraged companies doing innovative work in STEM fields or with experience in Northrop Grumman's focus areas to meet with them to discuss further collaboration. Representatives from Northrop Grumman invited attendees to several upcoming conferences.
Companyprofile
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Numerical thinking
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Making meditation a part of a daily routine, even if just 10-15 minutes per day, can offer significant health benefits over time such as improved focus, better sleep, and a more positive outlook.
Statisics for hackers
A 80/20 approach to getting maximal insight in the shortest time and for the least fuss from your data (and a tour of corresponding pitfalls).
Brave New Concurrent World
[talk from Webcamp Ljubljana 2009] A non-apologetic treatise on how to think concurrency. Contains exotic languages, swearing, and only a passing relevance to the web.
Prgišče Lispa
The document discusses functional programming concepts in Common Lisp including: abstraction of common operations using functions, recursion, iteration and filtering; functions as parameters; combining functions; constructing and deconstructing data structures recursively; basic data structures like atoms, cons, lists; examples of map, reduce, and tail call optimization; abstraction of iteration; working with tree structures; homoiconicity of Lisp code; macros; and bottom-up programming approach.
Random Indexing
The document discusses the concept of random indexing as a method for representing words as vectors in a high-dimensional space to capture their meanings based on their contexts of use. It notes that random indexing maps each word to a sparse random index vector, allowing words with similar meanings to be clustered closer together in the vector space. This distributional representation of words addresses issues like synonyms and polysemy by representing the latent semantic meaning behind words. The method is also described as being computationally efficient and easily parallelizable.
Deep learning
Deep learning involves using deep neural networks with many layers to learn hierarchical representations of data. [1] Deep networks are better able to learn complex patterns than shallow networks. [2] Advances in computing power and algorithms like pre-training and contrastive divergence have enabled training very deep networks. [3] Deep learning is achieving state-of-the-art results in areas like computer vision, speech recognition, and natural language processing.
The time is out of joint: O cursed spite, / That ever I was born to set it ri...
The document discusses concepts related to time, concurrency, and functional programming. It explores ideas such as multiple intersecting timelines representing concurrency, action occurring sequentially while perception is parallel, and functional reactive programming involving inversion of control. Various concurrency models like shared-isolated, asynchronous, synchronous, coordinated, and autonomous are also mentioned.
Generic functions in TurboGears
This document discusses generic functions, which allow functions to be selected based on the context or type of arguments passed. It provides examples of using generic functions in TurboGears to make frameworks more extensible and data-driven. Finally, it discusses design considerations for generic functions like limiting introspection and avoiding cryptic errors.
Viewers also liked (20)
Umetna inteligenca in kaj se lahko naučimo od narave
Umetna inteligenca in kaj se lahko naučimo od narave
The time is out of joint: O cursed spite, / That ever I was born to set it ri...
The time is out of joint: O cursed spite, / That ever I was born to set it ri...
More from Simon Belak
Tools for building the future
The document discusses tools for building the future and their impact. It notes that the speed of iteration matters and that countless hours are lost building administrative interfaces and integrations. It advocates building using a library of standardized reusable components and learning from blockchains about openness and lowering friction. Trends to watch include no-code, augmenting human intelligence with AI, and API-first and systems-level thinking.
Doing data science with clojure
Having programmers do data science is terrible, if only everyone else were not even worse. The problem is of course tools. We seem to have settled on either: a bunch of disparate libraries thrown into a more or less agnostic IDE, or some point-and-click wonder which no matter how glossy, never seems to truly fit our domain once we get down to it. The dual lisp tradition of grow-your-own-language and grow-your-own-editor gives me hope there is a third way.
This presentation is a meditation on how I approach data problems with Clojure, what I believe the process of doing data science should look like and the tools needed to get there. Some already exist (or can at least be bodged together); others can be made with relative ease (and we are already working on some of these); but a few will take a lot more hammock time.
Clojure is fantastic for data manipulation and rapid prototyping, but falls short when it comes to communicating your insights. What is lacking are good visualization libraries and (shareable) notebook-like environments. I'll show my workflow in org-babel which weaves Clojure with R (for ggplot) and Python (for scikit-learn) and tell you why it's wrong, how IPythons of the world have trapped us in a local maximum and how we need a reconceptualization similar to what a REPL does to programming. All this interposed with my experience doing data science with Clojure (everything from ETL to on-the-spot analysis during a brainstorming).
Exploratory analysis
The document discusses tools for data analysis and building intelligence including Metabase, an open source business intelligence tool used by over 21,000 companies daily. It focuses on speeding up the time it takes to answer questions from data through automation and building a "data scientist in a box". The goal is to answer 80% of questions from data in under 20 minutes to facilitate real-time exploration and problem solving.
Levelling up your data infrastructure
The document provides guidance on leveling up a company's data infrastructure and analytics capabilities. It recommends starting by acquiring and storing data from various sources in a data warehouse. The data should then be transformed into a usable shape before performing analytics. When setting up the infrastructure, the document emphasizes collecting user requirements, designing the data warehouse around key data aspects, and choosing technology that supports iteration, extensibility and prevents data loss. It also provides tips for creating effective dashboards and exploratory analysis. Examples of implementing this approach for two sample companies, MESI and SalesGenomics, are discussed.
The subtle art of recommendation
Recommendation algorithms and their variations such as ranking are the most common way for machine learning to find its way into a product where it is not the main focus. In this talk we’ll dig into the subtleties of making recommendation algorithms a seamless and integral part of your UX (goal: it should completely fade into the background. The user should not be aware she’s interacting with any kind of machine learning, it should just feel right, perhaps smart or even a tad like cheating); how to solve the cold start problem (and having little training data in general); and how to effectively collect feedback data. I’ll be drawing from my experiences building Metabase, an open source analytics/BI tool, where we extensively use recommendations and ranking to keep users in a state of flow when exploring data; to help with discoverability; and as a way to gently teach analysis and visualization best practices; all on the way towards building an AI data scientist.
Metabase Ljubljana Meetup #2
This document summarizes Metabase, an open source business intelligence and analytics tool that runs on-premise and is data-agnostic. Metabase is used by over 13,000 companies daily, including Go-Jek which has 4,000 daily active users. Some common use cases for Metabase include exploratory analysis, product development, product analytics, support, customer success, BI dashboarding, and marketing. The document also discusses how Metabase can be used for data-driven product development, such as segmenting users by usage and analyzing feature usage.
Metabase lj meetup
Things to consider when setting up your ETL pipeline, data warehouse, and choosing an analytics tool.
Sketch algorithms
In this talk we will look at how to efficiently (in both space and time) summarize large, potentially unbounded, streams of data by approximating the underlying distribution using so-called sketch algorithms. The main approach we are going to be looking at is summarization via histograms. Histograms have a number of desirable properties: they work well in an on-line setting, are embarrassingly parallel, and are space-bound. Not to mention they capture the entire (empirical) distribution which is something that otherwise often gets lost when doing descriptive statistics. Building from that we will delve into related problems of sampling in a stream setting, and updating in a batch setting; and highlight some cool tricks such as capturing time-dynamics via data snapshotting. To finish off we will touch upon algorithms to summarize categorical data, most notably count-min sketch.
Transducing for fun and profit
Transducers -- composable algorithmic transformation decoupled from input or output sources -- are Clojure’s take on data transformation. In this talk we will look at what makes a transducer; push their composability to the limit chasing the panacea of building complex single-pass transformations out of reusable components (eg. calculating a bunch of descriptive statistics like sum, sum of squares, mean, variance, ... in a single pass without resorting to a spaghetti ball fold); explore how the fact they are decoupled from input and output traversal opens up some interesting possibilities as they can be made to work in both online and batch settings; all drawing from practical examples of using Clojure to analize “awkward-size” data.
Your metrics are wrong
Your metrics are wrong according to the document. The document provides reasons why metrics may be wrong and recommendations on how to improve them. Specifically, it recommends thinking in terms of distributions and segmentation rather than aggregates, understanding that populations are dynamic rather than static, determining what is signal versus noise, considering reference points and reproducibility, and documenting metric definitions.
Writing smart contracts the sane way
Writing correct smart contract is hard (a recent study estimated that 3% of Ethereum contracts in the wild have some sort of security vulnerability; we all know of the DAO and Parity exploits, …). There are two main reasons for this. First and foremost developing for the blockchain is quite different than what most programmers are used to. The level of concurrency is far beyond our (von Neumann) intuition and mental models. And you can’t stop and inspect running code like you can in other systems. Taken together blockchain is closer to a physical/living system than conventional software — a fact not reflected in the tools available. Compared to other domains our tooling and programming languages are somewhere between rudimentary and bad; and a far cry from where they would need to be to augment developers and help make programming for the blockchain less alien and less error prone. In this talk we will first unpack what makes programming for the blockchain hard, and what are the most common types of vulnerabilities and their causes. Then we will look at the state of art programming language research in correctness proving and programming massively concurrent systems; and how these can be applied to programming smart contracts; revisit some technologies from the past that didn’t get traction at the time, but are nevertheless worth studying; and finishing off by trying to imagine how programming for the blockchain should, and perhaps one day will, look like.
Online statistical analysis using transducers and sketch algorithms
Online statistical analysis using transducers and sketch algorithms. Don’t know what either is? You are going to learn something very cool (and perspective-changing) then. Know them, but want an experience report? Got you covered, fam.
Save the princess
OpenAI recently published a fun paper where they showed using evolution algorithms to train policy networks to perform on par with state of the art reinforcement deep learning. In this talk we’ll try to reimplement the main ideas in that paper using Neanderthal (blazing fast matrix and linear algebra computations) and Cortex (neural networks); make it massively distributed using Onyx; build a simulation environment using re-frame; and of course save our princess from no particular harm in our toy game example
Data driven going to market strategy
How to systematically open a new market where every step is supported by data, how to set up learning loops, and where to look for optimization opportunities.
Spec: a lisp-flavoured type system
You can do cool and unexpected things if your entire type system is a first class citizen and accessible at runtime.
With the introduction of spec, Clojure got its own distinct spin on a type system. Just as macros add another -time (runtime and compile time) where the full power of the language can be used, spec does to describing data.
The result is an entire additional type system that is a first class citizen and accessible at runtime that facilitates validation, generative testing (a la QuickCheck), destructuring (pattern matching into deeply nested data), data macros (recursive transformations of data) and a pluginable error system. And then you can start building on top of it.
The talk will be half introduction to spec and the ideas packed within it, and half experience report instrumenting 15k loc production codebase (primarily ETL and analytics) with spec.
A data layer in clojure
Clojure has always been good at manipulating data. With the release of spec and Onyx (“a masterless, cloud scale, fault tolerant, high performance distributed computation system”) good became best. In this talk you will learn about a streaming data layer architecture build around Kafka and Onyx that is self-describing, declarative, scalable and convenient to work with for the end user. The focus will be on the power and elegance of describing data and computation with data; the inferences and automations that can be built on top of that; and how and why Clojure is a natural choice for tasks that involve a lot of data manipulation, touching both on functional programming and lisp-specifics such as code-is-data.
We will look at how such an approach can be used to manage a data warehouse by automatically inferring materialized views from raw incoming data or other views based on a combination of heuristics, statistical analysis (seasonality, outlier removal, ...) and predefined ontologies. Doing so is a practical way to maintain a large number of views, increasing their availability and abstracting the complexity into declarative rules, rather than having an ETL pipeline with dozens or even hundreds of hand crafted tasks.
The system described requires relatively little effort upfront but can easily grow with one's needs both in terms of scale as well as scope. With its good introspection capabilities and strong decoupling it is for instance an excellent substrate for putting machine learning algorithms in production, which is the final use-case we will dive into.
Odkrivanje segmentov iz podatkov
Segmentacija je ključna za učinkovito nagovarjanje in konvertiranje potancialnih strank. Simon Belak, vodja analitike pri GoOptiju in transmedijski urednik pri kritičnem časopisu Tribuna, je razkril, kako odkrivati segmente iz podatkov.
Po njegovih besedah je povsem neupravičeno, da je segmentacija povečini statična in narejena na slepo, neupoštevajoč podatke. V predavanju je predstavil aletrnativo: analitično delno avtomatično odkrivanje segmentov iz podatkov.
Na konkretnih primerih je pokazal, kako preslikati podatke o interakcijah s strankami (obisk strani kot pokazatelji interesov, odgovori na ankete, vzorci premikanja po straneh, odpiranje emailov…) v model strank in nadaljeval z razdelitvijo v segmente. Simon je za konec izpostavil najpogostejše pasti in drobne trike za primere, ko imamo malo podatkov, ali so le-ti nejasni.
Using Onyx in anger
@sbelak
Simon Belak
Using Onyx in anger
Clojure has always been good at manipulating data. With the release of spec and Onyx ("masterless, cloud scale, fault tolerant, high performance distributed computation system") good became best. In this talk I will walk you through a data layer architecture build around Kafka an Onyx that is self-describing, declarative, scalable and convenient to work with for the end user. The focus will be on the power and elegance of describing data and computation with data; and the inferences and automations that can be built on top of that.
Spec + onyx
Clojure has always been good at manipulating data. With the release of spec and Onyx (“a masterless, cloud scale, fault tolerant, high performance distributed computation system”) good became best. In this talk you will learn about a data layer architecture build around Kafka and Onyx that is self-describing, declarative, scalable and convenient to work with for the end user. The focus will be on the power and elegance of describing data and computation with data; and the inferences and automations that can be built on top of that.
Dao of lisp
Whenever a programming language comes out with a new feature, us smug lisp weenies shrug and point out how lisp had that in the early seventies; and if you look at the list of influences of a given language, there is bound to be a lisp in there. In this talk I will try to unpack what makes lisp special, why it is called programming programming language , how it changes one’s thinking, and how that thinking can be applied elsewhere.
More from Simon Belak (20)
Online statistical analysis using transducers and sketch algorithms
Online statistical analysis using transducers and sketch algorithms
Recently uploaded
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Project Management Semester Long Project - Acuity
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Recently uploaded (20)
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Integrating the compiler with unit testing
- 1. Integrating the compiler with unit testing [email_address]
- 2. Programming should be about ideas not implementation!
- 4. Compiler as a part of the language
- 6. Separating ideas and the nitty-gritty
- 8. Let the robots do it
- 9. Problem: provably correct optimizations are hard
- 12. Evolution?