Framework-less Applications
•
0 likes•529 views
The Sceptical Programmer's Manifesto on choosing libraries versus frameworks for application development
Report
Share
Report
Share
Download to read offline
Recommended
The Art of Software Gardening
The document is a transcript from a presentation titled "The Art of Software Gardening" given by Patroklos Papapetrou at DevTernity 2015. The presentation proposes using the analogy of software development as gardening, where developers are called "software gardeners" and code is treated like plants in a garden. Some key aspects of this analogy include evolving design like a garden, continuous refactoring to remove dead code, treating each line of code with passion, and having skills, best practices, and tools to develop software while withstanding changes like a garden withstands weather. The goal of this analogy is to promote an attitude of care, evolution and passion in software development.
Agile Software Architecture
Agile software architecture aims to deliver value fast by evolving the architecture during the project based on what is important now, rather than defining it upfront. This reduces risk and waste by allowing decisions to be made based on actual knowledge gained during development. The architecture should be the simplest solution to support current functionality and evolve economically through changes without making the software worse. Principles like separation of concerns, refactoring, and tests that drive design help enable evolving the architecture in a controlled way.
Agile Data
To rephrase an old saying: ‘It takes a village to raise an Analyst.’ Data Analysts and Scientists are working in teams delivering insight and analysis on an ongoing basis. So how do you get the team to support experimentation and insight delivery without ending up in an IT Engineer vs Analyst vs Data Governance war? We present 5 shocking steps to get these teams of people working together with practical, doable steps that can help you achieve data agility. The speaker has decades of hands on and executive management experience in data, analytics, and software development.
Zero downtime deployment
Overview of techniques and architectures used in applications with zero downtime deployment. Talk was given on Kaunas Java User Group meetup #33 (http://kaunas-jug.lt/).
Programuotojo karjeros mitai
Programuotojai ne tik sėdi ir kodina, o jų karjera gali būti horizontali. Darbas nėra nuolatinis gaisrų gesinimas, o našumas matuojamas ne kodo eilutėmis. Aukštasis mokslas skirtas ne tik diplomui, nes darbe neišmoksi visko, ko reikia. Programavimo amatas galandamas visą gyvenimą. Ir pabaigai: ne visi programuotojai augina barzdas.
Simplicity
Building working software is hard. But it's so much harder to build software that is easy to change. Yet this is a prerequisite for being truly agile, and a key enabler of agility is simplicity. But what exactly does simplicity mean and why is it so hard to achieve? It looks like complexity creeps in as soon as you stop paying attention, and most of it is accidental. Luckily, there are practical ways to get to simplicity by following good design principles and choosing simpler tools.
Life without Objects (w/ Clojure)
The document discusses how applying object-oriented (OO) design principles can often lead to functional design when using Clojure. It provides examples of how single responsibility, interface segregation, and dependency inversion translate to more modular functional designs using namespaces, protocols, multimethods, and partial function application. Polymorphism in Clojure is more flexible than OO polymorphism through protocols and multimethods. State management can be modeled functionally using atoms to manage immutable state. Overall, Clojure allows embracing many benefits of OO and functional design together.
Name Stuff
Naming stuff is one of the two hard things in Computer Science. And we fail at it every time we create another Manager or Service, or when we follow "framework conventions". Those of us living in OOP world desperately need better abstractions. And Functional Programming is no panacea since we still need DDD practices to guide our design. Regardless of your background, this talk is designed to help you improve your names and naming habits. No need to reinvent the wheel - let's borrow ideas from Eric Evans, Uncle Bob, Kent Beck and other experts.
Recommended
The Art of Software Gardening
The document is a transcript from a presentation titled "The Art of Software Gardening" given by Patroklos Papapetrou at DevTernity 2015. The presentation proposes using the analogy of software development as gardening, where developers are called "software gardeners" and code is treated like plants in a garden. Some key aspects of this analogy include evolving design like a garden, continuous refactoring to remove dead code, treating each line of code with passion, and having skills, best practices, and tools to develop software while withstanding changes like a garden withstands weather. The goal of this analogy is to promote an attitude of care, evolution and passion in software development.
Agile Software Architecture
Agile software architecture aims to deliver value fast by evolving the architecture during the project based on what is important now, rather than defining it upfront. This reduces risk and waste by allowing decisions to be made based on actual knowledge gained during development. The architecture should be the simplest solution to support current functionality and evolve economically through changes without making the software worse. Principles like separation of concerns, refactoring, and tests that drive design help enable evolving the architecture in a controlled way.
Agile Data
To rephrase an old saying: ‘It takes a village to raise an Analyst.’ Data Analysts and Scientists are working in teams delivering insight and analysis on an ongoing basis. So how do you get the team to support experimentation and insight delivery without ending up in an IT Engineer vs Analyst vs Data Governance war? We present 5 shocking steps to get these teams of people working together with practical, doable steps that can help you achieve data agility. The speaker has decades of hands on and executive management experience in data, analytics, and software development.
Zero downtime deployment
Overview of techniques and architectures used in applications with zero downtime deployment. Talk was given on Kaunas Java User Group meetup #33 (http://kaunas-jug.lt/).
Programuotojo karjeros mitai
Programuotojai ne tik sėdi ir kodina, o jų karjera gali būti horizontali. Darbas nėra nuolatinis gaisrų gesinimas, o našumas matuojamas ne kodo eilutėmis. Aukštasis mokslas skirtas ne tik diplomui, nes darbe neišmoksi visko, ko reikia. Programavimo amatas galandamas visą gyvenimą. Ir pabaigai: ne visi programuotojai augina barzdas.
Simplicity
Building working software is hard. But it's so much harder to build software that is easy to change. Yet this is a prerequisite for being truly agile, and a key enabler of agility is simplicity. But what exactly does simplicity mean and why is it so hard to achieve? It looks like complexity creeps in as soon as you stop paying attention, and most of it is accidental. Luckily, there are practical ways to get to simplicity by following good design principles and choosing simpler tools.
Life without Objects (w/ Clojure)
The document discusses how applying object-oriented (OO) design principles can often lead to functional design when using Clojure. It provides examples of how single responsibility, interface segregation, and dependency inversion translate to more modular functional designs using namespaces, protocols, multimethods, and partial function application. Polymorphism in Clojure is more flexible than OO polymorphism through protocols and multimethods. State management can be modeled functionally using atoms to manage immutable state. Overall, Clojure allows embracing many benefits of OO and functional design together.
Name Stuff
Naming stuff is one of the two hard things in Computer Science. And we fail at it every time we create another Manager or Service, or when we follow "framework conventions". Those of us living in OOP world desperately need better abstractions. And Functional Programming is no panacea since we still need DDD practices to guide our design. Regardless of your background, this talk is designed to help you improve your names and naming habits. No need to reinvent the wheel - let's borrow ideas from Eric Evans, Uncle Bob, Kent Beck and other experts.
How To Implement DevSecOps In Your Existing DevOps Workflow
Prioritizing DevOps without considering security can be dangerous. So how can security be implemented within a DevOps team? Adapt to DevSecOps and see how it assists you in developing your implementation technique. This blog will provide a comprehensive understanding of the DevSecOps methodology.
Agile software development
Overview of the agile software development. This contents was originally created for my team's internal workshop. It includes basic concept of the agile software development, and introduction of some practices and tools for it.
Glossary of Agile Terms
An A - Z glossary of terms for agile methodology, designed to help businesses understand the terminology used by technical software development teams.
Breaking Tradition: Agile Frameworks For The Modern Era of Collaborative Proj...
Agile software development is an application development methodology emphasizing an iterative process in which cross-functional teams collaborate to produce superior solutions. Agile frameworks are distinct development methods or techniques that adhere to Agile principles. The majority of businesses utilize these frameworks to address their particular needs.
Benefits of Agile Software Development for Senior Management
This is a presentation to Senior and Executive Managers which is used to explain how Agile Software Development processes and practices benefit them, their organization and their customers.
331103344.ppt
The document discusses agile process models and compares plan-driven and agile development approaches. Agile development involves interleaving program specification, design, and implementation. The system is developed through frequent delivery of new versions for stakeholder evaluation. Agile aims to reduce overheads and quickly respond to changing requirements through practices like minimal documentation and extensive automated testing.
Scrum Awareness 2.0.1
Here are the estimates for the paper town buildings in story points:
House: 3 story points
Villa: 5 story points
Apartment Building: 8 story points
Fire Department: 13 story points
02_Introduction to Software Engineering(1).pptx
Dokuemen ini merupakan materi ajar matakuliah Rekayasa Perangkat Lunak. Materi ini merupakan materi awal yang berisi:
What is Engineering?
What is Software?
Software Applications
Software—New Categories
A Software Engineering
What is Software Engineering?
A Layered Technology
Software Development Life Cycle
The document discusses software engineering and the software development life cycle (SDLC). It defines key terms like system software, application software, and network-based software. It describes the characteristics of well-engineered software and lists the typical phases in the SDLC: analysis, design, coding, testing, implementation, maintenance, and re-engineering. The advantages of following the SDLC are also highlighted.
Scrum presentation jyoti
Scrum is an agile process that focuses on delivering business value in the shortest time. It delivers working software in short iterations called sprints. The key aspects of scrum include user stories to define requirements, a product backlog to track and prioritize work, sprint planning and daily standups to coordinate work within a sprint, and sprint reviews and retrospectives after each sprint to inspect progress and improve processes. The scrum team consists of a product owner, development team, and scrum master. The product owner manages the product backlog. The development team does the work. And the scrum master facilitates scrum processes and removes impediments.
Difference Between Agile And Scrum
The document discusses the differences between Agile and Scrum methodologies for software development. It states that Agile is a broader framework that contains basic principles adopted by different methods, including Scrum. Scrum is described as a more independent methodology focused on project efficiency. The document then provides more details on the Scrum methodology, describing elements like Sprints (iterative development cycles of 1-4 weeks), daily stand-up meetings, and product backlogs to plan work. It notes that while Scrum is very popular, it can face scaling challenges with very large teams. Dividing teams into multiple Scrum of Scrums is proposed as a potential solution to address those challenges.
AGILE PROJECT MANAGEMENT
The document discusses agile project management and agile software development methodologies. It defines agile management as an iterative, incremental approach that aims to provide flexible development of new products or services. Some key points made include:
- Agile methods complete small portions of deliverables in short iterations, while iterative methods evolve all deliverables over time.
- Adaptive project life cycles use very rapid 2-4 week iterations with fixed time and resources.
- Scrum is an agile framework that uses short sprints, daily stand-ups, and emphasizes self-organizing teams and responding quickly to change.
- Scrum roles include the Product Owner who prioritizes work, the Scrum Master who facilitates
SE notes by k. adisesha
The document discusses software engineering and provides an overview of key concepts. It defines software engineering and discusses its need. It describes characteristics of good software and lists factors like operational, transitional, and maintenance characteristics. It also covers software development life cycles and models like the classical waterfall model. The classical waterfall model divides the life cycle into phases like feasibility study, requirements analysis, design, coding/unit testing, and integration/system testing.
DevOps interview questions and answers
The document provides information on various DevOps concepts through a question and answer format. It defines design patterns as solutions to common problems faced by developers that represent best practices. It describes continuous deployment as instrumenting important project life cycle steps when moving code to production. It distinguishes between functional testing which targets business goals and requirements, and non-functional testing which focuses on aspects like performance and security. It explains the differences between white box testing which uses internal knowledge and black box testing which does not. It provides examples of resilience test tools like Hystrix and Chaos Monkey. It describes extreme programming as an agile methodology focused on customer satisfaction and team collaboration. It defines pair programming as two programmers working together on the same code. Finally
Basics Of Software Engineering
What is Software Engineering
Software Characteristics
Types Of Software'S
Layered Technology
Difference Between Software Engineering and Computer Science
ch2-Agile-Software-Development-engineerning.pdf
This document provides an overview of agile software development and extreme programming (XP). It discusses how agile methods aim to rapidly develop and deliver working software through an iterative process with customer collaboration. Key aspects of XP are described, including planning with user stories, small incremental releases, test-driven development, pair programming, collective code ownership, and continuous integration. The document contrasts plan-driven and agile development approaches and outlines some principles and practices of XP such as simple design, refactoring, and sustainable pace of work.
Flavours of agile software engineering
This document provides an overview of agile software development methods. It defines agile as developing software incrementally in rapid cycles with close customer collaboration. The agile manifesto values individuals, working software, customer collaboration, and responding to change. Popular agile methods described include scrum, extreme programming (XP), test-driven development (TDD), and lean. Scrum uses short iterations called sprints, with roles like product owner and scrum master. XP advocates frequent releases and pair programming. TDD involves writing tests before code. Lean aims to maximize value while minimizing waste. Agile frameworks help teams deliver faster with less risk by focusing on customer value.
Flavours of agile software engineering
This document provides an overview of agile software development methods. It defines agile as developing software incrementally in rapid cycles with close customer collaboration. The agile manifesto values individuals, working software, customer collaboration, and responding to change. Popular agile methods described include scrum, extreme programming (XP), test-driven development (TDD), and lean. Scrum uses short iterations called sprints, with roles like product owner and scrum master. XP advocates frequent releases and pair programming. TDD involves writing tests before code. Lean aims to maximize value while minimizing waste. Agile frameworks help teams deliver faster with less risk by focusing on customer value.
Reducing Cost With Agile
The document discusses how adopting Agile practices can help reduce costs and increase project success rates. It provides an overview of the Agile manifesto and techniques like iterative development, improved communication, and leverage existing investments. Adopting Agile can lead to reduced inventory, quick turnaround focusing on required functionality, minimizing costs, and delivering working software sooner to generate savings and quicker time to market. This allows for a focus on ROI and increased project success rates through improved quality, productivity, visibility for customers, and alignment between business and technology needs.
Top 5 DevSecOps Tools- You Need to Know About
The increased efficiency brought about by DevSecOps Tools can be attributed to its ability to streamline processes across all three groups involved: development, operations and security teams. For example, if there's an issue with your application's code or infrastructure configuration that needs fixing before it goes live on production servers (i.e., somewhere where users could see it), this process will now happen much faster because everyone involved has access to all relevant information at once instead of having separate conversations between each individual group member who might not know what another person knows about a particular problem area within their respective domains
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...
Direct losses from downtime in 1 minute = $5-$10 thousand dollars. Reputation is priceless.
As part of the talk, we will consider the architectural strategies necessary for the development of highly loaded fintech solutions. We will focus on using queues and streaming to efficiently work and manage large amounts of data in real-time and to minimize latency.
We will focus special attention on the architectural patterns used in the design of the fintech system, microservices and event-driven architecture, which ensure scalability, fault tolerance, and consistency of the entire system.
More Related Content
Similar to Framework-less Applications
How To Implement DevSecOps In Your Existing DevOps Workflow
Prioritizing DevOps without considering security can be dangerous. So how can security be implemented within a DevOps team? Adapt to DevSecOps and see how it assists you in developing your implementation technique. This blog will provide a comprehensive understanding of the DevSecOps methodology.
Agile software development
Overview of the agile software development. This contents was originally created for my team's internal workshop. It includes basic concept of the agile software development, and introduction of some practices and tools for it.
Glossary of Agile Terms
An A - Z glossary of terms for agile methodology, designed to help businesses understand the terminology used by technical software development teams.
Breaking Tradition: Agile Frameworks For The Modern Era of Collaborative Proj...
Agile software development is an application development methodology emphasizing an iterative process in which cross-functional teams collaborate to produce superior solutions. Agile frameworks are distinct development methods or techniques that adhere to Agile principles. The majority of businesses utilize these frameworks to address their particular needs.
Benefits of Agile Software Development for Senior Management
This is a presentation to Senior and Executive Managers which is used to explain how Agile Software Development processes and practices benefit them, their organization and their customers.
331103344.ppt
The document discusses agile process models and compares plan-driven and agile development approaches. Agile development involves interleaving program specification, design, and implementation. The system is developed through frequent delivery of new versions for stakeholder evaluation. Agile aims to reduce overheads and quickly respond to changing requirements through practices like minimal documentation and extensive automated testing.
Scrum Awareness 2.0.1
Here are the estimates for the paper town buildings in story points:
House: 3 story points
Villa: 5 story points
Apartment Building: 8 story points
Fire Department: 13 story points
02_Introduction to Software Engineering(1).pptx
Dokuemen ini merupakan materi ajar matakuliah Rekayasa Perangkat Lunak. Materi ini merupakan materi awal yang berisi:
What is Engineering?
What is Software?
Software Applications
Software—New Categories
A Software Engineering
What is Software Engineering?
A Layered Technology
Software Development Life Cycle
The document discusses software engineering and the software development life cycle (SDLC). It defines key terms like system software, application software, and network-based software. It describes the characteristics of well-engineered software and lists the typical phases in the SDLC: analysis, design, coding, testing, implementation, maintenance, and re-engineering. The advantages of following the SDLC are also highlighted.
Scrum presentation jyoti
Scrum is an agile process that focuses on delivering business value in the shortest time. It delivers working software in short iterations called sprints. The key aspects of scrum include user stories to define requirements, a product backlog to track and prioritize work, sprint planning and daily standups to coordinate work within a sprint, and sprint reviews and retrospectives after each sprint to inspect progress and improve processes. The scrum team consists of a product owner, development team, and scrum master. The product owner manages the product backlog. The development team does the work. And the scrum master facilitates scrum processes and removes impediments.
Difference Between Agile And Scrum
The document discusses the differences between Agile and Scrum methodologies for software development. It states that Agile is a broader framework that contains basic principles adopted by different methods, including Scrum. Scrum is described as a more independent methodology focused on project efficiency. The document then provides more details on the Scrum methodology, describing elements like Sprints (iterative development cycles of 1-4 weeks), daily stand-up meetings, and product backlogs to plan work. It notes that while Scrum is very popular, it can face scaling challenges with very large teams. Dividing teams into multiple Scrum of Scrums is proposed as a potential solution to address those challenges.
AGILE PROJECT MANAGEMENT
The document discusses agile project management and agile software development methodologies. It defines agile management as an iterative, incremental approach that aims to provide flexible development of new products or services. Some key points made include:
- Agile methods complete small portions of deliverables in short iterations, while iterative methods evolve all deliverables over time.
- Adaptive project life cycles use very rapid 2-4 week iterations with fixed time and resources.
- Scrum is an agile framework that uses short sprints, daily stand-ups, and emphasizes self-organizing teams and responding quickly to change.
- Scrum roles include the Product Owner who prioritizes work, the Scrum Master who facilitates
SE notes by k. adisesha
The document discusses software engineering and provides an overview of key concepts. It defines software engineering and discusses its need. It describes characteristics of good software and lists factors like operational, transitional, and maintenance characteristics. It also covers software development life cycles and models like the classical waterfall model. The classical waterfall model divides the life cycle into phases like feasibility study, requirements analysis, design, coding/unit testing, and integration/system testing.
DevOps interview questions and answers
The document provides information on various DevOps concepts through a question and answer format. It defines design patterns as solutions to common problems faced by developers that represent best practices. It describes continuous deployment as instrumenting important project life cycle steps when moving code to production. It distinguishes between functional testing which targets business goals and requirements, and non-functional testing which focuses on aspects like performance and security. It explains the differences between white box testing which uses internal knowledge and black box testing which does not. It provides examples of resilience test tools like Hystrix and Chaos Monkey. It describes extreme programming as an agile methodology focused on customer satisfaction and team collaboration. It defines pair programming as two programmers working together on the same code. Finally
Basics Of Software Engineering
What is Software Engineering
Software Characteristics
Types Of Software'S
Layered Technology
Difference Between Software Engineering and Computer Science
ch2-Agile-Software-Development-engineerning.pdf
This document provides an overview of agile software development and extreme programming (XP). It discusses how agile methods aim to rapidly develop and deliver working software through an iterative process with customer collaboration. Key aspects of XP are described, including planning with user stories, small incremental releases, test-driven development, pair programming, collective code ownership, and continuous integration. The document contrasts plan-driven and agile development approaches and outlines some principles and practices of XP such as simple design, refactoring, and sustainable pace of work.
Flavours of agile software engineering
This document provides an overview of agile software development methods. It defines agile as developing software incrementally in rapid cycles with close customer collaboration. The agile manifesto values individuals, working software, customer collaboration, and responding to change. Popular agile methods described include scrum, extreme programming (XP), test-driven development (TDD), and lean. Scrum uses short iterations called sprints, with roles like product owner and scrum master. XP advocates frequent releases and pair programming. TDD involves writing tests before code. Lean aims to maximize value while minimizing waste. Agile frameworks help teams deliver faster with less risk by focusing on customer value.
Flavours of agile software engineering
This document provides an overview of agile software development methods. It defines agile as developing software incrementally in rapid cycles with close customer collaboration. The agile manifesto values individuals, working software, customer collaboration, and responding to change. Popular agile methods described include scrum, extreme programming (XP), test-driven development (TDD), and lean. Scrum uses short iterations called sprints, with roles like product owner and scrum master. XP advocates frequent releases and pair programming. TDD involves writing tests before code. Lean aims to maximize value while minimizing waste. Agile frameworks help teams deliver faster with less risk by focusing on customer value.
Reducing Cost With Agile
The document discusses how adopting Agile practices can help reduce costs and increase project success rates. It provides an overview of the Agile manifesto and techniques like iterative development, improved communication, and leverage existing investments. Adopting Agile can lead to reduced inventory, quick turnaround focusing on required functionality, minimizing costs, and delivering working software sooner to generate savings and quicker time to market. This allows for a focus on ROI and increased project success rates through improved quality, productivity, visibility for customers, and alignment between business and technology needs.
Top 5 DevSecOps Tools- You Need to Know About
The increased efficiency brought about by DevSecOps Tools can be attributed to its ability to streamline processes across all three groups involved: development, operations and security teams. For example, if there's an issue with your application's code or infrastructure configuration that needs fixing before it goes live on production servers (i.e., somewhere where users could see it), this process will now happen much faster because everyone involved has access to all relevant information at once instead of having separate conversations between each individual group member who might not know what another person knows about a particular problem area within their respective domains
Similar to Framework-less Applications (20)
How To Implement DevSecOps In Your Existing DevOps Workflow
How To Implement DevSecOps In Your Existing DevOps Workflow
Breaking Tradition: Agile Frameworks For The Modern Era of Collaborative Proj...
Breaking Tradition: Agile Frameworks For The Modern Era of Collaborative Proj...
Benefits of Agile Software Development for Senior Management
Benefits of Agile Software Development for Senior Management
Recently uploaded
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...
Direct losses from downtime in 1 minute = $5-$10 thousand dollars. Reputation is priceless.
As part of the talk, we will consider the architectural strategies necessary for the development of highly loaded fintech solutions. We will focus on using queues and streaming to efficiently work and manage large amounts of data in real-time and to minimize latency.
We will focus special attention on the architectural patterns used in the design of the fintech system, microservices and event-driven architecture, which ensure scalability, fault tolerance, and consistency of the entire system.
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
This is a session that details how PostgreSQL's features and Azure AI Services can be effectively used to significantly enhance the search functionality in any application.
In this session, we'll share insights on how we used PostgreSQL to facilitate precise searches across multiple fields in our mobile application. The techniques include using LIKE and ILIKE operators and integrating a trigram-based search to handle potential misspellings, thereby increasing the search accuracy.
We'll also discuss how the azure_ai extension on PostgreSQL databases in Azure and Azure AI Services were utilized to create vectors from user input, a feature beneficial when users wish to find specific items based on text prompts. While our application's case study involves a drug search, the techniques and principles shared in this session can be adapted to improve search functionality in a wide range of applications. Join us to learn how PostgreSQL and Azure AI can be harnessed to enhance your application's search capability.
inQuba Webinar Mastering Customer Journey Management with Dr Graham Hill
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
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?
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).
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Leveraging the Graph for Clinical Trials and Standards
Katja Glaß
OpenStudyBuilder Community Manager - Katja Glaß Consulting
Marius Conjeaud
Principal Consultant - 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.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
A Deep Dive into ScyllaDB's Architecture
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
This LF Energy webinar took place June 20, 2024. It featured:
-Alex Thornton, LF Energy
-Hallie Cramer, Google
-Daniel Roesler, UtilityAPI
-Henry Richardson, WattTime
In response to the urgency and scale required to effectively address climate change, open source solutions offer significant potential for driving innovation and progress. Currently, there is a growing demand for standardization and interoperability in energy data and modeling. Open source standards and specifications within the energy sector can also alleviate challenges associated with data fragmentation, transparency, and accessibility. At the same time, it is crucial to consider privacy and security concerns throughout the development of open source platforms.
This webinar will delve into the motivations behind establishing LF Energy’s Carbon Data Specification Consortium. It will provide an overview of the draft specifications and the ongoing progress made by the respective working groups.
Three primary specifications will be discussed:
-Discovery and client registration, emphasizing transparent processes and secure and private access
-Customer data, centering around customer tariffs, bills, energy usage, and full consumption disclosure
-Power systems data, focusing on grid data, inclusive of transmission and distribution networks, generation, intergrid power flows, and market settlement data
[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.
QA or the Highway - Component Testing: Bridging the gap between frontend appl...
These are the slides for the presentation, "Component Testing: Bridging the gap between frontend applications" that was presented at QA or the Highway 2024 in Columbus, OH by Zachary Hamm.
"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.
The Microsoft 365 Migration Tutorial For Beginner.pptx
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Day 2 - Intro to UiPath Studio Fundamentals
In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project.
📕 Detailed agenda:
Variables and Datatypes
Workflow Layouts
Arguments
Control Flows and Loops
Conditional Statements
💻 Extra training through UiPath Academy:
Variables, Constants, and Arguments in Studio
Control Flow in Studio
Recently uploaded (20)
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
inQuba Webinar Mastering Customer Journey Management with Dr Graham Hill
inQuba Webinar Mastering Customer Journey Management with Dr Graham Hill
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Leveraging the Graph for Clinical Trials and Standards
Leveraging the Graph for Clinical Trials and Standards
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
QA or the Highway - Component Testing: Bridging the gap between frontend appl...
QA or the Highway - Component Testing: Bridging the gap between frontend appl...
The Microsoft 365 Migration Tutorial For Beginner.pptx
The Microsoft 365 Migration Tutorial For Beginner.pptx
Framework-less Applications
- 3. The Sceptical Programmer's Manifesto While there is value in the items on the right, we value the items on the left more
- 4. The Sceptical Programmer's Manifesto explicit implicit>
- 5. The Sceptical Programmer's Manifesto explicit implicit> transparency abstraction>
- 6. The Sceptical Programmer's Manifesto explicit implicit> transparency abstraction> utility enforced structure>
- 7. The Sceptical Programmer's Manifesto explicit implicit> transparency abstraction> utility enforced structure> focused tools all-in-one solutions>
- 8. The Sceptical Programmer's Manifesto explicit implicit> transparency abstraction> utility enforced structure> focused tools all-in-one solutions> ease of change ease of use>
- 9. The Sceptical Programmer's Manifesto explicit implicit> transparency abstraction> utility enforced structure> focused tools all-in-one solutions> ease of change ease of use> learning the standards learning derivative tools>
- 10. Idiot-proof ?