5 ms·
we're already drones. If i wanted to be an ant, i'd join the military. >lifestyle preferences of the extreme programmer talking about stereotypes, fashion and
by trhway 11y ago
we're already drones. If i wanted to be an ant, i'd join the military.
>lifestyle preferences of the extreme programmer
talking about stereotypes, fashion and fad.
Though the article does state one point which i've always found a funny - software teams/organizations whose job is to build/design complex/network/distributed systems fail to see that they themselves are subject to the same basic rules of complex systems.
Like for example "latency vs. bandwidth" - software organizations everywhere are trying to introduce SCRUM - "latency at all costs" process - in order to increase productivity, ie. bandwidth, and they find themselves in such a deep surprise when productivity is actually falling as result of SCRUM.
- RangerScience 11y ago> we're already drones. If i wanted to be an ant, i'd join the military. Author is talking about ants as they are (which are really awesome!) rather than ants as a poor metaphor for mindlessness. > lifestyle preferences of the extreme programmer As my job duties have gotten more intense and I've needed to become more productive (I say while arguing on the internet at work...) I've really come to appreciate the utility of preferences. As you need to do more, better, faster, you start figuring out the little things that maximize yourself so that you /can/. When I see SCRUM "fail" in that productivity goes down, it's not that teams produce less, it's that they fail to produce what's actually valuable. The 10x engineer doesn't write 10x the code, they write the code that's 10x the value.
- trhway 11y ago>> we're already drones. If i wanted to be an ant, i'd join the military. >Author is talking about ants as they are (which are really awesome!) rather than ants as a poor metaphor for mindlessness. it is exactly the same. Just painted with different sentiments. Self-organization by the way of deciding what to do just based on the current state of the local context is exactly the military way - you carry your order without taking in and analyzing the global context of that order. I.e. mindlessly. It is a _good_ thing there. >When I see SCRUM "fail" in that productivity goes down, it's not that teams produce less, it's that they fail to produce what's actually valuable. yes, that is one of the ways SCRUM kills productivity by design - many valuable things in software can't be (or much harder to) produced while adhering to the strict latency requirements of SCRUM and thus people/teams produce what they can instead while staying inside those latency limits. Again, it is basic system analysis - decomposing system and introducing interfaces in unnatural places just to meet the artificial requirements of the process weakens the system and leads to degradation of it. As i said - it is funny how supposedly professional system designer/developers, ie. software engineering teams and orgs, fail to see it in many cases.
- RangerScience 11y ago> Self-organization by the way of deciding what to do just based on the current state of the local context Isn't this only a problem because the "local context" is limited? Humans can handle really large "local contexts" (otherwise, who'd make the plan in the non-stigmertic organization?), and we can add a big set of time-dimension information to that context ("here's what we're trying to achieve and the information we have about best doing that") In the end, swarm methodologies are about empowering individual agents with intelligence and information such that they "inherently" coordinate and the result of that coordination is the desired, overall effect. "Hire good people, keep them informed, and get out of their way." But yes. The downside of things that focus on rapid iteration (which is how stigmertic stuff works) aren't good at large, single-chunk problems: if you can't iterate your way to a solution, these methods won't work for you. There are some problems and individuals that are well suited to multiple agents iterating closer to an optimal solution, and there are problems and individuals that aren't. The world has me convinced that technology development is the latter and product development is the former: it depends on how quickly I need to adapt to changes beyond my control.
- trhway 11y ago> swarm methodologies are about empowering individual agents with intelligence and information man, it is gold. Sounds like a great pitch to lure into the swarm... Yet it is completely contradictory. Swarm is called swarm because it consists of insects. For swarm intelligence to work, individual intelligence must be dumpened, almost turned off, and the information dispensed to an individual must be minimal to avoid his/her swerving off its prescribed course of action that the intermediate or global plan/context may be heavily depended upon. It is like with a bricklayer or a soldier on the mission - him seeing and thus possibly trying to optimize the global plan especially by altering his mission/plan or its place/time inside the larger may affect his carrying over of the mission or the bricklaying scheme and thus endanger the bigger context. >Isn't this only a problem because the "local context" is limited? it isn't a problem. It is a feature. >Humans can handle really large "local contexts" not really. This is why we have abstraction process.