Open a terminal and enter the following commands. If you already have a working Homebrew installed, you can skip to Step 3

# First, we need to install the basics. You will be asked to enter your password during this process
xcode-select --install 

# After xCode is installed we can install homebrew
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" 

# After succeessful homebrew install it should give you two commands to run 
echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

# Now open a new terminal and run brew doctor
brew doctor

Next, Let's Install Some Apps

My personal list of must-have applications is as follows

• iTerm2 - The best terminal on OSX, period.

• Cheatsheet - Tells you all the hotkeys the current App has just by holding CMD down

• MyCLI MySQL CLI client with Syntax Highlighting and Autocomplete.

• BAT A syntax-highlighted, searchable, mouse-scrollable version of CAT.

• EXA A much better version of LS

• Speedtest-CLI Run a speed test from your CLI.

brew install --cask iterm2
brew install --cask cheatsheet
brew install mas-cli/tap/mas
brew install mycli
brew install bat
brew install exa
brew install speedtest-cli

Let's Install OH-MY-ZSH and Prompt

# First let's install OH My ZSH
sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"

# Install zsh-autosuggestions
git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions

# Install zsh-syntax-highlighting using Oh-my-zsh (Preferred)
git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting

# Now add them to the .zshrc plugins
nano ~/.zshrc

# find the plugins and add both of these
plugins=(zsh-autosuggestions zsh-syntax-highlighting)

# While you are in .zshrc go ahead and add the following near the bottom change username with your username. 

if [ -f "/Users/username/.aliases" ]; then
   source /Users/username/.aliases
fi

# Save the file and Open a new terminal tab to verify your ZSH is working.

Installing Powerlevel10k Theme

Run the following commands to install Powerlevel10k

# gh cli
gh repo clone romkatv/powerlevel10k $ZSH_CUSTOM/themes/powerlevel10k

# git
git clone https://github.com/romkatv/powerlevel10k.git $ZSH_CUSTOM/themes/powerlevel10k

Enabling PowerLevel10k

Then you need to enable it change the value of ZSH_THEME to the following in ~/.zshrc file :

ZSH_THEME="powerlevel10k/powerlevel10k"

Configuring PowerLevel10k

Make sure your terminal font is FiraCode NF.

You can get it at https://fonts.google.com/specimen/Fira+Code install the whole family. Using OSX's FontBook. And set your terminal font to FiraCode NF

And to configure your prompt run the following command

p10k configure

Another good prompt I have used for a long time is Spaceship Prompt which offers a powerful prompt with very configurable options, but lately, I like PowerLevel10k.

Let's add iTerm2's Shell Utilities

iTerm2 has some really useful utilities, so let's add some aliases to make them easier to remember and use.

First, I suggest reading the Iterm2 Shell Utilities

After that, let's add some aliases to our aliases file. I always create a .aliases file in my home directory and include it in my .zshrc I suggest leaving this file open in your editor.

## IMG CAT Alias 
alias icat="imgcat $1"
## LS with Image Previews
alias ils="imgls"
## Copy to clipboard
alias icp="it2copy $1"
## Download from SSH to your Downloads folder
alias idl="it2dl $1"
## Upload Filename through SSH 
alias iup="it2ul $1 -c -z -v -f"

Let's add syntax highlighting to Nano

Now let's spruce up Nano with some syntax highlighting by running the following commands in iTerm2.

# install nano from homebrew
brew install nano nanorc

# update your .nanorc file
echo 'include "/opt/homebrew/share/nanorc/*.nanorc"' >> ~/.nanorc

# Close and re-open your terminal, and you'll have syntax highlighting

Now let's fix up Quicklook real quick and add some features

Let's add Quicklook plugins to make Quicklook more useful. The plugins installed have the following usage.

• qlcolorcode - Preview source code files with syntax highlighting

• qlstephen - Preview plain text files without or with an unknown file extension.

• qlmarkdown - Preview Markdown files

• quicklook-json - Preview JSON files

• qlimagesize - Display image size and resolution

• suspicious-package - Preview the contents of a standard Apple installer package

• apparency - Preview the contents of a macOS app

• quicklookase - Preview Adobe ASE Color Swatches generated with Adobe Photoshop, Adobe Illustrator, Adobe Color CC, Spectrum, COLOURlovers, Prisma, among many others.

• qlvideo -Preview most types of video files, as well as their thumbnails, cover art and metadata

• syntax-highlight - Preview many different source code files

brew install qlcolorcode qlstephen qlmarkdown quicklook-json qlimagesize suspicious-package apparency quicklookase qlvideo

brew install --cask --no-quarantine syntax-highlight

# To get plugins working in Catalina, you will need to remove the quarantine attribute.
#Run this to see the attributes:
xattr -r ~/Library/QuickLook
#And run this to remove the attributes:
xattr -d -r com.apple.quarantine ~/Library/QuickLook

Let's add allow using our thumbprint to sudo

# First open the following file with sudo
sudo /etc/pam.d/sudo
# Add the following line at the very top and save
auth sufficient pam_tid.so
# Finally run this command 
defaults write com.apple.security.authorization ignoreArd -bool TRUE

Fixing iTerm2 to allow using the thumbprint

The default terminal works like a charm, but iTerm2 needs an extra configuration. Go to Prefs -> Advanced -> Allow sessions to survive logging out and back in and set the value to no.

Now logout and back in, and both the default terminal and iTerm should allow using the Thumbprint instead of entering a password when sudoing

Adding more Aliases for EXA and BAT

If you kept your .aliases file open, then add the following aliases. Otherwise, reopen it and add the following aliases.

## Alias to make LS look like this
alias ls="exa --icons -lh"

Now my prompt at the bottom is set up using Power10k, but you can see how it adds icons to the different file types and such.

While you have the .aliases file open, let's add a few more aliases I find useful.

# Copies you public key to your clip board
alias pubkey="more ~/.ssh/id_rsa.pub | pbcopy | echo '=> Public key copied to pasteboard.'"
# Stat Provides a Nice looking CLI Stats 
alias sstat="macchina"
## I use VSC Insider, if you don't use Insiders you dont need this
alias code="code-insiders $1"
## Reload apache
alias rapache="sudo systemctl reload apache2"
# dump autoloader and optimize autoloader
alias cda="composer dumpautoload -o --dev"
# bulk association again if you don't use VSC Insiders just put code
alias -s {md,css,php,js,json,html}=code-insiders

macchina or the alias sstat will render a CLI CPU Stats that looks like this

Using BAT, the CAT replacement

Sometimes, I like CAT to grep it and find specific things. Other times like log files, I want to be able to search and use the mouse to scroll through it, like this. It offers search and mouse scrolling and a lot of other commands.

If you can't figure out how to exit, it's like Vim type:q, but there are other commands you can use with: I suggest reading the docs on BAT.

I have some more tools, but this article is getting pretty long, so stay tuned for the following article, which will expand on this one.

Setting up your unit testing

We'll need to change the composer.json file by adding the following components to move forward.

This will facilitate the required functionality and ensure the smooth execution of subsequent processes.

[
    "require-dev": {
        "phpunit/phpunit": "^9.5",
        "robtimus/multipart": "1.*"
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "scripts": {
        "start": "php -S localhost:8888 -t public",
        "test": "phpunit --configuration phpunit.xml"
    }
]

Next, let's create a phpunit.xml configuration file. This step is essential to ensure that PHPUnit can adequately execute the unit tests in our project.

<?xml version="1.0" encoding="UTF-8"?>
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/9.3/phpunit.xsd" backupGlobals="true" backupStaticAttributes="false" beStrictAboutTestsThatDoNotTestAnything="true" beStrictAboutChangesToGlobalState="false" beStrictAboutOutputDuringTests="true" colors="true" convertErrorsToExceptions="true" convertNoticesToExceptions="true" convertWarningsToExceptions="true" processIsolation="false" stopOnFailure="false" bootstrap="tests/autoload.php">
  <coverage processUncoveredFiles="true">
    <include>
      <directory suffix=".php">src/</directory>
    </include>
  </coverage>
  <testsuites>
    <testsuite name="RESTAPI Test Suite">
        <file>./tests/DummyTest.php</file>
    </testsuite>
  </testsuites>
</phpunit>

After successfully configuring PHPUnit to execute tests in a specific order, we will implement a Dummy Test. This essential step in our testing process will allow us to verify that the PHPUnit configuration has been accurately set up.

By doing so, we can ensure that all subsequent tests are executed in the desired order and that any potential issues with the configuration are promptly detected and resolved. Such a proactive approach will enable us to maintain a high-quality assurance standard in our testing procedures.

Finally, we need to create a tests directory and make a DummyTest.

mkdir tests
touch tests/DummyTest.php

Then paste the following code into your DummyTest

<?php

use PHPUnit\Framework\TestCase;

/**
* Trivial dummy test used to confirm test configuration working.
*/
class DummyTest extends TestCase
{
    /**
    * Trivial dummy test guaranteed to succeed.
    */
    public function testAssertEquals()
    {
        $this->assertEquals('abc', 'abc');
    }
}

We also need to create a new file named autoload.php and paste the following code into it.

<?php

require_once __DIR__.'/../vendor/autoload.php';

Running your first test

Now that all the setup is done, we can install PHPUnit and start our first test.

Run the following commands in your terminal to test that everything is set up and working correctly.

composer update
composer test

You should receive a message saying 1 test was completed.

Building the first real unit test

Now you have PHPUnit set up and working. We can start by creating some tests. Instead of making an application, let's use this tutorial. I found it on a simple Google search that builds an extremely simple REST API.

There's a Route to get all Customers, so to make that work first, I created a TestCase class that extends the PHPUnit Frameworks TestCase.

That way, I could add some Database Commands to the Tests. Since the guide didn't use a Container or Actions for each route, we will have to do some hacky coding to get the tests to work.

First, create a file tests/TestCase.php and paste the following into the file.

<?php
namespace Tests;

use PHPUnit\Framework\TestCase as PHPUNIT_TestCase;
use Slim\Factory\AppFactory;
use Slim\Psr7\Factory\RequestFactory;
use Slim\Psr7\Factory\ResponseFactory;
use Slim\Psr7\Factory\ServerRequestFactory;
use Slim\Psr7\Response;
use Slim\Psr7\Stream;
use App\Models\Db;

Class TestCase extends PHPUNIT_TestCase
{
  public $customer;
  public $lastID;

  public function getCustomer()
  {
    $SQL = "SELECT * FROM customers ORDER BY id DESC LIMIT 1";
    $db = new Db();
    $conn = $db->connect();
    $stmt = $conn->query($SQL);
    $customer = $stmt->fetch(\PDO::FETCH_NAMED);
    $this->customer = (object) $customer;
    $this->lastID = $this->customer->id;
    unset($db);
    return $this->user;
  }

  // ------------------------------------------------------------------------

  public function getTotalCustomers()
  {
    $db = new Db();
    $conn = $db->connect();
    $sql = "SELECT count(id) AS count FROM customers GROUP BY id";
    $stmt = $conn->prepare($sql);
    $customers = $stmt->execute();
    $customers = $stmt->fetchColumn();
    return $customers;
  }

  // ------------------------------------------------------------------------

  public function getLastCustomerID()
  {
    if (!is_int($this->lastID) OR !is_object($this->user)) {
      $this->getCustomer();
    }

    return $this->customer->id;
  }

}

There are better methods of doing this, but this is the best method I found that worked without using an Application Container PHP-DI and without using Actions instead of writing the code directly into the route's anonymous functions.

Finally, let's write a simple test to verify that the GET /customers route tests correctly.

Create a file tests/GetCustomersTest.php and paste the following into it.

<?php

use PHPUnit\Framework\TestCase;
use Slim\Factory\AppFactory;
use Slim\Psr7\Factory\ServerRequestFactory;
use Slim\Psr7\Response;
use Slim\Psr7\Stream;

class GetcustomersTest extends TestCase {

  public function testGetRoute() {

    // Set up the app
    $app = AppFactory::create();

    // Add the route to be tested
    $app->get('/customers-data/all', function (Request $request, Response $response) {
      $sql = "SELECT * FROM customers";

      try {
        $db = new Db();
        $conn = $db->connect();
        $stmt = $conn->query($sql);
        $customers = $stmt->fetchAll(PDO::FETCH_OBJ);
        $db = null;

        $response->getBody()->write(json_encode($customers));
        return $response
        ->withHeader('content-type', 'application/json')
        ->withStatus(200);
      } catch (PDOException $e) {
        $error = array(
          "message" => $e->getMessage()
        );

        $response->getBody()->write(json_encode($error));
        return $response
        ->withHeader('content-type', 'application/json')
        ->withStatus(500);
      }
    });

    // Create a new GET request to the route
    $request = (new ServerRequestFactory())->createServerRequest('GET', '/customers/all');

    // Invoke the application
    $response = $app->handle($request);

    // Assert that the response status code is 200
    $this->assertEquals(200, $response->getStatusCode());

    $existing_customers = $this->getTotalCustomers();

    $customers = (array) json_decode($response->getBody());
    $count     = count($customers);

    $this->assertIsArray($body);
    $this->assertCount($count, $existing_customers, 'The count of the existing customers does not match the count of the customers returned');
  }
}

And to make this test run, edit phpunit.xml and add the test case to the Test Suite by adding this line.

        <file>./tests/GetCustomersTest.php</file>

In summary, this is not the correct way to write tests like these, but the guide I found online didn't use a Container or Actions. And I needed something very similar but couldn't find any helpful information online, so I wrote this article.

Maybe I will write another article showing how to correctly write the REST API with a Container and Actions. If anybody is interested in it, please leave a comment.

A resume should be depending on your work history 1 or 2 pages at most. Leave the story out of the resume, that's what the cover letter is for.

When writing your resume, include your Contact Information, a Short Summary of what you specialize in, your skillset, and languages spoken if you are bilingual, followed by your work history.

Now, in your work history, I personally use bullet points of my daily tasks, followed by my most important contributions to the project.

After your work history, I list any open source projects I have developed or been on the development team of. Again I bullet point what I did at those open source projects.

Finally, the file name of your resume is important also. I always save mine in the format My Name - Position Applying For so say I'm applying for a Full Stack Position, I save my resume as Shawn Crigger - Full Stack Developer.pdf and since a lot of companies want a Microsoft Word Copy, I also save it in word format too.

For work history, I only include jobs related to the job I am applying for, if you are applying to a Full Stack Developer job, don't include the time you worked at the Bagel Factory, or the time you were an HVAC Service Tech.

So, the 3 companies I've ordered from our MyOllie, The Farmers Dog and finally Nom Nom Now.

Each of these products is subscription-based and cost between 70-150 a month, and I'm going to review them in the order of what I consider the best to the worst.

MyOllie

I ordered MyOllie's and was impressed with the packing material, and the shipping speed but more than anything I was impressed mostly with the difference it made in my dog's Fur and Energy Level. The only downside I have to MyOllie's is they only allow ordering 2 months at a time, and with just 25% of your dog's daily calories, it costs $150 for 2 months of food. I kept MyOllie's subscription for about 4 months because in the first week I noticed a spot of fur that she chewed out 3yrs ago had grown back in and her energy level had spiked to puppy-like levels. I hated that due to the money situation I had to cancel my subscription and plan to resubscribe as soon as possible. Also, MyOllie's sent their food in easy to open and easy to serve packages and even provided a very nice container to store your open packages and a serving spoon to correctly portion your servings with the first order. Definitely a plus, I still use both the container and the spoon daily.

Nom Nom Now

Nom Nom Now's dog food also was packed fairly well, almost as good as MyOllie's and the shipping speed wasn't too bad, but it looked like they had just dumped a bunch of canned vegetables and meats into the packages, Nom Nom Now's packaging was almost as good as MyOllie's where you can open 1 package and easily portion out the food without making a giant mess. But the price was more than MyOllie's and my dog didn't like the food as well, I also really haven't noticed the energy boost or the fur quality that I did with MyOllie's

The Farmers Dog

The Farmer's Dog shipping was ridiculously slow, they said it would arrive 7 days before it was even shipped, they included a cardboard takeout box to put your open packages in which I broke the first time I tried using it. Also instead of providing single packages that you could easily open and portion out, they put an entire week's worth of food in 1 package that I had to cut open with scissors just to portion out. My dog did not like it at all and I still have most of the packages in my freezer.

My thoughts on the matter

1. MyOllie's is my favorite but you have to purchase 2 months worth at a time, if you have the freezer space for all that great, it fills ours big time, but I like it the best for my dog, her coat is fuller, she sheds less, and honestly she has grown hair where she has never had hair before or it grew back where she had chewed out a piece of fur on her tail before I got her over 5yrs ago, in less then a month that small patch had grown back!

2. My second choice is NomNomNom their food was easier to work with on the subscription, and you could tell what each piece of food was as it was chopped but not pureed together.

3. Don't bother with farmers dog your getting ripped off.

Summary

Hopefully, this will help someone else who loves their dog and finds the idea of feeding them kibble disgusting. With all the dogs being poisoned by dog food makers lately I find it sickening to even think of feeding food that is not human quality to my dog.

I personally make a base food which is basically cooked chicken/pork or deer meat in rice. I make a week's worth at a time which takes very little effort with an air fryer and a rice cooker. If anybody is interested in the recipe I am using for my base food just comment below and I will make a post about it.

This has a lot of benefits but can also cause a lot of confusion when it comes down to extending the user system, as with extending anything you want the end product to be maintainable but still be powerful and do everything you needed.

Bonfire's default user system is set up with a main user table and a metatable, kinda something like this

User Table

Meta Table

So basically the meta values are stored in a separate table and added to the current_user object as needed with $this->user_model->load_meta, this does a good job for most systems I'll develop but every so often a piece of the user data that isn't important enough to alter the entire system but I needed to be able to display this data like it was in the same table, so instead of 2 tables it would look like

Joined table result

<?php
    /**
     * Loads user and meta data in one query.
     *
     * @param  int  $user_id      user_id or blank for all.
     * @param  bool $show_deleted [show deleted users]
     *
     * @return mixed
     */
    function load_user_meta($user_id = 0, $show_deleted == FALSE)
    {

        $this->db->select('users.*, roles.role_name');

        $this->db->select('m1.meta_value AS first_name');

        // Just keep adding these and alias as you need!
        $this->db->select('m2.meta_value AS last_name');

        //
        $this->db->select('m2.meta_value AS alias');


        $this->db->join('user_meta', 'user_meta.user_id = users.id', 'left');

        // Here is the magic baby!
        $this->db->join('user_meta as m1', "m1.user_id = users.id AND m1.meta_key = 'first_name' ", 'left');


        $this->db->join('user_meta as m2', "m2.user_id = users.id AND m2.meta_key = 'last_name' ", 'left');

        // ! Change me
        $this->db->join('user_meta as m2', "m2.user_id = users.id AND m2.meta_key = 'alias' ", 'left');

        if ($show_deleted === FALSE)
        {
            $this->db->where('users.deleted', 0);
        }

        $this->db->where('users.banned =', 0);
        $this->db->group_by('users.id');

        if (is_numeric($user_id) && $user_id > 0)
        {
            return parent::find($user_id);
        }

        return parent::find_all();
    }
?>

This is a really simple trick I learned not too long ago but makes upgrading very easy later on which with a constantly changing software like Bonfire then Over-riding my Core modules and keeping track of the changes gets hard namely when you build as many websites's as I do in a year. This is a very very very simple trick and you'll probably have a Facepalm Moment for not thinking of this yourself after seeing what it involves!

Basically, modules in Bonfire exist in 2 locations

• bonfire/application/core_modules

• bonfire/modules

  Which the Core Bonfire-related modules live in core_modules and custom modules belong in the modules directory. So the simple trick here is just to copy your core_module into the modules directory like this.

     cp -rfv /bonfire/application/core_modules/users /bonfire/modules

Or you can drag and drop it using Finder or whatever you do to copy a folder to a new location. So now you have 2 copies of the same module, you can actually delete the one your overriding but I prefer to just leave it there myself.

So what have we learned here, the order modules are loaded is first "core_modules", then "modules" so anything in the modules directory will over-ride the "core_modules" directory. Simple enough?

Hope this helps someone. Enjoy and Cheers!

Basically, Bonfire has 2 helper methods called logit one as an application helper and one in the model, these handy helpers make a log entry in CodeIgniter's system log, and use the Console class already included in Bonfire to output any message. The only problem with this is normally when you have an error the page doesn't finish rendering and the stock Bonfire Console library doesn't display any data since it's not rendered. So I just made a few quick changes to the logit methods and added the helper. And now I have better-debugging ability!

First, get the helper and the extension, my friend Marco Monterio has already explained on his blog how to install the extension and the helper, so check his blog out on installing the ChromePhp library to CodeIgniter. Once you have it installed, then you can make these changes and you'll be debugging like a kingpin while your off getting your ChromePhp on, I'll gonna drink that beer you bought me :beer:

Ok, so we only need additions to 2 files and 2 methods, this is easy! Let's start with MY_Model. So open up /bonfire/application/core/MY_Model.php, do a quick search for "logit" and add the code I have below for ChromePhp

<?php
    /**
     * Logs an error to the Console (if loaded) and to the log files.
     *
     * @param string $message The string to write to the logs.
     * @param string $level   The log level, as per CI log_message method.
     *
     * @access protected
     *
     * @return mixed
     */
    protected function logit($message='', $level='debug')
    {
        if (empty($message))
        {
            return FALSE;
        }

        if (class_exists('Console'))
        {
            Console::log($message);
        }

        // Just add from here
        if (class_exists('ChromePhp'))
        {
            if ($level == 'error')
            {
                ChromePhp::error($message);
            }
            else
            {
                ChromePhp::log($message);
            }
        }
        // Just to here.

        log_message($level, $message);

    }//end logit()

    //--------------------------------------------------------------------
?>

Ok so there's the Model changes, now open up bonfire/application/helpers/application_helper.php and once again find the "logit" function

<?php
    /**
     * Logs an error to the Console (if loaded) and to the log files.
     *
     * @param $message string The string to write to the logs.
     * @param $level string The log level, as per CI log_message method.
     *
     * @return void
     */
    function logit($message='', $level='debug')
    {
        if (empty($message))
        {
            return;
        }

        if (class_exists('Console'))
        {
            Console::log($message);
        }

        if (class_exists('ChromePhp'))
        {
            if ($level == 'error')
            {
                ChromePhp::error($message);
            }
            else
            {
                ChromePhp::log($message);
            }
        }

        log_message($level, $message);
    }

    //--------------------------------------------------------------------
?>

And there ya go, now every time logit is called, you can see what the message was inside of your Chrome Web Inspector Console just like you would a JavaScript console.log method would give. Amazing stuff!

Cheers and Free beers again!

The first step is to remove the screen protector from the case.

Step 2 - Removing The Front Bezel

This was the hardest part of the whole process, First step is to remove the memory door and memory. After that remove all Torx Screws out of the way. There are 8 short T8 Torx Screws along the top and side of the bezel. Then there are 4 long Torx screws along the bottom.

After removing the Torx screws, Work your way around the bottom of the iMac and try to loosen the stand, there's a groove on the bottom I used a pocket knife to get it started then lifted carefully lifted up from there.

Step 3 - Disconnecting the iSight Camera

![Finish Removing the Front Bezel(https://cdn.hashnode.com/res/hashnode/image/upload/v1617569596022/K4rCw26RI.jpeg)

Step 4 - Removing the Screen

Ok, now there are 8 Torx T8 or T9 screws holding the LCD Display to the Case. If you are very careful, You can remove these screws and Tilt the Display out of the way so you do not have to unhook the wires.

Step 5 - Replacing the Hard Drive

Ok After all that finally found the hard drive, there is a Black Handle on one side of it, I used my leg to hold the mac in place and pulled the handle to me so that the hard drive pulled right out. Personally, my Temp Sensor would not stick back on so I used electric tape to tape it back on. Once you have finished this step, Reverse the rest of the steps and make sure you Clean both the LCD Display and the Inside and Outside of the Screen Protector or you will have annoying fingerprints on your display.

One other thing makes sure all your wires are routed properly and not blocking any screw holes, When I went to reinstall one of the wires in the bottom would not fit the screw hold so I had to remove everything to figure out why, if I would have forced it to go in, It would have broken something I'm sure.

Step 6 - Reverse the process

After replacing the hard drive just reverse the process to put everything back together. One important thing I forgot to mention is to do a Drive clone before you change the drives out. I forgot to do that and had to boot from my old drive as an external drive.