There’s plenty of room for improvement in the typical development workflow for Kubernetes.
One area in particular is the development feedback loop. The shorter the feedback loop, the more you stay in the creative mindset — which, in turn, is what makes coding so much fun.
But in most workflows, every time you change a service that’s running on Kubernetes — be it a major upgrade or just fixing a typo — there are lots of steps between writing your code…
A lot of people use
That is: When your program doesn’t work, add a ton of
Printlns everywhere so you know whether things are going the way you planned as your code runs.
Take the following code — and yes, there’s a bug in it:
The idea is to listen for connections, and simultaneously send a GET request to that listener. The listener should reply with
Howdy!, and the output should be:
The webserver said: Howdy!
Instead, it just hangs without printing my message. In attempting to debug this, you’ll typically see something like:
2019 fashion brings neon colors, cargo pants, and auto re-building & re-deploying microservices. Get with the times!
In this year’s dotGo I presented
go3dprint, a demo project for playing with 3D objects in Go.
The version presented had zero frills: The code compiled into a single binary, ran on my OS, and the editor simply refreshed the output files. The audience could follow along with zero distractions.
But what if we wanna make it…
I’m happy to announce that my company, Garden, has raised a €1M+ pre-seed round led by Fly Ventures. As a team of developers passionate about distributed systems, we’re excited to use these funds to tackle one of our industry’s most difficult problems.
In the current landscape we have the whole Kubernetes ecosystem at our disposal, but developing distributed systems is still hard, inconvenient, and often just not very enjoyable. The tools simply haven’t kept up with the times. …
On part #1 we discussed the nature of the issues behind onboarding in large open source projects, and briefly got into what it is about Kubernetes that makes it so complicated.
On part #2 we talked about many different possible ways to solve, or at least alleviate, the issues we saw in part #1.
Now let’s see these solutions in practice. Let’s see what they actually look like in the real world, using Kubernetes as an example.
For the past few months there has been a concerted effort towards documentation, and it’s taking the form of a complete revamp of…
I’ve been interviewing with a few companies the past month, and as part of these interviews, the other day I was asked to write an API as a take-home code challenge. I had a lot of fun doing it, so I thought I’d make a series of articles/videos on the subject.
I’m obviously not gonna use the exact same API from the interview, which left me with the question of what to do for these.
I then came up with the silliest, greatest idea I ever…
On March 8, women’s day, I and a bunch of amazing ladies had a chat at Cheesecake Labs about all things Women In Tech.
Something we quickly found out about ourselves was how many of us had come from different backgrounds than tech, and had then quit our previous careers to pursue a more computery life.
Arguments aside about why that is and why it shouldn’t have to happen, it raised a few interesting questions. One of which, as brought up by Letícia Portella, was:
How do you cope with feeling like you got into…
Last week we discussed the nature of the issues behind onboarding in such large projects, and briefly got into what it is about Kubernetes that makes it so complicated.
We also looked at a few possible solutions for those issues, and concluded they may not be enough.
Communities behind such large projects need to continually make things easier, more accessible, and make it so that new contributors can get the hang of things consistently, without needing tons of extra help.
Here are a few suggestions about how to make that happen in your project.
Let’s take it from the top.
With my Outreachy internship nearing its end, I’d like to share what I believe to be the most important lesson from working on Kubernetes full time for nearly three months.
You might’ve guessed from the title: it’s about onboarding. I won’t go so far as to claim it’s the most important part of a successful project — it’s the only part I’m familiar with so far really — but it seems like a pretty significant portion either way.
As much as we all think we know what onboarding is all about, some things might surprise you. …
Ellen Körbes runs DevRel at Tilt. They’ve built Kubernetes tooling under SIG-CLI and spoken about Go and Kubernetes at events worldwide. She/they. @ellenkorbes