Spray
•
1 like•604 views
The document profiles Diego Pacheco as a software architect and agile coach who specializes in Scala and principles like non-blocking I/O and actor-based architectures using Akka. He has experience with several Spray libraries for building modular systems with caching, clients, HTTP handling, routing, testing, JSON, and more. The profile expresses thanks to Diego Pacheco.
Report
Share
Report
Share
Download to read offline
Recommended
A quick introduction to GraphQL
Presentation on GraphQL. It provides a quick introduction, explaining the what, why and how of the GraphQL capabilities. Presentation includes a working demo of GraphQL features through simple code example. Code used in the demo can be downloaded from https://github.com/ashokkumarta/graphql-samples
Introduction to lambda behave
Are you a Java developer and you've seen the fluent and modern specification frameworks available in other programming languages such as spock or jasmine and wondering why we can't have the same thing?
Then Lambda Behave is made for you! It uses numerous Java 8 features in order to enable cleaner and more readable tests and specifications. This quickie will introduce the framework, explain why you would want to use it over junit and cover some of its cool features, including:
* How to write fluent and clean specifications in your domain language
* How to write data driven specifications
* How to integrate these into your build tool or IDE
* How IDE usage can influence library design for the better
http://richardwarburton.github.io/lambda-behave/
Building APIs with Node.js and Swagger
This talk started with a quick description of APIs and the importance of good documentation. We then introduced Swagger, talked about how/why it helps in solving this process. Finally, we talked about a number of Node.js tools we've built to help make API design, API development and better overall APIs using Node.js and Swagger.
Rest API with Swagger and NodeJS
In this presentation I will explore what Swagger and OpenAPI is and what advantages you get in developing a REST API for IoT
APIdays Paris 2019 - Delivering Exceptional User Experience with REST and Gra...
Delivering Exceptional User Experience with REST and GraphQL APIs
Rebecca Fitzhugh, Director, Developer Relations at Rubrik
API-first development
The API-first design approach treats APIs as first-class citizens. The entire system or project is built around the idea that components connect via APIs. The first step is, therefore, to design the APIs and their connections.
However, there is a gap between the beautiful world of API specifications and the reality of agile development. This gap means that published API specifications are often incomplete, missing examples or simply outdated. The API specification meant to help developers can be a thorn in one’s side because keeping the specification in sync with its implementation is a manual process, tedious and prone to be forgotten during the rush to deliver.
We show how this gap can be bridged effectively using the API specification as the only source of truth driving the API implementation with proven tools enabling automation.
apidays LIVE Helsinki - Implementing OpenAPI and GraphQL Services with gRPC b...
apidays LIVE Helsinki - APIs, Platforms, And Ecosystems - Transforming Industries And Experiences
Implementing OpenAPI and GraphQL Services with gRPC
Tim Burks, Software Engineer at Google
Implement Web API with Swagger
Swagger is a description standard of REST API. I will show you features of Swagger UI, and how to make it out with grape and grape-swagger. At the end introduces PostgREST and emphasizes DRY principle.
Recommended
A quick introduction to GraphQL
Presentation on GraphQL. It provides a quick introduction, explaining the what, why and how of the GraphQL capabilities. Presentation includes a working demo of GraphQL features through simple code example. Code used in the demo can be downloaded from https://github.com/ashokkumarta/graphql-samples
Introduction to lambda behave
Are you a Java developer and you've seen the fluent and modern specification frameworks available in other programming languages such as spock or jasmine and wondering why we can't have the same thing?
Then Lambda Behave is made for you! It uses numerous Java 8 features in order to enable cleaner and more readable tests and specifications. This quickie will introduce the framework, explain why you would want to use it over junit and cover some of its cool features, including:
* How to write fluent and clean specifications in your domain language
* How to write data driven specifications
* How to integrate these into your build tool or IDE
* How IDE usage can influence library design for the better
http://richardwarburton.github.io/lambda-behave/
Building APIs with Node.js and Swagger
This talk started with a quick description of APIs and the importance of good documentation. We then introduced Swagger, talked about how/why it helps in solving this process. Finally, we talked about a number of Node.js tools we've built to help make API design, API development and better overall APIs using Node.js and Swagger.
Rest API with Swagger and NodeJS
In this presentation I will explore what Swagger and OpenAPI is and what advantages you get in developing a REST API for IoT
APIdays Paris 2019 - Delivering Exceptional User Experience with REST and Gra...
Delivering Exceptional User Experience with REST and GraphQL APIs
Rebecca Fitzhugh, Director, Developer Relations at Rubrik
API-first development
The API-first design approach treats APIs as first-class citizens. The entire system or project is built around the idea that components connect via APIs. The first step is, therefore, to design the APIs and their connections.
However, there is a gap between the beautiful world of API specifications and the reality of agile development. This gap means that published API specifications are often incomplete, missing examples or simply outdated. The API specification meant to help developers can be a thorn in one’s side because keeping the specification in sync with its implementation is a manual process, tedious and prone to be forgotten during the rush to deliver.
We show how this gap can be bridged effectively using the API specification as the only source of truth driving the API implementation with proven tools enabling automation.
apidays LIVE Helsinki - Implementing OpenAPI and GraphQL Services with gRPC b...
apidays LIVE Helsinki - APIs, Platforms, And Ecosystems - Transforming Industries And Experiences
Implementing OpenAPI and GraphQL Services with gRPC
Tim Burks, Software Engineer at Google
Implement Web API with Swagger
Swagger is a description standard of REST API. I will show you features of Swagger UI, and how to make it out with grape and grape-swagger. At the end introduces PostgREST and emphasizes DRY principle.
Arquillian 소개
The document discusses Arquillian, a testing framework that allows integration tests to be written and run similarly to unit tests. It can package components and their dependencies into a deployable archive. Tests using Arquillian can be run inside an IDE, incrementally built, and debugged like unit tests. The framework provides a component model for tests that encapsulates business logic and allows flexible configuration of the test classpath and deployment.
System design and architecture GgraphQL Public
Although a new technology when it comes to system design patterns, GraphQL borrows and builds on top of patterns that have been around for a while.
Serverless meetup - OpenWhisk overview and architecture
OpenWhisk is an open source serverless cloud platform that runs user-provided code in response to events or direct invocations. It was started by IBM and supports multiple programming languages and invocation models. The OpenWhisk architecture uses Nginx as an API gateway, a Scala controller to handle requests, Consul for service discovery, Kafka for messaging, Docker containers to run code, and CouchDB for persistent storage. This allows user code to be quickly deployed and executed in response to events in a scalable and reliable manner.
Designing APIs with OpenAPI Spec
A look into designing and build RESTful APIs using OpenApi Specification and Swagger tools, with examples in Node.js.
Javantura v4 - FreeMarker in Spring web - Marin Kalapać
Javantura v4 - FreeMarker in Spring web - Marin KalapaćHUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association
This document discusses using FreeMarker as a template engine with Spring MVC instead of JSP. It provides an overview of FreeMarker, how to configure Spring MVC to use it, and examples of FreeMarker syntax including variables, collections, includes, and macros. Commonly used FreeMarker components are demonstrated along with comparisons to JSP syntax.PostGraphQL
This document discusses PostGraphQL, which allows automatically generating a GraphQL API from a PostgreSQL database schema without writing any code. It describes how PostGraphQL can define the data model in PostgreSQL, handle permissions, generate CRUD operations and mutations, and connect to a PostgreSQL database. It also mentions how PostGraphQL supports features like pagination, sorting, access control, and computed properties through PostgreSQL functions.
Lift
The document discusses the Scala programming language and web framework Lift. It mentions that Scala and Lift were created in 2007 and highlights some of Lift's unique features, including lazy loading, parallel page rendering, Comet and Ajax support, wiring UI dependencies, designer friendly templates, wizards, and security. It also asks who is using Lift and provides commands to run a Lift application with sample code files.
Beautifying the Beautiful: Theming WSO2 API Manager
The portal apps play a significant role in designing and publishing APIs for API developers and enabling API consumers to discover and consume APIs. WSO2 API Manager 3.0 comes with complete portals conforming to a Single Page Application architecture using ReactJS. This architectural change brings lots of advantages, such as the modernized JS dependency system (NPM), improved packaging and build system (Webpack), and many more. These technologies allowed us to build versatile yet easily customizable portals.
This deck will explore the architectural changes in the new portal applications and how you could customize them to facilitate your custom requirements.
Discussion topics include:
- First level theming support to change many common issues without any hassle
- Advanced customization
- Theming for tenants
Watch the webinar on-demand here: https://wso2.com/library/webinars/2019/11/beautifying-the-beautiful-theming-wso2-api-manager/
apidays LIVE Australia 2020 - Have your cake and eat it too: GraphQL? REST? W...
apidays LIVE Australia 2020 - Building Business Ecosystems
Have your cake and eat it too: GraphQL? REST? Why not have both!
Roy Mor, Technical Lead at Sisense
Level 3 REST Makes Your API Browsable
The document discusses different levels of REST APIs. Level 3 REST expresses everything as links in the response body. An example is given where a GET request for doctor appointment slots returns an XML response containing the slots with a link to book each slot. Level 3 REST makes APIs browsable by including links to related resources, avoiding the need for separate documentation on how to perform actions.
apidays LIVE Australia 2020 - Productising your Microservices as API Products...
apidays LIVE Australia 2020 - Building Business Ecosystems
Productising your Microservices as API Products
Pubudu Gunatilaka, Technical Lead at WSO2
Everything you want to know about microservices
Introduction to microservices architecture, each chapter in the presentation target a step in your journey to build distributed system based on micro-services architecture form the design to the delivery
check my the explanation on the YouTube playlist
https://youtube.com/playlist?list=PLl0FlSJn8Rjxyo7Qx0JEOhLap9u6Lc-Bf
and on the CloudReady blog
https://www.cloudready.club
API Automation Testing Using RestAssured+Cucumber
The slides cover the introduction to cucumber, testNG, RestAssured why is BDD used, Basic concepts, and terminologies used in RestAssured, cucumber and TestNG.
apidays LIVE Australia 2020 - Leveraging DevOps to visualize your digital eco...
apidays LIVE Australia 2020 - Building Business Ecosystems
Leveraging DevOps to visualize your digital ecosystem
Mark Crawshaw, Founder of Aplas
Punta Dreamin 17 Generic Apex and Tooling Api
How to write highly generic and dynamic code and utilize the Salesforce Tooling API, from Punta Dreamin' 17!
Overview of Java EE
Java EE is a set of API specifications for enterprise application development on the Java platform that focuses on server-side development. It includes APIs like JAX-RS for RESTful web services, JPA for object-relational mapping, and JBatch for batch processing. Java EE applications can be run on various application servers like GlassFish, WildFly, WebSphere, and WebLogic. Java EE offers a rich set of APIs for server-side development that are built and maintained by experts in the community.
Javantura v4 - Java and lambdas and streams - are they better than for loops ...
Javantura v4 - Java and lambdas and streams - are they better than for loops ...HUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association
This document compares the performance of for loops, iterators, and Java 8 streams for processing collections of objects. It describes benchmark tests performed on different collection sizes ranging from 10 to 1,000,000 objects. The tests focused on common collection operations like finding the youngest/highest paid object, filtering by a property, and grouping by a property. The results showed that streams were generally faster than for loops for larger collections (>1000 objects) but slower for smaller collections. Iterators had the best performance overall. The document concludes that while streams offer a functional programming style, traditional for loops may still be better for smaller collections or certain object types due to stream overhead.AN EXERCISE IN CLEANER CODE - FROM LEGACY TO MAINTAINABLE
We’ve all had those projects, the salvage project, the legacy project that we picked up, and wished we never had.
Was it written 5 years ago by that young dev with lots of passion but no big picture vision.
Was it written 6 months ago by another team, by a top gun developer who knows all the design patterns, and tried to future proof the app, only succeeding in making it impossible for anyone else to understand.
Or was it you, 2 years ago, before you joined the community and learned more about best (better) practices and you almost cannot comprehend how you used to code.
Long story short, we have all been there, but the past is history, how do we proceed from here, that’s the key. We’ll look at some of the ways you can clean up your code, and walk through some examples, and walk the journey to software craftsmanship
5 main points
What is clean code
Reading vs Writing Code
Don’t suffocate your code, let it breathe
Simple & Self Documenting Code
Lower the Cognitive Load
Create GraphQL server with apolloJS
1. The document discusses how to use GraphQL with ApolloJS and provides an overview of both technologies. It introduces the presenter and covers GraphQL history, companies using GraphQL, advantages over REST, how to use GraphQL, and what ApolloJS is and its products.
2. It then summarizes how to set up an ApolloJS server including installing ApolloServer, defining types and schemas, resolving queries and mutations, using DataLoader for performance, subscriptions, and directives.
3. The presentation concludes with references for further reading on GraphQL and ApolloJS.
API SDK Development – Lessons Learned
Building a solid API is a challenge but getting our APIs to be adopted by a larger audience, we quickly realized that having solid SDKs is the key element.
At Rubrik we have been developing SDKs to supplement our APIs for over 3 years and during this process we have been making sure our SDKs provide a seamless experience for end-users to consume. When breaking API changes occur during the development of our product.
The key takeaways of this session are:
* How to strategize SDK development against an ever-changing API
* Securely open-source your SDK development process
Effective Scala (JavaDay Riga 2013)
This document provides an agenda and notes for a talk on optimizing Scala code to solve real-world problems without explosions, broken thumbs, or bullet wounds. The agenda includes discussing mantras, collection functions, implicits, and style. It emphasizes writing expressions instead of statements, avoiding null, staying immutable, using options instead of null checks, and limiting the scope of implicits. It also covers collection functions, type classes, and breaking out of for-comprehensions. The overall message is to write clear, concise Scala code using best practices around expressions, immutability, and type safety.
Baking Delicious Modularity in Scala
This was a presentation I gave in October 2013 to the Waterloo Scala Meetup. It's probably the 437th presentation on Scala modularity to date. There's tons of them, but the group was curious about how it was done and wanted the personal touch, so I gave it to them...
More Related Content
What's hot
Arquillian 소개
The document discusses Arquillian, a testing framework that allows integration tests to be written and run similarly to unit tests. It can package components and their dependencies into a deployable archive. Tests using Arquillian can be run inside an IDE, incrementally built, and debugged like unit tests. The framework provides a component model for tests that encapsulates business logic and allows flexible configuration of the test classpath and deployment.
System design and architecture GgraphQL Public
Although a new technology when it comes to system design patterns, GraphQL borrows and builds on top of patterns that have been around for a while.
Serverless meetup - OpenWhisk overview and architecture
OpenWhisk is an open source serverless cloud platform that runs user-provided code in response to events or direct invocations. It was started by IBM and supports multiple programming languages and invocation models. The OpenWhisk architecture uses Nginx as an API gateway, a Scala controller to handle requests, Consul for service discovery, Kafka for messaging, Docker containers to run code, and CouchDB for persistent storage. This allows user code to be quickly deployed and executed in response to events in a scalable and reliable manner.
Designing APIs with OpenAPI Spec
A look into designing and build RESTful APIs using OpenApi Specification and Swagger tools, with examples in Node.js.
Javantura v4 - FreeMarker in Spring web - Marin Kalapać
Javantura v4 - FreeMarker in Spring web - Marin KalapaćHUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association
This document discusses using FreeMarker as a template engine with Spring MVC instead of JSP. It provides an overview of FreeMarker, how to configure Spring MVC to use it, and examples of FreeMarker syntax including variables, collections, includes, and macros. Commonly used FreeMarker components are demonstrated along with comparisons to JSP syntax.PostGraphQL
This document discusses PostGraphQL, which allows automatically generating a GraphQL API from a PostgreSQL database schema without writing any code. It describes how PostGraphQL can define the data model in PostgreSQL, handle permissions, generate CRUD operations and mutations, and connect to a PostgreSQL database. It also mentions how PostGraphQL supports features like pagination, sorting, access control, and computed properties through PostgreSQL functions.
Lift
The document discusses the Scala programming language and web framework Lift. It mentions that Scala and Lift were created in 2007 and highlights some of Lift's unique features, including lazy loading, parallel page rendering, Comet and Ajax support, wiring UI dependencies, designer friendly templates, wizards, and security. It also asks who is using Lift and provides commands to run a Lift application with sample code files.
Beautifying the Beautiful: Theming WSO2 API Manager
The portal apps play a significant role in designing and publishing APIs for API developers and enabling API consumers to discover and consume APIs. WSO2 API Manager 3.0 comes with complete portals conforming to a Single Page Application architecture using ReactJS. This architectural change brings lots of advantages, such as the modernized JS dependency system (NPM), improved packaging and build system (Webpack), and many more. These technologies allowed us to build versatile yet easily customizable portals.
This deck will explore the architectural changes in the new portal applications and how you could customize them to facilitate your custom requirements.
Discussion topics include:
- First level theming support to change many common issues without any hassle
- Advanced customization
- Theming for tenants
Watch the webinar on-demand here: https://wso2.com/library/webinars/2019/11/beautifying-the-beautiful-theming-wso2-api-manager/
apidays LIVE Australia 2020 - Have your cake and eat it too: GraphQL? REST? W...
apidays LIVE Australia 2020 - Building Business Ecosystems
Have your cake and eat it too: GraphQL? REST? Why not have both!
Roy Mor, Technical Lead at Sisense
Level 3 REST Makes Your API Browsable
The document discusses different levels of REST APIs. Level 3 REST expresses everything as links in the response body. An example is given where a GET request for doctor appointment slots returns an XML response containing the slots with a link to book each slot. Level 3 REST makes APIs browsable by including links to related resources, avoiding the need for separate documentation on how to perform actions.
apidays LIVE Australia 2020 - Productising your Microservices as API Products...
apidays LIVE Australia 2020 - Building Business Ecosystems
Productising your Microservices as API Products
Pubudu Gunatilaka, Technical Lead at WSO2
Everything you want to know about microservices
Introduction to microservices architecture, each chapter in the presentation target a step in your journey to build distributed system based on micro-services architecture form the design to the delivery
check my the explanation on the YouTube playlist
https://youtube.com/playlist?list=PLl0FlSJn8Rjxyo7Qx0JEOhLap9u6Lc-Bf
and on the CloudReady blog
https://www.cloudready.club
API Automation Testing Using RestAssured+Cucumber
The slides cover the introduction to cucumber, testNG, RestAssured why is BDD used, Basic concepts, and terminologies used in RestAssured, cucumber and TestNG.
apidays LIVE Australia 2020 - Leveraging DevOps to visualize your digital eco...
apidays LIVE Australia 2020 - Building Business Ecosystems
Leveraging DevOps to visualize your digital ecosystem
Mark Crawshaw, Founder of Aplas
Punta Dreamin 17 Generic Apex and Tooling Api
How to write highly generic and dynamic code and utilize the Salesforce Tooling API, from Punta Dreamin' 17!
Overview of Java EE
Java EE is a set of API specifications for enterprise application development on the Java platform that focuses on server-side development. It includes APIs like JAX-RS for RESTful web services, JPA for object-relational mapping, and JBatch for batch processing. Java EE applications can be run on various application servers like GlassFish, WildFly, WebSphere, and WebLogic. Java EE offers a rich set of APIs for server-side development that are built and maintained by experts in the community.
Javantura v4 - Java and lambdas and streams - are they better than for loops ...
Javantura v4 - Java and lambdas and streams - are they better than for loops ...HUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association
This document compares the performance of for loops, iterators, and Java 8 streams for processing collections of objects. It describes benchmark tests performed on different collection sizes ranging from 10 to 1,000,000 objects. The tests focused on common collection operations like finding the youngest/highest paid object, filtering by a property, and grouping by a property. The results showed that streams were generally faster than for loops for larger collections (>1000 objects) but slower for smaller collections. Iterators had the best performance overall. The document concludes that while streams offer a functional programming style, traditional for loops may still be better for smaller collections or certain object types due to stream overhead.AN EXERCISE IN CLEANER CODE - FROM LEGACY TO MAINTAINABLE
We’ve all had those projects, the salvage project, the legacy project that we picked up, and wished we never had.
Was it written 5 years ago by that young dev with lots of passion but no big picture vision.
Was it written 6 months ago by another team, by a top gun developer who knows all the design patterns, and tried to future proof the app, only succeeding in making it impossible for anyone else to understand.
Or was it you, 2 years ago, before you joined the community and learned more about best (better) practices and you almost cannot comprehend how you used to code.
Long story short, we have all been there, but the past is history, how do we proceed from here, that’s the key. We’ll look at some of the ways you can clean up your code, and walk through some examples, and walk the journey to software craftsmanship
5 main points
What is clean code
Reading vs Writing Code
Don’t suffocate your code, let it breathe
Simple & Self Documenting Code
Lower the Cognitive Load
Create GraphQL server with apolloJS
1. The document discusses how to use GraphQL with ApolloJS and provides an overview of both technologies. It introduces the presenter and covers GraphQL history, companies using GraphQL, advantages over REST, how to use GraphQL, and what ApolloJS is and its products.
2. It then summarizes how to set up an ApolloJS server including installing ApolloServer, defining types and schemas, resolving queries and mutations, using DataLoader for performance, subscriptions, and directives.
3. The presentation concludes with references for further reading on GraphQL and ApolloJS.
API SDK Development – Lessons Learned
Building a solid API is a challenge but getting our APIs to be adopted by a larger audience, we quickly realized that having solid SDKs is the key element.
At Rubrik we have been developing SDKs to supplement our APIs for over 3 years and during this process we have been making sure our SDKs provide a seamless experience for end-users to consume. When breaking API changes occur during the development of our product.
The key takeaways of this session are:
* How to strategize SDK development against an ever-changing API
* Securely open-source your SDK development process
What's hot (20)
Serverless meetup - OpenWhisk overview and architecture
Serverless meetup - OpenWhisk overview and architecture
Javantura v4 - FreeMarker in Spring web - Marin Kalapać
Javantura v4 - FreeMarker in Spring web - Marin Kalapać
Beautifying the Beautiful: Theming WSO2 API Manager
Beautifying the Beautiful: Theming WSO2 API Manager
apidays LIVE Australia 2020 - Have your cake and eat it too: GraphQL? REST? W...
apidays LIVE Australia 2020 - Have your cake and eat it too: GraphQL? REST? W...
apidays LIVE Australia 2020 - Productising your Microservices as API Products...
apidays LIVE Australia 2020 - Productising your Microservices as API Products...
apidays LIVE Australia 2020 - Leveraging DevOps to visualize your digital eco...
apidays LIVE Australia 2020 - Leveraging DevOps to visualize your digital eco...
Javantura v4 - Java and lambdas and streams - are they better than for loops ...
Javantura v4 - Java and lambdas and streams - are they better than for loops ...
AN EXERCISE IN CLEANER CODE - FROM LEGACY TO MAINTAINABLE
AN EXERCISE IN CLEANER CODE - FROM LEGACY TO MAINTAINABLE
Viewers also liked
Effective Scala (JavaDay Riga 2013)
This document provides an agenda and notes for a talk on optimizing Scala code to solve real-world problems without explosions, broken thumbs, or bullet wounds. The agenda includes discussing mantras, collection functions, implicits, and style. It emphasizes writing expressions instead of statements, avoiding null, staying immutable, using options instead of null checks, and limiting the scope of implicits. It also covers collection functions, type classes, and breaking out of for-comprehensions. The overall message is to write clear, concise Scala code using best practices around expressions, immutability, and type safety.
Baking Delicious Modularity in Scala
This was a presentation I gave in October 2013 to the Waterloo Scala Meetup. It's probably the 437th presentation on Scala modularity to date. There's tons of them, but the group was curious about how it was done and wanted the personal touch, so I gave it to them...
Scala Implicits - Not to be feared
These are the slides from a talk I gave at the Waterloo Scala Meetup on October 9th 2013. The talk was geared toward describing the purpose of implicits, use cases, and getting past that initial hump of "what are they and why would I need them" in order to get people to start exploring the ideas.
Scala Past, Present & Future
Can you believe that the Scala programming language is already 13 years old? Scala was an experiment back in 2003, but there are no questions today about its success and its great influence on other languages, especially on Java. In this session we will travel time, going back to the age when Java was the hacker’s drink, while Pizza was the hacker’s food. We will glance through some of the memorable moments, and land in the present days to introduce all the goodnesses available in the upcoming Scala 2.12 release. Finally, we will take a brief but intense look at what we can expect from the future. Prepare your time traveling equipment, and be ready to rewind the clock to more than 20 years ago!
Akka in 100 slides or less
I gave this presentation to my coworkers recently. Unfortunately, the animations done translate to PDF so it's a tad sucky, but the main content is there.
Effective Scala (SoftShake 2013)
This document provides a summary of a presentation on optimizing Scala code without explosions or injuries. The presentation covers topics like style guidelines, collection APIs, implicits, and immutability. The speaker emphasizes expressing code as functions rather than statements, avoiding null, using Options instead of null checks, and limiting the scope of implicits for better performance and readability. The document includes code examples demonstrating various Scala features.
Introduction to Functional Programming with Scala
The document provides an introduction to functional programming with Scala. It outlines the following topics that will be covered: learning Scala syntax and writing simple programs; important functional programming concepts like closures, higher-order functions, purity, lazy evaluation, currying, tail calls, immutability, and type inference; and understanding the functional programming paradigm through Scala. It also provides some background information on Scala and examples of Scala code demonstrating various concepts.
Viewers also liked (7)
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!
Spray
- 1. @diego_pacheco Software Architect | Agile Coach
- 2. Scala
- 5. Principles Nom-blocking-io Actor-Based(Akka) Library Modular
- 6. Modules Spray-Caching Spray-Can Spray-Client Spray-Http Spray-HttpX Spray-IO Spray-Servlet Spray-Routing Spray-testkit Spray-util Spray-json
- 7. Architecture
- 11. Benchmark
- 12. @diego_pacheco Software Architect | Agile Coach Obrigado !!!