Gleipnix
Free, openly licensed material for learning computing.
Fundamentals in the Academy, applied work in Resources — mathematics, computer science, cloud, IoT and IT, written to be used this week rather than filed away for later. No sign-up, and nothing behind a paywall.
Everything written here is reusable under CC BY-SA 4.0 — copy it, teach from it, translate it, with credit.
Two ways in
The Academy
FundamentalsMathematics, computer science, data and engineering — a roadmap of topics, written in an order you can actually follow, with worked problems.
5 subjects · 68 topics mappedResources
AppliedCloud, networking, IoT, security and the rest of the working knowledge you need while you are in the middle of the job.
20 entries · 8 topicsBrowse by topic
Cloud Infrastructure
3Providers, architecture, networking and what actually drives the bill.
OpenNetworking & DNS
3Records, TLS, routing and how to debug something that will not resolve.
OpenIoT & Devices
3Sensors, gateways, MQTT and getting telemetry somewhere useful.
OpenAutomation & Scripting
2Shell, Python, scheduled jobs and replacing manual work.
OpenSecurity & Access
3Identity, least privilege, backups and what to do when it goes wrong.
OpenData & Reporting
2Pipelines, modelling, storage and dashboards people trust.
OpenLinux & Servers
2Services, permissions, logs and process management.
OpenWeb & Hosting
2Domains, deploys, CDNs and static hosting.
OpenRecently added
Choosing between GCP, AWS and Azure for a small business
The provider differences that matter at 10 servers, and the ones that only matter at 10,000. A decision guide without the marketing.
DNS records explained without the hand-waving
A, AAAA, CNAME, MX, TXT, and the ones you only meet when something is broken. What each record actually does and when to use it.
Designing MQTT topic hierarchies that survive growth
Topic structure is the schema of an IoT deployment. Getting it wrong is expensive later, and most of the cost comes from wildcards.
Least privilege in practice, not in principle
Everyone agrees with least privilege and almost nobody implements it. A concrete way to get from admin-everywhere to scoped access without stopping work.
What actually drives a cloud bill up
Egress, idle capacity, over-provisioned managed services and storage tiers. The line items worth attacking first.
Infrastructure as code when you are one person
You do not need a platform team to stop clicking in the console. A pragmatic starting point with Terraform.