Web development, as I practise it, means building websites that work for the people using them and for the systems reading them: fast on a mid-range phone on a Nepali mobile connection, secure by default, and still readable when a script or a network request fails.
Principles this site is built on
Content must not depend on a script
Animation and interaction are layered on top of HTML that is already complete. This site learned that the hard way — a script truncated to zero bytes left pages blank while every monitor reported success — and now has three independent fail-safes, so a failed script costs an animation and never the page. The full account.
Performance is measured where visitors are
Slow sites in Nepal are usually slow before any image loads: a slow server response, scripts blocking the first render, images without dimensions that shift the layout as they arrive. Across 34 Nepali websites, 1,584 of 2,167 images had no width or height set. What the timings show.
Security headers are cheap, and mostly missing
HTTPS is necessary and not sufficient. Headers such as Strict-Transport-Security, Content-Security-Policy and X-Content-Type-Options close whole classes of attack for a line of configuration each. All 30 Nepali government websites I checked served valid HTTPS; only 2 sent HSTS. The government header study. References: MDN on HSTS and the OWASP Secure Headers Project.
Metadata is part of the build
Titles, canonicals, Open Graph tags and structured data are how a page presents itself when it is shared or indexed, so they belong in the build rather than an afterthought. A missing og:image turns every WhatsApp share into a grey box. Why that costs more in Nepal.
Reliability means checking what is served
An uptime check confirms that a server answered, not that it answered with anything. Check the bytes, check that the words are there, and check what the CDN is serving rather than what is on disk.
