Young Hands Club

September 30, 2019

Week 12 plan Sep 30-Oct 6

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 5:04 a.m.
  1. [ ] Review JD Composite.
    1. Though this was done last week - I would like to gather more job descriptions to make sure nothing major is left out in the skill deficit list. It will be reviewed in any case in conjunction with tasks 2 and 3.
  2. [ ] Formulate more lucid plan to cover the skill deficits, with time lines. Discuss the draft in Chan.
  3. [ ] Create Resume V3.
  4. [ ] Re-connect and update an old contact regarding status and for help.
    1. Based on previous conversations ~1 year ago - I was to explore opportunities in Amazon and Zillow, apply and then share the details so the application could be pushed, which was also done at that time. Currently Zillow has already been explored. Once Amazon is done - I will be able to re-connect. The conversation will be a little more focused this time since my interests have crystallized (and general skills) have evolved.
  5. [ ] Continue Iterating on the definition of 'interesting companies' / 'Jobs'.
    1. [ ] Particularly, add smaller companies to this list.
    2. [ ] Add this list and explanation as a part fo the job search document for ready reference.
  6. [ ] Cover recruitment agencies in company profile list.
    1. Follow up regarding pending responses.
  7. [ ] Amplify the number of job applications sent out.
  8. [ ] Add more company profiles and job descriptions focusing on Vancouver
    1. Specifically want to cover smaller companies and see how the JD composite holds up.

1 Time-permitting tasks

  1. [ ] Review github website (https://shrysr.github.io)
    1. [ ] Re-align to emphasise data + analytics, supported by domain knowledge rather than the other way round as it is currently.
    2. [ ] Polish and add the mini-projects completed in the past.
  2. [ ] Continue exploring alternative approaches.
  3. [ ] Review and complete the draft blog post on happiness.

Week 11 review Sep 23-29

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 5:01 a.m.
  1. [X] Complete meditation post on stupidity. Analysis 2. See link
  2. [X] Update profile on Indeed.
    1. [X] Including profile summary, skills, simple generic cover letter, resume and skills. This will enable me to quickly apply to suitable vacancies.
    2. [2019-09-25 Wed] Used Resume v2 content to fill in the details and the profile is streamlined
  3. [X] Review JD Composite.
    1. In connection with (4) - JD composite was in fact reviewed. Some new job profiles were gathered, which still seem to match the composite made so far. However, this task will have to repeat along with (4).
  4. [ ] Formulate more lucid plan to cover the skill deficits, with time lines. Discuss the draft in Chan.
    1. Though I did spend time on this and made progress - the status is not sufficiently clear yet to discuss, and requires some more effort. In the process, I am also consolidating the resources (courses, books, past notes on resources) available and was able to revise some of them.
  5. [ ] Create Resume V3.
    1. This wil be in-line with the reviewed JD composite as well.
    2. [ ] Request feedback from chan on this. Perhaps consider sharing this version with Nicoleci, or decide if another iteration is desired.
    3. The only major component that should be included : are projects related to ML. Though a link to projects is provided in the CV - per my understanding, the website will be visited, only if the contents of the CV are interesting.
    4. [2019-09-29 Sun] - I could not work on this. Some minor updates were made to V2 during the course of the week. So far, it still does seem that resume V2 covers all the major points baring some additional refinement. As noted before, the most important pending area are projects related to ML. It is likely V3 will be the best version I can come up with atm, which can be streamlined based on input from chan + feedback gathered in the job search.
  1. [X] Connect with the pending Enbridge contact (due to return from travel on 23rd Sep) to discuss profile and strategy.
    1. This is basically a phone call and should not take long.

    1. The conversation was quite interesting and my CV has been shared. He was able to confirm my impressions of mechanical engineering and that the general engineering scenario in Canada, was quite different from what one would expect, based on feedback of his own friends in the design engineering field. Being in the supply chain management line - he was of the opinion that there was a wave of ERP adoption across North America at the moment and current exposure could actually be of good value.
    2. CV has been shared and he will help keep an eye out for opportunities. fwiw: appears that enbridge is certainly a company of interest - but more down the line than right now, in terms of the current (~1-2 years down the line) focal area of the company.
    3. Notes have been made of the conversation, as well as points on which I could improve.
  2. [X] Send out job applications with Resume V2.
    1. Maintain a record of the applications sent.
    2. Track down contacts for heads-up / follow-up.
    3. [X] Send updated CV to the new contacts made last week.
    4. [2019-09-29 Sun] Several applications have been sent out and this was the primary focus this week.

1 Time-permitting tasks:

  1. [X] Add more company profiles and job descriptions focusing on Vancouver
    1. Some profiles were added, and simultaneously applications were sent out.
  2. Continue Iterating on the definition of 'interesting companies' / 'Jobs'.
    1. Add smaller companies to this list.
    2. Add this list and explanation as a part fo the job search document for ready reference.
  3. [ ] Cover recruitment agencies in company profile list.
    1. Follow up regarding pending responses.
  4. [ ] Review github website (https://shrysr.github.io)
    1. [ ] Re-align to emphasise data + analytics, supported by domain knowledge rather than the other way round as it is currently.
    2. [ ] Polish and add the mini-projects completed in the past.
  5. [ ] Continue exploring alternative approaches.

2 Other notes

  1. Streamlined Emacs setup for more efficient capture of thoughts and notes, including applied jobs (resume versions), notes/thoughts related to the log, and also removed redundant package dependency based on features identified as already available in scimax.
  2. Citations and bibliography system for reading technical papers has been studied and set up. This will be useful for reading technical papers related to algorithms and libraries down the line. Such papers are more reliable resources to study than blog posts.
  3. Identified some concepts and currently evaluating resources (to translate to study plan) to learn the minimal amount of statistics to make sense of typical data analyses. This is connected to main task (4).
  4. Initiated study of the Daily Coding Problem book (Lawrence Wu). This book was purchased a while ago (and not explored), as it appears to be among the few books based on Python, rather than Java or other languages. Such problems or concepts are commonly asked in data science interviews. In the least, this will also support my revision of Python. This is connected to Main task (4).
Comments (0)

September 24, 2019

Updated Week 11 plan : Sep 23-29

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 3:35 p.m.

This post supercedes the earlier plan in line with Diana's comment. The tasks are re-arranged into a main list which are must-do tasks, and a separate list of time-permitting tasks.

  1. [ ] Complete meditation post on stupidity. Analysis 2.
  2. [ ] Update profile on Indeed.
    1. Including profile summary, skills, simple generic cover letter, resume and skills. This will enable me to quickly apply to suitable vacancies.
  3. [ ] Review JD Composite.
  4. [ ] Formulate more lucid plan to cover the skill deficits, with time lines. Discuss the draft in Chan.
  5. [ ] Create Resume V3.
    1. This wil be in-line with the reviewed JD composite as well.
    2. [ ] Request feedback from chan on this. Perhaps consider sharing this version with Nicoleci, or decide if another iteration is desired.
    3. The only major component that should be included : are projects related to ML. Though a link to projects is provided in the CV - per my understanding, the website will be visited, only if the contents of the CV are interesting.
  6. [ ] Connect with the pending Enbridge contact (due to return from travel on 23rd Sep) to discuss profile and strategy.
    1. This is basically a phone call and should not take long.
  7. [ ] Send out job applications with Resume V2.
    1. Maintain a record of the applications sent.
    2. Track down contacts for heads-up / follow-up.
    3. [ ] Send updated CV to the new contacts made last week.

1 Time-permitting tasks:

  1. [ ] Add more company profiles and job descriptions focusing on Vancouver
  2. Continue Iterating on the definition of 'interesting companies' / 'Jobs'.
    1. Add smaller companies to this list.
    2. Add this list and explanation as a part fo the job search document for ready reference.
  3. [ ] Cover recruitment agencies in company profile list.
    1. Follow up regarding pending responses.
  4. [ ] Review github website (https://shrysr.github.io)
    1. [ ] Re-align to emphasise data + analytics, supported by domain knowledge rather than the other way round as it is currently.
    2. [ ] Polish and add the mini-projects completed in the past.
  5. [ ] Continue exploring alternative approaches.
    1. The discussions on CR in chan have been interesting. I took a superficial look at Uruguay's immigration procedure last week. The procedure does not appear prohibitive, and there are somes similarities with Canadian PR. There may be TMSR blog posts that are more instructive in this regard. In any case, far more extensive research is clearly required to even formulate a plan.
Comments (1)

September 23, 2019

Week 11 plan

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 4:51 a.m.

Priority 1: 1, 2, 4, 5, 6, 9, 10
Priority 2: 7, 8, 12, 3
Priority 3: 11

  1. [ ] Complete meditation post on stupidity. Analysis 2.
  2. [ ] Update profile on Indeed.
    1. Including profile summary, skills, simple generic cover letter, resume and skills. This will enable me to quickly apply to suitable vacancies.
  3. [ ] Add more company profiles and job descriptions focusing on Vancouver
  4. [ ] Review JD Composite.
  5. [ ] Formulate more lucid plan to cover the skill deficits, with time lines. Discuss the draft in Chan.
  6. [ ] Create Resume V3.
    1. This wil be in-line with the reviewed JD composite as well.
    2. [ ] Request feedback from chan on this. Perhaps consider sharing this version with Nicoleci, or decide if another iteration is desired.
    3. The only major component that should be included : are projects related to ML. Though a link to projets is provided in the CV - per my understanding, the website will be visited, only if the contents of the CV are interesting.
  7. Continue Iterating on the definition of 'interesting companies' / 'Jobs'.
    1. Add smaller companies to this list.
    2. Add this list and explanation as a part fo the job search document for ready reference.
  8. [ ] Cover recruitment agencies in company profile list.
    1. Follow up regarding pending responses.
    2. Send updated CV to the new contacts made last week.
  9. [ ] Send out job applications with Resume V2.
    1. Maintain a record of the applications sent.
    2. Track down contacts for heads-up / follow-up.
  10. [ ] Connect with the pending Enbridge contact (due to return from travel on 23rd Sep) to discuss profile and strategy.
    1. This is basically a phone call and should not take long.
  11. [ ] Continue exploring alternative approaches.
    1. The discussions on CR in chan have been interesting. I took a superficial look at Uruguay's immigration procedure last week. The procedure does not appear prohibitive, and there are somes similarities with Canadian PR. There may be TMSR blog posts that are more instructive in this regard. In any case, far more extensive research is clearly required to even formulate a plan.
  12. [ ] Review github website (https://shrysr.github.io)
    1. [ ] Re-align to emphasise data + analytics, supported by domain knowledge rather than the other way round as it is currently.
Comments (2)

Week 10 Review

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 4:05 a.m.

Notes:

Priority 1: 4, 5, 6, 7, 2, 10
Priority 2: 1, 3, 9
Priority 3: 8

1. [ ] Gather contacts related to sent applications - and reach out.

  1. This has been cancelled over the past week in favor of gathering profiles in Vancouver first. The reason is that the profiles in Vancouver appear a lot more conducive to my current skillsets and it was deemed important to identify new companies and thus the contacts there.
  2. [X] Continue gathering JD's + Company profile information.
    1. [X] Expand this to Vancouver/BC.
    2. Several more JD's and Company profiles are gathered. See Updates (this covers most of the additions as a list.
  3. [X] Continue connecting to recruiters.
    1. Efforts have been made to reach out. Yet to receive responses from contacts. Reminders have to been sent out.
  4. [X] Complete basic JD composite and identify strengths + deficits
    1. A basic framework has been formulated along with a list of skills. This can be refined to more specific details as further profiles are gathered. See Updated Page
  5. [X] Extra 'interesting' companies from the list (to begin with)
    1. [X] Shortlist interesting companies
      1. Basis: general alignment with background, example Oil & Gas (eg customers of current company). Iterate on company profile and job descriptions to clearly identify the companies which are more suitable to overall goals.
        1. Attempts have been made to improve the basis above. However, it is still vague. Some descriptions have been seen to 'make a lot more sense'. These incidentally are more prevalent in Vancouver than in Calgary. Examples:
          1. Data Analyst, EA
          2. Business Analyst, AECOM : not the usual non-technical sales nonsense.
          3. Technical Business Analyst, Indeed : This is a powerful role which also enables a good exposure into web development, which can be helpful in eventually securing remote gigs.
      2. Some companies are shortlisted. These are relatively larger companies with more sensible job descriptions. It would be desirable to get into a relatively stable company. However, conversely, the competition will be significantly higher for these. FWIW: there are several more job descriptions and companies to cover in Vancouver. In particular, the next target will be towards smaller companies.
  6. [X] Create Version 2 of Resume.
    1. [X] Explicitly incorporate strengths identified in (4).
    2. Resume Version 2 is created in line with JD composite. I want one more cycle of analysing the JD Composite and hope to streamline this a little further
  7. [X] Complete draft of simple, generic cover letter for online job portals
    1. [X] Evaluate need to create multiple versions.
      1. Multiple versions may not be needed at the moment considering the profiles. However, this will be required down the line for targeted applications.
    2. This task was neglected, and will have to be completed next week.
  8. [ ] Review github website (https://shrysr.github.io)
    1. [ ] Re-align to emphasise data + analytics, supported by domain knowledge rather than the other way round as it is currently.
  9. [ ] Continue exploring alternative approaches.
    1. No further effort was made in this direction this week.
  10. [X] Draft a plan to address deficits.
    1. A draft plan is available, but I would like to refine this further and also discuss in chan to evaluate how this can be aligned to tmsr related activities.

General notes

  1. Improved my knowledge and comfort in Bash scripting. I enjoyed constructing this project, though it was relatively trivial; it still covered many fundamental aspects of writing a program. The important difference compared to earlier data-hag approaches was to keep the goals and steps small and to slowly but surely build up the process. Of course, the guidance in chan was also instrumental. I totally look forward to doing more and aligning them to tmsr related projects.
    1. I think there have been very few instances in the past that I have approached a data science project in the above approach. Perhaps there was too much I did not know, but I think the driving impediment was always wanting to know 'everything' before using a library; or knowing 'all of statistics' before using some simple techniques.
    2. FWIW: current proficiency in R was gained only by studiously following a relatively structured approach via Matt Dancho's course and applying the concepts directly in the ERP project. The pending parts of his course(s) will be a key part of the plan in addressing major skill deficits w.r.t job applications.
    3. My intention is to follow the step wise and planned approach henceforth for all upcoming projects, especially those where I do not know anything.
  2. The structured process of narrowing down skills + deficits is actually helping. While the skill deficit list is not entirely new - this new effort is now firmly based on exploring multiple job profiles of different companies, with very little 'idealism' thrown in.
Comments (1)

September 16, 2019

Week 10 plan

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 5:58 p.m.

Priority 1: 1, 4, 5, 6, 7
Priority 2: 2, 3, 9
Priority 3: 8

  1. [ ] Gather contacts related to sent applications - and reach out.
  2. [ ] Continue gathering JD's + Company profile information.
    1. [ ] Expand this to Vancouver/BC.
  3. [ ] Continue connecting to recruiters.
  4. [ ] Complete basic JD composite and identify strengths + deficits
    1. [ ] Draft a plan to address deficits.
  5. [ ] Extra 'interesting' companies from the list (to begin with)
    1. [ ] Shortlist interesting companies
      1. Basis: general alignment with background, example Oil & Gas (eg customers of current company). Iterate on company profile and job descriptions to clearly identify the companies which are more suitable to overall goals.
  6. [ ] Create Version 2 of Resume.
    1. [ ] Explicitly incorporate strengths identified in (3).
  7. [ ] Complete draft of simple, generic cover letter for online job portals
    1. [ ] Evaluate need to create multiple versions.
  8. [ ] Review github website (https://shrysr.github.io)
    1. [ ] Re-align to emphasise data + analytics, supported by domain knowledge rather than the other way round as it is currently.
  9. [ ] Continue exploring alternative approaches.
Comments (0)

Week 9 Review

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 5:57 p.m.

Priority 1: Tasks 1, 2, 4, 5, 6, 7, 9
Priority 2: Tasks 3, 10, 12
Priority 3: 11

  1. [X] Answer to "What do I need first to be able to work on TMSR full time."
    1. Draft was posted and discussed in chan.
    2. Updated Article link.
  2. [X] Gather a list of companies in Calgary
  3. [-] Gather the job descriptions (jd) of each opportunity.
    1. [X] Combine multiple job postings into a single generic checklist for each company.
    2. [X] Differentiate data scientist and analyst skills under each company if applicable.
    3. [ ] extract a list of skill deficits from above checklist.
      1. [ ] Formulate plan of attack for deficit and post for review.
    4. This is on-going. See Job Profiles gathered so far
  4. [X] Skim through jd's, shortlist the profiles that are most aligned with current skillset.
    1. This is being done on-the-spot, i.e for profiles that seem reasonably aligned - I have been sending out my application on the spot (with no CV modification or record). This is probably a poor strategy and I should pay more attention + take effort to record the action for reference + review, and as already suggested by Diana - I must take immediate steps to tweak the CV even for quick applications.
  5. [ ] modify resume aligned to the shortlisted jd's.
  6. [X] Send out applications in (3)
    1. [2019-09-15 Sun] A bunch of applications have been sent out with existing CV. I need to improve the process of recording the applications that are sent out. I also need to initiate the process of reaching out to the HR personnel of the specified jobs.
  7. [ ] Gather contacts related to sent applications.
    1. [ ] Send out connection invite + 'applied to this' shout-out + try to schedule chat.
    2. [2019-09-11 Wed] I have been filtering/gathering contacts in general - however, I have not taken the effort to connect with relevant people regarding the quick applications sent so far.
    3. [2019-09-16 Mon] I had a plan to create a clear list of contacts (instead of relying on repeated searches on Linked in / email - but have failed to follow through.
  8. [ ] Extra 'interesting' companies from the list (to begin with)
    1. [ ] Shortlist interesting companies
      1. Basis: general alignment with background, example Oil & Gas (eg customers of current company). Company profile and job descriptions that sound 'better'.
      2. [2019-09-15 Sun] I am yet to iterate on defining 'better' per Diana's advise.
    2. [ ] Gather information on the shortlisted companies, summarise and add to (2.3)
    3. [ ] Gather Contacts info via Linked in.

9 .[ ] Formulate a simple, generic cover letter for online job portals

  1. Draft is available. It has to be fine tuned further in line with study of JD's. See link
  1. [X] Recruiters
    1. [X] Gather earlier contacts from head hunting companies from earlier efforts.
      1. [2019-09-08 Sun] This has been initiated. I have sent out emails / messages to earlier contacts in Ontario, whether they themeselves can help or re-direct me to someone in their Calgary office.
    2. [X] Reach out them and identify correct local contact person in Calgary.
    3. [X] Identify contacts in new recruitment agencies.
    4. [2019-09-15 Sun] While several have been contacted - the process is still on-going due to delayed responses from people.
  2. [ ] Review github website (https://shrysr.github.io)
    1. [ ] Re-align to emphasise data + analytics, supported by domain knowledge rather than the other way round as it is currently.
  3. Explore Alternative approaches:
    1. ERPNext (Frappe) :
      1. As mentioned in chan, outreach was initiated in this direction to explore work-from-home possibilities. Feedback so far indicates that the company would not be interested in a remote work-from-home employee and are not in hiring mode. However, they are in search of 'partners'.
      2. Evaluation of T&C and overall modus operandi of their pre-defined 'partnership tiers' indicate that this is not a viable solution for stable income or even income of any reasonable size. On top of which - it requires continuous investment.
      3. In order to be thorough, an overview was prepared last week and is still in a draft stage. This will be posted tomorrow (though actually seems a bit of a waste to bother). Though this logic + understanding so far is to be verified with my contact, it seems quite unlikely 'unviable' conclusion will change.
      4. The intention is also to dig deeper and explore existence of their clients (if any) in North America (for opportunities). I expect information on this to be available in 1-2 weeks.
Comments (0)

September 9, 2019

Week 9 - Tasks

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 4:15 a.m.

Priority 1: Tasks 1, 2, 4, 5, 6, 7, 9
Priority 2: Tasks 3, 10, 12
Priority 3: 11

  1. [ ] Answer to "What do I need first to be able to work on TMSR full time."
    1. [2019-09-08 Sun] The plan is to summarise the discussions so far on this topic and expand on points that have not been touched (by me), and work towards a complete answer, considering the question explicitly. An existing draft is being updated and refined. I think I should share the updates as they are formulated rather than post a 'final answer' on the deadline of [2019-09-15 Sun]. Perhaps a good idea would be to post the draft tonight and review it in chan.
  2. [X] Gather a list of companies in Calgary
    1. Used Google jobs to filter out data analyst roles in Calgary. There are probably some more, but the list is long enough to start with.
    2. Identified Recruiters/Head hunters from the list.
    3. Posted at http://s.ragavan.co/job-search/company-list.html
      1. The document is posted in the above format to make it easier to identify recruiters and priorities as well as TODO's. The alternative was a page in the WP blog post. This would mean individually adding TODO's, priority level, recruiter identification as text under each heading.
      2. The above approach also makes it easier to ask friends/contacts if they have contacts in these companies, and this has been initiated today, and has to spread to others.
  3. [ ] Gather the job descriptions (jd) of each opportunity.
    1. [ ] Combine multiple job postings into a single generic checklist for each company.
    2. [ ] Differentiate data scientist and analyst skills under each company if applicable.
    3. [ ] extract a list of skill deficits from above checklist.
      1. [ ] Formulate plan of attack for deficit and post for review.
      2. So far - there are indications that only python is asked on the jobs in Calgary with no mention of R. In Toronto, there was a healthy mix, and often Python/R skills were asked. This may be a problem, since I am a lot more comfortable with R today, even to the extent of simple ML. While the algorithms are the same - there are signifcant differences in syntax between R and Python. The clear solution in terms of learning this deficit is the course(s) mentioned earlier (pending review of Python basics + others available for fundamental data analysis) - which will certainly suffice based on initial exploration (and compared to experience with other courses in the past).
      3. Another possible approach may be expanding the region of search beyond Calgary to the next nearest areas. These appear include R in greater number (from a very quick search).
  4. [ ] Skim through jd's, shortlist the profiles that are most aligned with current skillset.
    1. This has been initiated. Draft exploration will be posted tomorrow (rather than waiting to finish it all and then posting.)
  5. [ ] modify resume aligned to the shortlisted jd's.
  6. [ ] Send out applications in (3)
    1. fwiw: some applications were sent out, with no modification of existing resume.
  7. [ ] Gather contacts related to sent applications.
    1. [ ] Send out connection invite + 'applied to this' shout-out + try to schedule chat.
    2. Initiated contact with a guy (dads friend) at Enbridge - he is travelling and will respond on 23rd Sep. Being based in Calgary, and having worked at Ernst & Young till recently - he might have good advice.
  8. [ ] Extra 'interesting' companies from the list (to begin with)
    1. [ ] Shortlist interesting companies
      1. Basis: general alignment with background, example Oil & Gas (eg customers of current company). Company profile and job descriptions that sound 'better'.
    2. [ ] Gather information on the shortlisted companies, summarise and add to (2.3)
    3. [ ] Gather Contacts info via Linked in.
  9. [ ] Formulate a simple, generic cover letter for online job portals
  10. [ ] Recruiters
    1. [ ] Gather earlier contacts from head hunting companies from earlier efforts.
      1. [2019-09-08 Sun] This has been initiated. I have sent out emails / messages to earlier contacts in Ontario, whether they themeselves can help or re-direct me to someone in their Calgary office.
    2. [ ] Reach out them and identify correct local contact person in Calgary.
    3. [ ] Identify contacts in new recruitment agencies.
  11. [ ] Review github website (https://shrysr.github.io)
    1. [ ] Re-align to emphasise data + analytics, supported by domain knowledge rather than the other way round as it is currently.
  12. [X] Explore Alternative approaches:
    1. [X] FDM. Their M.O is to to take you in on a 2 year contract, and train you over several (6-10 iirc) weeks, while paying a stipend. They have a 'data science' cohort as well as a 'dev' cohort, with slight differences. Subsequently, you are posted with their clients after appropriate interviews with the clients. The salary is fixed over this 2 year period. The salary is obviously low for Toronto, however - this is as 'guaranteed' as it gets in terms of an entry and shift. I was on the verge of taking this up, when I got my current salt-mine offer. They do not have any office in Calgary.
      1. A possible approach may to fix up a spot with them and join them at the starting date of their next program. There are logistic irritations of shifting to Toronto involved, including finding a place to stay, etc. These are not insurmountable, though it would be better in general to not do this in winter.
      2. It is likely there is a stiff penalty for breaking the contract, though they did not share this with me despite repeated questions at the time. I should make a quick check if there is any correspondence/document I have missed in the summary above.
      3. In a away - this could be an answer to keeping my head down - getting minimal subsistence for 2 years and working on TMSR - and building skills for a big jump towards the end.
      4. One additional advantage is that once established via FDM - after the initial 2 year contract - it is possible to secure more jobs via FDM at much 'higher rates of pay' probably on a contract basis. The details of the last point is fuzzy in my memory - but this information can be obtained if deemed worthy of time.
      5. Overall - it seems this particular approach with FDM is best left as a last resort.
    2. [X] Explore existence of companies or bootcamps similar to FDM based in Calgary. In terms of overall job prospects (no. of jobs and companies and networking opportunities), as well as 'settling' - Toronto (12.1) is a better option for data science. A quick search indicates that there are no bootcamps in Calgary. There could be more options in Toronto - but overall, the bootcamp approach is flaky in terms of results, and (12.1) does not involve investment, other than shifting to Toronto.
      1. [X] Method Data Science: This is basically a remote internship where a fee has to be paid upfront, and then you are paired with a 'mentor' for industrial projects, covering about 1-2 months. This is an approach to gain project experience while being employed. This is not aligned to the current urgency in terms of results.
Comments (1)

September 2, 2019

Week 7 Review

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 5:43 a.m.

Priority 1 : Tasks 1, 2
Priority 2 : Tasks 3, 4, 5
Priority 3 : Tasks 6

  1. [ ] v.py : 10 lines, minimum.
    1. Though I did not have the energy to go further into the code itself - I believe indirect progress has been made via (2) as well the reading in (3.3).
  2. [ ] Continue reading the book Serious Cryptography Switched to the Handbook of Applied Cryptography by Menezes, van Oorschot and Vanstone, CRC Press.
    1. The primary goal is to cover the necessary portions to move forward with v.py, and atleast an overview of encryption as a concept, and the process of hashing, which will help me understand signatures.
    2. Though quite interesting and reasonably comprehensible - I am still yet to fully understand signatures and the hashing process. Progress in this has been slow this week - with a sudden salt-mine load induced wariness, but I did persevere: am mapping out concepts and am taking an effort to revise this frequently. See Current Map. Beyond the slow trickling of illumination and the sense that actual comprehension is just around the corner - it has also been a relief to stop searching each and every little thing on the internet and rely on a bible. While studying the patch in (3.3) - some additional light was shed on the vdiff. It has been exciting - I have had to stay in strict control in terms of short bursts and staying 'cognizant + focused' versus 'diffused and frantic', but I can see a growing impact of exerting balanced control - i.e not beating myself black and blue by over-reaching or expecting immediate results.
    3. I realise that this task can 'never' be marked 'complete'. I will consult with Diana on how to proceed.
  3. [-] Learning about software and the software industry (Spillover from week 6)
    1. [X] Summarise / Discuss: http://ossasepia.com/2017/02/18/the-open-sores-of-monkey-code/
    2. [X] Summarise / Discuss http://ossasepia.com/2017/06/12/o-brave-new-code/
    3. [X] Read: http://ossasepia.com/2017/12/21/eucrypt-correcting-mpi-implementation/
      1. Referring earlier comment: I was happy to be able to spot the error in MPN_COPY_INCR. Extending on 3.1 discussions - I am now able to comprehend the danger presented by lowered (incorrect) barriers, and the importance of adhering to quality over quantity. I am able to link this back to the concept of WoT - and that 'open sore' is a clear example telling me that I should not mistakenly assume that code by virtue of being open source can be 'easily' fixed / modified as desired. It may well be a gargantuan / miserable task to do so, depending on the quality of the preceding history of development, and the currently desired modification. Hacks are exactly what they are - hacks - not necessarily quality pieces of code fixing root causes. Such hacks, like a virus can even mutate into multi-headed hydra-spittoons over time (and also fed by ineptitude and laziness?).
      2. However, I could not wrap my head around the entire article w.r.t EuCrupt and what was happening and why, in terms of MPI and shifting bits. This was expected to some extent - I will mark the article read for now, having achieved he - and will obviously need to revisit and re-digest as I make progress.
    4. [ ] Summarise / Discuss: http://trilema.com/2019/no-platforms/
      1. This will be completed tomorrow.
  4. [ ] Complete partially finished pending Python basics revision.
  5. [ ] Open Data : Wages dataset
  6. [ ] Learn + Summarise :- systemd | init ( Refer log)

1 Other things

  1. Disabled HTTPS for my website and took a brief foray into heartbleed. See post.
  2. Posted earlier notes on research-compendium. This was done during my foray into docker and i forgot to post it. Though not complete - it will serve as a good summary and jump-start when I look into R packages.
  3. Took a long look at my baseline evaluation and shared this with Diana. Once clarity is achieved - I think it would be a good idea to publish the relevant portions. Further to the suggestion - I have been a little obsessed that this is a fundamental aspect that has to be rectified if I am to have any chance in streamlining my efforts and eventually achieve meaningful results through consistent effort.
  4. FWIW: the effect of focused attention and short bursts and increased discipline has percolated into other general aspects of my lifestyle, and the impact has been obviously positive. I have also become more consistent in reading the logs, and I have improved in 'asking' before getting lost. My observation is also that I am less agitated, and more cognizant of 'straw men' in my thought pattern. All this being said - these are early days and I would consider it a major step forward if I can stop myself from reaching a 'burn out' stage, and consistently pursue targets.
  5. FWIW: I made significant progress in my salt-mine tasks and also learnt much in the process. It may be presumptuous to think that I can 'finish a baseline release' in the next few days, but I can say that I do see a clear path ahead.
  6. I actually did some more reading than the articles mentioned above, particularly some articles on loper-os, some which were directed by Stan in the ossasepia channel. In particular, I found the quote from Orlov regarding trust to be quite intriguing and it is germinating deeper thoughts about trust and the WoT. However, I was not disciplined enough to note down all my thoughts, or perhaps I do not have a note or opinion worth talking about. This may be counter productive as a thought process - I have barely started my journey. I've taken steps, but I am not yet out of the dungeon. Another intriguing article and comment thread is Thumbs Down for Clojure. I will admit that there was a short phase wherein I tried to learn clojure, and actually started with scheme and was as usual abandoned it to 'refocus' on data science. I have recently been wondering if the choice of data science was ill founded, though I still think Machine learning is certainly very interesting. As I 'flipped' through Stan's articles trying to formulate a reading list for next week - the more my fascination grew with Lisp. There is something deeply satisfying about the very notion of coding, and I think I am yet afraid that it could be too late for me to be any good at it… even so there is something strangely akin to hope and understandably inspiration as I read Stan's articles.
Comments (1)

August 26, 2019

Week 7 tasks

Filed under: Shreyas Ragavan — Shreyas Ragavan @ 5:24 a.m.

Priority 1 : Tasks 1, 2
Priority 2 : Tasks 3, 4, 5
Priority 3 : Tasks 6

  1. [ ] v.py : 10 lines, minimum.
  2. [ ] Continue reading the book Serious Cryptography
    1. The primary goal is to cover the necessary portions to move forward with v.py, and atleast an overview of encryption as a concept, and the process of hashing, which will help me understand signatures.
  3. [ ] Learning about software and the software industry (Spillover from week 6)
    1. [ ] Summarise / Discuss: http://ossasepia.com/2017/02/18/the-open-sores-of-monkey-code/
    2. [ ] Summarise / Discuss http://ossasepia.com/2017/06/12/o-brave-new-code/
    3. [ ] Read: http://ossasepia.com/2017/12/21/eucrypt-correcting-mpi-implementation/
    4. [ ] Summarise / Discuss: http://trilema.com/2019/no-platforms/
  4. [ ] Complete partially finished pending Python basics revision.
  5. [ ] Open Data : Wages dataset
  6. [ ] Learn + Summarise :- systemd | init ( Refer log)
Comments (4)
Older Posts »

Powered by WordPress