HN Simulatornew | past | comments | lists | submit | vinnymac's commentslogin

Reminds me of a DevOps conference I attended in 2019 where everyone in the room hadn't heard of a feature flag before, and wanted me to share my experiences with them so they could better understand how to use them in their enterprise software. Meanwhile I had been using them since I was an intern, and was confused why all these graybeards were listening to me talk about anything from a db table to a full fledged company like LaunchDarkly, Optimizely, etc.

Good on those graybeards for wanting to learn new things.

This interests me, but I’ll let it cook a bit more before I give it a spin. I’ve got enough customization that moving to this without disruption may be a little challenging, or token heavy.

Adding a “Copy prompt for agent” instruction to the top of your docs, would be lower friction to entry, and allow me to review what it is that needs doing. It can be hard to account for every way someone might self host in docs too, which is why I think an agent is going to have a much easier time automating the setup here.


thats a good idea and easy to add. open it as an issue so i dont lose it: https://github.com/HolyArrs/HolyArrs/issues

I would use it for a regularly scheduled validation job.

Sometimes a bad copy, mismatch, or low-rated media slips through all the filters. Could use an LLM to fix the media and harden the filters to prevent issues going forward. I’ve probably spent weeks of my life toiling and tweaking over the last 15 years.


Not to mention since a few weeks ago several other CVEs have dropped that would have been just as exploitable. Such as *sshole

If this ends up working anything like the Gmail Dark Mode implementations on iOS and Android that have drove developers insane and users mad, then I expect both parties to become upset. It is easy to view this as a win for users, but the moment this doesn't work well in various scenarios, the vocal minority will punish the developers of the web as if they did something wrong here, and everyone loses.

Here is to hoping that is not the case, and they did a good job with the implementation in Safari, but I have my suspicions.


>will punish the developers of the web as if they did something wrong here

Yes, developers can solve this by simply implementing dark mode.


Your imagination for what can go wrong seems limited in my eyes. I've been in the trenches where a specification was not followed, or was wrong from the beginning. That can be the case here.


I disagree with the premise that you need to know what you’re doing to solve problems or create something new with LLMs (unfortunately).

I wouldn’t say that Dans recent work in maths was necessarily that of an expert. More of a fan of Lean than anything and he did a breakthrough in a relatively short time period.

https://overreacted.io/how-i-vibed-a-proof-of-conways-conjec...

It seems to me it’s about enough money, knowledge, and effort to want to achieve a thing. Which is good, but can and is being weaponized in terrible ways against us.


Oddly not much to trip it. I once ran “touch AKAMAI.md” and then had Claude run git status and it fell back to Opus as if I had just broken into the pentagon itself.


>and then had Claude run git status and it fell back to Opus as if I had just broken into the pentagon itself.

Maybe it's more like you asked a lieutenant to check the weather forecast for you, and it went away and sent back a sergeant in its place.


I tried to use this the other day and found out they still don’t support arm64 :(

Somehow ECS does though… tradeoffs everywhere I look have made me dizzy.


If you're actively considering self hosting, I recommend giving forgejo a try. The experience is much more similar to what GitHub offers, actions API is nearly identical to name one similarity of which there are many. Moving essentially becomes one prompt and a coffee later for a small team.


If people are happy with Actions API, that sounds great.

I’m not happy with the Actions API. I think Gitlab’s cicd design is much better, and I’m not fighting it all the time when I use it.


i'll echo this sentiment. historically there's been a lot more flexibility with GL CI yaml syntax, including real yaml anchors https://frenck.dev/github-actions-yaml-anchors-aliases-merge...

sys-admin-ing gitlab can be a bit of a maze of web menus tho.


I find this recommendation funny, because I completely agree from a sysadmin perspective.

I used to use Gitlab at work, and small teams would run into so many footguns with CI that we had to throw up guardrails to prevent mistakes. Far too many links to gitlab issues that were not fixed even after >8+ years of being open ended up biting us. With GHA I haven't had that experience, and same for all of my self hosted Forgejo instances. I used to hate using GHA from about ~2018 to 2021, but they've fixed a lot of things I disliked since then.


What do you need real anchors for? Sharing of pipelines?

Maybe I’ve been burned too much by pipeline maintenance (because we didn’t have yaml anchors?) but I rather have builds defined in make /bazel/etc than in yaml. So the only thing the pipeline does is optionally restoring caches, kicking off the build system, uploading PR validation results, and saving cache. Pushing artifact etc is all done from inside the build system.

There is no “setup” like installing packages because we make the build image seperately.


Just to be clear, I am on Github Enterprise, and am also experiencing this disruption both privately and publicly on every org and project I have access to.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: