The software engineering field was once a closed system where engineers held gatekeeper power due to their specialized knowledge. This expertise allowed them to dictate what was feasible, effectively controlling product development. This "expert power," derived from the difficulty of coding and the illegibility of code, meant that if engineers said something couldn't be built, it wouldn't be. Non-engineers lacked the technical understanding to challenge these decisions, creating an information asymmetry that favored engineering. This dynamic was similar to how a seller with more information can exploit a buyer in a market.However, this era of engineering dominance is being dismantled by the rise of AI. Tools like "vibe coding" enable even non-technical individuals to generate functional software prototypes. This disruption mirrors historical shifts, such as desktop publishing, where increased accessibility to tools didn't immediately confer expertise. The value is shifting from operating the tool to knowing what to do with it. While AI-generated code can be fragile and contain significant technical debt, it serves as a powerful counterexample to the "it can't be done" argument. The ability to create "impossible" things, even imperfectly, challenges engineering's traditional monopoly on feasibility.