Live data from Hacker News

Viewing profile — ali_piccioni

ali_piccioni

HN member
Joined
Sat, Feb 10, 2024, 10:49 AM UTC
HN karma
21
Public activity
12 items

About ali_piccioni

https://www.linkedin.com/in/ali-piccioni-1217a411

Recent public activity

  1. story
  2. comment
    Comment #44452899

    I moved all my precommit hooks to prepush hooks. I don’t need a spellchecker disrupting my headspace when I’m deep into a problem. My developer environments are setup to reproduce …

  3. comment
    Comment #42821154

    Wittgenstein’s ruler in action.

  4. comment
    Comment #42253970

    It highlights a classic management failure that I see again and again and again: Executing a project without identifying the prerequisite domain expertise and ensuring you have the…

  5. comment
  6. comment
  7. comment
    Comment #41718913

    The information can be compressed into a table that shows what knowledge (columns) each party gain (rows) at each stage (cells) of the connection. Can Can Transmit | Receive Client…

  8. comment
    Comment #41659749

    In priority, 1. Stop using API keys. Configure SSO integration for developers and OIDC for automation. For example, this is very easy to setup with AWS. 2. If the above is not poss…

  9. comment
    Comment #40594772

    The rules are open source. We did run into some road bumps in Rules Rust, that required patches or clever work arounds. But I believe the community has made great strides to improv…

  10. comment
    Comment #40590835

    We had an integration test that involved many tool chains and languages to prepare. Rust compilation, WASM compilation, Docker builds shell scripts that produced a VM image, Python…

  11. comment
    Comment #40010094

    Long lived credentials are a security red flag. We setup our AWS organization’s policies (SCPs) to prohibit long-lived tokens. Instead access goes through SSO or OIDC. It’s difficu…

  12. comment
    Comment #39325225

    Having led a successful Bazel migration, I'd still recommend many projects to stick to the native or standard supported toolchain until there's a good reason to migrate to a build …