Skip to content

Search for:

Search

Blog
Twitter
Patreon
Talks
Newsletter
Search

Search for:

Search

Blog
Twitter
Patreon
Talks
Newsletter
Search

Historical reasons

December 2, 2012

Historical reasons

Share this:

Twitter
LinkedIn
Reddit
Pocket
Facebook

Post navigation

On order and overhead

Historical reasons

Search for:

popular

Product teams own capabilities, not (only) code.
PowerShell equivalent of find
Better coordination, or better software?
Develop in Docker: Node.js, Express, & PostgreSQL on Heroku
Git Rebase inside IntelliJ IDEA

twitter

instagram

Every software team has a “process,” a series of steps of work. And then move back and forth between them in no order, mashing them together and adding others as needed. Let’s call this a set of activities, and stop pretending work moves from left to right.

I am a daffodil in December

Can we see the system without owning it, without making it right or wrong?

meta

Log in
Entries feed
Comments feed
WordPress.org

Blog
Twitter
Patreon
Talks
Newsletter

Tags

abstraction agile architecture automation change clojure complexity concurrency conference design DevOps Docker Engineering functional functionalPrinciples Generativity git Java javascript learning node OO philosophy property-based testing reference ruby scala science Software Development symmathesy systems Systems Thinking teams testing thinkingFunctionally tistil typescript Web Development wit Yak Shaving

Archives

Archives

Search

Search for:

Sort by

© 2021 Jessitron, LLC

Scroll back to top