[–] 24 points 2 years ago

Well, you see, first off you need a microservice to distinguish between those 2 types of step, then you need separate microservices to handle storing those values. Then you need a GraphQL database in a multi zone Kubernetes cluster as a backend...

Ugh I feel dirty saying all that.

  • source
  • parent
  • context
  •  

    My wife and I are both autistic. She has difficulty moderating the volume of her voice, and I'm volume sensitive. So far she's been unable to recognize when I'm having trouble, and I've been unable to stop being so sensitive. :/

    I've tried wearing earplugs but I have trouble remembering to keep them in.

    Does anyone have any suggestions on how to reduce volume from someone when you're sensitive and they're loud without realizing it?

     

    This is solved, I was being dumb. Please see second EDIT below

    This isn't really language specific, but if it helps I'm using Python. I can get the parameters just fine with the Traitlets module, but I'm still a novice really and figuring out which patterns to use is challenging.

    Say you have a bunch of command line parameters. Some are booleans, where their presence means True, absence means False. Other parameters must accept one text string, and others can be used multiple times to build a list of strings.

    It feels inefficient/wrong to use a bunch of IF/THEN/ELSE statements to decide what to do with the parameters, and prone to edge case errors. Is there a pattern that would invoke the correct method based on the combination of input parameters?

    Examples:

    app thing --dry-run --create --name=newname01 --name=newname02 --verbose
    
    app thing --create --name=newname01 --name=newname02 --name=newname03
    
    app job --cancel -i 01 -i 02 -i 03
    

    EDIT: Via the Traitlets module, I get those arguments parsed and accessible as self.argname, so getting them into my app is working great. It's just deciding what to do with them that is confusing me.

    Thank you, sorry for my noobness.

    EDIT2: I think I understand where I'm going wrong:

    I'm creating subcommands based on objects, not actions. i.e. appname thing --action should really be appname action --thing. Once things are divided up into actions, assigning things to those actions will be much, much easier and straightforward.

    Sorry for a confusing and fairly pointless post :(

    view more: next ›