FP
•
1 like•499 views
The document discusses the benefits of functional programming compared to object-oriented programming, highlighting functional programming's focus on algorithms, avoiding side effects through pure functions to improve refactoring, and taking a state discipline approach. It encourages changing one's perspective and way of thinking to appreciate functional programming's practical and delivery-oriented nature despite potential distractions from object-oriented approaches.
Report
Share
Report
Share
Download to read offline
Recommended
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.
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.
Apache zookeeper
Diego Pacheco is a software architect and agile coach who tweets about his work. He received a response thanking him for something in Portuguese. The short exchange on Twitter between Diego Pacheco and another user was brief and informal.
Lean startup
This document discusses an agile approach to software development using lean startup principles. It mentions using a business model canvas to model ideas and small iterative "poker bets" or experiments to test assumptions quickly. The author is a software architect and agile coach advocating for lean startup methods.
The Professional Software Engineer
This document discusses the role and responsibilities of a professional software engineer. It covers topics like agile methodologies, software craftsmanship principles, test-driven development, architecture, design patterns, and resources for further learning. The document is presented by Everyware Technologies, a consulting, training and development company focused on helping engineers improve their skills and practices.
PMI Central Indiana Chapter - Product Owner - Michael Nir - Slide deck
PMI Central Indiana Chapter - Product Owner - Michael Nir - Slide deckMichael Nir Business Agility Speaker and Coach
Practical roadmap for value driven product owner excellence
The product owner is vital for the effective transformation of the organization. This presentation provides a practical roadmap to product owner excellence. We discuss BABOK framework and a business analysis approach for product owners - defining key concepts and methods for success. We touch on:
The Business Analyst, Agile - the manifesto, and the Product Owner;
PO and BA differences and similarities;
Three key differentiators for Product Owner excellence.
Professional Product Owners - pivotal in leading organization growth
Changes 2012
The document outlines Diego Pacheco's goals for 2012 which include hosting more coding dojos, taking Tuesday off, charging $1.99 for mind-blowing work, sponsoring a Trump beer, focusing on code quality, design changes, team practices and innovation, participating in a performance panel reviewing past metrics and awards, and starting the new year by "kicking asses".
3 little clojure functions ii
The document discusses Clojure functions including repeat, seq, and lazy-seq. It also mentions car and bank functions. The author is a geek who likes dinosaurs and recommends Clojure as a functional programming language over enterprise Java. Homework includes exploring more Clojure functions, solving problems on 4clojure, and calling a Clojure function from Java code.
Recommended
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.
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.
Apache zookeeper
Diego Pacheco is a software architect and agile coach who tweets about his work. He received a response thanking him for something in Portuguese. The short exchange on Twitter between Diego Pacheco and another user was brief and informal.
Lean startup
This document discusses an agile approach to software development using lean startup principles. It mentions using a business model canvas to model ideas and small iterative "poker bets" or experiments to test assumptions quickly. The author is a software architect and agile coach advocating for lean startup methods.
The Professional Software Engineer
This document discusses the role and responsibilities of a professional software engineer. It covers topics like agile methodologies, software craftsmanship principles, test-driven development, architecture, design patterns, and resources for further learning. The document is presented by Everyware Technologies, a consulting, training and development company focused on helping engineers improve their skills and practices.
PMI Central Indiana Chapter - Product Owner - Michael Nir - Slide deck
PMI Central Indiana Chapter - Product Owner - Michael Nir - Slide deckMichael Nir Business Agility Speaker and Coach
Practical roadmap for value driven product owner excellence
The product owner is vital for the effective transformation of the organization. This presentation provides a practical roadmap to product owner excellence. We discuss BABOK framework and a business analysis approach for product owners - defining key concepts and methods for success. We touch on:
The Business Analyst, Agile - the manifesto, and the Product Owner;
PO and BA differences and similarities;
Three key differentiators for Product Owner excellence.
Professional Product Owners - pivotal in leading organization growth
Changes 2012
The document outlines Diego Pacheco's goals for 2012 which include hosting more coding dojos, taking Tuesday off, charging $1.99 for mind-blowing work, sponsoring a Trump beer, focusing on code quality, design changes, team practices and innovation, participating in a performance panel reviewing past metrics and awards, and starting the new year by "kicking asses".
3 little clojure functions ii
The document discusses Clojure functions including repeat, seq, and lazy-seq. It also mentions car and bank functions. The author is a geek who likes dinosaurs and recommends Clojure as a functional programming language over enterprise Java. Homework includes exploring more Clojure functions, solving problems on 4clojure, and calling a Clojure function from Java code.
HawtDB
HawtDB is a lightweight, embedded key-value database written in Java that uses only a single JAR file of 172kb in size. It offers optional ACID transactions with optimistic concurrency and multi-version concurrency control. The database allows for customized key-value encoding and supports BTree or hash indexes with customizable comparators.
3 little clojure functions
This document discusses two little functions (assoc and subs), one big macro (dosync), and the calc function. It provides examples of using the calc function to perform basic arithmetic operations like addition, subtraction, multiplication, and division. It also outlines upcoming homework assignments involving creating new functions from Clojure.core and functions for calculating car taxes and modeling bank account transactions with unit tests.
Xp is not dead
This Twitter thread from Diego Pacheco introduces himself as a software architect and agile coach who then shares a link to the Half-Arsed Agile Manifesto website. He thanks someone for their comment.
Vacations 2011 for JTs
The document discusses improvements for a team including pair programming and Saturday DOJOs. Pair programming fosters communication, collaboration, and respect through learning. Saturday DOJOs would involve 10 lightning talks from team members on various programming topics along with coding challenges and beer. The document thanks the reader at the end.
3 little clojure functions 4
This document discusses a Clojure meetup where participants solved problems on 4Clojure.com and shared solutions. It promotes learning Clojure functions and practicing problem solving. Next steps include exploring Clojure functions, solving more problems on 4Clojure, giving lightning talks on the Clojure ecosystem, and planning for a final meetup.
Library Research Service and Colorado State Library
Presentation created for the students and faculty at the University of Denver to help explain the details and responsibilities of the Colorado State Library and its responsibilities to libraries and the state.
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.
More Related Content
Viewers also liked
HawtDB
HawtDB is a lightweight, embedded key-value database written in Java that uses only a single JAR file of 172kb in size. It offers optional ACID transactions with optimistic concurrency and multi-version concurrency control. The database allows for customized key-value encoding and supports BTree or hash indexes with customizable comparators.
3 little clojure functions
This document discusses two little functions (assoc and subs), one big macro (dosync), and the calc function. It provides examples of using the calc function to perform basic arithmetic operations like addition, subtraction, multiplication, and division. It also outlines upcoming homework assignments involving creating new functions from Clojure.core and functions for calculating car taxes and modeling bank account transactions with unit tests.
Xp is not dead
This Twitter thread from Diego Pacheco introduces himself as a software architect and agile coach who then shares a link to the Half-Arsed Agile Manifesto website. He thanks someone for their comment.
Vacations 2011 for JTs
The document discusses improvements for a team including pair programming and Saturday DOJOs. Pair programming fosters communication, collaboration, and respect through learning. Saturday DOJOs would involve 10 lightning talks from team members on various programming topics along with coding challenges and beer. The document thanks the reader at the end.
3 little clojure functions 4
This document discusses a Clojure meetup where participants solved problems on 4Clojure.com and shared solutions. It promotes learning Clojure functions and practicing problem solving. Next steps include exploring Clojure functions, solving more problems on 4Clojure, giving lightning talks on the Clojure ecosystem, and planning for a final meetup.
Library Research Service and Colorado State Library
Presentation created for the students and faculty at the University of Denver to help explain the details and responsibilities of the Colorado State Library and its responsibilities to libraries and the state.
Viewers also liked (6)
Library Research Service and Colorado State Library
Library Research Service and Colorado State Library
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
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Principle of conventional tomography-Bibash Shahi ppt..pptx
before the computed tomography, it had been widely used.
What is an RPA CoE? Session 1 – CoE Vision
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
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.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Mutation Testing for Task-Oriented Chatbots
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
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.
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.
Leveraging the Graph for Clinical Trials and Standards
Katja Glaß
OpenStudyBuilder Community Manager - Katja Glaß Consulting
Marius Conjeaud
Principal Consultant - Neo4j
"Choosing proper type of scaling", Olena Syrota
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
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
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.
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...Pitangent Analytics & Technology Solutions Pvt. Ltd
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.Dandelion Hashtable: beyond billion requests per second on a commodity server
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Recently uploaded (20)
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
Principle of conventional tomography-Bibash Shahi ppt..pptx
Principle of conventional tomography-Bibash Shahi ppt..pptx
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
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
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
Leveraging the Graph for Clinical Trials and Standards
Leveraging the Graph for Clinical Trials and Standards
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
FP
- 1. Diego Pacheco Software Architect | Agile Coach @diego_pacheco Functional Programming
- 5. Pratical OO, Fat but works!
- 9. Coder Focous
- 11. Cargo Cult!
- 15. What is the Difference?
- 18. Function & Data | Data & Functions
- 19. Algorithm focus
- 20. State Discipline
- 21. Deeply Learning
- 22. Pure Functions: Avoid Side Effects, Improve Refactoring!
- 23. Perpective is everything: Change your way to think!
- 24. Diego Pacheco Software Architect | Agile Coach @diego_pacheco Functional Programming Obrigado! Thank you!