Become the best software developer you can be
Apr 19 2015
Mar 20 2016
Dec 13 2016
Jun 25 2018
Jun 07 2014
Apr 29 2019
Dec 15 2014
Nov 25 2019
Sep 18 2017
Jan 28 2016
Dec 28 2016
Jun 22 2014
May 29 2017
Feb 10 2015
Oct 28 2019
May 11 2017
Apr 03 2018
Oct 12 2013
Feb 27 2016
Aug 21 2017
It’s all about telemetry and feedback as we continue learning from The DevOps Handbook, while Joe knows his versions, Michael might have gone crazy if he didn’t find it, and Allen has more than enough muscles.
For those that use their podcast player to read these show notes, did you know that you can find them at https://www.codingblocks.net/episode138? Well, you can. And now you know, and knowing is half the battle.
postgresdatabase orange. This color coding will be applied to both the navigation tree and the open file editors (i.e. tabs).
Aug 03 2020
Our journey into the world of DevOps continues with The DevOps Handbook as Michael doesn’t take enough tangents, Joe regrets automating the build, err, wait never regrets (sorry), and ducks really like Allen.
If you’re reading these show notes via your podcast player, you can find this episode’s full show notes at https://www.codingblocks.net/episode137, where you can be a part of the conversation.
I really hope laptop manufacturers stop putting numpads on laptops so we can stop the left justification madness. pic.twitter.com/hab359IdyN— Michael Outlaw (@iamwaltuo) July 17, 2020
CTRL+SHIFT+Vto see and choose from the list of items recently copied to the clipboard.
Just a thought. I know lots of people who contemplate paying for shared workspaces to get out of the house. Maybe all you need is a tethering plan for your phone, a nice butt pad, and a pretty park near you. #myofficetoday pic.twitter.com/0eSRZUGK1I— Allen Underwood (@theallenu) July 2, 2020
Jul 20 2020
We begin our journey into the repeatable world of DevOps by taking cues from The DevOps Handbook, while Allen loves all things propane, Joe debuts his “singing” career with his new music video, and Michael did a very bad, awful thing.
These show notes can be found at https://www.codingblocks.net/episode136 for those reading this via their podcast player.
I am truly, humbly honored to have been awarded the @MVPAward again. Being a part of such an amazing community of folks offering their time and experience is just incredible. #MVPBuzz— Allen Underwood (@theallenu) July 2, 2020
Huge thanks to @iamwaltuo @THEjoezack and @CodingBlocks for helping make this happen. pic.twitter.com/sv8Pd1flIx
The reality though …
Ideally though …
All of this allows entire systems to be spun up quickly making this …
“When developers put all their application source files and configurations in version control, it becomes the single repository of truth that contains the precise intended state of the system.”The DevOps Handbook
Here are the types of things that should be stored in source control:
SHIFTtwice to search everywhere in your IntelliJ project: Search for a target by name (Search everywhere) (JetBrains)
ALT+F1in Datagrip to see available options for a schema object such as navigating to it in the left pane.
Jul 06 2020
We review the Stack Overflow Developer Survey in the same year it was created for the first time ever, while Joe has surprising news about the Hanson Brothers, Allen doesn’t have a thought process, and Michael’s callback is ruined.
If you’re reading these show notes via your podcast player, you can find this episode’s full show notes and join the conversation at https://www.codingblocks.net/episode135.
Jun 22 2020
As we learn from Google about how to navigate a code review, Michael learns to not give out compliments, Joe promises to sing if we get enough new reviews, and Allen introduces a new section to the show.
For those reading this via their podcast player, this episode’s full show notes can be found at https://www.codingblocks.net/episode134.
A couple starting questions when reviewing a CL (changelist):
Jun 08 2020
We learn what to look for in a code review while reviewing Google’s engineering practices documentation as Michael relates patterns to choo-choos, Joe has a “weird voice”, and Allen has a new favorite portion of the show.
Are you reading this via your podcast player? You can find this episode’s full show notes at https://www.codingblocks.net/episode133 where you can also join the conversation.
A particular type of complexity is over-engineering, where developers have made the code more generic than it needs to be, or added functionality that isn’t presently needed by the system. Reviewers should be especially vigilant about over-engineering. Encourage developers to solve the problem they know needs to be solved now, not the problem that the developer speculates might need to be solved in the future. The future problem should be solved once it arrives and you can see its actual shape and requirements in the physical universe.Google’s Engineering Practices documentation
TODOstatements for cleaning up existing code if outside the scope of the CL.
May 26 2020
We dig into Google’s engineering practices documentation as we learn how to code review while Michael, er, Fives is done with proper nouns, Allen can’t get his pull request approved, and Joe prefers to take the average of his code reviews.
In case you’re reading this via your podcast player, this episode’s full show notes can be found at https://www.codingblocks.net/episode132. Be sure to check it out and join the conversation.
Q: What is a code review?A: When someone other than the author of the code examines that code.
Q: But why code review?A: To ensure high quality standards for code as well as helping ensure more maintainable code.
The purpose of the code review is to make sure code quality is improving over time.
Reviewers should favor approving the changes when the code health is improved even if the changes aren’t perfect. There’s no such thing as perfect code, just better code.
Code that worsens the overall quality or health of a system should not be admitted unless it’s under extreme/emergency circumstances.
A small change that:
Code reviews can absolutely be used as a tool for mentoring, for example teaching design patterns, explaining algorithms, etc., but if it’s not something that needs to be changed for the PR to be completed, note it as a “Nit” or “Note”.
NEVER let a change sit around just because the reviewer and coder can’t come to an agreement.
May 11 2020
We gather around the water cooler at 6 foot distances as Michael and Joe aren’t sure what they streamed, we finally learn who has the best fries, at least in the US, and Allen doesn’t understand evenly distributing your condiments.
For those reading this via their podcast player, this episode’s full show notes can be found at https://www.codingblocks.net/episode131. Stop by and join in on the conversation.
helm uninstalldoesn’t remove persistent volumes nor their claims.
helm uninstall RELEASE_NAME, delete the persistent volume claim using
kubectl delete pvc PVC_NAMEto remove the claim, which depending on the storage class and reclaim policy, will also remove the persistent volume. Otherwise, you’d need to manually remove the persistent volume using
kubectl delete pv PV-NAME.
Apr 27 2020
We dig into the details of how databases use B-trees as we continue our discussion of Designing Data-Intensive Applications while Michael’s description of median is awful, live streaming isn’t for Allen, and Joe really wants to bring us back from the break.
For those reading this via their podcast player, this episode’s full show notes can be found at https://www.codingblocks.net/episode130 in all their glory. Check it out, as Joe would say, and join the conversation.
refreshenvfor short, that you can use to update the environment variables in your current PowerShell session, much like
. $HOME/.profilefor MacOS/Linux. (Chocolatey)
docker statsto monitor the usage of your running Docker containers. It’s like
topfor Docker. (Docker)
Apr 13 2020
Since we can’t leave the house, we discuss what it takes to effectively work remote while Allen’s frail body requires an ergonomic keyboard, Joe finally takes a passionate stance, and Michael tells them why they’re wrong.
Reading these show notes via your podcast player? You can find this episode’s full show notes at https://www.codingblocks.net/episode129 and be a part of the conversation.
Amateur tip: need to kick a build? Gonna squash anyway? Use –allow-empty to do a commit with no files added or actual changes. pic.twitter.com/3P0Twdbast— Nick Craver (@Nick_Craver) March 21, 2020
Need to take a break from Netflix before you binge-watch the entire library? Introducing our brand new concert series: #MetallicaMondays, debuting tonight on our YouTube channel and on Facebook!— Metallica (@Metallica) March 23, 2020
Tune in at 8 PM EDT to watch Metallica: Live at Slane Castle – June 8, 2019! pic.twitter.com/91Eymjx2jr
Mar 30 2020
Mar 16 2020
Mar 02 2020
Feb 17 2020
Feb 03 2020
Jan 20 2020
Jan 06 2020
Dec 23 2019
Dec 09 2019
Nov 25 2019
Nov 12 2019