- There will always be something to complain about
- There will always be something you still have to clean up
- There will always be things on your todo list
- There will always be things you forget
- There will always be things you learn
- There will always be books you still want to read
- There will always be the hope of things improving in the future
“I’m a software developer, but I’m very bad at estimating a task’s workload. What can I do to improve on that?”Posted: August 26, 2018
There are a couple of things that you might try, at different points in the process of developing software, or any complex activity come to that:
It is possibly (likely even) that you are not breaking your task down into subtasks. Eg if you have to add a new text field to a screen, you might be saying ‘oh, maybe a couple of hours’ to yourself when estimating. However, if you start to break it down you might end up with a list a bit like this:
- Modify database to add new field -1h
- Modify stored procedure to get new field from DB – 1h
- Modify stored procedure to set new field in DB – 1h
- Update repository code to retrieve new field from 2 above – 1h
- Update repository code to provide new field to 2 above – 1h
- Modify business objects to support new field – 2h
- Modify view code to display new field from business object – 1h:30
- Modify controller to update business object from view code – 1h.
So immediately you can start to see that your couple of hours is looking a bit tight, and you have not even added any tasks for the stuff you need like testing, code reviews, review with the business analyst etc.
And what about all of the stuff that we do as developers that does not contribute to the codebase directly?
- Updating the task in task management system
- Creating code branches
- Merging changes
- Running remote builds
- Regression testing
When you have a breakdown into sub-tasks like the above, you can start to record a narrative against the sub-tasks to record how long each took, especially stuff that you had not planned to have to do. Eg “table definition is in repository xxxx, took 45 minutes to track it down, 15 minutes to review with tech lead”.
When you have done a few tasks with a decent task breakdown as above you can start to get a feel for how long things take. Eg you might discover that changing a stored procedure takes a couple of hours to do the work but that typically another hour is spent on non-functional stuff like finding it in the source code base, reviewing it to understand how it works, cross-checking tables etc. All of this takes time and should be used to feed back into your estimates next time.
Finally you can take your detailed tasks narrative to see where you are actually spending time and how much. You can then use that to influence your subsequent estimates.
An important part of my next project involves letting people indicate whereabouts they are, but without disclosing detailed location information until later. In the UK, we have Post codes which are alphanumeric codes between five and eight characters long which broadly identify roughly where a building is. They are composed of two parts, the outward code and the inward code separated by a single space.Examples: IV51 9XB or SE22 8BS.
There are about 3000 outward codes, and while many cover a fairly small area especially in cities, others like IV51 cover several hundred square miles. Generally they are good enough for my purpose, and where the outward code isn’t specific enough I will use the first part of the inward code as well.
My plan is to use the postcode information here http://www.freemaptools.com/download-uk-postcode-lat-lng.htm to identify the centre of each outward code and use that as a proxy for wherever the user is located. From that I can calculate a rough distance to other users. Where two users share an outward code, I can identify that fact and report it to the user doing the search.
Next time: Importing the data into MongoDB.
I guess writing a blog post about traffic or planning, (or traffic and planning even!), could mark the descent into middle-aged senescence, but the state of planning by North Yorkshire County Council’s roads department is deserving of a blog rant.
Here in Harrogate, they have been responsible for the design of a new road junction, here: https://goo.gl/maps/KrJqn.
The two lane turn right at Hookstone Rd onto the A61 Northbound is a prime example of a bad and probably dangerous junction. Turning south from Leadhall Lane feels scary even in large car as it is impossible to determine if it is safe to make the turn, so instead you hold back which results in all the traffic leaving Leadhall Lane being blocked. Why NYCC decided to deviate from the usual pattern of having a right-turn lane and a straight-on-or-left lane is not something I can determine. I suspect that the first serious accident at this junction will result in NYCC being on the receiving end of a court case when the defence argues that it is the junction at fault rather than a driver.
In the past couple of weeks I have twice seen people heading north on the A61 stopping because they are confused by the red light that controls the turn-right traffic. Most days there is one car stranded ahead of the stop line in the turn-right lane. Once, there were two, preventing east-west traffic.
The left turn into Leadhall Lane is difficult for the school buses going to Rossett and Asheville – I’ve seen one have to reverse back, blocking both lanes as it attempts the corner. This is lamentably bad and even a few brief consultation with bus companies would have shown how poorly laid out the entire thing is.
Update: Car drivers coming from Hookstone Road are starting to use the turn-left only lane as a straight-ahead lane. Illegal but predicable.
In no particular order
* I’m not maintaining a web site on http://www.hyperoceanic.com at the moment.
* All the Groove related stuff should be considered to be of historical value only
* I got a new job at the British Library, leading an Agile team that builds the systems that import the digital media (eJournals, eBooks, web archives etc) into the Digital Library System. C#, SQL Server, MSMQ being the chief skills.
Son #1 and I went to this event a couple of weeks ago.
Just found this report from The Royal Society: Shut down or restart? The way forward for computing in UK schools. Looks relevant.