site-for-developers
๐๐ ๊ฐ๋ฐ์๋ค์ ์ฒซ ๋ฒ์งธ ๋ถ๋งํฌ
Runssource: GitHubPythonMITcommit cac25bc2c1ad
Python, MIT licensed. The project labels itself: ai, ai developer tools, ai tools, artificial intelligence, awesome list, bookmark, chatgpt and curated list.
site-for-developers runs. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The static site builds from the canonical README (388 resources, 57 categories), all 49 unit and Playwright browser tests pass, both ko and en pages serve HTTP 200 at their project prefix with working 404 handling, and generated SVG/PNG assets decode correctly.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- System Python externally managed (PEP 668) blocked 'pip install playwright==1.58.0'3 minutes
- Playwright not installed so browser test modules (test_site_browser, test_locale_browser, test_static_seo) failed to import3 minutes
- 'playwright install chromium' reported exit code 2 with '/bin/sh: 1: Bad substitution' due to the container's login-shell profile2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- python3 scripts/build_site.py exit 0 (JSON output 388 resources, 57 categories); /tmp/sfd_venv/bin/python -m unittest discover -s tests -p 'test_*.py' ran 49 tests in 42.7s, OK, exit 0; curl -s -o /dev/null -w %{http_code} on served _site returned 200 for ko/en roots and resources.json, and 404 for a missing path; ffmpeg -v error -i _site/art/poster.png -f null - exited 0; live scripts/github_stats.py refreshed 1179 stars over the network without a token.
- Model tokens used
- 137,921
- Exact commit tested
- cac25bc2c1ad
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
app.js art en favicon.svg index.html logo.svg resources.json sitemap.xml poster size: -rw-rw-r-- 1 runner runner 57694 Oct 28 07:18 _site/art/poster.png tokens used 137,921
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 215 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 216 ai projects Argusic has installed and timed, site-for-developers was the 126th fastest to reach a running state, and 141 of 216 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
aiai-developer-toolsai-toolsartificial-intelligenceawesome-listbookmarkchatgptcurated-listcursordeveloper-resourcesdeveloperskoreanllmopen-sourcevibe-coding
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/site-for-developers)Questions
- Does site-for-developers run?
- Yes. site-for-developers runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test site-for-developers?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cac25bc2c1ad. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test site-for-developers?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does site-for-developers take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does site-for-developers need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing site-for-developers?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does site-for-developers compare with the alternatives?
- Of the 216 ai projects Argusic has installed and timed, site-for-developers was the 126th fastest to reach a running state, and 141 of 216 reached one at all.
- Where is the evidence for site-for-developers?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.