pull down to refresh
100 sats \ 7 replies \ @l0k18 OP 23 Jan 2023 \ parent \ on: Indranet White Paper Updated bitcoin
We are working as fast on it as us two amateur devs can manage. Some more money might help things along, a little bit, though too much might actually be counterproductive.
I think probably a somewhat more seasoned protocol/server dev than me could probably help me advance faster by eliminating the newbie architecture mistakes that consume my time but end up being scrapped a little later on. That would be money well spent if we could get that kind of support, helping fan out the work a little and improve the architecting, and it would be equally valuable even if it was just voluntary/self funded.
Developing new systems is a little bit like walking around in a pitch dark place you don't know. It's very easy to get over excited and venture out in a direction and wind up slamming up against a brick wall, and then make it even worse because you deleted a bunch of work you thought wasn't important, and then either can't find it or it was written so that you can't easily correct the error.
I still think I'm on target to have some form of working testnet by the end of next month, but I honestly don't know how big the pieces are that are required to get to that point. Fingers crossed, not too big.
I think you should consider using a version control system to maintain and control your code and organize its development. I'll make sharing the code with other devs who might help, and/or publishing it later on, much easier, as well. BitKeeper is an excellent choice for that.
reply
I'm not that terrible with git though. Usually deleted code now ends up in the "shelf" in my intellij VCS interface at least until I next wipe my filesystem and start again. But haha, no I've managed to keep all my data together now for several years running.
reply
Ah, sorry for being an arrogant prick, then. Since you said
[...] you deleted a bunch of work you thought wasn't important, and then either can't find it or it was written so that you can't easily correct the error.
I assumed you weren't using (or were even familiar) with version control systems. I apologize for that.
reply
Haha! No offense taken!
Yeah, some days I am at something for hours and I get to the end of a step and I've walked the wrong direction entirely. I still have many old shelvings in my files now but usually I just rewrite it a lot simpler and faster than the wrong version that I shelved anyway. But that backup soothes my nerves a bit anyway.
reply
I see, but my point was that all that "wrong" code is also worth preserving in your CVS repository, in my opinion, because it might become relevant later. 😂
reply
Ah yeah, well, that just happens when more than a day passes between changes. I generally make about 3-5 commits a day. I was talking about those irritating times when I try to make a bunch of changes and it just gets too confusing for me to debug and I start again. Usually in the process I learn something about what I'm trying to do and the second try is really smooth. Those errors tend to get lost, but now they end up on my disk in the "shelf" storage in Goland.
reply
Ahh I know the feeling all too well! Wish my development skill were strong enough to help
reply