I Was Studying Exceptions, But Got Confused, So I Luckily Designed The Code Editor Instead
I spend a lot of time doing nothing without realizing I'm doing nothing. Brain injuries are like that, I guess. I don't think anybody knows crap about anything & 99% of life is made up and provably stupid. Whatever. I seem to get going between 1-4pm. No matter how hard I try to get moving, I bounce between different tasks until the fear piques and I find something to work on and hopefully find my focus.
Awesome Sauce grew too much, or too big, or my living situation is overwhelming, or something. Because I went from highly productive to scattered right after my son fed me his mom's lentils and rice. Hmm. That's like what happened after the cup of coffee at his piano teacher's apt. Whatever. Keep forgetting nobody cares. Except for those people putting me on blast on their social media accounts. I'm probably good entertainment because I'm blind and write a lot.
Last week I started trying to build diagrams for Awesome Sauce Java. Then apparently forgot what I was writing and where the files were. Today, I opened a word processor, restored a file, and saw a list of tasks I was writing to try to get organized...a month ago. I completely forgot I wrote it. Was looking at it, and had to look away. I'm disgusted. If even one person had helped, I'd have had disability somewhere around 17 years ago, and would have been able to work on recovering from head injuries forever ago.
The thing I've wanted to do, and have prototyped a number of times over the last 15-20 years, have to do with hyperorganizing detail. I didn't just want organization, I wanted access and quickly. It's been hard to find the balance and the control and the presentation interface and interactions. But, this week it all feels like it came together. Because it's coming together and parts keep getting added in without any, "that won't work".
In order to explore the idea further, I've been applying the concept to other application types. I figure if it looks like it'll work for an editor, taking a look at other problem sets will highlight if there are strengths to the model, or will serve to expose weaknesses in the concept that being a coder might make me (more) blind to.
Point is? I'm going to do some more drawing on paper. If it continues to hold together, will balance writing it against writing the Forex trading application. I've started the Forex/Stock Market app. It'll be fun to start making some progress, but there's a couple pieces of infrastructure I have to build, that I've been having problems working on. Macros took a long time to see how to build, then no time at all to build. I've been considering and trying to unravel and build some constructs I just can't see.
I've been trying to build these functions and methods and classes for years. It's maddening, but it'll come together at some point. Persistence has always paid off, so I do my best to look, attempt, and if it's not happening, keep calm and find a problem I can make progress on. There's lots to do with Awesome Sauce Java with Hot Sauce, and it makes sense to make progress, rather than get frustrated not seeing how to build something for hours, days, or weeks on end.
Will keep working on the Editor, I hope. Or finalizing the testing of macros. Or the web code. No, definitely the Editor, because it'll help with everything else. And the Forex/Stock Market app.
Definitely going to stay focused on the Editor, because it looks like it'll be faster to work with. It also offers pretty significant benefits regarding structuring code, using packages (very different, more compact, super-expressive), localization (this is especially cool), and many other aspects of what is involved in writing code.
Editors definitely represent an interesting problem. There's a delicate balance between making an editor functional versus making an editor non-functional. But the package code is a pretty big deal, because it's going to make it easier to not only explore code really quickly, it's going to make it immensely practical to make use of code, no matter the source. The Editor, in combination with the benefits of the components it includes, offers a lot of benefits. Plus, I can test it by writing the Forex/Stock Market application. And the web code. And all the other parts of Awesome Sauce with Hot Sauce basically looking at me going, "You ever going to get any of this done?"
Man, I hope I get this done. It's some fun software.
Awesome Sauce grew too much, or too big, or my living situation is overwhelming, or something. Because I went from highly productive to scattered right after my son fed me his mom's lentils and rice. Hmm. That's like what happened after the cup of coffee at his piano teacher's apt. Whatever. Keep forgetting nobody cares. Except for those people putting me on blast on their social media accounts. I'm probably good entertainment because I'm blind and write a lot.
Last week I started trying to build diagrams for Awesome Sauce Java. Then apparently forgot what I was writing and where the files were. Today, I opened a word processor, restored a file, and saw a list of tasks I was writing to try to get organized...a month ago. I completely forgot I wrote it. Was looking at it, and had to look away. I'm disgusted. If even one person had helped, I'd have had disability somewhere around 17 years ago, and would have been able to work on recovering from head injuries forever ago.
Whatever, the Editor
The other day I was working on something in Awesome Sauce Java. Then, I started working with the spreadsheet, tried to figure out how if it could be made to work with the complexity of data, and finally had insight into how to structure the UI to turn it into an editor. I've had ideas for an editor for many years. Most programmers have at least some sense of how editors are at least limiting.The thing I've wanted to do, and have prototyped a number of times over the last 15-20 years, have to do with hyperorganizing detail. I didn't just want organization, I wanted access and quickly. It's been hard to find the balance and the control and the presentation interface and interactions. But, this week it all feels like it came together. Because it's coming together and parts keep getting added in without any, "that won't work".
In order to explore the idea further, I've been applying the concept to other application types. I figure if it looks like it'll work for an editor, taking a look at other problem sets will highlight if there are strengths to the model, or will serve to expose weaknesses in the concept that being a coder might make me (more) blind to.
Validating the UI
The last few hours, I've been considering how to use the Awesome Sauce Editor (IDE/Code thing) for a number of other concepts. So far, it looks like it might work for at least:- shell
- search
- file manager
Point is? I'm going to do some more drawing on paper. If it continues to hold together, will balance writing it against writing the Forex trading application. I've started the Forex/Stock Market app. It'll be fun to start making some progress, but there's a couple pieces of infrastructure I have to build, that I've been having problems working on. Macros took a long time to see how to build, then no time at all to build. I've been considering and trying to unravel and build some constructs I just can't see.
I've been trying to build these functions and methods and classes for years. It's maddening, but it'll come together at some point. Persistence has always paid off, so I do my best to look, attempt, and if it's not happening, keep calm and find a problem I can make progress on. There's lots to do with Awesome Sauce Java with Hot Sauce, and it makes sense to make progress, rather than get frustrated not seeing how to build something for hours, days, or weeks on end.
Will keep working on the Editor, I hope. Or finalizing the testing of macros. Or the web code. No, definitely the Editor, because it'll help with everything else. And the Forex/Stock Market app.
Definitely going to stay focused on the Editor, because it looks like it'll be faster to work with. It also offers pretty significant benefits regarding structuring code, using packages (very different, more compact, super-expressive), localization (this is especially cool), and many other aspects of what is involved in writing code.
Editors definitely represent an interesting problem. There's a delicate balance between making an editor functional versus making an editor non-functional. But the package code is a pretty big deal, because it's going to make it easier to not only explore code really quickly, it's going to make it immensely practical to make use of code, no matter the source. The Editor, in combination with the benefits of the components it includes, offers a lot of benefits. Plus, I can test it by writing the Forex/Stock Market application. And the web code. And all the other parts of Awesome Sauce with Hot Sauce basically looking at me going, "You ever going to get any of this done?"
Man, I hope I get this done. It's some fun software.
Comments
Post a Comment