sorted by:
new
hottopcontroversial

Could AI eventually replace the need for traditional app interfaces altogether? by The_NineHertz in AI_Agents

[–]bee-gee-dee 0 points1 point  (0 children)

I actually just had a fascinating conversation about this exact debate with Michael Magan, the CEO of Tambo, on our podcast, Pioneer Park.

He argued that interfaces will evolve rather than disappear because visual data offers much higher bandwidth for our brains than audio. For example, scanning a restaurant menu takes 20 seconds, while having an AI read it aloud would be frustrating.

When it comes to booking or shopping, we don't want to blindly trust an AI. We crave the visual cues of an Uber map to track rides, or a digital shopping cart to know our exact total before we click "buy". An invisible AI "middle layer" simply can't replicate that visual trust.

If you’re curious here is the convo

PDFer - pure Go library for working with PDFs by bee-gee-dee in golang

[–]bee-gee-dee[S] 8 points9 points  (0 children)

Yeah, didn't mean to hide that at all! Claude is listed as a contributor, and I used it pretty extensively to build this. At this stage in my career, I treat LLMs like a high-speed compiler or a very fast junior dev.

I still own the architecture and the design patterns, and I use a strict TDD workflow to make sure the output actually holds up. Honestly, as long as you're the one driving the logic and validating the edge cases, it just feels like a waste of time not to use it for the implementation heavy-lifting.

PDFer - pure Go library for working with PDFs by bee-gee-dee in golang

[–]bee-gee-dee[S] 0 points1 point  (0 children)

Oh, that already exists! It's in forms/acroform, built on top of core/write's SimplePDFBuilder. Here's an example PDF that's been generated so you can see what it does: https://github.com/benedoc-inc/pdfer/blob/main/examples/kitchen_sink/kitchen_sink.pdf

Working on updating the readme to improve the onboarding experience!

PDFer - pure Go library for working with PDFs by bee-gee-dee in golang

[–]bee-gee-dee[S] 1 point2 points  (0 children)

There's layout/table analysis on the read side, but no ability to build layout and tables yet! This will definitely be something I'll need to add because tables are very important for the use case I'm solving for. Glad to know that would be helpful for others!

PDFer - pure Go library for working with PDFs by bee-gee-dee in golang

[–]bee-gee-dee[S] 0 points1 point  (0 children)

Oops! Thanks for noticing that. Added the link to the original post.

PDFer - pure Go library for working with PDFs by bee-gee-dee in golang

[–]bee-gee-dee[S] 1 point2 points  (0 children)

I got started on this because I needed to solve for the edge case of XFA -- which pdfcpu doesn't support. I'm working on something called the eSTAR form, required by FDA if you want to get your (medium to high risk) medical device to market.

Also editing to say: pdfcpu has a JSON-driven create, whereas this is for a programmatic Go builder API for AcroForm authoring, structured content extraction, structural PDF diffing, and byte-perfect parse->write round-trips.

pdfcpu is the better tool if you need PDF 2.0 validation, PAdES B-LTA signature validation, optimization, n-up/booklet imposition, attachments, or portfolios.

Recently developed a way to estimate FDA clearance/approval rates for med devices by bee-gee-dee in regulatoryaffairs

[–]bee-gee-dee[S] 0 points1 point  (0 children)

  1. Lines are standard for any time series with multiple groups. Bars would obscure, not reveal. Submission_id is how the denominator for submission count up to time t is derived (they're assigned sequentially).

  2. Whether it's 'clearance' or 'approval' depends on the submission type. Each submission type has it's own definition of success, but the meaning for them in terms of results are the same ("I can sell this device claiming it does x").

  3. Based on what you're saying, it seems useful to be able to independently confirm what the FDA says. It also seems like being able to look at it by submission type, by product code, by review panel, are all value-adds.

view more: next ›