When I first entered the workforce after college I really wanted to go work in an office. Part of this is that I grew up seeing those who went to offices (mostly on TV and later on in-person) as being people who had life figured out and who doesn’t want that?
As we grow up and spend some time in an office, we learn that no one knows what they are doing. We’re all just making up life as we muddle our way through life and this is even more obvious for our most incompetent co-workers.
I also wanted to work in an office because I knew that if I were to work at home, I would be very tempted to play video games all day and risk getting fired. Luckily when I started working from home full-time in March 2020, I am little more mature than I was in my twenties (although not by much) and I have only been slightly tempted to open up Steam in the middle of the day. …
I have been working for the military for the past 10 years; first as a member of the military and later as a contractor writing software.
You can do things that you would never be able to do anywhere else. The above photo is of one of the jets that I worked on as an avionics journeyman.
I left active duty early through the Palace Chase program to go back to college. …
As a programmer, I tend to write a lot of my code and non-code in VSCode or light-weight tools. And this extends to my Medium articles. Medium used to let you upload Markdown directly into their editor or import the story from a Markdown gist[1]. I believe I’ve found an acceptable alternative to importing Markdown that some developers may appreciate.
In VSCode if you install the Markdown All in One tool, you can get a preview of your Markdown as you type it.
You can see things like:
Reflecting on my journey from dropping out of college, joining the Air Force, going back to college, and now living in my hometown as a Software Engineer / Data Scientist.
Let me start by giving a little of my background to put things into context.
I live in Central New York. There is a community of software engineers who work at local startups and commercial companies, but the main game in town is the Air Force research labs. I was in the Air Force on active duty and for the air national guard for a combined 8 years working as an avionics journeyman. My bachelor’s degree is in Applied Mathematics and my master’s is in Computer Science with a focus in software engineering and mathematics. …
In Concourse, resources are comprised of three parts check
, in
, and out
. Here we will be discussing the out
, what it needs to do, and try to cover some questions you might have when trying to write your own Concourse resource.
The out
can be performed any time you have something you want to put
into it.
check
, in
, and out
.In Concourse, resources are comprised of three parts check
, in
, and out
. Here we will be discussing the in
, what it needs to do, and try to cover some questions you might have when trying to write your own Concourse resource.
The in
is performed after a check
has confirmed there is something there to pull from and has provides information that will be sent to the standard-in of the in
script.
In Concourse, resources are comprised of three parts check
, in
, and out
. Here we will be discussing the check
, what it needs to do, and try to cover some questions you might have when trying to write your own Concourse resource.
The check
is typically performed before anything can use the resource. This can be seen if you click on a resource block (smaller blocks on the left-hand side of a task).
In this article I am going to give a brief overview about resources and link to my GitHub repository with a working Concourse resource written in Python. I will also write subsequent articles going more in-depth about each stage of resource. I will update this article with links to the check
, in
, and out
articles.
Writing a Concourse resource is not terribly difficult, but instructions on how to do so are generally incomplete. I have managed to stitch together a couple of resource using these tutorials and GitHub repository as guidance:
About