Rails 3
•
0 likes•279 views
Rails 3 is a web application framework that utilizes the Model-View-Controller (MVC) pattern and represents resources and data using Representational State Transfer (REST) principles. The document discusses getting started with a new Rails 3 application by installing Rails, generating a new application, and starting the server. It also covers generating scaffolds to quickly develop models and controllers, the project structure, and testing Rails applications using RSpec.
Report
Share
Report
Share
Download to read offline
Recommended
Erlang Build Tools
The document provides an overview of different build tools available for Erlang projects, including Emakefile, Rebar, Rebar3, Erlang.mk, and Mix. Each tool has its own strengths in areas like packaging and releases, documentation, compilation and tests, and dependency management. The document describes how to set up a basic project using each tool and references additional online resources for using the tools in Erlang and Elixir development.
Trucker
The document discusses migrating legacy data from one application to another using the Trucker gem. It provides an overview of the typical manual and error-prone migration process and introduces Trucker as a way to migrate data from day one and improve it over time. The document then demonstrates how to generate a Trucker migration, define legacy model classes and mappings, run migrations in batches, and use custom helper methods.
Panoramic view of web APIs
Overview of web APIs
What is an API?
Explain the key parameters of the request/response cycle.
RESTful web API (Resources represented in URLs and HTTP verbs explained with example)
Basic CRUD operations
Show basic CRUD operations of an API using Flask on dummy data.
Show how "Flask-RESTful" library simplifies this to just a single code template
Background Tasks - Why and How?
Show how tasks like sending an email can block the API
Threading for blocking APIs
Scaling background tasks using "Task queues - Celery".
Comparing "threading" and "task queue".
Briefly go over the various ways to update the status of the background task.
API Documentation
Good documentation of APIs is extremely vital.
Serverless app deployment
Software design
Software design is important for complex software systems because it provides a map and metaphor to help understand the system. Good design uses tools that increase abstraction, such as domain-specific languages, design patterns, and refactoring. It also draws on principles from object-oriented analysis and design, SOLID principles, design patterns, code smells, test-driven development, functional programming design, and refactoring to produce high-quality code.
Scala
Diego Pacheco is a software architect and Agile coach who specializes in functional and object-oriented programming as well as traits and the actor model. He thanked someone for their time on Twitter while sharing details about his background and areas of technical expertise.
Cucumber
BDD was created by Dan North in 2003 as an evolution of TDD to improve communication between customers and developers. It uses examples written in a business-readable language to define requirements and tests. Cucumber is a tool that supports BDD using a natural language syntax for writing tests in Ruby.
Solution
Diego Pacheco discute várias opções de soluções, mas conclui que a melhor abordagem é a melhoria contínua sem controle rígido.
Treinamento Testes Unitários - parte 2
O documento apresenta uma palestra sobre testes unitários com ênfase em TestNG, Spring Framework e Mockito. Apresenta uma agenda com tópicos como revisão de Spring e Mockito, exercícios práticos de integração desses frameworks e revisão de código. Também fornece referências sobre testes unitários em livros e sites.
Recommended
Erlang Build Tools
The document provides an overview of different build tools available for Erlang projects, including Emakefile, Rebar, Rebar3, Erlang.mk, and Mix. Each tool has its own strengths in areas like packaging and releases, documentation, compilation and tests, and dependency management. The document describes how to set up a basic project using each tool and references additional online resources for using the tools in Erlang and Elixir development.
Trucker
The document discusses migrating legacy data from one application to another using the Trucker gem. It provides an overview of the typical manual and error-prone migration process and introduces Trucker as a way to migrate data from day one and improve it over time. The document then demonstrates how to generate a Trucker migration, define legacy model classes and mappings, run migrations in batches, and use custom helper methods.
Panoramic view of web APIs
Overview of web APIs
What is an API?
Explain the key parameters of the request/response cycle.
RESTful web API (Resources represented in URLs and HTTP verbs explained with example)
Basic CRUD operations
Show basic CRUD operations of an API using Flask on dummy data.
Show how "Flask-RESTful" library simplifies this to just a single code template
Background Tasks - Why and How?
Show how tasks like sending an email can block the API
Threading for blocking APIs
Scaling background tasks using "Task queues - Celery".
Comparing "threading" and "task queue".
Briefly go over the various ways to update the status of the background task.
API Documentation
Good documentation of APIs is extremely vital.
Serverless app deployment
Software design
Software design is important for complex software systems because it provides a map and metaphor to help understand the system. Good design uses tools that increase abstraction, such as domain-specific languages, design patterns, and refactoring. It also draws on principles from object-oriented analysis and design, SOLID principles, design patterns, code smells, test-driven development, functional programming design, and refactoring to produce high-quality code.
Scala
Diego Pacheco is a software architect and Agile coach who specializes in functional and object-oriented programming as well as traits and the actor model. He thanked someone for their time on Twitter while sharing details about his background and areas of technical expertise.
Cucumber
BDD was created by Dan North in 2003 as an evolution of TDD to improve communication between customers and developers. It uses examples written in a business-readable language to define requirements and tests. Cucumber is a tool that supports BDD using a natural language syntax for writing tests in Ruby.
Solution
Diego Pacheco discute várias opções de soluções, mas conclui que a melhor abordagem é a melhoria contínua sem controle rígido.
Treinamento Testes Unitários - parte 2
O documento apresenta uma palestra sobre testes unitários com ênfase em TestNG, Spring Framework e Mockito. Apresenta uma agenda com tópicos como revisão de Spring e Mockito, exercícios práticos de integração desses frameworks e revisão de código. Também fornece referências sobre testes unitários em livros e sites.
Naming Things Book : Simple Book Review!
The document discusses principles for naming identifiers in code such as variables, classes, and functions. It notes that naming is important because identifiers make up 70% of code and influence comprehension, recall, and bug fixing time. Good naming follows principles like understandability, using names that describe concepts, and consistency. It provides specific rules for naming classes, variables, functions for conciseness, consistency, and distinguishability. The goal is to use names that are understandable to both current and future engineers working on the code.
Continuous Discovery Habits Book Review.pdf
This document summarizes key points from the book "Continuous Discovery Habits" by Diego Pacheco. It advocates for continuous discovery through an outcome-oriented and customer-centric mindset. Discovery requires the collaboration of product managers, designers, and engineers to iteratively test assumptions and validate ideas with customers. The goal is to ensure teams are creating value for users and addressing their needs, pain points, and desires on an ongoing basis through experimental and visual approaches.
Thoughts about Shape Up
This document discusses the Shape Up methodology for agile software development projects. It introduces Shape Up as similar to Dual Track Agile, with an initial 6-week discovery process. Key aspects of how shaping works include setting boundaries, roughing out elements, addressing risks, writing a pitch, and creating simple breadboarding prototypes. Other topics covered are cutting scope, how the pitch works, using betting tables instead of backlogs, dealing with bugs, and making progress on the whole stack through scope mapping and discovery charts.
Holacracy
This document discusses Holacracy, an alternative organizational structure to traditional hierarchies. It notes that current management structures were designed for factories, while Holacracy is designed for humans. Holacracy eliminates hierarchies and instead focuses on clearly defined roles and circles within an organization. It aims to embrace autonomy through separating people from roles and having roles, not managers, make decisions. While challenging to implement due to issues of power, some companies have adopted aspects of Holacracy.
AWS IAM
This document discusses AWS Identity and Access Management (IAM). It provides an overview of IAM including its ability to provide fine-grained access control and integrate with SAML 2.0 and LDAP. It notes issues with passwords and credentials like entropy and rainbow table attacks. The document outlines IAM roles and policies and recommends making credentials temporary to improve security.
CDKs
This document is a profile for Diego Pacheco, who is a cat's father, head of software architecture, agile coach, SOA/microservices expert, DevOps practitioner, speaker, and author. He has expertise in topics such as Terraform, CDKs, and CDKs code generation and maintains GitHub repositories on these subjects.
Encryption Deep Dive
Encryption Deep Dive: Randomness, Entropy, RNG, PRNG, AES, AES Operational Modes, Data Rotations, Java Encryption APIs, Tradeoffs, challenges, Envelope Encryption, KMS, and much more on all things encryption.
Sec 101
This document profiles Diego Pacheco and provides an overview of key software security principles including defense in depth, the least privilege principle, encryption, TLS and mTLS, misconfiguration and error handling, input sanitization, cross-site scripting (XSS), insecure serialization/deserialization, known vulnerabilities, logging and audit trails, threat analysis, and engineering friction. The document emphasizes applying security best practices to protect customer experience, brand integrity, and compliance while avoiding friction for engineering teams.
Reflections on SCM
Reflections on SCM: DevOps, CI/CD, Branches, Architecture, PRs, and many more considerations and thoughts.
Management: Doing the non-obvious! III
This document discusses various management concepts and techniques, including:
- Biases that can negatively impact decision-making like planning fallacy and availability bias.
- How work is becoming indistinguishable from sabotage due to bureaucracy and predictability.
- The importance of having "skin in the game" and being willing to be wrong to drive change and learning.
- Dealing with scarcity by identifying high and low performance areas and reallocating resources accordingly.
Design is not Subjective
Design is Not Subjective! Software design and Lean UX, Ux, Design Thinking are not that different after all. UML was in the right direction the problem was where we applied. In this video, I will explain why Design is not subjective. Video https://www.youtube.com/watch?v=ijGR6Tbhr54
Architecture & Engineering : Doing the non-obvious!
Diego Pacheco is a software architect, agile coach, and speaker who focuses on non-traditional approaches. Some of his views include that requirements can change and duplication is okay, tests don't always improve design or find bugs, and complexity sometimes needs abstractions but other times they add unnecessary complexity. He also believes teams will always have technical debt so it's important to prioritize fixing quick wins over deep technical issues, and that architecture is about people and enabling teams.
Management doing the non-obvious II
This document discusses various management concepts and principles:
- You cannot regulate failure in complex systems and it is better to focus on recovering from failures rather than trying to predict and prevent them.
- Product teams are more effective than feature teams because they are focused on discovering customer needs rather than having predefined solutions.
- Sharing a vision rather than a detailed roadmap allows for more flexibility and ability to change tactics.
- Psychological safety and an environment where people feel included, safe to learn and contribute, and safe to challenge the status quo is important for teams.
- Discipline is needed to successfully execute digital transformations but often lacks longevity and focus shifts to short term goals.
Testing in production
The document discusses testing in production environments using "dark canaries". Dark canaries involve deploying code changes to a small percentage of real users without their knowledge to test for issues before broad deployment. The key benefits are that it allows testing with real users and traffic in the actual production environment and catching problems early before they affect everyone. Some challenges are potential privacy issues if users are not informed and ensuring changes don't negatively impact the small group of unaware users.
Nine lies about work
The document outlines 9 common lies about work and proposes alternative truths. The lies discussed include that people care most about the company they work for rather than their team, that the best plan wins rather than intelligence in real-time, and that feedback and performance reviews can reliably rate people. The author argues that people primarily care about their team, intelligence is needed to adapt to a dynamic world, and that reviews mostly reflect raters rather than ratees. The truths proposed emphasize caring for one's team, prioritizing real-time intelligence over static plans, and that people can best rate their own experiences.
Management: doing the nonobvious!
This document provides advice and perspectives on management and leadership from Diego Pacheco. Some of the key points discussed include:
- Ego can distort reality and inhibit innovation, so leaders should suppress ego with humility.
- Not all communication needs to happen between all people; structured teams are better models than rigid organization charts.
- Feedback is difficult to give and receive but is important for growth if approached without emotion or defensiveness.
- Scenario modeling and role playing exercises can help train leaders by anticipating problems before they occur.
AI and the Future
The document discusses several topics related to artificial intelligence and the future, including:
1) Whether AI-generated music has soul or not.
2) The possibility of AI judges making faster parallel decisions.
3) Elon Musk's view that we are all already cyborgs.
4) Musk's proposal that augmented humans could regenerate organs and tissues by 2100 through technologies like neuralink.
5) The potential to reengineer humans and expand lifespans to 120-150 years through these technologies.
Dealing with dependencies
This document discusses dealing with dependencies between teams when developing software. It acknowledges that fixed release schedules and monolithic codebases can create issues. Some potential solutions proposed include using contracts and mocks between teams, restructuring code using domain-driven design principles, and creating lean shared libraries to reduce duplication while allowing independence. The document advocates for moderate approaches between extremes rather than ignoring problems with dependencies.
Dealing with dependencies in tests
This document discusses different types of test doubles (fakes, stubs, mocks, spies, and dummies) that can be used to deal with dependencies in tests. It explains what each type is and provides examples of when each might be used. It also discusses how to design code for better test isolation by reducing coupling and avoiding tightly binding components together, though this can sometimes make the code harder to test. Cross-cutting concerns like authentication are discussed as things that may be difficult to fully isolate or mock at a component level.
Kanban 2020
This document discusses issues that can arise with Scrum implementations and introduces Kanban as an alternative. It notes problems with a focus on dates in Scrum and retaining the process rather than changing it. Kanban is presented as a lean approach that emphasizes continuous learning and improvement rather than utilization. The document outlines Kanban concepts like value stream mapping, cost of delay, Kanban boards, and metrics that can be used to test if a Kanban approach is being implemented.
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
More Related Content
More from Diego Pacheco
Naming Things Book : Simple Book Review!
The document discusses principles for naming identifiers in code such as variables, classes, and functions. It notes that naming is important because identifiers make up 70% of code and influence comprehension, recall, and bug fixing time. Good naming follows principles like understandability, using names that describe concepts, and consistency. It provides specific rules for naming classes, variables, functions for conciseness, consistency, and distinguishability. The goal is to use names that are understandable to both current and future engineers working on the code.
Continuous Discovery Habits Book Review.pdf
This document summarizes key points from the book "Continuous Discovery Habits" by Diego Pacheco. It advocates for continuous discovery through an outcome-oriented and customer-centric mindset. Discovery requires the collaboration of product managers, designers, and engineers to iteratively test assumptions and validate ideas with customers. The goal is to ensure teams are creating value for users and addressing their needs, pain points, and desires on an ongoing basis through experimental and visual approaches.
Thoughts about Shape Up
This document discusses the Shape Up methodology for agile software development projects. It introduces Shape Up as similar to Dual Track Agile, with an initial 6-week discovery process. Key aspects of how shaping works include setting boundaries, roughing out elements, addressing risks, writing a pitch, and creating simple breadboarding prototypes. Other topics covered are cutting scope, how the pitch works, using betting tables instead of backlogs, dealing with bugs, and making progress on the whole stack through scope mapping and discovery charts.
Holacracy
This document discusses Holacracy, an alternative organizational structure to traditional hierarchies. It notes that current management structures were designed for factories, while Holacracy is designed for humans. Holacracy eliminates hierarchies and instead focuses on clearly defined roles and circles within an organization. It aims to embrace autonomy through separating people from roles and having roles, not managers, make decisions. While challenging to implement due to issues of power, some companies have adopted aspects of Holacracy.
AWS IAM
This document discusses AWS Identity and Access Management (IAM). It provides an overview of IAM including its ability to provide fine-grained access control and integrate with SAML 2.0 and LDAP. It notes issues with passwords and credentials like entropy and rainbow table attacks. The document outlines IAM roles and policies and recommends making credentials temporary to improve security.
CDKs
This document is a profile for Diego Pacheco, who is a cat's father, head of software architecture, agile coach, SOA/microservices expert, DevOps practitioner, speaker, and author. He has expertise in topics such as Terraform, CDKs, and CDKs code generation and maintains GitHub repositories on these subjects.
Encryption Deep Dive
Encryption Deep Dive: Randomness, Entropy, RNG, PRNG, AES, AES Operational Modes, Data Rotations, Java Encryption APIs, Tradeoffs, challenges, Envelope Encryption, KMS, and much more on all things encryption.
Sec 101
This document profiles Diego Pacheco and provides an overview of key software security principles including defense in depth, the least privilege principle, encryption, TLS and mTLS, misconfiguration and error handling, input sanitization, cross-site scripting (XSS), insecure serialization/deserialization, known vulnerabilities, logging and audit trails, threat analysis, and engineering friction. The document emphasizes applying security best practices to protect customer experience, brand integrity, and compliance while avoiding friction for engineering teams.
Reflections on SCM
Reflections on SCM: DevOps, CI/CD, Branches, Architecture, PRs, and many more considerations and thoughts.
Management: Doing the non-obvious! III
This document discusses various management concepts and techniques, including:
- Biases that can negatively impact decision-making like planning fallacy and availability bias.
- How work is becoming indistinguishable from sabotage due to bureaucracy and predictability.
- The importance of having "skin in the game" and being willing to be wrong to drive change and learning.
- Dealing with scarcity by identifying high and low performance areas and reallocating resources accordingly.
Design is not Subjective
Design is Not Subjective! Software design and Lean UX, Ux, Design Thinking are not that different after all. UML was in the right direction the problem was where we applied. In this video, I will explain why Design is not subjective. Video https://www.youtube.com/watch?v=ijGR6Tbhr54
Architecture & Engineering : Doing the non-obvious!
Diego Pacheco is a software architect, agile coach, and speaker who focuses on non-traditional approaches. Some of his views include that requirements can change and duplication is okay, tests don't always improve design or find bugs, and complexity sometimes needs abstractions but other times they add unnecessary complexity. He also believes teams will always have technical debt so it's important to prioritize fixing quick wins over deep technical issues, and that architecture is about people and enabling teams.
Management doing the non-obvious II
This document discusses various management concepts and principles:
- You cannot regulate failure in complex systems and it is better to focus on recovering from failures rather than trying to predict and prevent them.
- Product teams are more effective than feature teams because they are focused on discovering customer needs rather than having predefined solutions.
- Sharing a vision rather than a detailed roadmap allows for more flexibility and ability to change tactics.
- Psychological safety and an environment where people feel included, safe to learn and contribute, and safe to challenge the status quo is important for teams.
- Discipline is needed to successfully execute digital transformations but often lacks longevity and focus shifts to short term goals.
Testing in production
The document discusses testing in production environments using "dark canaries". Dark canaries involve deploying code changes to a small percentage of real users without their knowledge to test for issues before broad deployment. The key benefits are that it allows testing with real users and traffic in the actual production environment and catching problems early before they affect everyone. Some challenges are potential privacy issues if users are not informed and ensuring changes don't negatively impact the small group of unaware users.
Nine lies about work
The document outlines 9 common lies about work and proposes alternative truths. The lies discussed include that people care most about the company they work for rather than their team, that the best plan wins rather than intelligence in real-time, and that feedback and performance reviews can reliably rate people. The author argues that people primarily care about their team, intelligence is needed to adapt to a dynamic world, and that reviews mostly reflect raters rather than ratees. The truths proposed emphasize caring for one's team, prioritizing real-time intelligence over static plans, and that people can best rate their own experiences.
Management: doing the nonobvious!
This document provides advice and perspectives on management and leadership from Diego Pacheco. Some of the key points discussed include:
- Ego can distort reality and inhibit innovation, so leaders should suppress ego with humility.
- Not all communication needs to happen between all people; structured teams are better models than rigid organization charts.
- Feedback is difficult to give and receive but is important for growth if approached without emotion or defensiveness.
- Scenario modeling and role playing exercises can help train leaders by anticipating problems before they occur.
AI and the Future
The document discusses several topics related to artificial intelligence and the future, including:
1) Whether AI-generated music has soul or not.
2) The possibility of AI judges making faster parallel decisions.
3) Elon Musk's view that we are all already cyborgs.
4) Musk's proposal that augmented humans could regenerate organs and tissues by 2100 through technologies like neuralink.
5) The potential to reengineer humans and expand lifespans to 120-150 years through these technologies.
Dealing with dependencies
This document discusses dealing with dependencies between teams when developing software. It acknowledges that fixed release schedules and monolithic codebases can create issues. Some potential solutions proposed include using contracts and mocks between teams, restructuring code using domain-driven design principles, and creating lean shared libraries to reduce duplication while allowing independence. The document advocates for moderate approaches between extremes rather than ignoring problems with dependencies.
Dealing with dependencies in tests
This document discusses different types of test doubles (fakes, stubs, mocks, spies, and dummies) that can be used to deal with dependencies in tests. It explains what each type is and provides examples of when each might be used. It also discusses how to design code for better test isolation by reducing coupling and avoiding tightly binding components together, though this can sometimes make the code harder to test. Cross-cutting concerns like authentication are discussed as things that may be difficult to fully isolate or mock at a component level.
Kanban 2020
This document discusses issues that can arise with Scrum implementations and introduces Kanban as an alternative. It notes problems with a focus on dates in Scrum and retaining the process rather than changing it. Kanban is presented as a lean approach that emphasizes continuous learning and improvement rather than utilization. The document outlines Kanban concepts like value stream mapping, cost of delay, Kanban boards, and metrics that can be used to test if a Kanban approach is being implemented.
More from Diego Pacheco (20)
Architecture & Engineering : Doing the non-obvious!
Architecture & Engineering : Doing the non-obvious!
Recently uploaded
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
CAKE: Sharing Slices of Confidential Data on Blockchain
Presented at the CAiSE 2024 Forum, Intelligent Information Systems, June 6th, Limassol, Cyprus.
Synopsis: Cooperative information systems typically involve various entities in a collaborative process within a distributed environment. Blockchain technology offers a mechanism for automating such processes, even when only partial trust exists among participants. The data stored on the blockchain is replicated across all nodes in the network, ensuring accessibility to all participants. While this aspect facilitates traceability, integrity, and persistence, it poses challenges for adopting public blockchains in enterprise settings due to confidentiality issues. In this paper, we present a software tool named Control Access via Key Encryption (CAKE), designed to ensure data confidentiality in scenarios involving public blockchains. After outlining its core components and functionalities, we showcase the application of CAKE in the context of a real-world cyber-security project within the logistics domain.
Paper: https://doi.org/10.1007/978-3-031-61000-4_16
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
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.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
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.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
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
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Things to Consider When Choosing a Website Developer for your Website | FODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Recently uploaded (20)
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
CAKE: Sharing Slices of Confidential Data on Blockchain
CAKE: Sharing Slices of Confidential Data on Blockchain
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Things to Consider When Choosing a Website Developer for your Website | FODUU
Things to Consider When Choosing a Website Developer for your Website | FODUU
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Rails 3
- 1. Rails 3 @diego_pacheco Software Architect | Agile Coach
- 3. Model, View & Controller
- 4. RESTful
- 5. D.R.Y
- 6. C.O.C
- 8. It’s CODE time !!!
- 9. Getting Started… $ gem install rails $ rails new rails3app $ cd rails3app $ rails s
- 12. rails3app / config / routes.rb
- 13. $ rails g scaffold person name:string email:string
- 14. $ rails g scaffold person name:string email:string class Person < ActiveRecord::Base end
- 15. RSpec / Rails Tests
- 16. Rails 3 Thank You @diego_pacheco Software Architect | Agile Coach