Dreamer. From Silicon Saxony to Silicon Valley to Isar Valley. Enjoys transitioning ML R&D concepts into production. ❤️ Languages, food, sports, 80's. She/Her
One of the most common mistakes I see from subscription apps?
Making the free product ~too~ good.
Many founders say they'll change the paywall to optimize conversion later on, but that’s hard to do. Here’s why ⬇️
@johncutlefish A: siloing with periodic large sync meetings; delays or changes are communicated late; more "following the plan"; complain about dependencies
B: more collaboration than A and fewer meetings; transparent realtime communication; more "inspect and adapt"; complain about less focus
Everyone wants to learn how to code.
But coding is secondary.
Your ability to analyze a problem is the most important skill you can build.
(Writing code is easy; most of the work is understanding what problem to solve and how to do it elegantly.)
One of the ML mistakes that you will hurt you the most: not collecting the right features. If the information you need isn't in your data, you won't recover it with a better model.
Gestern Abend hat @ZelenskyyUa bei den Filmfestspielen in Cannes eine Rede gehalten. Es war bereits seine 150. Ansprache seit Beginn des Krieges. Rhetorikexperte @rhetrocks sagt in der @SZ, dass Selenskij den Verlauf des Krieges damit beeinflusst hat. Wie macht er das? 🧵
Software engineering: 50% understanding requirements, 40% complexity management, 9% debugging, 1% solving "interesting" algorithmic problems.
You'll enjoy software engineering a whole lot more if you instead think of the first 99% as the interesting part.
Vor der russischen Invasion war Mariupol eine florierende Großstadt, jetzt liegt sie in Trümmern. @fin et al @SZ haben Satellitenbilder ausgewertet, die das Ausmaß der Zerstörung zeigen - und erklären, warum Angriffe auf urbane Zentren oft so brutal sind. https://t.co/vM042JYcef
This can impede finding the right solution or architecture and creates dependencies too early. And then you end up with that giant software project with all involved teams tightly coupled, spending too much time in sync meetings, slow progress and meaningless deadlines. No fun.
When creating vertical prototypes (German: Durchstich) focus on the learning and then do the right thing to build your product or feature.
Often, engineers and managers desperately hold on to the prototype and treat it as an early version of the final product.
Most people suck at managing up.
They waste their boss’ time with too much (or too little) information.
Here’s how to give the right amount of context: