Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
You are right
I was thinking more on the feature stuff... And analytics probably...
Like, does our new ui work for the customers?
Is the search performant? Do we have to give in more data for a more accurate search, what has it to get or to deliver to raise the performance
What is actually bought? Does the paper trail deliver all needed data in a reasonable time
How about fallout security?
Backups? Restore procedures?
The whole monty
For higher grade software development it should be mandatory to understand the big picture of problems...
If you are working for a online shop, you might want to ask marketing, what they want to sell, before they do it
You might want to ask billing, what customers buy, before you spend time on unnecessary features
You want to ask billing and legals, how they do fraud detection and you want to get the it security fellows on board too.
If marketing and billing knows, that maintenance needs time and money, they can calculate with that. If security knows, that some fails will be catched, no matter if you fix it in software or not they can adapt their priorities.
You might want to know something about process optimisation... Factories of car parts have spent years on such problems - learn from them.
rant
wk92