The next technique to keep in mind is called timeboxing. At the very least (if you're still not convinced by now to use source control), apply the Copy Folder Versioning anti-pattern and make yourself a backup copy (or ZIP) of the folder you're working on. And if you're stuck, before you start ripping everything you're working on apart or throwing things at the wall to see what sticks, make sure you have a copy of the code in a working (or very nearly working, if that ship has sailed) state. Even if you're not writing tests, Check In Often. If you're following TDD, try to also follow Red-Green-Refactor-Commit (or even RGCRC) as you do so. Ideally, you committed (at least locally) the last time you found yourself in a KGS. Obviously, the best way to do this is through the use of source control. In any case, the first thing you should think about when you find yourself running into problems is make certain that you have a means of returning to a Known Good StateTM (KGS). A much better literary analog would be Ariadne's Thread, but this is much less well-known. Sadly, although this story demonstrates that breadcrumbs are a terrible way to find your way back to a safe location, this term continues to be used to describe exactly this feature. The story of Hansel and Gretel describes how two children became lost in the woods because they left a trail of breadcrumbs, but this trail was eaten by birds, and so they couldn't find their way home. Don't waste it, or your company or customer's money! Get back to a productive (and happier!) state as quickly as possible. Remember, programmer time tends to be expensive, and your time is the most valuable asset you have. When you're stuck, when you're spinning your wheels, here are some things you can do to help get you back on track as quickly as possible. Hopefully this fact will help you avoid some natural imposter syndrome as you consider what to do (and may help if you're wondering if programming is really what you want to be doing). Take heart: facing a blocking issue that's difficult for you to diagnose is something that happens to every programmer (please comment if it's never happened to you). This is such a common occurrence for programmers that it has its own popular meme: And soon, you may find yourself growing frustrated. "No problem," you think to yourself, "I'll just try this slightly different approach." And that doesn't work, either. You're in the zone, coding away, getting stuff done, and feeling good. RoadblocksĪs a programmer or software developer, from time to time it's likely you'll be trying to solve a problem, and things just don't go your way. If you find it useful, please consider sharing it with someone you know who might also benefit from it. This is advice that I have given to many novice developers, and that I would like to have been able to give to myself when I just getting started (though some of the advice refers to resources that didn't exist then - alas).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |