HN user

gscho

341 karma
Posts9
Comments94
View on HN

Having worked there around 2020-2021 there were many folks not happy with being forced to use azure and being forced to build GitHub actions based on azure devops. Lots of AWS usage still existed at that time but these days u bet it’s mostly gone.

Back in university I took a course in legacy programming. We did a project in each of Fortran, COBOL and Ada. I enjoyed Ada very much. The module system made a lot of sense to me and the compiler found a lot of mistakes (compared to C). Thanks for sharing this article. It brought me back and makes me want to give Ada another go now that I have 10 years of real world experience.

Not the OP but we could mention that time where he called a hero a pedophile or when he bought twitter to promote free speech and then banned anyone who said negative things about him. No one human should have 260 billion dollars and be thought of as a good person unless they do a ton of philanthropy.

This is exactly how I feel about my side projects. Sometimes our day jobs are not exactly what we’d like to be working on so it’s nice to “putter” on a side project to scratch that itch. If someone else finds it useful one day that is a nice bonus but is ultimately not what drives me to work on it.

Another pitfall I have encountered is the lack of a true ephemeral agent runner solution for running the actions runner agent in your own infrastructure. The way it works (the last time I checked) is when you register a worker as "ephemeral: true" it automatically deregisters itself from your runner pool and kills the agent process when a job is completed, but it is up to you to clean things up. This leads to somewhat hacky scripts to delete the compute instance after the agent process exits. There is also no officially supported kubernetes controller for creating ephemeral agents but the community created one [1] is often mistaken as an official github project.

- [1] https://github.com/actions-runner-controller/actions-runner-...

This looks really cool and should help me out when integration testing things are require an LDAP connection. For example setting up the Jenkins ldap connector in an automated test.

PS: I'm glad we no longer need to state in the title of a Show HN post "written in rust".

I think calling it a secret when it isn’t gave it a bad wrap. The last time I looked at the documentation it didn’t even clearly describe that it is not a secure object (that may have changed recently). Why call it a secret when it is not even close to one? I guess thing-to-store-secrets-if-you-use-rbac was too long.