Jeffrey Kern’s Post

Why is code often open-source, while design is closed? After 20 years as a designer, now diving deeper into code, I’ve been reflecting on this difference. Code is often open-source because it thrives on collaboration and continuous improvement. It’s adaptable, evolves with contributions, and is shared to solve real-world problems. In contrast, design is usually kept closed or paid, viewed as a polished, final product—something visual and ready to use. But here’s the truth: design is just an abstraction. The real value lies in the code, because code is the final product. Without it, design remains a static idea, a vision that doesn’t function. People tend to value design more because it’s the first thing users see, but code is what brings that vision to life. Designers who code understand this dynamic—they see that both abstraction (design) and implementation (code) are crucial. Ultimately, code and design need each other to create great products. But code is where the product truly lives. ⚡️ What are you doing to close the gap? #OpenSource #Design #Code #ProductDevelopment #ProductDesign #DesignersWhoCode

Tips for Devs & Designers #17: Mastering the basics is underrated. Fancy techniques won’t save you if you don’t have a solid foundation.

Tips for Devs & Designers #13: Creating something scalable, even if it’s not perfect, is often better in business. It allows you to build upon it and improve over time.

Why Do Design Patterns Exist? In the dynamic world of software development, it’s fascinating to observe how certain challenges repeat, regardless of the project or team. This phenomenon led to the birth of design patterns, a set of best practices that guide us in crafting elegant solutions. What Is the Value of Understanding Design Patterns? Understanding these patterns is similar to having a map through complex coding problems. They are not meant to be committed to memory but to be understood and applied as needed. Yet, there’s a misconception in some evaluation and hiring processes that a developer’s worth can be measured by their ability to recite these patterns. How Should a Developer Be Evaluated? True expertise lies not in memorization but in the practical application of these principles. It’s entirely possible for a proficient developer to be fluent in the essence of design patterns without being able to label each one. After all, it’s the ability to solve problems effectively that distinguishes a great developer, not just the knowledge of the patterns’ names. #design_patterns #software_development #developer #software_developer

Tips for Devs & Designers #8: Having the right tools won’t solve everything. The real value comes from knowing when and how to use them efficiently.

It’s hard to build one 🔥 10 points on approaching towards design system : 1. Making the “design system” part of your business requirements is key. 2. Take the time to get it right. This might involve deeper research in every topic you touchdown. 3. Creating a design system is only the beginnning. The hardest part is applying it to the codebase. 4. Deciding what belongs to design system can be challenging. 5. Having a design system will not solve all your consistency problems. Although, the fact, “consistency” is a never-ending mission ⚡️ 6. Design system doesn’t end with design and develop once. It takes meaningful time and effort to maintain the consistency while developing. 7. Stronger sense of community makes the process stronger (Involving the team on requirements, usecases,..) 8. Efficiency is the most tangible benefit of the design system approach. 9. Communication is key. As new devs onboard it’s important to introduce them on the design system in details to maximize productivity. 10. Even the biggest changes can and should be delivered in increments 🚀 *** Go through my one stop frontend resources here : https://lnkd.in/gMG_6QEw (2400+ learners, 1800+ downloads)

"I have a great idea! Let's hire developers and build it!" I've seen this mistake 100 times. Here are the 5 things you NEED before hiring developers: ➡️ Must-Have Features: List only what you need. ➡️ Wireframes: Sketch your screens. They don't need to be pretty. ➡️ Budget: Know how much you can spend. Be real about it. ➡️ Timeline: When do you need it done? Be clear. ➡️ Success Metrics: How will you know if it works? Decide now. Having these ready will save you money. It helps developers get your idea. Need help with this list? Let's talk. I've helped 100s of businesses turn ideas into real products. Cheers

I believe that having this would help recruiters and other viewers see the extent of how good the designs were vs the implementation. Having a higher correlation would help bring out the beauty and excellence of the designs. I simply hope devs would help us have higher scores for the correlation of design vs implementation. #design #dailydesigndose #implementationj

😂😂 Devs and designers in this house please can you relate to this . Let me know in the comments session

𝐃𝐞𝐬𝐢𝐠𝐧 𝐒𝐲𝐬𝐭𝐞𝐦𝐬 𝐚𝐫𝐞 𝐇𝐀𝐑𝐃? You are expected to: 𝐌𝐲𝐭𝐡 1: Design Systems require extensive knowledge of complex codebases. 𝐌𝐲𝐭𝐡 2: Implementing a Design System means rigid adherence to predefined rules. 𝐌𝐲𝐭𝐡 3: They are only useful for large-scale projects with vast teams. But it’s (actually) really simple: 𝐑𝐞𝐚𝐥𝐢𝐭𝐲 1: Design Systems are about creating a shared language and set of tools that streamline design and development. You don’t need to be a coding expert to use them effectively. 𝐑𝐞𝐚𝐥𝐢𝐭𝐲 2: They provide flexibility within a structured framework, allowing for creativity while maintaining consistency. 𝐑𝐞𝐚𝐥𝐢𝐭𝐲 3: Even small teams and projects can benefit from a Design System, improving efficiency and scalability as you grow. Design Systems aren’t hard, but we’ve been conditioned to think they are. "𝑫𝒆𝒔𝒊𝒈𝒏 𝒊𝒔 𝒏𝒐𝒕 𝒋𝒖𝒔𝒕 𝒘𝒉𝒂𝒕 𝒊𝒕 𝒍𝒐𝒐𝒌𝒔 𝒍𝒊𝒌𝒆 𝒂𝒏𝒅 𝒇𝒆𝒆𝒍𝒔 𝒍𝒊𝒌𝒆. 𝑫𝒆𝒔𝒊𝒈𝒏 𝒊𝒔 𝒉𝒐𝒘 𝒊𝒕 𝒘𝒐𝒓𝒌𝒔."  – Steve Jobs