Define when it should end

I think the most important thing is to know when your project will be done. When you start a journey where you don’t know where to go, any path is an option. You can easily lose your focus and walk in circles. When you define your final destination, you can build the path to there. In my experience, it helped a lot. I had to write a proposal before writing the book. The proposal helped me to create the scope of the book. That scope wasn’t written in rocks, I could change it. However, functional programming is a large subject, drafting the table of contents first helped me to see how far the book would go and what the readers would learn.

Breakdown your tasks

“How long to finish your book?” I’ve lost count of how many times I’ve been asked this. It is very hard to answer that question, especially when some tasks are out of your control. But, at least, you can get an idea of how far you’re close to the end.

When you have your final destination, it’s time to break down your path to there. There are many techniques of breakdown and tools to keep track of your tasks. You don’t need to invest too much time in planning your project, things can change and you might need the flexibility to change your direction.

In my experience, writing a basic summary of each chapter helped me to have an idea of how big they would be. Then, before start writing a chapter, I wrote all the chapter sections’ titles to give the chapter a structure and to define how it should end. Breaking down the book in chapters and chapters in sections, helped me to answer the question “how long to finish?”. Now, I could answer for example with “there are 2 missing sections to finish this chapter”, or “there are two missing chapters to finish the book”.

Create a routine and ask help to protect it

If you want to finish your project, you need to work on it. How many hours per day? How many days per week? It depends on which type of work you are doing. I suggest you to find a space to work on the project every day, but save 1 day per week to rest. You need a routine and you need to protect it to finish your project.

It can sound tough, I know. However, it reminds me of when I was studying in college. I worked during all the day and studied at night. If you had done something similar in your life, you’ll know what I’m talking about. But this time, for me, it wasn’t study and work, it was work and work. You don’t need to face this journey alone. You can ask support from family, partner, kids, and friends to help you to protect your routine.

Some people will be tempted to avoid work every day and will try to work many hours on weekends. The problem is if you can’t work one weekend, you will lose an entire week of progress. When you miss a week, it’s easier to lose motivation because it’s harder to recover from that. If you work a little bit on your project every day, it helps you to keep progressing. One day that you miss, won’t be a huge impact on your routine.

Creating a routine to work on your personal project is not an easy task. You might stop doing some other stuff in your life. Don’t get too stressed trying to do everything you had been doing. Admit soon that you’re not a superhero. You might need to stop or slow down in other activities in your life to work on your personal project. Like a friend said, “life is an exchange”.

Look for Feedbacks

If your project will impact people, show it to people. Don’t spend too much time working just for your eyes. Everyone has blind spots, so you can be making mistakes that other people with a fresh mind can easily spot.

First, look out for your target audience. Invite them to review what you are doing. Also, look for professionals, people that are experts in the field that can help you. When I was writing my book, I had help, not just from excellent developers, but also from book writers and English experts.

Sometimes you can get upset if some people that you asked support didn’t help you, even though they said that they would. People have their life, their stuff to do, your work is not their priority. Just don’t put all your eggs in one basket and you’ll be fine. In some cases, you may need to invest some money to have a expert feedback that you need.

Time to rest

“All work and no play makes Jack a dull boy”. Some people are fully committed to their project and they forget to rest. They can do that for one week, maybe one month. Sooner or later, they’ll burn out and give up on their project. It could be avoided by using their free time to relax.

When you are stressed and tired, it will start impacting your full-time job. If our personal project impacts our job, you obviously will give up your project to work on the most important one. The job that pays your bills.

Managing your energy is a hard task, try to save at least one day to rest. If you are thinking about scheduling your next vacation to work on your project, please don’t. Especially if your project can take a year. It’s something that I wouldn’t personally do anymore. Time is one of the most precious things you have in your life. Vacations are a special moment to rest and spend time with your family and friends. You would never have that same moment again in your life. If I had to choose again, I would have chosen to enjoy my vacation.

Recovering is more important than having no failures

If you are running a personal project that can take several months to finish, you can fail. You can burn out and give up on your project. It happens. It happened to me.

It’s very important to create strategies to manage your energy and maintain your routine. But, the most important in my opinion, is how you will recover from a failure. You may need to take some time to rest, maybe you should talk to your trustworthy friends about what how miserable you are feeling. You need to figure out what you did wrong and learn from your mistakes. Then, finally, go back to work when you have energy again.

I don’t know if it works for you, but it’s a relief to me, every time that I remember that I can fail and try again.

I hoped you liked my personal experience and lessons learned from running a long project in my free time. Have you tried to work on a personal long project? Do you have some lessons learned to share? Something that helped you? Please, let me know in the comments below.

One last thing, my long project was Learn Functional Programming with Elixir book. You can have the e-book or the printed version on The Pragmatic Bookshelf or Amazon. You can have a free chapter by following the instructions of this link.

The post Long projects in your free time first appeared on Plataformatec Blog.

A couple of months ago, our team member Ulisses Almeida blogged about the release of his book, Learn Functional Programming with Elixir. It’s still in beta and you can buy it on The Pragmatic Bookshelf website. To celebrate this occasion, we have something special for you.

We have reached out to Ulisses and PragProg and they allowed us to give away the first chapter of the book: Thinking Functionally. \o/

What’s there for you

This chapter focuses on functional programming concepts. You’ll understand the mindset required to program functionally with Elixir, and you’ll learn these three core principles:

• Immutable Data
• Functions
• Declarative code

Above all, this book is for who wants to learn Elixir and functional programming from the very beginning.

If you know absolutely nothing or a little bit of Elixir (the same for functional programming), this book is definitely for you; or if you gave up learning Elixir because it’s different from the programming language you use at work like ASP, PHP, Java and so on, this book is perfect for you, too.

After reading it, you’ll be able to think functionally.

Click the button below to get the first chapter of the book Learn Functional Programming with Elixir.

Download Thinking Functionally for free

The post Thinking Functionally first appeared on Plataformatec Blog.

Why Writing a Book?

Last year, we were, company-wise, looking for different ways to contribute to the Elixir community. At some point, Hugo Barauna reached out to me and said: “Why don’t you write a book?”. I must tell you: I wasn’t ready.

I’m Brazilian and Portuguese is my native language. Writing a book in English is a great challenge. I thought about everything that I would have to give up to write a book (goodbye, video game nights) and then… I accepted it.

Once Hugo told me The Pragmatic Bookshelf was behind it, I felt motivated. I had a big challenge in front of me, but I knew I wouldn’t be alone. But most of all, what made me most excited about the book was the opportunity to present a different way of learning Elixir that might help people that are stuck in their journey.

Why Functional Programming with Elixir?

After accepting the challenge, I had to write a book proposal. It’s a document outlining the book topics. The Pragmatic Bookshelf is one of the most important technical publishers. Your proposal must stand out if you want to be accepted. One of the ways to stand out is to figure out exactly what the other books are missing.

We have great Elixir books. Some of them are for expert programmers, others are for beginners. These books usually focus on Elixir features and OTP. But they don’t slow down and explain functional programming. Then, observing that functional programming was missing in these books, I came up with an idea of a book that has a balanced level of Functional Programming and Elixir.

I had to do my homework in order to explain why teaching functional programming and Elixir together is a good idea. To write a book, you need to read books. I had to read beyond all of the Elixir books out there. I used dynamic reading, looking for content that authors weren’t talking about.

What’s in the Book?

You’ll find a beginner’s guide to functional programming concepts, at the same time, you’ll be introduced to Elixir. You’ll learn:

The book introduces functional programming while teaching Elixir in the proper pace. For example, in other books, the recursion concepts are presented fast in two or three pages. Meanwhile, in Learn Functional Programming with Elixir, you’ll have an entire chapter with more than twenty pages explaining many concepts, like unbounded and bounded recursion, divide and conquer, and tail call optimization.

The Next Months

Before the release of the book’s final version, we’ll release two more chapters. We’ll refine the book with all suggestions and errata from readers during this beta phase. Soon, the book will reach its final stage and it’ll also have a printed version.

Thanks to Jackie Carter and Bruce Tate from The Pragmatic Bookshelf, Plataformatec, technical reviewers, beta readers, and friends, we’re building a great book.

If you bought it and you are reading it, I’m counting on your feedback. For now I have to go, I have a lot of work to do! XD

The post Book Release: Learn Functional Programming with Elixir first appeared on Plataformatec Blog.