Skip to content

Instantly share code, notes, and snippets.

@woozyking

woozyking/dear-diary.md

Created March 16, 2020 19:55
Show Gist options
  • Save woozyking/fcb7e02c5babde022cc47352a606977b to your computer and use it in GitHub Desktop.
Save woozyking/fcb7e02c5babde022cc47352a606977b to your computer and use it in GitHub Desktop.
Download ZIP
dev-journal-diary
Raw
dear-diary.md

Dear Diary,

Yesterday, I did yet another batch of GAM segments upload, and re-re-mirrored swarm repo, again.

But enough with the chores, let me share with you something more exciting!

I finally further automated the GAM segment upload process to source newly submitted jobs from segment_gam data table. Even better, now OPs have learned to use the already built (albeit hidden) LOCUS UI (/segments-gam, and /segments-gam-list) to input the GAM List ID and Segment pairs. 100% win-win for all!

On the front-end of LOCUS (snoke), I finally completed this iteration of builder view job redesign implementation, as well as the builder list redesign follow-up issue (snoke#703). At last, the crawling is over.

On the back-end of LOCUS (first order), I upgraded the runtime to Node.js v12 across configurations including AWS Lambda, GitHub Actions, and local development environment (.nvmrc). This has the implication of reduced odd issues seen by developers who run different versions across projects and unknowingly run into mysterious GC/malloc related crashes. Feature-wise, maps list endpoint now filters out ones without a FINISHED job -- one less awkward "technical difficulties" for sales people to run into.

Also, our beloved common sees another addition of dedicated meetings section to offer both core objectives to pursue after, as well as practical guides for teams to adopt and adapt in order to achieve those objectives. Hope all teams that read and adopt it become better at do(dg)ing meetings ;)

Today, I plan to:

  • Document on journal (:yodawg:), so everyone can get a better understanding of why we're doing this (perhaps not in a "Dear Diary" fashion).
  • Come up with potential automations to make journal practices a bit less cumbersome, or a bit more insightful.
  • Implement backoff retry logic for avail-bot routine so we don't shoot ourselves in the foot for evangelizing Dev Avail only to see it fail.
  • Investigate snoke webpack dev server's insane CPU usage issue.
  • ...

But obviously you know very well that I probably won't finish all, if any of the above. Let's keep out fingers crossed for no

Until the next work day.

Some Random Corporate Minion

YYYY-MM-DD HH:mm:ss+00:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment