#iterative-development

#iterative-development

Voice interaction with Claude Code significantly enhances the user experience by allowing for faster input. Speaking is often 2-3 times quicker than typing, which can streamline the process of giving commands.

Santa Cruz de Tenerife is one of the most idyllic cities in the Canary Islands. At its heart stands the jewel - the Auditorio. It's a place where talent from both worlds, New and Old, comes together. A theatre, opera, dance, and music heaven.

Capacity Planning is the process of right-sizing the 'Total Project Demand' with the forecasted Team Capacity. Most UX teams have no idea what their capacity is. Fewer still have a process for calculating it and using it during quarterly planning activities with their counterparts in Product Management & Engineering to ensure teams don't commit to more work than they can handle.

Her payment form wasn't connecting to the payment processor, and every attempt ended in an error message that made no sense. I understood her frustration. As a founder myself, I was acutely aware of the pain of trying to run a business and feeling like nothing was going your way. When I dug into her form, I found the problem a few minutes later: a mismatch between test mode and live credentials.

Hello, I am about to launch a website which offers an analytic tool which will enable traders in the financial market to analyze their performance. I will post on a few selected forums an offer of free full use of the tool. CHat GPT claims that a period of 30 days will be enough as by then users will be well familiarized with the system and a longer period will be unnecessary.

Most of these companies start the journey from a functional standpoint, avoiding extra layers that may "divert users' attention", such as refined flows, potential edge cases, and, sometimes, proper visual design foundations and user experience. Here, the goal is to ship the product first to validate its value, then address other considerations.

It's been almost 20 years since I started my career in product design, and, as you might imagine, many things have changed dramatically since then. One of the main characteristics of the technology industry is the constant evolution of its dynamics, roles, processes, technologies, experiences, and even business models. Those changes are inevitable and will continue. In retrospect, I see that there is one reality that has not changed much over the last 20 years and remains a constant issue to this day: building technology products can sometimes be a discouraging and exhausting process, from junior positions to senior management levels. Why do we suffer every time we need to build something? Why is there so much burnout among today's tech professionals? Why is it that, regardless of the industry, company, or technology, we always hear the exact phrases: "I'm exhausted, I feel drained by this job."? Well, those are valid questions that still haunt me 20 years after my first web design job. It seems like there's no choice in this environment but to suffer.

"I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue."

Scrum has a bad reputation in some organizations. In many cases, this is because teams did something they called Scrum, it didn't work, and Scrum took the blame. To counter this, when working with organizations, we like to define a small set of rules a team must follow if they want to say they're doing Scrum. Enforcing this policy helps prevent Scrum from being blamed for Scrum-like failures.

During my eight years working in agile product development, I have watched sprints move quickly while real understanding of user problems lagged. Backlogs fill with paraphrased feedback. Interview notes sit in shared folders collecting dust. Teams make decisions based on partial memories of what users actually said. Even when the code is clean, those habits slow delivery and make it harder to build software that genuinely helps people.