Understanding Engineers' "I Can't" and What It Really Means
Written on
Chapter 1 The Complexity of "I Can't"
In conversations with engineers, it's common to hear queries like, "Can't we achieve this?" followed by a response of, "Hmm, that's challenging. We can't do that." This exchange reflects a deeper meaning behind the term "can't." There are various interpretations of this word, ranging from genuine limitations to potential adjustments that could make it feasible. It's crucial to delve into what engineers truly convey when they say "it can't be done."
We often hear that engineers may lack the vocabulary to express their limitations clearly. This communication gap can lead to misunderstandings, hinging on mutual trust. It's essential to foster better dialogue to grasp the engineer's perspective when they express that a task is unfeasible.
Section 1.1 Current Functionality Constraints
Consider a scenario where someone asks, "Can we track the clicks on this button?" The response might be, "I can't do that right now (I could if I developed a solution and deployed it later)." This indicates that while it's not possible at the moment, it doesn’t imply that it is impossible indefinitely. Instead of abandoning the idea, it could be worthwhile to inquire, "Does this mean it's not feasible with the existing capabilities?"
Subsection 1.1.1 Time Limitations
If the question arises, "Can I modify this design?" the engineer may respond, "I can't do that (given the current deadline). (Perhaps I could if the deadline were extended or if I reprioritized other tasks.)" Development schedules often impose strict time constraints. When urgent requests come in, engineers might instinctively say, "I can't do it," though adjustments could make it possible. Exploring whether time or resource allocation could enable the task is beneficial.
Section 1.2 Challenges of Implementation
When asked, "Can you speed up the image loading time?" an engineer might reply, "There are options, but they aren't straightforward. (If you can allocate about two weeks of work, I can adapt it to WebP format or modify the image size.)" This scenario highlights that while solutions exist, they may require significant effort or time. Clarifying expectations, such as, "I'm not in a rush, but what if I gave you a couple of weeks?" could change the response.
Chapter 2 Skill Limitations and Learning Opportunities
Inquiries like, "Can you suggest posts I would enjoy?" might elicit a response of "I can't do that (with my current skills). (I could learn how or collaborate with someone knowledgeable.)" The notion that something is too challenging often masks the opportunity for growth. It can be invigorating for an engineer to venture into new areas, provided they have a timeline for when results are expected.
Section 2.1 Potential Problems with Current Designs
When posed with a question like, "Can we display this kind of information here?" the engineer may respond, "That's not feasible (due to current design limitations, which could lead to performance issues and slower displays)." While the request may be valid, it could introduce new complications. Understanding the trade-offs involved often requires insight from someone familiar with the underlying code.
Section 2.2 Rethinking Functionality Requests
In situations where someone asks, "Can we implement this search filter?" the engineer might respond, "I can't do that (because it may lead us in the wrong direction regarding functionality)." This response can sometimes stem from a lack of clarity about the intention behind the request. Sharing the rationale behind the request can provide valuable context, potentially leading to better solutions.
Ultimately, engineers often hesitate to say "I can't" because it feels negative. However, constraints related to time and resources can make it challenging to commit to an affirmative answer. The important takeaway is that very few things are genuinely impossible; rather, they often involve overcoming obstacles. When an engineer states, "It can't be done," it's beneficial to interpret this as a signal that while it may not be straightforward, solutions are possible with the right adjustments and collaboration.