Joined December 2011
24 Photos and videos
Philipp Häfelfinger retweeted
📸 @Haefelfinger 📸 @Eosandy 📸 Me
1
6
97
Philipp Häfelfinger retweeted
1
5
14
458
Philipp Häfelfinger retweeted
3
12
2,511
Philipp Häfelfinger retweeted
4
11
2,727
Philipp Häfelfinger retweeted
25 Apr 2024
Der Entscheid ist gefallen: Sieg im #Glasfaserstreit! -> was nun: AUSBAU!!!📢 An mehr als 260PoP's sind wir nun vertreten in der CH, weitere 180Standorte sind in der Realisierung-> Check wann du, nicht überbuchte, ungeteilte Bandbreite für dich ganz allein erleben darfst 🥳🐇
27 Jul 2022
4
5
34
3,217
Philipp Häfelfinger retweeted
25 Apr 2024
WEKO-Entscheid: Sieg im #Glasfaserstreit! 💪 Swisscom darf Glasfasernetz nicht monopolisieren. Mehr Infos in unserer Medienmitteilung: init7.net/de/news/
13
34
134
20,349
Philipp Häfelfinger retweeted
Liebe Leute in der Community, es bedeutet mir viel, dass ihr hinter Init7 steht und uns unterstützt im Kampf gegen das Monopol, die PR-Maschinerie des Gegners, einen Grossverlag, der die Wahrheit biegt. Bitte teilt den Text. Reichweite ist wichtig. 🙏 linkedin.com/posts/fredykuen…
4
76
131
7,335
Philipp Häfelfinger retweeted
«Da gibts ja Leute, die haben so Boxen zuhause, Alexa und Hey Siri und so weiter … [boink] … dieses Zeugs, das hört dir einfach zu, da musst du dir keine Illusionen machen, das musst du einfach ausstecken!»
1
7
19
2,597
Philipp Häfelfinger retweeted
Abt. #Kabelaufklärung. Der Bundesrat behauptete, es gäbe keine Massenüberwachung durch den Staat. Das Gegenteil ist der Fall, wie @adfichter / @RepublikMagazin recherchierte. republik.ch/2024/01/09/der-b…
11
40
105
9,483
Philipp Häfelfinger retweeted
Lehren des Trainings für den Alltag – Swipe weiter um mehr zu erfahren 👉 #SKEMA #Kampfkunst #Selbstverteidigung #Kampfkunstschule instagr.am/p/C0uP_vvykOj/
2
3
58
Philipp Häfelfinger retweeted
3 Nov 2023
A recipe for frustrating developers: 🚫 Require a slow VPN or slow remote virtual machine to work. 🚫 Forbid changing most things. We must accept painful, slow, difficult, outdated processes. 🚫 Provide unclear or constantly changing requirements. 🚫 Don’t trust their judgment. 🚫 Create a highly political environment. 🚫 Hire incompetent people, freeloaders, and jerks. Then, ignore the people issues that occur. 🚫 Micromanage. Try to dictate precisely how people do their job. Require management approvals for every release. 🚫 Be cheap. Use old, slow hardware and software. Be unwilling to spend money to save time.
29
129
843
142,644
Philipp Häfelfinger retweeted
SKEMA-Prüfungssystem für Kinder Kung Fu und Jugend-Selbstverteidigung Blog-Beitrag: skema.ch/skema-pruefungssyst…
2
3
34
Philipp Häfelfinger retweeted
𝗠𝗮𝘀𝘀𝗧𝗿𝗮𝗻𝘀𝗶𝘁 𝗶𝘀 𝗮 𝗴𝗮𝗺𝗲 𝗰𝗵𝗮𝗻𝗴𝗲𝗿 𝗳𝗼𝗿 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗱𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀. And it makes the whole process incredibly simple. It's a .NET library that gives you all the tools you need to build modern distributed systems. The core concept of any messaging library is messages. A message can be a record, class, or interface. It should only contain data properties. The publisher and consumer need to know the message format, so you need to be able to share it. You can do this with a shared library or a NuGet package. After that, pick one of the supported transport mechanisms for messages. You can use several different transports: - Azure Service Bus - Amazon SQS - RabbitMQ - Kafka - In Memory* I encourage you to try it if you haven't had a chance to use it before. You'll be blown away by all the supported features. P.S. If you liked this, consider joining The .NET Weekly - my newsletter with 28,000 engineers that teaches you how to improve at .NET and software architecture. Subscribe here → milanjovanovic.tech Did you use MassTransit before?
10
61
356
54,557
Philipp Häfelfinger retweeted
2 Dec 2022
Da wir immer wieder gefragt werden, wie es denn jetzt beim #Glasfaserstreit weiter gehe, hier der aktuelle Stand. Danke @simonschlauri! ✅ #P2PvsP2MP
2
10
44
Philipp Häfelfinger retweeted
How can you use Feature Flags in .NET? It's only a few lines of code. Here's how. 👇 Feature flags are used to turn features on or off in your application without redeploying the code. Here are 4 simple steps to get started: - Install `Microsoft.FeatureManagment` - Register feature management services - Define your feature flags in `appsettings.json` - Check the feature flag state using `IFeatureManager` Sounds simple? Great, but we only scratched the surface of what's possible. Now, you need to learn about feature filters, phased rollouts, and A/B testing... Yesterday, 28,713 engineers learned to work with feature flags in .NET. If you missed the issue, you can grab it below. 👇 milanjovanovic.tech/blog/fea…
9
48
293
46,987
Philipp Häfelfinger retweeted
Selbstverteidigung als Teamevent - Kampfkunst für Firmen Blogpost: skema.ch Melde dich bei deiner lokalen SKEMA Kampfkunstschule, falls du mehr über Selbstverteidigung als Teamevent erfahren möchtest.
2
3
47
Philipp Häfelfinger retweeted
27 Aug 2023
Scrum is a cancer. I've been writing software for 25 years, and nothing renders a software team useless like Scrum does. Some anecdotes: 1. They tried to convince me that Poker is a planning tool, not a game. 2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing. 3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention. 4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint. 5. I had to use t-shirt sizes to estimate software. 6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points." 7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this. 8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously. 9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind. I believe in Agile, but this ain't agile. We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it. The result was always the same: It didn't work. Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control. But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team." Sure it is.
2,027
4,327
24,966
4,846,630