Tag: planning

  • Forever change

    Let’s start with a few updates about the blogs. I’m going to be busier in the coming weeks so, for now, posts will only be once a week. It might be possible to go back to twice a week once things have settled down. We’ll have to see. If you’ve been reading from the start…

  • Learning from… jigsaws

    Since starting this blog it has made me think about regular activities and wonder if they can teach me any lessons for writing better software. In the last couple of years jigsaws have gone from not on being my radar to a fairly regular thing. I often pick colourful, geometric or architectural one. Although there’s…

  • Time complexity

    If you’ve had a university education in software engineering you have probably come across algorithmic time complexity. This classifies algorithms by how long they take to run given an known amount of input, normally written using big O notation. Picking an algorithm with a good time complexity can make an enormous difference to the performance…

  • The taste test

    Imagine you’ve just been given a new cookbook. It has a recipe for Oysters Rockefeller that a friend recommended. Really it could be anything but oysters have been in my media for the last week so we’ll go with them. You buy the ingredients, prepare them carefully, cook and serve. It looks great, you take…

  • Searching for design

    This Problem Changes Your Perspective On Game Dev looks at game design as though it’s a search algorithm touching on: Jonas Tyroller talks quickly and makes an argument for discovery rather than one off design. While I’m interested in game design are there lessons to be learned beyond that? Is game dev different? Jonas is…

  • Retrospective 1-26

    One of my original goals with this blog was to manage 26 posts in 6 months. Here I am in 3 months. Well done me. This one is both a retrospective of that achievement and my thoughts about retrospectives themselves. I think they’re a good idea but… I’m not entirely sure they work. Retrospectives Maybe…

  • Less can be more

    I was listening to the podcast series Cautionary Tales and their episode Do nothing, Then Do Less. By all means listen to the whole thing but I’d like to highlight the crossover with The Happiness Lab starting 12 minutes 30 in. Bias for adding People are apparently biased towards adding things in order to solve…

  • How to manage a backlog?

    One of my friends had an issue with assumption that tasks rise towards the top of the backlog in a previous post. That is an assumption from working on Jira with a particular team and isn’t how backlog or tasks lists always work. Working with a prioritised backlog It’s very frustrating when you ask which…

  • Time estimation is hard

    In my experience estimating how long a software engineering task will be is hard. I think this is often the case with software engineering tasks in a way that it isn’t for other disciplines. More design than assembly A quick internet search suggests a beginning bricklayer might lay 250 bricks per day, an intermediate 450…