maintaining

Our team has three primary responsibilities: 1) Supporting and maintaining existing code for building and applying predictive models.

But the whole idea was to not simply strip but to strip while maintaining all the old functionality.

It is the cold hard weight of experience building and maintaining large codebases for years in various languages.

This allows maintaining a clear separation between your local names and the imported names, you have full control over what names in your local namespace are touched when a module is imported.

Just shows that we can push for advanced features while maintaining compatibility for the simplest experiences.

If you were responsible for shipping and maintaining the product for a few years, we really want to talk to you.

This means working with them to really understand what they need built, carefully planning how to do it, and delivering what we promise while maintaining a sensible work/life balance.

I would argue maintaining control was no longer possible since the invention of magnetic tape.

Tasks will include developing, integrating, and maintaining software modules for new instruments, as well as understanding the existing codebase to enable efficient support of existing instruments.

Unfortunately, maintaining the watercolor (even with the tiles) as we changed the campus (e.g.

If I have a greenfield, I'll probably do it in tcl/tk or python/wx but I'm stick maintaining old win32 and winforms stuff for people.

At that point, maintaining efficiency becomes impossible.

In reality there are many "-10x developers" which may increase the costs for maintaining the software, or cause a lot of performance problems with the results of their work.

I'm sure I can agree that Java, C#, Python, or Javascript are any better than Ruby in terms of difficulty of installing and maintaining the "right" version on your system, or in terms of quirks that are not present in other languages.

Maintaining hierarchy requires inertia and increased transaction costs.