Ssi maintainers
•Download as PPTX, PDF•
0 likes•188 views
The document discusses enabling smooth transitions between software maintainers. It suggests that when inducting a new maintainer, an experienced maintainer should discuss the software's design, develop code together, and walk through the code. For self-guided learning, documentation like user docs, tests, design docs and commented source code can help navigate understanding. When inheriting a large codebase, inspecting the code, documenting assumptions and designs, and writing tests and user docs creates resources to help future maintainers. Well structured code with tests that demonstrate functionality form a minimal effective handover.
Report
Share
Report
Share
Recommended
Clean code chpt_1
The document discusses clean code and defines it as code that is simple, direct, and readable. It provides definitions of clean code from experts like Bjarne Stroustrup, Grady Booch, Dave Thomas, Ron Jeffries, and Robert Martin. Clean code is code that can be easily understood by other developers, has tests, meaningful names, minimal dependencies, and expresses design ideas clearly. The document emphasizes that code readability is more important than writability since code is read much more often than written.
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
The document discusses test-driven development (TDD). TDD is a software development process where test cases are created to specify requirements before code is written to pass those tests. This ensures code meets requirements. Benefits of TDD include fewer bugs due to comprehensive testing, and ability to refactor code without breaking functionality. The document provides examples of different types of tests and outlines best practices for getting started with TDD.
Code Quality
The document discusses the importance of code quality and maintaining clean code. It provides principles for writing clean code such as the Boy Scout Rule, DRY principle, and Single Responsibility Principle. Pair programming and code reviews are recommended practices for ensuring code quality. Unit testing using a test-driven development approach helps avoid bugs and allows flexibility. Measuring metrics like test coverage and implementing a coding standard can improve code quality.
Code Quality Assurance
The document discusses code quality assurance and clean code. It begins with an agenda covering why clean code is needed, what constitutes clean code, how to write and test clean code, and how to measure code quality. Writing clean code makes code easier to read, understand and maintain. Clean code follows principles like the single responsibility principle and boy scout rule. Code quality can be measured using tools like Sonar that integrate with build systems like Maven and Ant. While primarily focusing on making code work, practices like clean code aim to produce well-structured and maintainable code.
BDD & Cucumber
When All Teammates Speak The Same Language
Two main problems in software development
It's all about brains
What is BDD?
BDD vs TDD vs ATDD
Three Amigos
Gherkin
Cucumber and Selenium WebDriver
How to use feature files and create steps definitions
Examples
Writing High Quality Code
This document discusses writing high quality code and provides tips for doing so. It states that high quality code should be pleasant to read, abide by standards, be modular, bug-free, finished, clean, documented, and work properly. It emphasizes writing code for others to understand, following naming conventions and style guides, separating an app into small modular components, and ensuring the code is thoroughly tested and documented.
Clean Software Design - DevNot Summit Istanbul 2017
This the content that I shared at DevNot Summit 2017 conference. It mentions my ideas about clean software design.
The five expertise of a software architect
The document discusses the five areas of expertise of a software architect:
1. Technology - Having strong technical skills including writing code, understanding technologies, and solving difficult problems.
2. Technical communication - Effectively communicating technical concepts to both technical and non-technical audiences.
3. Human communication - Having strong empathy, influencing, and communication skills to work with various teams.
4. Domain knowledge - Understanding the business domain including customers, competitors, and market factors.
5. Architectural methods - Applying design principles, patterns, and processes to software architecture.
Recommended
Clean code chpt_1
The document discusses clean code and defines it as code that is simple, direct, and readable. It provides definitions of clean code from experts like Bjarne Stroustrup, Grady Booch, Dave Thomas, Ron Jeffries, and Robert Martin. Clean code is code that can be easily understood by other developers, has tests, meaningful names, minimal dependencies, and expresses design ideas clearly. The document emphasizes that code readability is more important than writability since code is read much more often than written.
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
The document discusses test-driven development (TDD). TDD is a software development process where test cases are created to specify requirements before code is written to pass those tests. This ensures code meets requirements. Benefits of TDD include fewer bugs due to comprehensive testing, and ability to refactor code without breaking functionality. The document provides examples of different types of tests and outlines best practices for getting started with TDD.
Code Quality
The document discusses the importance of code quality and maintaining clean code. It provides principles for writing clean code such as the Boy Scout Rule, DRY principle, and Single Responsibility Principle. Pair programming and code reviews are recommended practices for ensuring code quality. Unit testing using a test-driven development approach helps avoid bugs and allows flexibility. Measuring metrics like test coverage and implementing a coding standard can improve code quality.
Code Quality Assurance
The document discusses code quality assurance and clean code. It begins with an agenda covering why clean code is needed, what constitutes clean code, how to write and test clean code, and how to measure code quality. Writing clean code makes code easier to read, understand and maintain. Clean code follows principles like the single responsibility principle and boy scout rule. Code quality can be measured using tools like Sonar that integrate with build systems like Maven and Ant. While primarily focusing on making code work, practices like clean code aim to produce well-structured and maintainable code.
BDD & Cucumber
When All Teammates Speak The Same Language
Two main problems in software development
It's all about brains
What is BDD?
BDD vs TDD vs ATDD
Three Amigos
Gherkin
Cucumber and Selenium WebDriver
How to use feature files and create steps definitions
Examples
Writing High Quality Code
This document discusses writing high quality code and provides tips for doing so. It states that high quality code should be pleasant to read, abide by standards, be modular, bug-free, finished, clean, documented, and work properly. It emphasizes writing code for others to understand, following naming conventions and style guides, separating an app into small modular components, and ensuring the code is thoroughly tested and documented.
Clean Software Design - DevNot Summit Istanbul 2017
This the content that I shared at DevNot Summit 2017 conference. It mentions my ideas about clean software design.
The five expertise of a software architect
The document discusses the five areas of expertise of a software architect:
1. Technology - Having strong technical skills including writing code, understanding technologies, and solving difficult problems.
2. Technical communication - Effectively communicating technical concepts to both technical and non-technical audiences.
3. Human communication - Having strong empathy, influencing, and communication skills to work with various teams.
4. Domain knowledge - Understanding the business domain including customers, competitors, and market factors.
5. Architectural methods - Applying design principles, patterns, and processes to software architecture.
Infinum Android Talks #19 - Stop wasting time fixing bugs with TDD by Domagoj...
1. This document discusses how test-driven development (TDD) using tools like Robolectric, Dagger, and Mock Web Server can help fix bugs and develop Android applications more efficiently.
2. It describes the author's experience transitioning from not writing any tests to learning how to implement TDD for a new project using these tools.
3. Advice is provided on how to get started with TDD, including creating layouts, writing tests before application logic, and being able to debug and mock responses while developing features faster.
The Role of the Software Architect (short version)
Talk at the First Israeli Conference on Software Architecture
http://www.iltam.org/sw-arch2014/
Abstract:
In this talk Hayim will present the practical aspects of the role of the Software Architect, including the architect's contribution at the diverse stages of the software development life cycle, and the cooperation with the diverse stakeholders: Developers, Team Leaders, Project Managers, QA and Technical Writers.
Bio: Hayim Makabee was born in Rio de Janeiro. He immigrated to Israel in 1992 and completed his M.Sc. studies on Computer Sciences at the Technion. Since then he worked for several hi-tech companies, including also some start-ups. Currently he is a Research Engineer at Yahoo! Labs Haifa. He is also a co-founder of the International Association of Software Architects in Israel.
Computer software specialists wikki verma
Wikki Verma Suggest Before opening an IT consultancy, I did my homework. I interviewed lifelong consultants. I read books. I even took personality tests to confirm that my psychological constitution matched the challenges I did face as an entrepreneur owning and operating my own business.
BDD with the Cucumber
Behaviour Driven Development with The Cucumber
Test Pyramid
BDD Concept
Why BDD
Traditional Loop
Collaboration
Cucumber is the Tool
Cucumber structure
Sample feature
Gherkin is the Language
Step Definitions
Reqular Expressions
How the Cucumber Works
Expressive Scenarios
Outside-in development
Keeping your cucumbers sweet
Environment
Conclusion
Designing with tests
Unit tests are great, they help a developer gain control over his code and catch bugs and regression issues.
Test Driven Development is a methodology that uses unit tests but it's not about writing unit tests - in fact the tests are only a design tool.
TDD is a methodology that solves problems in an iterative way, it's about emergent design that creates a maintainable solution.
In this session I'll talk about common mistakes and misconceptions, how to benefit from TDD and show how to design your code using unit tests.
The code for this talk can be found on GitHub: https://github.com/dhelper/DesignWIthTests
Unwritten Manual for Pair Programming
This document discusses pair programming and provides guidance on how to effectively implement it. It begins by explaining the purpose of pair programming is to produce high quality software. It then discusses various pairing techniques like ping-pong pairing and mob programming. The document also identifies benefits like higher quality code and faster defect removal, as well as challenges like being tiring. Finally, it provides tips for making pairing work well such as starting with a defined task, switching roles frequently, and not forcing people who strongly dislike pairing.
Global Day of Coderetreat'14 - Istanbul Event
These are the slides we used during Istanbul/Turkey event of Global Day of Coderetreat on November 15th, 2014.
Introducing systems analysis, design & development Concepts
Basic concept on Systems/Software Analysis, Design & Development, how software engineering, large projects are done, collaborated, best practices & standards.
“One man” development process model
This document outlines the "One Man" development process model for managing projects as a solo developer. It describes common problems with earlier approaches, such as producing low-quality codebases and fear of changing code. The presented model focuses on designing software, writing tests, documenting code, and releasing in small versions to improve code quality and allow for stable releases. Key techniques include breaking work into features and versions, writing tests and documentation, using tools like source control and issue tracking, and following a workflow of coding, testing, refactoring and releasing features.
성공적인코드리뷰 문화 사내 발표
The document discusses tips for a successful code review. It outlines three types of code reviews: pair programming, formal code review, and lightweight code review. It emphasizes that code reviews should focus on improving code quality and sharing knowledge, rather than finding faults. Reviewers are advised to ask questions instead of making statements, avoid "why" questions, and keep discussions focused on code instead of people. Writers should document code and allow time before reviews.
DSpace 7 - Creating High-Quality Software: Update to Development Practices
Presentation given at OR2019 in Hamburg
DSpace 7 has offered the opportunity to enforce and improve practices introduced in previous years in the DSpace development process [1] moving forward to a Test-Driven Development (TDD) process. The presentation will provide an overview of the current practices and processes used from DSpace 7 on with regard to the test, development and documentation of the software: concrete examples about how to report a bug, solve a bug, propose and develop a new feature will be presented.
The use of the git branch and github PRs [2] will be shown to illustrate how automatic testing helps to quickly validate changes, discover impact on unexpected points in the software and collaboratively improve the proposed solution. This will demonstrate the value of new requirements about code styling [3], code documentation, raising the test coverage and recommendation to provide automatic test to uncover found bugs. The introduction of community development sprints [4] provides community developers the opportunity to learn the new development processes in a hands-on fashion, with the help of fellow developers and coaches.
The introduction of new DSpace docker images [5] (for each published branch) helps to simplify the development process by allowing developers to more easily test, validate and manage code changes against multiple versions of DSpace..
Finally, the REST contract [6] and the use of wireframes [7] will be presented as best practices to support early sharing of ideas and development proposals, and to drive uniformity in the implementation both on the REST and on the Angular side.
Integration Testing for Polyglot Ecosystems
This brief talk introduces a Docker-backed testing harness for conducting integration tests on systems that are built in multiple languages and on multiple platforms.
Code detox
How to achieved code smell From Zero to full applied?
Highlighted the following aspects:
API Design
Styling
Linter
Your Journey to the Uknown: A tale of how I debunk new codebases.
The document discusses strategies for contributing to new codebases, including identifying patterns in the codebase such as frameworks or libraries used. It recommends reading documentation, checking requirements, using online resources like Google and Slack, and paying attention to identify patterns. Unit tests are described as documentation for programmers. The author thanks the reader and provides contact information.
CS 584 - Aligning development tools with the way programmers think about code...
This presentation reviews a proposed visual tool for generating source code transformations based on the edit-by-example principle. The tool aims to address limitations of existing approaches like regular expressions, IDE search/replace, and AST-based tools by allowing programmers to intuitively create custom transformations through direct manipulation of code representations. An initial prototype was implemented and evaluated via a user study, which provided insights for future iterations. The tool combines textual and graphical elements to naturally fit programmers' mental models of code structure.
Real life unit testing tools and practices
The document discusses the problems with testing legacy code that lacks isolation, such as slow and brittle tests, and recommends using mocking frameworks to isolate dependencies and enable writing effective unit tests that are quick, readable, focused and robust even as code changes over time. It also provides examples of hand-rolled mocks and mocking frameworks, and guidelines for writing good unit tests.
Talent42 2017: Mei Lu - 1_Pager Software Developer Job Descriptions
This job description lacks clarity and specificity, which could confuse candidates. It does not clearly define the role or responsibilities, and lists qualifications too broadly without indicating which are required versus optional. The ideal candidate section also does not distinguish between minimum and desired qualifications, so applicants may not know which skills are most important for the role. Overall, the description would benefit from more focused language to provide candidates a clear understanding of the position and what is expected.
10 Faulty Behaviors of Code Review - Developer Summit Istanbul 2018
The document outlines 10 faulty behaviors that can occur during the code review process and provides recommendations to address each one. The behaviors include having no standards for code reviews in the team, providing ambiguous content for review, selecting the wrong reviewers, requesting feedback too late in the process, not understanding what the code change is doing, treating the code as solely the author's work, trying to prove others are wrong instead of having constructive discussions, not being able to convince others with review comments, reviewers not providing feedback on pull requests, and prematurely merging pull requests before the review is finished. For each behavior, the document recommends actions like establishing review standards and processes, providing better context for reviews, selecting appropriate reviewers, reviewing code earlier, adding tests
Characteristics of Excellent Software Engineers, by Lee Bob Black
Excellent software engineers have several key characteristics:
1. They are passionate about coding and love figuring out how systems work.
2. They are dedicated to getting work done efficiently and regularly improving their code.
3. They are merciless in debugging and removing all errors from their code to ensure high quality and availability.
4. They are naturally curious and experimental to continuously innovate and bring visions to life through code.
Coding Dojo - Refactoring Tennis Kata
This document outlines an exercise for practicing refactoring code through pair programming. Developers pair up to refactor a tennis scoring program, taking turns coding on one shared computer every 7 minutes. The goals are to learn refactoring techniques, improve code design through applying principles like removing duplication and revealing intention, and perform small, tested changes to restructure the code without altering its functionality.
Digital Economies Southampton
This talk was presented by Simon Hettrick at the University of Southampton, Digital Economies Christmas Party.
The talk covered three activities of the Software Sustainability Institute: the Collaborations Workshop, the Agents network and Ask Steve!
Preserving software workshop - Community engagement workshop
A presentation by Matt Shreeve from curtis+cartwright Consulting Ltd..
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010
More Related Content
What's hot
Infinum Android Talks #19 - Stop wasting time fixing bugs with TDD by Domagoj...
1. This document discusses how test-driven development (TDD) using tools like Robolectric, Dagger, and Mock Web Server can help fix bugs and develop Android applications more efficiently.
2. It describes the author's experience transitioning from not writing any tests to learning how to implement TDD for a new project using these tools.
3. Advice is provided on how to get started with TDD, including creating layouts, writing tests before application logic, and being able to debug and mock responses while developing features faster.
The Role of the Software Architect (short version)
Talk at the First Israeli Conference on Software Architecture
http://www.iltam.org/sw-arch2014/
Abstract:
In this talk Hayim will present the practical aspects of the role of the Software Architect, including the architect's contribution at the diverse stages of the software development life cycle, and the cooperation with the diverse stakeholders: Developers, Team Leaders, Project Managers, QA and Technical Writers.
Bio: Hayim Makabee was born in Rio de Janeiro. He immigrated to Israel in 1992 and completed his M.Sc. studies on Computer Sciences at the Technion. Since then he worked for several hi-tech companies, including also some start-ups. Currently he is a Research Engineer at Yahoo! Labs Haifa. He is also a co-founder of the International Association of Software Architects in Israel.
Computer software specialists wikki verma
Wikki Verma Suggest Before opening an IT consultancy, I did my homework. I interviewed lifelong consultants. I read books. I even took personality tests to confirm that my psychological constitution matched the challenges I did face as an entrepreneur owning and operating my own business.
BDD with the Cucumber
Behaviour Driven Development with The Cucumber
Test Pyramid
BDD Concept
Why BDD
Traditional Loop
Collaboration
Cucumber is the Tool
Cucumber structure
Sample feature
Gherkin is the Language
Step Definitions
Reqular Expressions
How the Cucumber Works
Expressive Scenarios
Outside-in development
Keeping your cucumbers sweet
Environment
Conclusion
Designing with tests
Unit tests are great, they help a developer gain control over his code and catch bugs and regression issues.
Test Driven Development is a methodology that uses unit tests but it's not about writing unit tests - in fact the tests are only a design tool.
TDD is a methodology that solves problems in an iterative way, it's about emergent design that creates a maintainable solution.
In this session I'll talk about common mistakes and misconceptions, how to benefit from TDD and show how to design your code using unit tests.
The code for this talk can be found on GitHub: https://github.com/dhelper/DesignWIthTests
Unwritten Manual for Pair Programming
This document discusses pair programming and provides guidance on how to effectively implement it. It begins by explaining the purpose of pair programming is to produce high quality software. It then discusses various pairing techniques like ping-pong pairing and mob programming. The document also identifies benefits like higher quality code and faster defect removal, as well as challenges like being tiring. Finally, it provides tips for making pairing work well such as starting with a defined task, switching roles frequently, and not forcing people who strongly dislike pairing.
Global Day of Coderetreat'14 - Istanbul Event
These are the slides we used during Istanbul/Turkey event of Global Day of Coderetreat on November 15th, 2014.
Introducing systems analysis, design & development Concepts
Basic concept on Systems/Software Analysis, Design & Development, how software engineering, large projects are done, collaborated, best practices & standards.
“One man” development process model
This document outlines the "One Man" development process model for managing projects as a solo developer. It describes common problems with earlier approaches, such as producing low-quality codebases and fear of changing code. The presented model focuses on designing software, writing tests, documenting code, and releasing in small versions to improve code quality and allow for stable releases. Key techniques include breaking work into features and versions, writing tests and documentation, using tools like source control and issue tracking, and following a workflow of coding, testing, refactoring and releasing features.
성공적인코드리뷰 문화 사내 발표
The document discusses tips for a successful code review. It outlines three types of code reviews: pair programming, formal code review, and lightweight code review. It emphasizes that code reviews should focus on improving code quality and sharing knowledge, rather than finding faults. Reviewers are advised to ask questions instead of making statements, avoid "why" questions, and keep discussions focused on code instead of people. Writers should document code and allow time before reviews.
DSpace 7 - Creating High-Quality Software: Update to Development Practices
Presentation given at OR2019 in Hamburg
DSpace 7 has offered the opportunity to enforce and improve practices introduced in previous years in the DSpace development process [1] moving forward to a Test-Driven Development (TDD) process. The presentation will provide an overview of the current practices and processes used from DSpace 7 on with regard to the test, development and documentation of the software: concrete examples about how to report a bug, solve a bug, propose and develop a new feature will be presented.
The use of the git branch and github PRs [2] will be shown to illustrate how automatic testing helps to quickly validate changes, discover impact on unexpected points in the software and collaboratively improve the proposed solution. This will demonstrate the value of new requirements about code styling [3], code documentation, raising the test coverage and recommendation to provide automatic test to uncover found bugs. The introduction of community development sprints [4] provides community developers the opportunity to learn the new development processes in a hands-on fashion, with the help of fellow developers and coaches.
The introduction of new DSpace docker images [5] (for each published branch) helps to simplify the development process by allowing developers to more easily test, validate and manage code changes against multiple versions of DSpace..
Finally, the REST contract [6] and the use of wireframes [7] will be presented as best practices to support early sharing of ideas and development proposals, and to drive uniformity in the implementation both on the REST and on the Angular side.
Integration Testing for Polyglot Ecosystems
This brief talk introduces a Docker-backed testing harness for conducting integration tests on systems that are built in multiple languages and on multiple platforms.
Code detox
How to achieved code smell From Zero to full applied?
Highlighted the following aspects:
API Design
Styling
Linter
Your Journey to the Uknown: A tale of how I debunk new codebases.
The document discusses strategies for contributing to new codebases, including identifying patterns in the codebase such as frameworks or libraries used. It recommends reading documentation, checking requirements, using online resources like Google and Slack, and paying attention to identify patterns. Unit tests are described as documentation for programmers. The author thanks the reader and provides contact information.
CS 584 - Aligning development tools with the way programmers think about code...
This presentation reviews a proposed visual tool for generating source code transformations based on the edit-by-example principle. The tool aims to address limitations of existing approaches like regular expressions, IDE search/replace, and AST-based tools by allowing programmers to intuitively create custom transformations through direct manipulation of code representations. An initial prototype was implemented and evaluated via a user study, which provided insights for future iterations. The tool combines textual and graphical elements to naturally fit programmers' mental models of code structure.
Real life unit testing tools and practices
The document discusses the problems with testing legacy code that lacks isolation, such as slow and brittle tests, and recommends using mocking frameworks to isolate dependencies and enable writing effective unit tests that are quick, readable, focused and robust even as code changes over time. It also provides examples of hand-rolled mocks and mocking frameworks, and guidelines for writing good unit tests.
Talent42 2017: Mei Lu - 1_Pager Software Developer Job Descriptions
This job description lacks clarity and specificity, which could confuse candidates. It does not clearly define the role or responsibilities, and lists qualifications too broadly without indicating which are required versus optional. The ideal candidate section also does not distinguish between minimum and desired qualifications, so applicants may not know which skills are most important for the role. Overall, the description would benefit from more focused language to provide candidates a clear understanding of the position and what is expected.
10 Faulty Behaviors of Code Review - Developer Summit Istanbul 2018
The document outlines 10 faulty behaviors that can occur during the code review process and provides recommendations to address each one. The behaviors include having no standards for code reviews in the team, providing ambiguous content for review, selecting the wrong reviewers, requesting feedback too late in the process, not understanding what the code change is doing, treating the code as solely the author's work, trying to prove others are wrong instead of having constructive discussions, not being able to convince others with review comments, reviewers not providing feedback on pull requests, and prematurely merging pull requests before the review is finished. For each behavior, the document recommends actions like establishing review standards and processes, providing better context for reviews, selecting appropriate reviewers, reviewing code earlier, adding tests
Characteristics of Excellent Software Engineers, by Lee Bob Black
Excellent software engineers have several key characteristics:
1. They are passionate about coding and love figuring out how systems work.
2. They are dedicated to getting work done efficiently and regularly improving their code.
3. They are merciless in debugging and removing all errors from their code to ensure high quality and availability.
4. They are naturally curious and experimental to continuously innovate and bring visions to life through code.
Coding Dojo - Refactoring Tennis Kata
This document outlines an exercise for practicing refactoring code through pair programming. Developers pair up to refactor a tennis scoring program, taking turns coding on one shared computer every 7 minutes. The goals are to learn refactoring techniques, improve code design through applying principles like removing duplication and revealing intention, and perform small, tested changes to restructure the code without altering its functionality.
What's hot (20)
Infinum Android Talks #19 - Stop wasting time fixing bugs with TDD by Domagoj...
Infinum Android Talks #19 - Stop wasting time fixing bugs with TDD by Domagoj...
The Role of the Software Architect (short version)
The Role of the Software Architect (short version)
Introducing systems analysis, design & development Concepts
Introducing systems analysis, design & development Concepts
DSpace 7 - Creating High-Quality Software: Update to Development Practices
DSpace 7 - Creating High-Quality Software: Update to Development Practices
Your Journey to the Uknown: A tale of how I debunk new codebases.
Your Journey to the Uknown: A tale of how I debunk new codebases.
CS 584 - Aligning development tools with the way programmers think about code...
CS 584 - Aligning development tools with the way programmers think about code...
Talent42 2017: Mei Lu - 1_Pager Software Developer Job Descriptions
Talent42 2017: Mei Lu - 1_Pager Software Developer Job Descriptions
10 Faulty Behaviors of Code Review - Developer Summit Istanbul 2018
10 Faulty Behaviors of Code Review - Developer Summit Istanbul 2018
Characteristics of Excellent Software Engineers, by Lee Bob Black
Characteristics of Excellent Software Engineers, by Lee Bob Black
Viewers also liked
Digital Economies Southampton
This talk was presented by Simon Hettrick at the University of Southampton, Digital Economies Christmas Party.
The talk covered three activities of the Software Sustainability Institute: the Collaborations Workshop, the Agents network and Ask Steve!
Preserving software workshop - Community engagement workshop
A presentation by Matt Shreeve from curtis+cartwright Consulting Ltd..
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010
Sustainability Training Workshop - Managing Sustainability into Software
Sustainability Training Workshop - Managing Sustainability into SoftwareSoftware Sustainability Institute
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.Managing Code in Repositories
The document discusses code repositories and recommends hosting code online for open source projects. It describes how code repositories provide a safe place to store code, manage changes, and collaborate. It then discusses local versus internet repositories and recommends internet repositories for open source projects to avoid hosting burdens. Several popular online repositories are described, including SourceForge, Google Code, and GitHub.
Governance for Software
The document discusses several key aspects of project governance, ownership, exploitation, and funding for software projects, including:
1) Governance models can range from a single leader to a meritocratic model, and the level of control needs to balance the originator's vision with expanding contribution.
2) Ownership is usually defined by copyright, but gets complicated with many contributors; contribution agreements and a single custodian can help define ownership and accountability.
3) Exploitation considers how the software can move forward commercially or as open source, targeting current and potential new users as well as integrators and partners.
4) Funding can come from grants, donations, services, licensing, or spin-
Supporting Software
The document discusses expanding support for software users by providing multiple avenues of help including email lists, FAQs, tutorials, a public issue tracker, and chat rooms. It emphasizes being honest about quality of service commitments like response times, supported platforms and issue scope, as well as types of support offered such as general help or tailored solutions. Alternative resources are suggested to help users help each other through a public archive and code drops while still ensuring individual requests are addressed.
Lightning talks - Workshop for e-Infrastructure trainers
A summary and all the slides for the lightning talks session at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
Introduction to the Software Sustainability Institute
Introduction to the Software Sustainability Institute and a record of the discussion held at the JISC RI Software Sustainability Workshop on the 12th May 2010.
Engaging the software in research community
The document discusses the Software Sustainability Institute's community engagement efforts, including its Agents/Super Pals program and Fellows program. It recruits early-career and mid-career researchers to gather intelligence, run workshops, and provide feedback. The Fellows program has grown from 10 Agents in 2011 to 15 Fellows in 2013 across various research domains. The goals are to effectively serve the research community, maximize the Institute's impact, and promote awareness of software sustainability best practices.
Introductory Talk - Workshop for e-Infrastructure trainers
The introductory talk given by the Software Sustainability Institute's Simon Hettrick at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
The provision of support and training for e-Infrastructure users and potentia...
The provision of support and training for e-Infrastructure users and potentia...Software Sustainability Institute
Presented by Simon Hettrick at the e-Infrastructure Academic User Community Forum, this talk provides a number of recommendations for improving the provision of training for e-Infrastructure.How does the workshop work?
The document provides information about a workshop hosted at www.software.ac.uk, including details on how it works, the events team members, ways to provide feedback, announcements, an agents network, and collaborative ideas activities. Attendees are encouraged to meet new people, visit the website for information, email (but not attach) documents, and that the workshop is flexible.
Preserving software workshop - Sustainability approaches
A presentation by Neil Chue Hong, Director of the Software Sustainability Institute.
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010.
Issue Tracking
Issue tracking allows organizations to manage changes and bugs in an ordered way. An issue can represent any query, occurrence, or task that may impact a project, such as a software bug, request for change, or action item from a meeting. When an issue is reported, it goes through a typical workflow of being assigned, accepted, worked on, and eventually closed or reopened. Popular open source bug trackers include Bugzilla, Trac, and JIRA, with Trac being a good example of a lightweight yet powerful option that allows cross-referencing with wikis and version control systems.
Viewers also liked (14)
Preserving software workshop - Community engagement workshop
Preserving software workshop - Community engagement workshop
Sustainability Training Workshop - Managing Sustainability into Software
Sustainability Training Workshop - Managing Sustainability into Software
Lightning talks - Workshop for e-Infrastructure trainers
Lightning talks - Workshop for e-Infrastructure trainers
Introduction to the Software Sustainability Institute
Introduction to the Software Sustainability Institute
Introductory Talk - Workshop for e-Infrastructure trainers
Introductory Talk - Workshop for e-Infrastructure trainers
The provision of support and training for e-Infrastructure users and potentia...
The provision of support and training for e-Infrastructure users and potentia...
Preserving software workshop - Sustainability approaches
Preserving software workshop - Sustainability approaches
More from Software Sustainability Institute
SPOTonLondon Data
Introduction from Neil Chue Hong, Director of the Software Sustainability Institute for session on "Publishing Research Data: What’s in it for me?" at Science, Policy, Outreach and Tools Online.
Collaborations Workshop Lightning Talks
These are the combined slides from the lightning talks sessions at the Collaborations Workshop 2012. For speaker information, see: http://www.software.ac.uk/cw12/cw12-topics-lightning-talks
How breakouts work
The document provides instructions for conducting breakout sessions, which include choosing a Chair and Scribe in the first 5 minutes to lead discussion on lessons learned, problems and solutions, further work needed, and resources. In the last 10 minutes, the Scribe distills the group's notes using a template, and the group chooses a presenter to report the results to the larger group via email.
Collaborations Workshop 2012 Introduction to the Software Sustainability Inst...
Collaborations Workshop 2012 Introduction to the Software Sustainability Inst...Software Sustainability Institute
Neil Chue Hong's introduction to the Software Sustainability Institute, presented at the Collaborations Workshop 2012.Digital Social Research
David De Roure's introduction to the Digital Social Research project presented at the Collaborations Workshop 2012.
Adopting Open Source Software for Longer-term Reuse
This document provides guidance on carefully selecting open source software for adoption and long-term reuse. It emphasizes the importance of evaluating several key factors, such as whether the software meets functional requirements both currently and for the future, has an active user and developer community, provides good documentation and support, remains up to date and interoperable with standards, and has a development roadmap that indicates ongoing support. The document advises asking the developer community questions and provides an example of thoroughly evaluating the Taverna workflow system based on these criteria.
Sustainability Training Workshop - Intro to the SSI
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.
Planning your project
Planning is essential for any project that produces software, even if it is research-oriented. Development plans should be detailed enough to provide guidance but not constrain the project. The plan should be useful to the project team and use tools that work best for the individuals involved. The plan should set regular milestones to release work in progress and review progress without locking in scope too early. A product-based approach to planning breaks work down into components that can be estimated, and the plan should include testing, integration, documentation, and release tasks.
More from Software Sustainability Institute (8)
Collaborations Workshop 2012 Introduction to the Software Sustainability Inst...
Collaborations Workshop 2012 Introduction to the Software Sustainability Inst...
Adopting Open Source Software for Longer-term Reuse
Adopting Open Source Software for Longer-term Reuse
Sustainability Training Workshop - Intro to the SSI
Sustainability Training Workshop - Intro to the SSI
Recently uploaded
Project Management Semester Long Project - Acuity
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Digital Marketing Trends in 2024 | Guide for Staying Ahead
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
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.
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
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 .
Recently uploaded (20)
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Ssi maintainers
- 1. Enabling transition between maintainers
- 2. Need to know What it does How it’s used How it works What is where
- 3. Oracle and novice Oracle inducts novice Discuss designs Develop code Walk through code Is there time for this?
- 4. Self-guided Software development > programming User docs Tests Design docs Research papers Commented source code Your navigators
- 5. In at the deep end A mass of source code An idea of what it does DIY Inspect code Document the design and assumptions Write tests Write user doc A resource for those who come next
- 6. A minimal set? Well structured and commented code Tests that embody what it’s meant to do