Alfred Abner

Assistant Development Officer Candidate

I teach in the lab, and I build the tools the lab is missing.

About

Short bio

I'm Alfred Abner, a Software Laboratory Assistant at BINUS University, Kemanggisan, since February 2026. Before that, I spent a year as an Education Counselor, helping future students picture a career in technology. I'm curious by nature: when something feels slow or repetitive, I want to find out whether I can build a better way. That curiosity turned into projects like an online course platform, a cruise-ship management system, and small tools for my lab work, such as a schedule calendar and an exam proctoring checklist. I'd like to bring that same curiosity to AstDev.

Quick facts

Role
Software Laboratory Assistant
Where
BINUS University, Kemanggisan
Since
February 2026

Strengths and Weaknesses

Strengths

  • Relentless Perseverance

    When something breaks, I treat it as a puzzle, and I see hard, ambiguous tasks through without constant oversight.

  • Systems Thinking from Gaps

    I spot ground-level gaps and turn them into structured proposals.

  • Cross-Team Coordination

    I read people and group dynamics fast, from the Social Media Team to mentoring new students as a Freshmen Partner, so I can tell confusion from nerves and keep teams working together.

  • Transparent Communication

    I say what I mean and do not use influence tactics to get my way.

Weaknesses

  • Solo working tendency

    I work well alone, but working alone by default can weaken how a team holds together.

    I keep collaboration a priority, so independence never becomes distance.

  • Unstructured criticism

    I used to raise process issues, like the TPA onsite format, without offering a clear alternative.

    I now pair every critique with a specific proposed change.

  • Time management

    I used to struggle to balance several responsibilities at the same time.

    I plan in fixed time blocks and track everything in one place.

Innovations

Work Plan

Semester 1

  1. Feb 2027Pre-TPA standardEvery Pre-TPA comes just before its initial phase, with the material shared three days ahead, starting with TPA Game.
  2. Feb 2027First onsite quizTPA Game runs the first onsite quiz at 35:65, solo, with Code Viva questions drawn from each assistant's own commits.
  3. Apr 2027Tested casesDesktop and Web cases get a test run by hand and with AI before release, and each case maker receives handoff notes from the last.
  4. Jul 2027Mid-year reviewGame and Desktop results are compared with 26-1, and the playbook is adjusted before Web and Network.
Continues
The TPA flow (take home, presentation, revision), the calendar shape of 26-1 and the existing Pre-TPAs.
Improves
Pre-TPA timing and material, the first onsite quizzes, test-run cases and Code Viva, tried first on Game and extended to Desktop and Web.
Hands over
Results from Game compared with 26-1, and playbook version 1.

Semester 2

  1. Sep 2027Network improvementsTwo Pre-TPAs, a 30-question onsite in one 2-hour shift per group, and spare examiner days.
  2. Oct 202727-2 with more onsiteGeneration 27-2 starts with a 40 percent onsite share for Game and 50 percent from Desktop on, including a Desktop onsite on diagrams and a simple Rust Tauri case.
  3. Dec 2027Full 27-1 cycle and Proximal into RIGMobile completes the first full cycle, and RIG uses AI fully, built by assistants who understand their work.
  4. Jan 2028Lineage handoverThe playbook, Pre-TPA packs, test run notes and handoff notes go to the 28-1 case makers and the next officer.
Continues
Whatever worked in 27-1, applied to Network, Mobile and 27-2, with the same measurements.
Improves
Network's two Pre-TPAs and question limit, and the move from TPA into RIG with AI used fully and a continuation step.
Hands over
The playbook, Pre-TPA packs, test run notes, handoff notes and the 28-1 calendar method, so the next officer starts on day one.
Goals
Bring every TPA within reach, so assistants build real understanding and use the right amount of AI, measure understanding instead of output, and keep every core lesson for the next generation.
Deliverables
The 27-1 and 27-2 calendars with a Pre-TPA before every TPA, onsite quizzes for Game, Desktop and Web and a 30-question onsite for Network, Code Viva question sets, handoff notes for every case, a TPA playbook, and the RIG continuation step.
Success measures
More assistants finish each phase within its time than in 26-1; every group member answers at least 5 Code Viva questions and is scored individually; onsite days fit one shift per group; every case has test run notes and handoff notes at handover.
Risks
Examiner workload grows with onsite parts (mitigated by one 2-hour shift per group, spare days and generated question sets); case makers need time for test runs (planned into the Lineage handoff); assistants used to AI shortcuts may resist (the Pre-TPA and right-sized cases make building it yourself possible again).

TPA Change

Current

In 26-1, each Pre-TPA was held on the TPA's first day, and Network's fell on the day its take-home began. Only Web and Network had onsite parts, and the cases had grown beyond what one assistant could build alone in the time given.

Proposed

In 27-1, every Pre-TPA comes just before the initial phase with the material shared three days ahead, and every TPA except Mobile gets an onsite part on a case the TPA case maker decides. The onsite share grows from 35 to 50 percent, and in 27-2 it starts at 40 percent, so understanding counts as much as output.

  • Take-home days, initial and revision
  • Presentation days, red
  • Onsite and onsite revision, outlined
  • Pre-TPA and shared material, corner square
  • Weekend, dimmer number
  • Blue outline: onsite new compared with 26-1
  • Blue corner square: Pre-TPA or material, new compared with 26-1
  • National holiday, hatched, name on hover
  • Collective leave, lighter hatch

  1. Step 1Prepare

    From Dec 2026, write the Pre-TPA packs, set up handoff notes and run the first test runs on TPA Game.

  2. Step 2Start with Game

    In Feb to Apr 2027, run the first onsite quiz and Code Viva on Game and record what worked and what broke.

  3. Step 3Extend

    From Apr 2027, carry the lessons into Desktop, Web and Network, and into 27-2 from Aug 2027 with a higher onsite share.

  4. Step 4Review and hand over

    After 27-1 ends in Nov 2027, compare it with 26-1 and pass the handoff notes to the 28-1 case makers.

Philosophy

    Why Accept Me

    1. I build what this role maintains

      This site runs on infrastructure I built and look after myself on Azure.

    2. I have been through it myself

      I went through the TPA as an assistant, so I know where the time and pressure go.

    3. My plans come with their handover

      Each proposal says what we keep, what we improve, and how it is passed on.

    Live System

    Status

      Latency

        CI/CD

          Questions

          Ask a question

          2 to 5 letters.

          Asked so far