Rubyslava debugging with_pry
•
0 likes•452 views
This document discusses using the Pry debugging tool for Ruby programs. Pry allows inserting binding.pry commands in code to drop into a REPL session and debug. It has commands like ls, cd, edit and breakpoint to examine state and set breakpoints. Demos show using Pry to debug tests and controller actions. Pry integrates with Rails and has plugins like pry-rescue and prymounth. Resources listed provide more information on using Pry.
Report
Share
Report
Share
Download to read offline
Recommended
Test Motherfucker...Test
This document discusses different types of software testing for a Grails application. It begins by introducing integration testing and explaining that integration tests should be done first because they test important services. It then discusses what to test with integration tests like database, web services, and queue integration. The document also discusses Grails integration testing tools like interactive mode and the Guard plugin. It also discusses unit testing controllers and services using mocking. Finally, it briefly introduces functional testing using plugins like Geb and testing JavaScript functionality.
Cucumber integration tests alireza zare
Alireza Zare discusses using Cucumber integration tests to address issues with outdated documentation, complex workflows, and reproducing problems when upgrading Liferay. Cucumber tests provide benefits like being easy to set up, using natural language, bridging communication gaps between teams, serving as documentation, and reusing steps. Zare demonstrates Cucumber tests and invites questions.
TDD super mondays-june-2014
This document provides an overview of test-driven development (TDD) and discusses:
- The key steps of TDD including writing a test, seeing it fail, writing code to pass the test, and refactoring.
- Popular Python testing tools like unittest, nose, pytest, and sure that can be used for TDD.
- How TDD is applied to JavaScript/CoffeeScript using frameworks like Mocha, Should.js, and Expect.js.
- The benefits of TDD including early detection of errors, improved design, and serving as documentation for code changes.
Can you TDD Rails?
The document discusses how test-driven development (TDD) can help address common fears and issues developers experience when working with existing or new code. It argues that while TDD may seem difficult with Rails, the challenges are likely due more to issues with the code structure rather than limitations of TDD or Rails. The document differentiates between hard skills related to TDD tools and techniques versus softer skills around understanding requirements, isolating business logic, continuous delivery, and refactoring tests. It provides suggestions for improving TDD skills like practicing with code katas, extracting business logic into gems, and doing "domain spikes" with in-memory objects to focus on logic alone.
team++
The document summarizes the practices of the BBC Homepage development team to continuously improve their work. Some key practices include continuous peer review of all code changes before being committed, writing tests to prevent breaking existing functionality, and performing pair programming where appropriate. The team also emphasizes maintaining standards, not working outside of hours, and socializing to enhance collaboration and enjoyment of the work.
openQA Hoverboard - Open-source Question Answering Framework
This document provides an overview of openQA, an open-source question answering framework. It discusses what openQA is, when it should and should not be used, its history and development over time including versions and addressed problems. The document also addresses myths about openQA and describes its hoverboard architecture, features, and plans for future improvements.
Java EE 7 meets Java 8
The last few years have been pretty exciting for Java with new versions of EE and SE platforms. Java EE, introduced a new API to build WebSockets; a new API to parse, process and generate JSON; a new Client API in JAX-RS to invoke REST services, and finally the Batch Processing API to build batch applications. Java SE brought us the long awaited Lambda expressions; the powerful Streams API to perform operations like filtering, mapping or sorting in a very easy and fluent way, and a brand new Date Time API, to deal with the complexities of Timezones and Periods. This session will combine all of these elements together and show you how to easily develop an application using Java SE 8 with Java EE 7, with live coding and samples.
This session will explore the usage of the new Java 8 API's, combined with some of the new and existing features of Java EE. It will mostly be a live coding session where I plan to combine Java 8 Lambdas, Streams and DateTime API's with JPA, CDI, REST, Websockets and Batch.
The interesting thing about this session is about how to adjust your coding style and learn where you can use all these awesome Java 8 feature when developing a standard Enterprise application.
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at QCon NYC 2017
As in a good Greek Tragedy, scaling devops to big teams has 3 stages and usually end badly. In this play (it’s more than a talk!) we’ll present you with Pentagon Inc, and their way to scaling devops from a team of 3 engineers to a team of 100 (spoiler – it’s painful!)
Recommended
Test Motherfucker...Test
This document discusses different types of software testing for a Grails application. It begins by introducing integration testing and explaining that integration tests should be done first because they test important services. It then discusses what to test with integration tests like database, web services, and queue integration. The document also discusses Grails integration testing tools like interactive mode and the Guard plugin. It also discusses unit testing controllers and services using mocking. Finally, it briefly introduces functional testing using plugins like Geb and testing JavaScript functionality.
Cucumber integration tests alireza zare
Alireza Zare discusses using Cucumber integration tests to address issues with outdated documentation, complex workflows, and reproducing problems when upgrading Liferay. Cucumber tests provide benefits like being easy to set up, using natural language, bridging communication gaps between teams, serving as documentation, and reusing steps. Zare demonstrates Cucumber tests and invites questions.
TDD super mondays-june-2014
This document provides an overview of test-driven development (TDD) and discusses:
- The key steps of TDD including writing a test, seeing it fail, writing code to pass the test, and refactoring.
- Popular Python testing tools like unittest, nose, pytest, and sure that can be used for TDD.
- How TDD is applied to JavaScript/CoffeeScript using frameworks like Mocha, Should.js, and Expect.js.
- The benefits of TDD including early detection of errors, improved design, and serving as documentation for code changes.
Can you TDD Rails?
The document discusses how test-driven development (TDD) can help address common fears and issues developers experience when working with existing or new code. It argues that while TDD may seem difficult with Rails, the challenges are likely due more to issues with the code structure rather than limitations of TDD or Rails. The document differentiates between hard skills related to TDD tools and techniques versus softer skills around understanding requirements, isolating business logic, continuous delivery, and refactoring tests. It provides suggestions for improving TDD skills like practicing with code katas, extracting business logic into gems, and doing "domain spikes" with in-memory objects to focus on logic alone.
team++
The document summarizes the practices of the BBC Homepage development team to continuously improve their work. Some key practices include continuous peer review of all code changes before being committed, writing tests to prevent breaking existing functionality, and performing pair programming where appropriate. The team also emphasizes maintaining standards, not working outside of hours, and socializing to enhance collaboration and enjoyment of the work.
openQA Hoverboard - Open-source Question Answering Framework
This document provides an overview of openQA, an open-source question answering framework. It discusses what openQA is, when it should and should not be used, its history and development over time including versions and addressed problems. The document also addresses myths about openQA and describes its hoverboard architecture, features, and plans for future improvements.
Java EE 7 meets Java 8
The last few years have been pretty exciting for Java with new versions of EE and SE platforms. Java EE, introduced a new API to build WebSockets; a new API to parse, process and generate JSON; a new Client API in JAX-RS to invoke REST services, and finally the Batch Processing API to build batch applications. Java SE brought us the long awaited Lambda expressions; the powerful Streams API to perform operations like filtering, mapping or sorting in a very easy and fluent way, and a brand new Date Time API, to deal with the complexities of Timezones and Periods. This session will combine all of these elements together and show you how to easily develop an application using Java SE 8 with Java EE 7, with live coding and samples.
This session will explore the usage of the new Java 8 API's, combined with some of the new and existing features of Java EE. It will mostly be a live coding session where I plan to combine Java 8 Lambdas, Streams and DateTime API's with JPA, CDI, REST, Websockets and Batch.
The interesting thing about this session is about how to adjust your coding style and learn where you can use all these awesome Java 8 feature when developing a standard Enterprise application.
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at QCon NYC 2017
As in a good Greek Tragedy, scaling devops to big teams has 3 stages and usually end badly. In this play (it’s more than a talk!) we’ll present you with Pentagon Inc, and their way to scaling devops from a team of 3 engineers to a team of 100 (spoiler – it’s painful!)
team++; making your team work better together
As presented at London Web Standards, on Monday 14th November 2011.
This talk isn't brain science.
Some teams are better than others. Some get more done, some have more bugs. What they all can be though, is better. In this session, Neil Crosby witters on about some of the things that he's done to help create a better functioning team.
Bsu on rails_testing
The document discusses testing in Ruby. It covers different types of testing like functional, security, and performance testing. It discusses the benefits and drawbacks of manual testing versus automated testing. The document recommends taking the best of both worlds by using automation for critical parts of an application and letting users test other parts. It also provides an overview of popular Ruby testing tools like Minitest, Rspec, Cucumber, and Capybara. It discusses testing techniques like test-driven development (TDD), stubs, mocks, and behavior-driven development (BDD) with Cucumber.
WTF TDD?
The document discusses the history and benefits of test-driven development (TDD). It notes that practices like agile development, extreme programming, and open source helped popularize TDD. TDD emphasizes writing tests before code, continuous integration, refactoring, loose coupling, and testing all new code. The document acknowledges research showing TDD may take longer initially but finds fewer bugs. It provides examples of Ruby testing tools and frameworks that facilitate TDD. The overall message is that the software development community now widely accepts and uses TDD.
Testing Pyramid
My talk is up: https://vimeo.com/179151225
Testing is not Dead => Confidently shipping to production
Presented at Sydney Cococaheads, July 2016
1. Type Safety
2. Unit Tests
3. Snapshot
4. Stubbed UI Test
5. Integration Test
6. AAA Shakedown
7. Dogfood
8. Blitz
Building a PWA with Ionic, Angular and Spring Boot - Jfokus 2017
This document discusses building progressive web apps. It introduces Matt Raible and his background working with web frameworks like Spring Boot. It then covers the PRPL pattern for progressive web apps, which involves pushing critical resources, rendering, pre-caching remaining routes, and lazy-loading routes. It also discusses using tools like Lighthouse and Chrome DevTools for testing mobile performance. The rest covers a demo of creating a beer API and UI using Stormpath and deploying it to iOS, as well as resources for learning Ionic and staying in touch with Matt Raible.
Lrug
The document discusses the convergence of system administrators and developers as programming has become more integral to system administration work. It notes that system administrators now write code using languages like Ruby, Python, and Bash just as developers do. It argues that system administrators who do not program have become merely domain experts. The document also discusses challenges around sharing system administration tools and modules, as well as testing infrastructure using approaches from software development like Cucumber testing.
Patterns and antipatterns in Docker image lifecycle as was presented at Globa...
While Docker has enabled an unprecedented velocity of software production, it is all too easy to spin out of control. A promotion-based model is required to control and track the flow of Docker images as much as it is required for a traditional software development lifecycle. New tools often introduce new paradigms. We will examine the patterns and the antipatterns for Docker image management, and what impact the new tools have on the battle-proven paradigms of the software development lifecycle.
Patterns and antipatterns in Docker image lifecycle as was presented at Scale...
This slide presentation discusses using Docker containers and JFrog Artifactory for continuous delivery of applications. It addresses how to set up repositories in Artifactory to support different environments like development, testing, staging and production. It also discusses using a layered approach to container builds, with shared base images, to optimize builds and promote containers through the different environments. The presentation emphasizes the need for automation, speed and quality controls when using containers in a continuous delivery pipeline.
Keeping your users happy with testable apps - Greg Shackles
This document contains notes from a presentation on keeping apps testable. It discusses the importance of testing for stability and the ability to refactor. Tests should cover important parts of the code's value rather than seeking full coverage. Both unit/integration and UI tests are important, though unit tests are more automated and have lower friction. Manual testing is also critical for user feedback. MVVM is recommended for shared, testable view models and thin views.
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at DevOps Detroit...
As in a good Greek Tragedy, scaling devops to big teams has 3 stages and usually end badly. In this play (it’s more than a talk!) we’ll present you with Pentagon Inc, and their way to scaling devops from a team of 3 engineers to a team of 100 (spoiler – it’s painful!)
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at Devoxx 2017
As in a good Greek Tragedy, scaling devops to big teams has 3 stages and usually end badly. In this play (it’s more than a talk!) we’ll present you with Pentagon Inc, and their way to scaling devops from a team of 3 engineers to a team of 100 (spoiler – it’s painful!)
Test Driven Development on Android (Kotlin Kenya)
This document discusses test-driven development (TDD) and its application to Android development. It begins with an introduction to TDD, outlining its core principles and benefits. It describes the "red, green, refactor" process and emphasizes writing tests before code. It addresses challenges with testing Android code, such as dependencies on framework classes, and recommends strategies like wrapping classes to isolate dependencies. Finally, it outlines the benefits of TDD such as reduced bugs, improved design, and increased productivity over the long run despite initial slower development.
TDD on android. Why and How? (Coding Serbia 2019)
The document discusses test-driven development (TDD) on Android. It covers:
- The history and principles of TDD, including writing failing tests first and then only producing code to pass those tests.
- How TDD works in practice using the "red-green-refactor" process of writing a failing test, passing code, then refactoring.
- Benefits of TDD like fewer bugs, easier refactoring, and faster long-term development.
- Considerations for testing Android code, such as using mockable classes and avoiding direct testing of activities/fragments.
Chaos Engineering Talk at DevOps Days Austin
Chaos engineering is the discipline of experimenting on a distributed system to build confidence in how it withstands turbulent conditions in production. It involves intentionally introducing failures or unpredictable conditions to test a system's resilience. Some key aspects of chaos engineering include starting with questions about possible failure cases, having tools and means to test ideas and measure outcomes, ensuring observability of experiments, learning from results, and conducting dedicated "game days" with teams. The overall goal is to amplify feedback and continually learn and improve a system's reliability through principled experimentation.
Joel Arvidsson, Klarna. What You See is What You Get – a case for visual testing
Experienced software engineer, currently working mainly in JavaScript and React Native. Passionate about open source and building delightful mobile experiences
Speech Overview:
Components are commonly tested with snapshots of the rendered DOM. While it’s beneficial when working with untested legacy systems, often it’s a high noise and high maintenance approach that easily lets regressions slip by. It’s now considered bad practice having it as the single testing strategy.
Loki is a visual testing tool that has similar benefits as snapshot testing in that it’s quick and easy to get started, but fewer of the downsides – refactors are not flagged as regressions and discerning desirable from unintended changes is much easier. Last year it gained a place in the ThoughtWorks Tech Radar and has since matured to support advanced use cases with massive parallelization using lambdas.
The talk outlines successful strategies for visual testing in general, pitfalls to avoid and how to get started in under a minute
PSPDFKit on Android
This document discusses lessons learned in creating an Android library. It recommends keeping sanity during development through continuous integration, static analysis, and testing. It also recommends making the library fast by avoiding the main thread, using RxJava, and custom views. Additionally, it suggests avoiding duplicated code by sharing business logic between platforms using a common C++ layer and bridging interfaces. Finally, it acknowledges the insanity of different OEM implementations.
Hacking on gems
This document provides instructions for contributing to Ruby gems hosted on GitHub. It outlines steps such as forking the gem's repository, making changes on a new branch, running tests, and submitting a pull request with a descriptive message to the gem maintainer. If the pull request is accepted, the new version of the gem will be published for others to benefit from the contribution. The overall process emphasizes making improvements through the open source community rather than maintaining private forks.
'IS THERE JAVASCRIPT ON SWAGGER PLUGINS?' by Dmytro Gusev
This document discusses JavaScript plugins for the Swagger API documentation framework. It begins with an overview of Swagger and related tools like swagger-editor. It then covers challenges with customizing Swagger and different approaches tried, like using custom Swagger definitions or closures. The main topics covered are the plugin system architecture, including available React components, Redux state management, and plugin APIs. It asks several questions about how to interact with and extend the plugin system.
Burp better - Finding Struts and XXE Vulns with Burp Extensions
DerbyCon 2017 Stable Talk about finding Struts (and other vulnerabilities) with Burp extensions. Full talk available on YouTube: https://www.youtube.com/watch?v=DSJW8_VzElI
Solving Cross-Cutting Concerns in PHP - DutchPHP Conference 2016
Talk about solving cross-cutting concerns in PHP at DutchPHP Conference.
Discussed questions:
1) OOP features and limitations
2) OOP patterns for solving cross-cutting concerns
3) Aspect-Oriented approach for solving cross-cutting concerns
4) Examples of using AOP for real life application
Are Automated Debugging Techniques Actually Helping Programmers
Automated debugging tools may help expert programmers but not others. A study of 34 programmers debugging two programs found:
1) Programmers did not follow ranked lists linearly but jumped around and zig-zagged.
2) When finding the bug, only 1 in 10 stopped investigating while others spent 10 extra minutes.
3) Overall, automated tools did not speed up debugging except for expert programmers who were 5 minutes faster.
4) Developers wanted explanations, not just recommendations from tools. More studies are needed on how programmers use tools.
Debugging Rails 3 Applications
This document summarizes various debugging techniques for Ruby on Rails applications. It discusses using the debugger, awesome_print and Pry gems to debug Ruby code. It also covers using the better_errors and Errbit gems to debug Rails errors and exceptions. The document provides an overview of debugging JavaScript using the Chrome developer tools console. It also discusses using git blame and git bisect to help debug code changes that may have introduced bugs.
More Related Content
What's hot
team++; making your team work better together
As presented at London Web Standards, on Monday 14th November 2011.
This talk isn't brain science.
Some teams are better than others. Some get more done, some have more bugs. What they all can be though, is better. In this session, Neil Crosby witters on about some of the things that he's done to help create a better functioning team.
Bsu on rails_testing
The document discusses testing in Ruby. It covers different types of testing like functional, security, and performance testing. It discusses the benefits and drawbacks of manual testing versus automated testing. The document recommends taking the best of both worlds by using automation for critical parts of an application and letting users test other parts. It also provides an overview of popular Ruby testing tools like Minitest, Rspec, Cucumber, and Capybara. It discusses testing techniques like test-driven development (TDD), stubs, mocks, and behavior-driven development (BDD) with Cucumber.
WTF TDD?
The document discusses the history and benefits of test-driven development (TDD). It notes that practices like agile development, extreme programming, and open source helped popularize TDD. TDD emphasizes writing tests before code, continuous integration, refactoring, loose coupling, and testing all new code. The document acknowledges research showing TDD may take longer initially but finds fewer bugs. It provides examples of Ruby testing tools and frameworks that facilitate TDD. The overall message is that the software development community now widely accepts and uses TDD.
Testing Pyramid
My talk is up: https://vimeo.com/179151225
Testing is not Dead => Confidently shipping to production
Presented at Sydney Cococaheads, July 2016
1. Type Safety
2. Unit Tests
3. Snapshot
4. Stubbed UI Test
5. Integration Test
6. AAA Shakedown
7. Dogfood
8. Blitz
Building a PWA with Ionic, Angular and Spring Boot - Jfokus 2017
This document discusses building progressive web apps. It introduces Matt Raible and his background working with web frameworks like Spring Boot. It then covers the PRPL pattern for progressive web apps, which involves pushing critical resources, rendering, pre-caching remaining routes, and lazy-loading routes. It also discusses using tools like Lighthouse and Chrome DevTools for testing mobile performance. The rest covers a demo of creating a beer API and UI using Stormpath and deploying it to iOS, as well as resources for learning Ionic and staying in touch with Matt Raible.
Lrug
The document discusses the convergence of system administrators and developers as programming has become more integral to system administration work. It notes that system administrators now write code using languages like Ruby, Python, and Bash just as developers do. It argues that system administrators who do not program have become merely domain experts. The document also discusses challenges around sharing system administration tools and modules, as well as testing infrastructure using approaches from software development like Cucumber testing.
Patterns and antipatterns in Docker image lifecycle as was presented at Globa...
While Docker has enabled an unprecedented velocity of software production, it is all too easy to spin out of control. A promotion-based model is required to control and track the flow of Docker images as much as it is required for a traditional software development lifecycle. New tools often introduce new paradigms. We will examine the patterns and the antipatterns for Docker image management, and what impact the new tools have on the battle-proven paradigms of the software development lifecycle.
Patterns and antipatterns in Docker image lifecycle as was presented at Scale...
This slide presentation discusses using Docker containers and JFrog Artifactory for continuous delivery of applications. It addresses how to set up repositories in Artifactory to support different environments like development, testing, staging and production. It also discusses using a layered approach to container builds, with shared base images, to optimize builds and promote containers through the different environments. The presentation emphasizes the need for automation, speed and quality controls when using containers in a continuous delivery pipeline.
Keeping your users happy with testable apps - Greg Shackles
This document contains notes from a presentation on keeping apps testable. It discusses the importance of testing for stability and the ability to refactor. Tests should cover important parts of the code's value rather than seeking full coverage. Both unit/integration and UI tests are important, though unit tests are more automated and have lower friction. Manual testing is also critical for user feedback. MVVM is recommended for shared, testable view models and thin views.
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at DevOps Detroit...
As in a good Greek Tragedy, scaling devops to big teams has 3 stages and usually end badly. In this play (it’s more than a talk!) we’ll present you with Pentagon Inc, and their way to scaling devops from a team of 3 engineers to a team of 100 (spoiler – it’s painful!)
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at Devoxx 2017
As in a good Greek Tragedy, scaling devops to big teams has 3 stages and usually end badly. In this play (it’s more than a talk!) we’ll present you with Pentagon Inc, and their way to scaling devops from a team of 3 engineers to a team of 100 (spoiler – it’s painful!)
Test Driven Development on Android (Kotlin Kenya)
This document discusses test-driven development (TDD) and its application to Android development. It begins with an introduction to TDD, outlining its core principles and benefits. It describes the "red, green, refactor" process and emphasizes writing tests before code. It addresses challenges with testing Android code, such as dependencies on framework classes, and recommends strategies like wrapping classes to isolate dependencies. Finally, it outlines the benefits of TDD such as reduced bugs, improved design, and increased productivity over the long run despite initial slower development.
TDD on android. Why and How? (Coding Serbia 2019)
The document discusses test-driven development (TDD) on Android. It covers:
- The history and principles of TDD, including writing failing tests first and then only producing code to pass those tests.
- How TDD works in practice using the "red-green-refactor" process of writing a failing test, passing code, then refactoring.
- Benefits of TDD like fewer bugs, easier refactoring, and faster long-term development.
- Considerations for testing Android code, such as using mockable classes and avoiding direct testing of activities/fragments.
Chaos Engineering Talk at DevOps Days Austin
Chaos engineering is the discipline of experimenting on a distributed system to build confidence in how it withstands turbulent conditions in production. It involves intentionally introducing failures or unpredictable conditions to test a system's resilience. Some key aspects of chaos engineering include starting with questions about possible failure cases, having tools and means to test ideas and measure outcomes, ensuring observability of experiments, learning from results, and conducting dedicated "game days" with teams. The overall goal is to amplify feedback and continually learn and improve a system's reliability through principled experimentation.
Joel Arvidsson, Klarna. What You See is What You Get – a case for visual testing
Experienced software engineer, currently working mainly in JavaScript and React Native. Passionate about open source and building delightful mobile experiences
Speech Overview:
Components are commonly tested with snapshots of the rendered DOM. While it’s beneficial when working with untested legacy systems, often it’s a high noise and high maintenance approach that easily lets regressions slip by. It’s now considered bad practice having it as the single testing strategy.
Loki is a visual testing tool that has similar benefits as snapshot testing in that it’s quick and easy to get started, but fewer of the downsides – refactors are not flagged as regressions and discerning desirable from unintended changes is much easier. Last year it gained a place in the ThoughtWorks Tech Radar and has since matured to support advanced use cases with massive parallelization using lambdas.
The talk outlines successful strategies for visual testing in general, pitfalls to avoid and how to get started in under a minute
PSPDFKit on Android
This document discusses lessons learned in creating an Android library. It recommends keeping sanity during development through continuous integration, static analysis, and testing. It also recommends making the library fast by avoiding the main thread, using RxJava, and custom views. Additionally, it suggests avoiding duplicated code by sharing business logic between platforms using a common C++ layer and bridging interfaces. Finally, it acknowledges the insanity of different OEM implementations.
Hacking on gems
This document provides instructions for contributing to Ruby gems hosted on GitHub. It outlines steps such as forking the gem's repository, making changes on a new branch, running tests, and submitting a pull request with a descriptive message to the gem maintainer. If the pull request is accepted, the new version of the gem will be published for others to benefit from the contribution. The overall process emphasizes making improvements through the open source community rather than maintaining private forks.
'IS THERE JAVASCRIPT ON SWAGGER PLUGINS?' by Dmytro Gusev
This document discusses JavaScript plugins for the Swagger API documentation framework. It begins with an overview of Swagger and related tools like swagger-editor. It then covers challenges with customizing Swagger and different approaches tried, like using custom Swagger definitions or closures. The main topics covered are the plugin system architecture, including available React components, Redux state management, and plugin APIs. It asks several questions about how to interact with and extend the plugin system.
Burp better - Finding Struts and XXE Vulns with Burp Extensions
DerbyCon 2017 Stable Talk about finding Struts (and other vulnerabilities) with Burp extensions. Full talk available on YouTube: https://www.youtube.com/watch?v=DSJW8_VzElI
Solving Cross-Cutting Concerns in PHP - DutchPHP Conference 2016
Talk about solving cross-cutting concerns in PHP at DutchPHP Conference.
Discussed questions:
1) OOP features and limitations
2) OOP patterns for solving cross-cutting concerns
3) Aspect-Oriented approach for solving cross-cutting concerns
4) Examples of using AOP for real life application
What's hot (20)
Building a PWA with Ionic, Angular and Spring Boot - Jfokus 2017
Building a PWA with Ionic, Angular and Spring Boot - Jfokus 2017
Patterns and antipatterns in Docker image lifecycle as was presented at Globa...
Patterns and antipatterns in Docker image lifecycle as was presented at Globa...
Patterns and antipatterns in Docker image lifecycle as was presented at Scale...
Patterns and antipatterns in Docker image lifecycle as was presented at Scale...
Keeping your users happy with testable apps - Greg Shackles
Keeping your users happy with testable apps - Greg Shackles
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at DevOps Detroit...
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at DevOps Detroit...
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at Devoxx 2017
DevOps @Scale (Greek Tragedy in 3 Acts) as it was presented at Devoxx 2017
Joel Arvidsson, Klarna. What You See is What You Get – a case for visual testing
Joel Arvidsson, Klarna. What You See is What You Get – a case for visual testing
'IS THERE JAVASCRIPT ON SWAGGER PLUGINS?' by Dmytro Gusev
'IS THERE JAVASCRIPT ON SWAGGER PLUGINS?' by Dmytro Gusev
Burp better - Finding Struts and XXE Vulns with Burp Extensions
Burp better - Finding Struts and XXE Vulns with Burp Extensions
Solving Cross-Cutting Concerns in PHP - DutchPHP Conference 2016
Solving Cross-Cutting Concerns in PHP - DutchPHP Conference 2016
Viewers also liked
Are Automated Debugging Techniques Actually Helping Programmers
Automated debugging tools may help expert programmers but not others. A study of 34 programmers debugging two programs found:
1) Programmers did not follow ranked lists linearly but jumped around and zig-zagged.
2) When finding the bug, only 1 in 10 stopped investigating while others spent 10 extra minutes.
3) Overall, automated tools did not speed up debugging except for expert programmers who were 5 minutes faster.
4) Developers wanted explanations, not just recommendations from tools. More studies are needed on how programmers use tools.
Debugging Rails 3 Applications
This document summarizes various debugging techniques for Ruby on Rails applications. It discusses using the debugger, awesome_print and Pry gems to debug Ruby code. It also covers using the better_errors and Errbit gems to debug Rails errors and exceptions. The document provides an overview of debugging JavaScript using the Chrome developer tools console. It also discusses using git blame and git bisect to help debug code changes that may have introduced bugs.
CDFA Annual VC Report for 2013
This document summarizes a report by the Council of Development Finance Agencies analyzing 2013 private activity bond and volume cap trends in the United States. Key findings include that total private activity bond issuance decreased to $8.8 billion while available volume cap increased to nearly $90 billion. Industrial development bond issuance increased slightly to $356 million issued across 27 states, with the top states being Pennsylvania, Massachusetts, and Michigan. Overall, states used only 10% of available volume cap in 2013.
Rubyslava beyond the_monolith
So, your monolith is getting out hand and you read about this cool microservice infrastructure thing. You may have done something similar, but are not quite sure whether to take the plunge or not.
Financing_Contamination_Remediation_FinalReport
This document discusses various financing mechanisms for addressing contaminated site remediation, including bond finance programs, loan fund programs, tax increment and special assessment finance programs, tax credit and incentive programs, and grant financing programs. Bond finance programs utilize governmental bonds or private activity bonds to fund remediation projects. Loan fund programs establish revolving loan funds to provide loans for remediation. Tax increment and special assessment programs use increased property taxes from redeveloped sites to fund cleanups. Tax credit and incentive programs provide tax breaks to encourage remediation. Grant programs directly award funds for assessment and cleanup of contaminated sites.
Debugging application using visual studio 2010 and intellitrace
When the unexpected happens, how do you figure out what went wrong and recover gracefully? We take a look at the debugging features and capabilities of the latest version of Visual Studio 2010. Where you can take advantage of the tools to simplify and streamline the complex job of debugging software.
Eb 14 15 application process
This document provides information about the application process for the Executive Board (EB) committee of AIESEC in SIM for the 2014-2015 term. It describes the roles and responsibilities of EB members in shaping members' experiences, leading the local committee, and being a source of support, guidance, and inspiration for members. The application process takes place from January 29th to February 27th and involves submitting a Letter of Intent, completing a general questionnaire, participating in an EB Candidate Development Day camp, shadowing current EB members, an interview, and multiple rounds of reviews to select new EB members for the following term.
Django debugging
This document provides an overview of different tools that can be used for debugging in Django:
1. Pdb is the Python debugger that allows setting breakpoints to inspect code and variables.
2. Django debug toolbar adds panels to request information like SQL queries and templates rendered.
3. Fire logger enables logging to the Firebug console in Firefox for JavaScript debugging.
4. Profile middleware captures profile data on view execution times and queries to help optimize performance.
(Pdf) yury chemerkin def_con_2013
This document provides an overview and agenda for dissecting the security of the Blackberry Z10 mobile device. It begins with a review of the Blackberry OS which is built on QNX. It then discusses gaining shell access, various approaches for analyzing the device such as fuzzing and exploiting system utilities, examining the firmware, analyzing the browser and application-level security. It also covers interacting with APIs and MDM capabilities. Metrics are provided on the efficiency of security features compared to other mobile platforms. The document aims to serve as a guide for further researching the Blackberry Z10.
AP_2015_AIESEC in SIM_AP Achievement Awards
This document summarizes the achievements of AIESEC in SIM in Asia Pacific in 2014-2015. It describes how they improved their recruitment process, shortening the time to match candidates from 1 month to 1 week through a sales development program. This increased participation at recruitment events and improved their conversion rate. Their innovation in directly matching candidates to partner projects upon contracting increased matches by 100% compared to the previous year. They were recognized with multiple awards from AIESEC Asia Pacific for their growth, collaboration, and innovation.
(Pdf) yury chemerkin _ath_con_2013
The document discusses differences in how integration features affect the security sandbox on BlackBerry devices. It notes that BlackBerry evaluates every application request to access device capabilities. However, malware boundaries can become unclear as BlackBerry handles technologies like native apps, third-party apps like Android and iOS, each with different controls through sandboxes, permissions, and device/MDM security features. Compliance standards also bring useless recommendations that are less extensive than mobile device management (MDM) features. The document outlines the various capabilities controlled on BlackBerry, Android, and iOS platforms and notes issues like useless solutions, GUI exploitation on older BlackBerry devices, and conclusions regarding oversimplified security controls through general permissions rather than concrete permissions.
Node.js debugging
Pittsburgh Node.js presentation explaining the different options available for Node.js across IDEs, command line, and node modules.
Debugging Debugging
Delta debugging is a technique for isolating the cause of failures in programs. It works by systematically removing parts of changes made between a version where the program worked and a version where it fails. The algorithm efficiently determines the minimal set of changes responsible for the failure. The technique was able to isolate a single change causing a failure in GDB from 178,000 changed lines within a few hours. Automating debugging through techniques like delta debugging can help developers quickly find and fix bugs.
Principles in software debugging
The document summarizes key concepts from the Udacity CS259 Software Debugging course, including:
1) Three states of errors in programs - defects in code, infections spreading errors, and failures in execution. Understanding how errors propagate through a program is important to debugging.
2) Techniques for debugging like assertions, code coverage, tracing, delta debugging and phi scoring to narrow relevant information and find root causes of failures.
3) Managing bugs in a project through proper tracking of problem lifecycles from new to closed, and use of bug databases linked to version control to map defects to code revisions.
AIESEC in SIM 14/15 Team Leaders & Team Members Application
This document outlines the structure and roles for AIESEC in SIM for the 2014/2015 term. The team aims to develop members, create a sustainable talent pipeline, and ensure customer satisfaction. Key roles include the Vice President of Talent Management overseeing programs like GCDP and GIP, and the Vice President of Brand and Marketing overseeing communications and marketing for programs. Positions include Team Leaders for programs and roles in talent management, marketing, and sales. Success will be measured by metrics like program realizations and customer satisfaction scores. The roles will help members gain experience in areas such as leadership, marketing, and customer service.
Debugging (Django) application in PyCharm
This document discusses debugging Django applications in PyCharm. It begins by mentioning common debugging tools like print statements in different languages. It then recommends using a debugger, explaining that debuggers are useful for large projects, troubleshooting third party libraries, or poorly written code. The document goes on to describe different debugger features in PyCharm like breakpoints, investigating variables and objects, evaluating expressions, and exception breakpoints. It concludes by providing some additional information about PyCharm editions.
Myanmar's Politics, Economy, and Government
Myanmar, also known as Burma, is located in Southeast Asia. It has over 60 million people and its largest city and capital is Naypyidaw. The official language is Burmese and other major languages include Shan, Karen, Kachin, Chin, Mon, and Rakhine. Myanmar has experienced decades of isolation and stagnation under military rule since a 1962 coup, though some political and economic reforms have taken place in recent years. The economy remains very weak despite natural resource wealth.
2014-geothermal-opportunities-usa
This document discusses opportunities for utilizing geothermal resources in the United States. It begins by providing background on renewable energy generation in the US, including centralized plants and distributed generation. It then analyzes a study of renewable energy production in LEED-certified buildings in northern US states. The document goes on to describe various applications of geothermal energy like direct use, power generation, cogeneration, enhanced geothermal systems, and geothermal heat pumps. It also reviews the benefits and costs of different geothermal technologies. The document uses Iceland as a case study to illustrate geothermal development and policies. It concludes by recommending increased adoption of geothermal heat pumps and capacity additions in the US through various
Cambios físicos y químicos - Mora Arguelles
El documento describe dos tipos de cambios: cambios físicos, donde la sustancia subyacente permanece la misma aunque cambie su forma, como el agua que se convierte en hielo; y cambios químicos, donde la sustancia se transforma en una nueva como el té al añadirle leche. También menciona que los cambios de estado incluyen la solidificación de un líquido a un sólido y la sublimación de un sólido a gas.
Viewers also liked (19)
Are Automated Debugging Techniques Actually Helping Programmers
Are Automated Debugging Techniques Actually Helping Programmers
Debugging application using visual studio 2010 and intellitrace
Debugging application using visual studio 2010 and intellitrace
AIESEC in SIM 14/15 Team Leaders & Team Members Application
AIESEC in SIM 14/15 Team Leaders & Team Members Application
Similar to Rubyslava debugging with_pry
Hangout Utche #6. "Rambovidnaya problema"
This document discusses the "diamond inheritance problem" in programming languages and summarizes efforts to implement just-in-time (JIT) compilation in the Ruby programming language. It describes early JIT implementation attempts by Shyohei Urabe and Vladimir Makarov, which had stability issues. It notes that Takashi Kokubun's MJIT-JARV implementation addressed some of these by removing optimizations and reverting some changes to the Ruby virtual machine, making the JIT slower but more stable. The document also briefly discusses JIT implementations in other languages like Go and issues with dependencies in Node.js package management.
CI doesn’t start with Jenkins
Slides from the talk "CI doesn’t start with Jenkins" from DevOps Stage 2018 (12-13 October 2018, Kyiv, Ukraine)
CI is not only a tool. You cannot simply install and configure Jenkins or whatever system and say that you have CICD pipeline. Here I'm trying to cover different aspects and dependencies of the CICD process based on Preply Inc experience.
External Links:
[2] CatOps Telegram channel: https://t.me/catops
[2] HashiCorp User Group Kyiv: https://www.meetup.com/Kyiv-HashiCorp-User-Group/
[12-24 ]https://www.endpoint.com/blog/2014/05/02/git-workflows-that-work
[49-50]: https://nvie.com/posts/a-successful-git-branching-model/
[51-56]: https://www.toptal.com/software/trunk-based-development-git-flow
[64] Django Anonymizer: https://github.com/knowledge-point/dj_anonymizer
Waterfalls for Agile in a bag
The document discusses issues that can arise from siloed roles in Scrum teams, such as developers, testers, and Scrum Masters acting as separate functions. This leads to reduced understanding between roles, bottlenecks when resources are unavailable, and an overall lack of team accountability. The document suggests that defining roles rigidly can cement separations and inhibit collaboration, flexibility, and process improvement. It argues teams should avoid "mini-waterfalls" between roles and instead strive for full cross-functionality, shared understanding of requirements, collective responsibility, and empowerment of self-organizing teams.
Waterfalls for agile cambridge
The document discusses various "mini-waterfalls" that can emerge in Scrum teams through defined roles like analysts, developers, and testers working sequentially rather than collaboratively. Some examples provided include analysts completing work before passing it to developers or testing only occurring at the end after development is finished. This siloed work can reduce understanding, flexibility, speed, and quality. The document suggests empowering cross-functional teams and automating work to avoid these anti-patterns. It prompts readers to examine their own teams for similar issues and ways to continuously improve.
Battle for Code Quality - A Story of One Java Project
This presentation is about unit tests, integration tests, REST tests, code coverage and analysis tools, code reviews and other tools that help achieve high-level results.
This presentation by Ilya Tsvetkov (Associate Manager, GlobalLogic) was delivered at GlobalLogic Java Conference in Krakow on December 12, 2015.
Surviving SOA
The document discusses challenges faced by a development team working within a large organization on a SOA project. Key challenges included long development cycles, separate testing teams, infrequent releases, and outdated technologies like SOAP. The team adopted practices like test-driven development, service mocking, telemetry, and exploratory testing to help improve their process under these constraints. While integration issues persisted, the team was able to keep their own defect rates low through these practices.
Surviving SOA - delivering (somewhat) continuously on a hostile planet
The document discusses challenges faced by a development team working within a large organization on a SOA project. Key challenges included long development cycles, separate testing teams, infrequent releases, and a lack of feedback mechanisms. The team adopted practices like TDD, trunk-based development, service mocking, and telemetry to reduce their cycle times, minimize risks, and improve quality despite the constraints of the larger organization. While integration issues persisted due to assumptions between teams, the team was able to react quickly to changes and had very low defect rates, though they did not significantly influence practices outside their team.
Quality at Speed - Penny Wyatt
How can a team of 65 developers build and rapidly ship a high-quality product with only six QA engineers? At Atlassian, we’ve introduced the Quality Assistance model that changes the developer QA mindset, and engages developers in exploratory testing so software is developed right the first time. After all, the cheapest time to fix a bug is before it's written. Join us as we walk through the theory, history, and practice of the model, while busting some of the myths about developers and QA. Reject the tradeoff of time, scope, and quality, and finally have your cake and eat it too.
Conquering AngularJS Limitations
Valeri Karpov
MongoDB - NodeJS Engineer
Tuesday, Oct 20th
11:25 am - Front-End/Back-End Dev
Find more by Valeri Karpov: http://www.slideshare.net/vkarpov15/
Conquering AngularJS Limitations
The document discusses strategies for addressing common AngularJS challenges including SEO, responsive design, and integration testing. It recommends using Prerender.io to generate static HTML for search engines to index Single Page Apps. For responsive design, it suggests using reactive directives that emit events in response to screen size changes rather than having directives know about screen size. Finally, it outlines an approach to integration testing AngularJS directives in isolation using Karma and bootstrapping directives for testing DOM logic.
Dev ops lessons learned - Michael Collins
The document discusses lessons learned from trying to implement DevOps in a rapidly growing company. Some key lessons include: (1) being able to clearly articulate what DevOps means for both individuals and the organization; (2) trusting developers and providing them with what they need; and (3) starting DevOps efforts with a focus on development environments rather than just production. The document also emphasizes focusing on toolchains rather than individual tools, using a service delivery pipeline approach, and ensuring good communication and hiring practices.
Fighting Ruby code smell
This document discusses code quality tools for Ruby code and how RubyMine can help. It introduces static and runtime tools for finding code smells, metrics for measuring qualities like duplication, and testing and coverage tools. RubyMine integrates many of these tools and performs on-the-fly code inspections to help improve code quality. The document encourages attendees to try RubyMine's code quality features themselves.
React, London JS Meetup, 11 Aug 2015
React is a revolution in web UI technology that uses a virtual DOM for fast rendering. It allows developers to build user interfaces as components in a declarative way using JavaScript or JSX. Components are fast, stateless, and their UI is a projection of data. The virtual DOM diffing algorithm efficiently detects changes and updates the real DOM. React promotes building user interfaces with unidirectional data flow and separating concerns into components rather than MVC.
Ruby codebases in an entropic universe
The document discusses how the entropy of Ruby codebases increases over time if changes are not limited, making future changes more difficult. It advocates for writing specs to establish confidence in code and observing trends in metrics like code coverage, complexity, and churn to catch signs of rising entropy early. Sticking to conventions but knowing when to deviate, and focusing on principles over mechanics can help limit a codebase's entropy.
Deploying 3 times a day without a downtime @ Rocket Tech Summit in Berlin
A look at how we try to make our architecture robust, resilient and fun to work with: Namshi is not github or spotify but... ...imitation is the sincerest form of flattery!
Test Driven Development - Workshop
Test Driven Development (TDD) is a software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases that are failed, then the software is improved to pass the new tests, and finally any newly introduced code is refactored. The document outlines the TDD lifecycle and process, describes unit testing and how it verifies isolated units of code, and discusses how TDD results in testable, clean code through refactoring. It provides examples of unit testing code for a bank account class.
My Little Webap - DevOpsSec is Magic
The document discusses the DevOpsSec approach which aims to integrate security testing into the development process through automation. It outlines how DevOpsSec can help address issues that arise from the traditional separation of development and operations teams. The document provides examples of different types of tests that can be automated, such as unit testing, performance testing, and security testing of an application's attack surface. It promotes automating as many tests as possible and sharing test automation code to continuously monitor for vulnerabilities and issues.
6 reasons Jubilee could be a Rubyist's new best friend
(Video here: http://confreaks.com/videos/5014-RubyConf2014-6-reasons-jubilee-could-be-a-rubyist-s-new-best-friend or https://www.youtube.com/watch?feature=player_embedded&v=FFR0G89WXI8)
Rubyconf 2014 talk on Jubilee, a Vert.x module that runs rack apps.
Alternate titles
Beyond Rails while using Rails
Rails can't do everything I want and <fill> makes me want to cry
Rubyconf abstract
Do you do web development in Ruby? Have you been forced to go to node or other technologies just for concurrency/websockets etc. Do miss your gems, and tire of functionality you have to implement from scratch? Do you hate javascript?
Well no need to switch languages/platforms, Jubilee could be your new best friend.
Jubilee, a rack server on top of Vert.x gives you
* Concurrency
* Speed
* Easy Websockets support
* Shared Memory
* Access to the JVM ecosystem
* Ability to reuse your existing Ruby knowledge and gems
"Say Hello to your new friend" - Al Pacino
10+ Deploys Per Day: Dev and Ops Cooperation at Flickr
Communications and cooperation between development and operations isn't optional, it's mandatory. Flickr takes the idea of "release early, release often" to an extreme - on a normal day there are 10 full deployments of the site to our servers. This session discusses why this rate of change works so well, and the culture and technology needed to make it possible.
Why You Should Be Fixing Bugs
The document discusses fixing bugs in software. It lists 4 bugs that have been fixed or are currently being worked on. It provides reasons for fixing bugs such as working on real software used by millions, impressing others, and learning valuable skills. Tips are given for getting started with bug fixing, including resources on the Mozilla hacking page and source code review site. Contact information is also listed for asking any questions.
Similar to Rubyslava debugging with_pry (20)
Battle for Code Quality - A Story of One Java Project
Battle for Code Quality - A Story of One Java Project
Surviving SOA - delivering (somewhat) continuously on a hostile planet
Surviving SOA - delivering (somewhat) continuously on a hostile planet
Deploying 3 times a day without a downtime @ Rocket Tech Summit in Berlin
Deploying 3 times a day without a downtime @ Rocket Tech Summit in Berlin
6 reasons Jubilee could be a Rubyist's new best friend
6 reasons Jubilee could be a Rubyist's new best friend
10+ Deploys Per Day: Dev and Ops Cooperation at Flickr
10+ Deploys Per Day: Dev and Ops Cooperation at Flickr
Recently uploaded
Public CyberSecurity Awareness Presentation 2024.pptx
Cyber security awareness slides for a busisness by TreeTop Security
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
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
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Dmitrii Kamaev, PhD
Senior Product Owner - QIAGEN
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
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 .
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
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.
The Microsoft 365 Migration Tutorial For Beginner.pptx
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
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.
Leveraging the Graph for Clinical Trials and Standards
Katja Glaß
OpenStudyBuilder Community Manager - Katja Glaß Consulting
Marius Conjeaud
Principal Consultant - Neo4j
Recently uploaded (20)
Public CyberSecurity Awareness Presentation 2024.pptx
Public CyberSecurity Awareness Presentation 2024.pptx
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
The Microsoft 365 Migration Tutorial For Beginner.pptx
The Microsoft 365 Migration Tutorial For Beginner.pptx
Leveraging the Graph for Clinical Trials and Standards
Leveraging the Graph for Clinical Trials and Standards
Rubyslava debugging with_pry
- 1. Debugging with Pry Michal Oláh @michalolah @bonetics
- 2. Progammers spend 60% of their time debugging We should pay attention to our workflow
- 4. “There are no fully fledged IDEs for Ruby on Rails…” –Agile Web Development with Rails -July 2009
- 5. WTF
- 6. WTF?
- 7. WTF?!
- 8. Actually its not that bad
- 9. we have tests after all
- 10. And puts is a powerfull thing
- 11. But what if you meet this guy?
- 13. Commands ! binding.pry play whereami edit -c exit ls cd next, previous, skip, breakpoint (debugger)
- 14. Demo 1 ! • debugging integration tests ! • fast feedback of what works and what doesn’t
- 15. Demo 2 ! • debugging controller action ! • ls, cd ! • inplace code edit and debug with breakpoints ! • edit, breakpoint, whereami, wtf?! ! • debugging with pry-rescue
- 17. Plugins and features • pry-debugger (MRI 1.8-1.9) • pry-byebug (MRI 2.0+) • pry-rescue - resque from exceptions in to a pry session • plymounth - jump into a pry session on test failure • pry-rails • help command • pry custom commands