This is my presentation from the DevOps track at QCon 2010, where I attempt to explain what's going wrong with the industry, and what to do at the coalface to fix things
Cruz Alonzo is a creative marketer who freelances while working full-time at a retail company. He enjoys making content for businesses and wants to work at a creative agency so he can focus fully on creative work. Alonzo is passionate about marketing and has skills in areas like photography, web development, and Adobe InDesign. His goal is to be successful enough to quit his full-time job and focus solely on creative projects.
The document discusses traits of a successful leader. It lists six key traits: 1) listening and communicating effectively, 2) treating your team with the same respect you want them to show others, 3) having patience and flexibility, 4) encouraging creativity, 5) serving as a role model, and 6) adaptability. Each trait is accompanied by an image to illustrate the point.
The document is a collection of images and captions related to health, stress, and lifestyle topics. Some of the images provide tips for lowering blood pressure, curing colds, reducing acne, saving time and money. Other images advertise lifestyle changes like going medication free, looking like someone else, or living a socially unacceptable lifestyle. The images have captions about feeling sick, stressed, wanting more time and money or less stress. Overall it discusses various health, lifestyle and stress related issues and solutions.
This document contains links to various photos on Flickr related to ticket driven development and planning poker. The links showcase images of software development workflow tools and planning techniques like sticky notes and planning poker card decks that are used for estimating tasks in an agile, ticket driven development process.
This document provides an overview of Arduino, an open-source electronics prototyping platform. It introduces (1) the Arduino Uno board and its features, including a microcontroller, digital and analog pins for input/output, and connections for power and communication; (2) Arduino programming using the C/C++ based IDE to write sketches with setup() and loop() functions; and (3) examples of Arduino projects and where to purchase Arduino boards and components.
The document is a collection of Flickr photos with captions that relate to improving student behavior and academic performance. The photos promote identifying real-world preparation, providing feedback to students, and helping students learn to cope with challenges and organize themselves. They suggest working with students can make a positive difference and that change is needed to continue progress.
Kari Hamnes, Bedre digitale kundeopplevelserTag-IT
The document is a collection of random Flickr photo URLs and short phrases with no clear overall theme or narrative. It includes links to photos of cars, web design, luggage and more. Interspersed are short questions or statements about starting something, resources and contact with organizations. The document lacks coherence and a discernible purpose.
The document is a series of slides for a presentation with photos and captions. It appears to be about an individual's career goals in the music industry, including working with music companies, venues, broadcasters, and famous artists, as well as nurturing new talents, mingling with creative minds, hosting talent shows, and discovering the next big thing in the industry.
This document discusses alternatives to traditional education and what happens when students leave that system. It notes that many students change their majors and that the future is unclear for those who do not follow the traditional path. Images accompany the text but do not provide much additional context on their own. The average tuition costs for postsecondary education in the US is also listed.
Risk Measurement and Management Using Open Source ToolingJoe Kuemerle
This document outlines a methodology for measuring and managing risk using open source tooling. It discusses assessing the likelihood and impact of risks, calculating inherent and residual risk scores, and mitigating risks. Key aspects include evaluating factors like technical debt, security coverage, who has access to systems, and what types of data could be disclosed. Suggested next steps are to apply the methodology, provide feedback, and discuss/contribute to the resources shared.
This document discusses Vagrant, an open source tool that allows users to create and configure lightweight, reproducible, and portable development environments. It provides instructions on installing Vagrant and the base box, configuring a Vagrantfile to define VMs, provisioning VMs using tools like Puppet, accessing VMs using SSH, suspending, destroying, and reloading VMs. Benefits mentioned include having disposable environments, version controlling configs, sharing configs between environments, and managing multiple VMs. Potential objections and questions are also addressed.
This document summarizes Justin Kadima's presentation on RESTful web development at Webstock 2009. It provides examples of Twitter and MySpace APIs that follow REST principles by allowing GET requests to retrieve user timelines, followers, photos, albums and more. It defines what a web service is and why APIs and web services are important for integration. It also outlines best practices for RESTful design, including determining resources and supported methods, linking resources, and choosing data formats.
Open Data: How, why, and is there any point?Cameron Neylon
Slides from a talk given at Manchester Institute for Science, Ethics and Innovation on 13 October 2009. Focusses on the reasons why there is public funding of science and the issues that need to be tackled to insure this in the future.
This document contains a collection of images related to microbes, including bacteria, viruses, and other microorganisms. Images show bacteria that cause diseases like polio, malaria, and the common cold. Other images depict vaccines, macrophages fighting viruses, and flagella on microbes. The images provide visual examples of different types of microbes and how they relate to human health.
Build an App with JavaScript and jQuery - LA - July 27Thinkful
This document provides information about a workshop to build an app with JavaScript and jQuery. The workshop will be led by Fernando Arocho and TA's from Revuelo. Attendees will learn key jQuery and JavaScript concepts, work on building a shopping list app from starter code, and review solutions at the end. Thinkful helps people become developers through project-based learning and mentorship.
The document contains 10 links to photos on Flickr covering a variety of subjects including landscapes, animals, people, and medical equipment. As the document only provides links without any other context, it is difficult to determine any clear overall theme or message being conveyed.
This document discusses content management systems (CMS). A CMS is a system for managing digital content on websites. It discusses Drupal, an open source CMS framework that allows users to collaboratively create and manage website content. The document contains several images and links related to CMS platforms and Drupal.
The document discusses different types of pathogens including viruses, bacteria, and parasites. It provides images of polio drops, mosquitoes, macrophages attacking viruses and bacteria, and microscopic images of flagella and microbes. The document highlights the difference between cold and flu viruses while also showing how vaccines can provide protection against pathogens.
This document contains a list of URLs for blog posts and slideshare presentations related to teaching history and methodologies like the problem situation approach. The URLs link to blogs, slideshows, and websites that discuss topics such as oral history, interviews, narratives, and different educational theories. Many of the links are to presentations by the same user on slideshare.net about various history teaching products and methodologies.
Everything I learned about Continuous Integration, I learned from Systems Adm...Julian Simpson
DevOpsDays Gothenburg presentation where we explain how an earlier career in Systems Administration helped us kick ass in running Continuous Integration.
The document encourages everyone to pursue their dreams and not let others put them down. It stresses that everyone deserves respect and compassion, as we are all fundamentally the same. The overall message is one of empowering all people and bringing more love and kindness into the world.
The document discusses the convergence of system administrators and developers as programming has become more integral to system administration work. It notes that system administrators now write code using languages like Ruby, Python, and Bash just as developers do. It argues that system administrators who do not program have become merely domain experts. The document also discusses challenges around sharing system administration tools and modules, as well as testing infrastructure using approaches from software development like Cucumber testing.
The document provides instructions for multiplying polynomials using different methods:
1) The box method involves creating a box for each term and multiplying the terms to fill in the boxes.
2) The tile method represents each term with a tile and combines like terms.
3) The stack method rearranges terms in stacks and multiplies vertically.
4) The distributing property method draws arrows between terms and multiplies accordingly.
Examples are provided for multiplying different polynomials like 2(3), 2(x+2), and (x+2)(x+3) using these various methods.
El documento presenta una serie de preguntas sobre conceptos relacionados con el emprendimiento y la publicidad. Cada pregunta tiene 5 opciones de respuesta y la respuesta correcta es "E. Todas las anteriores" para la mayoría de las preguntas, lo que indica que los conceptos cubren múltiples aspectos. El documento evalúa el conocimiento sobre competencias, características del emprendedor, elementos del plan de mercadeo y otros temas clave relacionados con el emprendimiento.
El documento define los conceptos de mercado, mercadotecnia y mezcla de mercadotecnia. Un mercado consiste en consumidores con necesidades que pueden ser satisfechas a través de intercambios. La mercadotecnia es el proceso de planificación, ejecución y conceptualización de precios, promociones y distribución de bienes y servicios para crear intercambios que satisfagan necesidades individuales y organizacionales. La mezcla de mercadotecnia incluye el producto, precio, plaza y promoción.
This document discusses Agile systems administration using tools like Puppet, Rake, Ruby, Subversion, and CruiseControl. It summarizes how these tools can be used together in an iterative and collaborative manner to continuously test and deploy system configurations from a versioned code repository. Key benefits include always deploying tested configurations, versioning infrastructure configurations, visibility of project status, and enabling continuous integration practices for system administration work.
Techniques for stress free software releasesrouanw
The recent explosion of DevOps tools and techniques means that releasing new features doesn’t need to be a stressful all-weekend slumber party. Rouan will give you a set of steps you can take to move your release process from zero to hero.
He’ll show you how to gain confidence in your changes with automated testing and a build pipeline. He’ll share his experience of implementing push-button deployments to production, so that you can shrink your margin of error right down. He’ll tell you about Infrastructure as Code and how you can have your very own phoenix servers, so that disaster recovery is built into your release process. Finally, he’ll share techniques for blue-green deployment so that you can deploy with no impact to your customers.
10+ Deploys Per Day: Dev and Ops Cooperation at FlickrJohn Allspaw
Communications and cooperation between development and operations isn't optional, it's mandatory. Flickr takes the idea of "release early, release often" to an extreme - on a normal day there are 10 full deployments of the site to our servers. This session discusses why this rate of change works so well, and the culture and technology needed to make it possible.
The document discusses that the value of technology is not just about apps, but how people configure platforms and connect them together in new ways to solve specific problems. It notes that niche user groups can deliver more value than mass production models. Structuring configurations can help with re-use while still allowing for expression. The most important things are learning from each other and sharing stories of both success and failure.
This document describes how to build a Jabber bot that can process Twitter messages serialized as XMPP messages. It provides instructions on setting up the necessary Ruby gems, creating a daemon to serialize tweets, writing specs to test the bot's behavior, and implementing the bot client to apply rules to messages. Sample Twitter messages in XMPP format are also included. The goal is to allow others to build their own bot armies that can process tweets and perform actions.
Living system or build factory - Chris MaxwellDevopsdays
This document discusses the differences between living systems and build factories in IT operations. A living system mutates and evolves over time as the business needs change, resulting in each system being slightly different. In contrast, a build factory aims to replicate systems exactly using automated procedures so that each new system has identical configurations. The document advocates describing processes, automating steps, and enabling production of identical systems through repetition as an effective approach for build factories. It also notes some challenges that can arise when deeply embedded problems occur in living systems or unexpected changes are required for production systems.
virtual presentation by Kristina D.C. Hoeppner for Mahara UK 11 http://maharauk.org on June 22, 2011; the recording is available at http://www.youtube.com/watch?v=Rbz9vST0CLw
Slide deck from "Modern Web Applications with Struts 2" at ApacheConEU 2012 Sinsheim, by Johannes Geppert and me. The corresponding code example can be found at GitHub:
https://github.com/jogep/struts2-todo-examples
The document discusses potential improvements to the iPad based on user feedback. It suggests adding more ports like USB and SD card slots for additional storage options. It also proposes implementing full OSX support on the iPad to allow running laptop-like applications and better meet user needs. The document argues Apple should listen more to customer complaints in order to further improve its products and reduce users switching to competitors.
Nick Oostvogels: 5 Arguments Against KanbanAgileee
Kanban faces several common arguments against its adoption. These include concerns that Kanban will:
1) Limit the ability to plan work.
2) Cause work to take longer to complete.
3) Result in work getting stuck if work-in-progress limits are enforced.
4) Not align with stakeholder priorities if they do not consider flow.
5) Reduce team cohesion by focusing on individual tasks rather than collaboration.
The document discusses governance and flexibility in systems and processes. It recommends keeping processes simple through approaches like MVP and KISS. Regulations and audits are important to implement for risk management and legal compliance. Overall systems should be designed to make users' lives easier and improve the product, while also preparing for unexpected problems. Flexibility and a focus on the individual are key principles.
The document summarizes a TDD boot camp event that took place on January 23-24, 2011. It provides an overview of the schedule and activities, which included sessions on test-driven development (TDD) fundamentals and techniques, as well as hands-on practice with tools like Subversion, Maven, and Jenkins. The goal of the boot camp was to teach attendees the principles and practices of TDD through lectures, demonstrations, and collaborative coding exercises.
Introduction à l’intégration continue avec JenkinsEric Hogue
This document provides an introduction to continuous integration with Jenkins. It discusses key concepts like continuous integration, automation of builds and tests, and using tools like Jenkins to run builds, tests and analyze results. It provides examples of extensions that can be used with Jenkins like Git, Phing, reporting and notifications. The document encourages automating the integration process for rapid feedback and increased confidence in changes.
The document appears to be a biography of an individual who was born and raised in Oregon. As a child, they were involved in various sports like running, skateboarding, and snowboarding. As an adult, they have taken on many roles such as a coffee drinker, music producer, DJ, best friend, drill sergeant, mentor, leader, and husband. However, they felt frustrated and needed more, so they chose to attend Full Sail University to further their career and build their future. The long road has been challenging but their future is near.
A Jisc Perspective Of Impact And EvidenceIan Cooper
This document discusses the challenges of measuring the impact and value of investments in digital resources and services. It notes that while performance was originally the main focus, the emphasis is now shifting toward tracking usage and value, though not all impacts can be measured in the same way. Consistent measurement of things like audience size, market penetration, and value for money is important but difficult.
This document discusses experience design and three paths to creating digital experiences: structural, community, and customer. The structural path focuses on site organization and usability. The community path involves creating digital spaces for conversation and participation. The customer path examines a customer's journey and looks for ways to improve and surprise customers through the digital experience. The overall goal is to connect customers and facilitate real conversation through the design of the digital experience.
This document discusses best practices for taking a visual design mockup and implementing it as a functional website. It recommends deconstructing the mockup to understand clickable elements, platforms, and browser support. Estimating costs requires breaking work into components, accounting for risks and unknowns, and tracking time versus quotes. Prototyping early and following a KISS (Keep It Simple, Stupid) approach are also advised. Third-party libraries should be vetted for quality and activity level. The recap stresses function over form, anticipating invisible elements, prototyping, and following a KI(RF)SS (Keep It Relevantly Simple, Stupid) principle.
The Future of Design is Not Just the Web - Web Visions Workshop 2011Samantha Starmer
The document discusses designing cross-channel experiences. It begins by explaining that customers experience brands across multiple touchpoints and channels, both digital and physical. The key is to design experiences that are convenient, connected, consistent, contextual, and span across time.
The document then provides five principles and five methods for cross-channel design. The principles are to make experiences convenient, connected, consistent, contextual, and spanning across time. The methods are to think in terms of services, share design work across teams, start by observing customer behaviors, be comfortable with ambiguity, and focus on customer needs rather than specific solutions.
Finally, the document discusses various discovery and solution activities for cross-channel design, such as stakeholder interviews
Introduction to Continuous Integration with JenkinsEric Hogue
Talk on Continuous Integration given at Sunshine PHP 2015 on February 7.
Continuous Integration allows developers to run tests automatically every time code is pushed to source control. We will look at the different tests that a Continuous Integration server can run. How to create a build script so it runs the tests and make sure it produces the needed reports. Finally, how to set up Jenkins to run the build and display the reports.
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
Kief Morris rethinks the infrastructure code delivery lifecycle, advocating for a shift towards composable infrastructure systems. We should shift to designing around deployable components rather than code modules, use more useful levels of abstraction, and drive design and deployment from applications rather than bottom-up, monolithic architecture and delivery.
How RPA Help in the Transportation and Logistics Industry.pptxSynapseIndia
Revolutionize your transportation processes with our cutting-edge RPA software. Automate repetitive tasks, reduce costs, and enhance efficiency in the logistics sector with our advanced solutions.
Advanced Techniques for Cyber Security Analysis and Anomaly DetectionBert Blevins
Cybersecurity is a major concern in today's connected digital world. Threats to organizations are constantly evolving and have the potential to compromise sensitive information, disrupt operations, and lead to significant financial losses. Traditional cybersecurity techniques often fall short against modern attackers. Therefore, advanced techniques for cyber security analysis and anomaly detection are essential for protecting digital assets. This blog explores these cutting-edge methods, providing a comprehensive overview of their application and importance.
Choose our Linux Web Hosting for a seamless and successful online presencerajancomputerfbd
Our Linux Web Hosting plans offer unbeatable performance, security, and scalability, ensuring your website runs smoothly and efficiently.
Visit- https://onliveserver.com/linux-web-hosting/
Measuring the Impact of Network Latency at TwitterScyllaDB
Widya Salim and Victor Ma will outline the causal impact analysis, framework, and key learnings used to quantify the impact of reducing Twitter's network latency.
UiPath Community Day Kraków: Devs4Devs ConferenceUiPathCommunity
We are honored to launch and host this event for our UiPath Polish Community, with the help of our partners - Proservartner!
We certainly hope we have managed to spike your interest in the subjects to be presented and the incredible networking opportunities at hand, too!
Check out our proposed agenda below 👇👇
08:30 ☕ Welcome coffee (30')
09:00 Opening note/ Intro to UiPath Community (10')
Cristina Vidu, Global Manager, Marketing Community @UiPath
Dawid Kot, Digital Transformation Lead @Proservartner
09:10 Cloud migration - Proservartner & DOVISTA case study (30')
Marcin Drozdowski, Automation CoE Manager @DOVISTA
Pawel Kamiński, RPA developer @DOVISTA
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
09:40 From bottlenecks to breakthroughs: Citizen Development in action (25')
Pawel Poplawski, Director, Improvement and Automation @McCormick & Company
Michał Cieślak, Senior Manager, Automation Programs @McCormick & Company
10:05 Next-level bots: API integration in UiPath Studio (30')
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
10:35 ☕ Coffee Break (15')
10:50 Document Understanding with my RPA Companion (45')
Ewa Gruszka, Enterprise Sales Specialist, AI & ML @UiPath
11:35 Power up your Robots: GenAI and GPT in REFramework (45')
Krzysztof Karaszewski, Global RPA Product Manager
12:20 🍕 Lunch Break (1hr)
13:20 From Concept to Quality: UiPath Test Suite for AI-powered Knowledge Bots (30')
Kamil Miśko, UiPath MVP, Senior RPA Developer @Zurich Insurance
13:50 Communications Mining - focus on AI capabilities (30')
Thomasz Wierzbicki, Business Analyst @Office Samurai
14:20 Polish MVP panel: Insights on MVP award achievements and career profiling
論文紹介:A Systematic Survey of Prompt Engineering on Vision-Language Foundation ...Toru Tamaki
Jindong Gu, Zhen Han, Shuo Chen, Ahmad Beirami, Bailan He, Gengyuan Zhang, Ruotong Liao, Yao Qin, Volker Tresp, Philip Torr "A Systematic Survey of Prompt Engineering on Vision-Language Foundation Models" arXiv2023
https://arxiv.org/abs/2307.12980
Quality Patents: Patents That Stand the Test of TimeAurora Consulting
Is your patent a vanity piece of paper for your office wall? Or is it a reliable, defendable, assertable, property right? The difference is often quality.
Is your patent simply a transactional cost and a large pile of legal bills for your startup? Or is it a leverageable asset worthy of attracting precious investment dollars, worth its cost in multiples of valuation? The difference is often quality.
Is your patent application only good enough to get through the examination process? Or has it been crafted to stand the tests of time and varied audiences if you later need to assert that document against an infringer, find yourself litigating with it in an Article 3 Court at the hands of a judge and jury, God forbid, end up having to defend its validity at the PTAB, or even needing to use it to block pirated imports at the International Trade Commission? The difference is often quality.
Quality will be our focus for a good chunk of the remainder of this season. What goes into a quality patent, and where possible, how do you get it without breaking the bank?
** Episode Overview **
In this first episode of our quality series, Kristen Hansen and the panel discuss:
⦿ What do we mean when we say patent quality?
⦿ Why is patent quality important?
⦿ How to balance quality and budget
⦿ The importance of searching, continuations, and draftsperson domain expertise
⦿ Very practical tips, tricks, examples, and Kristen’s Musts for drafting quality applications
https://www.aurorapatents.com/patently-strategic-podcast.html
Best Programming Language for Civil EngineersAwais Yaseen
The integration of programming into civil engineering is transforming the industry. We can design complex infrastructure projects and analyse large datasets. Imagine revolutionizing the way we build our cities and infrastructure, all by the power of coding. Programming skills are no longer just a bonus—they’re a game changer in this era.
Technology is revolutionizing civil engineering by integrating advanced tools and techniques. Programming allows for the automation of repetitive tasks, enhancing the accuracy of designs, simulations, and analyses. With the advent of artificial intelligence and machine learning, engineers can now predict structural behaviors under various conditions, optimize material usage, and improve project planning.
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
BT & Neo4j: Knowledge Graphs for Critical Enterprise Systems.pptx.pdfNeo4j
Presented at Gartner Data & Analytics, London Maty 2024. BT Group has used the Neo4j Graph Database to enable impressive digital transformation programs over the last 6 years. By re-imagining their operational support systems to adopt self-serve and data lead principles they have substantially reduced the number of applications and complexity of their operations. The result has been a substantial reduction in risk and costs while improving time to value, innovation, and process automation. Join this session to hear their story, the lessons they learned along the way and how their future innovation plans include the exploration of uses of EKG + Generative AI.
6. “Don't waste my time, buddy.
You're just a dogsbody sysadmin; I write the software and
you merely service it.
So just shut up with your petty concerns and do as I say,
OK?”
Taken from http://serverfault.com/questions/16698/what-do-you-wish-developers-would-do-differently
7. "The Fuckup Fairy is a developer
who has only been on the project
for 6 months or so ...
... This touched off The Pontificator.
The Pontificator is another developer ..."
Taken from alt.sysadmin.recovery
8. It shouldn’t have to be like this
http://www.flickr.com/photos/angells60640/3411660099/
9. “That brings me to Dennis Ritchie. Our collaboration has
been a thing of beauty” --Ken Thompson
37. Thank you!
More at:
http://build-doctor.com
http://twitter.com/builddoctor
Editor's Notes
* do the check on the particpants
* summary is
** The IT industry is broken
** We’re caught up in silos
** We’re failing to deliver because of it
** And some people don’t even enjoy their work
Entered IT Industry in 1991. First task: rolling up cables to exacting standards of fastidious boss
Brief foray as screwdriver and TCP fix-er
Solaris Admin
build and release manager
blogger at build-doctor.com
Example: sequence 2001-2004
Impact: we certainly delivered late
Bad devs, who the ops team didn't help, but chose to get pissed off at
Good ops team, but attitude poor in retrospect
Vicious cycle of passive aggression, political needling
Social group theory
Entire department collocated in room but argued over email and IM
Who gives out these incentives? Sociopaths? Sociopaths do well in organisations
Do you think these guys argued about who did the deployments
Most teams seem to have an adversarial approach "we just need to get this past the operations" "damn developers keep dumping crap on us"
Does an adversarial approach work well in many situations, even in legal?
Collaboration is key to all working in organisations
Yet we pass work around as if we were assembling TV's
We're passing up effecting collabotation to score points
There's no need for me to cite examples of underskilled developers when the DailyWTF does it so well.
Worked with many, many developers who were out of their league but had incentives to stay in the game
You won't get co-operation with someone who doesn't feel equal to the other party
Most of us don't know how to hire good developers
Warning signs: won't pair, prefer to work alone, talking loud, but delivering little
Exact same problem with sysadmins
Sometimes harder to document, but go to pub with sysadmins: the stories are there
We don't know how to hire them either
Warning signs, everything is a security risk, excessive caution, failing to use sudo or SSH pubkey
If people aren't just conditioned to make meetings, plan 'catch-ups', telephone calls, write email
Then they are using the organisation to hide - policy is my favourite
People,
Process
Technology
Why people?
Gerald Weinburg’s Second law of consulting “No matter how it looks at first, it’s always a people problem.”
We know that email removes most of the communication.
One study at UCLA indicated that up to 93 percent of communication effectiveness is determined by nonverbal cues. Another study indicated that the impact of a performance was determined 7 percent by the words used, 38 percent by voice quality, and 55 percent by the nonverbal communication.
And we’re really, really bad at writing them, too. Stop!
They may not share your views, but that doesn’t stop them being valuable
Sysadmins and developers have different skills, but there’s no excuse to disrespect anybody because of their career path
It's a meeting with a purpose
You might learn something
Part of theme of engaging early with sysadmins
Sysadmins love problem solving
Usually don't like being presented with a problem and solution
It's that whole team thing. Can be boring, but better to overcommunicate.
Nonverbal communication again
Face-to-face is only way to overcome communication barriers
Further the distance, less the effort
Different building might as well be in a different city
Collective code ownership is a good rule. Reduces bus factor and onboarding and allows us to plow forward with development
But why do we stop there?
We slow down when the release and build scripts are owned by 1 person.
Pure Theory of Contstraints to
Often people who maintain these aren’t be best coders in the room
Who wants that?
This won't feel natural at first
Harder. because of lack of tools (pairing with vi can be hard)
Great, safe way to learn
Paiting with DBA
You're faking it unless you count them as done when they are in production
This gives incentive to help the deploy effort
An operations job is about tracking and controlling change. Why wouldn't you?
I suspect the answer is cultural - it's seen as a developer
But we’re all developers
Don't use fancy vendor tools, don't use CVS either
Why watch someone flounder?
Some sysadmins don't use SSH properly. Those who do, do well. Help developers become more fluent on the systems that you manage. They'll only thank you.
Knowing that your code is undeployable should focus the mind. I've done this, and it helped the testing no end, and it helped derisk the prod deploys
Continuous deployment might not be 50 days to prod
But why not 50 a day to a test server?
CD needs adapting for some domains
But you can take the principles
You don't need to choose one or the other
You need to get good at modelling your systems
And then the choice of tool should come second
Remember this is a VI vs Emacs/Ruby vs Python - you should be focusing on automating well - the other guys are the ones telling the CTO that installing stuff by hand is cool
Big visible state of your build: fine. What about your build infrastructure?
@auxesis compares the two
Don't you want to know? What about production? Is that broken?
It's easy to write plugins to monitoring systems.
OS packages contain useful metadata
It means you can match up your application and its native dependencies
Doesn't help developers all that much but it helps sysadmins a boatload
Development help in delivering these can be a godsend to devs, and likely to make you a hero
Tripwire effect
"how often do you ask the sysadmin what they want? - or do you just show up and ask them to deploy something?
What works for your desktop and your very first single-node test environment may not work for all environments
This will hurt everyone unless you head it off at the pass
Seems obvious but I've had people fight me on it
Making development systems too easy to deploy to causes deployment problems down the line.
Make development a little more like production and gradually roll it out.
YouDevise have UAT at the production facility
Feedback loop. If you can't see what your code does in production, how can you improve?
Little tweaks here and there go unoticed. REbuilding frequently forces us to have a process. rebuilding any system is possible these days with puppet.