# Michael Dubakov

Riding the edge of cHa0S. Founder: Fibery (2017), Targetprocess (2004).

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

## No-code Revolution. Why Now?

DevFeed: [No-code Revolution. Why Now?](<https://devfeed.tech/articles/no-code-revolution-why-now-30378.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/no-code-revolution-why-now>)

Published: 2019-09-04T09:12:28Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [No-code](<https://devfeed.tech/topics/no-code.md>), [Low code](<https://devfeed.tech/topics/low-code.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [2015](<https://devfeed.tech/tags/2015.md>), [2017](<https://devfeed.tech/tags/2017.md>), [2020](<https://devfeed.tech/tags/2020.md>), [3](<https://devfeed.tech/tags/3.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [airtable](<https://devfeed.tech/tags/airtable.md>), [all](<https://devfeed.tech/tags/all.md>), [altair](<https://devfeed.tech/tags/altair.md>), [app](<https://devfeed.tech/tags/app.md>), [applications](<https://devfeed.tech/tags/applications.md>), [apps](<https://devfeed.tech/tags/apps.md>), [assemble](<https://devfeed.tech/tags/assemble.md>), [atari](<https://devfeed.tech/tags/atari.md>), [attack](<https://devfeed.tech/tags/attack.md>), [code](<https://devfeed.tech/tags/code.md>), [customers](<https://devfeed.tech/tags/customers.md>), [fast](<https://devfeed.tech/tags/fast.md>), [no-code](<https://devfeed.tech/tags/no-code.md>), [software](<https://devfeed.tech/tags/software.md>), [valuation](<https://devfeed.tech/tags/valuation.md>)

### AI overview

The article traces no-code's delayed rise through four overlapping software waves. In 1960-1980, users were often programmers who could build what they needed; in 1980-2000, personal tools such as spreadsheets and HyperCard gained traction, but often still required programming skills. The web then enabled collaborative software, while its early limitations made it difficult to recreate powerful desktop tools, leaving no-code technology behind. The author argues that web development has since matured enough to support complex applications, and that users are ready for tools that shorten feedback loops. Examples include marketers updating websites, consultants automating processes and small businesses building apps. The author predicts further disruption across industries, while noting that today's no-code vendors may not dominate the coming wave.

### Source excerpt

It seems no-code software is booming. Fast adoption, huge rounds, insane valuation 🦄, happy customers. Why now? Why not 20 years ago? Why...

## Features composability

DevFeed: [Features composability](<https://devfeed.tech/articles/features-composability-30328.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/features-composability>)

Published: 2019-03-19T14:27:48Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

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

Tags: [api](<https://devfeed.tech/tags/api.md>), [board](<https://devfeed.tech/tags/board.md>), [component](<https://devfeed.tech/tags/component.md>), [composability](<https://devfeed.tech/tags/composability.md>), [copy](<https://devfeed.tech/tags/copy.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [features](<https://devfeed.tech/tags/features.md>), [filter](<https://devfeed.tech/tags/filter.md>), [flexibility](<https://devfeed.tech/tags/flexibility.md>), [interface](<https://devfeed.tech/tags/interface.md>), [internals](<https://devfeed.tech/tags/internals.md>), [list](<https://devfeed.tech/tags/list.md>), [product](<https://devfeed.tech/tags/product.md>), [project](<https://devfeed.tech/tags/project.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [services](<https://devfeed.tech/tags/services.md>), [sort](<https://devfeed.tech/tags/sort.md>), [system](<https://devfeed.tech/tags/system.md>), [tasks](<https://devfeed.tech/tags/tasks.md>)

### AI overview

The text argues that features should depend on other components' public interfaces, not their internal details. In its ToDo app examples, coupling a Filter to List internals or Copy to Task View makes those features difficult to reuse in Board View or Project. It recommends treating features as independent components and giving complex components extension points, so a component can act as a skeleton filled by smaller features. The author says this improves reuse and software evolution, while tight coupling makes changes increasingly painful.

### Source excerpt

When we add features to a product, we rarely think about composability. We assume that it is OK for any feature to rely on internal...

## Make your own tools.

DevFeed: [Make your own tools.](<https://devfeed.tech/articles/make-your-own-tools-30365.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/make-your-own-tools>)

Published: 2019-02-01T15:02:56Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [dogfooding](<https://devfeed.tech/topics/dogfooding.md>), [React](<https://devfeed.tech/topics/react.md>)

Tags: [airbnb](<https://devfeed.tech/tags/airbnb.md>), [alibaba](<https://devfeed.tech/tags/alibaba.md>), [angular](<https://devfeed.tech/tags/angular.md>), [apple](<https://devfeed.tech/tags/apple.md>), [aws](<https://devfeed.tech/tags/aws.md>), [business-value](<https://devfeed.tech/tags/business-value.md>), [clojure](<https://devfeed.tech/tags/clojure.md>), [docker](<https://devfeed.tech/tags/docker.md>), [facebook](<https://devfeed.tech/tags/facebook.md>), [fun](<https://devfeed.tech/tags/fun.md>), [git](<https://devfeed.tech/tags/git.md>), [github](<https://devfeed.tech/tags/github.md>), [ios](<https://devfeed.tech/tags/ios.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [javascript-frameworks](<https://devfeed.tech/tags/javascript-frameworks.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The article argues that making some tools for your own use can help a company find novel solutions: firsthand use makes the problem explicit, guides feature choices, and may reveal a product others need. It also says custom tools can waste time and money, and does not advocate building everything. Examples of companies creating frameworks illustrate how tools can spread and be evaluated by others.

### Source excerpt

Not Invented Here is a popular mantra in many companies. Majority thinks that you should focus on business value, and all other things are...

## Strategy-Implementation Mismatch

DevFeed: [Strategy-Implementation Mismatch](<https://devfeed.tech/articles/strategy-implementation-mismatch-30415.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/strategy-implementation-mismatch>)

Published: 2018-12-14T07:24:14Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [jira](<https://devfeed.tech/topics/jira.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Agile](<https://devfeed.tech/topics/agile.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [development](<https://devfeed.tech/tags/development.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [jira](<https://devfeed.tech/tags/jira.md>), [project-management](<https://devfeed.tech/tags/project-management.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

The article argues that JIRA's disconnect between tickets and project vision reflects a broader strategy-implementation mismatch in processes, not a problem unique to JIRA. It says Extreme Programming emphasizes technical work, SAFe attempts to connect levels but is often ignored by developers, and OKRs organize objectives across teams but relate poorly to day-to-day execution. GIST is presented as combining scientific strategy decomposition with a better connection to execution, though the author says no software tools support it. The author contrasts strategy-planning tools such as Aha! and ProductBoard with work trackers such as JIRA, Asana, and Trello, arguing that integrations preserve the gap. Separate documentation tools such as Confluence can also leave vision and work disconnected. The proposed direction is to address the mismatch methodologically, then bring strategy, documents, and work together in one tool.

### Source excerpt

JIRA is easy to hate. The latest article trashes JIRA and calls it an anti-pattern for software development. The main problem is work...

## The Next Wave of Work Management Software

DevFeed: [The Next Wave of Work Management Software](<https://devfeed.tech/articles/the-next-wave-of-work-management-software-30425.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/the-next-wave-of-work-management-software>)

Published: 2018-12-03T11:21:00Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Software](<https://devfeed.tech/topics/software.md>), [App](<https://devfeed.tech/topics/app.md>), [Database](<https://devfeed.tech/topics/database.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [database](<https://devfeed.tech/tags/database.md>), [software](<https://devfeed.tech/tags/software.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [work-management](<https://devfeed.tech/tags/work-management.md>)

### AI overview

An opinion article argues that a new wave of work management software is emerging, highlighting Airtable, Zenkit, Notion, and Coda. It identifies product flexibility, domain generalization, automation, and user interface as drivers of this market shift, then examines Airtable as an example.

### Source excerpt

Work management software is boring. Innovations are rare and you may think that no cool new vendors appeared in the last 5 years. Indeed...

## Post-agile process agnosticism

DevFeed: [Post-agile process agnosticism](<https://devfeed.tech/articles/post-agile-process-agnosticism-30392.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/post-agile-process-agnosticism>)

Published: 2018-10-25T09:27:38Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Software Process](<https://devfeed.tech/topics/software-process.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [agile-development](<https://devfeed.tech/tags/agile-development.md>), [control](<https://devfeed.tech/tags/control.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [kanban](<https://devfeed.tech/tags/kanban.md>), [process](<https://devfeed.tech/tags/process.md>)

### AI overview

The author argues that engineers should control and adapt their development process instead of following a branded methodology by default. They describe "Fake Agile" as organizations adopting visible practices such as stand-ups and sprints while retaining fixed assignments, substantial design documents, and spotty unit testing. The proposed response is process agnosticism: programmers should care about process and seek authority to change it, using systems thinking, evidence, and collaboration. Managers should support teams through education and mentoring. Development tools should be easy to adapt to changing practices; the author says process-specific tools can make switching approaches costly, citing Leankit for Kanban and AgileCraft for SAFe, and criticizes VersionOne as ineffective for any process. The text advocates flexible tooling, including support for Waterfall where a team considers it suitable.

### Source excerpt

with Rick and Morty!

## Every Feature Is Considered Harmful

DevFeed: [Every Feature Is Considered Harmful](<https://devfeed.tech/articles/every-feature-is-considered-harmful-30325.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/every-feature-considered-harmful>)

Published: 2017-12-05T13:26:01Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [feature bloat](<https://devfeed.tech/topics/feature-bloat.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>)

Tags: [addition](<https://devfeed.tech/tags/addition.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [development](<https://devfeed.tech/tags/development.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [domain](<https://devfeed.tech/tags/domain.md>), [feature](<https://devfeed.tech/tags/feature.md>), [features](<https://devfeed.tech/tags/features.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [focus](<https://devfeed.tech/tags/focus.md>), [functional](<https://devfeed.tech/tags/functional.md>), [future](<https://devfeed.tech/tags/future.md>), [growth](<https://devfeed.tech/tags/growth.md>), [hacking](<https://devfeed.tech/tags/hacking.md>), [implement](<https://devfeed.tech/tags/implement.md>), [new-feature](<https://devfeed.tech/tags/new-feature.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

The article argues that each new product feature brings ongoing maintenance and can create functional, UI, quality, technical, documentation, or localization debt, making it difficult to add features without future costs. It suggests that young startups may prioritize growth, while successful products approaching maturity should devote resources to paying down debt; for the author's SaaS B2B context, that point may come after 4-8 years. A focused cleanup period may be warranted after 6-8 years, when technical problems, outdated features, bugs, and performance issues slow development. The author recommends weighing debt whenever adding a feature and says some resources should go toward debt repayment continuously.

### Source excerpt

We tend to believe that every new feature is a good and valuable addition to a product. Quite often, it can be hard to not implement a...

## IO.People Classification

DevFeed: [IO.People Classification](<https://devfeed.tech/articles/io-people-classification-30356.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/io-people-classification/>)

Published: 2016-11-08T15:41:57Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

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

Tags: [all](<https://devfeed.tech/tags/all.md>), [bench](<https://devfeed.tech/tags/bench.md>), [books](<https://devfeed.tech/tags/books.md>), [classification](<https://devfeed.tech/tags/classification.md>), [communication](<https://devfeed.tech/tags/communication.md>), [conferences](<https://devfeed.tech/tags/conferences.md>), [courses](<https://devfeed.tech/tags/courses.md>), [doing](<https://devfeed.tech/tags/doing.md>), [examples](<https://devfeed.tech/tags/examples.md>), [fail](<https://devfeed.tech/tags/fail.md>), [filter](<https://devfeed.tech/tags/filter.md>), [information](<https://devfeed.tech/tags/information.md>), [io](<https://devfeed.tech/tags/io.md>), [lazy](<https://devfeed.tech/tags/lazy.md>), [learn](<https://devfeed.tech/tags/learn.md>), [learning](<https://devfeed.tech/tags/learning.md>), [people](<https://devfeed.tech/tags/people.md>), [qa-engineer](<https://devfeed.tech/tags/qa-engineer.md>), [videos](<https://devfeed.tech/tags/videos.md>), [youtube](<https://devfeed.tech/tags/youtube.md>)

### AI overview

The post groups people by how they turn information into work: some avoid new learning or absorb knowledge without applying it, while others learn through examples, need prompting to produce, focus narrowly on job-related material, or share broad learning with limited hands-on work. It describes a balanced type as combining theory and practice, filtering distractions, and contributing in several ways, while warning that enthusiasm can lead to burnout. Each category is linked to a purported workplace fit, such as middle manager, QA engineer, bench, developer, mentor, or lead. These are the author's informal characterizations, not evidence-based assessments; the supplied excerpt does not include the complete classification.

### Source excerpt

This post is an attempt to create a classification of how people consume information and how it affects their work. Void: No input > No output This person is a master of ignorance. He doesn't read books that contain new knowledge, he doesn't visit conferences, doesn't watch videos, doesn't do online courses. He stops learning right after graduation with a strong belief that he learnt everything he needs (and probably he's right). If he reads something -- it's a fiction. It he watches something -- it's a TV-show or a blockbuster. If he visits YouTube channel -- it's Fail Army. All incoming information validated for a single purpose -- entertain. Validation filter becomes very advanced with time and around forties there is close to zero chance to let new information in. This type of person doesn't do much. His work is usually unchallenging and somewhat repetitive. He likes huge corporations where political games and dark corners of ancient divisions allow to survive and even move up the ladder sometimes. Hot spot: Middle manager. Gut: Some input > Action output Learn almost nothing, but somehow do things quite OK. Has supernatural ability to absorb information from the world via osmotic communication. He learns by doing and hates theoretical discussions. However, he do like examples and can somewhat generalize based on them. Hot spot: Middle QA engineer. Abyss: Input > No output This is a weird personality. He reads about everything and knows quite a lot. Unfortunately, all the knowledge carefully kept inside. He is quite lazy and doesn't like challenging tasks. The information inside puts pressure on his mind. He always unhappy about everything and usually grumpy. Life sucks. Existential crisis is real. Hot spot: Bench. Sponge: Input > .Squeeze > Output Absorbs information like a sponge. In some special mood can be quite productive, but he should be squeezed to shine. Direct orders, gentle pushes, flattery and all other manipulations are acceptable to help Sponge overcom

## Enterprise software vendors have no taste

DevFeed: [Enterprise software vendors have no taste](<https://devfeed.tech/articles/enterprise-software-vendors-have-no-taste-30323.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/enterprise-software-vendors-have-no-taste>)

Published: 2015-03-12T10:14:08Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [Interaction Design](<https://devfeed.tech/topics/interaction-design.md>), [software-development](<https://devfeed.tech/topics/software-development.md>)

Tags: [b2b](<https://devfeed.tech/tags/b2b.md>), [beautiful](<https://devfeed.tech/tags/beautiful.md>), [business](<https://devfeed.tech/tags/business.md>), [craftsmanship](<https://devfeed.tech/tags/craftsmanship.md>), [customer](<https://devfeed.tech/tags/customer.md>), [demo](<https://devfeed.tech/tags/demo.md>), [design](<https://devfeed.tech/tags/design.md>), [details](<https://devfeed.tech/tags/details.md>), [development](<https://devfeed.tech/tags/development.md>), [dna](<https://devfeed.tech/tags/dna.md>), [element](<https://devfeed.tech/tags/element.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-software](<https://devfeed.tech/tags/enterprise-software.md>), [executive](<https://devfeed.tech/tags/executive.md>), [experience](<https://devfeed.tech/tags/experience.md>), [features](<https://devfeed.tech/tags/features.md>), [focus](<https://devfeed.tech/tags/focus.md>), [products](<https://devfeed.tech/tags/products.md>), [research](<https://devfeed.tech/tags/research.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

The author argues that enterprise software often neglects visual polish and usability, and that this weakens how products feel in demos and daily use. They point to cluttered interfaces and small design flaws in products including Polarion, Rational Team Concert, DevSuite, Rally Software, and Salesforce, while acknowledging that B2B economics can discourage investment in design. The author believes expectations shaped by polished consumer and mobile products are making design more important, and argues that good design can combine usefulness with restraint and precision. They favor craftsmanship and passion even though design investment may not bring significant additional revenue immediately.

### Source excerpt

Every time I research some domain related to enterprise and check various products in it, my eyes bleed. I just can't embrace unsightly...

## Visual Management Software

DevFeed: [Visual Management Software](<https://devfeed.tech/articles/visual-management-software-30432.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/visual-management-software>)

Published: 2014-04-22T12:10:12Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Data visualization](<https://devfeed.tech/topics/data-visualization.md>), [task management](<https://devfeed.tech/topics/task-management.md>), [roadmaps](<https://devfeed.tech/topics/roadmaps.md>)

Tags: [project-management](<https://devfeed.tech/tags/project-management.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Targetprocess 3 presents project data as interactive views that users can filter, inspect and change in place. It offers boards for two-dimensional views, lists for hierarchies, and timelines for progress, workload and planning; users can switch views, zoom, focus, and apply flexible filters. The text also describes creating boards, updating hierarchical backlogs, and manipulating selected items through batch drag and drop. It argues that this approach addresses limitations it attributes to other project management tools, such as fragmented views, restricted filtering and static reports. These are the source's claims; the excerpt provides no independent comparison or evaluation.

### Source excerpt

Targetprocess

## Why Targetprocess is better than Trello

DevFeed: [Why Targetprocess is better than Trello](<https://devfeed.tech/articles/why-targetprocess-is-better-than-trello-30442.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/why-targetprocess-is-better-than-trello>)

Published: 2013-12-20T14:18:27Z

Content type: comparison

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [To-Do](<https://devfeed.tech/topics/todo.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [add-ons](<https://devfeed.tech/tags/add-ons.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [api](<https://devfeed.tech/tags/api.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [beautiful](<https://devfeed.tech/tags/beautiful.md>), [better](<https://devfeed.tech/tags/better.md>), [billing](<https://devfeed.tech/tags/billing.md>), [board](<https://devfeed.tech/tags/board.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [card](<https://devfeed.tech/tags/card.md>), [cases](<https://devfeed.tech/tags/cases.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [column](<https://devfeed.tech/tags/column.md>), [comes](<https://devfeed.tech/tags/comes.md>), [complex](<https://devfeed.tech/tags/complex.md>)

### AI overview

Trello is described as simple, fast, free, and well supported for collaboration, but harder to use as boards grow: the text cites 100+ cards, limited filtering and sorting, and cards that belong to a single board. Targetprocess addresses these needs with collapsible and zoomable views, list-like backlog browsing, sorting and filtering, reusable entities across boards, time tracking and reports, assignable tasks with custom fields, and dependency views. It also supports more tags and timeline visualizations. These capabilities add flexibility for large or varied workflows, but Targetprocess is more complex and has a learning curve; the text leaves the switch as a user decision.

### Source excerpt

But more complex for sure.

## Visual Specifications

DevFeed: [Visual Specifications](<https://devfeed.tech/articles/visual-specifications-30433.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/visual-specifications/>)

Published: 2013-10-26T10:56:50Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Specifications](<https://devfeed.tech/topics/specifications.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [Software](<https://devfeed.tech/topics/software.md>), [bug](<https://devfeed.tech/topics/bug.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [bug](<https://devfeed.tech/tags/bug.md>), [software](<https://devfeed.tech/tags/software.md>), [specifications](<https://devfeed.tech/tags/specifications.md>)

### AI overview

The article examines why software specifications are often difficult to write and poorly received. It contrasts lightweight Agile requirements with detailed documentation and describes two developer attitudes toward specifications, arguing that the right approach depends on team conditions and communication.

### Source excerpt

Why most software specifications suck and how to improve them

## First impression failures

DevFeed: [First impression failures](<https://devfeed.tech/articles/first-impression-failures-30329.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/first-impression-failures>)

Published: 2013-07-15T12:22:04Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Usability](<https://devfeed.tech/topics/usability.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [ui](<https://devfeed.tech/tags/ui.md>), [usability](<https://devfeed.tech/tags/usability.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

This opinion article explains how first-time users can become stuck when applications provide too few successful paths and insufficient guidance. It recommends identifying obstacles, improving user flows, and observing recorded first-use sessions from people in the target audience.

### Source excerpt

You don't have a second chance to make a first impression. It's important to design users' flows and remove all obstacles on their way.

## Software Development: Fast and Slow.

DevFeed: [Software Development: Fast and Slow.](<https://devfeed.tech/articles/software-development-fast-and-slow-30411.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/software-development-fast-and-slow/>)

Published: 2013-06-14T15:41:57Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [development-process](<https://devfeed.tech/topics/development-process.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [backlog](<https://devfeed.tech/tags/backlog.md>), [book](<https://devfeed.tech/tags/book.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [customer](<https://devfeed.tech/tags/customer.md>), [daniel-kahneman](<https://devfeed.tech/tags/daniel-kahneman.md>), [decision-making](<https://devfeed.tech/tags/decision-making.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [feature](<https://devfeed.tech/tags/feature.md>), [features](<https://devfeed.tech/tags/features.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

### AI overview

The article argues that software teams can improve decisions by slowing down intuitive judgments and using simple models. It compares Kahneman's fast, effortless System 1 with effortful System 2, using cache and business operations as an analogy. Examples include giving a quick estimate despite missing requirements, prioritizing one customer's request without considering the wider customer base, substituting current progress for a forecast, and choosing technologies based on preference. It recommends pausing and evaluating options with models such as Kano, or a backlog model that considers feature type, customer and lead requests, competitor offerings, novelty, effort, and risk. The excerpt presents modeling as a way to examine a problem from multiple angles, while acknowledging skepticism about people's ability to engage System 2 reliably.

### Source excerpt

How to use ideas from the great book by Daniel Kahneman Thinking, Fast and Slow.

## Agile is Poisonous

DevFeed: [Agile is Poisonous](<https://devfeed.tech/articles/agile-is-poisonous-30292.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/agile-is-poisonous/>)

Published: 2013-04-01T15:41:57Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Kanban](<https://devfeed.tech/topics/kanban.md>), [Standup Meeting](<https://devfeed.tech/topics/standup-meeting.md>), [pair\_programming](<https://devfeed.tech/topics/pair-programming.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [acceptance-tests](<https://devfeed.tech/tags/acceptance-tests.md>), [agile](<https://devfeed.tech/tags/agile.md>), [agile-development](<https://devfeed.tech/tags/agile-development.md>), [iteration](<https://devfeed.tech/tags/iteration.md>), [kanban](<https://devfeed.tech/tags/kanban.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [qa](<https://devfeed.tech/tags/qa.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [scrum](<https://devfeed.tech/tags/scrum.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The author reports that their company abandoned several agile practices after finding them unproductive: daily standups were replaced by weekly email status reports, while one- and two-week iterations brought meeting overhead, rushed work, technical debt, and testing difficulties. Kanban's 23-state board and later state limits did not prevent deadline pressure, work-in-progress overload, or reported 100-hour weeks. The account also describes punitive productivity displays and enforced pair programming, which led to conflict and, in one incident, a broken nose; pair programming was then banned. These are the author's company-specific experiences, not evidence that the practices fail universally.

### Source excerpt

I don't believe in agile development anymore. Our company applied agile practices from day one. We've started agile usage in 2006. We tried almost everything: Extreme Programming, Scrum, Kanban and many many small practices. Did it stick? Hell no. Let's review the lessons. Daily Meetings They are just worthless. We used to gather together at 11 am in a single room and report what was completed, what is not, whether there are some blockers. Well, when there are about 30 people in a room these meetings are not fun. They took up to 10 minutes usually, but sometimes they took as long as 15 minutes (I think this duration just can't be tolerated). After the meeting, people go and grab coffee, chat about problems, chat about ideas... These useless activities distract people and they spend less time on coding. We've replaced daily meetings with a weekly status reports sending via email. The format is very simple with just 7 questions like "Please, enumerate all tasks you've completed last week" and "How you estimate your personal productivity on a scale from 1 (low) to 10 (exceptional)". We collect all emails, process them and have a real stats per person, per week, per project, etc. Really cool! Iterations We tried 1 week and 2 weeks iterations. Neither worked out. With short iterations there was a constant pressure to get shit done and technical debt accumulated like a huge garbage heap. It is impossible to squeeze a good solution into a short timeframe. There're so many meetings like iteration planning, planning poker sessions, iteration demo, iteration retrospective... These meetings are killing productivity, you know. QA were struggling with short iterations as well. It is impossible to test a user story thoroughly in few days. We tried mini-waterfall in a single iteration -- didn't work, testing phase started just 2 days till the end of the iteration with miserable outcome. We tried to write many unit tests and acceptance tests -- didn't help, since requirements were changi

## Great Things Take Time

DevFeed: [Great Things Take Time](<https://devfeed.tech/articles/great-things-take-time-30337.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/great-things-take-time/>)

Published: 2013-03-04T15:41:57Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [cars](<https://devfeed.tech/tags/cars.md>), [change](<https://devfeed.tech/tags/change.md>), [company](<https://devfeed.tech/tags/company.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [created](<https://devfeed.tech/tags/created.md>), [deep](<https://devfeed.tech/tags/deep.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [fail](<https://devfeed.tech/tags/fail.md>), [fast](<https://devfeed.tech/tags/fast.md>), [faster](<https://devfeed.tech/tags/faster.md>), [game](<https://devfeed.tech/tags/game.md>), [game-development](<https://devfeed.tech/tags/game-development.md>), [games](<https://devfeed.tech/tags/games.md>), [good](<https://devfeed.tech/tags/good.md>), [history](<https://devfeed.tech/tags/history.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

The essay argues that meaningful product success often takes time: software can be updated and iterated quickly, but sustained focus and repeated attempts help produce better solutions. It contrasts "hedgehog" companies, which concentrate on one area, with "fox" companies that pursue varied markets and projects. Rovio's many games before Angry Birds, Apple's careful product launches, and Salesforce's enterprise SaaS focus illustrate the hedgehog model; the author says diversified service companies may grow and earn well but are unlikely to create something disruptive. Focus alone is not enough: people, strategy, and passion matter too. Patience helps avoid rushed, superficial work, while persistence lets teams revisit problems with new experience and ideas. The author also recognizes that crises demand intense effort, and describes balancing that urgency with patience as difficult.

### Source excerpt

Great things take time. Evolution and complexity are two sides of the nature development. Let's take cars. Cars are becoming more and more complex. At the same time, cars are becoming more reliable, faster, more efficient, safer and better. It took humankind a century to get there. The progress pace is impressive, but incomparable with software development. Things change in software development world with an astonishing "never seen before" speed. 10 y.o. technologies are history. 10 y.o. software without major upgrades is dead. While 10 y.o. cars are quite good and decent. We, software developers, are blessed with a gift that makes our industry truly different -- we can upgrade working systems on the fly. To have a new car you should sell an old one and buy the new car. To have a new version of SaaS application you don't have to move a finger. Software developers have a luxury to iterate fast, fail fast and emerge viable, efficient solutions. Software development industry is not so young, it is about 50 years old. It took us 50 years to reach the point where "software is eating the world". Companies: Hedgehogs and Foxes OK, back to the main point of this essay. There are two types of companies: Hedgehogs and foxes. Hedgehog company takes one area and digs deep. It usually create a single software application for a single market (no matter if niche or wider). Fox company builds many applications for various markets, it constantly tries many new things and never stick to a single thing. I don't like foxes. In most cases they can't create something significant. However, let's check some examples. Rovio created 50 or so games till the Angry Birds slam-dunk It's a hedgehog company. It was fully focused on game development. They tried various models and various gameplays. They iterated and failed many times. Apple is a hedgehog company (well, there were different times at Apple, but now this statement is correct). Apple launches new products with care. No rush jumps to fin

## UX Rule #1: Everything is Possible

DevFeed: [UX Rule #1: Everything is Possible](<https://devfeed.tech/articles/ux-rule-1-everything-is-possible-30326.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/everything-is-possible/>)

Published: 2012-09-07T15:41:57Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [User Experience](<https://devfeed.tech/topics/user-experience.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [consistency](<https://devfeed.tech/topics/consistency.md>)

Tags: [batch](<https://devfeed.tech/tags/batch.md>), [change](<https://devfeed.tech/tags/change.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [data](<https://devfeed.tech/tags/data.md>), [domain](<https://devfeed.tech/tags/domain.md>), [email](<https://devfeed.tech/tags/email.md>), [hidden](<https://devfeed.tech/tags/hidden.md>), [model](<https://devfeed.tech/tags/model.md>), [october](<https://devfeed.tech/tags/october.md>), [operations](<https://devfeed.tech/tags/operations.md>), [possible](<https://devfeed.tech/tags/possible.md>), [project](<https://devfeed.tech/tags/project.md>), [properties](<https://devfeed.tech/tags/properties.md>), [rules](<https://devfeed.tech/tags/rules.md>), [software](<https://devfeed.tech/tags/software.md>), [software-systems](<https://devfeed.tech/tags/software-systems.md>), [story](<https://devfeed.tech/tags/story.md>), [system](<https://devfeed.tech/tags/system.md>), [systems](<https://devfeed.tech/tags/systems.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### AI overview

The article argues that software should support every operation allowed by its domain model: extracting, presenting and changing data, including changing properties and relationships or creating entities. It illustrates this with an email client that can group messages by sender or move October's messages into a folder, and with inconsistent project tools that allow moving a story or batch editing features but restrict changing an owner or editing tasks in bulk. The author says knowing an operation is possible builds user confidence, even when the control is advanced or hard to find, and criticizes restrictions that feel illogical.

### Source excerpt

Software systems work with data. I believe great system should obey the one simple rule Every possible operation with data does exist The knowledge of possibility is a really powerful thing. I want to create a software system that has almost no restrictions in a given domain. You should be able to extract any data, present data and change any data. Let's imagine you are using an email client. Suddenly, you want to group all incoming messages by sender. You should be able to do that. Or you want to find all emails for October, create October folder and move the emails into this folder. That should be possible as well. Every software system has a domain model behind and a set of rules. As a minimum, system should provide all kind of operations on this model: change properties, change relations, create entities, etc. Unfortunately, almost all existing systems are restrictive. If you know that operation is possible, you'll find it. This knowledge gives you a confidence. The operation can be quite advance and well hidden, but still it is much better to know that it does exist than dealing with illogical restrictions. Why the hell I can move a user story into a project, but can't change it's owner? Why I can change features in batch, but can't do that with tasks? If the rule #1 is applied, you are giving many great things to the end users: Confidence UI consistency Power Pretty cool it seems...

## A Curious Company

DevFeed: [A Curious Company](<https://devfeed.tech/articles/a-curious-company-30397.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/q-curious-company>)

Published: 2012-03-19T09:12:28Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

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

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [agile-project-management](<https://devfeed.tech/tags/agile-project-management.md>), [best](<https://devfeed.tech/tags/best.md>), [books](<https://devfeed.tech/tags/books.md>), [ceo](<https://devfeed.tech/tags/ceo.md>), [changes](<https://devfeed.tech/tags/changes.md>), [client](<https://devfeed.tech/tags/client.md>), [company](<https://devfeed.tech/tags/company.md>), [cool](<https://devfeed.tech/tags/cool.md>), [curiosity](<https://devfeed.tech/tags/curiosity.md>), [education](<https://devfeed.tech/tags/education.md>), [environment](<https://devfeed.tech/tags/environment.md>), [features](<https://devfeed.tech/tags/features.md>), [follow](<https://devfeed.tech/tags/follow.md>), [goals](<https://devfeed.tech/tags/goals.md>), [learn](<https://devfeed.tech/tags/learn.md>), [learning](<https://devfeed.tech/tags/learning.md>), [management](<https://devfeed.tech/tags/management.md>), [need](<https://devfeed.tech/tags/need.md>), [people](<https://devfeed.tech/tags/people.md>)

### AI overview

A 35-person bootstrapped company revived curiosity by setting an ambitious goal--building the best agile project management software for small and medium companies--and changing its culture. The CEO argues that an environment of trust and learning matters more than hiring only people who already learn actively: hire curious people, give them room to make decisions, tolerate failure, and support exploration. The company stopped tracking time, estimating effort, and setting deadlines; it offered five hours each Friday for personal learning, held internal conferences, and supported side projects. The CEO reports renewed discussion, learning, and enjoyment at work, while acknowledging uncertainty about long-term success. In this view, leaders set goals, maintain trust, support people, and occasionally restart activities during low-mood periods rather than trying to motivate employees.

### Source excerpt

Recently I've got an interesting question: "Do you hire people who learn new things or do you create an environment where everyone starts learning"? Who is this mysterious "everyone"? These people are not very active. These people prefer to adopt to existing conditions and follow the rules. I answered almost immediately "both", but what really is more important? I've always learned new things. Sure, my self-education style is far from perfect. I jump from subject to subject and read quite random books from disciplines barely related to my actual work. I know that and trying to fix that. I'm 33. Right now I try to gain fundamental CS knowledge (while I don't actually need to). I'm a CEO of a small 35-people-company. Bootstrapped. Profitable. And curious. The spirit of curiosity was always inside me. It was inside our company in early days, but depleted. Novelty darkened and goals blurred. The company started to look like "just one more place to work at". I hated that feeling. We did common tasks, released common features. It was two years ago. Two years ago we've changed everything. What is the right goal for the company? Do something incredibly cool, something that you can honorably call "the best in the world". Why the hell spend your time on boring, common staff? Fuck it. You don't want to create "yet another twitter client". You want to create "best in the world twitter client". If you can't, learn and try or die trying. We set the goal to create "the best in the world agile project management software for small and medium companies". And suddenly everything started to look sooo simple. What do you need to do something best in the world? More precise, "who" do you need? You need the best people. Most likely you don't have them yet, but there is a good chance you can grow them. Why not? You don't need people who hate changes. You don't need people who hate learning. You need curious, hungry and intelligent people. If you have best people, you should provide best p

## Expertise and Software Development

DevFeed: [Expertise and Software Development](<https://devfeed.tech/articles/expertise-and-software-development-30327.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/expertise-and-software-development>)

Published: 2011-10-02T09:12:28Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Algorithms](<https://devfeed.tech/topics/algorithms.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [css](<https://devfeed.tech/tags/css.md>), [java](<https://devfeed.tech/tags/java.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

### AI overview

The excerpt argues that teaching a fixed checklist can lead students to gather information by rote instead of forming hypotheses. It applies this criticism to software development: learning technologies such as CSS, RoR, and Java without foundational knowledge may produce long résumés but leave developers unable to write a simple algorithm or explain why a solution fits a problem. The excerpt advocates teaching both how to learn a subject and how to apply its fundamentals in practice.

### Source excerpt

Students are commonly given an outline of all data that they might collect, organized by "social history," "previous illness," and so on, suggesting that medical diagnosis is a process of collecting data in a fixed order. The results is that students sometimes collect information by rote, without thinking about hypotheses at all! This is the excerpt from the "Nature of Expertise" book I'm reading. This example shows how educational system is broken. The first two things EVERY educational system should do are: teach how to learn the subject. give fundamental understanding of the subject and provide a formalized mechanism how to apply knowledge on practice in the most efficient way. In software development people often learn new technologies like CSS, RoR, Java, etc., without fundamental knowledge of the subject. As a result, they have impressive list of technologies in CV, but fail to write a simple algorithm or explain why this particular solution is best to this particular problem. Average developer can solve problems using google. Good developer knows patterns and some clever techniques. Great developer can explain EVERY decision he makes.

## The Race to Performant Application: Designing Time and Flow

DevFeed: [The Race to Performant Application: Designing Time and Flow](<https://devfeed.tech/articles/the-race-to-performant-application-designing-time-and-flow-30426.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/time-flow/>)

Published: 2009-05-26T15:41:57Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Software](<https://devfeed.tech/topics/software.md>), [Usability](<https://devfeed.tech/topics/usability.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Agile](<https://devfeed.tech/topics/agile.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [required](<https://devfeed.tech/tags/required.md>), [software](<https://devfeed.tech/tags/software.md>), [ui](<https://devfeed.tech/tags/ui.md>), [usability](<https://devfeed.tech/tags/usability.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

The article argues that software products should prioritize simplicity, performance, and usability instead of continually adding features, functions, and settings. Drawing on Steven C. Seow's book, it discusses Hick-Hyman Law, perceptible performance improvements, and the importance of preserving user flow.

### Source excerpt

Fact: Complexity causes 50% of product returns Fast and easy-to-use applications are quite rare. Simplicity and Performance are two major properties of any killer software product. We, as software developers, should pay attention to these properties as non-functional requirements, but in real life we often tend to implement more features, more functions, more settings, more, more, more... The race is hard to win with this strategy along the whole way. I must confess we've done almost the same to TargetProcess. We went on with providing more and more features and options. Definitely we tried to keep the application simple and fast, but these goals were secondary. We've stopped. And changed. Now we are focusing on better performance and usability. We think that TargetProcess is a quite feature-rich application that fulfills most needs in agile project management. It is time to stop and find answers to the questions: "Where do people get stuck with our software?", "What is complex and how it can be simplified?", "How to make TargetProcess enjoyable to use?", "How to make TargetProcess the most performant software in our niche?". The questions are hard to answer and address quickly, but we are looking for the answers. Steven C. Seow wrote an excellent book about principles that should be taken into consideration for any "performant" application Designing and Engineering Time: The Psychology of Time Perception in Software. I read it and want to share some interesting observations. Hick-Hyman Law describes the time it takes for a person to make a decision as a result of the possible choices he or she has. Simply speaking, less functions -- simpler and faster choice. It leads to several conclusions what we should do as software developers: Minimize options. Obviously, if you have 50 elements on the screen, it takes time to choose which action is required. If you have 20, the UI is faster to work with. Keep it simple. Well, it is a general principle for all the facets of agile

## Simple Rules, Complex Systems and Software Development

DevFeed: [Simple Rules, Complex Systems and Software Development](<https://devfeed.tech/articles/simple-rules-complex-systems-and-software-development-30407.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/simple-rules-complex-systems-software-development/>)

Published: 2009-03-23T15:41:57Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Complex Systems](<https://devfeed.tech/topics/complex-systems.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Cellular automaton](<https://devfeed.tech/topics/cellular-automaton.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [communication](<https://devfeed.tech/tags/communication.md>), [complex-systems](<https://devfeed.tech/tags/complex-systems.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [development](<https://devfeed.tech/tags/development.md>), [development-process](<https://devfeed.tech/tags/development-process.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [rules](<https://devfeed.tech/tags/rules.md>), [simple](<https://devfeed.tech/tags/simple.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

### AI overview

The source argues that simple local rules can produce complex behavior, illustrating the idea with ants' scent trails, flocking principles, and Conway's Game of Life. It then applies this to software development: complex processes can encourage mechanical behavior, while Scrum's small set of roles, rules, and artifacts is presented as a way to support learning, feedback, communication, and cooperation. The source notes that implementing Scrum can be difficult because people may resist changing habits, and warns that deep management hierarchies and lengthy process documents can add unnecessary complexity.

### Source excerpt

Many complex systems are based on simple rules. A set of several simple rules leads to complex, intelligent behavior. While a set of complex rules often leads to a dumb and primitive behavior. There are many examples. Ants Colony How ants search for food? They do not have cell phones, cars and mini-markets near the nest. They should have something simpler to communicate. Here is how ants work: Travel randomly in search for food. Take a piece of food and head straight back to the nest. On the way back to the nest lay down an odor trail. Notify nestmates of the discovered food encouraging them to leave the nest. These newly recruited ants will follow the odor trail directly to the food source. In their turn, each ant will reinforce the odor trail until the food is gone. Sounds simple? Take a look at this very nice ants colony model. Drop some food and enjoy the action. Birds Flocks Birds flocks are beautiful. You may think that the movement gets orchestrated by one savvy bird. But this is not the case. A bird glock is guided by three simple principles (every decent bird knows them): Separation: steer to avoid stumbling upon local flockmates. Alignment: steer towards the average heading of local flockmates. Cohesion: steer to move towards the average position of local flockmates. Simple? Yes, it is. Look at the picture on the right. It's just amazing! Game of Life Game of Life was invented in 1970 by John Conway. It is a cellular automaton and simulates the birth, death, etc., of organisms based on certain rules: Each cell with one or no neighbors dies, as if of loneliness. Each cell with four or more neighbors dies, as if of overpopulation. Each cell with two or three neighbors survives. Each empty cell with three neighbors becomes populated. Simple rules. But these rules lead to fantastic diversity of the forms. Different types of the forms have been discovered e.g. still objects, oscillators, gliders, spaceships, etc. It is impossible to predict the state of a syste

## Zero Defects? Are You Kidding Me?

DevFeed: [Zero Defects? Are You Kidding Me?](<https://devfeed.tech/articles/zero-defects-are-you-kidding-me-30444.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/zero-defects/>)

Published: 2009-03-19T15:41:57Z

Content type: opinion

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [agile](<https://devfeed.tech/tags/agile.md>), [army](<https://devfeed.tech/tags/army.md>), [battlefield](<https://devfeed.tech/tags/battlefield.md>), [book](<https://devfeed.tech/tags/book.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [complex](<https://devfeed.tech/tags/complex.md>), [defects](<https://devfeed.tech/tags/defects.md>), [drive](<https://devfeed.tech/tags/drive.md>), [engine](<https://devfeed.tech/tags/engine.md>), [errors](<https://devfeed.tech/tags/errors.md>), [hard-drive](<https://devfeed.tech/tags/hard-drive.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [house](<https://devfeed.tech/tags/house.md>), [initiative](<https://devfeed.tech/tags/initiative.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [lean](<https://devfeed.tech/tags/lean.md>), [mistakes](<https://devfeed.tech/tags/mistakes.md>), [motivation](<https://devfeed.tech/tags/motivation.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

The author argues that a zero-defects mentality can suppress initiative: fear of mistakes may discourage refactoring, sound decisions, and taking responsibility. Software is difficult to test and predict fully, so production bugs cannot realistically be eliminated; the practical goal is to minimize them. The excerpt introduces strategies for doing so but does not include their details, and rejects zero bugs as a sprint goal.

### Source excerpt

Are you familiar with zero defects mentality? It looks very good from the first sight. Zero defects... Let me think... Well, cool! I like it! I'd like to have zero defects in my projects. So, what is zero defects mentality? Here is the quote from Lean Software Development an Agile Toolkit book: "One of the fastest ways to kill motivation is what is called in the US Army a zero defects mentality. A zero defects mentality is an atmosphere that tolerates absolutely no mistakes; perfection is required down to the smallest detail. The army considers a zero defects mentality to be a serious leadership problem, because it kills the initiative necessary for success on a battlefield" -- Mary & Tom Poppendieck Obviously, zero defects mentality is not something that HOUSE M.D. likes ;) Moreover, I think Dr. House hates zero defects mentality. It causes several unpleasant effects: Not enough courage to refactor complex, messy, buggy, but important piece of code. Can't make important decision, instead make less risky, but wrong decision. Do everything to avoid responsibility, that leads to coward and stupid behavior. "Zero defects" may sound good. But in reality you still have errors after production. Even in predictable and (quite) easily testable industries (hardware, automobile, etc.) there are problems with 100,000 power adapters that should be replaced (or hard drive problems, or engine problems, I bet you can continue the list). How can we expect zero defects in software development? It is harder to test, harder to define in details, harder to predict. Software development is a complex adaptive system, we can't predict all effects. Bugs in production is a normal thing, and by "normal" I mean we can't bring them to zero. We can (and should) minimize them using all possible ways, but The Last Bug is a mirage. There are several obvious strategies that may help: Test Driven Development. Nice side effect of TDD is a unit tests suite. You have tests for new code, and you have unit te

## Edge of Chaos and Hyper Productive Software Development Teams

DevFeed: [Edge of Chaos and Hyper Productive Software Development Teams](<https://devfeed.tech/articles/edge-of-chaos-and-hyper-productive-software-development-teams-30321.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/edge-of-chaos-hyper-productive-teams/>)

Published: 2008-12-02T15:41:57Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [development-process](<https://devfeed.tech/topics/development-process.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [am](<https://devfeed.tech/tags/am.md>), [apply](<https://devfeed.tech/tags/apply.md>), [base](<https://devfeed.tech/tags/base.md>), [but](<https://devfeed.tech/tags/but.md>), [call](<https://devfeed.tech/tags/call.md>), [can](<https://devfeed.tech/tags/can.md>), [cas](<https://devfeed.tech/tags/cas.md>), [cellular](<https://devfeed.tech/tags/cellular.md>), [cellular-automata](<https://devfeed.tech/tags/cellular-automata.md>), [changes](<https://devfeed.tech/tags/changes.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [complete](<https://devfeed.tech/tags/complete.md>), [complex](<https://devfeed.tech/tags/complex.md>), [creative](<https://devfeed.tech/tags/creative.md>), [development](<https://devfeed.tech/tags/development.md>), [edge](<https://devfeed.tech/tags/edge.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

The excerpt argues that software teams may be most productive between rigid order and unchecked chaos: heavy processes can suppress creativity, while having no rules can leave teams stuck in "hack & fix." It connects this balance to agile practices such as feedback, information exchange, adaptability, and self-organization, and relates those qualities to Clinton Keith's conditions of independence, leadership, core competency, and cooperation. The author says hyper-productivity is difficult to define, presents these properties as ones that may help achieve it, and suggests that CTOs, CIOs, project managers, and Scrum Masters should remove obstacles that impede teams. The excerpt does not provide a detailed method for measuring or reliably producing hyper-productivity.

### Source excerpt

Many researchers tend to think that CAS may work efficiently at the edge of chaos. A system with a very high order can't solve complex creative tasks, as well as a pure chaotic system. It seems the system should balance between chaos and order to survive and adapt. The "edge of chaos" term was emerged during self-reproductive cellular automata researches in 1990. It appeared that at a particular noise level the system can reproduce its state, while at a low noise levels states are random. This edge value was mathematically analyzed and it was shown that in such a state the system has a maximum of information. The "Edge of Chaos" term spread and applied to complex adaptive systems. For example, we may suggest that evolution drives systems to the edge of chaos, and it is one of the reasons of life origin. Life is a very interesting and complex thing in itself. Most likely it could not appear neither in order state and in chaos state. Life exists if there is a stable base, but with possibilities of changes. Edge of Chaos and Software Development How can we apply the edge of chaos concept to software development? Obviously, edge of chaos is a state where the development team works with maximum efficiency. Complex processes and explicit rules impede creativity. The team becomes too ordered to think :). On the other hand, no processes and no rules lead to chaos. The development team can't complete anything useful, and that is something we call hack & fix process. As a software development folks, we are particularly interested in two questions: How can we drive the team to the edge of chaos? How we will ensure that the team is at the edge of chaos? The human who knows the answers to these questions most certainly will be rich and famous. However I am not sure whether you can find such a man. It is obvious that edge of chaos = hyper productivity. This term often used in Scrum. However it is quite hard to define hyper productivity. Hyper-productive teams are hard to define.

## Agile Software Development and Complex Adaptive Systems: Intro

DevFeed: [Agile Software Development and Complex Adaptive Systems: Intro](<https://devfeed.tech/articles/agile-software-development-and-complex-adaptive-systems-intro-30410.md>)

Original publisher: [Read original article](<https://www.mdubakov.com/posts/software-development-cas/>)

Published: 2008-11-22T15:41:57Z

Content type: article

Language: en

Sources: [Michael Dubakov](<https://devfeed.tech/sources/blog-by-michael-dubakov.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Complex Systems](<https://devfeed.tech/topics/complex-systems.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [cas](<https://devfeed.tech/tags/cas.md>), [complex](<https://devfeed.tech/tags/complex.md>), [development](<https://devfeed.tech/tags/development.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

The author argues that software development shares the basic properties of a Complex Adaptive System (CAS), and that understanding CAS may explain why agile practices work and traditional project management techniques fail in software projects. The planned posts will examine CAS properties--including adaptation, feedback, self-organization, emergence, edge of chaos, and nonlinearity--and consider their application to software development and agile principles. These are presented as the author's aims and expectations, not as conclusions demonstrated in this introduction.

### Source excerpt

There are quite many agile processes in the world already. We have Extreme Programming, Scrum, Crystal, DSDM, Feature Driven Development, Lean. Some of them are famous, some are maybe dying. The point is, we have plenty of agile processes. In general this is not too bad. We've got alternatives, they move agile forward and solve real problems. On the other hand, I feel the lack of information on the roots of agile processes. Most articles available are missing the point on my opinion. Why iterative development works? Why agile manifesto is the truth? Why traditional project management techniques miserably fail on software development projects? Somehow many people feel the right direction. They have a background that guides their decisions. We feel that agile manifesto brings real value. We has proven this in practice after all! But I personally feel that there is something deep and cool behind most of agile practices. Something that will explain why this all works. While reading Jeff's post about Scrum roots, I found a reference to Complex Adaptive Systems. I went digging into more details. I read a lot about CAS and related things and there were many "a-ha" moments. There are so many parallels between CAS and Software Development. It is pretty obvious that Software development is a Complex Adaptive System itself. It has almost all basic properties of CAS and it is interesting to read, for example, about adaptation in various CAS and think about its application to the software development and agile principles. I believe that a deep understanding of Complex Adaptive Systems will shed some light to the real roots of agile development and will answer important questions. With this knowledge in hand it will be easier to see why this works and why that failed. It will be easier to make decisions and create a better software faster. However, I am not sure how interesting this will be to the people :) In the next several posts I will write on why software development is CAS

[Next page](<https://devfeed.tech/sources/blog-by-michael-dubakov.md?cursor=WyIyMDA4LTExLTIyVDE1OjQxOjU3KzAwOjAwIiwgIjJkN2VmMWQ4LTBkY2EtNGMyZS1hM2M4LTA0MjdkYzI2NWE1NCJd>)