Martin Røssell

Have you been thinking about AI lately and come up with some ideas? Together with the awesome teams from Pareto AI and SE7EN, we’re offering companies the chance to submit their AI project ideas for a FREE expert review and initial cost estimation—no strings attached. This is your chance to get real, actionable feedback from people who’ve been in the trenches of AI and tech development. Whether you’re working on a big, ambitious project or just testing the waters, we’ll help you figure out your next steps. 🚨 Here’s the kicker: You’ve got until 31.10. to submit. Don’t wait until the last minute—this is a limited-time deal! Submit your idea here 👉 https://lnkd.in/dSHXemaX, Submit and let’s see what you’ve got!

4

I'm so tired and, slightly, brain-dead from making full use of Frontend Masters today. I opted for the Git course and signed up for a workshop on testing. So I've been hopping from one to the other for about 8 hours so far. 🤔 Hmm, I just noticed that's a full workday! 🤣 Don't worry, I'll switch to straight up coding now. But during my last switch to the git course, I made an error! I had a moment of panic, then realized I've just been learning how to fix that. So learning for the win! If you were wondering, the error I made was in #vim, because I generally only use it in tutorials. Day 96's #impromptuvideos

12

Curious about Laerdal strategy on DesignOps? Or on DesignOps in general? I have a 6-ish minutes read for you! (Emphasis on "ish") In the article, I describe our approach to our DesignOps work and how we used methods inspired by the current product movement to focus on and deliver impact through our operationalizing work. Thanks to Design Matters DK  for the opportunity to publish some of these thoughts, and special thanks to Yulia Kosheva  for the illustrations! #laerdalcphlife #techforgood

51

3 Kommentarer

Caching hides many sins, and the new caching strategy in Umbraco 15 might just uncover some of yours 😯 In Umbraco 14 and below, all content is loaded into cache at boot time. This is not the case for Umbraco 15 - and that's a good thing! However, you still might need to load a lot of content into cache, specially on older sites that are overdue a performance overhaul. The good news is you can leverage the new caching strategy to lazy-load content into cache, without sacrificing boot time 🚀 The details are in my latest blog post 👇 https://lnkd.in/dXBEEfGD

31

Elevate Your Team’s Efficiency to next level with Klarity Architect! Klarity Architect doesn’t just document; it analyzes pain points, maps out flow diagrams (BPMN), and delivers actionable improvements in just minutes!📈 Let's revolutionize the way your team works!🌟 #FutureOfWork #BusinessAnalysts #ProcessTeams #ProcessImprovement #GenAIPowered

3

I came across a post from Jakob Jenkov (Thank you, for the insights) regarding OOP & FP. I felt it was worth delving into the details and sharing my openion: ✴️ 1. OOP and FP Are Not Opposites: OOP and FP are not inherently contradictory. Both paradigms aim to build modular, reusable, and maintainable systems, though their approaches differ: FP emphasizes pure functions, immutability, and stateless computation. This formalism naturally leads to composable systems, as smaller, predictable units are easier to combine. Modern OOP has shifted toward composition over inheritance, emphasizing modularity and composability. The key is how OOP concepts are applied in practice. ✴️ 2. OOP Is Evolving: Inheritance: Once central to OOP, inheritance is now often avoided due to the tight coupling and complexity it introduces. Many prefer composition or interface-based design to achieve flexibility. Encapsulation: While foundational, modern OOP recognizes that strict encapsulation can be impractical. In real-world systems, breaking encapsulation (e.g., sharing internal state where it makes sense) can simplify code. This evolution reflects a pragmatic shift: use OOP as a means to an end, not a rigid ideology. ✴️ 3. Composability as the Common Goal: In FP, composability is often explicit (e.g., function composition, higher-order functions). In modern OOP, composability can be achieved through patterns like dependency injection, modular design, or component-based architectures. The focus is less on adhering to OOP "purity" and more on creating adaptable systems. ✴️ 4. OOP's Original Theory Has Limitations I agree with your critique of classical OOP theory. Its emphasis on: Hierarchies (overuse of inheritance) often result in rigid, overly complex systems. Encapsulation for its own sake can obscure the bigger picture and hinder performance or flexibility. Modern programming has demonstrated that loosening these constraints leads to better outcomes. ✴️ 5. Practicality Over Purity In practice, many modern languages (e.g., Python, Kotlin, JavaScript) and frameworks blend OOP and FP principles. Examples: Python’s standard library uses both FP (e.g., map, filter, lambdas) and OOP (classes, inheritance). Functional concepts like immutability and first-class functions are increasingly embraced even in traditionally OOP languages (e.g., Java’s Streams, C#’s LINQ). What matters is achieving composability and maintainability, not strict adherence to one paradigm. ✴️ ✴️ Final Take: OOP and FP each offer valuable tools for building composable systems. The key is understanding the strengths and weaknesses of both: Use FP when we need immutability, statelessness, and predictable behavior. Use OOP when we need encapsulated state and modular abstractions. In practice, a hybrid approach—embracing the best ideas from both paradigms—is often the most effective way to write clear, composable, and maintainable codebases. Please share your thoughts as well. 🙏

17

2 Kommentarer

I recently had a conversation with Mariia Vain, a Staff Software Engineer at AgencyAnalytics, about one of the most critical skills for Staff+ engineers: prioritization. As Mariia pointed out, there will always be countless things you could be fixing, improving, or building. The challenge isn’t in finding what to work on but in narrowing it down to the 2-3 things that will have the most impact over the year. This can involve engaging in deep conversations and interviews with engineers across different areas, identifying opportunities where solving one issue could have rippling effects across teams. Using data like performance metrics, security reports, and reliability stats to back up these decisions can also make a stronger case for why a particular direction is chosen. Setting up recurring meetings with focused teams—like a backend council or guild—can help align on priorities and gather insights from those closest to the work. At the end of the day, it’s up to the Staff+ engineer to make the final call and communicate this clearly to engineering leadership. While ensuring that all voices are heard, sometimes you need to disagree and commit in order to move forward. How do you navigate prioritization in your role? I’d love to hear your strategies and experiences! If you're a Staff+ Engineer I'd love to connect: https://lnkd.in/gKT7unhC

9

Can a machine be empathetic? "If it feels real, it is real" opens Petri Lattu the Designing for machines that can feel: GenAI is flipping the script of human-centered design workshop by Siili Solutions Could not imagine a better or more interesting start for Service Design Global Conference 2024 in Helsinki #SDGC24 #servicedesign #interactiondesign #GenAI

52

8 Kommentarer

Are you trying to develop accessible design guidelines and UI components? No need to reinvent the wheel. You can save tons of design, development, and testing time by taking examples from or using other's accessible design systems. Vitaly Friedman lists some great examples👇

15

Side projects can be a game-changer for growth—especially when you own the whole process. Not just coding, but everything: production monitoring, customer support, DevOps, architecture decisions, performance, cost optimization etc. Working on Rechound has challenged me to solve problems I’d never faced in my full-time job. When you’re responsible for every aspect of a product, you’re forced to learn quickly and adapt. The best part? Those skills carry over. It’s made me more effective in my day job and more confident in tackling the challenges of building and running software.

13

1 Kommentar

Do's and Dont's of collaboration between UX and POs, devs, managers and all folks involved in product development. A couple weeks ago, Anna Slotty and me hosted a session on this for UX Frankfurt (thanks Juri Wan and Thomas Jackstaedt for having us!). With UX professionals for UX professionals we mapped out challenges that they face and ideated on solutions. Let's see what we've been thinking about. 🔍 Topic 1: Planning & processes 🌶 Problem: - Even though UX is supposed to be a part of the product machinery, it is not necessarily. - UX often has no defined place in product development processes. - Product works in agile sprints, UX not necessarily. - Product dev runs on tickets, UX not necessarily. 🌮 Solutions: - Identify how processes are defined today and "sneak" in where UX fits best. - Try to use UX tickets to speak product language, place them where others can see them. - Try to provide UX deliverables that fit within one sprint and are relevant to what's going on in product. 🔍 Topic 2: Roles & communication 🌶 Problem: - Extensive and unstructured meetings where UX has no or only a short part to contribute. - Being left out from actually important conversations, where UX can and should provide value. - Lack of focus time to do meaningful work caused by meeting mania. 🌮 Solutions: - You're not alone. Everybody hates bad meetings. Surprise solution - Host a good one! Define roles upfront, provide an agenda what's to be discussed, timebox topics, take the role as facilitator. - Figure out who can invite you and why you weren't in yet. Assume best intentions. - Be brave and hop out in times where you're not needed. Save that time for the good. 🔍 Topic 3: UX acceptance & enablement 🌶 Problem: - Nothing new here - product still needs to understand what value UX brings to the table, but many times doesn't. - UX often can be perceived as finger pointing about how important they are (and yes they are), but this can lead to avoidance by others, if you keep telling them what they're doing wrong. 🌮 Solutions: - Create a stakeholder map and figure out, who you need to make friends with and which people with strong opinions oppose UX work. From there, systematically meet up with them to understand their needs and concerns so that you can figure out how to approach them. - Understand their languages and speak them. Tailor your results to what they need to understand what you offer them. - Make UX work fun and tangible. Share snackable UX content (e.g. reels created from usability tests) to create buzz around you and your work. People will remember. PS: If you ever wondered if a taco is appropriate to visualize solutions, the short, the long and the definite and undisputedly true answer is yes.

37

2 Kommentarer

Strategic DDD: Speaking the Same Language (Finally!) 📚 Ever been in a meeting where everyone's using the same words but meaning completely different things? That's exactly what the Published Language pattern helps solve! Did you know? 🤔 Just like shipping containers revolutionized global trade by standardizing transport, Published Language standardizes how our systems talk to each other. Key insights about Published Language: 📖 Shared Vocabulary: Everyone agrees on what words mean 🤝 Common Ground: Standard way to communicate 🔄 Flexible Usage: Keep your internal language, just translate at the boundaries 🌱 Natural Evolution: Grows and adapts with your needs Common winning scenarios: - Industry standards - B2B integration - Event-driven systems - Partner ecosystems Architect's Alert 🚨: Remember, creating a shared language is like writing a constitution - it needs to be specific enough to be useful but flexible enough to last! Want to dive deeper? Check out my detailed blog post here: https://lnkd.in/dwVtaN_n 📚 #DomainDrivenDesign #SoftwareArchitecture #SystemDesign #ArchDeck #TechnicalArchitecture Stay tuned for more patterns in this series! Next up: Separate Ways relationships 🚀

5

One of the hardest things about shipping products is balancing this contradiction: you want to do the best possible work everywhere, but optimizing every piece takes time, and time is finite. I’ve done a poor job here countless times in my career. And I have seen many others struggle here, too. If you like your craft, it’s natural that you want to do your best all the time. But the best and good enough are different things: you must learn when and where to aim for each. This is easy to understand, but it’s very hard to put into practice when it is time to do the work. How do you convince creative individuals who love building things to build less? How do you get someone who enjoys technical challenges to try to make things simpler and more boring? There is a joke about never asking a surgeon if you need surgery. What about asking developers if they need to build the perfect interaction, abstraction, or library? Of course they do! I believe the solution here is not about good practices or coaching. Instead, it’s about creating a working environment that makes costs a first-level concern for those doing the work. Aiming for good enough won’t happen as an intellectual exercise in the abstract but out of pure necessity at execution time. How can you create such an environment? With constraints! I’ve seen 37signals apply these two consistently: First, timeboxing. Time is not infinite, so don’t pretend it is. Set a deadline and give people doing the work the power to adjust what’s built. "Fixed time, variable scope" is probably the single most powerful concept I have ever learned about shipping [1]. Second, scarcity. Tiny teams that want to ship need to make the most of their time. Why would you restate problems to simplify them when you have an army of colleagues to work on whatever is pending to ship? On the contrary, how won’t you do it if shipping depends on completing a long list of additional things on your plate? The specific team sizes will vary, but I believe the principle prevails: a sense of scarcity helps shipping. It may sound counterintuitive but consider the alternative. If neither time nor development bandwidth is a concern, how could people doing the work make the right call for the millions of decisions ahead? When it comes to shipping, constraints are not to be avoided or resisted but rather embraced and even induced. https://lnkd.in/dvGeniJV [1] https://lnkd.in/dTyR-ncd

54

1 Kommentar

Got an email this morning from Kaspar Von Grünberg over at Humanitec predicting the trough of disillusionment coming to #platformengineering in 2026. He specifically called out that one of the top reasons for a failed platform engineering initiative is a lack of focus on measurable impact. "You should be absolutely obsessed with ROI, impact, measurement etc." This resonated with me and it aligns with how we discuss using our product Optimize Live with users. By adding automated workload rightsizing to your platform you will remove cognitive load from developers that don't want to think about how to size their workloads running on #kubernetes. And you can easily track how much waste and performance risk you have corrected by rightsizing your workloads. You'll see your CPU and memory requests go down, which in turn will cause you to use less nodes, and you'll see your CPU and memory utilization increase. This is all very actionable and measurable.  So if your platform engineering initiatives aren’t making the impact you hoped for, we’d love to help you out.

31

1 Kommentar

AI Will End Mundane Tasks for Designers! What if you could stop wasting time on repetitive tasks and focus entirely on the creative work that truly matters? Value for customers? At Y OSLO, I unveiled how AI is revolutionizing the design world: No More Mundane Tasks - AI handles the tedious stuff. 80% Productivity Gains - Faster results, fewer headaches. Rapid Iteration - AI accelerates the feedback loop, helping you refine ideas. Innovation on Overdrive - AI enables customer-validated designs to hit the market faster than ever, changing the game for creators everywhere. Ai is more than a tool it’s a paradigm shift. From Double Diamond into a Stingray Model. Watch my Y Oslo talk here Link Here> https://lnkd.in/dEs-duWq 👇 Let’s discuss: How is AI transforming your design process? #AI #DesignInnovation #FutureOfDesign #ProductivityHacks #YOSLO #CreativityUnleashed

46

2 Kommentarer

Introducing TestDriver “Turbo Mode.” A new set of optimizations that reduce test soeeds by over 40%! Not only is TestDriver smarter than any test framework of yesteryear, now it’s faster than many too. Check out our progress in the chart below. When we couldn’t make the AI any faster we wrote our own algorithms to power “turbo” mode using a combination of string matching algorithms and statistical analysis.

7

A couple of years ago, at React Finland 2022, I shared my insights on a topic that is near and dear to my heart - benchmarking for design systems. As a consultant for design systems, I often find myself advising clients on the best practices and strategies to adopt. One of the recurring challenges we've faced is determining the right standard to benchmark against. With so many diverse design systems out there, it can be overwhelming to determine which one should serve as the baseline. To address this, I shared the results of a comprehensive study I conducted, analyzing dozens of design systems and their various features and attributes. The goal was to develop a structured approach to industry research, one that would empower teams to make informed strategic decisions and identify effective implementation strategies. The result was a Miro board that serves as a meticulously curated collection of design system examples, with each section linked to corresponding features and content across different systems. This resource has become an indispensable tool in our work at Bridge The Gap, as we constantly refer to it when discussing design system requirements with our clients. The visual representation and the wealth of examples help us communicate the subject matter more effectively and pinpoint the features that are most crucial to our clients' needs. I'm sharing this talk from 2 years ago because it has recently resurfaced in one of our current projects at Bridge The Gap. We just had a discussion around the features the design system documentation website needs, and this comprehensive Miro board once again proved to be incredibly valuable. It allowed us to effectively showcase the options for the features our blended team (us-consultants and the client's developers and designers) was seeking. If you're interested in learning more about this topic, this is the full video of the talk: https://lnkd.in/dPF5VMSu And of course, the Miro board is available for you as well (look in the comments to this post). Feel free to explore and let me know if this approach or a similar one was helpful for your work as well.

19

1 Kommentar

Accessibility, and the way it is managed and governed within an organization, are crucial topics. Failing to address accessibility can lead to poor design and code, which ultimately creates barriers for users. In a recent Elisa blog post, I explored this subject in depth, gathering insights from Elisa’s top management. The article highlights how Elisa is strategically approaching accessibility, the steps being taken to effectively manage and govern it - and where the journey goes.

16