professional-programming
A collection of learning resources for curious software engineers
Could not verifysource: GitHubPythonMITcommit c48230149511
Python, MIT licensed. The project labels itself: architecture, computer science, concepts, documentation, engineer, learning, lessons learned and professional.
Argusic could not get professional-programming running. An Argusic agent installed it in 5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pre-commit installed in /tmp/repo-venv and all 5 hooks pass against the repo's tracked files
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 50 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.
- pre-commit hook 'black' (rev 19.3b0) failed with ImportError: cannot import name '_unicodefun' from 'click'2 minutes
- pre-commit hook 'doctoc' (v1.4.0) failed with ENOENT on file with spaces in name2 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pre-commit run --all-files exited 0, 5 hooks passed (check-yaml, end-of-file-fixer, trailing-whitespace, black, doctoc)
- Model tokens used
- 100,439
- Exact commit tested
- c48230149511
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
.pre-commit-config.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) exec /bin/sh -lc 'cd /work/repo && /tmp/repo-venv/bin/pre-commit run --all-files 2>&1' in /work/repo succeeded in 1596ms: check yaml...............................................................Passed fix end of files.........................................................Passed trim trailing whitespace.................................................Passed black....................................................................Passed doctoc...................................................................Passed tokens used 100,439
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
- Installed in 5 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.05 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.03 |
Topics (from GitHub)
architecturecomputer-scienceconceptsdocumentationengineerlearninglessons-learnedprofessionalprogrammerprogramming-languageread-articlesscalabilitysoftware-engineering
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/professional-programming)Questions
- Does professional-programming run?
- Argusic could not verify that professional-programming runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test professional-programming?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c48230149511. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test professional-programming?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does professional-programming take to install?
- 5 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 professional-programming need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing professional-programming?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for professional-programming?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.