This article was originally published on LinkedIn — thought I’d share it here.
Delivering digital experiences on mobile devices is no small feat. It’s the discipline of not only removing obstacles from the path to quickly producing software, but also increasing the pace down that path. It considers the 3 pillars of DevOps: flow, feedback, and continuous improvement.
Continuous Integration — the term seems self-explanatory. Integration that happens all the time. In the software development context, it’s the combining of application source code changes into the main or master version of the code base. This indicates that some form of code versioning must be used, and the main version of the source code is often referred to as the mainline, trunk, or the master branch. Continuous integration (CI) is focused on ensuring code changes are frequently integrated with the mainline and ready for deployment.
Beyond the realm of the programmer hobbyist lies customer focused software development, and scale — serving more users. In this new realm, questions arise like: How quickly and easily can you share an app demo with stakeholders? How quickly and easily can you resolve production issues by releasing a fix to production? Which begs the next question, how long does it take to release the app into production after making only a one-line code change?
We often try to answer these questions long after we write our application. This is way too late for the serious software product developer. From…
There are many names and descriptions to the organizations and teams companies use to improve software development speed and stability:
These types of organizations can range in size, housing many domains such as developer tools, build infrastructure, mobile infrastructure, cloud engineering, platform engineering, internal tools and developer happiness. And usually there is a team dedicated to each domain.
Bash is a shell from the GNU project, and was originally created for the GNU operating system. Bash stands for ‘Bourne-Again Shell’, a reference to Stephen Bourne’s Bourne shell (sh) that he created as a new Unix shell when he was at Bell Labs.
There are several different shells, and as per the Man documentation pages:
Bash also incorporates useful features from the Korn and C shells (ksh and csh).
I remember years back being fresh out of coding boot camp and sitting across from a senior software developer in an interview. It was for an unknown startup which today I still don’t remember the name. However, what still stands out to this day is the question I was asked: do you know what continuous integration is? I was clueless, and I openly admitted to being so. And I vaguely remember the developer’s brief explanation of continuous integration (CI).
Needless to say I didn’t land the job. Several months later…
Delivering digital experiences on mobile devices is no small feat. It’s the discipline of not only removing obstacles from the path that leads to quickly producing software, but also increasing the pace down that path. It considers the 3 pillars of DevOps: flow, feedback, and continuous improvement. By identifying the bottle necks and problem areas in the workflow used to develop a software product, and addressing these problems, we can boost productivity. It’s by our feedback systems that we can pin point problems and apply fixes and improvements. …