I started thinking about this while leading an internal Ops platform at a previous operations-intensive tech company. As we automated Ops work, I found the bottleneck to shifting left was was defining the processes our Ops team followed. Eng entered late: first, we'd throw Ops resources at a new challenge; then gradually systematize it; wait for PM attention; document the process; and finally engage engineering. This was necessary since systematized bad processes meant scaled mishandling of issues and engineering rework.

Drafting AI offers a different path: teams begin automating processes organically as they discover them, growing toward full automation as understanding deepens. Human review catches edge cases, handles ambiguous situations, and gives an incremental path towards full automation without rework.

Hopefully this lets internal tools teams shift automation further left.

I'm looking for something similar: I want it to trigger when I'm on Twitter (or HN) during 9-5 hours, and ask me what I'm supposed to be working on. Just a small nudge to rubber duck what's blocking me

yeah one flow for all the stages is the way. I like having a "status" column, and have a different task queue depending on the status

is the "workflow graph" entirely custom built or is there a library/framework/service for it? Would love to hear more

sorry I meant to say or explain computational graph, and yes langgraph was reintroduced recently last week.

totally— this is for integrating into custom internal tools. Consider content moderation: you wouldn't want mods getting tickets in JIRA then switching to a different tool to action them.

If switching between screens is not a problem, by all means prefer Linear/Asana/Jira/etc!

yes! One of my original thoughts was "Job queue, but for humans"

Totally— OpsQueue is for custom internal React apps to have integrated task management. If workers can switch between Linear and your internal apps, or you don’t have a custom internal React app, you should use Linear.

In some ways OpsQueue’s goal is to be a headless, API-first Linear.

Love to see this! I miss stacked diffs from working at FB— Graphite looks like the best way to be productive outside FAANG internal tooling

Hell yeah, that's the idea haha! Bringing the internal super secret FAANG workflows to the world :)

Yeah you have to do

  <If cond={...} then={() => 
    ...
  } els={() => 
    ...
  } />

so the `then` and `els` branches only get evaluated if needed

We use ternary extensively with in JSX. Keeps the logic in vanilla JS

{ some_condition ? (

  <H2>It was true</H2>

) : (

  <H2>It was false</H2>

)

Even though I'm a JS programmer myself and I do use similar constructs once in a while, I have to admit that this gets dangerously close to the Greenspun's tenth rule... In times like this I miss proper Lisp macros.

Which has ugly untax IMO

AI will solve web accessibility by screen readers that summarize visual content, ignoring ARIA and making it irrelevant. Multimodal GPT-4 can take a screenshot jpeg and answer questions about what’s in it (buttons, links, ads, headers, etc). The future of accessibility is rendering DOM to jpeg and asking GPT to be your eyes; we’ll look back on semantic markup as a failed idea that was never going to work