Ctrl Space Blog

Choco

2022-07-01T00:00:00+00:00

Open PowerShell as admin

Download Choco:

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

Test download by writing:

choco

The terminal should return something like:

Chocolatey v1.1.0
Please run 'choco -?' or 'choco <command> -?' for help menu.

Install Git with Choco:
```
choco install git
```
Open a new terminal and test whether Git is installed:
```
git
```
The terminal should return something like: ``` usage: git [-v | –version] [-h | –help] [-C ] [-c =] [--exec-path[=]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir=] [--work-tree=] [--namespace=] [--super-prefix=] [--config-env==] []

These are common Git commands used in various situations: … ```

Carrot Cake

2019-04-19T00:00:00+00:00

200 g gratted carrots
Chopped hazzelnuts
4 dl flour
1½ tsp backing powder
250 ml brown sugar
2½ tsp cinnamon
250 ml water
2 Tbsp sunflower oil

Bake at 200 degrees Celcius for 30 minutes

About Git Cicd Seperation By Concern And Maintainance

2018-10-10T00:00:00+00:00

WIP

https://sethrobertson.github.io/GitBestPractices/

One conceptual group per repository
Seperate repositories for files needed for reuseability in other projects
Individual repositories assembled into a superproject
- git-submodules
- gitslave
Do not create very large repositories

https://medium.com/@patrickleet/mono-repo-or-multi-repo-why-choose-one-when-you-can-have-both-e9c77bd0c668

https://www.reddit.com/r/devops/comments/8vgqhq/what_do_you_prefer_and_why_mono_repo_or_multiple/e1natwi

"Personally, I prefer micro repos as it helps enforce loose coupling, which means you can deploy smaller units more regularly without worrying too much about inter-connectivity." - the_hypotenuse

https://chengl.com/multirepo-vs-monorepo/

Anti patterns

http://mikehadlow.blogspot.com/2014/12/the-lava-layer-anti-pattern.html

http://www.ben-morris.com/entity-framework-anti-patterns-how-not-to-use-an-orm-with-sql-server/

Good Software

2018-09-20T00:00:00+00:00

How can good software be recognized?

(Points taken from Ib Havn)

Designed Well

High Cohesion
Loose Coupling
Independent modules
Clear Interfaces
Little Redundancy
Layered design
Designed for Test
Extensible
Portable

Maintainable

“What makes the difference between working code and great code is maintainability” - David Rachamim

“You don’t really know how good someone’s code is until you try to change it” – Kristopher Johnson

Well documented
Code is readable – stick to coding and naming standards
Code is simple – KISS Keep it simple stupid!
Testable
Dependency injection
Encapsulation
No “gold plating”
Only optimised if needed
Automated tests

It works

“Beautiful readable , testable, maintainable code that fails to meet the customer needs is still a failure” - codingdave

As specified by customer
It solves the intended problems
Users wants to use it
It’s stable

Testing

Black box testing

System Tests
Acceptance Tests
Test Driven Development (TDD)

White box testing
Unit Tests
ZOMBIES

ZOMBIES Spelled out:

Z – Zero
O – One
M – Many (or More complex)
B – Boundary Behaviors
I – Interface definition
E – Exercise Exceptional behavior
S – Simple Scenarios, Simple Solutions

http://blog.wingman-sw.com/archives/677#more-677

Use TDD together with ZOMBIES! :)

“Do The Simplest Thing That Could Possible Work.” - Kent Beck

Developing software…

Personally I think the best thing to do is first write down your items/stories and then translate these stories into something that you can write a Behaviour Driven Development test for. It is like adding an extra layer of refinement when you closely couple the business needs to TDD and make sure that TDD is focused on covering the desired specifications.

“As a user-role(1) want a feature(2) that I get business value/benefit(3).”

Items/Stories must never include design ideas –only describe wanted functionality!!

I think code should approach readability and abstraction. I think in any case that something can be descriped as one logical functionality it should be divided so. This will provide seggregation and the next person to read your code will be able to quickly disguish what belongs together and will be able to read on a more abstract level about what you are trying to do.

Getting Wsl

2018-09-15T00:00:00+00:00

Windows Subsystem for Linux (WSL) enables using the Linux terminal within your Windows system. It is more light weight than running a virtual machine. It is terminal only, so it is not the right option if you want to run a programme relying on a graphical user interface. However, you can launch the VS Code editor using WSL. WSL is a great light weight Linux developer tool for Windows users.

WSL installation

See the official guide by Microsoft or follow the steps below: https://docs.microsoft.com/en-us/windows/wsl/install-win10

Run the following command as administator in PowerShell:


Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

Restart you computer.
Install Ubuntu from the Microsoft Store:

https://www.microsoft.com/store/productId/9NBLGGH4MSV6
Launch Ubuntu and wait for the installation to complete.
Enter your desired username and password.

Navigate to your Windows folder system by writing:


cd /mnt

Return to the path of the Linux subsystem by writting:


cd ~

Visual Studio Code using WSL

Visual Studio Code (“VS Code” or just “Code” abbreviated) is an editor or light weight IDE. If you have not used it before you can download it here: https://code.visualstudio.com/

Launch VS Code.
Navigate to the Extensions Marketplace.
Search for “WSL” or “Remote - WSL” in the marketplace or download the extension here: https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl
Once installed you can now launch it from View>Command Palette... the shortcut for opening it is Ctrl+Shift+P.
The Command Palette should now be seachable in a field in top of the VS Code Window. A > should appear in the start of the search field.
Search for “Remote-WSL: New Window” and press enter once it has been selected.
Launch the terminal within VS Code to check that you are within the WSL environment. Open it using hte menu in View>Terminal or by using the shortcut Ctrl+æ (Danish keyboards)
You should now see a Bash terminal where the name you chose in the WSL installation step should appear.

It is also possible to start VS Code from WSL by writing code . in the WSL terminal.

Vanilla Pancakes

2018-08-26T00:00:00+00:00

These are my favorite pancakes. It is a modification of an old recipe that has been taken off the internet, so I decided to preserve it on my own page. It is a flat pancake like crêpe.

This portion is recommended for up to 4 people

125 g / 2 dL flour
3 dL milk
2 eggs
30 g butter / magarine
1 tsp of salt
1 tsp vanilla sugar

Mix flour, milk, salt and vanilla sugar
Mix with eggs
Melt the butter and mix it with the rest
Bake the pancakes :)

Package Managers For Windows

2018-03-07T00:00:00+00:00

Installing Chocolatey (or choco for short)

Chocolatey is a package manager for Windows (like apt-get or yum but for Windows). It was designed to be a decentralized framework for quickly installing applications and tools that you need. It is built on the NuGet infrastructure currently using PowerShell as its focus for delivering packages from the distros to your door, err computer.

Source: Chocolatey

Open PowerShell as an Admin
Run the following command: Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))

Now choco should be installed and ready for use.

Installing Neovim from the commandline

Open PowerShell as an Admin
Run the following command: choco install neovim
Accept installing the scripts. You might have to write y into the commandline a few times

Add to Path from Advanced system settings

This is so you can open Neovim from the commandline.

Go to your Neovim path folder. It might be located here: C:\tools\neovim\Neovim\bin
Follow this guide to add variable: How to edit your system path
Use the path of the bin folder
You can now open nvim and nvim-qt from the commandline

Use Chocolatey indirectly with PackageManager

Instead of directly using the Chocolatey packagemanger the PackageManager (previously known as OneGet) can be used. PackageManager Is more of a package manager manager. So it can manage Chocolatey for example.

Run PowerShell as an Admin
Register-PackageSource -Name chocolatey -Location http://chocolatey.org/api/v2 -Provider NuGet -Trusted -Verbose
Maybe take a look at Chocolatey packages. Neovim is there. Or look whether it is there with Find-Package -Name Neovim
Install-Package -Name Neovim

PackageManagement documentation can be found here: https://docs.microsoft.com/da-dk/powershell/module/packagemanagement/?view=powershell-5.1

Raspberry Pi Linux Terminal Basics

2018-01-16T00:00:00+00:00

Log 2018-01-04

A new adventure begins. Let me summarize what I am doing and where I currently am in my learning process:

I have aquired a Raspberry Pi Zero W
- I installed Raspian Lite on it
  - This seems to be distribution you want if you do not care for a GUI
- I installed Lynx on it and set it the to use Vi keybindings
  - It is nice to have a browser than enables me to stay in the same environment
- I installed Git so I can easily update my files from the Pi
  - E.g. using it for committing this file
- I Installed Nvim/Neovim
  - I want to try this modern continuation of Vi/Vim

I wanted to have a split screen and being apple to switch between multiple terminals. These are my findings:

Opening/switching to another terminal instance
- Press Alt+F<num>. You should already have a terminal open at Alt-F1
Go to Nvim and use the split window functionality there
- Use Ctrl+w v or Ctrl+w s for opening windows, Ctrl+w q for closing windows and Ctrl+w w for switching between windows
- Use :te to open a terminal within Nvim and Ctrl+\ Ctrl+N to exit terminal-mode and i to enter terminal-mode again

Now I didn’t get right down to documenting when I set up my Pi, but I remember that there was an issue with displaying on my screen through the display port. I think this was solved by unplugging the power supply and connecting it again. So first connect the SD card (with the desired distribution) and the HDMI cable. After that connect the Pi to power and you will now see the setup screen.

Log 2018-01-05

Today I want to learn tmux.

Basics
- Type tmuxto enter and exit within tmux to return the ordinary terminal
- When you are within tmux it is just like in the terminal, except you will now notice the line at the button that might say something like [0] 0:bash*
- Ctrl+b is as a prefix for tmux commands
- Ctrl+b d means that you will detach tmux - This might be a better way to exit tmux because it does not close the session and you might be able to return to the work you left

Log 2018-01-16

SSH

To set up the Raspberry Pi for SSH you have to go through a few steps.

Enable SSH on the Pi

SSH is by default disabled for the Raspberry Pi. Therefore you need the enable it. Use the following command to access the configuration of the Pi:

sudo raspi-config

Use the arrow keys to navigate within the configuration tool. Navigate to Interfacing Options and press Enter.

Now navigate to SSH and press Enter. You will now be asked Would you like the SSH server to be enabled?. Navigate to <Yes> and press Enter. You will now be informed that it has been enabled. Press Enter to return to the menu. Within the Configuration Tool menu simply press Esc to exit and return to the terminal.

The default login credentials of the Raspberry Pi is:

Username: pi
Password: raspberry

Using the default is a security issue as anyone who know of the common login of a Raspberry Pi can now access it through SSH. Therefore you most likely would like to change your password. You do this with:

sudo -i

This makes you the root. Meaning that you will no longer be pi@raspberrypi, but root@raspberrypi and you can now run commands without using the sudo prefix as you have root privileges.

Now you use the following command to say that you would like to change the password of the user pi:

passwd pi

After this you will be asked to enter a new UNIX password. Choose something that you can remember.

To logout from root simply write:

exit