An Introduction to Source Code

Every program you use is built from a string of instructions known as source code, which tell the software how to function. Referred to as a “technical blueprint“, there are two distinct forms programmers need to be aware of when designing a program: open source software, and closed source software.

Open source software is publicly available to be viewed, used, shared, and modified by users and organisations at little-to-no cost (e.g. Android, WordPress). Closed source software, on the other hand, is “proprietary software distributed under a licensing agreement to authorised users with private modification, copying, and republishing restrictions” (e.g. Apple, Skype). Most businesses have a closed source software arrangement so as to “maintain control over their brand and the user experience offered to customers“, although that’s not to say it is superior to its alternative.

Although open source software is often considered ‘free’, there are many costs involved beyond its initial acquisition, such as implementation, technical support, training, integration, and additional ad-ons. Alternatively, closed source software involves a hefty base charge, plus annual licensing fees. There are also significant differences in the innovative ability and customisation of either form, with open source software allowing users the freedom and flexibility to alter the system without restriction, while closed source software is fixed and, rather, “ensures the security and reliability of proprietary software that is fully tested and offered to all users“.

With so many advantages and disadvantages of each form, the most appropriate choice for your business will rely entirely on the business’s individual circumstances, resources, and experience, and so it is important to evaluate your priorities prior to committing to either arrangement. For a more comprehensive comparison of the two systems, take a look at API2Cart’s article here.

14 thoughts on “An Introduction to Source Code

  1. Hi there Taylor! Your attention to detail with your hyperlinking and structure of the post is really awesome and helpful. I would love to see you make more memes, super clever!
    I thought this list of open source applications https://www.techradar.com/best/best-open-source-software might be helpful for you to look at as you only mention a couple but you seem to know your way around the terms heaps well 🙂
    I think our two posts contrast nicely, as you took a more business minded approach where I went for a self-reflection based narrative for responding to this weeks material! https://bcmkelsea.wordpress.com/2020/05/24/w10-algorithmic-control/
    Great work this week!

    Liked by 1 person

    1. Hi Kelsea, thanks so much for your feedback! I’m really glad you were able to take something away from my blog and enjoyed my remediation. I’ll be sure to give your blog post a read, too – It’s always interesting to see the different ways people approach the same topic. While you’re at it, I’d love it if you could check out my Facebook page at https://www.facebook.com/Taylor-Sumelj-1329749160514049 and give it a like. Thanks again!

      Like

  2. Hi Taylor, I learned a fair bit from your post that I probably should’ve already known haha. Overall I thought it was really informative. We took a similar approach with our posts although yours is more thorough and well explained while I went off on a random tangent. Was really pleasant to read, Good Job!

    Liked by 1 person

  3. Hi Taylor, I really liked your blog post. It was both informative and captivating to read. I based my blog post very similar to yours focusing on open and closed source software. Your remediation is also really cool. Below is an article I found comparing open and closed sourced software. It is an informative read and helps to understand the concept a little further.
    https://www.coredna.com/blogs/comparing-open-closed-source-software

    Keep up the great work 🙂

    Liked by 1 person

    1. Hi Isabella, thanks so much for your feedback! I’m really glad you were able to take something away from my blog and enjoyed my remediation! If you link your blog post below, I’ll give it a read, too. It’s always interesting to see the different ways people approach the same topic. While you’re at it, I’d love it if you could check out my Facebook page at https://www.facebook.com/Taylor-Sumelj-1329749160514049 and give it a like. Thanks again!

      Like

  4. Hi Taylor, this is a great explanation of source code! I found your writing really easy to understand yet still very in-depth which helped me grasp a better understanding on the different uses of open and closed sources. In particular, I like that you mentioned that neither source code is superior, and how choosing a source code depends on the values of the business. Overall, this was an excellent read!

    Liked by 1 person

  5. One of the most detailed posts I’ve seen this semester. When it comes to tech speak I struggle a lot because a lot of the terminology tends to go completely over my head but this was a great way to clearly explain what source code is and what it entails. Thank you!

    Liked by 1 person

Leave a comment