Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Saturday May 04 2019, @04:34PM   Printer-friendly
from the Business dept.

For the digital enterprise making use of the best-in-breed applications is non-negotiable, and the number they are relying on is increasing. Workforces on average rely on 162 applications to stay productive, according to cloud identity and access management platform Okta's recent "Businesses @ Work" report. This is a departure from the traditional enterprise approach of stack simplicity; purchasing one integrated system from a big vendor like Microsoft, Oracle or SAP.

[...] To discuss the changing landscape, senior leaders from three of the most successful enterprise applications – communications platform Slack, cloud content management platform Box, and Okta itself – hosted a breakfast roundtable. They cautioned that while increased application volumes are improving enterprise productivity, they are also bringing fresh complexities.

[Source: https://techerati.com/features-hub/opinions/how-can-enterprises-avoid-app-overflow]


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by bzipitidoo on Saturday May 04 2019, @06:57PM (1 child)

    by bzipitidoo (4388) on Saturday May 04 2019, @06:57PM (#838925) Journal

    Well, yeah. These days, what kind of stack does it take to do serious software development? An editor, a compiler, and a reference manual alone doesn't cut it. Need version control (git is king of that these days), issue tracking (bugzilla), Agile management (various tools, often web based), build tools (make), continuous integration (cruise control) with automated testing.

    I actually do not find debuggers essential. Useful, but the venerable print statement style of debugging works for me. The problem is, might be working with huge amounts of data, and it can be a pain to zero in on a special case with a classic debugger. It's easier to add the conditions to the program, and call a function to display the data in the most readable manner possible, which might be graphical.

    Then there's tools such as doxygen, valgrind, various profilers, virtual machines, and keyboard and mouse inputters and loggers.

    If the program is a heavy graphical application such as a high end game, might have a whole department of artists banging out sprites and icons and the like with Photoshop or GIMP, or if its a big data app, may have a whole department of DBMs managing a dozen different databases.

    So, yeah, how many tools did I mention? Even a seemingly simple tool such as ls shouldn't be overlooked. When coding in a compiled language such as C++, I do use that fairly often tell if the binary is up to date with the source. Have on rare occasions used ar and nm to check libraries

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 1) by Ethanol-fueled on Sunday May 05 2019, @04:50AM

    by Ethanol-fueled (2792) on Sunday May 05 2019, @04:50AM (#839101) Homepage

    high end game...sprites

    Nigga wut. This ain't 1988.