Podcast Player

Listen on Apple Podcasts
Listen on Spotify

Episode #3 - Why am I doing this and How

1. Main Reason is Self-Improvement
1. If you teach something to someone, you get better at that thing yourself.
2. It is also a form of continuous learning and keeping your knowledge up to date.
3. What I have learned:
1. It is form of broadcasting which means that there is work involved in getting each episode published.
2. Each episode consists of recording, post-edit, and publishing.
3. I bought a desktop microphone and have a hand-held coming on Monday.
4. I use Audacity, free software, for editing and combining all the tracks for the episode.
1. Noise reduction.
2. Normalization
3. Apply Equalizers
4. Clip out bad segments
5. I use Buzzsprout for my publishing platform.  It will send the rss feed out to the major directories.
6. I use Blogger for my show notes for each episode (you are looking at one of them now).
7. Advertising:  Facebook, LinkedIn, Twitter, etc.
8. Legal Considerations:  Artwork, music (full or clips), royalties, voiceovers, commercial use licenses.
4. I mean to start with short episodes and get longer when the content merits the time (5-20 minutes).
5. I will have longer episodes when I have guests (30-45 minutes).

Episode #2 - What does DevOps mean to you

Episode 2 - What does devops mean to you?
----------------------------------------------------------------------
DevOps is the union of people, process, and technology to continually provide value to customers.

Teams that adopt DevOps culture, practices, and tools become high-performing....building better applications..... faster...... for greater customer value.

The true meaning of DevOps is all about delivering continuous value to customers.

I did a quick google search and found 10-15 well known websites (some are vendor sites) that each had a slightly different definition but they all revolve around people, process and culture.

Tools are a part of it but the people need to have the desire to achieve the goal and the processes should enable the people to do that.

It's many things
-culture
-mindset
-tooling and process


summary
-------
Some say it is a combination of people, process, culture.

set of processes that allow us to deliver and support software more efficiently.

Developers throw it over the wall.

Operations can't stand devs that do that and they then have to get creative to support it.

*** Looking back over these show notes, I see that I have used the word value a lot.  That is because, in my opinion, that is what DevOps is all about....Customer value.

Episode #1 - Introduction to Me

Episode 1 - Personal Introduction

Name: Scott Everhart
Location: North Carolina, USA
Years in industry: 21
Career Progression

•     Dept help desk for 3rd party apps
•     VB developer - real visual basic before .net was on the scene
•     application support and run team
•     java developer
•     java team lead on 3 projects for internal web apps
•     back to 3rd party app support and run team
•     Quality Tool administrator
•     ** Certified Tester Foundation Level (CTFL)
•     Quality Tool Admin and team lead of 8 people
•     Tool enhancements and reporting - quality metrics
•     SCM support and RFP
•     DevOps and automation - first jenkins pipelines with value stream mapping
•     Agile methodology (kanban and scrum)
•     Automation Engineer
•     Application Architect
•     Future State - to be determined

Tools used in Automation

•     Jenkins
•     Puppet
•     Docker
•     Maven
•     Gradle
•     Atlassian tool suite
•     Sonar

Check out the podcast of this same title.

Created a podcast on this same subject with the same title....

Scott Talks Tech