This short presentation was a 20 minute talk for Barcamp 4 in Ghent (2011). The talk is about how to work better with GIT. Some tips and tricks and must-do's for people who already use git
Paver is a Python-based build tool similar to Make or Rake. It allows defining tasks with decorators like @task and accessing command line options. Tasks can run shell commands and Python code. Paver is useful for managing software project build processes and tasks like testing, deployment, and documentation generation in a configurable way.
This document discusses source code management (SCM) systems and the Git SCM system. It explains that SCM systems are used to track changes to source code files and maintain versions. Git is an example of a distributed SCM that stores project files and versions locally, allows cloning repositories, and supports branching and merging. The document provides instructions for basic Git commands and configuring Git for Unity projects.
This document provides a summary of basic Git commands and workflows. It recommends using branches instead of directly working on the master branch. It also discusses fetching and merging from upstream repositories, as well as resetting, reverting, stashing, and using GUIs. The document ends by thanking the reader and reiterating the advice to not work directly on the master branch.
Git is a distributed version control system created by Linus Torvalds in 2005. It allows tracking changes to files and coordinating work among contributors. Common Git commands include git add to stage files, git commit to save file changes to the local database, and git push to sync changes with remote repositories. Branches allow contributors to work independently on different features or fixes simultaneously. Merging brings changes from one branch into another.
The document provides an overview of the basics of using Git for distributed version control. It discusses that Git allows for a fully functional local repository with remote repositories syncing changes. It outlines configuring Git and a basic workflow of cloning a repository, making changes, adding/committing files, and pushing changes. It also summarizes key Git commands like add, commit, branching, merging, resolving conflicts, and rebasing.
Kotlin is a general-purpose programming language that can be used for web development. It is statically typed, supports both object-oriented and functional programming, and was developed by JetBrains as an open source project. Ktor is a web framework for Kotlin that allows building asynchronous web servers and clients. This document discusses using Ktor with Kotlin for building web applications and services, including routing, templating, working with databases, and implementing CRUD functionality.
maksym vlasov - culture of git as roots of your ciDariia Seimova
?
This document discusses best practices for using Git to improve work efficiency. It recommends using Git aliases to create shortcuts for common commands, using Git hooks at different stages of the development process, learning how to effectively read a project's commit history, maintaining a global .gitignore file, signing all commits with GPG for security, and customizing Git configuration to fit your specific workflow needs. Overall it promotes developing a strong "culture of Git" to serve as the foundation for continuous integration practices.
Gitlab is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. This presentation covers advance topics of git
This document provides an introduction to Ktor, a Kotlin framework for building asynchronous servers and clients. It discusses that Ktor is developed by JetBrains, is open source under the Apache 2.0 license, and can be used to build HTTP servers and clients. It also provides an example of using Ktor to build a CRUD application with routing, templating, and error handling.
A quick introduction to ZSH and RVM, and how to get them playing nicely with TextMate, Rails 3 and RSpec 2 on a Mac.
Note that the shortcuts listed are just in my fork of Oh-My-ZSH, not the original. And these slides are kinda lacking when there's no audio - that may appear later.
This document provides an overview and introduction to Git:
1. Git is a distributed version control system created by Linus Torvalds that allows for blazingly fast local version control and collaboration through distributed development.
2. Git can be used through both a command line interface (CLI) and graphical user interfaces (GUIs). The CLI provides many basic commands for initializing repositories, making commits, branching, tagging, and more.
3. Users can create their own Git repositories on their local machine or hosting services like GitHub to collaborate on projects and share code.
This document discusses using Git hooks to automate tasks during the Git workflow. It provides examples of using pre-commit hooks to check for debugging code and validate commit messages include ticket numbers. prepare-commit-msg hooks can template commit messages with default text like ticket references. post-commit hooks may open a browser to log work time against a referenced ticket after a commit. Server-side hooks on push can trigger tasks like running tests. Overall the document explores leveraging Git hooks for tasks like validation, templating, integration and to enforce best practices when committing code changes.
This document discusses the byebug debugging tool for Ruby and compares it to similar tools like debase and ruby-debug-ide. It notes that byebug provides a REPL for debugging and uses TracePoint under the hood instead of relying on C code like debase. The document also provides links to blog posts about how byebug works and recommends using gdb to debug Ruby code.
This document discusses APIs and related tools. It mentions that the author is focused on Ruby/Rails development and open source software. It also discusses API documentation tools like Swagger and OpenAPI, a Ruby gem called schema_conformist for validating requests against OpenAPI schemas, and testing and development tools used for APIs including Docker, RSpec, FactoryBot and others.
This document discusses using Git hooks for deployment to staging and production environments. It provides examples of a simple scenario using a post-update hook to automatically deploy code on push to a single production server. It also outlines a more advanced setup using Git hooks to deploy to staging and production environments with different processes, including emails on staging deploys and manual gem updates for production.
This document provides an introduction to Git and GitHub. It discusses what GitHub is and how it relates to Git. It then covers how to perform common Git and GitHub tasks like creating a repository, pushing and pulling changes, forking repositories, and making pull requests. The document also includes sections on Markdown formatting and resources for learning more about Git and GitHub.
The document discusses why developers should use Git over Subversion (SVN) for version control, explaining that Git was created by Linus Torvalds as a distributed system that is optimized for workflows like branching, merging, and handling large codebases. It provides an overview of Git's core features like snapshots instead of differences, distributed model instead of centralized server, and various tools that can be used with Git. The document concludes by recommending that the company Namics switch from using SVN to using Git for version control.
This document compares Go and Python programming languages. It notes that while they share some similarities like being able to be imperative or object-oriented, having multiple return values from functions, and package management, they also have key differences. Go is compiled, strongly typed, and has concurrency built into its runtime via goroutines and channels, while Python uses threads and has a Global Interpreter Lock. The document provides examples of using goroutines, defer, wait groups, and channels for concurrency in Go.
ChatOps meetup: les humains parlent aux robotsOlivier Jacques
?
ChatOps: le lien entre les dvelopeurs, les oprations, le support et... Des systmes.
Prsentation durant le meetup DevOps Grenoble. http://www.meetup.com/Grenoble-DevOps-Meetup/
This document provides an introduction to version control and Git. It discusses what version control is, examples of version control systems like Git, and how to get started with Git. The document then covers Git basics like configuring username and email, making commits, viewing commit history, resetting and branching. It also discusses more advanced topics such as merging branches and resolving conflicts.
This document provides an overview of version control and the basics of using Git. It discusses why backups are important, how version control works, and how to install and set up Git. It then covers basic Git commands and workflows for creating repositories, cloning repositories, staging and committing changes, branching and merging, tagging releases, ignoring files, resolving conflicts, and working in a distributed environment.
Git is a popular distributed version control system that is designed to handle large projects with speed and efficiency. It is "stupidly fast" for local operations and branching/merging. Repositories are also "stupidly small" in size. Git is decentralized, with anyone able to act as a server, and everyone having a full local repository. This allows for benefits like no single point of failure and trivial backups. Git differs from centralized systems like Subversion in ways like its use of the index/staging area and commands like rebase. Overall, Git provides a powerful and flexible system for version control.
This document provides an introduction to Git and some basic Git concepts and commands. It discusses that Git is a distributed revision control system developed by Linus Torvalds for Linux kernel development. It was designed for distributed and large projects. The document explains what a Git repository is, how to initialize, add files, and commit changes. It also covers staging files before committing, removing and moving files, ignoring files with a .gitignore file, and that a GUI may be preferable to the command line for some users.
maksym vlasov - culture of git as roots of your ciDariia Seimova
?
This document discusses best practices for using Git to improve work efficiency. It recommends using Git aliases to create shortcuts for common commands, using Git hooks at different stages of the development process, learning how to effectively read a project's commit history, maintaining a global .gitignore file, signing all commits with GPG for security, and customizing Git configuration to fit your specific workflow needs. Overall it promotes developing a strong "culture of Git" to serve as the foundation for continuous integration practices.
Gitlab is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. This presentation covers advance topics of git
This document provides an introduction to Ktor, a Kotlin framework for building asynchronous servers and clients. It discusses that Ktor is developed by JetBrains, is open source under the Apache 2.0 license, and can be used to build HTTP servers and clients. It also provides an example of using Ktor to build a CRUD application with routing, templating, and error handling.
A quick introduction to ZSH and RVM, and how to get them playing nicely with TextMate, Rails 3 and RSpec 2 on a Mac.
Note that the shortcuts listed are just in my fork of Oh-My-ZSH, not the original. And these slides are kinda lacking when there's no audio - that may appear later.
This document provides an overview and introduction to Git:
1. Git is a distributed version control system created by Linus Torvalds that allows for blazingly fast local version control and collaboration through distributed development.
2. Git can be used through both a command line interface (CLI) and graphical user interfaces (GUIs). The CLI provides many basic commands for initializing repositories, making commits, branching, tagging, and more.
3. Users can create their own Git repositories on their local machine or hosting services like GitHub to collaborate on projects and share code.
This document discusses using Git hooks to automate tasks during the Git workflow. It provides examples of using pre-commit hooks to check for debugging code and validate commit messages include ticket numbers. prepare-commit-msg hooks can template commit messages with default text like ticket references. post-commit hooks may open a browser to log work time against a referenced ticket after a commit. Server-side hooks on push can trigger tasks like running tests. Overall the document explores leveraging Git hooks for tasks like validation, templating, integration and to enforce best practices when committing code changes.
This document discusses the byebug debugging tool for Ruby and compares it to similar tools like debase and ruby-debug-ide. It notes that byebug provides a REPL for debugging and uses TracePoint under the hood instead of relying on C code like debase. The document also provides links to blog posts about how byebug works and recommends using gdb to debug Ruby code.
This document discusses APIs and related tools. It mentions that the author is focused on Ruby/Rails development and open source software. It also discusses API documentation tools like Swagger and OpenAPI, a Ruby gem called schema_conformist for validating requests against OpenAPI schemas, and testing and development tools used for APIs including Docker, RSpec, FactoryBot and others.
This document discusses using Git hooks for deployment to staging and production environments. It provides examples of a simple scenario using a post-update hook to automatically deploy code on push to a single production server. It also outlines a more advanced setup using Git hooks to deploy to staging and production environments with different processes, including emails on staging deploys and manual gem updates for production.
This document provides an introduction to Git and GitHub. It discusses what GitHub is and how it relates to Git. It then covers how to perform common Git and GitHub tasks like creating a repository, pushing and pulling changes, forking repositories, and making pull requests. The document also includes sections on Markdown formatting and resources for learning more about Git and GitHub.
The document discusses why developers should use Git over Subversion (SVN) for version control, explaining that Git was created by Linus Torvalds as a distributed system that is optimized for workflows like branching, merging, and handling large codebases. It provides an overview of Git's core features like snapshots instead of differences, distributed model instead of centralized server, and various tools that can be used with Git. The document concludes by recommending that the company Namics switch from using SVN to using Git for version control.
This document compares Go and Python programming languages. It notes that while they share some similarities like being able to be imperative or object-oriented, having multiple return values from functions, and package management, they also have key differences. Go is compiled, strongly typed, and has concurrency built into its runtime via goroutines and channels, while Python uses threads and has a Global Interpreter Lock. The document provides examples of using goroutines, defer, wait groups, and channels for concurrency in Go.
ChatOps meetup: les humains parlent aux robotsOlivier Jacques
?
ChatOps: le lien entre les dvelopeurs, les oprations, le support et... Des systmes.
Prsentation durant le meetup DevOps Grenoble. http://www.meetup.com/Grenoble-DevOps-Meetup/
This document provides an introduction to version control and Git. It discusses what version control is, examples of version control systems like Git, and how to get started with Git. The document then covers Git basics like configuring username and email, making commits, viewing commit history, resetting and branching. It also discusses more advanced topics such as merging branches and resolving conflicts.
This document provides an overview of version control and the basics of using Git. It discusses why backups are important, how version control works, and how to install and set up Git. It then covers basic Git commands and workflows for creating repositories, cloning repositories, staging and committing changes, branching and merging, tagging releases, ignoring files, resolving conflicts, and working in a distributed environment.
Git is a popular distributed version control system that is designed to handle large projects with speed and efficiency. It is "stupidly fast" for local operations and branching/merging. Repositories are also "stupidly small" in size. Git is decentralized, with anyone able to act as a server, and everyone having a full local repository. This allows for benefits like no single point of failure and trivial backups. Git differs from centralized systems like Subversion in ways like its use of the index/staging area and commands like rebase. Overall, Git provides a powerful and flexible system for version control.
This document provides an introduction to Git and some basic Git concepts and commands. It discusses that Git is a distributed revision control system developed by Linus Torvalds for Linux kernel development. It was designed for distributed and large projects. The document explains what a Git repository is, how to initialize, add files, and commit changes. It also covers staging files before committing, removing and moving files, ignoring files with a .gitignore file, and that a GUI may be preferable to the command line for some users.
This document provides an overview of Git, including:
1. Git allows tracking changes to source code, allowing multiple people to work together and deploy to multiple servers.
2. Basic Git commands are used to initialize a repository, add files, commit changes, pull and push from remote repositories.
3. More advanced features include tags for releases, branches for different versions, and commands for reverting changes and amending commits.
4. Various Git tools and hosting services are referenced for visualizing repositories and collaborating online.
Git and GitHub basics provides an overview of source control systems and how to use Git and GitHub. It discusses why to use source control, how to set up Git and GitHub on Windows, basic terminology, how to create repositories and push code to GitHub, ignoring files, reverting commits, forking repositories, and pulling changes in shared repositories. The document includes demonstrations of key commands like init, add, commit, push, status, clone and pull.
This document provides an agenda and overview for a class on using Git, GitHub, and VSCode. It introduces command line basics, files and directories, terminal commands, text editors, GitHub, Git basics, and a homework assignment to create a GitHub repository and JavaScript program. Key topics covered include the Git workflow, essential Git commands, using GitHub Pages to host websites, and an introduction to JavaScript programming.
This document provides an agenda and overview for a class on using Git, GitHub, and VSCode. It introduces command line basics, files and directories, terminal commands, text editors, GitHub, Git basics, and a homework assignment to create a GitHub repository and JavaScript program. Key topics covered include the Git workflow, essential Git commands, using GitHub Pages, and an introduction to JavaScript programming.
ݺߣ deck with detailed step breakdown that explains how git works, together with simple examples that you can try out yourself. ݺߣs originated from http://teach.github.com/articles/course-slides/
Author: https://twitter.com/matthewmccull
The document provides an outline on installing and configuring Git, introduces common Git concepts and commands, discusses various Git workflows and hosting options on GitHub and Bitbucket, and includes examples of using Git in case studies. It covers topics such as setting up a local and global Git configuration, interacting with the staging area and working directory, branching and merging, and resolving conflicts. The document is intended to teach users the basics of using the popular version control system Git.
This document provides an outline for a course on learning Git version control. The course covers getting Git setup, the basic concepts and workflow of Git, branching and merging, resolving conflicts, working with remote repositories, and various Git commands. The document lists several modules that will be covered, including getting started, everyday Git usage, branching, merging and rebasing, additional tools and concepts, and advice on applying the skills learned. The goal is to teach participants how to install and use Git for version control on individual, local, and distributed projects.
The document provides an overview of version control systems and introduces Git and GitHub. It discusses the differences between centralized and distributed version control. It then covers the basics of using Git locally including initialization, staging files, committing changes, branching and merging. Finally, it demonstrates some common remote operations with GitHub such as pushing, pulling and tagging releases.
Git Obstacle Course: Stop BASHing your head and break down the basicsChris Bohatka
?
A world without source control leads to scary stories around the campfire. We all know we should commit early and often, and weve been told that Git is the system of choice. Looking at tutorials can be intimidating, though, with terminal commands here and bash commands there. What does it all mean, and how can you use it as a developer, designer, architect or analyst? In this session, we will work through these obstacles to bolster your Git knowledge en route to earning your Git More Done Camp Badge.
On the past Thursday, 10 November, the training Workshop : Git & GitHub took place, given by our colleague Alfonso Rodrguez, django developer, at IES CAMAS.
Git is a distributed version control system that allows developers to work independently and asynchronously on features or bug fixes through branches. Branches allow developers to commit changes frequently without disrupting the main codebase. If a branch is ready, a developer can merge the branch back into the main branch. Git also uses a commit and diff system to track changes at a file level, making it easy to revert changes or roll back to previous versions if needed. The distributed nature of Git provides advantages over centralized systems like SVN by allowing independent repositories and easy conflict resolution during merges.
This document provides an overview of basic Git commands and concepts:
- Git is a distributed version control system that allows developers to work locally without an internet connection and includes built-in backup of repositories.
- Common Git commands are demonstrated for initializing and cloning repositories, tracking and committing changes, branching, merging, and more.
- The document also discusses installing Git on various platforms and using GUI tools to help visualize repositories and histories.
This document provides an overview of various Git commands, workflows, and best practices. It covers the basics of initializing repositories, committing, branching, merging, tagging, undoing changes, and working with remotes. It also summarizes several common Git workflows including centralized, feature branching, Gitflow, and forking models. Best practices around aliases, ignoring files, log formatting, and branching strategies are also outlined.
Understanding Traditional AI with Custom Vision & MuleSoft.pptxshyamraj55
?
Understanding Traditional AI with Custom Vision & MuleSoft.pptx | ### ݺߣ Deck Description:
This presentation features Atul, a Senior Solution Architect at NTT DATA, sharing his journey into traditional AI using Azure's Custom Vision tool. He discusses how AI mimics human thinking and reasoning, differentiates between predictive and generative AI, and demonstrates a real-world use case. The session covers the step-by-step process of creating and training an AI model for image classification and object detectionspecifically, an ad display that adapts based on the viewer's gender. Atulavan highlights the ease of implementation without deep software or programming expertise. The presentation concludes with a Q&A session addressing technical and privacy concerns.
A Framework for Model-Driven Digital Twin EngineeringDaniel Lehner
?
ݺߣs from my PhD Defense at Johannes Kepler University, held on Janurary 10, 2025.
The full thesis is available here: https://epub.jku.at/urn/urn:nbn:at:at-ubl:1-83896
The Future of Repair: Transparent and Incremental by Botond De?nesScyllaDB
?
Regularly run repairs are essential to keep clusters healthy, yet having a good repair schedule is more challenging than it should be. Repairs often take a long time, preventing running them often. This has an impact on data consistency and also limits the usefulness of the new repair based tombstone garbage collection. We want to address these challenges by making repairs incremental and allowing for automatic repair scheduling, without relying on external tools.
EaseUS Partition Master Crack 2025 + Serial Keykherorpacca127
?
https://ncracked.com/7961-2/
Note: >> Please copy the link and paste it into Google New Tab now Download link
EASEUS Partition Master Crack is a professional hard disk partition management tool and system partition optimization software. It is an all-in-one PC and server disk management toolkit for IT professionals, system administrators, technicians, and consultants to provide technical services to customers with unlimited use.
EASEUS Partition Master 18.0 Technician Edition Crack interface is clean and tidy, so all options are at your fingertips. Whether you want to resize, move, copy, merge, browse, check, convert partitions, or change their labels, you can do everything with a few clicks. The defragmentation tool is also designed to merge fragmented files and folders and store them in contiguous locations on the hard drive.
Replacing RocksDB with ScyllaDB in Kafka Streams by Almog GavraScyllaDB
?
Learn how Responsive replaced embedded RocksDB with ScyllaDB in Kafka Streams, simplifying the architecture and unlocking massive availability and scale. The talk covers unbundling stream processors, key ScyllaDB features tested, and lessons learned from the transition.
How Discord Indexes Trillions of Messages: Scaling Search Infrastructure by V...ScyllaDB
?
This talk shares how Discord scaled their message search infrastructure using Rust, Kubernetes, and a multi-cluster Elasticsearch architecture to achieve better performance, operability, and reliability, while also enabling new search features for Discord users.
https://ncracked.com/7961-2/
Note: >> Please copy the link and paste it into Google New Tab now Download link
Brave is a free Chromium browser developed for Win Downloads, macOS and Linux systems that allows users to browse the internet in a safer, faster and more secure way than its competition. Designed with security in mind, Brave automatically blocks ads and trackers which also makes it faster,
As Brave naturally blocks unwanted content from appearing in your browser, it prevents these trackers and pop-ups from slowing Download your user experience. It's also designed in a way that strips Downloaden which data is being loaded each time you use it. Without these components
UiPath Agentic Automation Capabilities and OpportunitiesDianaGray10
?
Learn what UiPath Agentic Automation capabilities are and how you can empower your agents with dynamic decision making. In this session we will cover these topics:
What do we mean by Agents
Components of Agents
Agentic Automation capabilities
What Agentic automation delivers and AI Tools
Identifying Agent opportunities
? If you have any questions or feedback, please refer to the "Women in Automation 2025" dedicated Forum thread. You can find there extra details and updates.
What Makes "Deep Research"? A Dive into AI AgentsZilliz
?
About this webinar:
Unless you live under a rock, you will have heard about OpenAIs release of Deep Research on Feb 2, 2025. This new product promises to revolutionize how we answer questions requiring the synthesis of large amounts of diverse information. But how does this technology work, and why is Deep Research a noticeable improvement over previous attempts? In this webinar, we will examine the concepts underpinning modern agents using our basic clone, Deep Searcher, as an example.
Topics covered:
Tool use
Structured output
Reflection
Reasoning models
Planning
Types of agentic memory
UiPath Automation Developer Associate Training Series 2025 - Session 1DianaGray10
?
Welcome to UiPath Automation Developer Associate Training Series 2025 - Session 1.
In this session, we will cover the following topics:
Introduction to RPA & UiPath Studio
Overview of RPA and its applications
Introduction to UiPath Studio
Variables & Data Types
Control Flows
You are requested to finish the following self-paced training for this session:
Variables, Constants and Arguments in Studio 2 modules - 1h 30m - https://academy.uipath.com/courses/variables-constants-and-arguments-in-studio
Control Flow in Studio 2 modules - 2h 15m - https:/academy.uipath.com/courses/control-flow-in-studio
?? For any questions you may have, please use the dedicated Forum thread. You can tag the hosts and mentors directly and they will reply as soon as possible.
Many MSPs overlook endpoint backup, missing out on additional profit and leaving a gap that puts client data at risk.
Join our webinar as we break down the top challenges of endpoint backupand how to overcome them.
Just like life, our code must evolve to meet the demands of an ever-changing world. Adaptability is key in developing for the web, tablets, APIs, or serverless applications. Multi-runtime development is the future, and that future is dynamic. Enter BoxLang: Dynamic. Modular. Productive. (www.boxlang.io)
BoxLang transforms development with its dynamic design, enabling developers to write expressive, functional code effortlessly. Its modular architecture ensures flexibility, allowing easy integration into your existing ecosystems.
Interoperability at Its Core
BoxLang boasts 100% interoperability with Java, seamlessly blending traditional and modern development practices. This opens up new possibilities for innovation and collaboration.
Multi-Runtime Versatility
From a compact 6MB OS binary to running on our pure Java web server, CommandBox, Jakarta EE, AWS Lambda, Microsoft Functions, WebAssembly, Android, and more, BoxLang is designed to adapt to any runtime environment. BoxLang combines modern features from CFML, Node, Ruby, Kotlin, Java, and Clojure with the familiarity of Java bytecode compilation. This makes it the go-to language for developers looking to the future while building a solid foundation.
Empowering Creativity with IDE Tools
Unlock your creative potential with powerful IDE tools designed for BoxLang, offering an intuitive development experience that streamlines your workflow. Join us as we redefine JVM development and step into the era of BoxLang. Welcome to the future.
DevNexus - Building 10x Development Organizations.pdfJustin Reock
?
Developer Experience is Dead! Long Live Developer Experience!
In this keynote-style session, well take a detailed, granular look at the barriers to productivity developers face today and modern approaches for removing them. 10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, The Coding War Games.
Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method, we invent to deliver products, whether physical or virtual, we reinvent productivity philosophies to go alongside them.
But which of these approaches works? DORA? SPACE? DevEx? What should we invest in and create urgency behind today so we dont have the same discussion again in a decade?
[Webinar] Scaling Made Simple: Getting Started with No-Code Web AppsSafe Software
?
Ready to simplify workflow sharing across your organization without diving into complex coding? With FME Flow Apps, you can build no-code web apps that make your data work harder for you fast.
In this webinar, well show you how to:
Build and deploy Workspace Apps to create an intuitive user interface for self-serve data processing and validation.
Automate processes using Automation Apps. Learn to create a no-code web app to kick off workflows tailored to your needs, trigger multiple workspaces and external actions, and use conditional filtering within automations to control your workflows.
Create a centralized portal with Gallery Apps to share a collection of no-code web apps across your organization.
Through real-world examples and practical demos, youll learn how to transform your workflows into intuitive, self-serve solutions that empower your team and save you time. We cant wait to show you whats possible!
World Information Architecture Day 2025 - UX at a CrossroadsJoshua Randall
?
User Experience stands at a crossroads: will we live up to our potential to design a better world? or will we be co-opted by product management or another business buzzword?
Looking backwards, this talk will show how UX has repeatedly failed to create a better world, drawing on industry data from Nielsen Norman Group, Baymard, MeasuringU, WebAIM, and others.
Looking forwards, this talk will argue that UX must resist hype, say no more often and collaborate less often (you read that right), and become a true profession in order to be able to design a better world.
Technology use over time and its impact on consumers and businesses.pptxkaylagaze
?
In this presentation, I explore how technology has changed consumer behaviour and its impact on consumers and businesses. I will focus on internet access, digital devices, how customers search for information and what they buy online, video consumption, and lastly consumer trends.
4. ... and with the love from @github
If you dont have a @github account yet, then this talk isnt for you...
5. ... and with the love from @github
If you dont have a @github account yet, then this talk isnt for you...
6. 5 MUST-DOs as git user
or you would better not start using git at all...
7. 1. Dont use a GUI, ever! CLI ftw!
? You will never feel the power of GIT
? Not (almost) every command is possible through a GUI
OK, there are cool GUIs but becoming an expert is easier the
hard way, the CLI-way!
9. 2. Con?gure git like it should be...
?$ git con?g --global color.ui true
?$ git con?g --global format.pretty oneline
?$ git con?g --global core.autocrlf true (Windows) use a
LF
$ git con?g --global core.safecrlf true (Windows) line lways
end
$ git con?g --global core.autocrl input (OSX & linux) ing
s!
?$ git con?g --global core.excludes?le ~/.gitignore
$ printf ".DS_StorenThumbs.dbn._*n" >> ~/.gitignore
? enable bash autocompletion (Google it for your OS)
10. 2. Con?gure git like it should be...
?$ git con?g --global color.ui true
?$ git con?g --global format.pretty oneline
?$ git con?g --global core.autocrlf true (Windows) use a
LF
$ git con?g --global core.safecrlf true (Windows) line lways
end
$ git con?g --global core.autocrl input (OSX & linux) ing
s!
?$ git con?g --global core.excludes?le ~/.gitignore DR
Y
$ printf ".DS_StorenThumbs.dbn._*n" >> ~/.gitignore
? enable bash autocompletion (Google it for your OS)
11. 3. Use a remote repo if possible
and probably many more...
12. 4. Use submodules when possible
? Better overview of different parts in your code
? DRY: Re-use repositories in every project trough submodules
Good example: Every module in the @kohanaphp framework is a
seperate repository, so different contributors and releases possible
16. 5. Branch, branch and tag!
Choose your own work?ow
Source: http://nvie.com/posts/a-successful-git-branching-model/
17. 5 TIPS that will reduce
the amount of WTFs
and hopefully making you commit better then before
18. 1. Wheres my commit?
Oh no! Its on a detached HEAD?!
?A problem with submodules currently not on a branch
? Search for your commits SHA-reference (eg. a8e358c)
$ git log -p
? Merge it with your branch
$ git checkout master
$ git merge a8e358c
19. 2. Use git merge --no-ff
You will not regret it if you want to revert it!
Source: http://nvie.com/posts/a-successful-git-branching-model/
20. 3. Use git add -i
Becomes sometime you do different things together...
22. 4. git submodule rm exists, right?
No!
$ vim .gitmodules
$ vim .git/con?g
$ git rm --cached path/to/module NO trailing slash!
Commit your changes
23. 5. I didnt change my ?le but still...
git tracks ?le execution permissions too
2 Possibilities:
? Track no permissions
$ git con?g core.?leMode false
? Apply the permissions to the ?les without have it in your repo
$ git diff -p
| grep -E '^(diff|old mode|new mode)'
| sed -e 's/^old/NEW/;s/^new/old/;s/^NEW/new/'
| git apply