Neon Rocket

Even Neo is Impressed

RSS 2.0

worst practices


Requirements Gathering: set up to fail

Without project requirements gathering, a project is nothing. One failure point is letting the wrong people gather the requirements. There are basically two types of requirements for an application project: the functional/feature-set and the technical. Pitfall: There must be at least one cycle of comparing Functional to Technical requirements to ensure they sync up, followed by adjustments to both (as necessary). …Continue reading →

Don’t hate your users

If you want to enable your users to do something, such as create an account on your system, DO NOT MAKE IT IMPOSSIBLY HARD. Case in point: If algebra is too hard, just refresh and you’ll see something else. Woah, better refresh. You know what this does? It not only keeps out any bots, but turns a normal human into something …Continue reading →

How to ask for help the wrong way

When submitting  bug reports, it is a good idea to Realize that you’re asking for help from people who (usually) have day jobs, and Expend at least some amount of effort to show you’re not expecting someone else to do all the work. With that in mind, let me introduce to you the Best Bug Report Comment, Ever† First the bug …Continue reading →

The Importance of Not “Designing” your own Security

Recently, at a client, I had the opportunity to review their security implementation on their website. I realized that it is very important to never try to design one’s own security, because of the Dunning Kruger effect. In a nutshell, folks who don’t know very much about security think they know “enough,” and folks who are very knowledgable (e.g., Bruce …Continue reading →