Good technical writing should be easy to read. The reader should be able to switch in and out of the written instructions without getting lost. It should be engaging — the reader should want to see the instructions through to the end. Even better is if the reader learns something new and valuable about the subject.
One of software development’s most significant hurdles is easy to access to relevant technical documentation. Documentation-as-Code (or Docs-as-Code) offers a method to overcome this and unite the creators and consumers.
Sometimes following an OS update, you may be faced with the following error:xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools),missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun What is xcrun?xcrun is a helper tool for Xcode. It allows scripts and other applications that leverage Xcode, such as git, to run from any location without knowing where Xcode is installed or even what version […]
The default shell for MacOsx, starting with Catalina OS, is no longer .bash but is now .zsh. While you can easily change back to bash if you prefer, zsh does have some updated features that make it a solid shell. It also has a few quirks. One of the quirks is how it deals with autocomplete […]