Eduardo Arsand

Notes & Thoughts Quick thoughts, technical notes, and ideas.

Notes written to clarify my own thinking, share knowledge, explore ideas, and remember important concepts.

All Notes & Thoughts

There are 48 notes in total.

Why Performance Regressed Despite Faster Hardware

Performance can regress on faster hardware when software grows in hidden complexity. Abstractions, data volume, and toolchain overhead outpace raw speed gains.

ProgrammingTechnology
123 1 0
Read more

The Rise of Build Pipelines and the Loss of Directness

Build pipelines introduced powerful automation but severed the direct relationship between source code and runtime output. The cost of that indirection is rarely measured.

ArchitectureProgramming
92 0 0
Read more

Understanding Common Edge Cases in PHP and JavaScript

Edge cases in PHP and JavaScript stem from implicit type coercion and loose equality. Strict comparisons, boundary validation, and explicit type contracts are the primary defenses.

ProgrammingPHPJavascript
113 2 0
Read more

Vendor Lock-in Starts at Hello World

Vendor lock-in starts with defaults, APIs, and habits. I examine how early convenience hardens into dependency and how to preserve optionality.

ArchitectureProgramming
99 1 0
Read more

PHP self:: vs static::

PHP self:: binds to the defining class, static:: respects the calling class (Late Static Binding).

ProgrammingPHP
91 1 0
Read more

When Frameworks Became Products Instead of Tools

Frameworks were born to reduce friction. Somewhere along the way, many became platforms — shaped by adoption metrics, ecosystem lock-in, and brand loyalty more than technical merit.

ArchitectureProgramming
119 1 0
Read more

Understanding Abstraction

Abstraction hides complexity behind simple interfaces, enabling reusable, maintainable, and flexible code while focusing on what something does, not how.

ArchitectureProgramming
111 1 0
Read more

Why Most Websites Didn’t Need Single-Page Apps

SPAs solved collaboration problems but most websites adopted them unnecessarily. Traditional apps better suit content. Unnecessary complexity became technical debt.

ArchitectureProgramming
108 1 0
Read more

Why jQuery Was Never the Problem

A short analysis about how most of the time, blaming the tools is almost never the root cause of poor web development practices. The evolution to modern tools addressed new complexities, but did not retroactively make jQuery the problem.

ProgrammingLibrary
100 2 0
Read more

Frameworks vs Understanding the Web Stack

Relying solely on frameworks can obscure the essential workings of the web. I have found that a strong grasp of the web stack provides the flexibility and insight needed to use frameworks effectively and to build resilient, maintainable systems.

ProgrammingTechnology
113 0 0
Read more

The Hidden Complexity of “Simple” CRUD Systems

CRUD systems hide complexity behind simple operations. Soft deletes, permissions, side effects, and state transitions demand domain-aware design from the start.

ArchitectureProgramming
128 1 0
Read more

PHP Is Not Dead: The Cost of Writing Off Boring Technology

PHP’s reputation as a "boring" technology belies its strengths: stability, simplicity, and a robust ecosystem. Dismissing it for trendier alternatives often leads to unnecessary refactors, creating more problems than solving.

ProgrammingPHP
124 1 0
Read more