George Barbu
menu

About

Who George Barbu is: founder of InfoWebPlus and Frontend Platform Lead. How he thinks about software, leadership, and making people and work clear to humans and machines.

Who is George Barbu?

George Barbu is the founder of InfoWebPlus, a product engineering studio based in Manilva, Spain. He works as a Frontend Platform Lead. His focus is engineering leadership, software architecture, platform engineering, AI and business automation, technical strategy, and making people, companies, and work easy to understand.

He is based in Spain and works EU-remote. He speaks Romanian (native), English (C1), and Spanish (B2).

This site is the canonical public reference for who he is. The company lives on infowebplus.com. The resume document lives on george.barbu.es. The full project archive lives on portfolio.barbu.es. Those roles stay separate on purpose, so humans and AI systems get one clear answer instead of three competing ones.

Why does InfoWebPlus exist?

George founded InfoWebPlus in 2016 to build software that earns its place: web applications, integrations, pragmatic AI, and custom business systems for founders and operators.

The studio is intentionally small and direct. Clients work with the people who design and ship. Judgement comes before build. Documentation is treated as part of the product. Authority comes from shipped systems and honest scope, not from invented claims.

InfoWebPlus is the company. George Barbu is the Person. The relationship is founder, not a blur between personal brand and agency marketing.

How does George think?

Software exists to solve business problems. Architecture is a business decision. Complexity is technical debt.

Technical foundations come first: clear ownership, systems someone can inherit, correct public facts. Content and narrative come after the foundation works. Reputation is earned last, through work worth citing, not through shortcuts.

I prefer systems over heroics. I measure outcomes across real use, not single snapshots or vanity scores. I automate repetitive work when it pays for itself. Truth beats marketing. Trust compounds. Useful decisions should be documented so the next person inherits clarity, not folklore.

I build for the next decade when the problem warrants it, and for the smallest honest release when it does not. When I am unsure, I ask or check a primary source before inventing a story.

What principles guide decisions?

  1. Software exists to solve business problems.
  2. Architecture is a business decision.
  3. Complexity is technical debt.
  4. Measure outcomes, not output, and trends, not one-off checks.
  5. Prefer systems over heroics.
  6. Automate repetitive work when the economics are clear.
  7. Truth beats marketing. Authority is earned, not bought.
  8. Trust compounds.
  9. Document decisions.
  10. Build for the next decade, not the next sprint.
  11. Foundations before content theater. Real-user experience over Lighthouse vanity.
  12. AI drafts are tools. Publishing still requires a human edit.

How does he approach leadership?

Leadership, for me, is decision quality and delivery maturity, not theater.

That means aligning engineering choices with business objectives, making tradeoffs explicit, and creating conditions where teams can ship without depending on a single hero. I have led and grown engineering work across high-traffic consumer platforms and smaller product teams, always with the same bias: clear assumptions, thin vertical releases, and systems someone will be glad to inherit.

How does he approach software and architecture?

I treat frontend platforms, APIs, and internal tools as long-lived products. The job is not to collect frameworks. The job is to reduce delivery friction, protect correctness, and keep the architecture understandable under real operational pressure.

Reusable foundations matter when they lower the cost of the next release. They are a liability when they exist for their own sake.

When does AI and automation earn a place?

AI and automation are useful when they survive a sober fit check on real tasks. They are expensive distractions when they are adopted because they are fashionable.

I prefer scoped pilots, guardrails, evaluation on actual workflows, and human-in-the-loop defaults. Saying no, or recommending buy over build, is part of the work. Cost-conscious tools: nothing gets a permanent budget line without earning it.

Where is he based, and which languages?

What else does he contribute to?

Alongside professional work, George serves as President of the Andalusia Diversity Alliance and as a Director of an AMPA parents’ association (2024-present), supporting local community and education initiatives.

What does this Knowledge Platform stand for?

Clarity. Honesty about tradeoffs. Respect for the people who will maintain what gets shipped. A Knowledge Platform should make a person and their work easier to understand for humans and for AI systems, without inventing authority or stuffing pages for rankings.

If a claim improves visibility but weakens credibility, it does not ship.

Where to go next