Posts with #Tests
#Tests
Public posts on X that use #Tests.





THIS IS F*CKING INSANE Anthropic turned Agent Skills into an open spec and GitHub filled up with ready-made Claude Code teams for free one of these repos alone ships 135 agents, 35 skills, 42 commands, 176+ plugins and 20 hooks. another hands you 100+ specialized subagents. none of it costs anything 10 GitHub projects you should open first: 01 wshobson/agents → a plugin marketplace that installs the same agents into Claude Code, Codex, Cursor and Copilot, so your setup survives switching tools 02 VoltAgent/awesome-claude-code-subagents → 100+ specialized subagents covering most of what a normal engineering week throws at you 03 rohitg00/awesome-claude-code-toolkit → 135 agents, 35 curated skills, 42 commands, 176+ plugins, 20 hooks and 14 MCP configs in one place 04 anthropics/skills → the official Agent Skills repo. start here to see the shape of a working SKILL.md before you copy anyone else's 05 netresearch/claude-code-marketplace → curated skills on an open standard, portable across Claude Code, Cursor, Copilot, Codex, Gemini CLI and 30+ other agents 06 disler/claude-code-hooks-mastery → the hooks reference. this is where you learn to make the agent stop on your rules instead of stopping to ask you 07 karanb192/claude-code-hooks → an installable hooks marketplace split into safety, cost, observability and productivity 08 affaan-m/claude-swarm → multi-agent orchestration that decomposes the task, coordinates the agents and shows the whole run in a terminal UI 09 am-will/swarms → orchestration shipped as skills, so the coordination loads only when the job actually calls for it 10 eugeniughelbur/obsidian-second-brain → persistent memory as plain markdown in an Obsidian vault, shared across Claude Code, Codex and six other agents give the first team a job with an obvious finish line: one reviewed PR, one researched brief, one failing test turned green then look at how much of that output you actually kept, and what it cost to produce. a bigger roster earns its place when it moves that number the download is free. paying four agents to repeat the same investigation is not save this before you spend another weekend building a config that already exists the article below shows how to keep context small, reuse finished work and contain retries, so more of your budget reaches the finished result ↓Hanako @hanakoxbt658671894.5K
50 websites that feel like the internet’s hidden toolbox 🧰 1. — Free research papers 2. — Borrow books online 3. — Free academic journals 4. — App alternatives 5. — Find where to stream 6. — Internet archives 7. — 70K+ free books 8. — Free textbooks 9. — Free courses 10. — Solve complex problems 11. — Photoshop alternative 12. — Compress images 13. — Remove backgrounds 14. — Remove objects 15. — Remove video backgrounds 16. — Beautiful code images 17. — Code screenshots 18. — Product mockups 19. — Create mockups 20. — Check data breaches 21. — Scan files & URLs 22. — Self-destructing notes 23. — Temporary email 24. — Temporary file sharing 25. — Save webpages 26. — Find similar websites 27. — Explore global radio 28. — Discover music genres 29. — Find songs from shows 30. — Focus music 31. — Custom background sounds 32. — Café ambience 33. — Research assistant 34. — Research-backed answers 35. — Research connections 36. — Academic search 37. — Understand research papers 38. — YouTube summaries 39. — AI for developers 40. — Test regex 41. — Format code 42. — Format JSON 43. — Understand terminal commands 44. — Bookmark manager 45. — Check outages 46. — Reverse image search 47. — Internet speed test 48. — PDF tools 49. — Merge/split PDFs 50. — Temporary email Save this. You’ll definitely need some of these later. 🔖 Follow @The_techAI for more useful websites, AI tools & tech resources.2926893543.3K

After cracking a woman, there are 2 MAJOR tests she will try on you. 99% of men fail the 2nd; only a few pass. The first test is:12651.3K247K
In the spirit of transparency and openness, we are releasing the traces so developers can test this out for themselves. We noticed this behaviour without prefilling with the following prompt, but this is rare. If you want to reproduce it, you can use this prompt with prefilling. Open models make for better science and are part of why this problem came to light at all: developers running Qwen3.8 on their own machines spotted the strange links, and having the weights let us study the behaviour in depth. We're encouraged by the thoughtful discussion our research has sparked across the AI and security communities. It's our belief that open-weight models are an important part of the future of AI, and we've recently released several under the Apache 2.0 license. Trace, raw tokens, & minimal reproduction script:clem 🤗 @ClementDelangue@cohere could you share the full traces? Very important artefact for all to understand this!1351391.3K256K
A man reheated and ate a baked potato left in foil on the counter overnight. The next day, paralysis spread from his face down his body. Soon, he couldn’t breathe. What went wrong?2564883.9K1.4M
@DocPriyamMDFoodborne botulism: A poisoning that can paralyse the muscles you need to breathe. Potatoes can carry spores of Clostridium botulinum from soil. These can survive baking. If a baked potato stays wrapped in foil at room temperature, the low-oxygen conditions can let bacteria grow and produce toxin. Once swallowed, this toxin blocks the release of acetylcholine: the chemical signal nerves use to make muscles move. Symptoms usually begin 12-36 hours later: double vision, drooping eyelids or trouble swallowing. Weakness can then spread down the body and reach the breathing muscles. The person can remain fully awake throughout. Brief, uneven reheating may not destroy the toxin. The toxin CAN be destroyed by sufficient heating; the spores are much harder to kill. Urgent antitoxin can prevent further paralysis, but doesn’t reverse paralysis already present. Some patients need a ventilator, and recovery can take weeks to months. Refrigerate cooked potatoes within 2 hours-1 hour in temperatures above 32°C/90°F with foil loosened or removed. If left out overnight, throw them away. Never taste-test.422652.1K164K
LukeWarmDesigns@LukeWarmDesignsJust a couple little tweaks and I think Ballot Box V2 is ready to test.LukeWarmDesigns @LukeWarmDesignsWe can just do things now. And when the baffles erode, you can just reprint them!431392.7K44.9K
LukeWarmDesigns@LukeWarmDesignsWe can just do things now. And when the baffles erode, you can just reprint them!183069959.3K
BREAKING NEWS: In a potentially serious security breach, Oregon's Secretary of State's office reportedly exposed an internal election-testing website to the public internet just days before the November 3rd election. According to reporting by YamCo News and @Oregonian, the website displayed simulated election results, including 59,331 ballots counted and 2.39% statewide turnout. The Secretary of State's office says these were test results, not actual votes. But here's the troubling part. According to The Oregonian, a system update caused the website to become accessible outside its protective firewall, allowing public search engines to discover information that was apparently intended only for internal election testing - not the public. Former state representative Julie Parrish (@hotcouponmama) reportedly discovered the exposure, and the state subsequently took the website offline. Here's where things get interesting. Oregon's Secretary of State explicitly assures voters that the state's ballot-counting equipment is NEVER connected to the internet, so that is a lie they have been telling the public for years. This particular website has been indexed by Google for 10 YEARS. Now, to be clear, a publicly accessible election-results testing website is not the same thing as internet-connected ballot-counting equipment. There is currently no evidence that the actual vote-tabulation machines were compromised. But the distinction raises an important question: If an election-related staging website could become publicly accessible because of a system update, what safeguards ensure that Oregon's actual ballot-counting equipment and production election systems remain completely isolated? Is this just an example of embarrassing incompetence from @ORSecretaryRead's office or something far more sinister? This raises several questions that Secretary of State Tobias Read should answer publicly: How did a system update inadvertently expose an internal election website? What security controls failed, and how long was the website publicly accessible? Was the staging environment completely isolated from production election systems? Was any unauthorized access detected? Has an independent cybersecurity assessment been conducted to determine whether other election-related systems were exposed? Tobias Read regularly repeats the mantra to voters that its elections are safe and secure. This proves this not the case. As the Trump Administration is ready to send election monitors ahead of the November 3rd election, Read will have some explaining to do. In many states, this might get the Secretary of State immediately fired. Then Read could say goodbye to his future political aspirations, including the governorship. Yet here we have an election-related website that reportedly became accessible to the public because of a configuration error, just days before an election. Oregonians deserve more than Read's assurances that the exposed information was harmless. They deserve documentation establishing what happened, what systems were affected, and what corrective measures have been taken. Secretary of State Tobias Read should address this incident publicly and provide the evidence supporting his office's conclusions. Election integrity requires verifiable safeguards, transparency, and accountability, not empty platitudes.914001.1K34.9K
Learn Python. ⠀ Learn JavaScript. ⠀ Learn React. ⠀ Learn Docker. ⠀ Learn AWS. ⠀ Learn Kubernetes. ⠀ Finally, you start feeling confident. ⠀ Then someone says, “I built the whole app with a prompt.” ⠀ Welcome to being a developer. ⠀ After 16+ years in engineering, I understand why this feels exhausting. Every time you get comfortable, the industry gives you more homework. ⠀ But I’d redraw the last part of this curve. ⠀ Your engineering knowledge still matters when you have to explain why: ⠀ • The app works locally but fails in production. ⠀ • One database query takes down the API. ⠀ • A retry charges the customer twice. ⠀ • An AI-generated endpoint lets users access someone else’s data. ⠀ Knowing how to investigate those problems takes experience. Every layer you learned gives you somewhere to start. ⠀ That knowledge helps while you’re prompting, too. ⠀ You can spot a missing requirement, question a design choice, and catch a dangerous assumption before it spreads across twenty files. ⠀ I want AI to handle more of the repetitive work. I also want to understand what I’m putting into production. ⠀ If you’re feeling behind, try this: ⠀ Take one small feature you already know how to build. Ask an AI coding tool to implement it. Then review the result like a teammate’s pull request. ⠀ 1. Read the diff. ⠀ 2. Check the dependencies. ⠀ 3. Test the failure cases. ⠀ 4. Find something you would change and explain why. ⠀ You’ll learn the tool while exercising the judgment you’ve spent years developing. ⠀ And if you’re just starting, follow the generated code all the way through: from the button, to the API, to the database, and back. ⠀ You don’t have to restart your career every time the tools change. ⠀ You do have to keep learning. That part of the picture has always been accurate. ⠀ Which skill on this chart took you the longest to learn?3614791864.8K
retarded billa@24X7shitposterhow it feels studying for a test im going to fail either way373K13.6K110K

- Show more posts



