开发者

Live app: https://layoffs.kadoa.com Data and code are open source: https://github.com/kadoa-org/layoffs-tracker The federal WARN Act requires employers with 100+ workers to give 60 days notice before mass layoffs or plant closings (different thresholds by state, but roughly 50+ jobs lost). But the notices are scattered across 50 state websites, each with its own format, broken links, and no API. I think this should be transparent and easy-to-access public data, so I built an open-source aggregator for it. submitted by /u/madredditscientist [link] [留言]

submitted by /u/rebane2001 [link] [留言]

I've been putting off getting deeper into web design for a long time. Not because I wasn't interested, but because I kept telling myself I'd do it properly "at some point". At some point eventually arrived, and this is what came out of it. The motivation was simple: I couldn't find a task manager that just lived in my browser tab without requiring an account, an extension, a subscription, or a whole app install. I wanted something minimal, fast, and always there. So I built it myself. What it is: Vanta is a single HTML file Open it in your browser, bookmark it, done. It has: - Three themes (Focus, Minimal, Paper) - Drag-and-drop reordering - Separators to group tasks visually - Named profiles to save and switch between different lists - Full undo/redo (Ctrl+Z / Ctrl+Y) - JSON import/export - Keyboard shortcuts throughout - Everything persisted in localStorage I deliberately kept it as one file. I didn't really see a reason to split it - it's not a framework project, it's a tool I open in a tab. That was a conscious choice, though I'm curious if others would have approached that differently. https://github.com/Ventexx/vanta-Checklist What I'm actually after: Functionally, I'm happy with it. It does what I needed it to do. What I'm less confident about is everything else. I have always had a complicated relationship with web design. I've made projects that touched on it, but I've never built something I was genuinely visually pleased with at the end. Vanta comes closer than anything I've done before, but I still feel like I'm missing something beyond this - if I want to keep going down the path of building things that are actually aesthetically considered, I don't think I'm quite there yet in how I approach it, and I'm not sure where to look next. So if you have thoughts on where to go from here - what to learn, what I've approached wrong, or just what you'd improve in the app itself - I'd genuinely appreciate hearing it. This is the kind of thing I usually don't have

Ps. Not pitching anything; Just trying to understand where reality differs from the narrative We're a couple of ML students, mostly worked on ML/software before, but over the last few months we've been playing with VLAs, robot datasets, and trying to understand where the field is heading. After spending a few weeks downloading robotics datasets, we were surprised by how much effort went into just getting data into a usable format. Maybe we're missing something, but it felt like every dataset had different assumptions, schemas, sensors, coordinate frames, metadata standards, and tooling. That got us wondering: How do robotics teams actually think about data sharing? Do people genuinely want access to more robot data, or is the industry moving toward "collect your own data because nobody else's transfers"? Our current (possibly very wrong) hypothesis is: The robotics ecosystem doesn't have a data scarcity problem. It has a data interoperability problem. We're considering running a pretty large experiment: Take essentially every public robot-learning dataset we can get our hands on, normalize it into a common schema, enrich it with metadata, and see how much of it is actually reusable across tasks, embodiments, and learning pipelines. Before we spend months doing that, we'd love to hear from people actually building in robotics. Where is this hypothesis wrong? Is finding data not actually a problem? Is embodiment mismatch the real blocker? Is quality the issue? Is labeling the issue? Is everyone just collecting their own data anyway? Would you ever use robot data collected by another team? If I gave you access tomorrow to every public robotics dataset through one API, what would you actually do with it? Or would you ignore it completely? ------------------------------------------------------------------------------------------------------ Edit: One clarification We're not thinking about a marketplace, proprietary format, or closed platform. The experiment we're conside

I haven't seen anything as stupid as the WeWork IPO document in a very long time - that is, until Elon Musk filed to take SpaceX public. WeWork was a joke. SpaceX is a threat. And if Musk and his bankers have their way, you are going to be their bagholder. Lots of the top-line […]

submitted by /u/der_gopher [link] [留言]

Hey everyone. I have created a fully free PDF editor that doesn't require accounts. The files stay on your device, they are not uploaded anywhere. I have tried to add as many features as I could think. I hope someone will find it useful. Let me know what you think about it! The website is http://katanapdf.com submitted by /u/Standard_Ad_6045 [link] [留言]

A few weeks ago I posted about building a desktop app that automates GitHub commits because...

Finally got around making an portfolio site how is it ? (dev) submitted by /u/Miserable_Advice1986 [link] [留言]

I've been working on a side project called WEBDEVPACK - a collection of free web-based tools for developers, designers, and generally anyone working online. The idea is simple: lightweight tools that help us solve everyday problems. Check it out at webdevpack.com submitted by /u/ivopetkov [link] [留言]

This is a submission for the Hermes Agent Challenge: Write About Hermes Agent Hermes Agent...