NovArticles by Alexander Elshin
A source timeout should never become a zero value
Why a temporary failure to retrieve a property value must remain an unknown state instead of turning into a numeric zero that contaminates sorting and calculations.
A gallery must keep each caption attached to the right image
How a partial loading failure can turn an otherwise working property gallery into misinformation if captions drift away from the assets they describe.
Image provenance should travel with the asset
How image source, material type and asset lineage can survive resizing, cropping and reuse so a technically valid file does not lose its editorial meaning.
Price sorting needs a rule for properties with no confirmed price
A property with no confirmed price cannot honestly be treated as cheapest or most expensive, so sorting and budget filters need an explicit policy for unknown values.
A data migration should verify RU and EN records as pairs
Why a migration can copy every record successfully and still split one property into conflicting Russian and English representations.
A generator bug is more dangerous than a one-page bug
Alexander Elshin on why shared templates, generators and data sources need separate testing: one defect can spread across hundreds of NovAsia pages.
Time zones can make “updated today” wrong
Why relative date labels need a stable underlying event time, so the same property fact does not appear fresher or older merely because the reader is elsewhere.
Internal status labels should stay internal
Why operational workflow labels and buyer-facing property states should be separated without hiding material uncertainty from the public page.
Structured data should not tell a richer story than the page
Schema markup is useful when it represents visible, supported information—not when it adds claims that the user cannot verify on the page.
Localised formatting must not change the underlying amount
How number localisation can alter appearance without altering the property value, and where bilingual products can accidentally turn formatting into a data error.
After a release, I test more than the new page
A feature can work perfectly and still break shared components, routes or user journeys elsewhere on the platform.
A double click should not create two property enquiries
A reliable enquiry form should survive repeated clicks, retries and slow feedback without multiplying one buyer action into duplicate conversations.
Page speed should not be improved by deleting useful features
Performance matters, but a faster score is not a win if the property buyer loses comparison, evidence or another important tool.
Monitoring should distinguish a page failure from a data-source failure
Why a healthy-looking page can still be serving unreliable property information, and how separating failure types improves the buyer-facing response.
Project aliases need one identity without merging distinct phases
How project aliases can improve discovery while preserving the separate identity, history and facts of distinct phases and related entities.
A redirect is a claim that the new URL replaces the old one
Sending every removed page to the homepage hides errors without necessarily preserving what the visitor was trying to find.
Hreflang is useful only when both editions really exist
Language annotations cannot compensate for missing, redirected or materially different alternate pages.
A form works only when the message actually arrives
A success banner in the browser is not enough if the lead never reaches the system or person expected to receive it.
A URL change should not reset the property’s internal history
Why a property can move to a new public URL without losing saved state, verification context, source history or its identity across the product.
A number should never travel without its unit
Why units must stay attached to values through import, comparison, localisation and derived calculations so numerical precision does not become false precision.