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 Thinking Still Matters More Than Tools

Tools amplify thinking but cannot replace it. The capacity to reason precisely remains the irreducible foundation of effective technical work.

ProgrammingTechnology
54 1 0
Read more

Why AI Won’t Save Bad Architecture

AI can speed up coding inside a well-structured system, but it cannot repair fundamental architectural flaws. AI won't fix misorganization, it will only accelerate and amplify it.

Artificial IntelligenceProgramming
60 2 0
Read more

Automation Amplifies Design Decisions — Good and Bad

Automation accelerates the impact of design decisions, and its benefits are realized only when the underlying architecture is sound; otherwise, automation quickly magnifies existing problems.

TechnologyArtificial Intelligence
68 1 0
Read more

LLMs Don’t Understand — And That’s Fine.

LLMs repeat human knowledge without understanding it. This is not a flaw — it reveals something important about intelligence, meaning, and authorship.

Artificial IntelligenceHypePhilosophy
119 2 0
Read more

Why I Prefer Owning My Stack

Controlling my technology stack grants me autonomy, clarity, and speed. I have found that this approach leads to more robust, adaptable systems and shields me from the risks of vendor lock-in and opaque dependencies.

TechnologyArchitectureProgramming
75 1 0
Read more

Global State vs Provide/Inject in Vue.js

Global State vs Provide/Inject in Vue.js. Both solve different data-sharing problems. Selecting the appropriate strategy depends on scope, scalability needs, and architectural clarity.

ProgrammingVue.js
80 2 0
Read more

The Value of Boring, Predictable Systems

Boring systems outlast clever ones. Predictability reduces cognitive load, enables trust, and compounds value over time in ways that novelty cannot.

ArchitectureProgramming
75 2 0
Read more

Small Teams, Strong Systems

Small teams outperform large ones not through headcount, but through system design. Constraints force clarity, ownership, and feedback loops that scale beyond the team itself.

CultureArchitecture
83 1 0
Read more

When Flexibility Is Actually a Liability

Flexibility in software systems is often mistaken for value. Unconstrained optionality increases cognitive load, defers decisions, and erodes operational consistency.

ArchitectureProgramming
52 1 0
Read more

Custom Software vs Configuring Someone Else’s Vision

Building custom software versus configuring existing platforms is a decision about ownership, constraints, and long-term fit — not just cost or speed.

ArchitectureProgramming
55 1 0
Read more

When “DX” Hurts Real Productivity

Optimizing for developer convenience often masks deeper productivity losses. Real output — shipped features and resolved problems — matters more than frictionless workflows.

CultureProgramming
48 1 0
Read more

The Stack You Inherited Was Not Designed for Your Problem

Inherited stacks encode decisions made for different problems at different scales. I examine what it costs to build inside architecture that was never designed for your context.

Architecture
46 1 0
Read more

Fatal error: Uncaught Error: Class "PCWM\Utils\PCWMPinger" not found in /home/eaaone64/public_html/lib/classes/PCWM/PCWM.php:500 Stack trace: #0 /home/eaaone64/public_html/index.php(34): PCWM\PCWM::end() #1 {main} thrown in /home/eaaone64/public_html/lib/classes/PCWM/PCWM.php on line 500