This document discusses using Go and gRPC for building APIs. It provides an overview of Go and gRPC, recommends resources for learning Go, and discusses using gRPC for communication between a Ruby on Rails API and Go services, with examples like building a gRPC API for etcd.
Gitalist is a Git web interface written in Perl using the Catalyst framework. It aims to provide feature parity with gitweb.cgi while having an easier to extend codebase that better represents modern Perl. The project started by wrapping gitweb.cgi but has evolved over several steps to implement all actions using an object-oriented model without reliance on gitweb.pm. Future work includes adding more tests, improving configurability, and enhancing the interface.
Nordic Testing Days - Tallinn 2017 - Test your Java applications with SpockIván López Martín
Remember the old days when you tested using JUnit? How boring it was? You made a lot of excuses to avoid testing your code. Luckily those dark days now belong to the past because Spock is with us. Spock is a Groovy-based testing and specification framework for Java and Groovy applications that makes writing tests fun again. We can write beautiful and highly expressive tests because of its DSL and all the power that Groovy provides us.
In this live-coding session you'll learn the basics of Spock and you'll see how easily you can test a Java application. After the talk you won't have any excuse to don't test your applications, so you have been warned before coming to the talk!
This document discusses various Git workflows and simulations of software development workflows using games and diagrams. It describes common Git workflows like centralized workflow, Git flow, pull requests, and trunk-based development. It also presents hypothetical scenarios to simulate how different development practices might affect outcomes, such as varying commit frequencies, number of developers, and probabilities of merge conflicts. The document advocates experimenting with simulations to better understand one's own organization's workflows and challenges people to provide feedback to improve the ideas.
ADDO 2019: Looking back at over 10 years of DevopsKris Buytaert
Over the past 10 years of the devops movement:
- DevopsDays global conferences have grown from a single event in 2009 to over 250 events in 2019.
- Topic discussions have evolved from early automation tools to modern topics like containers, cloud platforms, and continuous delivery pipelines.
- While tools are helpful, the speaker emphasizes that culture and collaboration between developers and operations are ultimately more important for organizational success than any specific technology. Adopting devops practices requires change that can be challenging for large enterprises with established cultures.
This document discusses the technologies used to build the Malaysian Bill Watcher application. It uses the Bottle microframework for the backend, Elasticsearch for search via the pyes Python client, and SQLAlchemy for database abstraction. Bootstrap is used for CSS and jQuery for JavaScript. Beautiful Soup is used for web scraping. The talk focuses on how Bottle templates and views work to return JSON and render templates, and how Elasticsearch is used to index and search scraped bill data via the indexer. Future plans include localization, new data sources, moving templates to Jinja, potentially migrating to MongoDB, and improving the scraping.
Kris Buytaert discusses the past, present, and future of DevOps. He notes that while tools and technologies will continue to evolve, collaboration between development and operations remains a key requirement. DevOps adoption also faces challenges like broken certification processes, resistance to change from large organizations, and burnout. Ultimately, DevOps is still a work in progress with many organizations just starting their journeys, and its future will depend on continued education and bridging cultural divides between teams.
This document discusses using Go and gRPC for building APIs. It provides an overview of Go and gRPC, recommends resources for learning Go, and discusses using gRPC for communication between a Ruby on Rails API and Go services, with examples like building a gRPC API for etcd.
Gitalist is a Git web interface written in Perl using the Catalyst framework. It aims to provide feature parity with gitweb.cgi while having an easier to extend codebase that better represents modern Perl. The project started by wrapping gitweb.cgi but has evolved over several steps to implement all actions using an object-oriented model without reliance on gitweb.pm. Future work includes adding more tests, improving configurability, and enhancing the interface.
Nordic Testing Days - Tallinn 2017 - Test your Java applications with SpockIván López Martín
Remember the old days when you tested using JUnit? How boring it was? You made a lot of excuses to avoid testing your code. Luckily those dark days now belong to the past because Spock is with us. Spock is a Groovy-based testing and specification framework for Java and Groovy applications that makes writing tests fun again. We can write beautiful and highly expressive tests because of its DSL and all the power that Groovy provides us.
In this live-coding session you'll learn the basics of Spock and you'll see how easily you can test a Java application. After the talk you won't have any excuse to don't test your applications, so you have been warned before coming to the talk!
This document discusses various Git workflows and simulations of software development workflows using games and diagrams. It describes common Git workflows like centralized workflow, Git flow, pull requests, and trunk-based development. It also presents hypothetical scenarios to simulate how different development practices might affect outcomes, such as varying commit frequencies, number of developers, and probabilities of merge conflicts. The document advocates experimenting with simulations to better understand one's own organization's workflows and challenges people to provide feedback to improve the ideas.
ADDO 2019: Looking back at over 10 years of DevopsKris Buytaert
Over the past 10 years of the devops movement:
- DevopsDays global conferences have grown from a single event in 2009 to over 250 events in 2019.
- Topic discussions have evolved from early automation tools to modern topics like containers, cloud platforms, and continuous delivery pipelines.
- While tools are helpful, the speaker emphasizes that culture and collaboration between developers and operations are ultimately more important for organizational success than any specific technology. Adopting devops practices requires change that can be challenging for large enterprises with established cultures.
This document discusses the technologies used to build the Malaysian Bill Watcher application. It uses the Bottle microframework for the backend, Elasticsearch for search via the pyes Python client, and SQLAlchemy for database abstraction. Bootstrap is used for CSS and jQuery for JavaScript. Beautiful Soup is used for web scraping. The talk focuses on how Bottle templates and views work to return JSON and render templates, and how Elasticsearch is used to index and search scraped bill data via the indexer. Future plans include localization, new data sources, moving templates to Jinja, potentially migrating to MongoDB, and improving the scraping.
Kris Buytaert discusses the past, present, and future of DevOps. He notes that while tools and technologies will continue to evolve, collaboration between development and operations remains a key requirement. DevOps adoption also faces challenges like broken certification processes, resistance to change from large organizations, and burnout. Ultimately, DevOps is still a work in progress with many organizations just starting their journeys, and its future will depend on continued education and bridging cultural divides between teams.
Static analysis tools like PHPStan and Psalm can find bugs in PHP code within seconds by analyzing code without executing it. PHPStan performs static analysis to detect errors in code syntax and functionality. It has different configuration levels and plugins. Psalm is also a PHP static analysis tool that can lint code, support grandfathering in old code, and add new features to help find bugs.
Static analysis tools like PHPStan and Psalm can find bugs in PHP code within seconds by analyzing code without executing it. PHPStan checks for syntax and type errors as well as invalid functionality. Psalm is also a static analysis linting tool that can be configured to validate older codebases while also catching errors in new code. Both tools can help developers find and fix bugs more quickly.
This document provides an introduction to using Git and version control. It explains the basic concepts and workflow of Git, including initializing and committing to a local repository, pushing changes to a remote repository, and using branches for features and releases. It also discusses how to manage Drupal configuration changes using features in Git.
This document provides an introduction to using Git. It discusses key Git concepts like commits, branches, repositories, cloning, pushing and pulling. It recommends always using the command line for hands-on practice. It also provides examples of common Git commands and best practices for commits, branching strategies, and release strategies.
Git and GitHub are tools that software engineers use to collaborate on code and track changes over time. While primarily for software development, GitHub can also be used as a project management tool for any team. Key terms used in GitHub include repositories (folders for projects), branches (versions of code), commits (changes to code), and pull requests (requests to merge changes). As a non-technical professional, understanding these basic GitHub concepts and being able to engage teams there will help facilitate communication and progress on shared work. The document recommends following specific repositories at the company to stay informed on relevant projects.
This document provides an overview and introduction to the Git version control system. It begins with definitions of Git and revision/source code management. It then covers the history and basics of using Git, including initializing and cloning repositories, configuring user settings, and saving changes. It lists some common Git hosting services and concludes with recommendations for learning more about Git.
This document provides an overview and introduction to using the version control system Git. It begins with explaining what version control is and why it is useful for collaboration, storing versions, restoring previous versions, understanding changes, and backup. It then discusses using Git from the command line versus a GUI. The remainder of the document outlines Git's basic workflow, including configuring Git, committing related changes with good commit messages, using branches extensively, never committing half-done work by using stash, keeping the remote in sync, and merging changes. It concludes by inviting the reader to join them in learning more about Git.
KegKong: Automated Keg System, presented at the Flatiron SchoolJordan Trevino
This automated keg system was built at the Flatiron School, using Ruby, Arduino, a Raspberry Pi and most importantly: our trusty keg.
Creators are: Jordan Trevino, Joe Giralt, Chris Gonzales
Mahara UK 2011 Technical Day - Git for MaharaAndrew Nicols
My presentation/workshop from the Mahara UK 2011 technical day.
This gives a quick insight into Git, what git is, some of the useful features of git are, and how it can be used in Mahara.
This document discusses polyglot persistence, which is using multiple data storage technologies in an application. It mentions relation databases, object-relational mapping like Hibernate, and polyglot persistence as described by Martin Fowler. It also includes links about CAP theorem, NoSQL databases, Spring Data solutions, and Hibernate OGM solutions. The document is from @diego_pacheco, a software architect and agile coach thanking people.
This document discusses scraping public transportation data and developing open data projects. It addresses legal issues around scraping, recommends scraping only when necessary and with legal justification. It also discusses design challenges for such projects and encourages collaborating openly and fixing issues together. The overall message is to scrape responsibly when needed, work together as a community, and focus on quick solutions that can be improved over time.
The document outlines an anti-corruption project called unshred.it that aims to use computer vision, artificial intelligence, and machine learning techniques to reconstruct shredded documents. It provides links to the project's documentation and communication channels on Slack and encourages contributions by reviewing documents, adding ideas to the roadmap, filing Github issues, and following coding standards and workflows outlined in the action plan and how-to documentation.
This document provides an overview and agenda for introducing GitLab tools. It discusses trends in modern development like increased use of open source tools and continuous integration/deployment. GitLab is presented as a one platform solution that provides version control, issue tracking, code review, CI/CD pipelines, and other DevOps tools. Key benefits of GitLab like open source contributions and frequent releases are outlined. Upcoming features in GitLab 11 like CI pipelines in the web IDE and license management are previewed. The presentation concludes with a Q&A and information on how to get a GitLab cheat sheet.
This document provides an overview of Google Code-in (GCI) and resources on GitHub. It discusses how GitHub can be used for more than just software, including sharing data, writing, translations, and open company initiatives. It also summarizes GCI tips like choosing a project in advance, getting familiar with tools and communication practices, and practicing communicating without overly formal language. Finally, it introduces the loklak social media harvester project and some example tasks for GCI Challenge 2.
In this presentation, Dmitriy Zaporozhets and Job van der Voort talk about the GitLab Release process and give a guided tour of the new features in 8.4. You can find out why GitLab users always know when the next release is, and how they know what's coming next.
Sql Saturday 895 - SQL Server e PowerShell: from Zero to HeroMarco Obinu
Slides of the session held at SQL Saturday 895 - Parma 2019 about the use of PowerShell in conjunction with SQL Server.
Demo scripts available at https://github.com/OmegaMadLab/SqlPowerShell-FromZeroToHero
Session recording available at https://youtu.be/yR3TfZfzHss
Did you really `got Git? In this presentation for E-commerce at Scale meetup, I talk about why choose Git over other version control systems, Git Flows and also some very useful but not so popular Git features.
Git is a free and open source distributed version control system that allows for collaboration through features like tracking changes, managing versions, and reverting files. It works across operating systems and programming languages. Git uses a local repository that can be synced and shared through remote repositories on services like GitHub and GitLab. Branches allow for parallel development and features like commits, cloning, and pull requests help track changes.
Static analysis tools like PHPStan and Psalm can find bugs in PHP code within seconds by analyzing code without executing it. PHPStan performs static analysis to detect errors in code syntax and functionality. It has different configuration levels and plugins. Psalm is also a PHP static analysis tool that can lint code, support grandfathering in old code, and add new features to help find bugs.
Static analysis tools like PHPStan and Psalm can find bugs in PHP code within seconds by analyzing code without executing it. PHPStan checks for syntax and type errors as well as invalid functionality. Psalm is also a static analysis linting tool that can be configured to validate older codebases while also catching errors in new code. Both tools can help developers find and fix bugs more quickly.
This document provides an introduction to using Git and version control. It explains the basic concepts and workflow of Git, including initializing and committing to a local repository, pushing changes to a remote repository, and using branches for features and releases. It also discusses how to manage Drupal configuration changes using features in Git.
This document provides an introduction to using Git. It discusses key Git concepts like commits, branches, repositories, cloning, pushing and pulling. It recommends always using the command line for hands-on practice. It also provides examples of common Git commands and best practices for commits, branching strategies, and release strategies.
Git and GitHub are tools that software engineers use to collaborate on code and track changes over time. While primarily for software development, GitHub can also be used as a project management tool for any team. Key terms used in GitHub include repositories (folders for projects), branches (versions of code), commits (changes to code), and pull requests (requests to merge changes). As a non-technical professional, understanding these basic GitHub concepts and being able to engage teams there will help facilitate communication and progress on shared work. The document recommends following specific repositories at the company to stay informed on relevant projects.
This document provides an overview and introduction to the Git version control system. It begins with definitions of Git and revision/source code management. It then covers the history and basics of using Git, including initializing and cloning repositories, configuring user settings, and saving changes. It lists some common Git hosting services and concludes with recommendations for learning more about Git.
This document provides an overview and introduction to using the version control system Git. It begins with explaining what version control is and why it is useful for collaboration, storing versions, restoring previous versions, understanding changes, and backup. It then discusses using Git from the command line versus a GUI. The remainder of the document outlines Git's basic workflow, including configuring Git, committing related changes with good commit messages, using branches extensively, never committing half-done work by using stash, keeping the remote in sync, and merging changes. It concludes by inviting the reader to join them in learning more about Git.
KegKong: Automated Keg System, presented at the Flatiron SchoolJordan Trevino
This automated keg system was built at the Flatiron School, using Ruby, Arduino, a Raspberry Pi and most importantly: our trusty keg.
Creators are: Jordan Trevino, Joe Giralt, Chris Gonzales
Mahara UK 2011 Technical Day - Git for MaharaAndrew Nicols
My presentation/workshop from the Mahara UK 2011 technical day.
This gives a quick insight into Git, what git is, some of the useful features of git are, and how it can be used in Mahara.
This document discusses polyglot persistence, which is using multiple data storage technologies in an application. It mentions relation databases, object-relational mapping like Hibernate, and polyglot persistence as described by Martin Fowler. It also includes links about CAP theorem, NoSQL databases, Spring Data solutions, and Hibernate OGM solutions. The document is from @diego_pacheco, a software architect and agile coach thanking people.
This document discusses scraping public transportation data and developing open data projects. It addresses legal issues around scraping, recommends scraping only when necessary and with legal justification. It also discusses design challenges for such projects and encourages collaborating openly and fixing issues together. The overall message is to scrape responsibly when needed, work together as a community, and focus on quick solutions that can be improved over time.
The document outlines an anti-corruption project called unshred.it that aims to use computer vision, artificial intelligence, and machine learning techniques to reconstruct shredded documents. It provides links to the project's documentation and communication channels on Slack and encourages contributions by reviewing documents, adding ideas to the roadmap, filing Github issues, and following coding standards and workflows outlined in the action plan and how-to documentation.
This document provides an overview and agenda for introducing GitLab tools. It discusses trends in modern development like increased use of open source tools and continuous integration/deployment. GitLab is presented as a one platform solution that provides version control, issue tracking, code review, CI/CD pipelines, and other DevOps tools. Key benefits of GitLab like open source contributions and frequent releases are outlined. Upcoming features in GitLab 11 like CI pipelines in the web IDE and license management are previewed. The presentation concludes with a Q&A and information on how to get a GitLab cheat sheet.
This document provides an overview of Google Code-in (GCI) and resources on GitHub. It discusses how GitHub can be used for more than just software, including sharing data, writing, translations, and open company initiatives. It also summarizes GCI tips like choosing a project in advance, getting familiar with tools and communication practices, and practicing communicating without overly formal language. Finally, it introduces the loklak social media harvester project and some example tasks for GCI Challenge 2.
In this presentation, Dmitriy Zaporozhets and Job van der Voort talk about the GitLab Release process and give a guided tour of the new features in 8.4. You can find out why GitLab users always know when the next release is, and how they know what's coming next.
Sql Saturday 895 - SQL Server e PowerShell: from Zero to HeroMarco Obinu
Slides of the session held at SQL Saturday 895 - Parma 2019 about the use of PowerShell in conjunction with SQL Server.
Demo scripts available at https://github.com/OmegaMadLab/SqlPowerShell-FromZeroToHero
Session recording available at https://youtu.be/yR3TfZfzHss
Did you really `got Git? In this presentation for E-commerce at Scale meetup, I talk about why choose Git over other version control systems, Git Flows and also some very useful but not so popular Git features.
Git is a free and open source distributed version control system that allows for collaboration through features like tracking changes, managing versions, and reverting files. It works across operating systems and programming languages. Git uses a local repository that can be synced and shared through remote repositories on services like GitHub and GitLab. Branches allow for parallel development and features like commits, cloning, and pull requests help track changes.
This document provides an introduction to Git and common branching models. It begins by defining Git as a distributed revision control system created by Linus Torvalds for Linux kernel development. It then discusses why Git is useful, how it is distributed and optimized for merging, and some key Git concepts like commits, branches, and the local repository structure. The document also outlines common Git commands, workflows like centralized, feature branching, Gitflow and GitHub flow, and how pull requests enable collaboration. It concludes by listing additional Git learning resources.
Git Flow is a strict branching model for managing workflow in Git projects. It was created by Vincent Driessen to provide a robust framework for managing features, releases, and bug fixes. The model uses long-living branches for development (develop), releases (master), features, and hotfixes, along with clear guidelines on how to integrate these branches. It aims to make collaboration easier by clearly defining roles for different branches and standardizing the development process.
This document summarizes a presentation about migrating from Subversion to Git version control. It discusses performing an inception to determine suitability, converting repositories from SVN to Git format using git-svn, and adopting the new workflow. Key benefits of Git mentioned include flexible branching/merging, speed, and enabling new collaboration workflows. The document also addresses infrastructure changes, potential workflows using forks, and concludes that Git adoption is increasing while migration tools have improved.
Open Sprintera (Where Open Source Sparks a Sprint of Possibilities)GDSCNiT
OpenSprintera: Where Open Source Sparks a Sprint of Possibilities
Key Highlights:
🌐 Git & GitHub Mastery: Learn the essentials of version control and collaborative coding using Git and GitHub.
🚀 Explore Open Source: Navigate through diverse open-source projects and find your niche.
🌟 Benefits of Contribution: Uncover the impact and personal growth opportunities through contributing to open source.
💡 Earning from Passion: Learn how your passion for open source can translate into valuable opportunities.
The document discusses Gitflow, a Git workflow that provides high-level repository operations for Vincent Driessen's branching model. It introduces Gitflow, outlines its history and benefits including parallel development and release staging. The document then explains how Gitflow works and the commands to install, initialize and use it for features, releases and hotfixes.
My talk presentation from SQA Days 21 conference.
During last two years I've been working in Agile teams and quite often have come across the situation when the feature is pretty big, but they still want to release it at the end of the sprint. That is in spite of the fact, that there is a great risk of violation of the timing and poor product quality.
So what should we, quality guards, do when eventually everything depends on us?
My report presents the analysis of the development stages from the testing point of view in such a difficult situation and provides tips for success.
Detecting secrets in code committed to gitlab (in real time)Chandrapal Badshah
Slides from my talk "Detecting secrets in code committed to Gitlab" at OWASP Suffolk on 15th May 2020.
This talk will cover the following:
* Problem we had
* Techniques to solve that
* Existing tools that can help us
* Comparison of tools
* Final architecture and product
* What we learnt from the experiment
* Future enhancements
This document provides an introduction to using Git version control. It discusses key Git concepts like distributed version control, objects in Git like blobs and trees, and commands like add, commit, branch, merge, rebase, fetch and push. The introduction includes an agenda, sources for further information, and demos several Git workflows and commands.
This document discusses Git and the Eclipse Git integration tool EGit. It provides an overview of Git's history and how it works, compares it to other version control systems, demonstrates common Git commands, and describes what EGit can do. The presentation then demonstrates using EGit for basic tasks like committing and branching, as well as more advanced workflows involving remote repositories and code review.
Git is a version control system created by Linus Torvalds that allows developers to track changes to code. GitHub is a free online repository that hosts Git repositories and allows developers to share code and collaborate on projects remotely. GitHub also allows developers to showcase their work and share their code publicly, potentially helping with job applications by including a GitHub URL. Git uses snapshots of files, adding, committing, and pushing changes to track a project's evolution over time through simple commands like init, add, commit, push, clone, and branch.
The document discusses Git, including why it is useful, how it compares to Subversion, basic Git commands, branching and merging workflows, and a typical development workflow. Git is a distributed version control system that allows for offline work, rapid branching and merging, and scalability for large projects. It differs from Subversion in being decentralized, allowing local repositories with full development histories. The document reviews commands for repository management, viewing changes, and attributing changes to authors. It emphasizes best practices for branching like following a specific model and not working directly on master or development branches.
We discuss things to be taken into account when deciding on a policy for your CI/CD pipelines. This might include Git workflows, testing approaches, and shipping strategies.
This document summarizes a presentation about using Git for Android development. It introduces Git and its core concepts like blobs, trees, and commits. It discusses how to set up Git on different platforms and integrate it with IDEs. Common Git commands are explained like add, commit, branch, merge, and rebase. Best practices for semantic commits, branching workflows, and tools like Git Flow are covered. The presentation emphasizes that Git gives developers freedom and power through its distributed nature and history of file system snapshots.
You have been wanting to use the "new shiny", but there are too many "Git how-tos" out there and you don't kow where to start. This is not another one of those. Instead Adam Culp will give a practical walk through the development cycle and how to use Git as the source control. From initialization of a repository, to forking, cloning, and checkout, we will walk through a sample project and how most developers actually use Git to manage the workflow. Adam will also touch on how to use Git repository hosting providers, and how to use them with PAAS (Platform as a service) providers.
This document summarizes a presentation on using Git for version control of Joomla projects. It introduces Git and its basic commands like clone, init, status, add, commit, push, and pull. It discusses Git clients for different operating systems and hosting repositories on sites like GitHub. It provides recommendations for setting up Git for a Joomla project, establishing workflows, deployment, and handling database issues. The target audience is developers, programmers, and designers working on Joomla projects.
This document provides an overview of using Git from initialization to branching. It discusses initializing a Git repository, adding, committing, and pushing files. It also covers pulling versus fetching and rebasing, developing feature branches, creating pull requests, and some pro tips for using Git. The document is intended to help readers understand the basic Git workflow from setting up a project through collaborative development using branches and pull requests.
Source code control is the most important practice that a software professional can do. This presentation introduces Git, the modern, distributed, version control designed for speed and efficiency.
This was delivered for a local Drupal user group.
I originally gave this presentation at the Drupal Self-Help Group meetup, in May 2012.
The document discusses different types of metrics used to measure performance, including key performance indicators (KPIs) and objectives and key results (OKRs). It notes that measures can become targets if over-emphasized, and outlines examples of KPIs like deployment frequency and velocity. The document also provides an example of an OKR framework with objectives, key results, and metrics to evaluate progress. It recommends using OKRs and KPIs as a structured way to connect organizational vision and strategy to daily work.
A talk first given at DevOpsDays in Stockholm.
The way we approach automation is riddled with misconceptions. This talks goes through a bunch of those and addresses how to think of them.
For my talk Misused figures of DevOps. We go through some common misconceptions and talk about how they cost us dearly. We also cover some actions that can help alleviate some of these pains.
Why should I learn Git? I'm just a software developerJohan Abildskov
The document discusses why software developers should learn Git and provides examples of how Git can be used for version control, tracking changes, finding bugs, and maintaining a strong workflow. Key benefits highlighted include maintaining multiple versions, reversing changes, finding who wrote specific lines of code, pinpointing when bugs were introduced, and enabling an offline workflow.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Using Query Store in Azure PostgreSQL to Understand Query PerformanceGrant Fritchey
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesQuickdice ERP
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Microservice Teams - How the cloud changes the way we workSven Peters
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
E-commerce Application Development Company.pdfHornet Dynamics
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
2. Git Workflow @randomsort
Agenda
● What are we not talking (much) about?
● Why should we care?
● Why is it difficult?
● Git Workflows
● Question time