Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Wow, I found a smart way to bookmark code! 🤯 🔖 codemark — Structural bookmarks that survive refactors, renames & reformatting. 🌳 Capture the semantic structure of what you marked via tree-sitter 🐀 Includes a TUI for exploring the codebase! 🦀 Written in Rust & built with Ratatui ⭐...

11,048 Aufrufe • vor 18 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

I found 7 free Polymarket trading bots on GitHub for 7 different trading situations… Each of these repos comes with a detailed step by step setup and usage guide in English. > Beginner Friendly (3-5 min setup) 1. A bot with 118 ready to use trading strategies and tools for prediction markets (Binance-Polymarket latency, Penny Clipper, Smart Routing, DCA bots, Momentum and more). It was built by a computer science student who later won a hackathon with this bot. You can also see this bot in action in the video below. GitHub: 2. This is a huge trading bot-toolkit that includes Polymarket-Kalshi arbitrage, copy trading, whale tracking, sports trading, spread farming and more. GitHub: 3. A Smart Money trading bot that finds top traders in selected markets, filters them by PNL, win rate and consistency to create a list for automated copy trading. GitHub: 4. A weather bot that analyzes multiple sources in real time, like weather forecasts, airport data and aviation observations (METAR + SPECI), to get the latest temperature data and generate a detailed weather report for a specific city and day. GitHub: 5. A large collection of 30+ free trading dashboards and services for different prediction market platforms. GitHub: > Advanced Bots 1. This bot analyzes the real trading behavior of any Polymarket trader. It finds repeated patterns, identifies the strategies he uses and shows how you can adapt them to your own trading. GitHub: 2. A bot that automatically manages all your Polymarket limit orders to maximize liquidity rewards. GitHub: All of these bots also support Dry Run mode (paper trading), so you can test them on real markets but without risking any funds.

Recogard

41,374 Aufrufe • vor 15 Tagen

When I was in high school (20 years ago! 🤯), a song that really resonated with me while I was sitting alone on the bus was “The Middle” by Jimmy Eat World. A part of me loved it as a pop punk banger. And a part of me resented it for the lies it told. “Hey, don’t write yourself off yet. It’s just in your head you feel left out Or looked down on.” Screw you, Mr. Eat World! You don’t know me! I didn’t really find that community in high school—there were amazing humans, but I wasn’t comfortable enough with myself to connect genuinely with anything but sports. In football, I could play a confident main character. “Just do your best. Do everything you can.” I tried in college. But going to New York City from the country was hard. I was making my way solo—A lone wolf that felt rejected by the pack, but maybe just didn’t try hard enough to find a pack in the first place. Then I found running. And in running, I found a group of people who wanted to wake up at the butt-crack of dawn to do things that often hurt. People who shared a strange obsession that required a wild amount of grit. People who showed up and embraced the silliness of it all. People who often felt strange and accepted others who felt the same way. I love the people in this sport. I wish I could show younger me this video of a finish line kiss, celebrating with a ton of fellow runners. That whole time growing up, I was just in the middle of the ride, thinking my story was already written. If you are out there feeling like that, as Jimmy said, know that everything will be alright, alright. Running, at its core, is about love and acceptance for everyone, especially people who feel different. Through running, I found my people. I found my person. I wish I could go back in time and tell 16-year old me what I’m telling you now: You will too 🧡

David Roche

15,128 Aufrufe • vor 1 Jahr

Karpathy's Agentic Engineering finally has proper tooling! (built by Google) Karpathy defined agentic engineering as the discipline that separates production agent work from vibe coding. The core skills he listed were spec design, eval loops, and security oversight. The problem has been that practicing this still requires a different tool for every phase: - editor for code - a terminal for scaffolding - a browser for testing - a cloud console for deployment - and a separate framework for evals. Every transition is a context switch. The solution to production-grade Agentic Engineering is now actually implemented in Google’s Agents CLI. It covers the entire workflow in one place for scaffolding, evaluating, and deploying ADK agents. One setup command injects 7 ADK-specific skills into a coding agent's context, which lets it handle scaffolding, evals, deployment, and enterprise registration through natural language. I tested this end-to-end by building a RAG agent from scratch using Claude Code. It scaffolded the full project from the ADK agentic_rag template, generated 20 eval scenarios with LLM-as-judge scoring, and returned a quantitative scorecard. Finally, it also deployed everything to Agent Runtime and registered the agent to Gemini Enterprise, so the entire org can discover and use it. The video below shows this in action, and I worked with the Google Cloud team to put this together. Agents CLI GitHub repo → (don't forget to star it ⭐ ) I wrote up the full build covering all six steps from install to enterprise registration. It includes the eval scorecard, the instruction loophole the eval caught before deployment, and what the deployment process actually looks like end-to-end. Read it below.

Akshay 🚀

257,053 Aufrufe • vor 1 Monat

i'm not fine after reading this a guy with a laptop got his own silicon chip manufactured with software Google gave away. the commercial version of that software rents for up to $1,000,000 a year. he never signed a vendor contract and never paid for a seat. he wrote the logic, pushed it to GitHub, and nine months later a wafer came out of a fab. getting silicon with your name in it used to take a company. now it takes nine months. his slot was 160 by 100 microns: about 1,000 logic gates, 8 inputs, 8 outputs, clocked past 50 MHz. more than 600 designs have already come back this way. this is the open silicon stack. Google and SkyWater published a complete 130nm manufacturing process, DARPA funded the software that turns code into a fab-ready file, and all of it sits in public repositories. turns out the whole flow fits in a git push: - write the logic in Verilog, or drag gates around in a browser if you have never done this - push to GitHub, an action runs synthesis, placement, routing and sign-off on the commit - OpenROAD finishes place-and-route with no human in the loop, code to fab file inside 24 hours - SKY130 carries the fab's real design rules, so passing the checks means it is manufacturable - a few hundred designs share one wafer, which is the only reason a person can afford the masks nobody puts this part in the thread: 130nm is roughly where the industry stood in 2001, and you wait six to nine months for silicon. this does not get you a GPU. it gets you a real object with your logic inside it. bookmark this. the video is one of those designs opened layer by layer, and every rectangle in it exists in the file that was sent to the fab.

Argona

147,264 Aufrufe • vor 5 Tagen

Another WTF moment. A developer just open-sourced a coding agent harness that boots 245x faster than Claude Code. It's called jcode. You launch it and the first frame renders in 14 milliseconds. Claude Code takes 3,436. One active session uses 27.8 MB of RAM. Claude Code uses 386.6. Run ten sessions in parallel and jcode holds at 117 MB while OpenCode swells to 3.2 GB. Each agent has a semantic memory graph instead of a scratchpad. Every turn gets embedded as a vector. The graph is queried on every turn for related memories, and a sideagent verifies the hits before injecting them into context. Consolidation runs in the background to check for stale or conflicting facts. No manual /remember calls. No token burn on lookup tools. The provider list is 30+ deep. Claude, ChatGPT, Gemini, GitHub Copilot, Azure, OpenRouter, DeepSeek, Groq, Mistral, Perplexity, Fireworks, Ollama, LM Studio, and any OpenAI-compatible endpoint you point it at. Ran out of tokens on your first ChatGPT Pro sub? /account swaps to the second. Then there's Swarm. Spawn two agents in the same repo and the server manages them. When agent A edits a file agent B has been reading, agent B gets pinged and can check the diff. Agents can DM each other, broadcast to the room, or spawn their own worker teams for parallel tasks. Groups, channels, and completion statuses are handled automatically. The UI has live side panels that render mermaid diagrams inline. To make it fast, the author wrote a Rust mermaid renderer 1800x faster than the JavaScript one, then wrote a custom terminal called Handterm because no existing terminal could do smooth partial-line scrolling. Self-dev mode is where it gets wild. Tell your agent to enter self-dev and it starts editing jcode's own source code, rebuilds the binary, reloads it live, and keeps working across your existing sessions. You can also resume broken sessions from Claude Code, Codex, OpenCode, or pi directly inside jcode. Anthropic's cache goes cold at the 5-minute mark and you're staring down a big cache miss on your next turn? The UI warns you before you spend the tokens. Written in Rust. MIT licensed. Runs on macOS, Windows, Linux, and Termux. Sitting at 11.2k stars with a native iOS app coming.

Brady Long

203,163 Aufrufe • vor 9 Tagen

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

12,729 Aufrufe • vor 2 Monaten

Big moment for Postgres! Search has always been Postgres' weak spot, and everyone just accepted it. If you needed a real relevance-ranked keyword search, the default answer was to spin up Elasticsearch or add Algolia and deal with the data sync headaches forever. The problem isn't that Postgres can't do text search. It can. But the built-in `ts_rank` function uses a basic term frequency algorithm that doesn't come close to what modern search engines deliver. So teams end up: - Running a separate Elasticsearch cluster just for search - Building sync pipelines that inevitably drift out of consistency - Paying for managed search services that charge per query - Accepting mediocre search relevance because "good enough" ships faster But this is actually a solvable problem. You can realistically bring industry-standard search ranking directly into Postgres, which eliminates the need for external infra entirely. This exact solution is now available with the newly open-sourced pg_textsearch by Tiger Data - Creators of TimescaleDB, a Postgres extension that brings true BM25 relevance ranking into the database. BM25 is the algorithm behind Elasticsearch, Lucene, and most modern search engines. Now it runs natively in Postgres. Here's what pg_textsearch enables: - True BM25 ranking with configurable parameters (the same algorithm powering production search systems) - Simple SQL syntax: `ORDER BY content 'search terms'` - Works with Postgres text search configurations for multiple languages - Pairs naturally with pgvector for hybrid keyword + semantic search That last point matters a lot for RAG apps. The video below shows this in action, and I worked with the team to put this together. You can now do hybrid retrieval (combining keyword matching with vector similarity) in a single database, without stitching together multiple systems. The syntax is clean enough that you can add relevance-ranked search to existing queries in minutes. pg_textsearch is fully open-source under the PostgreSQL license. You can find a link to their GitHub repo in the next tweet.

Akshay 🚀

215,344 Aufrufe • vor 6 Monaten

Alhamdulilah. Now this is what we call a huge web3 did What a wonderful journey it has been. Almost done with my first house. And honestly, it doesn’t feel like just a structure being completed… it feels like a reflection of everything that came before it. time, discipline, mistakes, exposure all quietly compounding. › 2023 The Beginning It started with no real direction. I was grinding, exploring, trying things without fully understanding where it all leads. There was no structure yet… just curiosity, repetition, and a lot of learning through trial and error. I was simply moving, even when I didn’t fully know what I was moving toward. › 2024 Things Start to Form Then things began to shift. Not overnight but gradually, through exposure and experience. I entered deeper into the space and connected with OGs in the TON ecosystem And slowly, one important lesson became clear: it’s not just effort that matters… it’s information, timing, and the people you learn from. › So I also started trading as well Trading became a major part of my learning curve. Forex & Perps showed me risk in its raw form mehnn 🙂‍↔️ taught me discipline and patience. Memecoins show me shege rugs up and down Along the way, I learned from different people PMO, not just strategies, but perspectives. Each one added something I didn’t have before. › Late 2024 Structure Appears Then came a different phase. I signed my first structured deal with sign a monthly arrangement that brought a new level of stability into my journey. For the first time, things were not just random wins and losses… there was structure, expectation, and consistency. Then came the TGE. Execution was clean. The ecosystem moved properly. And as early participants, we experienced meaningful upside not just financially, but in understanding how systems actually work when they’re built well. › Now The Reflection Almost done with something physical. But the deeper truth is this: the house is just the surface. what actually got built was the person. through risk, through losses, through discipline, through time. This is not a story about outcomes. It is a story about becoming. And I am still becoming. Grateful for the journey so far. Still building.

Tajudeen ♟️

37,936 Aufrufe • vor 3 Monaten

Introducing a new tool called "SideChannel". A secure alternative to OpenClaw. Utilizes signal for communication and has Claude integration. I built SideChannel, an open-source Signal bot that connects Claude AI to your entire development workflow. End-to-end encrypted. From your pocket. The real power is autonomous development. Send one message like "Build a REST API with auth, pagination, and tests" and SideChannel will: - Generate a full PRD with stories and atomic tasks. - Dispatch up to 10 parallel workers (each running Claude). - Independently verify every task with a separate Claude context. - Run quality gates to catch regressions - Auto-fix failures. - Send you progress updates via Signal as work completes. Every piece of code is reviewed by a separate AI context using a fail-closed security model. If it detects security issues, backdoors, or logic errors — the code gets rejected automatically. No rubber stamps. It also has memory that actually works. Conversations are stored with vector embeddings for semantic search. Claude remembers your project conventions, past decisions, and what's been tried before. It gets smarter about your codebase over time. Other things I'm proud of: - Plugin framework for extending with custom commands. - Multi-project support with per-user scoping. - Rate limiting, path validation, phone allowlist. - Git checkpoints before every task, atomic commits after. - Stale task recovery, circular dependency detection. - Works on Linux and macOS, one-command install. It also integrates into OpenAI or Grok (optional) for more Generative AI response for simple things like "Whats the weather in New York City right now?".

Dave Kennedy

49,427 Aufrufe • vor 5 Monaten

I just built a Claude Code skill that scores whether your landing page actually keeps your Meta ad's promise 🤯 Drop in your ad and the page it points to. It reads both, scores the "ad scent" from click to page, and finds the exact line where the page breaks the promise that won the click. All inside Claude Code. Perfect for DTC brands and media buyers who pour everything into the ad and the CPA but never grade the seam in between. If you're scaling spend on a winning ad, the click is landing on a page that opens with something slightly different, the ad promised 50% off and the page shows full price, the ad hooked "for oily skin" and the page is a generic homepage, and nothing looks broken, but the visitor feels it and bounces... That gap has a name in conversion work: message match. And you already paid for the click you're losing. Here's what it does: → Drop in your ad (headline, copy, offer, CTA) and the landing-page URL → It fetches the live page and reads what's actually above the fold → Grades 7 continuity dimensions: promise, offer, angle, CTA, audience, proof, visual → Shows your ad's words next to your page's words, so every gap is right there → Rewrites your hero headline so the page keeps the ad's promise → Renders a dashboard with a Match Score out of 100 No guessing why the click bounced. No blaming the creative for a page problem. No buying more traffic to fix a copy problem. What you get: → A Match Score on every ad-to-page pair before you scale → The ad-side vs page-side quotes, side by side, for every leak → A hero rewrite you can paste straight onto the page → A dashboard you can hand to your team or client I'm giving away the full skill completely for free. Built 100% in Claude Code. No API keys. Want the skill? > Like this post > Comment "MATCH" And I'll send it over (must be following so I can DM)

Mike Futia

10,548 Aufrufe • vor 21 Tagen