Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> “Why are we over-complicating this?” is a very easy thing to say after being introduced to a project. What’s hard is to reserve judgement until you’ve educated yourself on the entire problem domain, and noted all the considerations that were made by previous developers.

I think that this is the "money quote."

I wrote something to that effect a while back[0].

I've been at this stuff for a long time. I have definitely done my share of overenginering, and overcomplicating, but it's my experience that a lot of that, comes from underestimating the complexity of the problem domain, during the design phase, and going "Lucy and the Chocolate Factory,"[1] after starting implementation (when things start to come out of the woodwork).

The more experienced that I get, the more likely I am, to predict some of the issues, before implementation, and I have learned to develop in a modular, flexible manner, that allows me to modify things, down the road.

Right now, I am in the middle of a fairly major refactoring of an app, that is in "chocolate meltdown" mode, because of all the addons.

Rewriting the server interactions is a big, risky task, but we aren't shipping (one reason I don't like the MVP model), so it's entirely possible to get it right before our first real users get their hands on it.

[0] https://littlegreenviper.com/miscellany/problems-and-solutio...

[1] https://www.youtube.com/watch?v=NkQ58I53mjk



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: