WingNews logo WingNews GitHub [2]

suhlig's comments

suhlig | 2 years ago | on: GitHub Actions could be so much better

Concourse has it right: You can ssh into a failed container, and debug in the exact environment where the failure occurred.

I don’t understand why people settle for less.

suhlig | 4 years ago | on: A career ending mistake

> Next to every incubator was […] a product that I had written a lot of software for.

That must feel like ultimate satisfaction - software that is making the world a better place. Congratulations!

suhlig | 4 years ago | on: How to rapidly improve at any programming language (2016)

That part where you have to make a commit in order to attempt to fix a CI problem was driving me nuts. It‘s the same with Travis.

Concourse gets this right - you can run a pipeline task as a one-off from your workstation until it’s done, and only then check it in. And even ssh into the build container in order to debug build failures.

suhlig | 4 years ago | on: Ask HN: Best self-hosted CI solution?

Not sure how your current builds look like, but I tend not having to deal with containers per se. All they force you to do is be explicit about the build‘s dependencies, which I think is a useful thing.

My approach for migrating existing builds to Concourse is to start with a stock image (alpine or ubuntu), and gradually add things that are missing (`fly execute` is a big help for that).

Once I have a successful build, I extract the prerequisites into a task image (but that really is an optimization).

suhlig | 4 years ago | on: The mortifying ordeal of pairing all day

> how do you check your e-mail?

You don’t. That’s what breaks are for (assuming personal e-mail).

> What if there's documentation that needs to be read?

- Define an objective together (e.g. „We‘d like to understand how the HTML progress element works“)

- Optionally, agree an a timeout

- Split (both reading at their own pace, on their own device)

- Join and discuss results

suhlig | 5 years ago | on: Universal Split Screen

How do you see this being used in pair programming? To me, the key is to work on the same thing, one person being the navigator (“where to go”), and the other being the driver (“handling the pedals and the steering”). In this mode, there is only one keyboard and one thing to look at. Why would you want a split screen?

suhlig | 6 years ago | on: Daytripper

Interesting - can you provide [1] and [2] please?
page 1