Lesson 15 / الدرس 15

What somebody actually looks at / ما ينظر إليه أحدهم فعلًا

Whoever is looking at your work has thirty of them to get through and is giving yours somewhere between twenty seconds and two minutes. Almost everything people put effort into is outside that window, and the few things inside it are cheap to fix.

من ينظر في عملك أمامه ثلاثون مثله ويعطي عملك ما بين عشرين ثانية ودقيقتين. ومعظم ما يبذل الناس فيه جهدًا خارج تلك النافذة، والقليل الذي بداخلها رخيص الإصلاح.

The instinct is to build more projects. Three finished things with a sentence each beat eleven half-built ones every time — because the reader is not counting, they are looking for evidence that you can take something all the way, and eleven unfinished repositories are evidence of the opposite.

The twenty seconds

Booking system for a small hotel                    Live | Code
PHP, MySQL. Rooms, availability and payments. The interesting
part is preventing two people booking the same room at once --
there is a note in the README about how.

^ what it is, what it is built with, and ONE thing that was hard.
  Three lines. A live link and a code link that both work.

Not this:

  My Project
  A web application built using modern technologies and best
  practices, demonstrating my passion for clean code.

^ says nothing. Could be attached to any project by anyone.
Naming the hard part is what does the work here. "Preventing two people booking the same room" tells a reader you met a real problem and knew it was one — which is the thing they are actually trying to find out, and it cannot be faked by anybody who has not met it.

What gets checked after the twenty seconds

  • Does the live link work? A dead link is worse than no link, because it says the last time anybody checked was before it broke.
  • The README, and then the commit history. A README that says how to run it, and commits that say why rather than "update" forty times. Those two say more about how you work than the code does.
  • One file, opened at random. Not to audit it — to see whether it looks like something a person maintained or something that was generated and never read.

Try it live / جرّب بنفسك

Preview / المعاينة

Check yourself / اختبر نفسك

1. Why do three finished projects beat eleven half-built ones?

2. What makes a project description work in twenty seconds?

3. Why not include something you cannot fully explain?

Your task / مهمتك

Write the top of your own portfolio and three project entries, each in the three-line shape: what it is, what it is built with, and the one thing that was genuinely hard. Then check every link, and note for each project whether you could explain all of it under questioning.

اكتب أعلى معرض أعمالك وثلاثة مدخلات مشاريع، كلٌّ في شكل الأسطر الثلاثة: ما هو، وبمَ بُني، والشيء الواحد الذي كان صعبًا حقًا. ثم افحص كل رابط، ودوّن لكل مشروع أتستطيع شرحه كله تحت الأسئلة.

  • A first line that says what you build, not what you are passionate about سطر أول يقول ماذا تبني، لا بمَ تشغف
  • Three projects, each with the one thing that was genuinely hard named ثلاثة مشاريع، ولكلٍّ الشيء الواحد الذي كان صعبًا حقًا مسمًّى
  • Every live and code link opened and confirmed working كل رابط حيّ ورابط كود فُتح وتأكد عمله
  • For each: could you explain all of it under questioning, honestly لكلٍّ: أتستطيع شرحه كله تحت الأسئلة، بصدق
How do you want to submit? / كيف تريد التسليم؟