DEV Community: Rami Massoud

Engineer's Guide To Windows: Ruby on Rails

Rami Massoud — Tue, 23 Feb 2021 18:00:00 +0000

As I've mentioned, I primarily work with Ruby on Rails applications. So it's fairly important that I can work with one on my sweet new WSL setup.

Mixed Bag of Prerequisites

Unlike a more standard Debian or a fresh macOS install, a clean WSL Debian install has a very minimal set of tools installed. So before getting into anything strictly Ruby or Rails related, I need to install some common tools I end up reaching for to accomplish all sorts of work, including getting a Rails dev environment setup.

sudo apt install ssh git man-db curl gnupg2 wget keychain

Nothing here should be too controversial to anyone who has worked in Unix-like systems before.

I was a little surprised that I needed to install the man database, but sure 🤷‍♂️. Installing ssh, git, curl and wget are reasonable basics to have on a Linux system and are required to install Ruby and Node through version managers. I use gnupg2 to sign my commits to get that sweet verified badge in GitHub.

Installing keychain is new for me. It's a handy tool to manage your ssh and GPG keys. Once installed, add

eval `keychain --eval --agents ssh id_rsa`

to .bashrc/.bash_profile, then enjoy not having to type a passphrase every time you run a GPG or ssh command!

The Journey to Install Ruby

Photo by Matt Howard on Unsplash with some help from Matz

It's possible to grab Ruby (or Node, for that matter) versions from the Debian package manager, but I don't believe that's the most common or recommended way to install them. I always end up needing multiple or unavailable versions for one reason or another, so I lean on rbenv to manage installing and switching between those versions.

Use rbenv to pick a Ruby version for your application and guarantee that your development environment matches production. Put rbenv to work with Bundler for painless Ruby upgrades and bulletproof deployments.

I chose to install rbenv with the rbenv-installer script (after reading the source over).

curl -fsSL https://github.com/rbenv/rbenv-installer/raw/master/bin/rbenv-installer | bash

Now rbenv and ruby-build should be installed; just don't forget to run rbenv init and follow the instructions to have the shell recognize and find Ruby binaries.

Theoretically, any version of Ruby should be installable at this point!

$ rbenv install 2.7.2
Downloading ruby-2.7.2.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.2.tar.bz2
Installing ruby-2.7.2...

BUILD FAILED (Debian 10 using ruby-build 20201225-2-g5de6d5f)

Inspect or clean up the working tree at /tmp/ruby-build.20201230170140.1599.9kPeZh
Results logged to /tmp/ruby-build.20201230170140.1599.log

Last 10 log lines:
checking for ruby... false
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/tmp/ruby-build.20201230170140.1599.9kPeZh/ruby-2.7.2':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details

Well, that's not good 🙈.

After seeing that error message, I hoped that installing GCC would be enough, but of course, there were a bunch of libraries missing too! I'll spare writing out the half dozen tries it took me to get all of the necessary libraries installed and get to the point.

sudo apt install gcc libc-dev make libssl-dev zlib1g-dev libreadline-dev

Those are what's needed just for Ruby. For my Rails app, I also needed to install libpq-dev to compile the Postgres gem, and g++ for the sassc gem.

Installing Node

Like with Ruby, it's good to have a version manager for all your Node needs. My preferred version manager for Node is nodenv, which, nicely enough, is the Node version of rbenv. 😎

It even has a similar installation process.

curl -fsSL https://raw.githubusercontent.com/nodenv/nodenv-installer/master/bin/nodenv-installer | bash

Again, just like with rbenv, follow the post-install instructions to ensure the shell recognizes and finds the binaries. Hopefully, as for me, installing Node will be much less eventful than Ruby was.

Rails Prerequisites

There is no reasonable way I know to cover the possible variations of Rails setups here. For clarity and sanity's sake, I'll limit this guide to generating a brand new app. Even more narrowly, this is the command I want to work:

rails new mycoolapp --skip-turbolinks --skip-action-cable --webpack=stimulus --database=postgresql

Yarn

As long as Node was successfully installed, installing Yarn is a one-liner.

npm install --global yarn

Keep in mind that Yarn will be installed in the current Node version, so verify it's the expected one with nodenv version.

Postgresql

Postgres is my go-to database for any project. As of this writing, the primary version available in Apt is Postgres 11, but pulling from the Debian testing source will get Postgres 13 for bleeding-edge database fun. Thankfully, installing is straightforward. As I mentioned earlier, make sure libpq-dev has been installed at some point, so the pg gem will be able to compile.

sudo apt install postgresql libpq-dev

It will not likely be a revelation to those who have experience with later versions of Postgres or who have only worked with it through Homebrew on a Mac, but I ran into some additional steps I needed to run through to connect to the database. After Postgres installed, I didn't have a way to create users, databases, or even access it with psql. It turns out I had to bootstrap myself a user through the postgres (sometimes postgresql) system user.

sudo -u postgres createuser --createdb --pwprompt WHATEVERUSERNAMEYOUWANT

I prefer to always create a Postgres role that matches my Linux username since that's the default if you don't specify a role name when using psql.

There is another way to work with databases locally, though it might be a little iffy on security. If this is strictly for development purposes, I don't think it's much of an issue. When creating users, leave off --pwprompt and change the Postgres config to instead trust any local connections. This can be done by updating /etc/postgresql/11/main/pg_hba.conf to have local and host use trust for authentication.

# "local" is for Unix domain socket connections only
local   all             all                                     trust
# IPv4 local connections:
host    all             all             127.0.0.1/32            trust

After the configuration change, any user or app's local connections will connect with only a username, no password required.

Bundler

What would working in Ruby be without Bundler? As long as Ruby is installed, this is as easy as

gem install bundler

Rails Itself 🤔

For completeness sake, installing the Rails gem should be the last piece of the puzzle to run that command I mentioned at the start of this section. Grab it just like Bundler

gem install rails

Enjoy Building A New Application

$ rails new mycoolapp --skip-turbolinks --skip-action-cable --webpack=stimulus --database=postgresql
      create  README.md
      create  Rakefile
      create  .ruby-version
      create  config.ru
      create  .gitignore
      create  .gitattributes
      create  Gemfile
         run  git init from "."
Initialized empty Git repository in /home/username/mycoolapp/.git/
      create  package.json
      create  app
         run  bundle install

Bundle complete! 16 Gemfile dependencies, 72 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
         run  bundle binstubs bundler
       rails  webpacker:install
      create  config/webpacker.yml
Copying webpack core config
Copying postcss.config.js to app root directory
Copying babel.config.js to app root directory
Copying .browserslistrc to app root directory
The JavaScript app source directory already exists
  Copying binstubs
Installing all JavaScript dependencies [5.2.1]
         run  yarn add @rails/webpacker@5.2.1 from "."
yarn add v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 594 new dependencies.
Done in 11.39s.
Installing dev server for live reloading
         run  yarn add --dev webpack-dev-server from "."
yarn add v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 102 new dependencies.
Done in 4.35s.
Webpacker successfully installed 🎉 🍰
       rails  webpacker:install:stimulus
      append  app/javascript/packs/application.js
Creating controllers directory
Installing all Stimulus dependencies
         run  yarn add stimulus from "."
yarn add v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 5 new dependencies.
Done in 4.43s.
Webpacker now supports Stimulus.js 🎉

A compact version of the output, but now generating a new Rails application should succeed! Maybe take a break, grab some water and a snack, then get to work on building a great side project.

Photo by Mike Enerio on Unsplash

Engineer's Guide To Windows: WSL

Rami Massoud — Mon, 08 Feb 2021 05:00:00 +0000

These days I mostly write Ruby, and from what I hear, it’s a nightmare on Windows proper.

Avdi Grimm

@avdi

"Why is everyone going to Node instead of Ruby??"

50% of developers primarily use Windows. (insights.stackoverflow.com/survey/2018/#t…)

Node works well on Linux, MacOS, and Windows.
Ruby works well on Linux, MacOS, and is (still) a fucking nightmare on Windows.

Do the math.

15:08 PM - 24 Mar 2019

Sam Saffron

@samsaffron

@avdi Ruby on pure Windows is a dead end for Rails and pointless investment of time imo, improving Ruby on "Windows Subsystem for Linux" should be a priority though, and bootsnap makes it bearable. meta.discourse.org/t/installation…

03:34 AM - 25 Mar 2019

Thanks to the Windows Subsystem for Linux (WSL), enough of the headaches have been smoothed out for me to give this a shot.

The Windows Subsystem for Linux lets developers run a GNU/Linux environment -- including most command-line tools, utilities, and applications -- directly on Windows, unmodified, without the overhead of a traditional virtual machine or dual boot setup.

Enabling WSL

Starting from a clean slate, it's time to start the Linux adventure.

I followed along with a helpful Microsoft article to get up and running. First, open up an admin PowerShell window, and enable the WSL feature with

dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

It’s important to end up with WSL 2 because of all of the performance improvements, so make sure to grab all of the Windows updates to get at least to version 1903 with build 18362. Then enable the Virtual Machine platform with

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Make sure to restart the computer! Something I missed at first. Once that's done, download and run the Linux kernel update package

https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msi

Now pop back into an admin Powershell to set the default WSL version to 2 with

wsl --set-default-version 2

Finally, head over to the Microsoft Store to find your favorite Linux distribution, Debian, and download/install that.

Virtualization Issues

Even if WSL avoids “the overhead of a traditional virtual machine,” it still takes advantage of virtualization tech. Initially, when I tried to open up the Debian app, I hit Error 0x80370102.

After some digging, I found that this meant some virtualization features on my system weren’t enabled. I have a newer Ryzen build and found a BIOS setting for SVM (AMD Secure Virtual Machine) Mode, disabled. Once I flipped that on and booted back into Windows, I was back in business.

Wrapping Up

Once successfully installed, create a primary user with a secure password, update with the system package manager, and hang tight for the next time where I’ll be getting my development environment ready for my day-to-day work!

Bonus: Windows Terminal

Microsoft has been doing a great job with their tooling for developers, and the Windows Terminal app is no exception! Grab it from the Microsoft Store, and it can be a great alternative to the more basic terminal experience you get from the WSL apps themselves.

Windows Terminal is super customizable, and all from editing an easy-to-read JSON file. Check out the documentation for the various options and even some cool custom color schemes.

Instance Doubles: Rspec Anti-Pattern?

Rami Massoud — Mon, 01 Feb 2021 05:00:00 +0000

Over twelve years in software, and I still find it incredibly difficult to write good tests for my code. Almost as difficult as getting a group of programmers to agree on what's a good test.

More than half of my career has now been working in Rails applications, and I’ve often seen specs using instance doubles as a tool to avoid the database. While I admire avoiding the database when possible in tests, the drive seems to lead to situations where the specs

Don’t actually test anything other than if you stubbed out methods properly
Are so brittle that any change to the structure of the code under test breaks them
Are so brittle that they are broken by changes to the structure of code that shouldn’t even be related 😱

It’s come to the point where if I run into a file that heavily relies on instance doubles, it’s almost a guarantee that I'll have to rewrite the specs from scratch.

I don’t have enough experience to say definitively, but I have a strong suspicion that the real issue in these cases is code that is too tightly coupled and/or some leaky abstractions are in use. In a newer codebase, you might be able to untangle these issues on the code side. Yet, in a long-lived project, you’re likely stuck making the compromises in your specs unless you want a 10,000 line PR untangling code that spans 5 years and 10 different pairs of hands, all with different ideas on How It Should Be™.

When I say compromises, I specifically mean test setup code. You might have to build up tons of entities/records to test the logic of a block of code successfully, but this is by far the lesser evil. The best way to explain is with a code example.

To start, here are a few Rails models, along with the specs for an order method. One spec in the style I suspect to be an anti-pattern, and another using my preferred way.

class PaymentMethod < ApplicationRecord
  belongs_to :account
end

class Account < ApplicationRecord
  has_many :payment_methods
  has_one :primary_payment_method, -> { where(is_primary: true) }, class_name: 'PaymentMethod'
end

class Product < ApplicationRecord
end

class OrderProduct < ApplicationRecord
  belongs_to :product
  belongs_to :order
end

class Order < ApplicationRecord
    belongs_to :account
  has_many :order_products
  has_many :products, through: :order_products

  def chargeable?
    return false unless products.size.positive?
    return false unless account.primary_payment_method.present?

    true
  end
end

RSpec.describe Order, type: :model do
  describe 'bad? #chargeable?' do
    subject { order.chargeable? }

    let(:order) { Order.new }
    let(:account) { instance_double(Account, primary_payment_method: double) }
    let(:product) { instance_double(Product) }

    before do
      allow(order).to receive(:account) { account }
      allow(order).to receive(:products) { [product] }
    end

    it { is_expected.to eq(true) }
  end

  describe 'good? #chargeable?' do
    subject { order.chargeable? }

    let(:order) { build_stubbed(:order, user: account) }
    let(:account) { build_stubbed(:account) }
    let(:product) { create(:product) }

    let!(:order_product) { create(:order_product, order: order, product: product) }
    let!(:payment_method) { create(:payment_method, account: account, is_primary: true) }

    it { is_expected.to eq(true) }
  end
end

If there is a #chargeable?, there is likely going to be a #charge! too. For the sake of not confusing the issue, I'll only show a simple version that won't actually hit a payment provider.

class Order < ApplicationRecord
  def charge!
    return false unless chargeable?

    # Call payment SDK
    true
  end
end

RSpec.describe Order, type: :model do
  describe 'bad? #charge!' do
    subject { order.charge! }

    let(:order) { Order.new }

    let(:account) { instance_double(Account, primary_payment_method: double) }
    let(:product) { instance_double(Product) }

    before do
      allow(order).to receive(:account) { account }
      allow(order).to receive(:products) { [product] }
    end

    it { is_expected.to eq(true) }
  end

  describe 'good? #charge!' do
    subject { order.charge! }

    let(:order) { create(:order, account: account) }
    let(:account) { create(:account) }
    let(:product) { create(:product) }

    let!(:order_product) { create(:order_product, order: order, product: product) }
    let!(:payment_method) { create(:payment_method, account: account, is_primary: true) }

    it { is_expected.to eq(true) }
  end
end

All of the specs for this hypothetical charging workflow pass! 🎉For now. 😈

Here is where things get tricky. What happens if a check needs to be added for if the primary_payment_method is expired? I think ideally, the only spec update required would be for #chargeable? with #charge! being left alone. If the default for #expired? is false, bad? #chargeable? is the only spec that has to change. But both should change to cover the new logic branch.

class PaymentMethod < ApplicationRecord
  def expired?
    false
  end
end

class Order < ApplicationRecord
  def chargeable?
    return false unless products.size.positive?
    return false unless account.primary_payment_method.present?
    return false if account.primary_payment_method.expired?

    true
  end
end

RSpec.describe Order, type: :model do
  describe 'bad? #chargeable?' do
    subject { order.chargeable? }

    let(:order) { Order.new }

    let(:account) { instance_double(Account, primary_payment_method: payment_method) }
    let(:product) { instance_double(Product) }
    let(:payment_method) { instance_double(PaymentMethod, expired?: false) }

    before do
      allow(order).to receive(:account) { account }
      allow(order).to receive(:products) { [product] }
    end

    it { is_expected.to eq(true) }
  end
end

Unfortunately, re-running the specs results in an error on bad? #charge!.

$ bundle exec rspec spec/models/order_spec.rb
..F.

Failures:

  1) Order bad? #charge!
     Failure/Error: return false if account.primary_payment_method.expired?
       # received unexpected message :expired? with (no args)
     # ./app/models/order.rb:10:in `chargeable?'
     # ./app/models/order.rb:16:in `charge!'
     # ./spec/models/order_spec.rb:35:in `block (3 levels) in '
     # ./spec/models/order_spec.rb:47:in `block (3 levels) in '

Finished in 0.08436 seconds (files took 0.99 seconds to load)
4 examples, 1 failure

Failed examples:

rspec ./spec/models/order_spec.rb:47 # Order bad? #charge!

The #expired? method has not been defined on the returned double, so the spec "erroneously" fails even though the code that's supposed to be under test hasn't changed. On the other hand, the spec for good? #charge! ends up passing since the default for the expired state is false.

This is a brief, semi-synthetic example of the issues I end up running into with the instance_double testing style all the time. This specific example could be easily adjusted to be less brittle, but as more time, hands, and complexity are added, things quickly spin out of control. There are few things worse than when I'm trying to make a small, targeted change and end up having to chase down why dozens of mostly unrelated specs are failing.

So that's my case against using instance doubles! Feel free to leave a comment or @ me on Twitter with feedback, especially if you've found a better way to manage complex specs 🙏

Engineer's Guide To Windows: Start Fresh

Rami Massoud — Mon, 18 Jan 2021 05:00:00 +0000

After constant disappointments with Apple’s Macbook Paperweights, I decided to switch back to Windows machines, especially once I learned about the Windows Subsystem for Linux (WSL).

SwiftOnSecurity

@swiftonsecurity

Microsoft brought Linux to the desktop twitter.com/sinclairinat0r…

15:46 PM - 19 May 2020

Jeremy Sinclair #WIMVP @sinclairinat0r
#WSL2 and GUI support <3 <3 #MSBuild https://t.co/NDeuqKQLic

This is the first of a series of posts covering all of the things I do to prep a machine for my dev and gaming needs.

Managing Vendor Cruft

DecentSecurity has a great guide for the very initial setup of a new machine. Unless you’ve built your own system, you’re going to have a bunch of vendor cruft installed on your new machine, and the guide has you do a fresh Windows install first thing to clear all of that out.

Once you have a clean Windows install, you need to clean up the Microsoft cruft. 😒

Managing Microsoft Cruft

Inspired by Win10-Initial-Setup-Script, I run the following commands in an admin PowerShell, which can be reached by right-clicking on the start button and clicking. Windows PowerShell (Admin)

Disable Cortana

If (!(Test-Path "HKCU:\Software\Microsoft\Personalization\Settings")) {
    New-Item -Path "HKCU:\Software\Microsoft\Personalization\Settings" -Force | Out-Null
}
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Personalization\Settings" -Name "AcceptedPrivacyPolicy" -Type DWord -Value 0
If (!(Test-Path "HKCU:\Software\Microsoft\InputPersonalization\TrainedDataStore")) {
    New-Item -Path "HKCU:\Software\Microsoft\InputPersonalization\TrainedDataStore" -Force | Out-Null
}
Set-ItemProperty -Path "HKCU:\Software\Microsoft\InputPersonalization" -Name "RestrictImplicitTextCollection" -Type DWord -Value 1
Set-ItemProperty -Path "HKCU:\Software\Microsoft\InputPersonalization" -Name "RestrictImplicitInkCollection" -Type DWord -Value 1
Set-ItemProperty -Path "HKCU:\Software\Microsoft\InputPersonalization\TrainedDataStore" -Name "HarvestContacts" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced" -Name "ShowCortanaButton" -Type DWord -Value 0
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\PolicyManager\default\Experience\AllowCortana" -Name "Value" -Type DWord -Value 0
If (!(Test-Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows Search")) {
    New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows Search" -Force | Out-Null
}
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows Search" -Name "AllowCortana" -Type DWord -Value 0
If (!(Test-Path "HKLM:\SOFTWARE\Policies\Microsoft\InputPersonalization")) {
    New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\InputPersonalization" -Force | Out-Null
}
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\InputPersonalization" -Name "AllowInputPersonalization" -Type DWord -Value 0
Get-AppxPackage "Microsoft.549981C3F5F10" | Remove-AppxPackage

Disable Web Search in Start Menu

Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Search" -Name "BingSearchEnabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Search" -Name "CortanaConsent" -Type DWord -Value 0
If (!(Test-Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows Search")) {
    New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows Search" -Force | Out-Null
}
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows Search" -Name "DisableWebSearch" -Type DWord -Value 1

Disable Application Suggestions & Automatic Installation

Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "ContentDeliveryAllowed" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "OemPreInstalledAppsEnabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "PreInstalledAppsEnabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "PreInstalledAppsEverEnabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SilentInstalledAppsEnabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-310093Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-314559Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-338387Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-338388Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-338389Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-338393Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-353694Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-353696Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SubscribedContent-353698Enabled" -Type DWord -Value 0
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" -Name "SystemPaneSuggestionsEnabled" -Type DWord -Value 0
If (!(Test-Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\UserProfileEngagement")) {
    New-Item -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\UserProfileEngagement" -Force | Out-Null
}
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\UserProfileEngagement" -Name "ScoobeSystemSettingEnabled" -Type DWord -Value 0
If (!(Test-Path "HKLM:\SOFTWARE\Policies\Microsoft\WindowsInkWorkspace")) {
    New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\WindowsInkWorkspace" -Force | Out-Null
}
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\WindowsInkWorkspace" -Name "AllowSuggestedAppsInWindowsInkWorkspace" -Type DWord -Value 0
# Empty placeholder tile collection in registry cache and restart Start Menu process to reload the cache
If ([System.Environment]::OSVersion.Version.Build -ge 17134) {
    $key = Get-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\Cache\DefaultAccount\*windows.data.placeholdertilecollection\Current"
    Set-ItemProperty -Path $key.PSPath -Name "Data" -Type Binary -Value $key.Data[0..15]
    Stop-Process -Name "ShellExperienceHost" -Force -ErrorAction SilentlyContinue
}

Uninstall OneDrive

Stop-Process -Name "OneDrive" -Force -ErrorAction SilentlyContinue
Start-Sleep -s 2
$onedrive = "$env:SYSTEMROOT\SysWOW64\OneDriveSetup.exe"
If (!(Test-Path $onedrive)) {
    $onedrive = "$env:SYSTEMROOT\System32\OneDriveSetup.exe"
}
Start-Process $onedrive "/uninstall" -NoNewWindow -Wait
Start-Sleep -s 2
Stop-Process -Name "explorer" -Force -ErrorAction SilentlyContinue
Start-Sleep -s 2
If ((Get-ChildItem -Path "$env:USERPROFILE\OneDrive" -ErrorAction SilentlyContinue | Measure-Object).Count -eq 0) {
    Remove-Item -Path "$env:USERPROFILE\OneDrive" -Force -Recurse -ErrorAction SilentlyContinue
}
Remove-Item -Path "$env:LOCALAPPDATA\Microsoft\OneDrive" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item -Path "$env:PROGRAMDATA\Microsoft OneDrive" -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item -Path "$env:SYSTEMDRIVE\OneDriveTemp" -Force -Recurse -ErrorAction SilentlyContinue
If (!(Test-Path "HKCR:")) {
    New-PSDrive -Name "HKCR" -PSProvider "Registry" -Root "HKEY_CLASSES_ROOT" | Out-Null
}
Remove-Item -Path "HKCR:\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" -Recurse -ErrorAction SilentlyContinue
Remove-Item -Path "HKCR:\Wow6432Node\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" -Recurse -ErrorAction SilentlyContinue

Uninstall Default Microsoft Applications

Get-AppxPackage "Microsoft.3DBuilder" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingFinance" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingFoodAndDrink" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingHealthAndFitness" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingMaps" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingNews" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingSports" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingTranslator" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingTravel" | Remove-AppxPackage
Get-AppxPackage "Microsoft.BingWeather" | Remove-AppxPackage
Get-AppxPackage "Microsoft.ConnectivityStore" | Remove-AppxPackage
Get-AppxPackage "Microsoft.FreshPaint" | Remove-AppxPackage
Get-AppxPackage "Microsoft.GetHelp" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Getstarted" | Remove-AppxPackage
Get-AppxPackage "Microsoft.HelpAndTips" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Media.PlayReadyClient.2" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Messaging" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Microsoft3DViewer" | Remove-AppxPackage
Get-AppxPackage "Microsoft.MicrosoftOfficeHub" | Remove-AppxPackage
Get-AppxPackage "Microsoft.MicrosoftPowerBIForWindows" | Remove-AppxPackage
Get-AppxPackage "Microsoft.MinecraftUWP" | Remove-AppxPackage
Get-AppxPackage "Microsoft.MixedReality.Portal" | Remove-AppxPackage
Get-AppxPackage "Microsoft.NetworkSpeedTest" | Remove-AppxPackage
Get-AppxPackage "Microsoft.OfficeLens" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Office.OneNote" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Office.Sway" | Remove-AppxPackage
Get-AppxPackage "Microsoft.OneConnect" | Remove-AppxPackage
Get-AppxPackage "Microsoft.People" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Print3D" | Remove-AppxPackage
Get-AppxPackage "Microsoft.RemoteDesktop" | Remove-AppxPackage
Get-AppxPackage "Microsoft.SkypeApp" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Todos" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Wallet" | Remove-AppxPackage
Get-AppxPackage "Microsoft.WebMediaExtensions" | Remove-AppxPackage
Get-AppxPackage "microsoft.windowscommunicationsapps" | Remove-AppxPackage
Get-AppxPackage "Microsoft.WindowsFeedbackHub" | Remove-AppxPackage
Get-AppxPackage "Microsoft.WindowsMaps" | Remove-AppxPackage
Get-AppxPackage "Microsoft.WinJS.1.0" | Remove-AppxPackage
Get-AppxPackage "Microsoft.WinJS.2.0" | Remove-AppxPackage
Get-AppxPackage "Microsoft.YourPhone" | Remove-AppxPackage
Get-AppxPackage "Microsoft.ZuneMusic" | Remove-AppxPackage
Get-AppxPackage "Microsoft.ZuneVideo" | Remove-AppxPackage
Get-AppxPackage "Microsoft.Advertising.Xaml" | Remove-AppxPackage

Take a Breath

Now you have a clean and fresh foundation to work from. Next time I’ll break down how I set up Windows Subsystem for Linux (WSL)! For now, why not kick back and relax for a bit?