Skip to content

Instantly share code, notes, and snippets.

View kepop1's full-sized avatar
🧙
This needs more D&D

Kenneth* kepop1

🧙
This needs more D&D
  • Manchester, UK
View GitHub Profile
@kepop1
kepop1 / so_you_want_to_be_a_dev.md
Last active August 25, 2023 09:27
So you want to be a developer?

Ello 👋

First it's absolutely fantastic that you're even considering getting into the world of development!

Secondly this is also not a path that can be taken lightly either and there's a lot of people who end up dropping out of the flow - but there's many many many more that succeed and change their careers 😁

In general the majority of developers will advise some form of the following for your journey.

Get a taster

@kepop1
kepop1 / BTBW_Lodash_README.md
Last active February 27, 2020 15:04
Behind the Buzzword - Lodash/FP - Kata Instructions

Lodash/FP - Behind the Buzzword Kata 🐝

After that short 5 minute micro-talk covering Lodash/FP, I'm sure that everyone's definitely an expert! However there's a couple of challenges that we can do to see this in action! 🤔

We've got ~15 minutes for this so that's plenty of time to have a beer and have a go at using lodash. 🚀


Challenge 1 🍺

You have a dataset that consists of a mixture of accounts for a user, this is similar to what we might face at WonderBill with our timeline ;).

@kepop1
kepop1 / visualstudio-parallels-mac.md
Last active February 9, 2020 23:47
Debugging Visual Studio 2017 inside Parallels on MacOS

Debugging Visual Studio 2017 with Parallels inside Mac

NOTE! This may not work on the later versions of Visual Studio!

This should gist should help you in creating a local development environment that allows the debugging of Visual Studio 2017 inside of Parallels (in my case running Windows 10)

The result of this enables you to debug Visual Studio through the Mac bridge, e.g. selecting debug in Visual studio, and the default web browser launches in Mac.

The project should work in Windows without being modified beforehand, fix any issues here before setting it up on Parallels

I've used port 57877 however this is what the local project was using at the time. You can use whatever port you would like (avoid any protected ports)