Home » Author Archives: Dalip Mahal (page 2)

Author Archives: Dalip Mahal

Dalip is a principal consultant at Accelerated Development and has worked his way through all aspects of software development. He started as a software engineer and worked his way through engineering and product management.

User Stories are Rarely Appropriate

All tools are useful when used appropriately, and User Stories are no different. User stories are fantastic when used in small teams on small projects where the team is co-located and has easy access to customers. User stories can quickly fall apart under any of the following situations:   the team or project is not small the team is not ...

Read More »

Seriously. The Devil Made me do It!

Just as eternal as the cosmic struggle between good and evil is the challenge between our two natures. Religion aside, we have two natures, the part of us that: thinks things through; make good or ethical decisions a.k.a. our angelic nature react immediately; make quick but often wrong decisions a.k.a. our devil nature Guess the powers that be left a bug in ...

Read More »

Failed! You get what you deserve!

Consider this, few projects fail because of unusual or unforeseen problems.  If you are trying to go so fast that you don’t do your due diligence or decide to skip steps then — “You get what you deserve!“. Projects succeed because they do not rely on force of personality and luck. Only 3 of 10 software projects succeed (see Understanding ...

Read More »

Don’t be a Slave to Your Tools

Developers attach quickly to tools because they are concrete and have well defined behavior.  It is easier to learn a tool than to learn best practices or methodology. Tools only assist in solving problems, they can’t solve the problem by themselves. A developer who understands the problem can use tools to increase productivity and quality. Poor developers don’t invest the ...

Read More »

Are Debuggers Crutches?

Debuggers have become powerful tools, but like a drug have we become too dependent on them? Since poor developers spend 25 times more time in the debugger there is a likelihood that people are zoning out in the debugger instead of using other methods. Defects are common, but they are not not necessary.  They find their way into code because: ...

Read More »

Agile tools do NOT make you Agile

 Ask yourself the following questions: Do great golf clubs make you a great golfer? Does a formula one race make you an expert driver? Do great development tools make you an expert developer?     Unless you are delusional, you know that the answer is NO to all these questions.  An expert’s performance can be dramatically improved with the right ...

Read More »

Productive Developers are Smart and Lazy

When I use the terms Smart, Lazy, and Developer, I mean the following: Smart as in intelligent and able to think things through (i.e. not smart-ass) Not a dreamer who never gets around to writing anything practical Lazy as in lazy-loading, that is wait to write code (i.e. not couch potato) Developer as in energetic and focused on building real-world ...

Read More »

The Programmer Productivity Paradox

Programmers seem to be fairly productive people. You always see them typing at their desks; they chafe for meetings to finish so that they can go back to their desks and code. When asked, they will say that there is not enough time to produce the code, and the sooner they can start coding, the sooner they will be done. ...

Read More »

When BA means Bt Artist

BA  means Business Analyst, but what makes for a good BA?  When do you have a good BA and when do you have someone who isn’t? Many projects fail at the beginning due to incomplete, inconsistent, and overly verbose analysis that then leads to incorrect project plans and projects heading in the wrong direction. Business analysis consists of all facets ...

Read More »

No Business Case == Project Failure

A business case comes between a bright idea for a software project and the creation of the software project. To – idea to have a project is born Tcheck – formal or informal business case Tstart – project is initiated Tend – project finishes successfully or is abandoned Not all ideas for software projects make sense.  In the yellow zone ...

Read More »

Want to take your Java skills to the next level?

Grab our programming books for FREE!

Here are some of the eBooks you will get:

  • Spring Interview QnA
  • Multithreading & Concurrency QnA
  • JPA Minibook
  • JVM Troubleshooting Guide
  • Advanced Java
  • Java Interview QnA
  • Java Design Patterns