- Leadership in Tech
- Posts
- Dealing with creaky legacy platforms
Dealing with creaky legacy platforms
Organizations that are constrained by creaky platforms are often slow
Dealing with creaky legacy platforms
19 minutes by Jonny Leroy
IT assets are relatively long-lived largely because modernization often represents a significant investment that doesn’t deliver new business value in a form that is very visible to managers or customers. Therefore organizations put off that investment until the case for change becomes overwhelming.
Launch Frictionless CSV Importing with OneSchema
sponsored by OneSchema
OneSchema is a ready-made CSV importer for developers that automatically corrects customer data. (Also: edge case handling, intuitive UI, bulk editing). Engineering teams use OneSchema to save months of development time building a CSV importer. With a large library of prebuilt validations and robust SDKs, OneSchema only takes 30 minutes to get running in your app. Solve CSV import with OneSchema.
The Review Is the Action Item
6 minutes by Fred Hebert
Incident reviews can be productive enough to be considered an action item on their own, if you have the right perspective and can avoid a few traps.
Inbox ten
8 minutes by Andrew Bosworth
Your ability to be effective is a function of your ability to efficiently ingest the information around you. Without this you have no chance of synthesizing something valuable. And this is why you end up plugged into vast communication networks of email, messages, slacks, chats, posts, video calls, all-hands, meetings, and any number of other channels.
Communication Structures
4 minutes by Kevin Yien
Every company has, or develops, a hierarchical reporting structure over time. It's normal. A common mistake I see is allowing the communication structure to mirror the reporting structure.
Will Larson, a veteran engineering leader and the CTO at Carta, holds three conventional engineering management “anti-patterns” up to the light for a closer look.
how did you like this issue? |