olafmol

6 ms·

1.
by olafmol 2mo ago
Now it's smartphones and devices, but in the past it was work. Personally I think these days kids get a lot more attention from their parents than anytime in the past. Even so much that it can be irritating/damaging (parents being
2.
by olafmol 3mo ago
This little line from the article scares me: "but a software engineer would iron out the remaining potential bugs that I could not find quickly" Every sw dev knows this is a very dangerous, and unrealistic, assumption.
3.
by olafmol 4mo ago
Phew, was this a test? ;P Tnx for checking, and reconfirming!
4.
Show HN: Chunk sidecars for validating agent-generated code before pushing to CI(circleci.com)
1 points by olafmol 4mo ago|2 comments
5.
by olafmol 4mo ago
This is exactly the reason why I like to work with local models on a regular specced machine. The fact that the agent moves slower allows me to stay in the loop much better, compared to skimming through a huge amount of generated content an
6.
by olafmol 4mo ago
An LLM should not "generate specs", a human should. The LLM can work from the specs. It can never infer meaning from a vague prompt. If so, it will start guessing. Every human that ever did functional specification or informatio
7.
by olafmol 5mo ago
Gitea might be an option also.
8.
by olafmol 5mo ago
Out of interest: what does "better AI integration" mean? Any specific functional or non-functional requirements?
9.
by olafmol 5mo ago
Out of interest: what VCS where you using with CircleCI? (as CircleCI is VCS agnostic)
10.
by olafmol 5mo ago
Correction: Gitlab is not Dutch. It has a Dutch co-founder, and was a B.V. for about one year before moving to the US and become an Inc. The original founder is from Ukraine.
11.
by olafmol 7mo ago
Let engineers do Vibe-accounting because, AI.
12.
by olafmol 7mo ago
Debug with SSH(1) is still one of our (CircleCI) most loved and praised features. I really believe that these little QoL features can make a world of difference for sw developers and engineers, and this stays a strong focus for us. 1: http
13.
by olafmol 7mo ago
This is exactly what my team told me when they switched from Concourse CI to CircleCI. I was surprised, this wasn't really discussed, but the pressure on the team to deliver features was increasing, and they were struggling to much wit
14.
by olafmol 7mo ago
I think we (CircleCI) are doing quite well: https://status.circleci.com/
15.
by olafmol 7mo ago
It’s open source right? You know what to do ;)
16.
by olafmol 8mo ago
Almost nothing i assume. NI really lost the plot several years ago when the original founders left the company. Crappy after-sales support, lack of product vision and corresponding crappy execution, and a ton of technical debt all over thei
17.
by olafmol 8mo ago
We (CircleCI) are still there, and doing just fine :) Out of interest, what are you currently missing and what would those "essential" V2 features be? tnx for sharing your thoughts!
18.
by olafmol 8mo ago
I'd like to point out that CircleCI is typically faster (and more consistent) than GH Actions, and also offers a free tier (with more free build credits for opensource projects: https://circleci.com/open-source/ )
19.
by olafmol 9mo ago
It's not obfuscated. The free plan gives you a max of 5 concurrent self-hosted runners. If you need more you can upgrade your plan: https://circleci.com/pricing/#comparison-table There simply is no free lunch, som
20.
by olafmol 9mo ago
Agreed that caching needs (and can be, and will be) improved.
21.
by olafmol 9mo ago
CircleCI does only charge for self-hosted runners generated egress and/or artifact storage: "Any Network Egress to CircleCI will be charged. At this current time, this includes CircleCI Caches, Workspaces, and Artifacts and will b
22.
by olafmol 9mo ago
This. There are plenty of good/better CICD solutions out there, but it's tricky to compete with "comes for free with our VCS". I guess it's clear now there is no such thing as a free lunch. I feel it's a good t
23.
by olafmol 9mo ago
"That said, most teams don't self-host purely to save money" I think most do. Or at least the infrastructure/compute costs are not coming from their own dept budget anymore ;)
24.
by olafmol 9mo ago
CircleCI made great steps the last few years, f.e. to better support proper DRY working, supporting OPA policies-as-code, VSCode extensions with "dry-run" options. For some examples of more advanced usecases take a look: https:&#
25.
by olafmol 2y ago
Thanks for clarifying, appreciate it! It's true we don't support all the events that Github exposes, but we believe we support the most common and useful ones. Also, this is not set in stone and expanding all the time, f.e. https
26.
by olafmol 2y ago
You mention you're looking for (ao) "proper test reporting". CircleCI has a "Test Insights" view ( https://circleci.com/docs/insights-tests/ ) and can collect test-results from a wide range
27.
by olafmol 2y ago
Although there are definitely merits in moving the complex logic outside of the CI/CD JSON/YAML DSL, especially when using monorepo setups that can become rather complex in their logic (that they made Google create Bazel, I can th
28.
by olafmol 2y ago
understood, tnx!
29.
by olafmol 2y ago
I didn't make myself clear I think. You mention that you love Captain, and wish you had access to it when migrating away from CircleCI. I'm interested in understanding the specific reason(s) for your love for Captain's featur
30.
by olafmol 2y ago
Out of interest: CircleCI also has flaky test detection, rerun failed tests etc. Or did you mean that the CI that you were moving towards could benefit from Captains features? (disclaimer: i'm a CircleCI employee)

More ›