Project: Do some micro-projects and report on them
Goal: Get used to noticing learning-focused micro-projects that I do already. Get used to thinking about the steps I do in those projects. Reflect on projects in general.
Details:
- What counts as a micro-project? I’ll start by aiming for projects that take less than three minutes to complete. I considered having a one minute limit, but that seems too short. I had trouble thinking of projects that would take under a minute. But I can think of more that take under three minutes. And a project that takes under three minutes is still pretty simple.
- How should I report on the micro-projects? I considered doing the project steps listed in this Doing a Project post or writing lists of steps for each project as in this Write Down Projects post. Those seamed too difficult. So I’m going to start with something easier: write a brief, informal report on each one. It may end up that some of the informal reports contain the steps for the micro-project and/or some other elements of a formal project plan, but they don’t have to.
- How many of this kind of micro-project should I do? It seems like at least twenty would be good, to get used to the thinking.
Evaluation: I would like to remember to evaluate this project once I’ve finished it.
Possible next steps: Maybe do more micro-projects and use more formal reporting or planning. Maybe do slightly longer projects. Maybe make some kind of diagram of how my micro-projects are related to each other.
Questions for others: Can you see any problems with this project? Any improvements I could make to it? Any reasons I shouldn’t do it?
Micro-project #1: Find the first video about learning html in the series by Mike Dane.
Micro-project #2: Find out if I can have more than one repository per account on GitHub
Micro-project #3: Find out the opposite of proportional spacing
Reflections on project plans for micro-projects
Micro-project #4: Make a second GitHub repository
Micro-project #5: Put something in the README file of the repository
Micro-project #6: See if I can remember how to make an html file and look at the website it creates
Next goals
Micro-project #7: Install Visual Studio Code (VSC) on laptop
Micro-project #8: Upload an index file that I made with Visual Studio Code to my GitHub test repository. Overwrite the index file I already have there.
Micro-project #9: Make a tree out of the steps from micro-project #7.
Micro-project #10: Post a tree to Basecamp
I’m going to try my second solution. If that doesn’t work, I’ll try one of my other solutions and/or think of another solution.
I see that in my solution brainstorming, I only came up with four ideas. That doesn’t seem like very many. But the one I plan to try won’t take long. So I’m not using up many resources by trying it.
Resources: I expect the project to take under one minute to either succeed or fail.
Steps:
Action: I’ll post this now and then try to post my tree in my next comment and do my evaluation there too.
Evaluation: Success.
I saw you did this and learned it from you,
You're also doing the resources section wrong every time. I haven't read much of the rest because you explicitly chose not to try to do my suggestions and to go off in your own direction.
You don't have mastery of project steps but are trying to add in the other parts. The underlying issue is that you can't tell when your practice is right or not, so you end up practicing wrong things and trying to build on them.
You are correct. Thank you.
I thought I was doing this suggestion of yours:
Steps to do a project - FI Learning
I think that this project is following your suggestion. I'm doing tiny, easy projects using organized, conscious, intentional steps. I'm trying to get experience and refine a process that works well for me.
I'm more worried about Elliot saying I'm dishonest. I thought of going through my writing and looking for things I wrote that are dishonest.
Goals
Continue?
> So far, no one has done several short, easy, successful projects, nor talked about why not.
Micro-project #11: Learn how to collapse and un-collapse sections of a MindNode tree.
Micro-project #12: Find out if there’s another way to collapse and un-collapse sections of a MindNode tree.
Micro-project #13: Write some sub-list items for a short list.
The last sub-step is kind of an if/then situation too: if (when) some condition is met, do some thing.
Micro-project #14: Practice side kicks
Micro-project #15: Open eyes
Micro-project #16: Zoom out on a short list of steps
Micro-project #17: Zoom out on the same thing a different way
It seems like you are asking if Elliot is trying to pressure you. I think the answer is no.
Regarding not reading your stuff specifically when you're not trying his suggestions, maybe Elliot is particular interested in people trying his suggestions as opposed to doing their own stuff.
I've already given some indication of some criticisms I have of the Elliot is trying to pressure you theory.
I am surprised that you said this. I often think Elliot is trying to pressure FI people to do certain projects or follow his advice or learn in certain ways.
I would love to find out I'm wrong. That would make FI way more pleasant for me.
I also think he's annoyed when people (especially me) don't follow his suggestions.
Maybe I'm right about the first but not the second.
Trying to pressure/manipulate/influence people is very second-handed. Elliot has written lots of criticisms of that kind of activity and goal. He's also done things like criticize segments of films for pulling people's strings, which is related. I wouldn't be super surprised if he's written more words on the general topic than Rand.
I think Elliot tries to appeal to people's reason, make good points, and offer suggestions and arguments. I think he's aware that sometimes people interpret such appeals to reason as pressuring, but that's different than saying he's trying to pressure people. People find all sorts of stuff pressuring, are emotionally complex, etc. It's a hard thing to deal with.
But I don't know what to do instead. If I just think to myself that he could have meant it a different way, then I still don't know which way he meant it. My social instincts tell me I'm being attacked and I don't have good reasons to tell them they're wrong, only possibilities that they could be wrong, and that's not enough to make a difference.
I agree.
I think that you should approach this as a problem that is amenable to rational analysis and as something you can resolve.
One question I would ask you is whether, given Elliot's ideas and writing, it makes sense to trust your culturally normal "social instincts" as reliable indicators in the FI context. Cuz as of now, it sounds like once you have a "social instinct" reaction, you're sort of going with that unless you can rebut it. But those "social instincts" may not make sense in all contexts. If you disagree, you may think that all people must necessarily act a certain way (as in, the ways your "social instincts" are calibrated to) which is itself an idea you can think about intellectually and criticize.
Not trying to come up with a "magic bullet" argument here right now btw, just trying to give some indication of the method to use.
I don't try to pressure FI people. That is not my intention or goal. I find that idea horrifying. I'm aware that people often pressure themselves and each other, and I've put work into figuring out how to avoid saying things that people will (incorrectly but semi-predictably) react to with self-pressuring.
I've often invited criticism and concerns be shared. If you thought there was a problem, e.g. pressuring, you could have first considered it could be a good faith misunderstanding or a minor mistake (by either party) or something and brought up the issue so it could be discussed and resolved. What you did instead was remember a negative interpretation that you didn't allow any rebuttal to or clarifications about. You did this multiple times and built up a significant group of unsolved, unaddressed problems and negativity which has now grown large, complex and severe enough to be difficult to address. Then you brought stuff up later, tangential to another topic (which is derailing to that topic), in a vague way without quotes or specifics (making the accusations hard to respond to), and after people forgot about the original discussion and context. Many people have done this specific thing to me, and I've often asked them not to. Please don't.
PS Your claims that I'm pressuring (on purpose!) are pressuring me to respond to your accusations.
😊 Negative feelings about FI - FI Learning
I added a word near the end of the first one that I thought would make it more clear.
I want to continue this thread about micro-projects here.
Micro-project #19: Italics in html
One of the these things was italics. I wrote some stuff in italics. Then I uploaded the file and checked the resulting website to see if the stuff came out in italics. It did.
Micro-project #20: Getting line wrapping in Visual Studio Code
Evaluation of this micro-project project