3 ms·
Read the link. Companies that develop their own idiosyncratic dev systems are generally making a mistake. Developers who endeavor to master those systems are u
by ubermonkey 7y ago
Read the link.
Companies that develop their own idiosyncratic dev systems are generally making a mistake. Developers who endeavor to master those systems are using energy and time to add a skill to their resume that has zero value on the open market, which is a bad career move.
- Rochus 7y agoI read it. The article is superficial and one-sided. And there is nothing wrong with companies building their own tools. There are many such companies, including SAP, Microsoft and Google.
- jacquesm 7y agoMost companies are not SAP, Microsoft or Google, and would do well to stay miles away from developing their own tools. Because the tools that you develop then become the millstone around your neck in the longer term. Unless a tool gives you a major advantage you should never go near that. Your competitors will all happily use COTS, drop projects and adapt new tech while you will be stuck in the hole with your sunk cost and impossible to migrate toolchain. That sort of situation has sunk more than one company.
- ubermonkey 7y agoAND more than one career, too. Folks who invest their careers in single-company toolchains tend not to have very remunerative or rewarding careers. It creates a monstrous imbalance between employer and employee, too -- all the "lifers" who stayed at TCK were being paid well below market, but couldn't command better elsewhere because their whole professional life had been spent on single-site tools. That's MUMPS for you.
- jacquesm 7y agoThat's an excellent point. Working on a single company toolchain when that company isn't a household name is a career dead end.
- ubermonkey 7y ago....which is the whole point of the MUMPS link to DWTF, so it's weird that the other guy is dug on on an alternate interpretation.