iTranslated by AI
Why You Shouldn't Treat Devin as a Human Junior Engineer
Treating Devin as a human junior engineer or intern is an idea that has been introduced in various articles.
In fact, the official documentation contains statements to that effect.
However, the mindset of "treating it like a human junior engineer or intern" can become a factor that limits Devin's potential.
In reality, Devin is not a human junior engineer or intern.
Of course, human junior engineers and interns must be treated humanely and ethically. However, Devin is an AI software engineer and is ultimately nothing more than "one of the tools."
Therefore, it is conceivable that work could be advanced more efficiently and effectively by giving instructions that would be unacceptable (or generally not recommended) for a human.
Yet, treating Devin like a human junior engineer or intern may unconsciously restrict such flexible thinking.
For example, suppose there are several possible approaches when implementing a certain task.
If you treat Devin as a human junior engineer or intern, you would follow the "same process as a human," which involves requesting the task first and then repeating trial and error within the session to decide on an approach. This is a natural way of thinking when requesting work from a human.
On the other hand, considering time efficiency, the increasing complexity of session context, and ACU consumption, there should be cases where it is more efficient and effective to instruct Devin with multiple patterns from the start, compare those outputs, keep only the "promising sessions," or choose one after comparing the final deliverables.
Treating it the same as a human junior engineer or intern will inevitably lead to longer sessions and increased ACU consumption.
Of course, depending on the task, there may be no need to try multiple patterns. However, human time is extremely valuable. If you can "buy" trial-and-error time in the form of ACU, there are many situations where doing so would be more efficient and effective.
In this way, treating Devin like a human junior engineer or intern risks unconsciously limiting our thinking. While this perspective might actually work well during the initial stages of adoption, to fully leverage Devin, we need to handle it beyond that framework. If you treat it like a human junior engineer or intern, no matter how hard you try, you will only get human-level output.
On the other hand, we are already starting to realize that, depending on the situation, AI has the potential to exceed human capabilities. In that case, there may be instances where it is preferable not to view Devin as a "human junior engineer." Rather, by incorporating new ideas and methodologies, we can expect to draw out Devin's full potential.
For those who want to use Devin
By signing up for Devin through the link below, you can receive additional ACU according to your plan. I would also be happy to receive ACU as well.
Discussion