457 karma · joined April 27, 2013
Some of us forced into sub-optimal patterns of behaviour now because the power structures of the organisations we work in prescribe following certain Agile "standards'.
There's lots of complaining (which is summarised in the article) but a lack of concrete suggestions to take things forward.
What's on the top of your wish list of improvements to make?
Knowing the way is 10x over finding the way.
But I think this is still an interesting piece of research, backing up a lot of what we expect empirically.
I hope people find the imagery useful.
Even if you aren’t on-board with the ones this article mentions, there are a bunch more in this list.. and it could probably do with a refresh soon
I guess we live in a world of too much choice, but it feels like there’s so much good stuff out there, and so many good bits of software that the world simply doesn’t have time To appreciate them all.
The winner-take-all nature of software these days is a big anti goal in my view.
Vvvvvv was lucky but a lot of people are just sucked into learning the world of growth-hacking. It might be just a sad downside of the Metcalfe effect but surely there are thousands of other games that deserved some attention too?
(An idea brought up on hacker news one day)
How does this model square with the estimation problems we see on a day-to-day basis?
Would love some feedback as I write this - there are a few more pages written and further ones planned in the series
Thanks
This episode starts easy with extrapolation, and adds the confounding factors from there.
Would love some feedback!
But surely, it's worth at least considering.
The argument here is that the development team is there to stop the business failing.
Is that all there is? Or is there something else?
This is the third part in a series of articles in my “Risk-First” (focused on addressing the concept of Risk in Software Development).
It’s looking at the question of, to what extent is debugging a series of gambles?
In looking for a bug, every time we try something out, we’re gambling our development time against testing some part of our code to narrow the range of places where the bug can live.
This is how it feels to me. I’d appreciate some feedback from the community on this.
So many things in life are about pulling the wool over the eyes of the young and idealistic.
Agile seems to have turned into one of them.
Surely there’s more to it than that?
At least, I think that’s the best reason for using estimates. I wrote something about this here: https://riskfirst.org/Estimates
Disclosure masquerading as a plug: I’m writing this at the moment- https://riskfirst.org
This whole article is just saying "Dear client, here's why your model is insufficient".
Which is a much nicer email to write than "Dear client, here's why my model was insufficient". Which is what happens when the estimates go south
- Ideally, I do work that can go on my public website, but working in Investment Banking, that doesn't happen a huge amount.
- Next, I look for work I can _at least_ put on my CV. Some new skill, or a project that will make sense.
- Third, I look for things that will keep my skills current. A lot of the "glue" mentioned in the article fits in this box. I'm ok with it if I feel it's also improving me.
- Then, there comes the stuff you have to learn but don't want to, like the vagaries of some internal process, like provisioning VMs or filling timesheets. I try to avoid this where possible, because it's knowledge that I won't find useful beyond my current contract. Sadly it's often essential..
It's certainly worth managing this, rather than just leaving to chance.
https://riskfirst.org/Evaluating-Risk#discounting-the-future...
Although it’s sometimes reasonable to not write tests, this kind of thing usually happens when everyone is being threatened with the sack on a daily basis, rather than lacking engineering skills
In Extreme Programming Explained, Kent Beck talks about how software development is all about balancing risk.
I’ve arrived at the same conclusion, and have been exploring this on in the Risk-First github project, which contains an argument about how this might be true and articles here about different types of software risk.
Hopefully this is useful to people here. Please feel free to ask anything.
I’ve been working for a while on documenting a “Risk-First” approach to understanding software development, which for me explains a lot of the behaviours we espouse in Agile, Lean, DevOps etc.
However, I wanted to try and apply this to see what insights it brings to bear on various development processes - starting with the Estimation process.
Hopefully this will be useful to some people.
I am currently working on scoping further pages explaining how risk aversion/management is embedded in other practices involved in software development, I would love to hear your thoughts on that.
> Predictably, everything exploded. The number of posts increased. The engagement with said posts increased. This is the scene in a movie in which, having launched something, a bunch of people stand in a large open war room waiting, and suddenly a geek staring at a computer goes wide-eyed, exclaiming, "Oh my god." And then the senior ranking officer in the room (probably played by a scowling Ed Harris or Kyle Chandler) walks over to look at the screen, where some visible counter is incrementing so rapidly that the absolute number of digits starts is incrementing in real time as you look at it, because films have to make a plot development like this brain dead obvious to the audience. And then the room erupts in cheers while different people hug and clap each others on the back, and one random extra sprints across the screen in the background, shaking a bottle of champagne that explodes and ejaculates a stream of frothy bubbly through the air like some capitalist money shot that inspires, later, a 2,000 word essay from Žižek.
Author here. Hope this is of some interest to people at Hacker News.
Feel free to AMA.
thanks, Rob
Author here. I just saw this review was posted of my work.
As the i-programmer review points out, Risk-First is takes the view that all the tasks we take on a software project are managing risk in some way, be it dealing with feature risk, operational risk, or coordination risk in our teams (for example).
All of the content in the book is on a github pages site at riskfirst.org, so feel free to take a look at that before diving in.
Hope this is of use to people here, feel free to ask me anything.
thanks
Also, machines, agents, processes, organisations, whole markets... any time we have an information-based model of the world which we use to interact with reality.
As a whole, I am trying to categorise different risks that we face on software projects, and explain why they are there.
Map and Territory Risk being one of them.
This is a page from the Risk-First project, which has had some interest on HN before. This page is about the mistakes we make within development teams confusing our internal mental model of the world with reality.
I hope it's of interest. Feel free to ask anything.
In the UK the points regularly freeze at even just a couple of degrees below zero, and the trains are just cancelled.
> Internet: Do you think JMAP will really take off?
> Me: JMAP is an open, smart, modern, and powerful E-mail protocol, so probably not.