// I need to

ModernizeUpgrade without breaking it RescueFix what someone else started Build NewTurn an idea into a product Reach More PeopleGet found, get used, include everyone

// Company

Case StudiesExpertiseAbout + CareersResourcesContact Book a call →
≡articleBuild New

Fun and Profit

Miss solving problems yourself when libraries do the work? Project Euler and other outlets for coding just for fun, practice, and optimization.

Art+Logic Jul 10, 20132 min read

From the Art+Logic archive · written in 2013. The tools may have moved on; the thinking still holds.

Image of money by Giorgio Trovato on Unsplash

A good developer will be familiar with and use numerous libraries. If you can find a library that is a good fit for your problem, it’s probably a better solution than your first crack at it will be. And the library has been reviewed, debugged and optimized by a wide community. And more often than not, like the guy in the meme above, we can’t spend much time hot-rodding code to see how good we can get it. These can lead to work which is a little stifling for anyone who likes to think about how fast that loop could be, or how he would implement that image processing feature. Where’s the fun?

I’ve found a couple ways to get the thrill of solving a problem for myself, in the language or my choice, and spending as much time tweaking, optimizing and rewriting as I could take away from Netflix marathons and scrolling through social media feeds.

Project Euler. For the mathematically minded. This site has a large number of problems to solve. They don’t care how you solve the problem, but it’s expected that you’ll write some code to come up with the result. If it’s correct you are free to enjoy the icing on the cake, the discussion forums. I’d say at least half the benefit of working these comes from seeing how others achieved their results and the problem author’s tips.

MOOCs. I’ve taken three Massive Open Online Courses over the past couple years. They all expanded my mind, and gave me the opportunity to work on some of the types of problems I rarely see in day to day programming. Topics like planning via dynamic programming, Markov chains, Bayesian classifiers, and proportional controllers are not going to be something most of us are often called upon to do for a paycheck. When given as manageable problems as they were in the courses I’ve taken, they are a lot of fun.

Stack Overflow provides a different kind of challenge coupled with a video game like reward system. This is more like work than my other programming pastimes. It is serious business we all most likely rely on. So it might appear odd that I would recommend it as something fun. But for relative newbies like me with still low reputation scores, receiving an upvote on a question they answered a year ago will understand. An unexpected +10 reputation simply feels good.

For a few years after I first graduated from college, I would spend a lot of time working on apparently worthless projects. Some of the strange things I did were a checkers program that could be played with a scripted opponent, a program for randomly scrambling audio data, and another to render and blur text for a shadow effect to name a few.  I didn’t realize it, but I was making technological bets and investments. I couldn’t have known exactly how the work I did for fun back then would position me to be ready for some of my most rewarding projects I’ve done in my day job, but that’s exactly what they did. Hasn’t that always been the secret of play?

keep going

More to explore in Build New.

All Build New resources →
let's talk

Got a problem like this one?

Tell us what's stuck. A real person replies within one business day.

Talk to our team →

Talk to people who know software, not a sales script.

Your first call is with Aja, our VP of Sales. He'll help make sure you're solving the right problem. Here's what you'll cover together:

  1. What you're trying to accomplish

    The business goal first, then the technology.

  2. Possible approaches

    And the tradeoffs of each, in plain language.

  3. Risks you may not have considered

    Technical and business, before they cost you.

  4. Whether AI changes the math

    What's practical, and what's just hype for your project.

  5. Sensible next steps

    Even if the right next step is not us.

book-a-call.ics

Loading the scheduler…

Open the booking page →

Some problems are easier to explain in writing. Send us a few lines about what you're working on, and we'll reply within one business day. Helpful to include:

  1. What the software does, or should do
  2. What's stuck, or what's worrying you
  3. Any deadline or budget you have in mind
note.md

Loading the form…