Michael Bromley

If you delete the issue template I will find you

Just got the last part of my mini pedal board. It's literally everything I need: octaver, Rat-style distortion, delay/reverb, looper/drum machine.

With this combination I can do all music.

Last night at @viennajs.bsky.social: give a talk about dotfiles and key bindings and you are guaranteed to be swarmed by devs for the rest of the night 😂

Great talk by our new @vendure.io team member Housein 👏

And overall the excitement is the far stronger feeling.

Today I'll be building more of the new @vendure.io dashboard at 10-50x the speed of my younger self. 🚀

It fills me with both dismay and excitement 😂

Dismay at the "lost" hours, days, weeks.

Excitement at the realization that during that process I learned deep fundamentals that newcomers may now have little incentive or opportunity to master.

I think back to the hours of my life spent painfully trying to figure out how to make JavaScript work.

Copy-pasting from random forum posts. This was even before Stack Overflow (RIP). Yes I'm that old.

And I compare it to the velocity I now have using AI tooling.

6,666 commits over 7 years of building @vendure.io

that's an average of 3-4 commits *every* work day for the past 7 years.

Consistency. Just show up and get the work done.

The types flow instantly from your GraphQL document, right into your React code, with ZERO waiting on code generation.

Shout out to @jovidecroock.com & @kitten.sh for gql.tada which powers the magic that you see here 🙏

And with our new Dashboard, we're leveraging GraphQL to help you build custom UI with speed and productivity you won't find anywhere else.

First post contains a clip of what it looks like to build a fully type-safe list view.

But after seven years, I'm still glad we chose GraphQL.

The unmatched DX of Vendure would simply not be possible without it:

- Type safety from backend to frontend
- Extend any response with custom fields
- Dynamic, type-safe sort & filter on all list queries

Sometimes I hear that it was a mistake to build
@vendure.io on top of GraphQL.

"Too complex", "Can't be cached", "Poor performance", "It was all hype"

Yes, every technology has its tradeoffs. I'm keenly aware. There *are* some aspects you need to be mindful of when working with GraphQL.

Not explored that yet. We have much simpler requirements for the back end part.

Yes, of course we did, what else?!

github.com/vendure-ecom...

In every case, no matter how ambitious my requirement - Vite made it positively *intuitive* to implement.

Bravo to @evanyou.me, @rich-harris.dev and the whole Vite team & community for producing this beautiful piece of software 👏

➔ Automatic type safety from GraphQL _without_ a codegen step
➔ Auto-generated list & detail view based on your GraphQL queries
➔ Dynamic components that adapt to the exact data types in your custom schema

In our case, we're using it to power our brand-new React-based dashboard. I've gone pretty deep building out some very cool Vite plugins that really make it feel magical to build UI extensions to your Vendure app.

Look, I've been around a while & remember when we used to bundle with Grunt, then Gulp, then Webpack. So isn't Vite just an incremental take on what has gone before?

No - Vite has something that makes it magical. An absolutely sublime plugin API that feel like you can build *anything* with it.

> @vite.dev is my new favourite thing. If you're a @vendure.io developer it's gonna become your new favourite thing too, very soon!

I was vaguely aware that it was slowly taking over the frontend world - every framework seemed to use it for some reason.

silent @ climax of night @silentho...6dv when the race war is happening and I gotta kill tony hawk Tony Hawk @tonyhawk Replying to @silenthooper I appreciate the hesitation though 10/30/18, 7:18 AM

I don't always get this perfectly right, still. But I can promise you that for Vendure developers I am fighting to bring simplicity to the often complex and over-engineered world of enterprise commerce.

It's all fun and games until, 6 months later, you need to debug something and proceed to spend 5 hours figuring out what the hell is even supposed to be happening here.

This message is brought to you by 7 years of hard-won lessons building @vendure.io

Could it have been a for loop? Could it?

If it could have been a for loop, please write a for loop.

This manifests in devops as things like ridiculously complex constellations of services and (gasp) microservices to power an app that could have run on a consumer pc.

But whenever you get the urge to bound over to your colleague to explain your incredibly clever solution, and get a pat on the head and a "good dev!"...

"look, by using partial application and meta-programming we can dynamically construct a pipeline of operations that..."

Every developer goes through that phase where they get drunk on their own mastery over complexity. On their own damn cleverness. I most definitely have been there!

And yes, some problems contain *inherent* complexity.

There's one lesson that has taken me years to *really* learn in software development:

Simplicity should be prized above all other things.

Simple code. Simple logic. Simple dependencies. Simple deployments.

OMG what. The web dev stuff is cool and all but now you truly have my respect.

Wait is this survival?

I love building stuff for developers.

Here's what's coming in the new @vendure.io dashboard:

“This is how big the pile of money is I got from my dad to work on open source” 😂

YouTube video by HalfStack Events You Aren't Gonna Need It...Until You Are?

𝐍𝐨𝐭 𝐞𝐯𝐞𝐫𝐲𝐭𝐡𝐢𝐧𝐠 𝐢𝐧 𝐭𝐞𝐜𝐡 𝐧𝐞𝐞𝐝𝐬 𝐚 𝐛𝐚𝐭𝐭𝐥𝐞.

@michlbrmly.dev reminded us at HalfStack Vienna that “it depends” is a valid answer ✌️

Watch his talk: youtu.be/WBpzS36-eIc

Submit your CfP for Vienna 2025! 🔗 halfstackconf.com/vienna

#TechWithoutTribalism #HalfStackEvents