Digitable · Data
Portal statistics
How much is here
- Articles
- 1,167
- Narrated end to end
- 70 of 1,167
- Hours of audio
- 23
Counted by the portal build from the repository: narrated end to end means audio on every paragraph, the hours are their durations summed and rounded down.
How many come here
- Views in 7 days
- —
- Visitors in 7 days
- —
- Views all time
- —
- Visitors all time
- —
Taken by the hourly pass over the web server logs, analytics/activity.json; bot requests are dropped by user agent.
How much of it is read
- Views
- —
- Articles with any views
- —
- Read-depth observations
- —
- Week over week
- —
- Mean share of text read
- —
- Reached the end of the text
- —
- Most often abandoned
- —
Taken by the backend counter, api/analytics. It is not the counter behind the visits above: there is no way to add the two up.
Read most often
- —
- —
- —
Data not loaded.
Corpus map
A row is a catalogue stage, a cell is a track: the number and the colour are hours of reading in it.
01
First steps
2 h
0.3How to learn · chapters: 16 · 0.3 h of reading
0.3Higher education as a research programme · chapters: 18 · 0.3 h of reading
0.3Mnemonics: memory built on images · chapters: 16 · 0.3 h of reading
0.2How to find information · chapters: 14 · 0.2 h of reading
0.3Programming from scratch · chapters: 16 · 0.3 h of reading
0.3Computer Science basics · chapters: 18 · 0.3 h of reading
0.3How software gets made, and careers · chapters: 20 · 0.3 h of reading
0.3Time management for engineers · chapters: 16 · 0.3 h of reading
02
Foundations
7 h
0.3Hardware and architectures · chapters: 16 · 0.3 h of reading
0.3Systems thinking · chapters: 16 · 0.3 h of reading
0.3Mathematics for programmers · chapters: 18 · 0.3 h of reading
4.6Logic and fallacies · chapters: 15 · 4.6 h of reading
0.2Data structures · chapters: 15 · 0.2 h of reading
0.3Algorithms · chapters: 19 · 0.3 h of reading
0.3Operating systems · chapters: 20 · 0.3 h of reading
0.2Development paradigms · chapters: 14 · 0.2 h of reading
0.2Development principles · chapters: 14 · 0.2 h of reading
0.2Church's lambda calculus · chapters: 14 · 0.2 h of reading
03
Languages and paradigms
6 h
0.2Go · chapters: 14 · 0.2 h of reading
0.2Elixir · chapters: 14 · 0.2 h of reading
0.2TypeScript · chapters: 14 · 0.2 h of reading
3.9Executable specifications in flang · chapters: 23 · 3.9 h of reading
0.2flang — a language with provable termination · chapters: 15 · 0.2 h of reading
0.2C# / .NET · chapters: 14 · 0.2 h of reading
0.3Python · chapters: 18 · 0.3 h of reading
0.3Java · chapters: 16 · 0.3 h of reading
0.2Rust · chapters: 14 · 0.2 h of reading
0.2Systems programming in C · chapters: 14 · 0.2 h of reading
0.3Functional programming · chapters: 17 · 0.3 h of reading
0.3Frontend development · chapters: 18 · 0.3 h of reading
0.2Mobile development · chapters: 15 · 0.2 h of reading
04
Designing systems
1 h
0.2Design patterns · chapters: 14 · 0.2 h of reading
0.2Architecture patterns · chapters: 15 · 0.2 h of reading
0.2Domain-Driven Design · chapters: 14 · 0.2 h of reading
0.2Distributed systems · chapters: 14 · 0.2 h of reading
0.2Compilers and languages · chapters: 14 · 0.2 h of reading
05
Data, ML and AI
2 h
0.3AI for engineers: the basics · chapters: 16 · 0.3 h of reading
0.3Engineering with AI agents · chapters: 16 · 0.3 h of reading
0.2Data Engineering and ETL · chapters: 14 · 0.2 h of reading
0.3Databases · chapters: 20 · 0.3 h of reading
0.2Data analytics · chapters: 15 · 0.2 h of reading
0.3Machine learning · chapters: 16 · 0.3 h of reading
0.2Neural networks · chapters: 14 · 0.2 h of reading
0.3AI agents and prompt engineering · chapters: 17 · 0.3 h of reading
0.3SBSE and search algorithms · chapters: 19 · 0.3 h of reading
0.2Web3 and blockchain · chapters: 14 · 0.2 h of reading
06
Infrastructure, tooling and quality
3 h
0.3SRE and reliability · chapters: 16 · 0.3 h of reading
0.3Platform engineering · chapters: 16 · 0.3 h of reading
0.3CI/CD, infrastructure and clouds · chapters: 18 · 0.3 h of reading
0.3Software testing · chapters: 16 · 0.3 h of reading
0.1Ouroboros: recording the calls of a running program · chapters: 7 · 0.1 h of reading
0.2Technical writing · chapters: 14 · 0.2 h of reading
0.2Engineering English · chapters: 14 · 0.2 h of reading
0.2Editors and IDEs · chapters: 14 · 0.2 h of reading
0.23D assets through an agent · chapters: 14 · 0.2 h of reading
0.2Computer networks · chapters: 14 · 0.2 h of reading
0.3Application security · chapters: 16 · 0.3 h of reading
0.2Systems performance · chapters: 15 · 0.2 h of reading
0.2Git and teamwork · chapters: 14 · 0.2 h of reading
0.2Accessibility (a11y) · chapters: 14 · 0.2 h of reading
0.2Embedded systems and robotics · chapters: 14 · 0.2 h of reading
0.2Engineering practice · chapters: 14 · 0.2 h of reading
07
Product, process and people
2 h
0.3Team lead and engineering leadership · chapters: 17 · 0.3 h of reading
0.2Product Management · chapters: 14 · 0.2 h of reading
0.2Project Management · chapters: 15 · 0.2 h of reading
0.2Scrum master (PSM I) · chapters: 14 · 0.2 h of reading
0.2Systems and business analysis · chapters: 14 · 0.2 h of reading
0.2UX and interface design · chapters: 14 · 0.2 h of reading
0.2Shipping software · chapters: 14 · 0.2 h of reading
0.2Business for engineers · chapters: 14 · 0.2 h of reading
0.2Management: core materials · chapters: 14 · 0.2 h of reading
Hours of reading per track: under 2 2 to 4 4 to 5 5 to 6 6 to 7 7 and more
The map holds 71 catalogue tracks and 1,093 articles out of 1,167; the other 74 are the blog, theses and examples, not track chapters. The hours sum the reading estimates of THIS edition, so the English map shows the size of the translation rather than the size of the corpus.
What gets read
| Article | Reads out of views | Mean share of text read | Last opened |
|---|
Data not loaded.
How it is counted
A view is a page that was opened; a read is a visit whose exit beacon arrived. The unit behind both is a visit, not a person.
The reporting threshold
A mean or a share is printed from 20 observations per article, the abandonment point from 30. Below the threshold you get the count of observations.
An estimate from browser and network signals: one person may be counted several times, several people once. «All time» runs from the first record in the logs. Updated .
What this method cannot tell you
- Exact MAU and number of people
- Unknown. There is only a visitor estimate from browser and network signals: it is computed in memory, while the signals and their hashes are not written to public data.
- Whether a person read or scrolled
- Unknown. What is measured is the scroll position reached: someone who scrolled quickly to the end looks exactly like someone who read it.
- How long they read
- Deliberately not counted: depth answers «do they read it through», while time is ruined by a single tab left open overnight.
- Readers without JavaScript
- Invisible in reads and in views alike: the beacon runs as a script. The same holds for
DNT: 1— the refusal to be tracked is honoured on the server. - Those who looked away and came back to finish
- Counted with a downward bias: the beacon leaves on the first time the page is hidden, and a second one would count the read twice. The summary errs towards «they read worse».
Where readers stop, per article and per tenth of the text: the reading summary.