Why I Use The Pomodoro Technique

Tony Cimaglia — Thu, 21 Jan 2021 11:53:59 +0000

The Pomodoro Technique

The Pomodoro Technique was invented by Francesco Cirillo. It's an
incredibly simple concept:

Start a 25 minute timer.
Work for 25 minutes straight with no distractions.
Stop for a few minutes and do something else.
Work again for 25 minutes
Repeat this cycle, and after 4 sessions of work, take a longer break.

That's it. There are tons of articles and books about the subject, most of which are going to overcomplicate everything. Can you imagine reading an entire book about setting a timer?

Why Did I Start Using This Method?

I've never had trouble focusing on tasks or paying attention to anything in my entire life. However, when the pandemic entered full swing, I found myself unable to get ANYTHING done. I was working from home with an active, loud 10 month old who just started walking. I kept changing the room my office was located in and shuffling the layout around. Even once the office was settled, I was consumed with anxiety about everything that was going on in the world. So, how did adhering to this system help me?

Staying on Track

I can't count how many times I've started a task, seen something in the code, and transitioned into doing something COMPLETELY DIFFERENT. To avoid this, I started to write down exactly what I'm working on or trying to accomplish before I start a timer:

"Create model, view, and controller for sign up screen."
"Write the logic to conditionally render check-out screen text."

I'm not a robot, so I still get lost in the sauce. Now though, I only lose a maximum of 25 minutes when it happens.

Measurable Productivity

About two thirds of my time at my current job is spent writing code. If I actually spend that portion of my day coding, and I get through around 10 cycles, I've had a fairly productive shift. It's not a perfect measure. Some days are spent in meetings, exchanging emails, or working on things that don't make sense to break up into time blocks. Tracking the cycles has at least allowed me to put something quantifiable behind what an average, productive day looks like.

Focus

Setting a timer really helps keeps me on task. I might check a text message to make sure it's not urgent. I might even reflexively check twitter. But I remember that I'm in the middle of a cycle and I get back on track. There's almost never a message or tweet that can't wait 25 minutes.

Finding Better Solutions

People solve problems with the slow-thinking portion of their brains. If I work for long stretches without pausing however, it becomes easy to slip into fast-brain thinking. That results in me writing code without thinking up front about what the best solution might be. When I break up my work flow, I'm able to think slowly for the entire cycle, and I'm usually able to come up with better ideas.

Solving Problems When I Take Breaks

Sometimes I get so hellbent on trying to fix something I become tunnel-visioned in my approach to trying to solve the problem. Whatever path I started down is the path I continue down until the task is done. However, if I break up my workflow and take a minute to breathe, I'll often come up with a much better solution to the problem at hand.

It's Not For Everyone

I know a lot of people who like to get into the zone and code for hours as time flies by. After working in restaurants for a decade and having my entire shift whiz past me in the blink of an eye, I really enjoy a slower, more deliberate approach to my work. If you're more like me, give the method a try for a week and see how you like it.

Let me know if you decide to give it a shot @TonyCimaglia.

Are Coding Bootcamps A Rip Off?

Tony Cimaglia — Thu, 27 Aug 2020 12:06:17 +0000

My Start In Software

Hey, I’m Tony. I'm a software engineer. And not long before I started writing code I was a bartender, finishing up a ten year stretch in the service industry. I worked my way up from my first job as a fry cook at a Five Guys to managing the bar at one of the best restaurants in the Southeast. I knew just about everything there was to know about my field, but ten years of long shifts full of lifting and bending was starting to take its toll on me physically. The combination of my aches and pains and an increasing feeling of boredom led me to the conclusion that it was time to find a new line of work. And, like many people who find themselves looking for the ever-elusive path to a new career, I found myself researching coding bootcamps.

The Bootcamp Model

Most of these “learn to code quick” programs boast the same basic structure: immersive learning for a small amount of time and a quick turnaround to a high-paying entry-level job. They promised that in just three months I could join the other grads (with a 97% hire rate!) who landed jobs at major companies. It sounded amazing. But what was the catch? Was it too good to be true? The answer was yes. But also, no. Allow me, a true bootcamp survivor, to share a few of the good, the bad, and the ugly truths about coding bootcamps.

Bootcamp Success

I decided on General Assembly, where I completed their Software Engineering Immersive course. Within a week of finishing I was starting my first job at a small start-up. Was it a hard three months? Absolutely. But on paper, it “worked” for me. I got a job. I was making money. I was writing code, when three months prior I was creating cocktail menus. I became another perfect success story for the bootcamps to advertise. But the truth of the matter is that a lot happened behind the scenes that contributed to my success, and not everyone in my class had the same outcome. When deciding if a bootcamp is right for you, it’s important to know what will make or break you.

The Grind

What these bootcamps don’t tell you is undoubtedly more important when deciding to attend than what they do tell you. Because what they don’t tell you is this: You will be teaching yourself most of the material. While there are teachers and TA’s to assist you, the structure of class is not designed for people who need a lot of instruction or extra assistance. Active instruction accounts for only 3-4 hours a day while the rest of the class time is devoted to solo practice. Many of the teachers are recent grads themselves. The material moves quickly. Very, very quickly. After all, the whole bootcamp model is based on making money from pushing a lot of students through in a short amount of time. If you fall through the cracks no one will catch you. If you’re not a fast and self-motivated learner, it’s easy to become one of the many students who drop out or drag themselves to the finish line just to end up unemployed because they never truly grasped the skills.

Finding Work After Graduation

They also don’t tell you that in order to find a job, you absolutely have to network. On your own. Yes, there are career coaches and presentation days all designed to steer you in the right direction and provide some opportunity for networking. But depending on your bootcamp, these resources might be minimal or even nonexistent. Even at GA, where job assistance is a point of focus, my resources were… flawed at best. My career counselor was working at GA on the side while she pursued her true passion for online matchmaking, which took up most of her time and energy. Emails went unanswered for days on end. Deadlines passed before she would notify us they existed. And while this might be a fluke, the hiring statistics are designed to hide a lot of unsuccessful students.

At GA, if you drop out you’re not counted in the statistics at all. If you do graduate but don’t participate in their career outcomes program (or miss even a single step) you’re automatically counted as a success, even if you’re never hired. “No problem, I’ll just participate in the career outcomes program, that sounds great!” You might be saying to yourself. Not so fast. The outcomes program requires you to spend a lot of time meeting application quotas and attending meetings. Most successful people I knew used that time to go out to networking events or sharpen their skills on their own, and the general consensus among my class was that outcomes was a waste of time. Could it work for you? Of course. But it’s not the 97% foolproof plan they advertise.

That Doesn't Sound So Bad...

At this point you may be thinking, “Great! I’m a self-motivated learner and I think I could handle networking. This could work for me!” And it could. But let me point out that all of the information in coding bootcamps is available online for free if you know where to look. freeCodeCamp.org is a great place to start if you're looking for a way to learn web development that doesn't cost 5 figures. If you’re truly comfortable teaching yourself and looking for your own job,
why not teach yourself how to code on your own time and save the cost of tuition? According to Course Report, coding bootcamps on average cost $13,584. While that's cheaper than a traditional associates or bachelor’s degree, it still isn't cheap.

So, Are Coding Bootcamps Worth the Money?

None of this is to say that coding bootcamps are inherently a rip off. I’m still writing code, I love working as a software engineer, and there’s no way I’d be where I am today if I hadn’t taken the leap. I won’t deny that I was successful by the bootcamp's standards. But they're not designed for everyone to succeed. The shadowy, unreported numbers represent the people who, by their standards, failed. Don't expect them to care much if you're one of them.

Have questions about bootcamps? You can tweet them at me @TonyCimaglia.

DEV Community: Tony Cimaglia