WuASM Episode 5 - "Feeling the Flow"

Captions as YouTube publishes them, usually machine-generated, so product and people names can be misheard.

1. 9:26

   he

2. 12:37

   hey good morning welcome to another edition of wake up and ship more I am your host Joe uh excited to be back uh with some new stuff all about uh building software uh entrepreneurship uh you know just the ins and outs of not just like actually coding some of the stuff that goes into it we're going to talk about all kinds of stuff uh on previous episodes we've been talking about MVPs app architecture things like that uh today we are talking

3. 13:08

   about so the title of the episode is feeling the flow uh we're talking about some flowcharts we're going to talk about just charting in general of in software preparation kind of what that means I'm going to talk a little bit about um some of my experience that I think has been really beneficial to How I build and and actually ship different software and so we're going to talk

4. 13:32

   about all kinds of stuff if you are not already uh I really encourage you to please make sure that uh you are following along with all of Dev hub's different socials uh this is now streaming in uh multiple places we are streaming live on YouTube on Twitch uh X Instagram is new today we started just uh actually live streaming on Instagram uh we also stream directly in the telegram group uh for this and uh I'll

5. 14:01

   put that here at the bottom so if you are watching this on replay if you are watching this at a different time if you downloaded and saved it for later uh you can join the telegram group at any time and ask questions there and be part of that conversation there and uh I hope that is hugely beneficial to people as well uh but we also we also stream this here as well so uh tons of places to

6. 14:25

   actually follow along uh if you you know have haven't already uh make sure you've actually already grabbed The Shard dog it's also the uh QR code in the top Corner uh this will just kind of get you into the group as we kind of continue to experiment with some different stuff uh as well and then lastly before I jump into stuff couple just other housekeeping things uh I'm going to bring it up here uh if you are not already signed up to the devhub

7. 14:57

   newsletter uh please please sign up to to that we just uh make sure actually that link is still the right one here cuz that's a uh I know we changed it for a little bit but uh devhub sign up yeah there we go okay yep perfect so if you go to that link you can sign up for our newsletter this is our newsletter about the developer ecosystem here on the near protocol um there's lots of different information you can get there if you go there if you've already signed up for the newsletter I encourage you to still go there because

8. 15:32

   there two new Fields they're completely optional and we just want to be able to to better get a sense of who our Builders are so is a place to put in your GitHub username that's it just want to know like your username to see uh what you're actually uh building and be able to connect with you on different topics there uh as well as if you are on near protocol and you want to share your wallet um again this helps us kind of

9. 15:55

   put all the pieces together uh but totally optional you do not have have to put that in but uh again it's just a way for us to better connect with the community and uh who's following along uh so that's that let's get into though some of the good stuff here around uh development and everything else so I'm going to bring uh couple things here on on onto the stage here so let's start with uh okay we're gonna here so today I'm talking about uh

10. 16:30

    charts and you can see in the little graphic and I'll make I'll make that bigger in a second here uh you know a basic chart flowcharts you probably seen and there's a lot of different again I'll say just similar to the stuff that we talking about like with the MVPs and everything else uh a lot of things are very opinionated you'll see different books you know even maybe like textbooks you might have been taught a particular

11. 16:55

    way um how to do certain things and especially like there are some very actually procedural based like flowcharts that are out there especially if you are doing software architecture there are some very clear like expectations sometimes especially in like large Enterprise environments of like what uh a flowchart looks like but I want to take the perspective though of the small Dev team the solo developer uh somebody who's maybe still new and learning whatever that might be and how

12. 17:27

    some basic flowcharting and just some basic charting can really actually help uh your overall building experience not just for like how you're able to get maybe things done and built faster but also like how you're able to actually uh conceptualize different processes and functions in your own mind okay uh and typically you're going to see here so if we're going to talk about like let's say you know if we're talking about flowcharts you know you think think of

13. 17:59

    the simple like I have a it goes to B right and then maybe B branches off into like right C and D kind of like basic stuff and that's part of it and and and we're going to act absolutely go through some of that but I also think it's important to kind of look at um what else can actually come of this from a standpoint of how do you talk to other developers how do you talk to your team members how do you you know talk to yourself and actually get a better sense

14. 18:33

    of like what uh you need to to do so let me me pull up just this chart here and I'm going to actually uh zoom in a little bit here so we can see this a little bit better okay so here is an example and these are everything I'm going to show today are actually things I've really actually used so these are not just like madeup examples I think and I'm doing this cuz I think is really relevant to show like actually you know how this is used in

15. 19:03

    the real world so this is an older one from a few years back in having a discussion actually about like you know how could we look at some data resources leading into an API that we were considering building on this small team and you know again this is really simple it's not really telling you much about the flow and that's not really what this is for like this was for clearly a

16. 19:26

    discussion with other team members not every team member is also technical sometimes especially if you're an entrepreneur if you're in a startup you're going to have some people on your team who are maybe less technical or not technical at all serving different roles you need to be able to have these discussions and sometimes something was visual is really helpful and so in this example here is you know this is not necessarily a flow chart because I'm not

17. 19:49

    showing the flow of the data per se but I'm showing like what actually goes into the API to populate it and like we're building out some custom stuff here of user data and interaction info and that's going to be tied into stuff like you know blockchain data collection data which is referring to like nft collection data and like the annotations that people are able to do all feeding into you know annotations meaning notes on something all this could feed into a

18. 20:19

    single API for the data set um and then it allows you I said okay this could come from block Eden I don't know if block Eden still exist I think it does um and you could do all that now the reason why this is relevant so when you're working on a distributed team one be able to show like all these different pieces in a very clear picture is sometimes better than actually writing it in a document not everybody can pick

19. 20:43

    up what you mean when you're writing something out uh it also shows exactly everything that's feeding into it and so when I am considering like what am I actually need to be aware of and how robust is this API how much work is going to go into this API I have to actually be ready to say oh okay there's a lot of different data s sets in here and when you see that right and you see like okay there's a lot of data sets in here that will then inform other

20. 21:16

    decisions I make later so let's let's go to let me go back to here for a second so when we talked about like app architecture and stuff like that being able to see something like all these different data sources it then lets me start to consider of like what do I need to actually be aware of for my app architecture how much like I need to now have based off of what I just show that example this is again this is just an example I need a

21. 21:48

    database um I probably need maybe something like a short-term storage so something maybe like a redus type of setup because I need something just maybe in memory so I'm not actually making full API calls to a third party while trying to call my own internal apis things like that uh you know and so now all of this stuff as well as like you know say third party right so now all of this stuff here is all leading

22. 22:19

    into you know my API and that's that's a a consideration I have to make right so that's one part part of that also here this helps like if I if we're not all at the same time zone we're we're meeting asynchronously um they can get a little better sense of again uh what I'm referring to when when I'm talking about Stu so that's one example so let me let me show you now another example

23. 22:50

    here and we we'll go from that to a full actual flow chart so share my screen okay so this um this example here is an actual flowchart and this is something that and here I'll I'll zoom in a little bit here too so we can see some a little bit better so for for my project Shard dog um I did a presentation once on what maybe could happen and how maybe Shard dog can address some voting processes

24. 23:34

    and making sure that uh we're able to do some screening around voting so this was not actually ever implemented this way this was just a a presentation this is an actual flowchart to show again the life cycle of uh the the user Journey essentially I guess right that's how kind of put it so this is where we're actually going through we're saying okay a user starts here at the green is going to go through some process um I like to use these

25. 24:06

    little like sticky note looking things as a way to add some notes because again A lot of times uh somebody is reading this asynchronously like they're reading this on their own they're so I'm not there to talk it through and so it gives me an opportunity to give some notes and I think this is like super powerful cuz they're just little notes but it it really helps put together a a bigger

26. 24:31

    picture of like what's actually really happening here because sometimes just like a little box of like oh like what is this surface here and like okay now we can explain that and then you know you have your logic of like okay does it you know yes no type of thing true false and based off of what's happening and again like having a little note here of what's a possibility uh what's something

27. 24:53

    to be considered you know things like that and then it goes through a whole flow and we talk about like okay you know okay here's a here's a new process here's a wallet login you know where is this getting logged it has to go someplace you can see there's no actual like architecture here there's no like reference to like what kind of database setup it is uh it's really just focused on flow it's focused on again the user experience the user Journey so why why

28. 25:24

    do we go through all of this well one is when you're building it helps helps you actually get a sense of you know what are the expectations that I have to go through so when I am planning out what I'm building I know that I need to have all these different steps here that's one part of it the other part of it too is that when I'm doing testing of what I built does it match the expectation of

29. 25:50

    what we wrote out in the flowchart and sometimes yeah that's going to to match up but maybe like you had to make a decision while building for something that just didn't make sense for whatever reason the tech technologically it was taking too much time it didn't work it was too hard whatever and then you can go back and you can compare that to your original expectations and then you can match things up hopefully and say okay

30. 26:14

    here's where we can fix or this still works or this still matches the expected outcome but if I hadn't planned ahead of time so let's just say I'm building a voter process and I hadn't planned this ahead of time I don't have this flowchart and something goes wrong or I shouldn't say wrong if something is not working the way I expected to while building I may come to a point where

31. 26:37

    like I'm now making different decisions here and I don't know if it still matches my outcome because I haven't actually mapped out the workflow and this is something that you can certainly do here as well unlik uh smaller parts so again when you're a solo Dev or on a small team it is definitely and I completely sympathize with it it's hard to do a lot of this work because you feel a constant pressure to build and you feel a

32. 27:12

    constant pressure to ship something and there is like oh it's just me building and so I need to actually have output and everything else that and again I think that is fine in a lot of cases especially early on like you're trying to get that mvp out like we talked about last week if you're trying to just experiment you're hacking around uh doing different things as soon as you

33. 27:36

    start to get to a point where you're actually trying to get a product in people's hands now again um there's a couple things here that we haven't totally talked about but uh are really relevant here I understand when you're a solo Dev or again small team it is sometimes a a it feels overwhelming to write too many stories if you're trying to follow like an Agile development process um and so maybe you kind of half ass your stories and you could probably get away with that okay you could probably get away

34. 28:10

    with like a punch list of things fine not a huge deal uh you can probably get away with you know also just you know minimizing your actual like unit test uh and things like that because you're going to actually be Hands-On testing a lot more and unit writing unit test takes a long time and again you're trying to hit Windows you're trying to ship stuff you're trying to get things out in people's hands totally get it um

35. 28:41

    understandably that you would maybe cut some things short there but I will say one area I always try to not cut short is something like this as these different flowcharts are even again like the chart I showed before of just laying out the different areas of like here's all the stuff that's flowing into my API here's all the data sources um and this this example here hey here's how this is all

36. 29:07

    going to work you know and again so that way I have at least something to compare this to and I have outcomes and what it's done for me this is like one of those like productivity hacks things but the Boost here is that it has forced me as both the developer and the entrepreneur and all these different hats you have to wear on a small team or as a solo Dev of have I thought through what my

37. 29:36

    product is actually supposed to do at different parts and again I'm not saying you have to write one of these out for every single part of your app it's helpful and I often will do it for most but you should at least do it for your main functionality and anything that is actually specialized you should absolutely do this for because again it's forcing you to have that thought process this is like this is one of

38. 30:03

    those like tricks where it's like yeah it it's maybe it's not even like useful to anyone else but yourself but it's worth putting in that work and that's a really important piece here maybe I show this to nobody else I'm a solo Dev no one else is going to see this but for me it lets me know that I have thought through the process here and I now know what's going on here so that's part of

39. 30:27

    it too let me show though another one here because there's a there's the other way you can go to which is more of like a diagramming method and let's see which one do I want to show here first okay this is I'm going to show one like feels like overwhelming on purpose here so on let me let me show this um here we go okay so this is is not necessarily A this is not I wouldn't say a flowchart but this is how all of maybe the components of an

40. 31:05

    app all link together um this one was for a project planning that I was doing a while back this is probably I don't know five six years ago or so um and you can see I actually color coded things specifically because I wanted to highlight some things that were happening so we were we were building this large project that involved a lot of different third party Services um had multiple data sources and actually needed to have some uh really some

41. 31:38

    custom stuff that was built out around all of this um and so it was really a fairly complicated uh piece of software from an architectural standpoint and so we wanted to highlight all of the features that were in there so this is more of a I would call this like a feature chart okay so it's not really a chart some of it flows you can see like things flow into to one or the other so like I'll here I'll I'll zoom in a bit here right so you can see over here on this side um

42. 32:08

    that you know this is a flowchart of how things would maybe work here and some of it though is just actually just Services connecting and so it varies if I zoom all the way out you can see the whole whole thing there now something like this so why is this important okay and why is this helpful because one of the things that can happen is you can start to have your app in your software like really start to balloon and become like

43. 32:43

    just full of features right like you you you just start get you get to a point where like all of a sudden my app is no longer just this app that is doing a and b it's not doing like A through Z right it's the whole thing I'm doing all this different stuff and sometimes you don't realize that so you start to plan it out and one of the things that was and I remember back that was really instructive around this here um when I wrote this out was like seeing

44. 33:15

    how many different Services had to be involved right so you know the purple here is third party Services okay and each one was actually for the most part I'm almost positive uh we're almost a different service each time so there's a couple duplicates in there for the most part that this a separate service each time so now as like we're planning things out and we're talking through things you say oh wait a second you know I have uh you know 10 to 12 different external

45. 33:47

    Services now I need to integrate in here that's a lot that's a lot especially if you are a small team even at a big team that's a lot there's a lot of dependencies that you're now having inside your app right so that's stuff that's really I think uh important to be aware of this also was super instructive too because it let let us know like okay where are all the different custom

46. 34:11

    pieces that are being fit in so you can see everything that's kind of like this like Peach kind of color like so this was part of stuff that was happening in a mobile app so you need to make sure that we have the right people doing stuff on the mobile side and then everything that is in the like uh light purple or pinkish color um that was all a custom based server work that's all backend work and that was all custom

47. 34:35

    that was not part of the third party services and so now you have like all of this stuff here and this like this again while this feels kind of crazy there's so much stuff on here right it it and again this is not a flowchart this is just showing how different functions are all connecting and where stuff is is uh linked to you start to see the scope of your project you start to get a sense

48. 34:58

    just from like a snapshot it's like a snapshot of like oh this is going to be the project so now as you start to build out like you know here's my punch list here's the stories you know here's you know my you know my first half dozen Sprints being planned out you start to see the real scope of this and gives me a real sense of like this is going to be a lot of work this is going to be maybe be more than we first planned for

49. 35:22

    because look how many you know external dependencies there are look how many you know custom things have to go into tie into these uh external services and all of that and so now again this is just that productivity piece for yourself of like by doing this exercise and this took a while to really plan out you now see oh here's the scope of my thing and so that's why this is like really

50. 35:44

    important and again I I really encourage this at you know any level that you're doing this and especially again if you are a solo or on a small team to really map out this stuff because again like let let's let's go back to the the other thing here of let me go um here I'll just I'll show the very first one I just showed right here of like right this is just a basic data this is so this is like much simpler than the other one right obviously but this is just showing all the different

51. 36:19

    data sources that have to go into this API it's really rudimentary like it's really simple I didn't color code it um but this again in was like super informative of like look how much external look how much stuff has to go into the apis look how much data sources there is and so that informs again like your decision- making like is this too much work for one Dev is this something

52. 36:42

    that we can still ship as an MVP if that's what we're trying to go for what becomes the timeline to actually ship this stuff when I have you know three external data sources two ex internal and now I got to build you know you know uh apps around it right so again goes back to this of like you know what's what's going to become the flow once I actually see that you know what do I need inside all of that so that that's where again I really want

53. 37:15

    to like highlight and emphasize that this stuff is like super important for plan again it's like a productivity hack you know times a thousand that's why I try to do this all the time just again even at the simplest manner it doesn't always have to just be a flowchart either um per se let me show you one more here and then we'll talk about some some other stuff and this is one where we did a little bit more uh kind of flowcharting around here so let

54. 37:47

    me show this so now this is one where I start to blend a little bit with not showing screen here we go where we blend a little bit of that planning part along with some of the flowcharting part right so now you can see again this is again this is not and if you're just joining us this is not the traditional of like here's how you make a flowchart or like if again if you're working in like a big company and you're like they are asking

55. 38:17

    you to develop a flowchart for like your architecture this is not that this is really for like planning and this is again where I I I feel very strongly that especially again I'm talking to you hopefully you know uh solo devs small teams entrepreneurs that this is the stuff that will really you know hopefully give you a productivity boost and change how you approach software because it's

56. 38:49

    hypercritical that you are understanding everything that's actually going into your product everything that has to go into your your app like you need to be aware of that and so in this one here uh in this planning again this is a an older thing from an older project um and we were having conversation about like what are all the feature sets in here and what goes into these feature sets right so and then I colorcoded it though a little bit differently so instead of color coding it on like

57. 39:22

    decision trees and actual like a traditional like flowchart color coding we said what's actually been built and not in production what's actually in production today and what's planned for but not actually either finalized or even build at all and the reason why we wanted to do this is one you want to look at you know how much total scope creep have we had over the over the years and you can

58. 39:47

    start to see like your stuff starts to balloon and balloon right and you have all these other features and then like I also want to be able to see like uh you know what if we build that's not actually in production that maybe fits into the flow here so that was important to us and then lastly you know if we want to look at other features and we want to have some of these discussions around like hey let's build X Y and Z like what has actually not been built yet but we've we've talked about and

59. 40:17

    where does that tie in again like like like what does that Branch off of that we have today and and that's the part that I think is like really again super important when you're trying to build so in in this example here right so like this is kind of again a quasi flowchart of like how does the user begin how does they how do they enter the app um and this is this was a mobile app in case you're curious um so you know how do

60. 40:41

    they enter the mobile app like where's that data coming from like what what invites them you know and then like when they go to like different Pathways so again that's why this like a quasi flowchart a little bit but also kind of a excuse me a diagram that helps uh show show you know again all the different features that's in here and now again here's an example where it's like okay you know if you're

61. 41:09

    in this flow here you see that there's a yellow and yellow is building that in production and so that's really helpful to inform at this a team meeting when we go through this we can say Hey you know like we have this thing built it's not in production you know and it can hopefully spark a conversation of like hey it connects to this part of the app this this part of the flow should it be

62. 41:33

    in production what does it mean for it to be in production um you know like why did we not put it in production you can start to have all the discussions again even if you're a small team or even if you're by yourself right and you're that solo Dev entrepreneur which is super hard I encourage you to have at least a co-founder but separate discussion uh we'll get there uh is like just to have

63. 41:59

    that conversation out loud sometimes of like why did we build this and then not ship it why is it here and like what's stopping us from actually putting into production you know what does it mean for it to be in production is it going to lead to possibly more work that we're not ready to support do we not have the support system in there yet uh a million different things may come up maybe we

64. 42:25

    build it but it's not you know we just didn't think it was good it would didn't work right whatever so it's just sitting on the shelf or maybe it was built it was great at the time but we never actually put in production and now it's outdated so whatever the reasoning is right so it's important to highlight some of that stuff we also wanted to be able to have discussions around again of like hey if I was going to expand a feature set you

65. 42:49

    know and I wanted to actually add something in and add an integration or add something else in right this is planned but not built what does that start to mean and this essentially like helps break off like what again that that thought process right this is all about you know understanding your product and what you're building and really pulling this all together of again like what's next cuz I'm going to be honest with you and this is something I have seen for years

66. 43:22

    and years now I mean I I've been building software for a long time in different aspects the biggest mistake that solo devs and like small teams make is you just start building stuff because it feels it sounds cool it's a cool feature it's a cool idea um as a developer we like to be challenged sometimes right so like we just like we're jumping into to like just be part of that you know

67. 43:53

    challenge like oh yeah like that's technically hard I want to show off that I can build that awesome like super cool but like it doesn't if you're trying to actually ship a product it doesn't help you and so it's important to be able to like objectively look at like here's what I have in again like so I we colorcoded it here's what we have in production today here's what we don't we're planning for and like and so again like you can have that discussion for

68. 44:16

    yourself and then like I wanted to be able to show in this example here again this is again that hybrid model of some of it's a flowchart some of it's just a feature set of what goes in there right and like okay and some stuff like again build but not in production like okay so here's some data resources you know why was this build but not put in production and maybe the answer simply is like we don't have any customers that use that

69. 44:39

    data and like that's fine and you're like okay cool like we're ready and so now if you have salespeople if you're again if you're an entrepreneur and you're a developer entrepreneur and you're doing some of the sales yourself you say oh I have this feature that can attract other customers that I have not gone after yet so I should should sell to those customers because I already have something they want already built

70. 45:02

    but it's not in production because nobody's using it so I don't have any customers for it these are these are important discussions this is why you want to think this through and I will also tell you as you go and as the time goes on if you are lucky enough to build on the same project for a while you know a year or two or three or four or maybe 10 years can I say lucky because because

71. 45:27

    so many projects start fail don't even make it don't even really get going so if you are in that camp like you've been now working on the same project for a few years that's incredible and you it's easy to forget like what you've already done it's easy to forget like oh I have this code base that is relevant just needs like a little bit of tweaking and I can unlock a new customer set right you're struggling you're plateauing on Revenue you're plateauing on on sales

72. 45:53

    you know and you you need something that's going to bring in new customers oh maybe you actually already have something so planning this out is like really really I think a super important piece of all of this all right let's go back though and I actually I want to try to show you here I think I have uh another one I can show that I think is like really really relevant piece to talk through um

73. 46:27

    let me show you okay so I I want to I want to just show this last example here and uh I think this is hopefully uh this is instructive for people so all right let me let me share share my screen here okay so I'm I'm going to give a warning I'm going give before I put this on on the on air here uh this is going to look like total chaos okay this is going to be this is you're you thought the other

74. 46:59

    ones look busy you are not prepared for the amount of busyness that is going to be on your screen from this chart it's okay it's okay you're not ready we're going to talk it through and I'm going to show you why sometimes like this is helpful and what this did for me personally uh as as a developer who is actively building a product right now what's in it and why I think sometimes

75. 47:32

    doing stuff like this that's kind of messy and doesn't always have to look you know uh like I guess really like fancy appropriate and like you know uh I guess social media Worthy is okay so I hope you're ready here we go it's a lot okay this is something from a project I'm actually working on now Shard dog this is not something that's in production this is something that we've actually uh I actually we've gone away from right so this was

76. 48:05

    something that um you know if you can see carefully on my screen it says like big picture and this was a while back this was thinking through like what do the product have to look like and the reason why I want to and I want to show this and I'm not giving away anything that we're working on now is because this was like so important to really put onto a screen and visualize of like what the product was doing and like where it could go and

77. 48:37

    like what was going to be involved now my project right now Shard dog it's two of us I'm the only developer though and we both make decisions though on product and so we both need to be able to talk it through so I need to be able to both talk about all the things that we've we've discussed today so far you know decisions about like what's going in production what's you know why things are not going in production what can be

78. 49:06

    built what's not being built um what is the actual flow of things now this is more of a traditional flow chart in the sense of like this is actually showing user flow but I will say like this became something where after doing this it was like oh this isn't the right way to go about this and and I'll kind of I'll explain why as we kind of go through this a little bit here but um I first put a key up here to

79. 49:35

    kind of get a sense of like in this example how much stuff is needed how much infrastructure is needed to achieve this and you start looking at this and you say oh okay this is this is a decent amount of infrastructure for a small team it's not abnormal is not you know too much where like again like I think in in 2024 building a startup um depending on what you're doing you could easily have a

80. 50:07

    bunch of infrastructure what's missing from here as well is all the stuff that we were doing on chain as well so this is just simply like the you know like non non-blockchain related stuff part of this is just that Ming so you start to see that and you're like okay that's a lot and then you start looking through these different processes you're like well I have these couple different flows and the flows all seem to be reliant on this

81. 50:37

    part here like oh I need a wallet and like look how complicated like these flows become like when somebody needs a wallet it's like oh all of this has to go on and then oh if I don't need a wallet well okay it's a little bit better but maybe we need to actually do you know we talked about like doing some um like user rep scores and things like that and then we say oh look at all the different apis that have to go into it you know and so you're like Okay and

82. 51:07

    like over here too it's like how many different apis we have to have for for this side of it you know once we're actually look into it and it just it just becomes like almost unruly of you're like this is a lot and the part that made us pivot a part of it here and and this is like I I I can't tell you why if you need a real example of why this is so important to do this type of stuff is that when we actually saw what we needed to do that we thought

83. 51:40

    was going to make it successful for doing wallet Creation in a way that was both um you know saving us some you know issues with like Bots and abuse uh making sure the user had a really good experience to make sure that you know that account creation was able to then lead to something else you know like mean like using something else in the ecosystem uh it became a lot it was a

84. 52:11

    lot of effort and work just to that one piece and that piece while we while Shard do does focus on onboarding the actual opening of the wallet is like a smaller piece of like what we really really trying to do and so for us was like okay this is not the right path and that's when we you know then if you had been following along with us that we then kind of pivoted a little bit to leverage Uh current wallets in the ecosystem that had ways to like more

85. 52:45

    quickly open a wallet and then like redirect back to us and so like we worked with groups like at the time it was Minas now it's B um you know meteor here wallet we we work you know we tried to build something out with all of them of like here's a way you can claim you know your your wallet and thing go back to Shard do and that was really important for us in the development process because it allowed us to focus on other things that were more core to

86. 53:14

    what we were trying to do and try to get to in the big picture with shardo but I I would say that we went for a while now I'm gonna put this up here use a little bigger so you can kind of see of what goes on here it of you know what of you know hey like this is we're going to have to build out all these different parts to be safe and you can see this flow here right so This MC

87. 53:49

    now was was was actually not there at first like it was just right to this flow and then like meteor came out with with their one click you know basic sign up and we were like oh well if I just want to make it now I just do that like look at like I just I bypass all of this and I get right to where I'm going and like that's what like that changed what we started to do because we're like this gives us no extra benefit like it doesn't do anything if anything it maybe

88. 54:19

    causes more problems because of one piece of it goes wrong it could lead to abuse we we are we've never raised money and so like you know this is fully boot trapped so if this gets abused and uh it gets botted and now people are you know draining our accounts to create wallets like that's not a good look either so we don't want any of that so then you see this you're like oh well I I could just

89. 54:43

    take this one simple path and then you're like yeah that's it like that's what we're going to do and so we moved to that and then we did it with mint base as well and like that made all the sense in the world because again it allowed us to focus on some of the more key stuff that we're trying to do big picture that uh was not necessarily like in our core planning per se right so I I

90. 55:10

    think that's the stuff for me that I really think is like super important and that's why I would also say that when you are starting to think through your software again I want to really uh hammer this home that you are taking if you're not going to take time on the stories and and again that's a separate discussion we'll talk about like story development Agile development things like that another time but if if nothing else making these visualizations are

91. 55:44

    really I think just incredibly important for how you start to plan long term okay uh lastly here like so again this is a little blurry here let's straighten this out a little bit okay there we go so one of the things that came up right here at the end is it starts to let me think a little bit more about of like what is what can I save and maybe that's both right that's both like time

92. 56:26

    and money okay when I start to build out you know where are friction points and this is goes to both parts of this so yes you're user right you're making flowcharts right but also as a developer and hopefully the example I just showed you illustrates that is that when we saw all the stuff that goes in to doing what we had in our mind that we thought would be a strong user experience and that we thought was the way to actually do it the right way for

93. 57:06

    something like again you know well account we'll call it account creation right then where we said oh well this's this other solution out here yes it's third party and so we're not owning that part of the stack but it's going to allow us to focus on other stuff like amazingly helpful like that's something that again it changed the direction of how we started to plan the future of the whole product and what we what then came later so that's that's an important piece so

94. 57:38

    we're saving time we're saving money we're check we're looking into what the frictions are for the user as well as for the development part process of this all of that together again starts to be super informative because at the end of the day okay and so again hence the title of the show wake up and ship more in order to ship more and ship stuff that is quality enough stuff that is worth other people's time not just your own time it is all about

95. 58:10

    productivity and you know that's something where like I If if you're not being productive it's you know when you are a again Solo or small team Dev like that's a killer like that's just going like you're going to get you're just going to be stuck spitting your wheels and especially if you are a solo Dev who maybe is working has a regular full-time job part or part-time job and then is doing maybe like a startup on the side you're trying to do something new you're trying to experiment and hack your way you need to

96. 58:43

    be productive you need to have that productivity and charting this stuff out both from like again the flowchart process of it because again that can save me some of the stuff with around and go doing testing and things like that as well as productivity of decisionmaking which is sometimes again the biggest you know I guess time suck is like working on something that you're never going to ship I just I'm building out something I'm never going to ship this so I need to be able to make sure

97. 59:17

    that I am being very clear of what my direction is and am I making the right decision and then can I have the right conversation with maybe my you know my co-founders or even just an outside party if I'm trying to show that idea so like we talked about last week with the MVP we said look the MVP is trying to solve a couple different problems here some of those problems are around like uh you know does does my idea make sense right do you understand what's trying to happen

98. 59:48

    here and you know and that's a piece of it and this is this kind of goes back into that mvp part of it of like hey if I show you this flowchart if I show you this diagram of what goes into my app is that going to make sense to you in order to actually you know leverage this and can I is this something if I then build it will it make sense to to do so that's how that all kind of fits together uh I think again I am a a huge

99. 1:00:21

    proponent of this uh is something for myself that has really changed my personal productivity um over the years I started doing this probably about about 10 years ago and it really changed a lot of things for me not just of being more ficient the work I've done but really being able to think through stuff because I and again like all all developers do this this is not like a unique thing if you actually are caught up in something

100. 1:00:57

     like uh you know you just it's all in your head right and you're just trying to build right it's great to get it on paper and sometimes like writing it out is not the right path um so this is one part of that secondarily is that if I'm trying to really again like future plan and I really want to be able to say like what needs to be done now charting this out like super powerful and so I really want to like emphasize that this is a skill that's super helpful and there's no real right

101. 1:01:34

     or wrong way of doing this um I showed you multiple examples of multiple different ways that I have done this from ways that are the a traditional flowchart all the way to like here's this diagram that's colorcoded only in the way that makes sense to me but I put a key up there so you could see so that it could lead to a discussion so it could lead to a conversation it could lead to all these different things

102. 1:01:57

     so uh just something to really consider that's it for today uh I I hope this was informative uh please join the conversation on telegram if you have questions uh if you're watching the replay uh make sure you're doing that uh also to you know if you haven't uh already make sure you're signing up for the for the newsletter uh through uh through devhub with all things developer in the near ecosystem uh we're also going to talk and have some more different highlights from this show as well as our devhub

103. 1:02:35

     live uh we'll be live again tomorrow both with this show uh wake up and ship more as well devhub live comes back tomorrow too to have some dis uh some cool discussions with some developers as well uh and so we're really trying to make sure that you know if you are building we want to help provide resources to you uh to improve that if uh if you have ideas and suggestions for the show uh please join the group and you're more than welcome to suggests of the group uh but otherwise uh until

104. 1:03:09

     tomorrow uh I am Joe you can message me any time on X or through that telegram group and keep building and keep shipping see you tomorrow thanks n