# hierarchy

Published articles for hierarchy.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## What Special Forces Can Teach Us About High-Impact Engineering Teams

DevFeed: [What Special Forces Can Teach Us About High-Impact Engineering Teams](<https://devfeed.tech/articles/what-special-forces-can-teach-us-about-high-impact-engineering-teams-38737.md>)

Original publisher: [Read original article](<https://codecapsule.com/2025/03/04/what-special-forces-can-teach-us-about-high-impact-engineering-teams/>)

Author: Emmanuel Goossaert

Published: 2025-03-04T21:59:28Z

Content type: opinion

Language: en

Sources: [Code Capsule](<https://devfeed.tech/sources/code-capsule.md>)

Topics: [cos](<https://devfeed.tech/topics/cos.md>)

Tags: [engineering](<https://devfeed.tech/tags/engineering.md>), [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [leadership-and-management](<https://devfeed.tech/tags/leadership-and-management.md>), [leadership-and-management-leadership-management](<https://devfeed.tech/tags/leadership-and-management-leadership-management.md>), [management](<https://devfeed.tech/tags/management.md>), [organizational](<https://devfeed.tech/tags/organizational.md>), [team](<https://devfeed.tech/tags/team.md>), [tech](<https://devfeed.tech/tags/tech.md>)

### AI overview

The article compares the French Special Forces' direct reporting structure with high-performing engineering teams. It argues that reducing hierarchy can speed decisions, preserve objectives, and improve feedback, drawing partly on the author's experience leading a large web ecommerce engineering organization at adidas.

### Source excerpt

There's a reason Special Forces bypass traditional military hierarchy, and it's the same reason high-performing tech teams should too. Being French and having an interest in organizational structures and cultures, it was logical that I ended up learning about how the French military is set up. I spent time learning... The post What Special Forces Can Teach Us About High-Impact Engineering Teams first appeared on Code Capsule.

## Organizational Tension Processing - Driving Change in Self-Organizing Companies

DevFeed: [Organizational Tension Processing - Driving Change in Self-Organizing Companies](<https://devfeed.tech/articles/organizational-tension-processing-driving-change-in-self-organizing-companies-39933.md>)

Original publisher: [Read original article](<https://mende.io/blog/organizational-tension-processing-driving-change-in-self-organizing-companies/>)

Author: tobi@techunicorn.builders (Tobias Mende)

Published: 2024-10-05T05:00:00Z

Content type: opinion

Language: en

Sources: [Tobias Mende](<https://devfeed.tech/sources/tobias-mende.md>)

Topics: [structure](<https://devfeed.tech/topics/structure.md>), [Processes](<https://devfeed.tech/topics/processes.md>)

Tags: [business-culture-employee-happiness-high-purpose-environments-leadership-developer-productivity](<https://devfeed.tech/tags/business-culture-employee-happiness-high-purpose-environments-leadership-developer-productivity.md>), [change](<https://devfeed.tech/tags/change.md>), [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [organizational](<https://devfeed.tech/tags/organizational.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [processes](<https://devfeed.tech/tags/processes.md>), [product-development](<https://devfeed.tech/tags/product-development.md>), [self-organizing](<https://devfeed.tech/tags/self-organizing.md>), [structure](<https://devfeed.tech/tags/structure.md>)

### AI overview

The article explains that self-organizing companies are not structureless or chaotic despite having no traditional people hierarchy. It discusses using a tension-based proposal process to adjust structures, processes, and goals while enabling employees to surface and implement ideas and support faster organizational change.

### Source excerpt

Organizational Tension Processing - Driving Change in Self-Organizing Companies Newcomers to self-organization often mistake the lack of a people-hierarchy for complete chaos. The term "flat" can be misleading, as it suggests that self-organizing companies lack any structure. In reality, this is far from the case.

## In-memory dictionary

DevFeed: [In-memory dictionary](<https://devfeed.tech/articles/in-memory-dictionary-39362.md>)

Original publisher: [Read original article](<https://kt.academy/article/pmem-in-memory-dictionary>)

Published: 2022-05-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [Kt. Academy](<https://devfeed.tech/sources/kt-academy.md>)

Topics: [Data structures](<https://devfeed.tech/topics/data-structures.md>), [structure](<https://devfeed.tech/topics/structure.md>)

Tags: [complexity](<https://devfeed.tech/tags/complexity.md>), [data-structure](<https://devfeed.tech/tags/data-structure.md>), [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [node](<https://devfeed.tech/tags/node.md>), [search](<https://devfeed.tech/tags/search.md>), [workshop-learning-programming](<https://devfeed.tech/tags/workshop-learning-programming.md>)

### AI overview

This tutorial begins by building an in-memory dictionary as a step toward understanding persistent memory. It compares data-structure options and uses a Trie to support adding words, searching for words, and finding words with a given prefix, while introducing trees and Trie nodes.

### Source excerpt

Let's begin our journey to understand persistent memory by building an in-memory dictionary.

## Effective Kotlin Item 36: Prefer composition over inheritance

DevFeed: [Effective Kotlin Item 36: Prefer composition over inheritance](<https://devfeed.tech/articles/effective-kotlin-item-36-prefer-composition-over-inheritance-39274.md>)

Original publisher: [Read original article](<https://kt.academy/article/ek-composition>)

Published: 2021-04-25T00:00:00Z

Content type: article

Language: en

Sources: [Kt. Academy](<https://devfeed.tech/sources/kt-academy.md>)

Topics: [Inheritance](<https://devfeed.tech/topics/inheritance.md>), [Object-oriented programming (OOP)](<https://devfeed.tech/topics/oop.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [reuse](<https://devfeed.tech/topics/reuse.md>), [superclass](<https://devfeed.tech/topics/superclass.md>)

Tags: [approach](<https://devfeed.tech/tags/approach.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [inheritance](<https://devfeed.tech/tags/inheritance.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [object](<https://devfeed.tech/tags/object.md>), [oop](<https://devfeed.tech/tags/oop.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [superclass](<https://devfeed.tech/tags/superclass.md>), [workshop-learning-programming](<https://devfeed.tech/tags/workshop-learning-programming.md>)

### AI overview

The article argues that inheritance should primarily model a clear "is a" relationship and can be problematic when used mainly for code extraction or reuse. It presents class composition as a safer and more explicit alternative, while acknowledging that composition requires additional code.

### Source excerpt

Years of OOP made us overuse inheritance. Instead, we should more often use a composition that is safer and more explicit. More often, but not always...

## On the Computational Complexity of MapReduce

DevFeed: [On the Computational Complexity of MapReduce](<https://devfeed.tech/articles/on-the-computational-complexity-of-mapreduce-40368.md>)

Original publisher: [Read original article](<https://www.jeremykun.com/2014/10/05/on-the-computational-complexity-of-mapreduce/>)

Published: 2014-10-05T09:00:30Z

Content type: article

Language: en

Sources: [Jeremy Kun](<https://devfeed.tech/sources/jeremy-kun.md>)

Topics: [computational complexity](<https://devfeed.tech/topics/computational-complexity.md>), [Algorithms, Complexity](<https://devfeed.tech/topics/algorithms-complexity.md>), [Graphs](<https://devfeed.tech/topics/graphs.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [circuit-complexity](<https://devfeed.tech/tags/circuit-complexity.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [computational-complexity](<https://devfeed.tech/tags/computational-complexity.md>), [distributed-computing](<https://devfeed.tech/tags/distributed-computing.md>), [exponential-time-hypothesis](<https://devfeed.tech/tags/exponential-time-hypothesis.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [karloff](<https://devfeed.tech/tags/karloff.md>), [l-vs-p](<https://devfeed.tech/tags/l-vs-p.md>), [map-reduce](<https://devfeed.tech/tags/map-reduce.md>), [padding](<https://devfeed.tech/tags/padding.md>), [research](<https://devfeed.tech/tags/research.md>)

### AI overview

The article presents an accessible discussion of research analyzing the computational complexity of a theoretical model of the MapReduce framework. It describes open questions about MapReduce's power, including whether constant-round algorithms can determine graph connectivity and how the model relates to complexity classes such as P and L.

### Source excerpt

I recently wrapped up a fun paper with my coauthors Ben Fish, Adam Lelkes, Lev Reyzin, and Gyorgy Turan in which we analyzed the computational complexity of a model of the popular MapReduce framework. Check out the preprint on the arXiv. Update: this paper is now published in the proceedings of DISC2015. As usual I'll give a less formal discussion of the research here, and because the paper is a bit more technically involved than my previous work I'll be omitting some of the more pedantic details.

## Liskov Substitution Principle

DevFeed: [Liskov Substitution Principle](<https://devfeed.tech/articles/liskov-substitution-principle-40710.md>)

Original publisher: [Read original article](<https://radek.io/posts/liskov-substitution-principle/>)

Published: 2011-08-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [Radek Pazdera](<https://devfeed.tech/sources/radek-pazdera.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [coding](<https://devfeed.tech/topics/coding.md>), [subclass](<https://devfeed.tech/topics/subclass.md>), [subtype](<https://devfeed.tech/topics/subtype.md>)

Tags: [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [object-oriented](<https://devfeed.tech/tags/object-oriented.md>), [software-design](<https://devfeed.tech/tags/software-design.md>), [solid](<https://devfeed.tech/tags/solid.md>), [subclass](<https://devfeed.tech/tags/subclass.md>), [subtype](<https://devfeed.tech/tags/subtype.md>)

### AI overview

This article explains the Liskov Substitution Principle, the L in SOLID object-oriented design. It presents definitions from Barbara Liskov and Jeannette Wing, a formulation by Robert C. Martin, and a Square-Rectangle hierarchy example showing how subtype behavior can violate substitutability.

### Source excerpt

SOLID Object-Oriented Design