Category 05 / ARM.NET
Learn the foundations of code, application development and tools for organizing projects.
Programming expresses instructions and rules to solve a problem. Projects also require organizing data, managing changes and checking behavior against expectations.
14 topics explained
01 / 14
HTML describes content structure and meaning; CSS controls presentation. Headings, links and forms should express their purpose before styling. Semantic structure improves navigation, accessibility and maintenance. MDN introduction to HTML.
Build a page with a main heading, sections and real links. Then adapt the layout using a grid and small-screen rules. Check that it remains understandable without styles and that controls work with a keyboard.
Back to the topic index ↑02 / 14
JavaScript adds behavior: responding to events, transforming data and updating interfaces. In browsers it can use the DOM representation of the page. Network operations are asynchronous and must handle both success and failure.
Start with a filter displaying items from a search field. Separate data from presentation logic and handle empty results. Avoid inserting untrusted text as HTML when only text content is needed.
Back to the topic index ↑03 / 14
Python serves automation, data analysis, services and many other tasks. Its syntax uses indentation for blocks. Learning types, functions, iteration and error handling offers more lasting foundations than memorizing libraries.
A first project could read a CSV file and calculate a summary. Work on a copy and validate columns and missing values. Use separate dependency environments when projects require different versions.
Back to the topic index ↑04 / 14
Java is statically typed and usually compiles to bytecode for a virtual machine. Classes, interfaces and build tools structure large applications. Environment version affects available features.
Practice with a small inventory: define a product, validate data and calculate stock. Separate logic from console input for testing. Check compatibility among the JDK, dependencies and execution environment.
Back to the topic index ↑05 / 14
C and C++ are distinct languages allowing close control of memory and the system. That control requires understanding object lifetimes, buffer limits and pointer behavior. C++ adds abstraction and resource management tools.
Start with small programs and enable compiler warnings. In C++, use appropriate containers and automatic resource management. Testing empty, very long or unexpected inputs reveals errors missed in normal cases.
Back to the topic index ↑06 / 14
Git records file versions through commits and supports branches. GitHub hosts repositories and adds collaboration around that history. Saving a file, committing and pushing to a remote repository are different operations.
Review the diff before committing and explain the change's purpose. Use a branch for a specific change and verify before integrating. Avoid passwords or tokens: deleting a line later does not automatically remove its history.
Back to the topic index ↑07 / 14
A web application may include an interface, server and storage. The browser presents content; the server validates requests and applies rules; the database stores information. Not every site needs all layers: a static blog can use files.
Start with an accessible page and add logic only when needed. Validate forms on the server even with visual validation. Check loading, errors and missing data as well as the ideal path.
Back to the topic index ↑08 / 14
Mobile development must consider touchscreens, battery use, permissions and connectivity changes. Applications may be native, share code across platforms or use web technologies, with different benefits and constraints.
Design a short task that can be completed one-handed. Test interruptions, rotation and connection loss. Saving progress and explaining permission requests improves experience more than adding features without a clear flow.
Back to the topic index ↑09 / 14
An API defines how software components interact. A web request usually includes a route, method and data; a response includes status and content. The contract defines formats, authentication and error behavior.
Design a simple resource such as a task list and document valid and invalid examples. Distinguish input errors from server failures. When retrying requests, consider whether the operation might create duplicates.
Back to the topic index ↑10 / 14
A database organizes information for querying and modification. Relational models use tables, keys and relationships; others use documents or different structures. Selection depends on queries, integrity and growth needs.
Model customers and orders separately and link their identifiers. Use parameterized queries for external inputs. Indexes speed reads but require space and extra write work; they should support real queries.
Back to the topic index ↑11 / 14
The cloud provides computing resources over a network: machines, storage, databases and managed services. Delegating infrastructure reduces some operations work, but data, permissions and configuration remain responsibilities.
For a small project, calculate resources, transfer and storage alongside compute price. Set spending limits or alerts and document recovery. More services than necessary increase complexity and dependencies.
Back to the topic index ↑12 / 14
DevOps combines development and operations practices for repeatable changes. Version control, continuous integration, observability and automation help detect faults and understand service state. A single tool cannot replace team agreements.
First automate a build and representative tests. Then document deployment, verification and rollback. Small changes with metrics and known recovery are usually easier to investigate than large releases without operational information.
Back to the topic index ↑13 / 14
A coding assistant can explore a codebase, draft functions or propose tests. Its limited context may lead to nonexistent interfaces or incompatible solutions. Review behavior and requirements as well as style.
Request a bounded change with input and output examples. Run tests capturing the real problem and review the diff. Explain why the solution covers the original case and how it handles unexpected inputs.
Back to the topic index ↑14 / 14
A project turns concepts into concrete decisions. A sound tutorial defines the deliverable, required knowledge and verification. Learning continues when you modify the example and observe which assumptions stop holding.
Create a catalog with three pages, an index and relative links. Then add search and an empty-results view. Document execution and ask someone else to follow the instructions: missing steps will become clear.
Back to the topic index ↑Start with a small, observable project such as a page with navigation or a text-processing program. Divide work into steps and use version control to preserve change history.
Explore these guides and resources for more detail. Links open in a new tab.