Author: dojo.live

Written by Jordan R Wilman / Cartoon Illustration by Carlos Ponce

Everyone is always looking to play that ‘perfect’ card. The option that gives you the most success, least chance of failure, and the option to improve your next turn in the future. What’s the problem with that thought process? It’s a well thought out philosophy – not a methodology. 

When we look at the technology sector, which sort of skilled employees and professionals have this problem? Yes, you guessed it! The unicorns of the technology sector – developers! The ones that are always looking to perfect that exact formula; thus, allowing their skill and experience to shine through on a project that everyone will remember them for! Wrong.

Software developers are always looking to be agile and perfect on every task, project, and initiative that gets forwarded their way. The problem with this mindset is that you will never be perfect, no matter how much of a unicorn you are. Like many concepts in life that are philosophies, when you add in the concept of the “real world”, this philosophy does not work in the way that it’s intended. Generally speaking, philosophies never transfer over; especially, when we talk about the work done by developers.  

Instead of a dreamt of philosophy of absolute agile perfection, what can we replace that with? Well, the efficient and useful concept of problem solving in order to complete a task. Understanding that “perfection” will never be attained, no matter how far you push yourself. Finally, recognizing that you are going to make mistakes along the way and that is okay.

No one ever asked you to be perfect, they just wanted you to do your job to the best of your abilities.

WE’LL DEAL YOU THE WINNING DEV CARD HAND!

We have a problem…

We must completely change the direction of the project that we are going in – stop the presses! The last thing anyone working on a project wants to hear is that we are stopping what we are doing and reworking the project in a new direction. Ugh, what a waste of time, right?!

Whatever the project is that you are working on, I can guarantee you that there is a major aspect to keep in mind – budget. Usually, there are two aspects to consider when it comes to budget: 1. What the project should cost, and 2. The actual cost of the project. Ah, yes, the practical side of the business that many of us tend to forget when we have our blinders on and are working away like mad, only to find out that changes are coming…

Do you know that more than 50% of software costs go to project rework and repairs, and not the original project cost itself? Yes, that’s baffling information to digest when reading it out loud (or inside) to yourself. A large portion of the rework comes after the initial launch of the project when corrections and implementations come up during the testing period. How can we fix these extra project costs?

Fortunately for you, there are a few ways to remove reworking time and extra costs. Integrate your test design into the requirement/overall process of the project, apply model-based technology to functional testing and specification timelines, and invest in test-driven development processes (i.e. incremental development). These methods will not only save on the costs and resources involved but your own sanity if you are lucky!

(Copy: Jordan Rinaldi / illustration: Carlos Ponce)

WANT TO AVOID REWORK IN SOFTWARE DEV? HERE’S HOW!

No need to grow a horn on your forehead.

These days, there’s increasing pressure for developers and coders to be able to define themselves as “full-stack”, most of the time referred to as unicorns (growing a horn in your forehead is the hardest part, though). This means essentially that they need to have a “unique set of skills”, though the skills are a little less cool than in Liam Neeson’s Taken.

Think instead in terms of HTML, CSS, JS, PHP, MySQL, Apache, Linux… A full-stack developer is practically a one-man/one-woman army when it comes to creating web apps. Can’t do all those things? Then you may have trouble getting an interview with a top employer.

Facebook, for instance, will only (allegedly) hire developers they classify as “full stack” and many others are following suit. Unfortunately, the list of skills involved in developing web apps only continues to grow.

Today there’s some debate as to whether it’s even possible to be a full stack developer. Even those who “believe” in the full-stack developer will debate the best definition for what that means. And recruiters at tech companies usually have a hard time interviewing them, since, you know, some pixie dust is required to do the trick. If you were asked what the term actually encompasses and how you might achieve that lofty, mythical status, what would you respond?

LET US HELP YOU BUILD YOUR TEAM OF UNICORNS!

Ahhh, the infamous Great Resignation!

Why are so many people quitting their jobs, some even with no new job lined up? Companies from all kinds of verticals – although this is a big thing at tech companies – are offering higher compensation, better benefits, flexible schedules, work from home opportunities and yet workers continue to leave. The dilemma lies in the lack of understanding by the employers of what their employees really want. And no, we’re not necessarily talking about bean bags, ping pong tables and truckloads of free beer, but other things like family time, self-management, autonomy, no commuting, no stringent dress codes and useless meetings, not to mention a holistic sense of purpose and belonging. We see monthly, quarterly, and annual surveys conducted by employers to monitor engagement, but none of these surveys capture what truly matters to the employees. Most surveys are “leading the witness” to ask questions that will always point to compensation, benefits, flex schedules and other short-term boosts for employees. But who dares to ask the employees, “are you happy at work? How do you feel at work every day? What’s really important for you?”

Happiness may be the most fundamental reason why employees leave. Happiness at work and in life has two key components, purpose and contentment. Do employees feel like their job has a purpose worth fulfilling, and are they content? You can’t measure happiness with periodic pulse surveys. You need them to self-reflect and record their happiness either positive or negative every single day.

We are beginning to see trends as people keep tabs on their mood daily. Imagine how these trends will evolve when we look at the happiness scores and mood trends for entire organizations! That is where the rubber will meet the road in our understanding of work culture and mental health. And as long as folks can work in their undies and slippers while bottle feeding toddlers… we’re good.

LET US HELP YOU BUILD A HAPPY DEV TEAM!