Software development is sometimes chaotic, but I'm excited that the things we build are ambitious, even if they operate in a world of uncertainty.
Estimates are first and foremost for project planning. Eventually, as various team members get familiar with the codebase, disparities should fade away.
You've made a big investment in creating a custom software package, and you want it to last for years to come. That means software project maintenance.
Experimenting and making mistakes is a great learning experience. Just make sure to check that you're solving the right problem or using the right tools.
The web projects I’ve been building are the best they’ve ever been. Incredibly, we can take for granted the development tools that make this possible.
I’d like to share how I dug into some unfamiliar code to find some direction so you can see how I approach this sort of problem.