6 comments

2

"By combining up front analysis and design of application architectures with rapid feedback on defects during short, iterative coding sprints, hybrid methods produce higher structural quality than Agile or Waterfall methods alone," according to CAST.

Yep AGILE creates crappy code. I told you so.

1

Working at a bank right now. People really underestimate how complex the development process is, because the clients don't actually know what they want (and this is somewhat fine, because what they want is quite complicated usually.) It's a non trivial management task of avoiding scope creep, finalizing requirements, working through the inevitable tech-debt, etc etc. I'm not saying things can't be done better, but simply that things are not complicated without a reason

1

Devs who don't give a shit and just bash out crappy code don't give a shit about it. News at 12.

1

Making everything insecure. Product managers don't give a shit about quality code. Writing quality code therefore does not get most programmers more money. So why do it?

0

https://archive.is/FdSZE | https://vgy.me/wJSHCv.png :

Devs bashing out crappy code is making banks insecure – report • The Register

'The software quality of financial applications is worse than that of those in telecoms and retail, according to the report. '

'Geographically, the UK scores the lowest out of all regions. '

'Previously CAST found that applications in the UK financial services sector had huge amounts of legacy code, making it prone to major outages. '

'"Despite the push to ‘go digital’ our CRASH Report findings indicate there is a significant amount of bad code lingering in enterprise systems. '

'"Lack of security architecture combined with porous code in legacy systems produce easy targets for hackers. '

This has been an automated message.