Internship
Semester VIII · BCA 452 · 3 credits
0 / 5
chapters done
-
The syllabus asks for
- What an internship is
- The running example: InternTrail
- Write your learning objectives first
- Searching and shortlisting
- The CV, the email and the interview
- Eight reasons good students lose good placements
Key points
- An internship is work in someone else's problem space, supervised and assessed; it differs from a project, a course and a job.
- Write three SMART learning objectives before searching; they decide whether an offer is good.
- Compare at least three options with a weighted matrix and check the result with a sensitivity test.
- The CV is one page and proof-first; the email is short and specific; the interview uses honest STAR stories.
- Start the search twelve weeks before the placement and finish the paperwork three weeks before.
-
The syllabus asks for
- The first day and the first week
- Etiquette and communication
- Confidentiality and data handling
- Rights, safety and digital hygiene
- Eight habits that make an intern trusted
Key points
- The first week is a checklist; confirm in week one that real tasks match your objectives.
- Good communication means the right channel, a complete message and a record of decisions.
- Use the 15-minute rule to balance independence with asking for help.
- Information has four levels; restricted data (passwords, IDs) never lives in code or chat.
- A leaked secret must be changed, not just deleted, and reported immediately.
-
The syllabus asks for
- Plan the eight weeks
- The daily log
- The weekly review
- Analysing the log
- Eight rules for a log that passes a supervisor's eye
Key points
- Plan the placement as observe, contribute, own, hand over and share the plan with your supervisor.
- A daily log has six fields; the entry must be specific, same-day and truthful.
- The weekly review (Keep, Stop, Try) keeps the placement on track and produces the supervisor's signature.
- Log data can be analysed: in the example, coding 34 percent, learning 19, and one honest miss against L3.
- Never adjust the log to fit the objective; adjust the objective next time and explain the gap.
-
The syllabus asks for
- The ticket life cycle
- Reading a code base you did not write
- Reproduce first, then fix
- Fix, test and ask for review
- What a code review looks for
- Documentation and hand-over
- Eight practices of interns whose work gets merged
Key points
- A ticket moves from backlog to deployed, and somebody else sees it at every step.
- Read an unfamiliar code base by running it, finding the entry point, tracing one path and asking one precise question.
- Reproduce first: HD-31 failed on 2 of 4 invoices because float 0.565 rounds down; Decimal rounding once gives 55.26.
- Tests (6 of 6 passing) prove the fix and document the promise; edge cases matter.
- Code review is normal, expected and educational; reply to every comment.
-
The syllabus asks for
- The internship report
- Planning the pages
- Reflection and the honest self-assessment
- Supervisor letter, certificate and references
- The presentation
- The viva: twelve questions and model answers
- Eight habits that finish an internship well
Key points
- The report is specific, evidence-based and honest; chapters 4 and 5 (your work) carry the most pages.
- Use a page budget, write from week five and cite log dates and ticket numbers.
- Reflect with a before-and-after self-assessment: mean 2.25 to 4.00 in the example, with one weak skill named.
- Request certificate, evaluation and reference early; thank people.
- A ten-minute talk tells one story; the viva rewards claim, evidence and an honest limit.
No chapter matches. Try another word.
The paper
TU assessment: 60% final examination set by the university, 40% internal (assignments, lab work, attendance). Confirm the split in your college's notice.