-1

archive,tag,tag-tech-debt,tag-164,stockholm-core-2.4.4,select-child-theme-ver-1.1.3,select-theme-ver-9.12,ajax_fade,page_not_loaded,,qode_menu_,wpb-js-composer js-comp-ver-7.9,vc_responsive

tech debt Tag

DALL·E 2023 08 28 10.38.34 matt groening style cartoon drawing of the side view a cheetah sitting at a desk writing software with a giant thick iron chain holding him back digi

August 28, 2023 In Code, Estimation, Process, Productivity, Tech Debt, Uncategorized

Top 10 Software Developer Productivity Killers

If you’ve recently found yourself trapped in a catacomb of chaotic code or entangled in a web of woefully unclear requirements, fret not! Bob’s journey through the perilous pitfalls of developer productivity is the adventure you’ve missed. Over the past two weeks, we’ve run a daily series of blog posts about the most prevalent software developer productivity killers we, at Facet Digital, often see in the engineering teams we are hired to assess. Some of these have do to with the technical team and their decisions, and some of them have to do with the business support around them.

Here’s a quick recap:

01	Useless Meetings	Breaking up the Maker’s focus time
02	Open-Plan Offices	Noise and visual distraction disrupt concentration
03	Technical Debt	Short cuts now make innovation take longer later
04	Dead Code	Hours wasted maintaining or searching through garbage
05	Too Many Status Reports	Talking more about work than doing the work
06	Unclear Requirements	Spending too much time guessing at the wrong intent
07	Poor Branching Strategy	Working in too large of chunks and not getting feedback quickly
08	Unrealistic / Arbitrary Deadlines	Demoralizing and stifling creativity
09	Micromanagement	Not letting the brains you hired use their brains to the fullest
10	Poor Documentation	Making the next dev guess and explore without a map

Familiar foes? If these productivity antagonists have been causing chaos in your dev-life, contact us for some superhero assistance.

🙋‍♀️ Encountered another productivity villain we missed? Share in the comments which dastardly devils resonate with you and any others lurking in the shadows!

August 23, 2023 In Code, Estimation, Process, Productivity, Tech Debt

The Dangers of Unrealistic Deadlines

Software Developer Productivity Killer #8: Arbitrary Deadlines

Ahoy, fellow digital voyagers! As the winds of our virtual journey continue to twist and turn, they bring forth tales of the perilous “unrealistic deadlines.” Just as the sirens of lore ensnared unwitting sailors with their deceptive songs, these ill-conceived timeframes can draw development teams into treacherous waters. Our ever-relatable friend Bob has been through this storm a few times and, suffice it to say, it wasn’t pretty.

😈 Bob’s Date with the Deadline Demon

It was a typical Monday when Bob was slapped with a seemingly simple mandate: “Get this done by Friday, Bob. It shouldn’t be that tough, right?” Attempting to reason and provide a more realistic deadline fell on deaf ears, overshadowed by the constant hum of “we really need it by then.” Bob found himself working late nights, compromising on code quality, and hastily rushing through reviews. All this effort, only to later find out that the deadline had no concrete reason behind it.

🕑 The Deadline Debacle

The Motivation Meltdown: Picture urging a crew to row faster, but there’s no looming storm or sight of a treasure-filled island. It’s like coaxing someone to row harder when there’s no land in sight.
Haste Makes… Technical Debt: Speeding through tasks to meet a deadline often results in cutting corners. Soon, your immaculate ship (or codebase) is leaking all over.
Burnout’s Blazing Trail: Constant urgency isn’t sustainable. It’s a surefire route to burnout, stifling creativity, and waning enthusiasm for future projects.
The Quality Question: Rushing invariably means skimping on important steps. Code reviews get hurried, testing is superficial, and the final output? A shaky product that’s far from shipshape.
Borrowing from Tomorrow: Overworking to meet today’s deadline is akin to taking a loan on future productivity. Just as sacrificing sleep one night necessitates extra rest later, pushing too hard today inevitably slows you down in the subsequent days. What you gain in the short-term, you often pay back with interest in decreased efficiency and stamina.

🗺️ Charting a Better Course

Estimation Exploration: Developers should play a key role in setting the timeline. Incorporate methods like T-shirt sizing, Fibonacci series, or planning poker to allow developers to weigh in on the effort required.
Estimates ≠ Deadlines: This distinction is crucial. Developers often dread giving estimates, primarily because they’re aware that those numbers might be taken as hard deadlines. Remember, estimates are educated guesses—sometimes you might overestimate, other times underestimate. They don’t account for all the unforeseeable challenges that could arise.
The Journey, Not Just the Destination: Concentrate on consistently delivering value rather than sprinting to a hastily determined finish line. A well-considered journey ensures both quality and team morale remain high.
Mutual Respect and Trust: Recognize that developers are experts in their domain. When they suggest adjusting the timeline, it’s based on experience and knowledge. It’s not just about buying time; it’s about delivering excellence.

💡 Conclusion

Deadlines, when used judiciously and not oppressively, can be effective. When they are pulled from the ether without basis, however, they wreak havoc. Bob has learned to voice his concerns, advocate for logical timelines, and champion for developer-centered estimations.

As our digital odyssey with Bob unfolds—from branching strategies to inadequate requirements —a consistent theme emerges: A content and well-managed team is the fastest route to successful project completion.

Could You Use a Guiding Hand in Navigating the Waters of Deadlines and Estimations? Are you inadvertently hampering your developers with unrealistic expectations? Our firm can guide you in establishing an effective, developer-centric estimation process. Such an approach not only uplifts morale but also boosts overall productivity. Get in touch with us to ensure your journey in the realm of software development is smooth and efficient. Set sail for success with us as your trusted compass!

August 16, 2023 In Code, Process, Productivity, Tech Debt

Technical Debt: When Ignorance Isn’t Bliss

Software Developer Productivity Killer #3: Tech Debt

Ahoy, dear reader! We’ve spoken about ‘useless meetings‘ and the perils of the ‘open-plan office‘. Today, we embark on a voyage beneath the surface to unveil a silent killer, lurking in the deep, dark abyss of codebases everywhere – Technical Debt.

For the uninitiated, technical debt might sound like the overdraft fees on a credit card statement, but trust us, the costs can be even more perilous if not managed. But fret not! We’re here to unveil the mysteries of this productivity assassin and guide you to safer shores.

🌊 Understanding The Iceberg That’s Technical Debt

The Tip of the Iceberg: On the surface, everything seems fine. Your software is running. New features get deployed. But underneath lies layers of rushed code, shortcuts, and bandaids that, much like the bulk of an iceberg, remain invisible to the untrained eye.
The Silent Accumulator: Technical debt accrues silently. It’s the byproduct of fast decisions, expedited features, and temporary fixes. While a quick workaround might speed things up today, it will slow everything down tomorrow.
Feature Slowdown: Ever wondered why the latest ‘simple feature’ took thrice as long as you hoped? Beneath the water, your dev team might be battling tentacles of ancient code and patchwork solutions. The deeper they swim, the harder it gets.

📉 The Business Cost of Ignoring Technical Debt

Lost Time and Money: The longer technical debt remains, the more expensive (in both time and resources) it becomes to address. Your devs aren’t magicians; they’re navigators trying to avoid crashing into that looming iceberg. Code reviews take longer, more bugs appear and are harder to fix the right way, and overall code quality suffers.
Reduced Morale: A team constantly battling the deep-sea monsters of messy code can quickly lose enthusiasm. And a demotivated team isn’t a productive one.
Innovation Stagnation: With so much energy going into managing existing chaos, there’s little left for innovation and growth. Do you really want to be stuck sailing in circles?

🚢 Navigating Away from The Iceberg

Post-Mortem’s Critical Role: Taking shortcuts during an emergency or to expedite a release can be an acceptable strategy. But it’s like borrowing against tomorrow – you must repay it, preferably sooner rather than later. After such incidents or rapid releases, conduct a post-mortem. Assess and catalog the quick fixes and patches applied. This isn’t about finger-pointing but about understanding the new debt that’s been taken on. Prioritize paying down the heaviest debt even before diving back into your feature roadmap. The short-term gain is only beneficial if you’re strategic about the long-term repercussions.
Track Technical Debt: Just as businesses track financial obligations, technical debt should be recorded and monitored. Consider tools or platforms designed for this. If you can’t measure it, you can’t manage it.
Allocate Regular Paydown Time: Embrace that a portion of your dev team’s time needs to be dedicated to addressing and reducing technical debt. Think of it as regular maintenance on a ship to ensure smooth sailing.
Educate and Involve Everyone: Tech debt isn’t just a ‘dev issue’. Business stakeholders should be educated on its implications. When everyone’s on board (pun intended), it’s easier to navigate treacherous waters.

💡 In Conclusion

Technical debt, if left unchecked, becomes that giant iceberg threatening to sink your ship. But with intentionality, regular check-ins, and an understanding that it’s as real as any financial debt, you can sail through smoother waters. After all, in business, as in sailing, forewarned is forearmed.

And if you’re already feeling a bit seasick from tech debt, consider chatting with an expert (hint: us) to help navigate. Why DIY when you have a seasoned captain just a call away?

✋ Keen on avoiding more developer productivity pitfalls? Dive into our discussions on ‘useless meetings’ and the ‘open-plan office’. Stay tuned; we have more voyages planned in this series to guide you through the turbulent seas of productivity.