When "consequentialism" meets a post-90s programmer

Is "consequentialism" right in software development management in IT companies? 

Consequentialism, especially only short-term externally visible (customer-visible) "results", is a lazy management strategy for leaders who are completely technically uninitiated.

A post-90s programmer implemented statistical functions like this:

He wrote a class CountPlaceDistrict to get the total number of statistics:

CountPlaceDistrict countPlaceDistrict = new CountPlaceDistrict(i+1, placeId,
sysCompany.getStr("comp_name"),
1, getStaffsByCompId(sysCompanys).size(),
getDailyCheckByCompList(sysCompanys).size(),getPlacesPunByCompList(sysCompanys).size(),getStaffsP(sysCompanys).size(),
getCaseInfoByCompList(sysCompanys).size(), getSuspiciousInfoByCompList(sysCompanys).size(),
getBusinessJournalByCompList(sysCompanys).size(), getSecurityPatrolLogByCompList(sysCompanys).size(),
getAlarmPersonByCompList(sysCompanys).size());

And the getStaffsByCompId, getBusinessJournalByCompList and other functions are like this:

/**
 * Get the number of employees in this jurisdiction based on the unit list
 *
 * @param sysCompanyList
 * @return
 */
 public List<Staffs> getStaffsByCompId (List<SysCompany> sysCompanyList) {
    List<Staffs> staffsList = new ArrayList<Staffs>();
    for (SysCompany sysCompany : sysCompanyList) {
        List<Staffs> staffs = Staffs.dao.getStaffs(sysCompany.getStr("comp_id"));
        for (Staffs s : staffs) {
            staffsList.add(s);
}
    }
    return staffsList;
}

That is, he first reads out all the practitioners, puts them all in the List, and then obtains the size() of the List to realize the statistical function...

The insider already knows where the problem with his implementation method is when he sees it here...

If the system is actually applied and the number of practitioners is large, especially the number of business logs ( getBusinessJournalByCompList ) is likely to be large, his writing method may have a serious performance overhead problem.

Then, because the bosses who do not understand technology are keen to hold weekly meetings and talk about the progress every week, the above method of writing seems to be able to obtain correct statistical results outside the current internal development stage, so the post-90s programmer's above mentioned The writing method is defaulted... If others want the post-90s programmer to correct it now, the post-90s programmer still has a lot of opinions, and thinks that others overthrow the fruits of his labor, which makes others seem to have more troubles Same..... 

This is an intuitive example of the evils of "consequentialism"...

Note: I have no prejudice or opinion on post-90s programmers, but this programmer happens to be post-90s, so it is just called "a post-90s programmer"