News for hackers. Stuff that matters.
Re:Applying programming language research ideas to transform... by antpls on Sunday January 20, 2019 @03:41AM (#18951966)
On 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

Re:Applying programming language research ideas to transform... by angry_octet on Sunday January 20, 2019 @09:11AM (#18953102)
You'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.

Re:Applying programming language research ideas to transform... by nerdponx on Sunday January 20, 2019 @10:24AM (#18953423)
That's because a dashboard is easy (boring) if you code it up right. Whereas in Excel it's wizardry.