A developer's peers will generally know whether they provide good value or not. When preparing to do a performance review of a developer, ask for feedback about that developer from other developers on the team (and other co-workers they interact with on other teams).
Reply to This
Duh, sorry. Posted to the wrong story.
A developer's peers will generally know whether they provide good value or not. When preparing to do a performance review of a developer, ask for feedback about that developer from other developers on the team (and other co-workers they interact with on other teams).
Some corporations aspire to higher levels of decency.
B Corps are for-profit companies certified by the nonprofit B Lab to meet rigorous standards of social and environmental performance,
accountability, and transparency.
The company I work for (as a software developer) is a B Corp.
You can find out more at https://www.bcorporation.net/what-are-b-corps
"Transplantation" sounds like a Bushism to me. "Transplant" is already a noun, thank you very much.
It's all fine until you start modifying triggers and templates. First there's the evil, kludgey combination of bad perl and bad Mason which you have to write overlays to, then once you've done this, you can't upgrade! If you upgrade, all of your overlays break. So you end up stuck with an out of date version with patch on top of patch.
Yes. If you make customizations, then you need to maintain them and update your patches to the current version.
This issue is not specific to RT. It is a fundamental issue of software development and revision control, and will affect you any time you make local customizations to software.
Perhaps you think it would be (easier|cheaper|Soviet America) if you had some shrink-wrapped proprietary software which you couldn't customize?
"Most of us, when all is said and done, like what we like and make up reasons for it afterwards." -- Soren F. Petersen
