I don’t think that a single “perfect” organizational structure exists. Every company has different needs and therefore has different talent requirements. Some team structures are flat, some are deep. No matter how you set up your technical team, if there are processes for shared ownership of your product, you can succeed.
However, there is one position that every company/team should prioritize: senior engineers.
No matter your industry, size, or tech stack, you need senior engineering leadership to guide your software products and internal processes. Without this senior leadership, unfortunate things can happen, some more damaging than others.
Here are some of the most common occurrences that can happen when you lack senior engineering leadership. …
When something as disruptive as a pandemic happens in a year, buying and consumer trends will shift, many permanently. Between lack of confidence in the markets and a record-high unemployment rate, people have held their money closer to their chests.
This is not to suggest we can’t still earn their business, but perhaps that we should work differently for it.
B2B vs. B2C: While companies and individuals spend their money on wildly different things, trends typically run parallel to one another. …
Technology companies and other organizations can face a number of realities throughout their lifespans.
Unfortunately, COVID has unleashed each of these realities at once. And while they’re widely out of your control, there are some things you can do to improve your position in the market. These things typically fall under one of these basic strategies.
There are many opportunities to increase revenue during a time of economic downturn, however, they all have their own set of challenges.
Reducing costs, on the other hand, is a bit more straightforward. …
Microservices have been everywhere for the past few years. YouTube is using them. Facebook is using them.
But should you use them?
Spoiler alert: Microservices probably isn’t the best solution for your cloud architecture. In this article, we’ll explain why.
Let’s start with the basics.
The two most popular paradigms are monolithic architectures or microservice architectures.
For years, a monolithic architecture has been a dependable way to compose systems. These systems have multiple components all under the same service. They leverage internal libraries and don’t require much network activity.
The other, newer, sexier option is microservices. Rather than a single service, microservices have many components, each with its own specific process. Each component has distinct lines of responsibility and is separated from one another. …
Since the mainframe computer in the 1970s, computing power has grown exponentially, doubling processing power while halving costs every year.
While server farms and data warehouses were once thought to be the final solution for speed and capacity, the pendulum is swinging back to an old-school-esque network of devices.
If you look at the evolution of computing, it’s easy to understand how cloud computing swung the pendulum from powerful devices to powerful networks. Entire business models have been built on the concept of offsite storage and fast networks e.g., …
Organizations today have larger business expenses than ever before. Security, data, tools, hardware, and development costs have all ballooned due to consumer preferences, regulations, and external risks.
It’s not hard to understand why a business would cut some of these costs by outsourcing development to an offshore company.
However, there are unseen risks associated with offshore companies that have their own set of expenses, so there are many things to consider.
Now a disclaimer: I am CTO at an onshore software development company, so naturally, I believe that onshore development almost always gives you a better product.
That being said, for some companies, it absolutely makes sense to hire an offshore development company. If that’s you, I understand (I have even been known to recommend offshore development when it makes sense). But it’s important to know what kind of tradeoffs you’ll be making in your offshore partnership. …
This past month, some of my engineering colleagues at a different company shared a perplexing experience.
They sat down at their remote setup, fired up their devices, and were met with an internal blockade. Their IT department had accidentally blocked the connection between their VPN and Amazon Web Services, rendering the team completely useless.
Rather than waiting around for an undisclosed amount of time, our friends took that snafu as an FU.
They took the day off.
This simple mistake likely cost the company tens of thousands of dollars in lost productivity.
Every time something like this (read: completely avoidable) happens, the leader of the IT team is sabotaging their entire company. …
Despite its precipitous rise in popularity, Kubernetes (also known as k8s) is a notoriously difficult concept to describe in non-technical terms. Any discussion of it relies on some knowledge of containerization, which itself is an extension of virtualization.
That’s a lot of multi-syllabic words to introduce at once, so let’s break all of that down.
According to VMware, a leading provider of virtualization technology, virtualization is “the process of creating a software-based, or virtual, representation of something, such as virtual applications, servers, storage, and networks.”
Virtualization, within the context of software engineering, refers to the use of virtual machines (VMs), which are software representations of computer hardware, firmware, operating systems, and software. …
You’re tasked with completing a UX/UI research project. Whether for a cloud-based application, communications website, or other interfaces, you need to sit down in a room and talk to real users.
Real users can provide unique insights into what motivates them and how they interact with products and brands. This insight, in turn, can fuel your UX/UI strategy and leave you with an evidence-based digital product plan.
Coming up with engaging questions can be a challenge, which is why we’ve taken the following questions directly from our team’s UX/UI handbook. We hope these questions shape your UX research and presentation.
Digital transformation has been around just long enough that everyone claims to be doing it. Startups, Fortune 500s, SMBs, and digital transformation consultants can all tell you about its vast benefits.
But what does digital transformation really mean? As a technology leader, how do you effectively wrap your head around it? And then how do you strategize, prioritize, and implement it?
The truth is that digital transformation is a complex and debated subject. It encompasses a lot and means different things to different people.
Fortunately, the basics of digital transformation are simple enough to understand, and we’ve taken our best shot at it below. …