Evolutionary Insights: E. Coli and the Challenge of Mirror Bacteria

of writing some sort of document to mix ure i kind of understand what the problem is. Icayou guess, in the beginning, beginning, when some one brings something for me to build, i ask a lot of questions and make sure that it's like, well, are you actually asking me for the thing you want, or you asking me to build the thing you think you need? That's usually where i start. Whenever it's a kind of, actually doesn't mater, doesn't mater, if it's a product person, or if it'something in building for myself, i say like, mi, is the premise that i have assumed here, or someone else has assumed the correct one. And once i kind of figure that out, i'll start with writing up a design dock or a scope do communicate, this is what we're going to build. And then i usually jump into some prototyping. And that's where i start actually, like, throwing some code into a code base. Then, like, the project usually gets legs from there, and we kind of e know if it's something for work. We develop out that design dock more we start having discussions than we actually make the four real code base, which might, unfortunately, be taking that prototype code i built, or it might be starting from fresh, which is, dely a preferable thing tos. Prototype code is never really written as well as we'd like it to be. That's usually like the the on ramp that i take. But that's really a lot. Because i'm a writer, so my comfort zone is like an empty document in google doxes or an empty vim window where i can just start typing out, o what is it that i'm trying to do? Blank

Episode 59: The apocalypse

The Studies Show

Remember Everything You Learn from Podcasts