Tag: Technical Team

Last update on

How to Assemble a High-Performing Team

Having spent my last 11 years growing an agency, one of the factors we squeeze and optimize most frequently is performance. Agencies are a weird beast that gets scrutinized all the time. Why? Enterprises are large and monolith enough to employ an endless set of processes going through multiple layers across a number of departments across the organization, taking forever to execute Product businesses don't face deadlines in the same way an agency does. Roadmaps are more easy-going, distractions are fewer, people work on a single product at a time (continuously) Support/maintenance firms get interrupted frequently, but established processes in… Continue Reading
Last update on

How to Incorporate Technology to Solve Business Problems

A couple of years ago, I gathered the 38 top business challenges across all industries. They fall within several main segments: Strategy Marketing Recruitment Management Sales Technology Legal While tech is self-explanatory (and notably solved with technology itself), software and hardware solutions can contribute to easier organization in the long run. Traditional methods for organization often rely on manual processes, paper trails, and human memory, leading to errors and inefficiencies. Technology solves this by: Automation: Repetitive tasks become automatic, freeing up employee time. Think scheduling, emails, reports. Data Management: Software excels at organizing data, providing easy access anytime, anywhere. No… Continue Reading
Last update on

How to Establish and Solidify the Technical Leadership in Your Company

I receive a good chunk of emails and messages from people in my network asking for general technical advice (infrastructure, architecture, picking the right platform or vendor, etc.) And many of them openly disclose they have spoken with 5–10 people and brainstormed over the different answers they get. Asking for a hundred different opinions may get confusing, though. I wouldn’t advise you to ask an open-ended question on Quora, Stack Overflow, social media, email blasts, personal networks, friends, and recommendations. Prepare that into multiple phases – half a dozen generic, high-end answers, sift through them, narrow down your options, iterate… Continue Reading
Last update on

What Does Technical Debt Mean?

What makes a $2,000 development project different from a $40K one? Code quality. The $2,000 project incurs the so-called "technical debt". A messy, spaghetti-like codebase is 5x, 10x, 20x more complicated to maintain, which skyrockets the maintenance costs over time. Technical debt is a well-known phenomenon in tech. But due to the price cuts, it happens all the time. The chart below shows the result of a survey conducted by CodeAhoy among software developers. Accordingly, the majority of the respondents are swamped with projects that have technical debt. [Tweet "There is a fine balance between providing a usable piece of… Continue Reading