Act as if You Have Infinite Time...

Table of Contents

Act as if You Have Infinite Time…

Tick tock, tick tock… The clock is inevitably ticking, time is passing, the deadline is approaching, yet the tasks are not decreasing. The more you rush, the more shortcuts you take, the more problems arise. Meanwhile, the answer is simple: Act as if you have infinite time!

Alright, it’s not really that simple, at least not simple to implement. Usually, a manager, client, project manager, or analyst stands over your shoulder and mercilessly reminds you of the approaching deadline. They certainly do not expect you to start working as if you have infinite time. After all, they probably know Parkinson’s Law, that work expands to fill the time available for its completion! And they won’t allow you to have too much time. Hence the emphasis on deadlines and commitments.

Meanwhile, programming is a very sensitive matter… many variables, a lot of information, assumed architecture, project structure, a multitude of technologies and tools, all contribute to making it difficult for a programmer when there is no time. There are many parameters, and it’s easy to make mistakes, which are multiplied by haste. Taking shortcuts causes more harm than good, and paradoxically, temporary solutions born out of haste become the foundation of the production system.

That is precisely why you should act as if you have infinite time! At such moments, keep telling this to yourself relentlessly and believe me, it won’t make you lazy! Your manager, client, project manager, or analyst won’t let that happen. However, it is important to mentally slow down to protect yourself from self-destruction, sleepless nights, and strained relationships with family or friends… well, maybe I am exaggerating! But sometimes, a bit of a scare is necessary ;-)

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

Weekend Workshops: Design Patterns

Invitation to Weekend Workshops on Design Patterns

We cordially invite you to the “Weekend Workshops on Design Patterns.” This is a special offer for users of the Goldenline.pl portal and readers of my blog as well as Michał’s. You won’t find this offer on the BNS IT website!

Read More

The Natural Order of Refactoring Under the Microscope Part 3: Extract Method

Analyzing Class and Method Responsibilities

In the next step, we examine the responsibilities of individual classes and methods, checking if they align with the intended responsibility of the class. It is best to analyze all methods and group them based on performing similar operations. We look for a place for these in other classes or a new class. Remember: if there is a significant private method in a class (longer than 3-4 lines), it should be moved to another class.

Read More

Task-doing vs. Responsibility Taking - A Subtle Distinction

The Subtle Distinction Between Task-doing and Responsibility Taking

I have been reading a book on parenthood recently (yes, tech guys also read such books :-)) and there has been a discussion about responsibility. Even when fathers devote their time to spending time with children and doing some tasks related to children and family, they may still not take responsibility for it. So you can take your children to the doctor when they are sick, bring them to school or kindergarten every day, go with them to a playground… and still not take responsibility.

Read More