Jens Neuse | Founder @ WunderGraph
@TheWorstFounder
Followers
2K
Following
3K
Media
579
Statuses
6K
Founder of @wundergraphcom - Building Cosmo to manage federated GraphQL APIs - https://t.co/jt9wdBtOz8 - Meet: https://t.co/Uf4l5qaQI3
Germany
Joined June 2019
The job is not to build what people ask for. It’s to find the pain-point and take the risk of building something better.
1
0
3
You can’t ask someone how to improve API workflows. You can only ask them what problems they're running into.
0
0
2
Lee really shaped what we know today as web dev. He redefined what developer advocacy means. Helped make Next.js what it is. I’ve got a lot of respect for him. Did a great job. Congrats, Lee - excited to see what’s next.
0
0
1
You write 100 lines a day. AI helps with 50. But now you’re shipping 100 lines instead of 50. Are they better? Or just more?.Every line of code is a liability.
0
0
3
GraphQL is great. But Subgraphs don’t have to be manually written. Ours are compiled from gRPC definitions. Faster, typed, and zero glue code. It works because gRPC is the source of truth.
0
0
2
We never planned to replace GraphQL Subgraphs. But we kept asking:.Why write glue code around services that already exist?.So we built a compiler. It turns gRPC services into fully typed Subgraphs. No wrapper. No duplication. Just the graph.
0
1
2
Collaboration across frontend, backend, design, product, and platform shouldn’t feel like duct tape. We threw it all out and started from scratch. A lot of hard lessons. But now, it’s taking shape.
0
0
1
We've worked with some of the world’s largest enterprises. It’s not the code that slows things down. It’s the org chart.
0
0
3
WunderGraph helps teams ship faster and more securely. Not by replacing legacy systems, but by removing friction.
0
0
3
You can modernize the stack all you want. If developers are scared to ship, nothing changes.
0
0
2
Left side: Just copy Apollo.Right side: Just copy Apollo.Middle: Do some super sophisticated whatever. Accept that you're a small startup and play the small startup role.
1
0
1
AI won’t solve the core blockers inside enterprises. Because the blockers aren’t technical, they’re organizational.
0
0
3
The DX is simply amazing. Define Subgraph SDL, compile to proto, generate stubs in language of choice, done. No Subgraph Frameworks, just gRPC. Early tests show up to 10x performance improvements, which makes sense given that GraphQL cannot compete with a binary protocol.
1
0
4
For quite some time we wanted to make @apollographql Federation easier to use, strictly typed and more performant. So we built a Subgraph SDL to gRPC compiler, removing #GraphQL completely from the service layer. The results speak for themselves.
2
0
5
The team is joining me in Germany this weekend. Some alignment, some bonding. Both are important when you're moving fast with new projects on the horizon.
1
0
2
It's impossible to find someone complaining about GraphQL in 2025 who read the spec, understands the background of the query language, is aware of best practices like persisted operations as well as understands how most enterprises use Federation with GraphQL. If you're still.
2
0
13
You write some code. It works. You’re proud. Then a PR comment hits and it stings. This is normal, but dangerous. Attachment to the solution blinds you to the problem. In Federation, that mindset breaks fast. You’re either aligned, or you’re blocked.
0
0
0
The real win is:.Write tests in plain English. Save 10 hours. If your hero doesn’t say that, start over. Velocity needs clarity.
0
0
2