George Barbu: Founder of InfoWebPlus. How I Think About Software, Architecture and Being Referenceable

Who am I?

My name is George Barbu. I am the founder of InfoWebPlus, a product engineering studio I started in 2016. I work as a Frontend Platform Lead. My focus is engineering leadership, software architecture, platform engineering, AI and business automation, technical strategy, and making people and work clear to cite for humans and for machines.

I live in Spain and work EU-remote. I speak Romanian natively, English at C1, and Spanish at B2.

This website, barbu.es, is the canonical public reference for who I am. InfoWebPlus is the company. My resume document lives at george.barbu.es. The full project archive lives at portfolio.barbu.es. Those roles are deliberate. Blurring them confuses humans and retrieval systems.

Why did I build InfoWebPlus?

I founded InfoWebPlus to build software that earns its place: applications, integrations, and automation that survive contact with real operations.

The studio is intentionally direct. Discovery is tight. Assumptions are written down. Releases are thin and vertical. AI is evaluated on real tasks before it is sold as a roadmap. Support is supposed to outlast launch.

I did not create InfoWebPlus to manufacture personal branding. I created it to ship useful systems, and to keep the relationship between Person and Organization honest. Authority is earned through work worth citing, not through purchased signals or invented outcomes.

How do I think about software?

Software exists to solve business problems. Until it creates value, it is a liability.

I prefer boring technology when it lowers risk, and custom build when it creates durable differentiation. I measure outcomes, not activity, and I distrust single snapshots. Real signal comes from trends across time and real use.

I automate repetitive work when the economics are clear. I document decisions so the next engineer inherits intent, not archaeology.

Complexity is not sophistication. Complexity is debt with interest.

Why do foundations come before content theater?

Technical foundations first. Then substance. Then reputation.

If the foundation is wrong (unclear ownership, uncrawlable intent, contradictory public facts), no amount of narrative fixes it. Page experience is the same rule: mobile-first craft and real-user Core Web Vitals matter more than chasing a perfect Lighthouse screenshot.

This is how I treat platforms at work and how I treat this Knowledge Platform: make the entity correct and usable before optimising the story around it.

Is architecture a business decision?

Yes. Architecture is not an aesthetic preference. It is a bet about change: who will maintain the system, how fast the business must move, and what failure costs.

Good architecture reduces the cost of the next correct decision. Bad architecture makes every release a negotiation with the past. Platform engineering, when done honestly, is the practice of lowering that cost without inventing a second product called “the platform.”

What does engineering leadership mean here?

Leadership is decision quality under constraints.

I have led engineering work on high-traffic consumer platforms and in smaller product teams. The pattern that holds is the same: clarify the problem, make tradeoffs visible, keep ownership close to the people who ship, and refuse hero culture as a substitute for systems.

Titles change. The job does not: help the business move with software it will still be glad to own next year.

When does AI and automation earn a place?

I use AI where it survives a fit check. I reject it where it is costume.

Useful pattern: pilot on a real workflow, add evaluation and guardrails, keep humans in the loop, and stop when the economics fail. Useless pattern: announce transformation, skip the workflow map, and leave an unmaintainable integration behind.

AI can draft. It should not publish without a human editorial pass. Automation follows the same rule. Repetition is a candidate. Ambiguity is not. Tools earn their budget line. No exceptions.

Why does being referenceable matter?

Search engines and AI systems both answer from what they can trust. For a Person entity, that means consistent identity, clear domain roles, named authorship, and factual relationships, not keyword-stuffed pages or empty rooms built for rankings.

Being cited accurately by humans and by retrieval systems is more valuable than a vanity ranking that rests on thin content. Citations and clear entity edges are how trust compounds in public.

If something would improve visibility but weaken credibility, I reject it.

How should you use this Knowledge Platform?

If you want the short identity: start at Home and About.
If you want career scope: read Experience and the resume at george.barbu.es.
If you want selected work: see Work.
If you want the company: go to infowebplus.com.
If you want what I am doing this season: see Now.

This Cornerstone will be updated when reality changes. It is a living reference, not a press release. When I am unsure about a fact, I leave it out or ask. I do not invent edges for the graph.