Computer Graphics’ Post

Read Part 1 of our 3-part blog series, "Design, Deploy, Sustain: A Guide for Automated Test Best Practices" to learn some of the steps to achieve faster time to market, and best practices when designing the perfect test system. https://hubs.ly/Q01-Jb4-0 #Blog #TestandMeasurement #Design #Communication

On Effective Program Design: After I write a program, one of the more important questions I ask myself is, “Could I simplify this program and accomplish the same thing?” Only when that answer is NO do I consider it complete. "As simple as possible, but no simpler." That's the goal. When you program, what questions do you ask yourself?

Design thinking is a powerful tool IT professionals are using to develop user-friendly and effective solutions. 1 minute overview if you're interested, a more in-depth video is on the way!

If you want to learn how to design things, but find the tools intimidating... ⛔ Don’t start by studying the technology or types of machines.  ⛔ Don't hire a consultant.  🥇 Start by creating a project that meets a business goal. Why? For my fellow engineers in the room: How do you learn to design? Do you: A. Take classes and learn about each concept and best practices for design? B. Start with a blank slate, not really knowing what you’re trying to build? OR C. Pick a project for something you'd like to create and try to build it.  From my time as an engineer, I found the best answer is C: You learn fastest by building something. If you just start calculating user needs and product requirements, you won’t get anywhere quickly.   But when you start building, that's when you really make progress. You'll find the gaps in technology that you need to solve certain problems.  You'll develop requirements from testing prototypes. You'll hear user needs from putting things in people's hands.  Start with the goal, and start building.  The rest of it will follow.   Need help on the Ideation (Fuzzy Front End) of your development project? Call me, 763-344-1308, let's chat.    or hit the link to get on my calendar: https://lnkd.in/gYy7tbHg

Interesting point Actually for certain works the theoretical path of the workflow is linear, for example drug development. The reality of how you get there is far from linear and need several path adjustments and deviations. This is because reality is not represented by linear mathematics which postulates that a force applied on a point has always the same effect independently of the position of the point. Reality is modeled by caothic mathematics in which a force has not always the same effect depending on the position of the point because of attractors present along the path which could make moving in a prechosen direction much harder prompting to find new paths. The result is a theoretical linear pathway to reach a goal (we have been teached to think using a linear mathematics frame) that is walked in a seemgly cahotic manner full of deviations and U turn because linear mathematics do not apply to complex life phenomena, caothic mathematics do. The latest predict that in order to go straight some time is better to turn right or left.

Life (or work) isn't always neat and linear or proceed as planned. So, I am trying to create a graphic that demonstrates the iterative, sometimes repetitive nature of a workflow. I want to be able to communicate the normalcy in some of the chaos and not oversimplify a process. Have any of you done this? Anyone want to share? #design #process #nonlinear

Totally agree with this—while a designer on a Design System team should have a decent base competency in Product Design, the true value is in crafting automated, resilient infrastructure or the “operations” of the System, and making it easy to learn and use. Talks, docs, 121s, and adapting the System to suit the mental model of your teams being key tools (in my experience anyway) to success 🚀

🔌🧩 Starting the hardware design process? Don't skip the Block Diagram! In the world of hardware design, the Block Diagram is your compass. 🗺️ It's your initial roadmap that can make or break the success of your project. 🚀 🔍 Understanding Requirements: The Block Diagram allows you to dissect and comprehend project requirements at a glance. It's your first step in translating ideas into tangible components. 🤝 Collaboration Magic: If you're working with a team (and most of us do!), the Block Diagram becomes the common language. It's the visual bridge that aligns everyone's vision, ensuring smoother teamwork and fewer missteps. 🧩 Puzzle Pieces: Think of it as putting together a complex jigsaw puzzle. The Block Diagram helps you see how each piece fits into the larger picture. It's the cornerstone of a well-thought-out design. So, whether you're a lone innovator or part of a dynamic team, remember this: Start with the Block Diagram, and watch your hardware design process become a masterpiece. 🎨💡 #HardwareDesign #BlockDiagram #Teamwork #Innovation #Engineering

I strongly believe that Design System work is a specialist role. As designers, we are often expected to be experts in everything, but the truth is that we need to start separating and defining these roles. In my experience, I have witnessed the negative impact of not having specialized Design Systems roles. There is an obvious overlap between general Product Design and specialized Design Systems work, but we need to start treating them as two distinct disciplines. Having applied to many Design Systems roles, I have noticed that many of them sound more like Product Design roles. Design Systems roles involve a unique set of skills that should not be overlooked. These skills include defining, managing and automating design tokens, design engineering, building documentation sites and maintaining documentation, and writing stories in Storybook and doing visual regression testing in Chromatic, among other things. It's time to recognize that Design Systems work is a specialized role that requires in-depth knowledge and expertise. As designers, we shouldn't be expected to know it all. Let's start defining these roles and recognizing the importance of specialized skills in Design Systems work. #designsystems