Mirco Bellagamba

If you want to see some of the new SwiftUI changes you can see my latest post, to discover how to leverage the newest APIs to design visually appealing features, including: ✅ Rounded Corners: Learn how to implement modern design elements for a polished look. ✅ Custom Tab Bar Settings: Optimize navigation for a seamless user experience. ✅ Efficient List Management: Hide scroll indicators and row separators for a clean interface. https://lnkd.in/d7TRbfnP #SwiftUI #iOSDevelopment #AppDevelopment #UserInterface #Coding #DeveloperCommunity

5

⛓️‍💥Connascence in Code Refactoring: Profound Insights from Marco Consolaro 📜 Refactoring code isn’t just about cleaner syntax—it’s about understanding connascence, the hidden relationships that drive complexity in systems. Marco’s #IAD24 talk (Italian 🇮🇹 version: https://lnkd.in/g6GuhEXj) delves deep into this concept, offering insights that are essential for developers and architects. For an English perspective, watch Marco’s related talk was initially made at KanDDDinsky (English 🇬🇧 verison: https://lnkd.in/gG3UPdAW). 💻 Marco, a partner and respected thought leader in #SoftwareCraftsmanship, is a key contributor to our strategic joint venture with Alcor Academy. This collaboration is part of our mission to continually enhance our digital portfolio improvement process, delivering an ever-better holistic offer for #PE / #VC stakeholders seeking the #DigitalEvolution of their IT assets. Together, we’re shaping the new SW Craftsmanship Dojo v.2.0, blending technical excellence with the behavioral and socio-technical aspects essential for true transformation. Explore how Marco connects technical excellence with holistic digital evolution. #Refactoring #Connascence

7

1 commento

Why do developers love Internal Developer Platforms? 🩵 The goal of an IDP is to provide an #Integrated, automated environment that allows developers to focus more on developing code while minimizing repetitive and manual #Tasks🚀 ⚡The implementation of an IDP can bring many benefits, such as improved #Productivity, faster #Onboarding, #Flexibility and #Adaptability. 🌍But these advantages aren’t limited to #Developers - companies as a whole can deeply benefit from an IDP. 🤔Why? Check out this article by our partner Omnia Group - Consulenza IT & Sviluppo Software to find out!  ➡️ https://lnkd.in/d-QfnPy9 #MiaPlatform #OmniaGroup #InternalDeveloperPlatform #IDP #PlatformEngineering #Article

9

Lifecycle Pmpath to to multiplatform

2

#frontend #component #refactoring Yesterday we talked about the purpose of components and the benefits they offer us in terms of readability, debugging, reuse and testing. Today we wanna share a video (no audio but with captions) to show you how to migrate from a static layout, built in Angular 18 and Tailwind, to a modular system made by "static" components. The process is very simple: 1️⃣ Identify the part of the static template that you want to convert in components. 2️⃣ Create the components (i.e. `<app-hero>`, `<app-card>`, ...) and copy-paste the parts of the HTML template they are responsible 3️⃣ Use the components This video is part of our latest article "From Static to Components", where we explain the procedure step by step. https://lnkd.in/dpwz5jTN In the next article I will show you how to make them reusable and more flexible.

2

1 commento

In the past few weeks, a junior developer asked me for some advice about books. I created this list, and I believe they should be a must-read for everyone involved in the software world: - The Pragmatic Programmer: Your Journey to Mastery, 20th Anniversary Edition - Clean Architecture: A Craftsman’s Guide to Software Structure and Design - Clean Code: A Handbook of Agile Software Craftsmanship - The Software Craftsman: Professionalism, Pragmatism, Pride - Extreme Programming Explained: Embrace Change - Release It!: Design and Deploy Production-Ready Software - Fundamentals of Software Architecture: An Engineering Approach - Head First Design Patterns: A Brain-Friendly Guide: Building Extensible and Maintainable Object-Oriented Software - The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win - Refactoring: Improving the Design of Existing Code (Second Edition) - A bonus: Lean Customer Development: Building Products Your Customers Will Buy. I suggest this last one because we need to understand our customers. We build software for others. #softwareengineering #dev #systemdesign Originally posted here https://lnkd.in/dkKaP4fV

3

Come la vedete voi? C'è un post su #HackerNews che mi ha fatto pensare... Hi. I've been in the profession (SW Eng) for about 18 yrs now. A few years from my 50s. Didn't go the managerial route. Stayed technical. My current gig is in a very difficult and complex project written in C. Been there for 2 yrs now and I'm afraid that due to the ancient tech stack and despite being a good engineer I'm loosing my marketability. After enduring bad behavior for nth time (yeah it's a toxic workplace) I decided I had enough and did a round of applications. Mostly for backend positions and mostly for golang positions. I don't have prod xp with golang but it's close to C and every time I've used it it seemed ok. But the problem is that I'm either being ignored or skipped over. All jobs are for seniors in the _specific_tech_stack_. Other positions I've applied for and got no response whatsoever are architects, tech managers and the like. Granded, this regards a turd job market (EU/Greece) but still that's where I am at. Am I toasted for good? I mean, nearing my 50s with my most recent gig writing "C" on it is as good as declaring my career over? Link nel primo commento...

14

16 commenti

The Hypertext Transfer Protocol (HTTP) stands as one of the oldest and most critical protocols in daily internet usage. Ensuring a solid and performant implementation of this protocol is fundamental for both user satisfaction and developer efficiency. Paolo Insogna explores how Node.js tackles this task and introduces Milo, a promising replacement for the current HTTP parser, llhttp. #Nodejs #JavaScript #OpenSource #Milo #WebDevelopment https://lnkd.in/e-__5RRG

11

Nice write up. Though I would call the Trunk based development review model, Non-blocking review. There integration of work and early feedback is valued as more urgent than code review. The code review is important, but often not to the degree of letting it block integration of work, getting early feedback from test environment, interupting flow of work of the reviewer or the reviewee. It also works counter to multiple developers working on the goal in parallel and collaborative. So try to find a way to make the review process non-blocking. A good first step is to be explicit about what you want out of reviews and whether blocking reviews actually helps with that or against it. Remember to use the 5 whys, so you dont optimize for a selected solution (e.g. blocking reviews to avoid errors in main - do they actually?). If you want software delivery performance, you might gain more from a process with less friction and quicker round trip than Gates that might actually not do what you claim or assume. There is such a thing as counter productively cautious. E.g. sacrificing early feedback for finished work in the wrong direction.

5

📡 Open Collaboration: OpenProject + GitLab Integrate A new article on the OpenProject #GitLab integration has been published on OpenSource.net, supported by the Open Source Initiative (OSI). The article tells the open source success story of how Community contributor Benjamin Tey created a GitLab plugin for OpenProject out of his own need. And how – due to immense demand – this plugin was recently integrated into the OpenProject core. We are very happy and proud of our amazing open source Community. Only together we can achieve great things. 💙 https://lnkd.in/dyc28x8K

13

1 commento

📢 We’ve published a new blog post! Our CTO, Gianfranco Papa, delves into Dart macros, an exciting experimental feature in #Dart that could change the way developers write and generate code. In this article, you’ll discover: ✅ How #macros simplify repetitive tasks. ✅ A better approach to JSON serialization. ✅ The advantages of real-time code generation. 📖 Read the full article here and explore the future of Flutter development: https://lnkd.in/g_pEFgMs 🚀 #Flutter #SoftwareDevelopment 

9

Do you know four reasons to use asynchronous images? Here are my four. 1.   Performance Optimization 2.   Reducing Memory Usage 3.   Bandwidth Management 4.   Enhancing User Experience If you are interested how use it in iOS. #iosdev #swiftui #swift https://lnkd.in/dXEdcd42

2

🔧 The Role of IDPs (Internal Developer Platforms) Internal Developer Platforms (IDPs) are designed to simplify complex tasks for internal engineers. They provide a pure UI layer with all the necessary capabilities in an abstract fashion. An IDP offers the right amount of abstraction for engineers to perform their tasks easily. Example: Integrating GitOps through ArgoCD or Flux without needing specific knowledge of the underlying processes. 🔍 Learn how Codiac.io integrates IDPs for optimal performance, making your engineering tasks simpler and more efficient. #PlatformEngineering #IDP

1

4 Reasons Software Engineers in Startups Should Avoid FAANG Patterns to Boost User Value and Reduce Frustration While reading technical documentation and blog posts from great companies is educative, applying what you read if you work in a startup is not always a good idea. Here are 4 reasons why you should not apply FAANG patterns if you work in a startup: Reason #1: Complexity Overload Applying patterns for large-scale companies, like Microservices, leads to increased complexity. Companies like Netflix need that complexity because of their scale. If you work in a startup, you will probably face thousands of users, not millions. Reason #2: Increased Bureaucracy The same complexity should be avoided also in the organization itself. Build in a lean environment and implement the process to align your teams. Avoid bureaucracy until you need it. Reason #3: Inhibited Flexibility Companies with a well-established business model can and should apply patterns to enforce their market presence. Startups can be in a stage where they are still exploring. Startups must change frequently, and being ready for that is crucial for the engineering team. Reason #4: Reduced User Proximity Big companies need to create and implement patterns to gather users’ feedback. You have a considerable advantage when you work in a startup: you can talk directly to your users. Use that advantage to learn what they need. —- Do you want to learn more about startup engineering practices? Subscribe to https://lnkd.in/dG5DPVzT. #StartupEngineering #SoftwareDevelopment #TechStartups #LeanStartup #EngineeringLeadership #AgileDevelopment #TechTrends #ProductDevelopment #UserFeedback #TechInnovation #SoftwareEngineering #BureaucracyInTech #StartupCulture #EngineeringBestPractices

5

🏗️ Decoding Software Architectures: Which One Fits Your Project? 🤔Explore 6 popular architecture styles and their pros and cons: 1️⃣ Monolithic: Simple but hard to scale 2️⃣ Microservices: Flexible but complex 3️⃣ SOA: Reusable but orchestration challenges 4️⃣ Event-Driven: Scalable but tricky to debug 5️⃣ Layered: Organized but potential overhead 6️⃣ Serverless: Cost-efficient but vendor lock-in risks 💡 Each architecture has its strengths and challenges. The key is choosing the right one for your specific needs. 👇 Which architecture style do you prefer for your projects? Share in the comments! Amit Singh Piyush Kumar Yadav Aditya Joshi rohit kundalwal Mandar Jahagirdar Mahesh Gawhane #SoftwareArchitecture #TechInnovation #DeveloperInsights #CloudComputing #TechTrends #LogicLoom

12

4 commenti

The #YAGNI principle: "You Aren't Gonna Need It" As a software #developer, there's often a tendency to build an overly polished product, even when it adds little value for the customer. This mindset extends beyond the #UI In the core design, you might create unnecessary APIs, classes, and customizable features where they're not needed. There are many drawbacks to this approach: wasted time, effort, and money, to name a few. You also risk introducing unnecessary #bugs and logical flaws. While future-proofing has its merits, it's not always the best approach. #YAGNI #SoftwareDevelopment #DeveloperLife #ProgrammingTips #ProductivityHacks #SoftwareEngineering #CodingBestPractices #EfficientCoding #TechMindset #API

2

1 commento

Fun little thing I discovered. Using CLI to Change npm package.json "type" to "module" or "commonjs" https://lnkd.in/esT4Js9W

12