Riding on Zwift (aka commuting to the wfh office) and reading @manton’s book (at book.micro.blog) on microblogging and the open web. 🥳
Staubsaugerroboter sind gar keine Roboter, sondern Saugetiere.
I just signed the web0 manifesto and you can too!
I brought an external display to my new desk in setting.io’s office. I really dig the change of scenery and having an optional commute again.
My micro.blog timeline is pretty empty during the day as I mostly follow people from US timezones.
I just spent more than 60 minutes reading up on Arel and trying a bunch of different things just to learn that it won’t work. So back to writing ugly SQL strings. Too bad.
Spatial audio with AirPods Pro when listening to music on my laptop is really confusing sometimes. After moving my head I wanted to make sure that the sound doesn’t come from the laptop’s speakers and indeed from the headphones. It appeared to come from the laptop. Crazy.
GitHub Codespaces port errors
GitHub codespaces is a great feature by GitHub that let’s me work on an iPad way easier than it was before. It’s also cool for teams to quickly setup a new developer, of switch between branches.
I use it for Ruby on Rails development, mostly. Sometimes a thing happens that prevents me from continuing
my work and I had trouble finding out how best to solve this. Here’s what happens:
I start my codespace and want to spin up a Rails server, to inspect the website.
Once I type bin/rails s the server starts and I get the notification to open up the browser in a new tab.
When I navigate there, I see this screen:
It’s a message from nginx that tells me that there is a 502 Bad Gateway error when I want to access my codespace.
The solution that always helps me is to unpublish the port and re-publish it again. Here’s how that looks in the interface:
That should solve your issue and you can quickly access the website.
Something new
Changes!
I joined my last client, Edeka, in April 2020. Since then I am not freelancing anymore. My old Wordpress site ran on quite expensive hosting. Which I could justify as a business expense. But since those are gone now, I have to switch to something cheaper.
This site now runs as a GitHub pages site, powered by Gatsby. Which I love quite a lot. And now I am free to experiment with this site more, again.
Onboarding new team members
Tomorrow I will help a new team member onboard at my client. I am the acting tech-lead for the client right now and so it’s my job to make sure that everything is in place for this new member of the team.
The former tech lead onboarded me in September (not so long ago). He had prepared a list of tasks we had to do together. He even created a whole new Trello board, just for the onboarding. Did he do it because it was so laborious? No! In fact, the onboarding mostly consisted of joining the services and Saas applications we use and getting familiar with all the processes for running the show.
But it did help to be able to cross items off the list. We were always aware of which services were yet to join. We also knew what was missing until I was at 100%. That was certainly helpful.
When I am onboarded at a new client, I generally send them my onboarding survey beforehand. In it I ask questions that are relevant to the process and to me, and that come up with every client. Asking them these questions before I arrive, they tend to be better prepared.
I am really looking forward to having the new developer join the team, tomorrow. I bet he’ll do great. And to help him along, I’ll just follow my onboarding sheet. 😉
Do you use something similar?
Yours,
Holger