Three entry routes into the same curriculum. Pick the one that matches how much time you can give each week and how much structure you want from us.
For people opening a code editor for the first time. Starts with how a program actually runs, then moves through variables, control flow, functions, and small command-line tools. Weekly exercises are short and checked against reference solutions, so you always know whether your reasoning held up.
Start with FoundationsBuilt for learners who already write basic code and want to ship something real. Covers version control, working with APIs, reading documentation, debugging a stack trace, and structuring a small project so it stays readable after three months. Includes a guided build you finish on your own.
See the Applied pathFor those heading toward backend or infrastructure work. Databases, data modelling, HTTP, deployment basics, and the trade-offs behind common architecture choices. Heavier reading, fewer hand-holding steps, and more open questions you resolve with your own notes.
Explore Systems and DataIf you prefer to move without a fixed schedule, individual modules from any track can be taken on their own. Same material, same exercises, no cohort timing. Useful when you want to fill one specific gap rather than follow a full pathway.
Ask about single modulesEvery learning path at Ideka Technology Academy follows the same route. You start with a topic you want to understand, work through guided modules, and finish with something you built and can explain. No shortcuts, no skipped fundamentals.
Tell us what you already know and what you want to build. A complete beginner starts with syntax and tooling; someone with scripting experience can jump straight into backend or frontend modules. The placement conversation takes a few minutes and sets the whole sequence.
Each module pairs a short concept section with a hands-on exercise. You read how a loop, a query, or a request works, then write it yourself in a small project. Exercises are checked against expected behaviour, not against a single correct line of code.
When something breaks, you learn to read the error, isolate the cause, and test a fix. Review sessions focus on why a solution works and where it would fail under different input. This is where most of the real understanding happens.
After a few modules you assemble them into something complete: a form that stores data, a script that processes files, a page that fetches and displays information. The project stays small enough to finish and large enough to expose real integration problems.
Finished modules open the next set: databases, APIs, version control, deployment basics. You can pause, repeat a topic, or switch direction. The path is progressive, but it is not a race, and nothing expires.
Questions about where to start? Write to info@idekalinga.com or call +43 1676 8746-17. We will suggest a starting module based on what you already know.
Ask about a learning pathLearning resources are grouped into working areas, not one long syllabus. Each area covers a set of tasks you would meet on a real project, from reading code you did not write to keeping a small service running. Modules can be taken in sequence or picked individually, depending on what you already know.
Variables, control flow, functions, and data structures explained through small programs you run and modify yourself. The focus is on reading code before writing it, so syntax stops being the main obstacle.
Version control, branching, code review habits, and structuring a project so another person can find their way around it. Includes how to write a commit message that still makes sense three months later.
HTML structure, CSS layout, and the browser behaviour behind forms, navigation, and responsive pages. Emphasis on understanding what the browser does with your markup rather than memorising framework syntax.
How applications store, query, and move data: relational tables, simple document structures, APIs, and the difference between a cache and a source of truth. Includes reading logs and tracing where a request went.
Reading error output, isolating a failure, and writing tests that describe behaviour instead of internal method calls. A practical routine you can apply in any language that prints a call stack.
Command line basics, file permissions, environment configuration, and the small operational habits that keep a development machine predictable. Useful before touching deployment or shared infrastructure.
Modules are self-paced and written for beginners, career changers, and self-taught learners who want a clear order to follow. If you are unsure where to start, the contact page is the right place to ask.