Developers: You are NOT special…

Software development is still a pretty immature industry. It’s very cheap to get started and essentially anyone can enter the arena. Obviously immature processes are not scalable to large endeavors, nor will hold up over time or personal changes. In particular, naming or code conventions are very important – and frequently hated by developers.

I had a conversation with a design engineer working at a domestic automobile manufacturer regarding standards. I asked of the impact to the company if designers could create blueprints/drawings by which ever manner they wanted. For example, the dimension arrows could be open or closed, wide or narrow; title blocks could be anywhere on the page; and so on. His response: “That would shut the company down immediately.”

In other words, having standard communication formats for blueprints is very valuable for the company. Mankind has been using blueprints to communicate for probably a couple hundred years now. In fact, in high school drafting class, we were instructed exactly how to create blueprints. The value of the blueprint is communication of the content.

With software development, many consider ourselves as “artisans”. Our style is best and the rest of humanity will come around. In the unlikely even this occurs, please be aware that even companies such as Microsoft are updating their tools (Visual Studio 2017) to enforce code formatting.

Notice that this is done by the IDE or source control system. It’s not a document you have to memorize. Also, each team can customize it for themselves and grow as a team. Success will be when one cannot discern who wrote what, rather we simply focus on material content.

Developers: You are NOT special…

Adding PGP (GPG) to Mac OSX

Recently it was necessary to add PGP technology to my work laptop. So then, it became imperative that the same be implemented on my personal MacBook Pro. This turned out to be pretty easy as I seemed to have found some great web pages that walked me through the steps.

The general recommendation was to have GPG Suite installed. It’s easy enough to download, but it had a SHA256 checksum hash to validate the download. The version of OpenSSL that Apple provides is not capable of SHA256, so that meant upgrading OpenSSL.

It turns out that OpenSSL is distributed as source, not a compiled binary. Compiling open source can be an adventure, so I pondered a bit to make sure I was willing to spend the time to get it working. It turns out, the pages I found worked perfectly – just follow the steps! The only hassle was adding my non-admin account to the sudo list. Not a big problem, just a small hiccup.

From there, installing GPG Suite was a breeze and testing with other accounts confirmed it’s working just fine.

Here are the pages you’ll need:

http://mac-dev-env.patrickbougie.com/openssl/ – takes > 1/2 hr to build. Follow each step & all will be well
https://gpgtools.org will get the installer
Adding PGP (GPG) to Mac OSX