How can I be disciplined with coding?

The explicit coding discipline favors clear and explicit expression of intent in the code. It suggests writing meaningful names for variables, functions, classes and other constructions. It suggests avoiding tricky solutions in favor of readings and clear intent. The uses-cases dictate the structure of the application.

How do I know if I am a good programmer?

i would simply say: if you’re passionate (i mean REALLY passionate) about what you do, if you’re flexible (another language, new technology, complete remake of an old project – let’s do it!), if you keep learning and improving your skills and never, never think you’re good enough to stop – then you’re a good programmer …

What is an explicit code?

For clarification, when you are writing code to handle different kinds of things, then you are writing explicit code. However when this same code has already been written and you are reusing it with a simple method call, then the behavior in this new context is then implicit.

Why discipline is useful in the software development processes?

With a disciplined process, managers develop a better sense of how long it takes to accomplish various kinds of tasks and what kinds of skills are needed.

What is lazy code?

In programming language theory, lazy evaluation, or call-by-need, is an evaluation strategy which delays the evaluation of an expression until its value is needed (non-strict evaluation) and which also avoids repeated evaluations (sharing).

What makes a lazy programmer a good programmer?

Lazy, because only a lazy programmer will avoid writing monotonous, repetitive code – thus avoiding redundancy, the enemy of software maintenance and flexible refactoring. Mostly, the tools and processes that come out of this endeavor fired by laziness will speed up the production. This makes a lazy programmer a good programmer.

Can being dumb make you a better programmer?

Being dumb—or at least trying not to be so clever—can help you remain humble and open to your colleagues’ advice. You may want to rethink these so-called flaws. Being lazy and acting dumb can actually make you a better, more productive, constantly improving programmer.

Do “lazy” programmers get rid of drudgery?

But Lenssen asserts that in the process of eliminating those unnecessary steps, the “lazy” programmer also is getting rid of future drudgery. If this programmer has to do something more than once, he will consider automating it, thus speeding up and improving the process.

What drives a programmer to improve his workflow?

If this programmer has to do something more than once, he will consider automating it, thus speeding up and improving the process. Being lazy also will drive a programmer to determine which software tools make work easier and to ensure that work can be maintained and refactored easily.