Software greenhouse · study season 01

Grow code that can keep growing.

Navurexi is an IT course studio arranged like a working greenhouse: clear light, patient repetition, and real things to tend. Build a practice across web, data, systems, and product work.

Learner working on a laptop among greenhouse plants
Slow is a feature.Observe · build · revise

The studio desk / daylight, notes, working code

Current growing conditionsFour terms, one connected practice
Term 1Set roots
Term 2Make systems
Term 3Ship a tool
Term 4Reflect & tend

01 / curriculum calendar

A season has a rhythm, not a conveyor belt.

01

Orientation

Tooling, files, command line, and an honest baseline.

02

HTML & structure

Build readable documents and durable interfaces.

03

CSS & response

Work with layout, type, and screens of different sizes.

04

JavaScript seeds

Model small interactions, data, and state with care.

05

Git habits

Leave a useful trail for your future collaborators.

06

First field review

Share a small build, annotate it, and revise once.

07

Data shapes

Read, transform, and question the information in a small dataset.

08

Requests

Connect a browser interface to an approachable API surface.

09

Persistence

Plan how a project remembers and retrieves useful things.

10

Testing paths

Trace ordinary and edge-case journeys through an interface.

11

System sketch

Map the boundaries, assumptions, and trade-offs in your tool.

12

Second field review

Bring a working system to the table for guided critique.

13

Choose a problem

Define a bounded need and who it is for without overpromising.

14

Prototype

Use quick screens and honest assumptions to test direction.

15

Build in slices

Make a small useful path work before adding decoration.

16

Document

Write a handover someone else can use on an ordinary day.

17

Present

Explain choices, limits, and next questions with precision.

18

Season close

Archive your work and name the next thing worth tending.

02 / growing prerequisites

Bring curiosity. Borrow the rest.

This is a ledger, not a gate. See what helps at the outset and what we build together along the way.

Cobalt glass forms and an acid-lime cable
01

A working device

A laptop or desktop you can use regularly. We help you check browser, editor, and terminal setup during orientation.

02

Weekly room to practice

Reserve modest, repeatable time between sessions. The calendar is designed around making, pausing, and returning.

03

A question you care about

Come with a process, community, or idea you want to understand. It can be unfinished; that is useful material.

04

Permission to draft

Early work is expected to be rough. We use versions, notes, and short reviews to make revision visible rather than mysterious.

A diverse group working together around a practical lab table

03 / hands-on lab bench

No spectators at this bench.

Every lab has separate roles so that making software involves noticing, explaining, testing, and tending—not only typing.

Builder

Turns a bounded sketch into a working slice.

Observer

Tracks friction, assumptions, and the question behind a choice.

Tester

Tries ordinary and unusual paths with a clear record.

Translator

Explains the tool in plain language for its intended user.

Two learners collaborating on a computer in a plant-filled studio
Skill trellis
pick a vine →
see what it supports

04 / skill trellis

Skills climb together.

Select a vine to see how each practice supports the others in the studio.

Structure makes room for meaning.

Learn to name, nest, and order information so people—and future you—can find their way through a tool.

05 / field-notes journal

Notes from the work between sessions.

The journal keeps the small observations that change a build: a strange error, a clear explanation, a decision worth revisiting.

“The bug was a sentence with one word missing.”

A prompt to read an error as information rather than a verdict.

Bring a stuck point

Show your next assumption before your next solution.

Small experiments make room for better questions.

See the calendar

Make the useful path work first.

A feature list is not a plan. A working path is.

Visit the bench
Notebook with code notes beside a small plant and laptop

“A study season is long enough to notice patterns, short enough to keep them in view.”

06 / cohort observatory

See the room, not a leaderboard.

A shared view of the working environment: what happens in sessions, what is made between them, and what gets recorded for return visits.

A quiet evening greenhouse workspace with a laptop and notebooks

Session habitat

One view of a study week

PlaceWorking modeTrace kept
Studio sessionGuided making & critiqueBench notes
Independent plotFocused practiceCommit or journal line
Peer crossingExplain & testQuestion list
Mentor sessionDecision supportNext-small-step

This is a course design map, not a measure of output. Different learners work with different conditions.

07 / assessment greenhouse

Evidence, not theatre.

Assessment is a cultivated record of what you can explain, build, revise, and hand over. It is not a single high-stakes performance.

Working artifacts — small, inspectable pieces of code and interface.
Decision notes — what changed, what stayed open, and why.
Guided review — a conversation around the next useful revision.
Talk through fit
Mentor guiding an online learning session in a greenhouse studio
Mentor with notebook and laptop in a blue plant studio

08 / learning-support shelf

Keep useful help within reach.

Support should be easy to find before a small uncertainty becomes a reason to stop.

  • Setup shelfPlain-English guides for your workspace, files, and starter tools.
  • Question shelfA place to bring a half-formed question without needing the answer first.
  • Revision shelfPrompts that help turn a review note into a manageable next move.
  • Pathway shelfConversation starters for choosing a direction after this season.

09 / frequently asked

Useful questions deserve complete answers.

No prior programming experience is assumed for the roots term. You do need a device you can use consistently and enough regular time to return to the work between sessions. We begin with files, browsers, editors, and simple web structure before introducing more moving parts. If you already have experience, the mentor session is a good place to identify a suitable starting point and scope.

A study season is a bounded period with a visible rhythm: introductions, small build cycles, time to practice alone, shared review, and a closing reflection. The metaphor is deliberate. Software learning rarely grows in a straight line, and progress is easier to recognize when you revisit the same ideas under different conditions. The calendar names the major markers while leaving room for the work that happens between them.

Roles are a way to broaden participation, not a way to label people permanently. A person may build one week, test another week, and translate a technical decision for a user on a later project. Each role has a practical contribution and a different vantage point on a software problem. Moving between them helps learners practice collaboration without pretending that everyone arrives with identical confidence or context.

A mentor session is a browser-based conversation about your current question, learning conditions, and practical next step. It can be used before a season to discuss fit, during a season to unpack a difficult decision, or afterwards to reflect on a direction. It is not an automated evaluation and it does not promise a particular outcome. Bring a link, a note, a rough idea, or simply the point where you became unsure.

10 / mentor-session contact

Bring the question that is still taking shape.

Tell us a little about where you are and what you want to grow next. This form creates a confirmation in your browser only; it does not send information anywhere.

Thanks — your note is ready for the next step. In this demo, nothing has been transmitted.

For general enquiries, use [email protected].

A learner considering notes at a greenhouse workspace
MENTOR SESSIONS
Remote · browser-based
Bring your earliest draft.