Most company IT systems are stratas of technology built on top of one another, much of it dangerously out of date if not outright obsoleteView in browser »
The New Stack Update

ISSUE #291: When 'Legacy' Means Everything in Production

Talk Talk Talk

"[O]ur objective is to create not just a language to specifically program computers, but a language to represent everything — including real things in the world — in computational terms." 

Stephen Wolfram on the creation of his mathematical programming language Mathematica.
What's Happening

Trickle-Down Technology

Here at The New Stack, we focus on cutting, if not actual bleeding, edge 
technologies. We hang on the ascending side of the Gartner Hype Curve, with all the other cool kids, obvs. 

So we sometimes forget that not all organizations can freely adopt all the shiny new toys whose possibilities we extoll. Most company IT systems are stratas of technology built on top of one another, much of it already dangerously out of date if not outright obsolete. Even the newer stuff is old in our industry. As VMware’s Mandy Stor pointed out in a recent TNS livecast, "When we talk about 'legacy,' really what we're really talking about is everything that is in production."

This point was emphasized again recently on Twitter, by Jean Yang, who is the founder and CEO of Akita Software. As someone who has met with hundreds, if not thousands of software developers, Yang noted that “there's a HUGE gap between what developer-influencers are writing about, versus the daily reality of most developers.” In other words, the trade pubs, such as TNS, don’t typically cover all the day-to-day issues developers have to deal with as they keep all the old bits running.

Adapting the new can be difficult, especially the open source software. A lot of the open source technologies that we write about come from the web-scale behemoths, such as Facebook (React), Netflix (Spinnaker), and Google (Kubernetes). 

Some of this technology will make it into everyday use, some will not.
“The solutions that engineers at a Netflix or LinkedIn or Facebook come up with aren't for the vast majority of software shops: they're often best for big companies that can afford to set a high engineering bar, that can afford large infrastructure teams and ops teams,” Yang writes.

Amazon Web Services Principal Engineer Jaana Dogan affirmed these points in her own illuminating Tweet thread. She has worked on both cutting edge web-scale technology and for the big cloud providers that serve the enterprise. And the difference between the two is telling, she writes. The big edgy tech companies can have their engineers feeling like they “are only bounded by the speed of the light,” whereas the cloud providers have to work backwards to meet customer bases, usually situated somewhere in legacy-land.  

“It's sometimes a challenge to balance to keep inventing and ensure what we invent is not alienating the industry,” she writes.

Contrast Security Adds Serverless Security for AWS Lambda

Contrast Security has expanded its Contrast Application Security Platform to support serverless environments, starting with AWS Lambda. Th Contrast ServerlessApplication Security platform will test serverless functions to find possible security vulnerabilities.

Do You Need an Internal Developer Platform?

Are internal developer platforms the answer to full-stack complexity? Asking 
yourself these six questions can help your organization determine whether creating a self-service platform for its developers makes sense.

Why Your Code Needs Abstraction Layers

Abstraction is one of the most important aspects of writing well-designed software. This contributed post from Coralogix developer Yair Cohen offers a system to follow and a clear mental model on how to create good abstractions.

What the Future of Cloud Native Is About to Bring

In this latest episode of The New Stack Makers podcast, Chris Aniszczyk, the Cloud Native Computing Foundation’s chief technology officer, discusses what’s hot in cloud native land and offers a glimpse of what’s emerging.

Add It Up
Not all employers should be scared in this job market, just those that usually blame the data engineering team when things go wrong with the company's data and analytics. Only 26% of 600 people with data engineer and related titles are very likely to leave their current company for another data engineering job in the next 12 months, based on a survey conducted on behalf of and DataKitchen and Data Engineer in August. Unsurprisingly, when data engineering is always blamed for the Data/Analytics problems, then 65% are very likely to leave.

Party On
BMC's Katie Carty Tierney

BMC's Katie Carty Tierney said during BMC Exchange that customers see "a huge workforce gap right now with open positions and no one to fill them. But second, we also have an issue where we don't have the right skills."

BMC President and CEO Ayman Sayed

BMC President and CEO Ayman Sayed said during BMC Exchange that "agility and resiliency come from knowing how, when and what to do— and in some cases, what not to do." 

On The Road
Why DevOps Isn't 100% Working for Most Teams
NOVEMBER 10, 2021 // VIRTUAL @ 8:15 AM PT
TNS Virtual Pancake & Podcast at Trajectory!
Come have a short stack with The New Stack and LaunchDarkly as we discuss how and why DevOps teams are turning to self-service developer platforms and how they’re achieving faster application deployment in the cloud. Register now!
Copyright © 2021 The New Stack, All rights reserved.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list

Email Marketing Powered by Mailchimp