4 ms·

DX works great if you have a new project in a new org. But as a contractor, there are many times I have to work in orgs that are 4-5 years old that have been th

DX works great if you have a new project in a new org. But as a contractor, there are many times I have to work in orgs that are 4-5 years old that have been through tons of admins and devs. I can't exactly convert an old org instantly to a dx project. Plus, as a contractor I'm not generally paid to convert their meta data. They want new features or bug fixes. They don't give a flying duck if their org is dx or how their code is organized.

chance_state 7y ago
> They don't give a flying duck if their org is dx or how their code is organized. I understand this 100%. I often end up using ForceCode (https://github.com/celador/ForceCode https://github.com/celador/ForceCode) for the get-in-get-out projects.
teh_klev 7y ago
>But as a contractor, there are many times I have to work in orgs that are 4-5 years old I'm a contractor as well. You know, there's a ton of legacy shite out there that isn't greenfield and you just need to get in there and guddle (Scottish word) about to earn the bucks. Sure I'd love to work all day long with .NET Core (or even .NET 4.7), but I also need to maintain a bunch of crap that dates back to 2006 and written in .NET 2.0. But as a contractor I kinda get on with it. It pays for my hobbies (model railways and building analogue synths, growing chillis and other stuff), so I kinda just suck it up because the rates are pretty ok. And you know, there's no shame in being a maintenance dev, some of the best devs I've met are looking after ancient crap long after the overpaid, unsupervised "superheros" that dug those holes moved on to their next 1000% glory roles, and we have to mop up afterwards (for a tidy hourly rate).