Frederic Branczyk

Vercel Ship 2024 Keynote starting now. At the UpLeveled GmbH #nextlevelcodingschool as one of the view coding bootcamps worldwide we always work with the latest Next.js version out there 👩‍💻🚀 https://lnkd.in/dbvTf8yp #vercel #nextjs #next #viennacodingbootcamp #amsterdamcodingbootcamp #stateoftheart #techstack #codingbootcamp #learntocode #learncoding

8

Thanks to everyone who attended "Breathing New Life Into Legacy PHP Applications" talk at the Munich International PHP Conference! My brother David and I had a great time with everyone. Here is a link to the talk: https://lnkd.in/erXRTKbG

5

In her last post, Miriam brought up the concept of user-centricity in the development of APIs. Our training sessions last week made it clear that there is still a long way to go to make an interface available in a needs- and user-centred way and to allow it to develop over time. Requirements are never rigid. But if we dig a little deeper, this user-centred approach is not that easy. In the literature and daily practice, we find providers and consumers. But is this really the reality? In our API Thinking training , we've mapped this out for a simple case. But what if a provider is also a consumer of a third-party API that brings its service forward? And then things get complicated. This is another reason why we need to understand APIs better instead of just building them with the framework of our choice. A big thanks to Marianne for creating the graphic and thanks to Stefanie Schwilski for the idea with the slide. And as you can see, we always work as a team at codecentric AG . #codecentriccrew

16

𝐀𝐧𝐨𝐭𝐡𝐞𝐫 𝐦𝐞𝐬𝐬𝐚𝐠𝐞 𝐟𝐫𝐨𝐦 𝐃𝐞𝐩𝐞𝐧𝐝𝐚𝐛𝐨𝐭... In the past, I would have waived recommendations like this away. Who needs automatic scanning of your repo and getting a recommendation to update libraries? Shouldn’t it be part of your daily business to check news and update all used dependencies from time to time? Why do I need a tool for that? Might be true. When you are deep into your project, this can be fixed yourself in seconds. But I’ve learned to love tools that automate the whole workflow of checking and fixing known CVEs. Especially when a CI pipeline makes sure those changes don't break the product. (On the other hand: better a broken than a vulnerable product, because this creates pressure to fix 😬) Adding tools like #Dependabot to the workflow and using GitLab’s Dependency Scanning can provide peace of mind. These tools can help ensure that things stay efficient and secure by reducing the risk of vulnerabilities slipping through the cracks. #continuousIntegration #bestPractice #vulnerabilityScanning #cybersecurity #github #python #cpp

8

Yes, I'm certainly not a fan of web apps and certainly not of hybrid apps. However, we live in a time where this type of software development for mobile applications is becoming increasingly important in order to reduce costs or reuse existing (web dev) knowledge. That's why I can only congratulate Gerald Versluis (and others) on this really great workshop. With Blazor Hybrid, we native developers can at least get around JavaScript and have all the niceties that the .NET ecosystem brings us in conjunction with C# and Blazor Pages. Chapo for this workshop! #dotnet #csharp #dotnetmaui #maui

13

13 Kommentare

Thanks viesure innovation center GmbH for hosting my blog article "Property Drilling: when best practices become best problems in Declarative UI (Compose, Swift UI)". Feel free to have a look at the company blog here https://lnkd.in/dk3GNqUS or on Medium https://lnkd.in/d7ReiHPQ - enjoy reading!

21

Here at willhaben talking to experts about Architectural Decision Records and how modern software is built 🚀 - with Katrin Freihofner Fabian Friedl Checkout Straion 😉 if you are interested in making smart decisions! #software #decisions #architecture #process

41

Rainer Hahnekamp presents a session titled “The End of Barrel Files: New Modularization Techniques with Sheriff” at #ngPolandConf. In this talk, Rainer explores new modularization techniques for Angular applications, focusing on the potential end of “barrel files”—a common practice used to centralize exports in large codebases. Instead, he introduces Sheriff, a new tool aimed at improving the modularization process by offering a more scalable and maintainable approach for managing Angular application code.

7

2 Kommentare

Nobody wants to spend +𝟭𝟬𝟬𝗸 𝗼𝗻 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀. But many do and 𝘀𝗶𝗴𝗻𝗶𝗳𝗶𝗰𝗮𝗻𝘁𝗹𝘆 𝗼𝘃𝗲𝗿𝗽𝗮𝘆𝗶𝗻𝗴 𝘁𝗵𝗲 𝗮𝗴𝗲𝗻𝗰𝘆 they hired. It's not because the developers they hired were necessarily inexperienced. But the process and pricing were simply off. Many are aware of the downfall of hourly pricing - and ask for fixed pricing. Which is not much better if done poorly. Check this blog post if you want to build software with a tighter budget and still get what you want. We are expensive at first, but only because we save you much more than you spend. Pricing software projects the right way: https://lnkd.in/dQfPwm5P

22

11 Kommentare

I'm very interested in how companies manage to combine business and open source, and this interest has grown since I joined Storyblok. At Storyblok we have an entire team dedicated to open source SDKs, and most of the engineers who build our headless CMS also contribute and maintain our packages. This costs money, of course, and comes with other problems, such as having to maintain not just one product, but a collection of tools exposed to the public, each potentially with its own set of problems and maintenance overhead. Why do we do this? This is not an easy question, and I think many companies and individuals can answer it in different ways. My entire career has been built on open source, so I know many of its benefits, but for a company it's different, and I'm starting to find some interesting answers. For starters, open sourcing our SDKs and tools promotes transparency, allowing developers to understand and trust our integrations. It also fosters innovation through collaboration, leveraging the collective expertise of the global developer community. This accelerates problem solving and creates valuable learning resources for developers at all levels. And engineers are happier when they contribute to open source, which is no small thing. I'm curious, what are your thoughts on the role of open source in business? I will continue my exploration... #opensource #business

17

2 Kommentare

Check out my guided solution for one of my favorite Katas! Learn JavaScript, German and how to properly clean-up after your dog! https://lnkd.in/epwU_VQj Hajime! 🙏 #javascript

6

🌟 New Article Alert! 🌟 I've just published an article on Medium: Demystifying Clean Architecture in Go: Separating Fact from Fiction. 🎉 https://lnkd.in/e6pnqEPz In this piece, I dive into the fascinating (and often misunderstood) world of Clean Architecture, exploring how its principles can be adapted to the simplicity and power of Go. From flat project structures to more elaborate designs, I've included practical examples to illustrate how we can balance clarity, scalability, and testability. Whether you're a seasoned Go developer or just curious about software architecture, I hope you'll find this article insightful and relatable. 💬 I'd love to hear your thoughts, experiences, or even challenges you've faced while applying Clean Architecture principles in your own projects. Let's keep the conversation going! #golang #go #cleancode #cleanarchitecture #softwarearchitecture Check it out and let me know what you think! 👇

6

Open source is eating the world. I wanted to find out what German R&D powerhouses contribute to the movement. Here is what I found by browsing around in Github:   I used a very simple methodology and just tried to find the repo with most stars for each company. As many repos are hosted by specific departments or labs, the list might not be completely accurate. Here are the results (more details in the slideshow): 1️⃣ Cariad/VW: 6 stars 2️⃣ Bosch: 380 stars 3️⃣ Mercedes-Benz: 255 stars 4️⃣ SAP: 2900 stars   🤔   This perspective oversimplifies things: Github stars are a vanity metric, there are many more ways to contribute to FOSS than owning repos and very successful projects might have already been moved to an independent organization such as Apache. But: I think the result is still devastating ‼️ My intention is not to point any fingers. I know from experience that it can be difficult to make the business economics work in the short term. I just think the issue is worth discussing and FOSS is a critical factor in today’s competitive landscape. There are so many advantages of open source, especially for larger organizations: 1️⃣ No vendor lock-in, especially with regards to cloud services 2️⃣ Better efficiency and security than custom solutions 3️⃣ Collaboration opportunities with startups and academia   So, please help me: Which open source success stories from large German corporates do you know (can be collaborations with startups / academia)? What do we have to do to get more of them?   Very much looking forward to learning what’s your perspective on this 👇in the comments ☕during a virtual coffee talk: https://lnkd.in/gjX6tzXJ #opensource #foss #industrialai

34

16 Kommentare

Excited to be at LeadDev Berlin for the first time! Chatting with other lead devs and engineering managers, I've noticed a pattern: Tech decisions: We all struggle with choosing the right stack. It's not just about the coolest tech, but what fits our teams and projects best. People management: As technical folks, we often find the "people" part challenging. Balancing coding time with leadership duties is a common hurdle. Imposter syndrome: Many of us feel we're not 'manager material'. It's reassuring to know I'm not alone in this. It's comforting to realize these aren't unique problems. We're all figuring it out as we go. What's your biggest challenge as a tech leader? #LeadDevBerlin

46

How to improve your code quality! 🏁 At nerdware GmbH, we believe in the importance of setting specific, measurable goals and consistently tracking progress. As a Lead Software Engineer, I work closely with each team member to set quarterly goals, with smaller, achievable goals within the three-month cycle. One important goal we've recently set is to improve code quality. Because it can be very subjective, quantifying this goal fairly was a challenge. To address this, I suggested implementing SonarQube locally. With this static code analysis, which comes with many metrics, we were able to set clear, measurable goals. (This could also serve as a compelling case for the customer to invest in a SonarQube license in the future). I see my role as not only being responsible for a successful project, but also coaching and empowering my team members to improve their skills. Curious about setting up SonarQube locally without a license? Check out my latest blog post for detailed instructions (https://lnkd.in/d-Yn4Z_9).

25

7 Kommentare

Next week, I will be in #Berlin at LeadDev, speaking about #NeurodiversityInTech which is a topic I care deeply about. I will also attend many other great talks, so I am giving a shoutout to some of the talks I am most excited to see. Ice, confusion, and the 38,000ft crash - Nickolas Means Level up the whole party, not just the hero - Denise Yu How to talk to everyone: Connecting with your reporting chain - Najla Elmachtoub

16

1 Kommentar

How many of your supposedly internal-only backends are serving critical end-user traffic? Probably more than you think! Most frontend services have many transitive dependencies, and understanding these dependencies becomes increasingly difficult as your system grows in scale and complexity. As a result, it becomes exceptionally tricky to ensure that internal-only backends are fully isolated from end users. Google uses a common infrastructure platform for almost all of its services, internal and external; this provides for a message-passing mechanism common to all of these services. One outcome is that systems engineers can build accurate dependency maps of services; and that we can ensure new services only depend on other services at the same level or higher in the dependency stack. Risky dependencies — in this case, dependencies which place internal-only backends on the critical path for end users — can be a source of major production outages, because the internal-only backends do not generally have necessary reliability or safety guarantees. For example, you might have an externally-visible service that requires high levels of availability and performance, and this system has an indirect dependency on a backend with no availability or performance SLOs. At Google, we found success preventing major and huge outages by clustering services into categories with distinct properties, clear perimeters, and limited blast surfaces. The properties will depend on the guarantees we want to enforce. In this article, we use Google Maps to demonstrate how risky dependencies proliferate in complex systems, and then showcase how clustering Google Maps services into just two categories ("Internal" and "External") can prevent major and huge serving outages. We also outline how OpenTelemetry is used to identify violations of this clustering, which can be fixed before the violations cause a major serving outage. This article is based on a talk by Pierre Theo Klein at SREcon EMEA, which you can see here: https://lnkd.in/e_cyxv_A. Jennifer Steiner Klein collaborated on turning the talk into an article.

39