Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
With external pressure to get something done and a full description of what needs to be done, lazy people will find a solution with the least possible amount of effort. That’s why they often make good developers.
Problems arise when there is no immediate external pressure, or when the task isn’t well-defined. In that case, lazy people will put it off until it becomes immediate (at which point the effort required may be much higher), or they will do the bare minimum to satisfy the requirements of the task according to the definition. If the definition of the task wasn’t complete, the task won’t be done completely.
Good developers don’t just write easy-to-write code. They write code that is easy to maintain and efficient to run - and oftentimes that requires forethought, a willingness to rewrite when a misstep is made, and above all else the willingness to tinker/learn effectively.
Source: I am a terrible developer and a very lazy person, and I have had to maintain lots of poorly-written code (some of it my own).
With external pressure to get something done and a full description of what needs to be done, lazy people will find a solution with the least possible amount of effort. That’s why they often make good developers.
Problems arise when there is no immediate external pressure, or when the task isn’t well-defined. In that case, lazy people will put it off until it becomes immediate (at which point the effort required may be much higher), or they will do the bare minimum to satisfy the requirements of the task according to the definition. If the definition of the task wasn’t complete, the task won’t be done completely.
Oh, this is me
Good developers don’t just write easy-to-write code. They write code that is easy to maintain and efficient to run - and oftentimes that requires forethought, a willingness to rewrite when a misstep is made, and above all else the willingness to tinker/learn effectively.
Source: I am a terrible developer and a very lazy person, and I have had to maintain lots of poorly-written code (some of it my own).
I’m a problem solver, not a planner.