3 ms·
1) Thanks for the clarification. The problem we ran into at IMVU was that the original product (an instant messenger add-on) had concepts that no longer applie
by chadaustin 16y ago
1) Thanks for the clarification. The problem we ran into at IMVU was that the original product (an instant messenger add-on) had concepts that no longer applied once our product pivoted a few times. These stale concepts hung around and prevented us from making changes to our core product. A 3D scene viewer consisted of at least 5 classes: SessionWindow, PresenceWindow, AvatarWindow, CustomWindowHelper, and RenderedWindow. Now the scene viewer is one class... SceneViewer! I'm a strong believer that mapping your code to customer-visible product elements is high-ROI.
2) Regarding ownership culture - that's exactly what I meant. If code is clean, anyone is comfortable touching it. If it's dirty, people start going directly to its author. Clean code is an organizational lubricant.