Speed-coding

I am working on an application prototype, that will eventually evolve into a full blown application that allows the tracking of projects through their life-cycle (beginning with the funding and through the closing of the project). As part of this, I have outlined an API of about 50 stored procedures that provide the database functionality for this application (which is otherwise an ASP.NET application). Now, since this is a prototype, I’ve just been coding away, but in the next two days, having the stored procedure API would speed up my ability to do my work. So… I am going to spend the rest of the morning doing some speed-coding. Just how many of the 50 stored procedures can I get written in the next 2-1/2 hours?

I’ll let you know after lunch…

Published by Jamie Todd Rubin

Jamie Todd Rubin writes fiction and nonfiction for a variety of publications including Analog, Clarkesworld, The Daily Beast, 99U, Daily Science Fiction, Lightspeed, InterGalactic Medicine Show, and several anthologies. He was featured in Lifehacker’s How I Work series. He has been blogging since 2005. By day, he manages software projects and occasionally writes code. He lives in Falls Church, Virginia with his wife and three children. Find him on Twitter at @jamietr.