Reflections on Software Performance An Article by Nelson Elhage blog.nelhage.com Performance is a feature Performance changes how users use software Performance needs effort throughout a project’s lifecycle Architecture strongly impacts performance Performance isn’t just about hot spots Performant foundations simplify architecture …we underrate performance when designing and building software. We have become accustomed to casually giving up factors of two or ten or more with our choices of tools and libraries, without asking if the benefits are worth it. performancesoftware
Design Leadership Truisms An Article by Peter Merholz www.petermerholz.com PEOPLE ARE NOT THEIR JOB TITLES. TEAM MEMBERS ARE NOT “RESOURCES”. PEOPLE WORK BEST WHEN THEY CAN BE THEIR FULL SELVES. YOU CANNOT CALCULATE AN ROI FOR DESIGN. FRAMING THE PROBLEM IS MORE IMPORTANT THAN SOLVING THE PROBLEM. (DESIGN) LEADERSHIP IS MORE TALKING THAN DOING. YOU’LL DO A BETTER JOB IF YOU LIGHTEN UP IF YOU HAVEN’T PISSED SOMEONE OFF, YOU’RE NOT DOING YOUR JOB RIGHT. NO ONE OUTSIDE YOUR TEAM UNDERSTANDS WHAT IT TAKES TO DO GOOD WORK. THE OUTCOMES ARE BETTER WHEN EVERYONE IS A DESIGNER. AGILE TRANSFORMATIONS ARE HOSTILE TO GOOD DESIGN. WHAT A DESIGN TEAM NEEDS MOST IS A CLEAR SENSE OF PURPOSE. YOU ARE ON THE FRONT LINE OF A GLOBAL WAR FOR TALENT. EVERYONE APPLYING FOR A ROLE HAS AN INFLATED TITLE. INTERVIEWS ARE A POOR WAY OF ASSESSING CANDIDATES. DESIGN EXERCISES ARE A BAD INTERVIEWING PRACTICE. YOU WILL NEVER HAVE ENOUGH DESIGNERS. YOU WILL NEVER HAVE ENOUGH TIME. THE SKILLS THAT GOT YOU HERE ARE NOT THE SKILLS THAT WILL CARRY YOU FORWARD. Truisms designleadershipteamwork