Hacker News: ahpook

New comment by ahpook in "Microsoft Office renamed to “Microsoft 365 Copilot app”"

ahpook — Mon, 05 Jan 2026 19:45:23 +0000

Moral: don't come for Prince or Anil will come for you :)

New comment by ahpook in "Anyone can access deleted and private repository data on GitHub"

ahpook — Fri, 26 Jul 2024 18:43:07 +0000

That's correct, it's doing a clone into an empty repo rather than using the fork API - code is here: https://github.com/github-community-projects/private-mirrors...

As it pertains to the post, since that private mirror is disconnected, none of the concerns about accessing deleted data apply.

The downside is that you don't get any of GitHub's performance and UI affordances from the fork network. But for the use case of private iterations on work headed for a public upstream, that's a trade-off that seems worth making.

New comment by ahpook in "Anyone can access deleted and private repository data on GitHub"

ahpook — Wed, 24 Jul 2024 22:55:17 +0000

Hubber here (same username on github.com). We in GitHub's OSPO have been working on an open source GitHub App to address the use case where organizations want to keep a private mirror of an upstream public fork so they can review code and remove IP/secrets/keys that get committed and squash history before any of those changes are made public. Getting a beta release this week, in fact - check it out, I'm curious what yall think about the approach

https://github.com/github-community-projects/private-mirrors

New comment by ahpook in "Show HN: Relay – Event-driven DevOps automation"

ahpook — Fri, 26 Jun 2020 00:31:57 +0000

FWIW we didn't make a separate extension, it uses the vscode-yaml extension from Red Hat, you just configure it to associate certain filetypes with our json-schema and custom tags. It is awesome for sure.

https://relay.sh/docs/setting-up-editor/

New comment by ahpook in "3 Commandments for CLI Design in 2020"

ahpook — Tue, 14 Apr 2020 19:30:20 +0000

Well, there are some people doing UX work in this area but it's under appreciated, and I agree that it's largely programmers who give a sh!t about design rather than the other way around.

I was really expecting, given the strong opinions people here have about all things design related, that there'd be some spicy takes :D

But I super appreciate your feedback, thank you!

New comment by ahpook in "3 Commandments for CLI Design in 2020"

ahpook — Mon, 13 Apr 2020 17:22:18 +0000

Thanks for the feedback!

Interesting point about "first 15 minutes" - the service (and CLI) we're building will probably guide users into the CLI experience during that first ... maybe first 30-60 minutes, rather than 15, but _really_ early on as they get familiar with it.

From a UX standpoint, that discoverability you describe with the GUI is really about the affordances the user can discern with from the baseline state. That is, the 'rotate' button is visible without the user having to do any discovery at all, it's just _there_. What would the CLI equivalent be - I think part of it is the autocompletion scripts that bash/zsh let programs drop in to the `completions` directory so `command ` shows you all the possible next steps...? Worth thinking about.

New comment by ahpook in "3 Commandments for CLI Design in 2020"

ahpook — Thu, 09 Apr 2020 21:01:45 +0000

Huh, I came here to submit this (I'm the author) and it was already in - neat. Would love to hear anybody's hot takes on the piece, there's some matters of taste in this (it's design, after all) but I think most of it is pretty well grounded in my experience living at the command line since the 90s...

New comment by ahpook in "Moving away from Puppet: SaltStack or Ansible?"

ahpook — Tue, 05 Aug 2014 18:17:46 +0000

I'm a little sad because most of these issues (as I understand your description them) are already fixed or well underway :( It's probably too late for your specific case but I'd like to reply anyway since a lot of this is "conventional wisdom" based on old information. Full disclosure: I'm the product owner for Puppet and before I worked here, I ran it in large-scale production since 2008.

Not quite sure what you mean by 'native support', but gem and pip package providers are built-in. there are high-quality modules for git (puppetlabs-vcsrepo), virtualenv (stankevich-python), npm (puppetlabs-nodejs), etc -- it's a design decision to move much of this into modules and out of core so they can iterate faster.

Totally agree that loops make many language constructs much easier, and there's looping in the rewritten parser -- https://docs.puppetlabs.com/puppet/3.6/reference/experiments... -- which will be on by default in the next semver major.

While the model definitely wants you to describe relationships between resources if you need to send subscribe/refresh messages, there's toggle-able ordering algorithms that will let you run them in manifest order -- I blogged about it here: http://puppetlabs.com/blog/introducing-manifest-ordered-reso...

The parser and evaluator are undergoing a total rewrite to be an expression based grammar, which is explicitly to make better definition around the language and eliminate the gotchas -- https://docs.puppetlabs.com/puppet/3.6/reference/experiments... (this will also be the default on the next semver major)

--eric0 / @ahpook