3 ms·
A good recent example of that. We were asking a dev team to build a dashboard (we are a bank) showing capital ratios. The team came back saying voila! We looked
by cm2187 8y ago
A good recent example of that. We were asking a dev team to build a dashboard (we are a bank) showing capital ratios. The team came back saying voila! We looked at it, and the headline number in bold at the centre of the dashboard was showing a cet1 ratio of 1300% (a cet1 ratio is typically in the 5%-20% range). I am sure they used modern programming techniques, but they left an error that would have shocked even the least sophisticated user.
I have many similar annecdotes. Having a good understanding of the underlying domain and what numbers to expect is critical to writing correct models and too often I see dev teams in banks that have no understanding or curiosity of what they work on.
- antpls 8y agoOn the other hand, a dashboard is probably one of the most boring stuff to work on when you have a CS degree. Typically, a dashboard is asked as a deliverable to keep the dev team busy while also making sure other people's jobs in the bank arent rendered obsolete if the dev team were used to its full potential. The people saying Devs dont do enough effort to understand the domain are the same people who try to keep the "domain" overly complicated to justify their jobs/positions
- angry_octet 8y agoYou're right, a dashboard is a project for when you don't know if they can do anything useful. I think the fault is actually the split between IT (a support function) and the product group, which often doesn't have/isn't allowed embedded devs. IT managers are often toxic for delivering, never take ownership, SLA bullshit, too much PRINCE2 and ITIL. If you can get developers embedded, huge wins are possible. But they have to bring the client with them, not code away in isolation.
- nerdponx 8y agoThat's because a dashboard is easy (boring) if you code it up right. Whereas in Excel it's wizardry.
- jrumbut 8y agoThis is such a common pathology it does cast doubt on the entire field of software development but I would like to note it's been pretty commonly spread and now many years old best practice to have real users in constant communication and perhaps colocated with developers. This is a very predictable outcome when a requirements doc is tossed over the wall followed by patient waiting for the output. Again, it happens all the time so maybe this advice isn't enough or practical or something, but there is a well recognized solution and I would wonder whether it was done in this project.