Lean-Coders

Lean-Coders Experts in web based fullstack solutions using Angular/React/Vue/Node/TypeScript

Die Mission von LEAN-CODERS®, ist es qualitativ hochwertige Software zu kreieren und Beratung auf Augenhöhe zu gewährleisten.

Good AI governance isn't a 40-page policy document but it's usually three things, done consistently.We've tackled this i...
25/08/2026

Good AI governance isn't a 40-page policy document but it's usually three things, done consistently.

We've tackled this in our last posts, and after talking to a lot of companies recently, we can confidently say what usually goes wrong when companies adopt AI without a plan. Fair, but it's worth flipping the lens: what does it actually look like when a company gets this right?

One approved path, not zero paths. Teams don't stop looking for AI tools because you ban them, they go find one anyway. Pick a secure, sanctioned option and make it the easy default.
One rule everyone can actually remember. Not a legal doc nobody reads. One clear line: what can go into an AI tool, and what can't.
Regular check-ins, not a one-time sign-off. AI tools and their data terms change fast. Review them the same way you'd review any other software.

That's it. No dedicated compliance department required for most mid-size companies.

The difference between companies that get burned and companies that don't usually isn't caution. It's whether these three things exist at all, versus being figured out for the first time after something already went wrong.

Where does your company sit on this? Have all three, some, or none yet?

If this sounds like a gap in your setup, we put together a short workshop on exactly this: 👉 https://lean-coders.at/ki-workshop-kits

18/08/2026

A lot of "open source" products only open the part that gets them the community, then lock down everything else. 🔐

Our CEO Christoph Ott breaks down why that's not open source, it's plain marketing. True open source means you can fork the code, extend it, and shape it. It means the architecture itself stays open, not just a slice of the codebase.

And if you know Christoph, you know that he is not the one to hide behind some words, and indeed he mentions Plane in this example, sharing why he disagrees with the whole concept.

We build on this principle because agility only works with open standards. Closed doors don't scale, no matter what you call them.

Where do you draw the line between "open source" and "open-source-flavored"?

If you haven't read Chris's full interview yet, make sure to head over here it's full of gems. https://bit.ly/4yPivf0

12/08/2026

Christoph Ott 𝗱𝗼𝗲𝘀𝗻'𝘁 𝗷𝘂𝘀𝘁 𝗯𝗲𝗹𝗶𝗲𝘃𝗲 𝗶𝗻 𝗢𝗽𝗲𝗻 𝗦𝗼𝘂𝗿𝗰𝗲. 𝗛𝗲 𝗹𝗶𝘃𝗲𝘀 𝗶𝘁.
And you can hear it the moment he talks about what happens when a problem hits and you actually have the key to fix it.

📖 Full interview on the blog: https://bit.ly/OpenSource-Bedeutung

A junior consultant pasted a client's financial report into ChatGPT to "make the summary sound better." 𝐍𝐨𝐭𝐡𝐢𝐧𝐠 𝐦𝐚𝐥𝐢𝐜𝐢𝐨𝐮...
10/08/2026

A junior consultant pasted a client's financial report into ChatGPT to "make the summary sound better." 𝐍𝐨𝐭𝐡𝐢𝐧𝐠 𝐦𝐚𝐥𝐢𝐜𝐢𝐨𝐮𝐬. 𝐉𝐮𝐬𝐭 𝐓𝐮𝐞𝐬𝐝𝐚𝐲.

That's shadow AI. And most companies have no idea how much of it is happening inside their own walls.

Here's the thing about shadow IT's new cousin: it doesn't look like a security breach. It looks like productivity.

👉 A recruiter pastes candidate CVs into an AI tool to draft rejection emails faster.
👉 A developer feeds proprietary code into a free coding assistant to debug it.
👉 A marketer uploads a competitor's leaked deck to "analyze the positioning."
👉 Someone in finance summarizes an unreleased earnings report because the AI tool is just sitting right there in the browser.

𝐍𝐨𝐧𝐞 𝐨𝐟 𝐭𝐡𝐞𝐬𝐞 𝐩𝐞𝐨𝐩𝐥𝐞 𝐭𝐡𝐢𝐧𝐤 𝐭𝐡𝐞𝐲 𝐝𝐢𝐝 𝐚𝐧𝐲𝐭𝐡𝐢𝐧𝐠 𝐰𝐫𝐨𝐧𝐠. They didn't. They just didn't know the tool's terms of service, where the data goes, or whether it gets used to train the next model. Or maybe they just didn't think too much into it.

The uncomfortable truth: by the time this shows up in a security audit, it's not one incident but a pattern that's been running for months.

The fix isn't "𝐛𝐚𝐧 𝐀𝐈 𝐭𝐨𝐨𝐥𝐬." That just pushes it further underground.

The fix is:
🟢 Give people an approved, secure alternative before they go find their own
🟢 Make the data policy for that tool one sentence anyone can understand 🟢 not a 40-page ToS
🟢 Treat "know what your team is actually using" as a basic operational question, not an IT afterthought

The companies that get burned aren't the ones using AI. They're the ones who found out about their AI usage after something already went wrong.

Has your company mapped what AI tools are actually being used day to day or is it still an educated guess?

𝗦𝗼𝗺𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗮𝗿𝗲 𝘄𝗼𝗿𝘁𝗵 𝗽𝗶𝗰𝗸𝗶𝗻𝗴 𝘂𝗽 𝗶𝗻 𝗽𝗲𝗿𝘀𝗼𝗻. 🤝A few weeks ago we announced our official partnership with Vendure, somethi...
07/08/2026

𝗦𝗼𝗺𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗮𝗿𝗲 𝘄𝗼𝗿𝘁𝗵 𝗽𝗶𝗰𝗸𝗶𝗻𝗴 𝘂𝗽 𝗶𝗻 𝗽𝗲𝗿𝘀𝗼𝗻. 🤝
A few weeks ago we announced our official partnership with Vendure, something we are incredibly proud of. Last week, David Höck went one step further and shared here on LinkedIn a framed certificate to celebrate the moment. More than something to hang on a wall, it is a recognition of years of work, trust, and a shared vision.

Because this partnership did not start with a contract. It started with conversations, early ones, when Vendure was still at its very beginning, and we believed in it from day one.
Florian Bacher, Co-CEO at LEAN-CODERS, stopped by the Vendure office to pick it up in person. That certificate is now hanging in our office in the third district. Right where it belongs. 🖼️

To Michael Bromley, David Höck, Max Page and the entire Vendure team, thank you for building something worth believing in from day one.

05/08/2026

Ask Simon Eckerstorfer why he loves building with Flutter, and he'll happily admit it: 𝐡𝐞'𝐬 𝐚 𝐛𝐢𝐭 𝐨𝐟 𝐚 𝐟𝐚𝐧𝐛𝐨𝐲.
For him, it comes down to three things:
▪️ 𝐓𝐡𝐞 𝐝𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫 𝐞𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞: it's simply fun to build with, and that's exactly what he keeps hearing from other developers too.
▪️ 𝐓𝐡𝐞 𝐜𝐨𝐦𝐦𝐮𝐧𝐢𝐭𝐲: the vibe at Flutter meetups is just different. People are there because they genuinely want to build, not because it's their job.
▪️ 𝐎𝐧𝐞 𝐜𝐨𝐝𝐞𝐛𝐚𝐬𝐞, 𝐞𝐯𝐞𝐫𝐲 𝐩𝐥𝐚𝐭𝐟𝐨𝐫𝐦: build for Android, compile for Windows, tweak a few layout details, ship for web.
But ""𝘪𝘵'𝘴 𝘧𝘶𝘯 𝘵𝘰 𝘸𝘰𝘳𝘬 𝘸𝘪𝘵𝘩" isn't a strategy on its own.
So in the article, Simon Eckerstorfer and Stefan Wöhrer connect that enthusiasm to the decisions CTOs and tech leads actually have to make:
🔹 Native vs. cross-platform: when each approach makes sense
🔹 The 3 decision criteria: time-to-market, maintainability, performance
🔹 Flutter vs. React Native vs. MAUI, compared directly
🔹 Why Flutter has become the first choice for many companies
🔹 Which projects benefit most from cross-platform development
👉 Read the full article: https://bit.ly/4wS3gjN

Your employees are already using AI. The question is whether anyone approved it.We've talked to a lot of companies latel...
03/08/2026

Your employees are already using AI. The question is whether anyone approved it.

We've talked to a lot of companies lately, and a pattern keeps showing up:

Someone on the team finds a great AI tool. It saves hours. Word spreads. Within weeks, half the department is using it — pasting in client emails, contracts, code, internal reports, whatever gets the job done faster.

Nobody asked IT. Nobody checked the vendor's data policy. Nobody knows if that data is now sitting on a server in a country your company has no legal standing in.

Do you think this is a hypothetical? Think again. It's the default path AI adoption takes inside most companies right now, since the tools are frictionless and the risks are invisible until something goes wrong.

A few questions worth asking this week if you haven't already:

→ Do you know which AI tools your team is actually using — not just the ones you rolled out officially?
→ If a customer asked "where is our data processed, and by whom," could you answer confidently?
→ Is there a difference in your company between "AI tool we approved" and "AI tool someone downloaded"?

The companies that get this right aren't the most cautious ones, instead they're the ones who built the guardrails early, before speed and safety became a trade-off.

Curious how this shows up at other companies — is AI usage in your org something IT tracks, or something that just... happens? If you dare to answer...

31/07/2026

𝗦𝗼𝗺𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗯𝗲𝘀𝘁 𝘁𝗵𝗶𝗻𝗴𝘀 𝘄𝗲 𝗵𝗮𝘃𝗲 𝗯𝘂𝗶𝗹𝘁 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝗮𝘁 𝗮 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆 𝗲𝘃𝗲𝗻𝘁. 💙

We host and sponsor events because we genuinely believe in the power of getting people in the same room. You meet someone, you hear about their passion, their project, sometimes you get to witness the very first steps of something that later becomes something big.

That is exactly what happened with Vendure and Michael Bromley. 🤝

Today we are proud to share a piece of that story. In this video, Florian Bacher, CEO of LEAN-CODERS, and Julian Pufler, one of our Software Engineers, talk about how that community connection turned into an official partnership, and why LEAN-CODERS is now the official Vendure partner in Austria.
Watch the full story https://youtu.be/DEACD5HbQdY?si=opKDNw79CiY8ouY4

27/07/2026

𝗗𝗼 𝘆𝗼𝘂 𝗸𝗻𝗼𝘄 𝘄𝗵𝗮𝘁 BMW Group , Alibaba Group 𝗮𝗻𝗱 eBay 𝗵𝗮𝘃𝗲 𝗶𝗻 𝗰𝗼𝗺𝗺𝗼𝗻?

No? Well, Simon Eckerstorfer and Stefan Wöhrer answer that for you. 🎙️

And once you know the answer, there's still one question left for you to answer: if it's good enough for them, why not for you?

💡 Want to find out if it fits your project? We run a free workshop, drop us a message! https://bit.ly/44EUcmw

𝗢𝗻𝗲 𝗱𝗮𝘆, 𝘁𝘄𝗼 𝘁𝗲𝗮𝗺𝘀, 𝗮𝗻𝗱 𝗮 𝘄𝗵𝗼𝗹𝗲 𝗹𝗼𝘁 𝗼𝗳 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴.This year's 𝐋𝐄𝐀𝐍-𝐃𝐚𝐲 was a first for us: we spent it together with marqa...
21/07/2026

𝗢𝗻𝗲 𝗱𝗮𝘆, 𝘁𝘄𝗼 𝘁𝗲𝗮𝗺𝘀, 𝗮𝗻𝗱 𝗮 𝘄𝗵𝗼𝗹𝗲 𝗹𝗼𝘁 𝗼𝗳 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴.
This year's 𝐋𝐄𝐀𝐍-𝐃𝐚𝐲 was a first for us: we spent it together with marqably, who recently moved into our office. What began as our internal day of learning turned into something better, 𝐭𝐰𝐨 𝐭𝐞𝐚𝐦𝐬 𝐬𝐡𝐚𝐫𝐢𝐧𝐠 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞, 𝐪𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 𝐚𝐧𝐝 𝐢𝐝𝐞𝐚𝐬.

𝐓𝐡𝐞 𝐦𝐨𝐦𝐞𝐧𝐭𝐬 𝐭𝐡𝐚𝐭 𝐬𝐭𝐚𝐲𝐞𝐝 𝐰𝐢𝐭𝐡 𝐮𝐬:
👉An honest look back at the first half of the year, the highs and the lows. Doing both out loud, and together, is what actually builds trust.

👉An open "𝐀𝐬𝐤 𝐮𝐬 𝐚𝐧𝐲𝐭𝐡𝐢𝐧𝐠" with Christoph Ott, CEO & Founder of LEAN-CODERS, and Simon Auer, CEO & Founder of . Real questions, real answers. Because two teams with their own identities were in the room, the conversation reached beyond our own four walls. Hearing how another company 𝐰𝐫𝐞𝐬𝐭𝐥𝐞𝐬 𝐰𝐢𝐭𝐡 𝐭𝐡𝐞 𝐬𝐚𝐦𝐞 𝐬𝐞𝐭𝐛𝐚𝐜𝐤𝐬, 𝐚𝐧𝐝 𝐜𝐞𝐥𝐞𝐛𝐫𝐚𝐭𝐞𝐬 𝐭𝐡𝐞 𝐬𝐚𝐦𝐞 𝐤𝐢𝐧𝐝𝐬 𝐨𝐟 𝐬𝐮𝐜𝐜𝐞𝐬𝐬𝐞𝐬, was a reminder that no team has it all figured out, and that's completely normal.

👉Talks that got people thinking.
A hands-on success case that showed the impact of the work.
A genuine declaration of Flutter love.
And with Simon Auer in the house, 𝐨𝐧𝐞 𝐨𝐟 𝐀𝐮𝐬𝐭𝐫𝐢𝐚'𝐬 𝐥𝐞𝐚𝐝𝐢𝐧𝐠 𝐀𝐈 𝐞𝐱𝐩𝐞𝐫𝐭𝐬, we couldn't miss a deep dive into AI, followed by the amazing workshop Christina Rohrmoser organised for all the teams.

The real takeaway wasn't in any single session. It was the reminder that 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞 𝐠𝐫𝐨𝐰𝐬 𝐟𝐚𝐬𝐭𝐞𝐬𝐭 when you stop guarding it and start sharing it, especially across teams that don't usually sit at the same table.

Thanks to our team, to marqably, and to everyone who made the day what it was. Swipe through to see how it went.

Adresse

Hainburger Straße 33
Meidling
1030

Benachrichtigungen

Lassen Sie sich von uns eine E-Mail senden und seien Sie der erste der Neuigkeiten und Aktionen von Lean-Coders erfährt. Ihre E-Mail-Adresse wird nicht für andere Zwecke verwendet und Sie können sich jederzeit abmelden.

Service Kontaktieren

Nachricht an Lean-Coders senden:

Verknüpfungen

Teilen