Hi, my name is Dwain.
I love my family and am so blessed to be married to Lauren, with whom I have 3 beautiful children: Judah and Hosea and Avah.
I work as a Software Engineer at Automattic Inc and have been working remotely for the last few years.
This blog is my creative outlet. I enjoy the process of using it as a tool to showcase things I’m learning and perspectives I appreciate.
This article targets Debian docker containers running on MacOS.
HTTP (hypertext transfer protocol) is a set of rules by which your browser retrieves web pages from the internet. HTTP is the same as HTTPS whit the difference being it retrieves pages from the internet in a secure way through a private communication channel.
In our modern age, most sites have this on by default.
When we are developing sites, specifically eCommerce sites, we assume that this would be turned on in the production environment. This post is an attempt to get your development environment even closer to production.
Step 1 – Generate Certificates
For your browser to recognize a site as trusted and secure, it needs to validate the site’s SSL certificate. We will start by creating certs locally. To do this, you need to have OpenSSL installed.
To confirm, type this into your terminal:
You should get the currently installed version as a reply. If not in you will first need to install it. See google for further instructions on this.
Next, change to the root directory of your project, where your docker-compose.yml is. There enter:
openssl genrsa -des3 -out rootCA.key 2048.
You will be prompted for a password, make sure you remember what he is to avoid recreation. This rootCA.key file will be used to create a new root SSL certificate.
To create a new root SSL certificate, valid for 1024 days, type the following command into the terminal. Feel free to change the number of days.
You will be prompted for the password that you set earlier and then some details about your address. Make sure you fill in the qualified hostname as the domain you’re using for testing.
To confirm that all is in order type: ls | grep root. You should now see two files:
Step 2 – Trust the Certificates Root
The files you’ve just created are certificate generator. Before we can trust the certificates we need to trust the generators. For us to trust the certificates generated by these files, we need to tell MacOS to trust the root files.
To trust the root files, open Keychain Access on your Mac. Press CMD+SPACE and type Keychain Access to open the program that allows you to manage your certificates. Click on the Certificates category in the bottom left sidebar. Now, import the rootCA.pem using `File > Import Items` from the top MacOS menu bar.
After the import, double click the imported certificate and under the “When using this certificate:” dropdown select “Always Trust”.
Step 3 – Generate Server Files
Create a file named server.csr.cnf. Edit this file and add the following content to it, be sure to change your domain name. This will help you avoid entering all the details manually:
Next, create a v3.ext file with the following content, in order to create a X509 v3 certificate. Notice how we’re specifying subjectAltName here. Also, make sure to change your domain name accordingly.
Next, create the certificate file called server.crt. The .key and .crt files will both be used by the server. server.key is the private part. sever.crt will be shared with browsers and other clients. Remember the password from step one:
Now we must figure out how to get our files in these directories. If your docker container is mapped to your local file system you can simply navigate to these and copy them over and then renaming your files to match these names( overwriting theses files)
Lastly, after overwriting these files with your own you can restart apache and then load up your sit at it’s HTTP address.
In the conf file above you will see that there are no ssl_certificates, but towards the bottom of the output, you will see include /etc/nginx/conf.d/*.conf;. Looking inside this directory we will see: /etc/nginx/conf.d/default.conf;
Now looking at the output of default you will see the location of the default SSL certificates.
An amazing (biased) talk about the rust language by one of the core contributors. Comparing accidents in the rail road industry to computer programming and memory safety.
Getting air-breaks approved in passenger and freight trains took a long time.
Have a listen to the talk. I found it very interesting and I’m sure you will too.
Valuable advice from the “Tech Lead”. A career in software engineering is a long term game, it’s a marathon, not a sprint. Having habits like these, ensure that you’re preserving yourself as you grow in experience and influence.
Healthy Lifestyle, exercise, water and nutrition. Keep a good posture.
Good Sleep routines.
Continual learning. Keep your skills sharp.
Have result-oriented work ethic. Focus on being effective, get work done.
Keep things simple. For yourself and others. Complexity works against you.
Create periods of deep work in your day.
Collaborate with other programmers to save time and effort
When we start a blog, we dream of many readers, followers, and online interactions. Our hope is that writing would open doors for us, you know make us a little more famous than we are currently. In most cases, what follows is the exact opposite. Our blog lies dormant, no articles, nor any comments and no changes since who knows when.
At the beginning of 2018, I started doing a few things very intentionally different, which helped me to do at least one post per month, and some months a little more. These ideas did not only lead to more articles but also, as you’ll discover, improved quality.
1 – Define consistency for yourself
We sometimes place subconscious pressure on ourselves. It affects our ability to think and write. The number one thing you can do for your blog is this: decide for yourself, based on the reality in your life, what the definition of an active blog is.
Defining this for yourself releases creativity and unblocks your thinking. Decide at minimum how many posts you want to put out for the period that you decide on, this has given me a way to maintain accountability. If your reality only allows for one post per quarter, do that! As you grow, so will the frequency. The aim here is not to post all the time, but mainly to get a good rhythm going.
2 – Forget quality
I use to think that the only thing that mattered was quality. Until I heard this story:
A teacher divided his art class into two groups. Each group will work on their year-end project. To the one, he said: “You will be marked based on the quality, bring me one top quality piece. The higher the quality, the better your grade.” and to the other, he said, “You will be marked based on quantity, bring me as many art pieces as you can. The more you bring, the higher your grade”. Both groups went off and came back at the end of the year with their art pieces.
You would think the group who focused on quality performed better, but the results were the opposite. The group who concentrated on quantity had better work than the group solely focused on quality. This deduction from this was simple:practice makes perfect! I believe the same applies to our ability to blog.
From this, I gather that the more you blog, the better your blog posts eventually become.
3 – Gather Ideas and move them to drafts
For a blogger, having nothing to write about is one of the worst situations to find yourself. Having the desire, but no content leaves one feeling paralyzed. To me, blogging is, starting with a basic idea and expanding on it. The wise Solomon said, “there is nothing new under the Sun”. I believe this to be true of ideas as well. There are no new ideas under the sun. There are; new ways to frame them, unique ways to express them and your own life experiences to incorporate into them.
Ideas come and go. Our job is to hold onto the good ones. You can write them down, make a video, graft it into a song. Just don’t leave them solely as thoughts -they will disappear. I’ve had many ideas that slid into forgetfulness. Now I write them in my journal; I email them to myself, I record voice notes. Whatever it takes, I make an effort to hold on to the good ones.
Read more. Reading exposes one to ideas and new ways to express them.
I currently have 20 drafts waiting to be fleshed out or polished. These may not sound like very much, but if I compare them to the time where my blog was a ghost town, I think they are a sign of my strategies working for me.
A strategy that I learned from writing is thinking is to start every blog post with a brain dump. Dump your idea and start creating small sentences as you explore the idea. Do this as a blog post draft so you can save it and have it ready for the next time you work on your drafts. The system of taking Ideas and fleshing them out into mind dumping drafts gives you something meaty to return to when you make time for your blog.
4 – Set out blog time every possible day
How much time should you set aside for blogging? How often? You decide. My method is to set time aside every working morning. I take 10-20 mins and work on my drafts. If you have more time, that’s even better! When you sit down to work on your drafts. Set a timer and stop when it runs out.
This method may mean that a blog post, like this one, takes you a few weeks to write. That doesn’t matter. What matters is that you are thinking as you are writing, which makes you a better thinker and a better writer. The result is a well thought out post every once in a while.
The more time you make per day, the more you can think and write, the more regular your blog posts may be. Remember you are getting better as you do this so 10 mins today and 10 mins 1 year from now is not the same 10 mins. A year from now, you are pouring more experience and knowledge into the 10 mins than what you are capable of today. This system helps you grow your capabilities.
5 – Remove the fear
I currently have about 21 drafts. I don’t work on all of them. I pick one; actually, I force myself to choose the one that’s closest to finish and try to push it forward. Some days, when my motivation is low, I allow myself to pick anyone I like and working on it until the timer runs out. This daily process has helped me with my consistency, which is the secret sauce of an active blog.
Don’t hit publish. I have touched on this before, but the most effective way for me to overcome fear is not to hit publish, but rather to set the date a week from today and then hit the schedule button.
Forget your readers (for now). If you care about who’s reading your posts, it puts even more fear on the table. Remember, we are not referring to a newspaper article that needs to go viral. We are talking about you developing your ability to communicate better by having a more active blog.
Forget the future. Focus on now and what you want to say now. How relevant that is tomorrow is not essential. One day you will write timeless classics, for now, focus on the habit of daily writing.
6 – Keep it short
If you only have a paragraph to share under a given topic, schedule that! If all you have is a sentence write that down. It’s your blog, if you want to come back in a few weeks and, in another post, elaborate on what you said, why not, you own it.
I have tried to use my blog as the primary outlet for social media rants and statuses. It is not as rewarding as my blog does not have many visitors, but I’ve gotten to a point where, growing my ability to communication and gathering skills in this area have become more important than likes, comments, and retweets. So the idea here is to blog first and share that on a post on other services you use. Pump your creativity into one platform, preferably one where the data belongs to you.
I’ve experienced more confidence and a greater desire to blog. My blog is no longer something I dread; instead, I’m excited to write and make time for writing. Let this be your reality too.
gap the alias I created, mapping to git add -p has been one of my most typed commands ever since I changed my workflow.
What this does :
It breaks up your diff into smaller chunks that help you avoid committing things you really don’t want to and helps you know exactly what code is going into the next command. For each chunk, you can choose to stage it or not. All staged changes are those that will be included in your next commit.
To add this command it opens your .bashrc in any editor and add this to it: alias gap="git add -p
It doesn’t matter if you use Git CLI or the app as you get the same things done, but if you really want to get comfortable with it, start using the terminal. It will be painful in the beginning, but you’ll learn more about Git this way.