HNHacker News
TopNewBestAskShowJobs

bobm_kite9

457 karma · joined April 27, 2013

submissionscomments
bobm_kite9··on Thinking Journeys rather than Estimates
I guess alchemy eventually grew up and turned into chemistry. I really hope the same happens to dev but I’m not expecting it in my lifetime
bobm_kite9··on The Post-Agile Movement
It's almost an article of faith ob HN that things like scrum and stand-ups are broken.

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?

bobm_kite9··on Challenging the myth of individual programmer productivity
Exactly. I talk about this at https://riskfirst.org/Estimates

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.

bobm_kite9··on Visualising “Anti Goals” in Software Projects and Startups
This is something of a riff on Sun Tzu ‘Strategy without tactics is the slowest route to victory. ‘.

I hope people find the imagery useful.

bobm_kite9··on Hierarchies are the wheel we’re happy to re-invent over and over and over again
Hierarchies are just a sub-case if directed graphs, which computers handle through pointers (Easily)
bobm_kite9··on Yes Silver Bullet (2019)
I wrote something similar several years ago: https://riskfirst.org/Silver-Bullets

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

bobm_kite9··on Goals and Anti-Goals
Maybe this is just an unassailable difficulty and not an anti-goal as described here, but getting your SaaS idea past ‘the algorithm’ and noticed by an unforgiving world seems to me the biggest problem everyone faces.

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?

bobm_kite9··on Show HN: Kitchen Cabinet Estimates
Part two of a series on the complexity of estimating in software development, exploring the conceit of estimating the time to move a kitchen were it to contain some cabinets, which themselves might contain other cabinets, and so on.

(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

bobm_kite9··on Estimating: Fill the Bucket
Part one of a series I am writing exploring why we have difficulties estimating.

This episode starts easy with extrapolation, and adds the confounding factors from there.

Would love some feedback!

bobm_kite9··on The Purpose of the Development Team
It can be a pain worrying about "what's the worst thing that can happen?" all the time. Maybe even psychologically counter-productive!

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?

bobm_kite9··on Debugging Bets
Hi HN,

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.

bobm_kite9··on Ask HN: What are exercises —e.g. brainstorming, planning, etc— you've seen?
This is one I find useful: https://riskfirst.org/Timed-Thinking
bobm_kite9··on Post-Agile: A Summary
It seems to me that the buy-in isn’t so much about hype-cycles, but just wanting to say the right things to get developers to sign on and work.

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.

bobm_kite9··on Faster, cheaper, and better: A story of breaking a monolith
Why is microservices so much more popular right now than, say, distributed processing via the actor model? It feels like splitting things up with HTTP boundaries is a lot of work, less flexible and precludes a lot of re-use. Is it just because of advances in tooling lately like Kubernetes and docker?
bobm_kite9··on Dear Agile, I’m Tired of Pretending (2018)
Actually I don’t really understand why all the HN posts on agile just devolve into a discussion about the difficulty of estimating.

Surely there’s more to it than that?

bobm_kite9··on Dear Agile, I’m Tired of Pretending (2018)
I think this comes down to the idea that estimates are really for coordination.

At least, I think that’s the best reason for using estimates. I wrote something about this here: https://riskfirst.org/Estimates

bobm_kite9··on Forget monoliths vs. microservices: cognitive load is what matters
This sounds about right. Also it feels like as a paradigm shift it’s not so far from Conway’s Law already
bobm_kite9··on Maybe Agile Is the Problem
So rare that perhaps the meaning of the word has changed irrevocably?

Disclosure masquerading as a plug: I’m writing this at the moment- https://riskfirst.org

bobm_kite9··on Dear Client, Here’s Why That Change Took So Long
Our internal model of the world is always simpler than the world itself (otherwise it wouldn't be a model).

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

bobm_kite9··on Being Glue
As a contract worker, I feel I have to be quite careful about this.

- 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.

bobm_kite9··on Ask HN: How common is it to work on projects with no testing?
I’ve seen this before. It’s not common practice as far as I can see but it does happen. I blogged about it here as ‘discounting the future to zero’

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

bobm_kite9··on Risk-First Software Development: A Quick Summary
Author here,

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.

bobm_kite9··on Software Estimating – Tips (Risk First)
Hi author here,

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.

bobm_kite9··on Status as a Service
I’ve only got halfway through this, but this paragraph was tremendous writing:

> 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.

bobm_kite9··on Risk-First Software Development
Hi,

Author here. Hope this is of some interest to people at Hacker News.

Feel free to AMA.

thanks, Rob

bobm_kite9··on Risk-First Software Development: The Menagerie
Hi,

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

bobm_kite9··on Confusing the Map with the Territory in Software Development
That could be the TL;DR, I guess.

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.

bobm_kite9··on Confusing the Map with the Territory in Software Development
Hi, author here.

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.

bobm_kite9··on It’s so cold in Chicago, crews had to set fire to commuter rail tracks
This is good though, right?

In the UK the points regularly freeze at even just a couple of degrees below zero, and the trains are just cancelled.

bobm_kite9··on JMAP: Like IMAP but Not Really
Loved this bit:

> Internet: Do you think JMAP will really take off?

> Me: JMAP is an open, smart, modern, and powerful E-mail protocol, so probably not.

← PreviousPage 3 of 5Next →