They are slow
Often I see many developers focus on speed. during some decision-making discussions he already thinking about implementation at the code level, after the meeting, immediately opened VScode and code, the test was only a “refresh page”, and no bugs came out, He fixed it fast, and new bugs came again, and fixed again, fast.
Does it sound good? no. looks bad? yes.
Only a few developers, during the design phase, think through the flow and use cases and start asking questions. design test cases, and write test cases. interfaces, implementation, inject concert class into abstraction, run.
I won’t say 0 bugs, but much less.
Often I see some devs reply to the message very fast.
“Can you get this done within today?”, “Of course. pushing a fix now”, and “Try again now”.
“Is this easy to fix?”, “Yes, give me 10 mins”.
“What is the reason for this issue?”, “I think it should be a data issue, not a bug”.
Responsive to simple questions is good. however, not all the questions are so simple to answer immediately, spend your time to find out, no one will blame you for slowness.
For other developers, I see they work a “smarter way”.
“Let me discuss it with my team and get back.”
