From e59d15d75d3b0e18251444cccc2694e28aad50d3 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sat, 26 Aug 2023 14:50:13 -0500 Subject: [PATCH 01/13] begin work on about page --- config/_default/menu.toml | 6 ++++++ content/about.md | 24 ++++++++---------------- 2 files changed, 14 insertions(+), 16 deletions(-) diff --git a/config/_default/menu.toml b/config/_default/menu.toml index 90d952b..4fc7ef2 100644 --- a/config/_default/menu.toml +++ b/config/_default/menu.toml @@ -4,6 +4,12 @@ # url = "/about/" # weight = 10 +[[main]] + identifier = "about" + name = "about" + url = "/about/" + weight = -100 + [[main]] identifier = "projects" name = "projects" diff --git a/content/about.md b/content/about.md index b08b449..7d12e14 100644 --- a/content/about.md +++ b/content/about.md @@ -1,27 +1,19 @@ +++ -title = "About" -description = "Hugo, the world's fastest framework for building websites" -date = "2019-02-28" -aliases = ["about-us", "about-hugo", "contact"] -author = "Hugo Authors" +title = "Hi, I'm John." +description = "A brief introduction to me, this blog, and the kinds of things you're likely to see here." +aliases = ["tldr"] timeless = "true" comments = false +++ -Written in Go, Hugo is an open source static site generator available under the [Apache Licence 2.0.](https://github.com/gohugoio/hugo/blob/master/LICENSE) Hugo supports TOML, YAML and JSON data file types, Markdown and HTML content files and uses shortcodes to add rich content. Other notable features are taxonomies, multilingual mode, image processing, custom output formats, HTML/CSS/JS minification and support for Sass SCSS workflows. +You've (somehow) managed to stumble upon my dark corner on the internet.[^1] -Hugo makes use of a variety of open source projects including: +## Who am I? +I've always enjoyed writing code and solving problems, but learned early in my career that I didn't want to be a full-time programmer. So I spent many years administering virtual systems and their supporting infrastructure, while writing scripts to help automate the management of those systems. -* https://github.com/yuin/goldmark -* https://github.com/alecthomas/chroma -* https://github.com/muesli/smartcrop -* https://github.com/spf13/cobra -* https://github.com/spf13/viper -Hugo is ideal for blogs, corporate websites, creative portfolios, online magazines, single page applications or even a website with thousands of pages. +I'm a part of a small *Platforms Engineering* team inside a large corporation. We preach the Good Word of *DevSecOps* and help our internal customers modernize the way they build, deploy, and ship products. -Hugo is for people who want to hand code their own website without worrying about setting up complicated runtimes, dependencies and databases. +[^1]: Congrats? -Websites built with Hugo are extremely fast, secure and can be deployed anywhere including, AWS, GitHub Pages, Heroku, Netlify and any other hosting provider. -Learn more and contribute on [GitHub](https://github.com/gohugoio). From 389597e5b3e5272645cfc8496e16b7c63f42d268 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sat, 26 Aug 2023 14:50:34 -0500 Subject: [PATCH 02/13] draft: how to ask technical questions --- .../how-to-ask-technical-questions/index.md | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 content/posts/how-to-ask-technical-questions/index.md diff --git a/content/posts/how-to-ask-technical-questions/index.md b/content/posts/how-to-ask-technical-questions/index.md new file mode 100644 index 0000000..1e1a380 --- /dev/null +++ b/content/posts/how-to-ask-technical-questions/index.md @@ -0,0 +1,32 @@ +--- +title: How to Ask Technical Questions +date: 2023-08-26 +timeless: true +draft: true +description: There are no dumb questions - but there are smarter (and dumber) ways to ask them. +--- +I spend a lot of my time and energy answering technical questions[^1]. How a question is asked plays a big factor in how effectively I'll be able to answer it. Years ago I came across Eric Steven Raymond's [How To Ask Questions The Smart Way](http://www.catb.org/~esr/faqs/smart-questions.html) and it really resonated with me. I wish everyone would read it before asking for technical help but I recognize it's a pretty large doc at this point. So I thought I'd summarize some of the main points that I would like to emphasize. + +## Research Before You Ask + +## Clear and Specific Subject Line + +## Correct Spelling and Grammar + +## Be Precise + +## ...But Not Unnecessarily Verbose + +## Describe the Symptoms, Not Your Guesses + +## Describe the Goal, Not the Step + +## Be Explicit About Your Question + +## Be Courteous + +## Follow Up with Solution + + + +[^1]: Both professionally as well as "for fun" because I love scratching that troubleshooting itch. From d1c606410f64a45ca4ca44dc28a313cf62cb3432 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sat, 26 Aug 2023 17:19:28 -0500 Subject: [PATCH 03/13] update draft --- .../how-to-ask-technical-questions/index.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/content/posts/how-to-ask-technical-questions/index.md b/content/posts/how-to-ask-technical-questions/index.md index 1e1a380..7d74c11 100644 --- a/content/posts/how-to-ask-technical-questions/index.md +++ b/content/posts/how-to-ask-technical-questions/index.md @@ -7,19 +7,36 @@ description: There are no dumb questions - but there are smarter (and dumber) wa --- I spend a lot of my time and energy answering technical questions[^1]. How a question is asked plays a big factor in how effectively I'll be able to answer it. Years ago I came across Eric Steven Raymond's [How To Ask Questions The Smart Way](http://www.catb.org/~esr/faqs/smart-questions.html) and it really resonated with me. I wish everyone would read it before asking for technical help but I recognize it's a pretty large doc at this point. So I thought I'd summarize some of the main points that I would like to emphasize. +## Know Who You're Asking +The sorts of people who choose to spend their time answering questions do it because they truly enjoy helping others. They thrive on interesting and challenging questions... but they're also busy, so may filter or pass over questions that don't seem as interesting. If your question or issue really is a tricky one, you need to take steps to communicate that. + +> Good questions are a stimulus and a gift. + ## Research Before You Ask +One of the best ways to demonstrate that your question poses an interesting challenge is to show that you've already put in some effort on your part. Search the web, read the documentation, and try to find the answer on your own. If you're still stuck, mention what you've already tried and why it didn't help. Show that you've already invested some time and energy into solving the problem yourself and you'll be more likely to get a response. ## Clear and Specific Subject Line +The subject line is your best chance to get someone to look at your question. If you're posting on a help forum, it's understood that you're seeking assistance; you don't need to put "help" anywhere in the subject line. Instead, use that space to clearly describe the problem you're facing, including any specific devices or software involved. ## Correct Spelling and Grammar +We need to understand what you're trying to ask before we can answer it, and that's hard to do if your question is loaded with typos and mistakes. It doesn't have to be perfect, but *please* make an effort. Once you've written your query, take the time to read back over it and make sure it makes sense. This is another chance to show us that you're serious about solving the problem. + +{{% notice tip %}}If you're posting on an English-language forum and you're not comfortable communicating in English, you might try using an online translation tool to help write your question. In that case, please also mention that you used a translation tool so that we can be more understanding of any irregular grammar or phrasing. +{{% /notice %}} ## Be Precise +Generally speaking, the more detail you can provide about your problem, the better. -## ...But Not Unnecessarily Verbose +- What system/device are you using? Be specific about the model and/or version. +- What are the symptoms of the problem? Are there any error messages? If so, include those *in full*. +- When did the problem start? Is this a new problem or has it never worked? What (if anything) changed before the problem started? +- What steps have you already taken to try and solve the problem? Don't say "I've tried everything" (which tells us nothing); tell us *exactly* what you've tried. ## Describe the Symptoms, Not Your Guesses +If you're not sure what's causing the problem, don't guess. Sharing a guess which isn't correct can lead people down the wrong path and waste everyone's time. Focus instead on accurately describing the symptoms and leave the diagnosis to the kind souls trying to help you. ## Describe the Goal, Not the Step +Similarly, when trying to accomplish a particular goal, share that goal rather than just focusing on the step you're trying to take. It's easy to get fixated on a small step (which may or may not be the correct one to take) and miss the better solution. ## Be Explicit About Your Question From b90c2321886ad0a1b8f3b1b580d568c67d855791 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sun, 27 Aug 2023 14:02:50 -0500 Subject: [PATCH 04/13] cleanup unneeded drafts --- .../how-to-ask-technical-questions/index.md | 49 ------------------- .../the-future-of-virtuallypotato/index.md | 26 ---------- 2 files changed, 75 deletions(-) delete mode 100644 content/posts/how-to-ask-technical-questions/index.md delete mode 100644 content/posts/the-future-of-virtuallypotato/index.md diff --git a/content/posts/how-to-ask-technical-questions/index.md b/content/posts/how-to-ask-technical-questions/index.md deleted file mode 100644 index 7d74c11..0000000 --- a/content/posts/how-to-ask-technical-questions/index.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: How to Ask Technical Questions -date: 2023-08-26 -timeless: true -draft: true -description: There are no dumb questions - but there are smarter (and dumber) ways to ask them. ---- -I spend a lot of my time and energy answering technical questions[^1]. How a question is asked plays a big factor in how effectively I'll be able to answer it. Years ago I came across Eric Steven Raymond's [How To Ask Questions The Smart Way](http://www.catb.org/~esr/faqs/smart-questions.html) and it really resonated with me. I wish everyone would read it before asking for technical help but I recognize it's a pretty large doc at this point. So I thought I'd summarize some of the main points that I would like to emphasize. - -## Know Who You're Asking -The sorts of people who choose to spend their time answering questions do it because they truly enjoy helping others. They thrive on interesting and challenging questions... but they're also busy, so may filter or pass over questions that don't seem as interesting. If your question or issue really is a tricky one, you need to take steps to communicate that. - -> Good questions are a stimulus and a gift. - -## Research Before You Ask -One of the best ways to demonstrate that your question poses an interesting challenge is to show that you've already put in some effort on your part. Search the web, read the documentation, and try to find the answer on your own. If you're still stuck, mention what you've already tried and why it didn't help. Show that you've already invested some time and energy into solving the problem yourself and you'll be more likely to get a response. - -## Clear and Specific Subject Line -The subject line is your best chance to get someone to look at your question. If you're posting on a help forum, it's understood that you're seeking assistance; you don't need to put "help" anywhere in the subject line. Instead, use that space to clearly describe the problem you're facing, including any specific devices or software involved. - -## Correct Spelling and Grammar -We need to understand what you're trying to ask before we can answer it, and that's hard to do if your question is loaded with typos and mistakes. It doesn't have to be perfect, but *please* make an effort. Once you've written your query, take the time to read back over it and make sure it makes sense. This is another chance to show us that you're serious about solving the problem. - -{{% notice tip %}}If you're posting on an English-language forum and you're not comfortable communicating in English, you might try using an online translation tool to help write your question. In that case, please also mention that you used a translation tool so that we can be more understanding of any irregular grammar or phrasing. -{{% /notice %}} - -## Be Precise -Generally speaking, the more detail you can provide about your problem, the better. - -- What system/device are you using? Be specific about the model and/or version. -- What are the symptoms of the problem? Are there any error messages? If so, include those *in full*. -- When did the problem start? Is this a new problem or has it never worked? What (if anything) changed before the problem started? -- What steps have you already taken to try and solve the problem? Don't say "I've tried everything" (which tells us nothing); tell us *exactly* what you've tried. - -## Describe the Symptoms, Not Your Guesses -If you're not sure what's causing the problem, don't guess. Sharing a guess which isn't correct can lead people down the wrong path and waste everyone's time. Focus instead on accurately describing the symptoms and leave the diagnosis to the kind souls trying to help you. - -## Describe the Goal, Not the Step -Similarly, when trying to accomplish a particular goal, share that goal rather than just focusing on the step you're trying to take. It's easy to get fixated on a small step (which may or may not be the correct one to take) and miss the better solution. - -## Be Explicit About Your Question - -## Be Courteous - -## Follow Up with Solution - - - -[^1]: Both professionally as well as "for fun" because I love scratching that troubleshooting itch. diff --git a/content/posts/the-future-of-virtuallypotato/index.md b/content/posts/the-future-of-virtuallypotato/index.md deleted file mode 100644 index 2335552..0000000 --- a/content/posts/the-future-of-virtuallypotato/index.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: "The Future of virtuallypotato" # Title of the blog post. -date: 2023-08-11T10:19:10-05:00 # Date of post creation. -# lastmod: 2023-08-11T10:19:10-05:00 # Date when last modified -description: "We've been around the internet long enough to know what a blog post about 'a commitment to' or 'the future of' means." # Description used for search engine. -featured: false # Sets if post is a featured post, making appear on the home page side bar. -draft: true # Sets whether to render this page. Draft of true will not be rendered. -toc: true # Controls if a table of contents should be generated for first-level links automatically. -usePageBundles: true -# menu: main -# featureImage: "file.png" # Sets featured image on blog post. -# featureImageAlt: 'Description of image' # Alternative text for featured image. -# featureImageCap: 'This is the featured image.' # Caption (optional). -# thumbnail: "thumbnail.png" # Sets thumbnail image appearing inside card on homepage. -# shareImage: "share.png" # Designate a separate image for social media sharing. -codeLineNumbers: false # Override global value for showing of line numbers within code block. -# series: Tips # Projects, Scripts, vRA8, K8s on vSphere -tags: - - meta -comment: true # Disable comment if false. ---- - -_You've probably been around the internet long enough to know what a blog post about "our commitment to" or "the future of" means..._ - -When I started sharing my technical notes here at `virtuallypotato.com`, I was excited about VMware's products and was really enjoying my early efforts with vRealize Automation (now Aria Automation). - From 3e4038b2cb7f6bc150f392ed602cb4ae41c3fbd4 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sun, 27 Aug 2023 14:02:59 -0500 Subject: [PATCH 05/13] update draft --- content/posts/how-to-ask-for-help/index.md | 64 ++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 content/posts/how-to-ask-for-help/index.md diff --git a/content/posts/how-to-ask-for-help/index.md b/content/posts/how-to-ask-for-help/index.md new file mode 100644 index 0000000..f809ef8 --- /dev/null +++ b/content/posts/how-to-ask-for-help/index.md @@ -0,0 +1,64 @@ +--- +title: How to Ask For Help +date: 2023-08-26 +timeless: true +draft: true +description: There are no dumb questions - but there are smarter (and dumber) ways to ask them. +--- +I spend a lot of my time and energy answering technical questions, both professionally and "for fun" as a way to scratch that troubleshooting itch. How a question is asked plays a big factor in how effectively I'll be able to answer it. + +Years ago I came across Eric Steven Raymond's [How To Ask Questions The Smart Way](http://www.catb.org/~esr/faqs/smart-questions.html) and it really resonated with me. I wish everyone would read it before asking for technical help but I recognize it's a pretty large doc so that's an unrealistic wish. There are a few main points I'd like to emphasize though. + +> Good questions are a stimulus and a gift. + +The sorts of people who choose to spend their time answering questions do it because they enjoy helping others. They thrive on interesting and challenging questions... but they're also busy, so may pass over questions that don't seem as interesting or have been asked (and answered!) countless times before. You're not just asking for an answer to your question - you're also asking for someone else to care enough about your problem to spend their time helping you. Put some time and effort into your question and you'll be more likely to get a helpful response. + +### Before You Ask... +One of the best ways to demonstrate that your question isn't going to waste anyone's time is to show that you've already made an effort to find the solution on your own. Search the web, read the documentation, browse posts on the forum you're about to post on, and maybe try a few different ways of tackling the problem. + +If you're still stuck, you can share in your message what you've already tried and why it didn't help. This will help people understand your problem and avoid suggesting solutions you've already tried. + +### Write a Clear Subject +The subject line is your best chance to get someone to look at your question. If you're posting on a help forum, it's understood that you're seeking assistance; you don't need to put "help" anywhere in the subject line. Instead, use that space to clearly describe the problem you're facing, including any specific devices or software involved. + +A good subject line is descriptive yet concise. + +Not great: "Help! Upgrade failed!" + +Much better: "Upgrade to v2.0.1 failed with error code: 0x80004005" + +### Use Correct Spelling and Grammar +We need to understand what you're trying to ask before we can answer it, and can be hard to do if your question is loaded with typos and mistakes. It doesn't have to be perfect, but *please* make an effort. + +Once you've written your query, take the time to read back over it and make sure it makes sense. This is another chance to show us that you're serious about solving the problem. + +Your helpers aren't going to judge you for linguistic errors but such mistakes may make it difficult for them to understand your problem. If you're not comfortable writing in English, try using an online translation tool to help write your question. In that case, please also mention that you used a translation tool so that people know to be extra careful when reading your question. + +### Be Precise +The more details you can provide about your problem, the better. + +- What system/device/application are you using? Be specific about the model and/or version. +- What are the symptoms of the problem? Are there any error messages? If so, include those *in full*. +- When did the problem start? Is this a new problem or has it never worked? What (if anything) changed before the problem started? +- What steps have you already taken to try and solve the problem? Don't say "I've tried everything" (which tells us nothing); tell us *exactly* what you've tried. +- If your research yielded other reports of the same problem but no solution, include links to those reports. + +Share anything you think might be relevant up front. It's easier for us to skip over details we don't need than to have to go back and forth asking for more information. + +### Describe the Symptoms, Not Your Guesses +If you're not sure what's causing the problem, don't guess. Sharing a guess which isn't correct can lead people down the wrong path and waste everyone's time. Focus instead on accurately describing the symptoms and leave the diagnosis to the kind souls trying to help you. + +After all, if you knew exactly what was wrong then you probably wouldn't be asking for help in the first place. + +### Describe the Goal, Not the Step +Similarly, when trying to accomplish a particular goal, share that goal rather than just focusing on the step you're trying to take. It's easy to get fixated on a small step (which may or may not be the correct one to take) and miss the better solution. Describe the Big Picture version of what you hope to do and let us help you figure out the best way to get there. + +### Be Courteous +Remember that you're asking for help, not demanding it, and that the people who will be helping you do so voluntarily. They're not getting paid for their time and are under no obligation to help you. Be polite and respectful of their time and effort. + +Their replies to you may be terse or blunt. It's not because they are offended by your question, but rather because there are a lot of people asking for their help and they're trying to maximize their time. Assume that their responses are offered in good faith, just as they'll assume the same of you. Don't take offense, but also don't be afraid to ask for clarification if you don't understand something. + +### Follow Up with Solution +Once your problem has been solved (either based on the advice you received or on your own), please be sure to report back to let everyone know. If the solution was reached based on the help you received, politely thank those who assisted. If you fixed it by yourself, share how you did it so that others may benefit from your experience (and, again, thank those who offered their time and advice). + + From a20dccbc505fc456219eb5c72ebfce0d89eabe76 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sun, 27 Aug 2023 14:30:47 -0500 Subject: [PATCH 06/13] update with JD's notes --- content/posts/how-to-ask-for-help/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/posts/how-to-ask-for-help/index.md b/content/posts/how-to-ask-for-help/index.md index f809ef8..6aea74b 100644 --- a/content/posts/how-to-ask-for-help/index.md +++ b/content/posts/how-to-ask-for-help/index.md @@ -32,13 +32,13 @@ We need to understand what you're trying to ask before we can answer it, and can Once you've written your query, take the time to read back over it and make sure it makes sense. This is another chance to show us that you're serious about solving the problem. -Your helpers aren't going to judge you for linguistic errors but such mistakes may make it difficult for them to understand your problem. If you're not comfortable writing in English, try using an online translation tool to help write your question. In that case, please also mention that you used a translation tool so that people know to be extra careful when reading your question. +Your helpers aren't going to judge you for linguistic errors but such mistakes may make it difficult for them to understand your problem. If you're not comfortable writing in English, go ahead and post in your native language. There are plenty of tools that your helper can use to translate your message, and those will be much more effective if the original message is clearly written in the original language. ### Be Precise The more details you can provide about your problem, the better. - What system/device/application are you using? Be specific about the model and/or version. -- What are the symptoms of the problem? Are there any error messages? If so, include those *in full*. +- What are the symptoms of the problem? Are there any error messages? If so, include those *in full*. Screenshots can be a big help here. - When did the problem start? Is this a new problem or has it never worked? What (if anything) changed before the problem started? - What steps have you already taken to try and solve the problem? Don't say "I've tried everything" (which tells us nothing); tell us *exactly* what you've tried. - If your research yielded other reports of the same problem but no solution, include links to those reports. @@ -46,7 +46,7 @@ The more details you can provide about your problem, the better. Share anything you think might be relevant up front. It's easier for us to skip over details we don't need than to have to go back and forth asking for more information. ### Describe the Symptoms, Not Your Guesses -If you're not sure what's causing the problem, don't guess. Sharing a guess which isn't correct can lead people down the wrong path and waste everyone's time. Focus instead on accurately describing the symptoms and leave the diagnosis to the kind souls trying to help you. +If you're not sure what's causing the problem, don't guess. Sharing a guess which isn't correct can lead people down the wrong path and waste everyone's time. Focus instead on accurately describing the symptoms and leave the diagnosis to the kind souls trying to help you. Also, don't say "I know it isn't _____" unless you can also tell us precisely why you think that. After all, if you knew exactly what was wrong then you probably wouldn't be asking for help in the first place. From 7d6303c2c603156d9def2744436a287f21cd9d4e Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sun, 27 Aug 2023 14:56:47 -0500 Subject: [PATCH 07/13] more tweaks from JD --- content/posts/how-to-ask-for-help/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/posts/how-to-ask-for-help/index.md b/content/posts/how-to-ask-for-help/index.md index 6aea74b..7a49d51 100644 --- a/content/posts/how-to-ask-for-help/index.md +++ b/content/posts/how-to-ask-for-help/index.md @@ -54,10 +54,12 @@ After all, if you knew exactly what was wrong then you probably wouldn't be aski Similarly, when trying to accomplish a particular goal, share that goal rather than just focusing on the step you're trying to take. It's easy to get fixated on a small step (which may or may not be the correct one to take) and miss the better solution. Describe the Big Picture version of what you hope to do and let us help you figure out the best way to get there. ### Be Courteous -Remember that you're asking for help, not demanding it, and that the people who will be helping you do so voluntarily. They're not getting paid for their time and are under no obligation to help you. Be polite and respectful of their time and effort. +Remember that you're *asking* for help, not *demanding* it. In many cases, you'll be posting on a user-to-user support community staffed entirely by volunteers. They are under no obligation to help you and will happily disengage if you're abusive or rude. Be polite and respectful of their time and effort. Their replies to you may be terse or blunt. It's not because they are offended by your question, but rather because there are a lot of people asking for their help and they're trying to maximize their time. Assume that their responses are offered in good faith, just as they'll assume the same of you. Don't take offense, but also don't be afraid to ask for clarification if you don't understand something. +Even if you are seeking help from a paid support team, remember that they are people too. Treat them with politeness and respect; not only is it the right way to interact with other humans, but it might keep them interested in helping you. + ### Follow Up with Solution Once your problem has been solved (either based on the advice you received or on your own), please be sure to report back to let everyone know. If the solution was reached based on the help you received, politely thank those who assisted. If you fixed it by yourself, share how you did it so that others may benefit from your experience (and, again, thank those who offered their time and advice). From f5a3a09343f547cb83234cd2cdd78343dcef9ecc Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sun, 27 Aug 2023 14:59:18 -0500 Subject: [PATCH 08/13] publish draft --- content/posts/how-to-ask-for-help/index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/posts/how-to-ask-for-help/index.md b/content/posts/how-to-ask-for-help/index.md index 7a49d51..193f060 100644 --- a/content/posts/how-to-ask-for-help/index.md +++ b/content/posts/how-to-ask-for-help/index.md @@ -2,7 +2,6 @@ title: How to Ask For Help date: 2023-08-26 timeless: true -draft: true description: There are no dumb questions - but there are smarter (and dumber) ways to ask them. --- I spend a lot of my time and energy answering technical questions, both professionally and "for fun" as a way to scratch that troubleshooting itch. How a question is asked plays a big factor in how effectively I'll be able to answer it. From b72d3a4d92de7203344051228d2f1bbd17ea908b Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Sun, 27 Aug 2023 14:59:40 -0500 Subject: [PATCH 09/13] update draft --- content/about.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/about.md b/content/about.md index 7d12e14..a90c490 100644 --- a/content/about.md +++ b/content/about.md @@ -1,6 +1,6 @@ +++ title = "Hi, I'm John." -description = "A brief introduction to me, this blog, and the kinds of things you're likely to see here." +description = "A brief introduction to me, this blog, and what you're likely to see here." aliases = ["tldr"] timeless = "true" comments = false @@ -9,7 +9,9 @@ comments = false You've (somehow) managed to stumble upon my dark corner on the internet.[^1] ## Who am I? -I've always enjoyed writing code and solving problems, but learned early in my career that I didn't want to be a full-time programmer. So I spent many years administering virtual systems and their supporting infrastructure, while writing scripts to help automate the management of those systems. +I've always enjoyed writing code and solving problems, but I learned early in my career that I didn't want to be a full-time programmer. So I instead spent years as a system administrator, first with Windows and Linux servers and then a focus on virtualization. Along the way, I still flexed my coding muscles by writing scripts and tools to help me work more efficiently. + + I'm a part of a small *Platforms Engineering* team inside a large corporation. We preach the Good Word of *DevSecOps* and help our internal customers modernize the way they build, deploy, and ship products. From 996a57db4ce4b0d62ba8dd9227015e44e873bd3e Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Tue, 29 Aug 2023 17:01:26 -0500 Subject: [PATCH 10/13] remove about link from menu, insert in sidebar --- config/_default/menu.toml | 6 ------ layouts/partials/about.html | 3 +-- 2 files changed, 1 insertion(+), 8 deletions(-) diff --git a/config/_default/menu.toml b/config/_default/menu.toml index 4fc7ef2..90d952b 100644 --- a/config/_default/menu.toml +++ b/config/_default/menu.toml @@ -4,12 +4,6 @@ # url = "/about/" # weight = 10 -[[main]] - identifier = "about" - name = "about" - url = "/about/" - weight = -100 - [[main]] identifier = "projects" name = "projects" diff --git a/layouts/partials/about.html b/layouts/partials/about.html index d6c0c92..5e69943 100644 --- a/layouts/partials/about.html +++ b/layouts/partials/about.html @@ -4,10 +4,9 @@

{{ .title }}

{{ partial "tagline.html" . }}
- {{ site.Params.Author }} + {{ site.Params.Author }} {{ end }} -