Skip to main content

Company vs company

In the English vocabulary, the word 'company' has 2 meanings:

Company: an organization that sells goods or services in order to make money

And

Company: the fact of being with a person or people, or the person or people you are with

I think it is no coincidence that the same word is used for both explanations.

Origin

The word "company" traces its origins back to the Latin term "com-" meaning "together with" and "panis" meaning "bread". In its earliest usage, "company" referred to a group of people who shared meals together, highlighting the communal aspect of coming together around a common table. This initial meaning laid the foundation for the word's dual evolution, branching into both social and business contexts.

Social Company:

In its more informal sense, "company" refers to a gathering of individuals for social interaction or mutual enjoyment. The shared origin with the concept of breaking bread emphasizes the communal nature of spending time together.

Business Company:

The transition from shared meals to shared endeavors led to the development of the second meaning of "company." Over time, the term expanded to encompass organized groups of people working together toward a common goal, often in a structured business setting. This evolution reflects the historical shift from agrarian societies, where shared meals were central, to more complex economic structures requiring collaboration for mutual success.

Why I think this is still important today?

More that just a shared etymological root, I think that it emphasizes an important aspect of why your workplace is more than just the place where you earn your bread. Instead, the workplace becomes a living embodiment of the communal spirit inherent in the word's origin. In a professional setting, "company" extends beyond tasks and deadlines, encapsulating the shared experiences, goals, and achievements of a group of individuals working together.

Your workplace is more than a location where you fulfill professional responsibilities; it is a dynamic environment where meaningful connections are forged. The colleagues with whom you collaborate daily become more than just coworkers—they become a part of your professional "company." Shared challenges, triumphs, and the day-to-day interactions contribute to a sense of camaraderie, transforming the workplace into a space where relationships are nurtured, and a collective identity is formed.

"Company" takes on a profound meaning, highlighting the significance of connections and shared goals in fostering a fulfilling professional environment. So, the next time you step into your workplace, consider it not just as a location for earning a wage but as a vibrant community where your contributions and relationships form an integral part of a collective journey.

Image generated by Microsoft Bing Image Creator.


Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...