Adnan Tarabishi
Choosing the priorities, shaping the experience, organising content and sources, directing development, checking results and listening to students.
Product decisions and responsibility stay human.
About the Hub · Build notes
Behind
the Build.
One student-led idea. Many thoughtful iterations. A shared space for the EU-HEM journey.
A look at the planning, creativity and practical work behind the Hub — not just the code.
Student-ledAI-assistedFree to use
01 / The effort
Where the hours went.
Six kinds of work, one shared purpose:
make student life a little easier.
Illustrative breakdown of the approximate 60-hour personal-effort estimate. Individual categories were not timed separately.
More than writing code.
The visible pages are only part of the work. Decisions, research, review and improvements matter too.
How to read the numbersDesign & visual identity15 h
Making every page feel like part of the same Hub.
- Homepage, navigation and page layouts
- Mobile and dark-mode refinements
- Visual identity, imagery and readable interfaces
Interactive tools & features14 h
Turning useful ideas into things students can actually use.
- Statistics Lab and Student Toolkit
- Timetables, calendars and interactive explorers
- Contact forms and editor workflows
Content & research13 h
Finding, organising and explaining the information that matters.
- Original study guides and learning activities
- Programme rules and source checks
- University, city and thesis information
Testing & refinement9 h
Checking the details that make a site usable and dependable.
- Reviewing behaviour on phones and desktops
- Fixing links, images and interface issues
- Checking changes, deployments and offline updates
Planning & direction6 h
Deciding what to build, how it should work and what to improve.
- Defining scope and priorities
- Writing development instructions and reviewing outputs
- Organising the roadmap and next steps
Launch & feedback3 h
Sharing the beta and learning from the people it is built for.
- Preparing the cohort launch
- Explaining the Hub and its features
- Collecting feedback and improvement ideas
Total estimate 60 hours
Percentages are calculated from the allocation and rounded; they do not indicate measurement precision.
02 / The journey
An idea, then a useful place.
The first public code
The homepage, timetable, calendar and announcements began taking shape in the repository.
Browse the code history ↗First cohort beta
The Hub was shared with classmates — a starting point for feedback, improvements and new ideas.
Read the project journey ↗A moment to look back
This approximate 60-hour personal-effort estimate records the effort so far. The Hub continues to evolve beyond this snapshot.
Read the estimate notes ↓
03 / Human + AI
Human direction. AI assistance.
Built with tools, guided by people.
ChatGPT · Codex · Claude Code
Used to support exploration, drafting, coding, debugging and iteration. Their outputs still need selection, checking and refinement.
Tool execution time is not a measure of personal effort.
04 / About the numbers
Transparent, not a timesheet.
The headline is an approximate estimate of personal effort, revised at the project owner's request on 9 October 2026. It is not an independently audited or automatically tracked total.
What the estimate covers
Planning, design decisions, content and source work, development direction, hands-on review, testing, launch preparation and feedback, including AI-assisted work with ChatGPT, Codex and Claude Code. AI runtime and GitHub activity alone cannot establish how long a person was actively working.
How the estimate was prepared
Restored to the owner's 60-hour estimate on 9 October 2026. Repository history and completed features provide evidence of the work, including AI-assisted development with ChatGPT, Codex and Claude Code, but do not measure time spent. A complete time log and private Claude Code conversation history were not available. Category hours are an illustrative allocation, not recorded hours or AI execution time.
The six categories are an illustrative allocation of the total, not six measured time logs. A work session can involve several activities; the display assigns the overall estimate once rather than adding overlapping sessions.
How the figures are maintained
This is a dated snapshot, not a live counter. The project owner can revise the estimate or request a new assessment of the completed work. The page does not track your visits, create a timer, or collect new personal information.
View the public estimate data ↗Explore the work itself: Source repositoryDevelopment reviewsRoadmap & updates
Better with your perspective
Help shape the next hours.
A confusing page, a useful idea, a missing feature — your feedback helps decide what comes next.