Skip to content

update blog post #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 16, 2021
Merged

update blog post #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ params:
ShowCodeCopyButtons: false
disableSpecial1stPost: false
disableScrollToTop: false
comments: false
comments: true
hidemeta: false
hideSummary: false
showtoc: false
Expand Down
4 changes: 3 additions & 1 deletion content/posts/software-idioms-you-should-know.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@
title: "Software Engineering Idioms You Should Know"
date: 2021-12-15T11:30:03+00:00
weight: 1
cover:
image: "https://i.imgur.com/IaI0TZD.jpg"
---

I have been working as a software engineer for just over five years. Every now and then I encounter a phrase used to describe something during an engineering discussion, where its meaning is not obvious from the words themselves. These kinds of phrases are known as *idioms* - expressions that have a non-literal meaning attached to the phrase. "Break a leg" is a well-known idiom to wish a person good luck.
Expand Down Expand Up @@ -41,7 +43,7 @@ Yak shaving is when you start a task but end up having to complete a number of o

## Technical debt

Technical debt is bad code which is the result of when a development team takes shortcuts in their code delivery in order to meet deadlines. The bad code causes issues down the line leading it to need to be refactored.
Technical debt is the implied cost of reworking an existing codebase or system. It is often incurred as a result of taking a quick and easy option now instead of a creating a better solution which would take longer.

## Bus factor

Expand Down
13 changes: 13 additions & 0 deletions layouts/partials/comments.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
<script src="https://giscus.app/client.js"
data-repo="craicoverflow/craicoverflow.github.io"
data-repo-id="MDEwOlJlcG9zaXRvcnkxMzU1NjMwMzY="
data-category="Blog Posts"
data-category-id="DIC_kwDOCBSHHM4CATbu"
data-mapping="title"
data-reactions-enabled="1"
data-emit-metadata="0"
data-theme="preferred_color_scheme"
data-lang="en"
crossorigin="anonymous"
async>
</script>
14 changes: 0 additions & 14 deletions layouts/partials/post_nav_links.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,17 +17,3 @@
{{- end }}
</nav>
{{- end }}

<script src="https://giscus.app/client.js"
data-repo="craicoverflow/craicoverflow.github.io"
data-repo-id="MDEwOlJlcG9zaXRvcnkxMzU1NjMwMzY="
data-category="Blog Posts"
data-category-id="DIC_kwDOCBSHHM4CATbu"
data-mapping="title"
data-reactions-enabled="1"
data-emit-metadata="0"
data-theme="preferred_color_scheme"
data-lang="en"
crossorigin="anonymous"
async>
</script>