[bdfh42]

Somebody near you might be saying; "Co-founder keeps droning on about development buzzwords while I am still trying to bang out a minimum viable product. Time for structure when we have our first hire."

The truth might be somewhere in between but worrying about bloated code while at an early stage must just be counter-productive. You might find something to add rather than something to maintain.

[boggled]

Sure, I'm just as capable of seeing things from another point of view as anyone [perhaps this is the voice of Dunning-Kruger]. I have to say that this perspective is limiting and is exacerbated by my co-founder's somewhat desperate financial straits. I have been adding features--the best I can do is revise code as I go.

The point about development buzzwords is well taken--I use them with some misgivings. I would like my co-founder to educate himself on some of them, however, instead of barking. Software development has advanced in the last 30 years.

My "droning" is confined to a question here. I don't believe I deserve angry, aggressive and peremptory behavior from an excitable person who seems to have anger management issues and delusions of grandeur about an app. What he does have is drive.

However, I find that adding features requires considerably more work than it would have been otherwise. It was a struggle to advance over every little point: use non-UI tasks for network operations lest you get an exception, etc. Also, I'm in the position of having to do merges since he refuses to use version control. Anyway it is a problem to work with one's hands tied--it takes me somewhat less work for me to implement features than my cofounder, even in the face of impediments that I find unnecessary impediments that would be straightforward enough to rectify--if only I could. This tends to perpetuate unfortunate practices.