Digital Technology Atlas: turn curiosity into a first project

What is inside

• 54 pages in the complete English PDF, ready to save and read offline.
• 27 sections spanning platforms, languages, web development, data, design, security and business.
• 678 catalogue entries covering fields, software projects, tools and resource collections.
• Six stages of the VITON13 protocol: goal, exploration, practice, project, verification and artifact.
• Three levels of work: START, BUILD and MASTER, from a first example to comparing solutions.

Why a map of technology matters

With hundreds of names competing for attention, it is difficult to separate your own goal from someone else’s agenda. You can spend hours comparing tools without writing your first program. The atlas starts with a more useful question: what do you want to build, understand or improve? A product page, an analysis of a spreadsheet and an interactive prototype each call for a different learning route.

The book provides a view of the digital landscape and then directs attention back to practice. At the beginning, that means seeing neighbouring fields before selecting one to study more deeply. A catalogue can reveal possible paths, but the reader still chooses which path serves the task. Save a resource alongside the question it is meant to answer; this makes it easier to use the collection when you return.

What 678 entries and 27 sections actually mean

The number 678 counts entries in the book’s catalogue. They include languages, platforms, software projects, areas of study and themed collections. These are not 678 separate courses. The sections cover front-end and back-end development, computer science, big data, databases, games, hardware, media, networks, testing, business and professional development. Read the table of contents to understand the range before choosing a starting point.

That breadth helps make connections visible. An interface meets data and accessibility; automation depends on integrations; a product launch needs observation and testing. Use the contents as a map of adjacent skills. Building a website does not require studying every programming language and network protocol at once. Add a neighbouring area when it resolves a problem that your current project has actually exposed.

The VITON13 protocol: learning you can demonstrate

The opening pages set out a six-stage cycle. A goal turns curiosity into a defined outcome. Exploration builds a small map of concepts from several resources. Practice means reproducing a working example yourself. A project introduces your own decisions. Verification finds weak points. An artifact preserves the result as code, screenshots, findings or a link to a working prototype that someone else can examine.

This gives the learning process something concrete to discuss. You can explain why you chose a structure, demonstrate a bug and its correction, and identify the limits of your work. Even a small project shows how you apply what you have read. For the first cycle, choose an outcome that can be checked with a simple action: opening a page, running a script or reproducing a calculation.

Choose a first route that belongs to you

If the web interests you, start with the front-end section and create one page with clear navigation that also works on a phone. Move to back-end development or databases when the page needs to store information. For research, use a small table, ask a specific question and preserve a repeatable way to find the answer. For design, an interactive prototype can be a useful first artifact.

A business route might start with a repeated operation: preparing a report, processing an enquiry or moving information between systems. Describe the inputs, expected output and check before choosing software. Combine the book’s business, platform and development-environment sections around that task. Use sample data when it can demonstrate the same process without introducing sensitive information. A narrow problem makes it easier to see whether the experiment worked.

START, BUILD and MASTER describe depth

START means understanding the terminology and running a first example. Record what each part does and where a question appears. BUILD means connecting several tools into a working project. Real boundaries emerge here: data formats, interfaces, dependencies and error handling. MASTER means comparing alternatives, measuring quality and explaining architectural trade-offs. The levels help you decide what kind of work to do next within one topic.

They describe depth rather than a timetable or a professional qualification. You may be at BUILD in web development and START in data analysis. Move forward when you can repeat the result, explain your choices and identify what still needs checking. The next cycle can introduce just one new constraint: a different volume of data, another screen size or a failure scenario. That is enough to make the investigation more demanding.

Keep using the atlas after the first project

Once the project is complete, return to the contents and ask what the solution lacked. Sometimes you need another tool; sometimes you need testing fundamentals or a clearer task description. Add a brief record to the project: goal, resources used, check result and next question. The general catalogue then becomes a personal knowledge map connected to working examples rather than a growing pile of bookmarks.

The atlas is a fixed digital publication. Software projects, documentation, access terms and licences can change, so consult the original source before installation. Free access to the book does not mean every listed service is free. Save the PDF, choose one section and finish a small result you can show to another person. That makes the next learning decision grounded in work you have actually done.