Episode #8 - Interim - Target Audience

A brief discussion about who my target is, what I can provide to them, how they can benefit from it, and a funny story about education.

Episode #7 - Tools - Github

Description of GitHub
- hosted platform for managing your source code from creation/ideation to production
- built-in actions and workflows to control your code build and deploys while not leaving GitHub's platform.

GitHub Project Structure
- It can be as varied as the languages that you can code in.

readme files
- how to tell the world about your GitHub project
- uses markdown for formatting

Pros/Cons of using GitHub
- Easy access for anyone with an internet connection
- Built-in process to enhance automation
- Its in the cloud....always a risk
- Only as good as what you put into it
- Concerns about Intellectual Property
- Concerns about security tokens, passwords, IDs, SSH keys, etc.

Workflows
- automate tasks directly in GitHub

Webhooks
- Used to drive automation tasks with other systems (or within GitHub itself)

GitHub Pages
- a website for your project....done right from your GitHub repo
- can use a custom domain name that you own

Integrations
- Integrates with almost any tool via Webhooks
- GitHUb has developed a lot of their own offerings around certain technologies

Code Review
- It all starts with a pull request
- diffs, history, blame
- embedded chat
- conflict resolution
- Integrations with other code review tools

GitHub Actions (or features/workflows)
- automation workflows built into GitHub
- run on any event
- hosted runners for most major OS flavors
- parallel builds for different OS or browser combination
- supports many languages
- users can build their own runners
- live logging for real-time build debugging
- built in secrets management

GitHub Products
- Atom - IDE
- Electron - Open source cross platform development with javascript, html, and css
- GitHub LFS - Large file storage offering
- IDE Plugins
- Mobile App
- GitHub Marketplace
- GitHub Security Lab

Git Merge Conference in March 2020 - Sponsored by GitHub

Coming up next - A look at BitBucket - Atlassian's Git offering.

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.

Check out the podcast of this same title.

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

Scott Talks Tech