• by Michael Dubakov
  • source https://www.mdubakov.me/malleable-software-solid-bases-custom-code/
  • You can’t vibe-code a full OS (yet),
    • … easily vibe-code small apps to solve personal problems.
  • … complex when you add “collaboration” as a dimension.
  • … collaborative use cases. You suddenly need:
    • data storage with relations,
    • concurrent editing,
    • notifications,
    • changes history,
    • permissions, etc.
  • solid base that can be tailored via custom code
  • solid bases
    • … specialized tool without any customization is as solid as it gets,

      • but the lack of customization is exactly what makes it unusable in many cases.
    • … Codex your solid base is almost non-existent, but you have enormous expression power and can build almost whatever you want …

    • … both extremes are suboptimal for the productivity tools market, and we should find a sweet spot somewhere in between.

    • solid base should cover what’s identical for every team, and custom code should cover what makes yours different.

      • Vibe-coding platforms give you a tech base
        • servers, raw database, auth
      • Low-code platforms give you an app base
        • UI components, connectors, access control
      • Malleable tools give you a work base
        • the data itself lives there, together with everything a team needs around the data
  • Custom code
    • … works well only …
      • Permissions, history and data integrity apply to custom code automatically.
      • … cannot corrupt the base …
    • … custom code extensions were hard (think about the Jira plugin ecosystem), but now they can be easy!
      • … malleable software becomes approachable for not-very-technically-savvy users and can beat specialized tools more often.
    • … unite high expression power and short build time.

JD's posts: