fatterypt

I'm more than happy with https://codefloe.com for private repos. The service is blazing fast and the maintainer does a great job keeping it up-to-date with recent Forgejo releases.

I've been using codefloe for everything personal, and I couldn't be happier. It's been stable, snappy, and offers me everything I need. I don't miss GitHub a single bit

I just wanted to say that I recently went back to using my RSS feed as a main source of news, and your TILs have been one of the first additions to it. Appreciate it!

Merry Christmas!

I generate one-time only email aliases to virtually every service I use. Some sort of a poor-man's hide my email from iCloud. If that email is compromised, or I start receiving spam for it, I know where it came from. This has become a vital part of my workflow, and not having it is a show stopper to me, unfortunately.

I cannot find it in the website, but do you offer catch all addresses?

Ankaux mi!

started clicking around and there it went 30 minutes of my time, increasing the lead time of the current task I'm working on. :)

Amazing game! Thanks!

This ^. I see a lot of people are tricked by their companies to get them to come to Berlin. Then the companies get them believing that a 60k salary is generous for someone with loads of experience.

Once you get here, you realize that a lot of companies pay much more than that and you've been taken advantage from.

I've been through a situation like that in a very international team, where culture played a significant factor in how people communicate. Once people knew about their preferences, it became easier for them to collaborate.

Did you try to do some team building activities with the whole group? Sometimes getting them to connect on a more personal level gets people to open up.

Getting things done should be the correct answer for most of the times. All the code quality, design patterns, testing, and automation is done with an objective of keeping the ability to still get things throughout the life of that product.

I've seen horrible overengineered sins being done due to this "focus on code quality" for the code quality sake.

While this may even work, it is not practical and it is a disappointing experience for a pipeline centric type of CI such as concourse.

In other tools, hitting re-run would simply replay the job, with the same state it was executed in the first run. I would expect concourse to behave similarly, but no.

This is also close to my experience. Improving, but not there yet. Unfortunately, it will retrigger the same job with the updated version of the resources. With other CI tools, it was possible to replay the same job, with whatever inputs they took by the time they ran, with concourse it does not seem t be possible.

A practical impact of this issue is that we cannot simply reprocess a previous deploy step, with the old artifacts and inputs in a middle of an outage.