SoylentNews is people
SoylentNews
Nikita Prokopov has written a blog post detailing disenchantment with current software development. He has been writing software for 15 years and now regards the industry’s growing lack of care for efficiency, simplicity, and excellence as a problem to be solved. He addresses the following points one by one:
- Everything is unbearably slow
- Everything is too large
- Bitrot
- Half-baked products get shipped
- The same old problems recur again and again
- Most code has grown too complex to refactor
- Business is uninterested in improvement
This discussion has been archived.
No new comments can be posted.
On Disenchantment with the Current State of Software Development
|
Log In/Create an Account
| Top
| 99 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
If life gives you lemons, make lemonade.
(Score: 2, Funny) by Anonymous Coward on Thursday October 04 2018, @02:10AM
Been there, seen that.
$job had a project where they were migrating data from 'legacy' data storage system into 'new improved shiny thing' storage system that was, at this point, also an untested storage system (this last bit is important). Migration was occurring by reading from 'legacy' system, over a network connection, and writing to 'shiny new system' over a network connection.
Dev's had not even considered the possibility that untested shiny new thing might just accept data writes, reply with "success" response, but not actually store the data that was sent to be stored. Additional fact, a prior 'shiny new, but different, storage system' failed for just this reason. Writes were indicated as "successful" but attempting to retrieve written data later resulted in failure from prior 'shiny new system' for some substantial portion of reads.
So, I asked that they add a test of data written to verify it was in fact stored successfully by reading the newly stored data back out from 'shiny new' and comparing it to the original that was still stored in 'legacy system'.
I learned a few days later that the dev's had been looking for a prebuilt "compare" library to accomplish this ask instead of simply coding a simple compare loop.