Viewing profile — mawildoer

I wanted to setup a slackbot to manager Doordash orders for our company. Starting with PyPi "Doordash Client": https://pypi.org/search/?q=doordash+client I was excited by 5 recentl…

Surfacing all exceptions at once saves end-users time and frustration. Collecting and raising exceptions is also a great pattern to write robust, simple multi-path code. I rolled t…

If you really want people to use your stuff, you should make it easy to get started as possible. For interacting with Github Actions, that means setting up OIDC, so you can prove w…

I thought it was a big upgrade. Comparing Zerox w/ Unstructured on the first 5 pages of [this datasheet]( https://www.ti.com/lit/ds/symlink/lm5117.pdf); zerox gave me what I wanted…

It's interesting how it ignores things like headers and footers. LLMs have an edge there in "deciding" whether to include something in the output or not. It'd be great if your host…

We have some plans and atopile already supports some configuration regarding those deviations. There's a component selector which can choose resistors, caps, inductors etc... from …

Lot of good stuff! We're working on some updates to the package manager now that should make a lot of that super tenable to build out.

Not at all! Thanks so much for engaging with us on this level. It's greatly appreciated!

You're not the first person to ask for alternative syntax highlighting! Might be something we need to address soon. I think an LSP server is what we're really excited about, since …

You're right about "code" not being the right solution for everything. In the case of the layout we have indeed already already implemented an MVP of the "snippets" approach you de…

If we can build the equation solver our hearts are set on, you should be able to account for as many factors as your design requires - albeit with some performance limitations at s…

For sure! You've made two super important points; how can I trust it shuffling things under me and how can I justify trusting this thing if it's going in long-lead or production ha…

We hear you! We're most certainly planning on eating up the system's chain to describe, version control and validate up the system's chain. As one example in an earlier (and likely…

Thanks mate!

You're right. It definitely is currently. This is a hole we're planning to fill between linters and a language server. Picture a red-underline under an instance which is insufficie…

Thank you!! That's just about the workflow as where we lie today - albeit without the full suite of potency we're working towards. I haven't actually used Onshape, so I'm not intim…

We're largely on board with the same problem's we're trying to tackle, and I most certainly understand why you're making these criticisms of these trivial examples and our current …

Sorry, not quite sure what you’re asking. Mind rephrasing?

Super! So far that’s all we support for layout and we love that it’s also super-low-barrier to entry OSS.

You're absolutely right! We've been thinking very similar ways about "dipole" components and how to best do this; and I think you've nailed it. What about using dunder __in__ and _…

Definitely agree this isn't taking away EEs - anytime soon or ideally ever! The goal is to make EEs far more potent, rather than bring SWEs to hardware (although letting them easil…

We share similar thoughts about the core of the auto-routing/placement/simulation issues being UX! We're a bit more bullish on code being able to fix that as well. Noticing that th…

Great question! We hope we have a few good reasons. This iteration of the project actually came after first working with and then modifying another awesome project called SKiDL ( h…

We're also super stoked about getting topology and equations together in the same file (and even code-base!) The equation solver is soon on our roadmap: https://atopile.io/roadmap/…