Home > Articles > Software Development & Management

Exploring the Mythical Weekend Coding Project

Did you ever spend a weekend working through some kooky idea for coding an app you'd had in mind for years? Like many of us, Dhanji R. Prasanna has carried concepts around in his mental pockets, and one day he decided to go ahead and try it. The goal was a working app in two days. Would he succeed or fail miserably? Some things he learned were to be expected, but others he could never have predicted.
Like this article? We recommend

Recently, I decided to give up one of my weekends and see if I could build an entire working product from scratch. If you're like me, you have a lot of ideas rattling around in your head and far too little time to realize any of them. Some seem like world-beaters; others are interesting asides that would probably delight a niche audience. Regardless, I can't shake the feeling that the world—and certainly I—would be better off with these ideas material in reality (and, perhaps more importantly, out of my head).

I'll give away the ending: I succeeded. It took me roughly 16 hours to plan, build, and launch my idea to the world. And then, there was the anticlimax.

But before we get into that, let me retrace my steps over a grueling, frustrating, and wholly satisfying two days.

The Idea

The easiest part of the whole process was the idea. Not only do I have far too many of those available, but at any given time I'm also sitting on a pile of partially built prototypes. They currently number in the twenties and were variously built at airports, hotel lobbies, conference venues, and at any other time that I imagine the rest of the population spends at the beach and on other healthy activities.

If you hack on open source or your own startup ideas, you know exactly what I mean. Many of these projects will never see the light of day, but there is a primal, irrepressible need at the cellular level to try.

I picked the one that I've been thinking about most recently, and I opened my code editor. As a lark, I decided to put this up on Twitter:

Attempting "weekend coding project" Goal: working app in 2 days. Will I succeed? 
Will I fail miserably? Watch this spot for hourly updates!

The Journey

There was quite a spirited response, plenty of encouragement, curiosity, and some snark for good measure:

@dhanji It'll kinda work but then you'll never finish it really is what usually happens.

@dhanji hashtag please

@dhanji Wats the app? Wat technologies u using?

I hadn't planned to put anything on Twitter, and I certainly hadn't planned on anyone following me through two days of blathering on about obscure compile bugs, PEBKAC errors, and mostly simple RTFM whining.

This was an unexpected boost to my productivity and cheer. It turned into a game: If I ran into something frustrating, I cursed and swore on Twitter while my friends cheered me up or brought me back down to earth.

Feeling a lot slower than I normally do with this setup. 
Waiting for that boulder to cross the crest of the hill #weekendproject
@dhanji perhaps it's all the tweeting slowing you down :D

If I achieved something, I could immediately shout it from the rooftops and be greeted by a wash of enthusiastic replies. This fact kept me engaged and determined to see the project through. As easy as it sounds, keeping your focus for two straight days is extremely difficult and tiring. If you don't believe me, keep a count of the number of times you're distracted during a normal workday. At an office, people come around for coffee, chat about their weekend plans, talk about paperwork they need done, and so on. At home, there are plenty of other distractions: roommates, children, chores, and what-have-you. Even when left completely alone, we're relentlessly distracted by all those blogs to follow, YouTube clips to watch, and Facebook and Twitter updates to read.

Setting all this distraction aside and concentrating on a single task for even a day is an incredibly intense activity. I think that the brain is better suited to processing a variety of inputs over time and periodically being given the freedom to wander. Processing on one task exclusively is thus brutally exhausting.

Taking microscopic breaks to tweet my progress and receive reciprocal cheerleading was invaluable. Engineers from Heroku and MongoLab even discovered what I was doing and chimed in to offer their support:

@dhanji Glad you'll be checking us out. Definitely email us at support@mongolab.com if anything comes up.

@dhanji DM me if you need a hand with anything Heroku-related.

This encouragement took hardly any effort on their part, but when I was sometimes frustrated and ready to discard Heroku for Amazon Elastic Compute Cloud (EC2) or Mongo for PostgreSQL, I thought twice—and I'm sure I would have been less willing to stick it out without their encouragement.


When you're under the gun, the first thing to get tossed out is testing. In a small, inconsequential project like this, it isn't really a problem. In fact, skipping tests really reduces your drag coefficient when you're trying to fly through a set of tasks, as I was. (This makes for a rather dangerous drug, though; many engineers take it to mean that the tests themselves are either unnecessary or unimportant enough to write during the proverbial "crunch time.")

I did stumble once or twice, however; and here tests were very useful. Not in their traditional role of protecting well-honed code against regressions from newer, rawer additions—rather, in the form of test-driven development (TDD).

TDD is actually a wonderful tool for probing the behavior of an API or library. You get to script very specific "what if" scenarios that would otherwise remain in the realm of idle speculation. Specifically, I wasn't very familiar with the details of MongoDB's Java Driver, and I was able to validate my (apparently faulty) assumptions trivially with a few simple tests.

After struggling with puzzling behavior late on Saturday night, I gave up, frustration at full tilt. Coming back the next morning, however, a methodical, reasoned approach, tight along the rails of TDD, worked beautifully. I solved in minutes what had thwarted me for hours just the night before.

By no means am I advocating TDD as a religious practice. I wrote a grand total of four tests, and I stopped writing them as soon as I had decent visibility into my component of interest.


So here's Pasteboard, in all its glory. It's a pasteboard—drag pictures onto it from the desktop and share the pasteboard via URL. A fairly simple concept, but it was a lot harder to realize than you might think. Of course, I wasn't expecting Google or Facebook to beat down my door on Monday morning, stock certificates in hand, but I wasn't sure what I was expecting, either. People seemed genuinely to enjoy using it. I was pretty much done with it—after 16 hours, I didn't want to see the code again, or think about the program's future.

So what could I take away from this experience? On reflecting a bit, I realized I could take away a great many things. They fell broadly into two categories:

  • Things I would have done differently
  • Techniques I would repeat because they worked so well

In the latter camp were things like Heroku, mongoDB, and my approach to testing. In the former camp, however, I classified the following:

  • No login restriction (and no Twitter sign-in).
  • Allow anyone to paste pictures on any board.
  • Get rid of commenting—it was hardly used.
  • Focus more on picture resizing and rotation.

Do you notice what's interesting about this list? All the items are product features—if I had a do-over, they're things I would have changed about the product in the first place. Whereas my assumptions had been validated nicely in technical matters—choice of platform, storage solution, and so on. In hindsight, this pattern is fairly obvious: My expertise is in engineering, so I'm much more likely to make good decisions about engineering matters. However, I had no prior experience building a pasteboard, so many of my product assumptions were wrong.

This was the single most important take-away from my project. Your expertise is almost never in the product that you're building (even if that's an engineering tool), and you gain that expertise only through a real-world test of your assumptions. Just 50 people on Twitter giving me feedback was more valuable than all the deep meditation and prototyping I've done about this idea over the past several months.


My weekend project will never go beyond this little experiment. Nor do I need more—I've seen it out in front of real users, learned some valuable lessons, and (more importantly) gotten it out of my system. I had ups and downs and found a good process for working through problems both technical and motivational. In a sense, this was a micro-startup experience, fast-forwarded and compressed into a single weekend. It validated several of my assumptions about the product, and it exploded many more. I am thus armed with far better tools for future projects.

I encourage you to try this experiment, too—your ideas always look and sound better in your own mind than in material reality. One's own reality distortion field is stronger than anything else. Once an idea takes form in the real world, however, your perspective will be very different. Often you'll find that an idea isn't really as impressive—or particularly distinctive—as you had hoped. But in the process you may discover things that truly are both impressive and distinctive.

Read Dhanji Prasanna at http://rethrick.com/about or find him on Twitter at http://twitter.com/dhanji.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020