As you could see in my ROI stock series, I’ve been using Trading212 for a while now.

While it has some nice dashboards, I wanted more and since they offer a very nice CSV exporting feature, I decided to create my own Go-based tool to do aggregation and create a financial overview of my stocks.

💸 You can still use my affiliate link to get your own Trading212 account including a free stock of up to €100: https://www.trading212.com/invite/HrAs2dFZ

Header by Alan Levine CC BY 2.0

Go has made it easy to work with Unix operations, it comes with the platform-independent built-in package os to interface with the operating system.

They offer nice features such as os.Stdin and os.Stdout, wrappers of type os.File around the OS’s common standard streams.

The os/exec package is also great. It allows you to run Unix-tools from within your Go application.

Package exec runs external commands. It wraps os.StartProcess to make it easier to remap stdin and stdout, connect I/O with pipes, and do other adjustments.

💬 Read more

I have been writing Go (or Golang) for about 6 years now. In that time I’ve seen quite a few different ways on how to organize a Go project. During my time at MessageBird I got introduced to a nice layered approach. I’ve taken those lessons and applied them to something that feels right for me; github.com/gerbenjacobs/svc

svc

svc is not an actual framework, but more a convention for creating microservices.

The core of svc is centered around 3 layers: handlers, services and storages. Together with the cmd folder they are responsible for organizing your code into a clean and well-organized structure.

It’s been a month since I joined GitHub in February of 2022. I’m enjoying myself a lot, but I’m also not sure if the reality has set in completely.

In 2014 I started my first tech job and remember that I went to a conference and got GitHub stickers, they were awesome and all ended up on my MacBook. Eight years later I now work at that exact company. 🚀

Onboard sessions

The first two weeks are oriented towards onboard sessions, unfortunately they were in Pacific standard time, so that meant 8PM CET. The first thing that you’ll notice is that a lot of the work you do is by using GitHub itself. There’s an onboarding repository with a project for every person that joined during your cohort. Here you can find issues with tasks that you can complete during the first days.

It’s time for a mental exercise. You are going to give story points to a user story, that I actually completed. Then I’m going to tell you what I had to do and which issues I ran into.

Background

We have a page that lists birthdays for people on that day, but excluding the current year. This way we can showcase everyone who is 1 year or older.

This is nice, but if you want to find birthdays for a specific date, you might have to wait a year for it to come around.

Since november last year I started working on the HabboAPI project. While it is not my first repository, and maybe also not the first serious project (that would be my attempt of the RWS library), it's the first where I went the extra mile to create documentation, tests, continuous integration and Packagist support.

I also intend to support this and hope to see other people contribute. So far I have one favourite!