Xtr3m3hodl @Xtr3m3hodl - 6d
I don't know if it's just me but I dislike having to come up with a comprehensive plan of what I need to build before build it. I would end up getting tired and loosing interest completely unlike just jumping on the problem and going with the flow, backtracking when new information comes up to ensure things are done well and actually testing hypothesis on the fly. It sounds counterintuitive to how most software engineering processes work but it hasn't failed me yet for the 15+ years building software. Anyone else experience this #asknostr
Even when working with others, and especially on existing projects, that's how I mostly work. I'm still familiar with all the obvious software development practices. It is just, I don't dwell too much on a written well thought out plan (things change more often). The way I see it, the "plan" is being developed mentally as I attempt to solve the problem
