HN user
Every time someone reinvents the wheel, it becomes a little rounder.
Not sure if this particular library is an improvement, but even if it serves nothing but the author’s enjoyment, or education, it’s a win.
Being involved with software professionally and woodworking as a hobby, I can recommend that talk. The parallels he draws are so good that I was almost angry with myself for not seeing them before watching that talk.
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.
dimensioned[1] got me interested in Rust. I’m not far enough to recommend it, but the concept seems right.
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!
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.
Used to be luftdaten.info (German), but seems more international now. They built a pretty accurate sensor based on an SDS011.
No soldering required.
I leave the handling of those situations to Lastpass. My wife and kids may request access to my password locker, and if I don't reject within 30 days the locker is opened to them.
run commands on the worker host directly
I‘d think that Concourse is not the best fit for this requirement.
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).
I am running https://concourse-ci.org on a cheap VPC and I am very happy with it.
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
„When a measure becomes a target, it ceases to be a good measure.“
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?
Interesting - can you provide [1] and [2] please?
Same here! I thought I was the only one with this strange habit.