开发者

I'm a builder. I taught myself to run servers because freelancers kept burning my money. West London, 2021. I was standing on a site holding a cup of tea that had gone cold an hour earlier, watching a crew argue about where a wall should go. That's my actual job. Schedules, suppliers, the kind of problems that only exist at 7am when half the crew hasn't shown up and the client is already phoning. But my head was somewhere else. I'd been chewing on an idea for a classifieds platform for months. Not a grand vision, nothing with a business plan and projections. Just a gap I could see — a way to connect buyers and sellers that felt easier and more global than what was out there. The problem was that I knew nothing about programming. And I mean nothing. I didn't know what a database was. I'd never written a line of code. My entire technical CV was "reasonably good at not breaking my own phone." So I did what most people in my position do. I tried to buy my way in. The expensive year I found a ready-made classifieds script online. Looked professional, had features, didn't cost the earth. The smart shortcut, I told myself. Then I hired a freelancer to customise it. Then another one, when the first disappeared mid-project. Then another, when the second delivered something that worked on a good day and fell over on a bad one. Here's the thing nobody warns you about hiring freelancers when you can't read code: you can't judge the work. You can't tell the difference between someone who wrote something clean and someone who duct-taped it together to last until the invoice clears. Both show you the same thing — a screen where the button does what the button's meant to do. So you pay, you say thanks, you move on. And three months later the button stops working and the freelancer's gone. Meanwhile the bots had found me. Within weeks of going live, automated scripts were hammering the contact form, then the registration page, then the login. "It's normal," a freelancer told me. "Ha

Microsoft is facing criticism for its handling of zero-day exploits. Someone going by the name Nightmare Eclipse has been publicly feuding with the company, posting proof-of-concept exploit code. Some of their posts suggest that they're a disgruntled former employee. But what caught cyber security researcher Kevin Beaumont's eye was how Microsoft has responded. Microsoft suggests […]

Inspired by a question on r/haskellquestions , i wrote about the practical aspect of monads for people at a beginner / intermediate level, about how to go beyond mere understanding the monad class. I try to highlight how we use monads to structure our code, what benefits they bring, and how to reason about them. it comes with exercises! submitted by /u/nicuveo [link] [留言]

I live in a part of Los Angeles where I feel safer bringing pepper spray on walks. The problem is, I don't always remember to bring it with me, and it's not legal to carry it everywhere I go. Pebblebee's $59.99 Halo Bluetooth tracker surprised me by being a suitable replacement because it doubles as […]

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

I'll keep this brief. Most of us can write great code. The harder part? Finding clients who actually pay well and don't ghost you after the first message. I struggled with that for a long time. Then a few weeks ago, something clicked - and the two platforms that changed everything for me were LinkedIn and Reddit. Here's why they work: 🔹 LinkedIn - Real people with real budgets post here. It's less about cold outreach and more about being present and visible. Set up your alerts, keep your profile sharp, and let opportunities come to you. Patience pays off. 🔹 Reddit - Underrated, honestly. Yes, the lead volume is lower, but the quality is surprisingly solid. People posting in relevant subreddits are often genuine and ready to hire. Bonus: no geo-restrictions, so you're playing in a global market from day one. The secret sauce? Be in the right subreddit at the right time. That's genuinely it. If you've been sleeping on either of these platforms, give them a real shot. You might be closer to consistent freelance work than you think. submitted by /u/theonlyaswin [link] [留言]

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] [留言]