| diana_coman: | shrysr: perhaps remember it's a republic, hence R at the end, lolz. | [02:20] |
| diana_coman: | as for the rest, there's a long history of my interaction with MP first, before there even was any sort of TMSR (it starts here: http://ossasepia.com/2009/12/18/despre-fantasme/ ) so I suppose you can say I was there from before the beginning. | [02:29] |
| diana_coman: | shrysr: re game dev no; the history is in the #eulora logs (logs.minigame.biz) and as a summary to start with http://ossasepia.com/2018/03/30/my-first-2-years-as-cto-for-minigame/ | [02:31] |
| shrysr: | okay that was intriguing. In general > is it good to follow the links in the article before reading all of it? I think that I should follow the links, as I read. i.e click on the link, read and then get back to the original. This is to understand the article better. However - it's not working as well as I want it to, especially the topics are entirely new. | [10:06] |
| shrysr: | diana_coman: http://ossasepia.com/2019/07/03/growing-young-hands/#selection-81.325-81.534 > how was this done step by step? Do you write notes as you read or after? | [10:06] |
| shrysr: | diana_coman: http://ossasepia.com/2018/03/30/my-first-2-years-as-cto-for-minigame/#selection-25.2-25.65 how did this 'pop up' and how does your time-log work ? | [10:25] |
| diana_coman: | shrysr: eh, that's a bit too intricate to extract it publicly really; let's say it's not all automated though, humans are involved! | [10:29] |
| diana_coman: | shrysr: as a rule, whenever you meet something you don't know, you *should* stop and look it up/read it so yes, follow the links | [10:30] |
| diana_coman: | it IS true that especially at first this can easily grow into reading 10 days from 1 single post | [10:31] |
| diana_coman: | (as a side note, do you see how lulzy the 5 minutes read! thingie on dev.to or whatever other similar nonsense actually is, if one really want to learn something?) | [10:31] |
| diana_coman: | but on the other hand, it's the only way to truly gain knowledge as opposed to skimming the surface | [10:32] |
| diana_coman: | as a starting compromise, you can basically make your tree of "must read this" and then work on it | [10:32] |
| diana_coman: | it will probably first grow more than it shrinks but keep at it and it *will* gradually start decreasing too | [10:32] |
| diana_coman: | re http://ossasepia.com/2019/07/03/growing-young-hands/#selection-81.325-81.534 the algorithm is always the very simple and same: make a written (this is mandatory, it HAS TO BE written) plan; start implementing it; review periodically how it's going (and/or change the plan accordingly) | [10:34] |
| diana_coman: | hence you know, http://younghands.club/2019/07/28/week-2-progress-summary-3/#comment-4 | [10:34] |
| diana_coman: | shrysr: by the way, you haven't actually answered ^ | [10:35] |
| shrysr: | diana_coman: that comment sort of led me into a tangent.... reviewing the way I 'do things'. | [10:44] |
| diana_coman: | re notes, it depends a lot on what I'm reading but in general I tend to take them as I read, yes. | [10:44] |
| diana_coman: | shrysr: there are some parts that are universal aka same for everyone: you NEED to look up stuff you don't know rather than skip it; you NEED to write in your own words as it helps you structure and go deeper; you NEED to plan in writing and in concrete steps as otherwise inevitably it will "slide" (aka you'll lie to yourself one way or another); | [10:48] |
| diana_coman: | then again there are some parts that in time you'll cut out the way that works for you: e.g. physically write notes or not; what tools to use. | [10:50] |
| diana_coman: | shrysr: the core of it is simple really (and TOO much focus on tools and structuring and whatnot is quite often a way to avoid the work) - concrete steps (e.g. "I'll write 500 words daily", "I'll read all about and related to the WoT on TMSR blogs"; do without fail what you set out in your plan; compare results with expected results and feed that back into "making a plan" for next item | [10:52] |
| diana_coman: | shrysr: from your work so far I'd say you are still jumping about a bit too much; I let it be for now as it's all the excitment of new and there's a lot to get in but soon you'll have to settle down a bit for the longer term | [10:53] |
| diana_coman: | because you risk burning out as it were, if you keep going on in this butterfly-mode | [10:54] |
| diana_coman: | if you need to, maintain also the tree of what you want to add in as soon as there is some opening for it, sure | [10:54] |
| diana_coman: | but do get some focus and stick with it. | [10:55] |
| diana_coman: | shrysr: understand that there's no rush; as you can see, I've been around for a while and TMSR has been around for a while so it's not one of those "get it now, latest buzz" thing | [10:57] |
| shrysr: | exactly.... i was just typing about burn out. I follow a rigorous time chunking schedule with 'control' and then after some time.. its depressing to think abt control and I slip. Sometimes I slip such that I forget most of what I've (ever) done, before 'bouncing back', but its pointless because I've lost the flow and thought process. | [10:58] |
| diana_coman: | shrysr: so you know, leave that part to me since you want to learn with me: stick to what I set for you to do and only that; write anything "new and shiny" in the "I might be interested in this" but do NOT just follow it blindly | [10:59] |
| diana_coman: | ultimately if you keep just bouncing about, there is no way I can help you either and it will come to grief | [11:00] |
| diana_coman: | focus for now on learning what you are set and forget about setting yourself - on one hand you can't really set yourself because you don't know what you don't know and on the other hand it will free you from the pressure of "oh,what if I miss something shiny" and from the bouncing about and from the burnout | [11:02] |
| diana_coman: | ultimately yes, learning happens only if you submit to a teacher; is this news? | [11:02] |
| diana_coman: | choose your teacher but once chosen stick to them. | [11:03] |
| diana_coman: | shrysr: the rigorous time chunking schedule sounds too tightly controlled - something like that will probably work only if either you're extremely disciplined or otherwise you live with someone who forces that on you; you need to be strict about "every day I do 2 hours of X" but don't push this into the automaton/depressing planning every minute of your day | [11:06] |
| diana_coman: | this is why I asked you to write a daily report as to what you did; I did not ask however for it to be written/published at 8pm every day | [11:08] |
| diana_coman: | shrysr: if you struggle with the planning, publish your current schedule /plan and ask for help; as always, this is the way to go about it | [11:10] |
| shrysr: | I don't particularly struggle with the planning as such. It's just that i plan something, and with experience, I've become better at estimating ..and toning down the 'excitement' and constant engagement thing, but probably 7 /10 times - i will pick up a new thread that is (hopefully) indirectly related to the planned task... I don't feel bad about pursuing the thread, but I do feel pissed off that I did | [11:15] |
| shrysr: | not do the planned task. | [11:15] |
| diana_coman: | shrysr: mk; *why* did you not do the planned task, did you figure that out? | [11:16] |
| diana_coman: | planning that you then fail to follow (and repeatedly i.e. predictably) sounds precisely like "I struggle with planning" | [11:17] |
| shrysr: | :D i know.. but as far as I can see...it seems like I lose interest after planning, and yet there is no point in not planning... it's bullshit, but I seem to think that I should be free to do whatever I want whenever I want, and that it will eventually come together though everything is disconnected. This works to a certain extent... but I think i am conflicted between 'free flow' and a 'plan'. Maybe I | [11:20] |
| shrysr: | dont even want to tell myself that this is what I shd do now. Its all bullshit. | [11:20] |
| diana_coman: | shrysr: by the sounds of it you are 1. focusing on the wrong thing ("do what/if I want but end up with what I need") 2. either planning the wrong thing or to the wrong level (and from earlier, possibly too detailed when you don't yet know the details) | [11:24] |
| diana_coman: | leave yourself *some* space for free flow too but within clearly defined boundaries (of a plan), essentially; and yes, it's not an easy thing to get right, sure. | [11:27] |
| diana_coman: | will bbl | [11:28] |
| diana_coman: | shrysr: btw, how's the v.py investigation going? | [14:04] |
| diana_coman: | shrysr: dont even want to tell myself that this is what I shd do now. Its all bullshit. -> the plan is not "telling you what to do now"; it's helping you keep on track and measure your progress; the *what* should flow *from* causes (e.g. you eat now because you are hungry now, not because some master plan says that at this precise hour you should eat every day). | [14:11] |
| shrysr: | 're-organising' efficiently i.e I have to 'archive' or hide the things I will do someday and keep ONLY the stuff I need today or the week ahead visible. | [14:21] |
| diana_coman: | sounds sensible | [14:24] |
| shrysr: | re v.py : i have a better idea of what it does - but I am yet to visit the code. as such - i had python setup for typical data science type explorations - but had left virtual env setup as a pending task. i figured this out yesterday and its working fine. I would also like to complete a refresher, i.e gain confidence in the basic data structures like tuples and lists, which are things I've always | [14:26] |
| shrysr: | 'forgotten'. Found a decent resource for this yesterday and ploughed through quite a bit - but not complete. | [14:26] |
| diana_coman: | shrysr: and open up if something is wrong, before it gets worse - there's no crystal ball so unless you make it public, nobody can help you with it, whatever it is (planning or anything else) | [14:26] |
| diana_coman: | shrysr: so where's the end-of-day list (or whatever other format you prefer): so far overall I think it does this and that ; my python setup changed this way and that; pending tasks x y z | [14:27] |
| diana_coman: | + "if time permits, z, t, w" etc | [14:28] |
| diana_coman: | end-of-day-notes are also there to support you next time you come back to the task - a sort of quick "get back into the flow" thing | [14:28] |
| diana_coman: | because guess what, life is full of interruptions of all sorts. | [14:29] |
| shrysr: | :)) I'm still figuring out my end of day list at mid day.... lol. But thats because of this revamp .. *brb* | [14:35] |
| diana_coman: | lol, ok. | [14:37] |
| shrysr: | I think >> 1. The Ecu + inflation concept (trilema) | [14:51] |
| shrysr: | 2. Explore selection to URL thingy -- DONE | [14:52] |
| shrysr: | 3. complete basic data structures - python | [14:52] |
| shrysr: | 4. complete new write up on WoT | [14:52] |
| shrysr: | 5. Causes and Purposes (trilema) | [14:52] |
| shrysr: | 6. continue with V-tronics 101 y | [14:52] |
| shrysr: | re: the selection to URL thingy >> this appears to be based on .htaccess which is not used in nginx. I saw the search parameters already seem to include the modification to .htaccess -- so I modified the functions.php file of the theme... but it did not work. As of now .... it seems this will need a lot of digging to implement. One way Might be >>> export as HTML and find a way to include an 'id' for each | [14:56] |
| shrysr: | html tag during export itself. Essentially... no easy way to implement. | [14:56] |
| diana_coman: | aha, it happens; | [15:02] |
| diana_coman: | now you get to re-examine your well-founded reasons for choosing nginx over apache :D | [15:02] |
| shrysr: | lmao extremely well founded. nginx docs even have an article saying - don't use .htaccess | [15:03] |
| diana_coman: | you do realise that there's "an article saying" for anything you substitute for "saying", yes? | [15:03] |
| shrysr: | :D yes | [15:04] |
| shrysr: | hehe yes | [15:04] |
| diana_coman: | that aside, the "web" is a pile of shit, sure; but until and unless we clear it up, we live with and in it, no way around this. | [15:04] |
| diana_coman: | anyway, this sounds like one of those that *can* wait for now | [15:05] |
| shrysr: | yes... DEFINITELY .. lol. | [15:05] |
| shrysr: | but i would so love to have it ... | [15:07] |
| diana_coman: | shrysr: that list earlier is what exactly, your to-do-list for today ? or for what? | [15:07] |
| diana_coman: | shrysr: so then switch to apache and be done with it, what | [15:07] |
| diana_coman: | or let me guess, there is an article saying not to use apache? | [15:08] |
| shrysr: | no! I still have no clue as to the difference between nginx and apache... n lol- i saw the nginx doc today! not before i 'chose' nginx. | [15:09] |
| diana_coman: | shrysr: so let me get this straight: you got nginx because it happened to be there but now you can't switch and be done with it because you don't know the difference? | [15:10] |
| shrysr: | lmao ... its sort of like that....but its more of an effort to rectify the mistake of not doing *any* research before opting. | [15:11] |
| diana_coman: | there IS something to that even, but then you have to live with no-selection-thingie | [15:12] |
| diana_coman: | shrysr: well, retroactively is retroactive you know? can't push the baby back so stop pretending it's even possible; you don't really have the option "what are the differences" since you have no idea on either A or B as it were | [15:13] |
| shrysr: | :)) i like the baby example... ok. I switch to apache..... | [15:16] |
| diana_coman: | your options now are instead: 1. you stick with what you have for now because it was there and you don't yet have the time to get something better - in this case, you live with whatever minuses it has, including no-selection 2. you switch to Apache on the grounds that a. those TMSR people chose it over nginx and they seem to know what they are doing - make a note to search for it one day! + get the selection thingie precisely like those cool people in tmsr | [15:17] |
| diana_coman: | shrysr: hopefully the experience sticks so that next time you ask and/or investigate *before* "choosing" | [15:20] |
| shrysr: | yes! | [15:20] |
| diana_coman: | cool then :) | [15:21] |
| shrysr: | I switch to apache... right now ...and make a note to re-visit apache/nginx someday. Added to today list. !! | [15:21] |
| diana_coman: | do me a favour though and do publish those end-of-day lists under their own category or whatevers but so that we can reference them when/as needed | [15:22] |
| diana_coman: | I'm not going to dig through the irc log after them | [15:22] |
| shrysr: | yes. Will Do. | [15:23] |
| diana_coman: | an unfortunate side of the remote interaction is that it does require even *more* details in what you publish as there's no other way for me to see and give you feedback on it otherwise | [15:23] |
| diana_coman: | good. | [15:24] |
| shrysr: | yes, i understand that. My original plan was to publish my daily agenda itself. I did not because it was ridiculously cluttered and i was sure you'd spit on the screen if i did not streamline it .... I will figure this out soon. | [15:27] |
| diana_coman: | shrysr: heh; trouble is you can't do those things on the quiet - i.e. say it upfront, don't just keep quiet about it until it's figured out. | [15:40] |
| shrysr: | diana_coman: LOL - i finally completed the switch to apache. | [18:06] |
| shrysr: | and........ | [18:07] |
| shrysr: | it did not work. | [18:07] |
| shrysr: | tried different themes and the same process. | [18:08] |
| shrysr: | Perhaps it works only on mp-wp ? <<sigh>> | [18:10] |
| shrysr: | diana_coman: ok the only difference is that instead of using/modifying .htaccess - I included the change in the website's <directory> configuration itself. Apparently, this is recommended over using .htaccess ... i do not have the httpd library installed either. | [18:17] |
| shrysr: | i'm not sure what is going wrong... but atleast - i did switch to apache. | [18:44] |
| shrysr: | diana_coman: i have an idea and i've outlined it here : http://p.bvulpes.com/pastes/wagAG/?raw=true | [22:27] |
Comments feed: RSS 2.0
[...] 30 Jul 2019 [...]