• Home
  • About
    • Bio
    • CV
  • Music
    • Shows
    • Works
  • Research
    • Works
  • Programming
    • Projects
  • Blog
    • Watson
    • Viget
  • Contact
    • Message
    • Subscribe
    • Availability

TTT

19 Jul 2016

Reading time ~1 minute

What I Did

  1. Given that today was TTT, I did not do much other than sit in on the mandatory meeting revolving around Viget’s current financial and logistical histories and trajectories. I regret not having contributed more to the scintillating discussions, though I honestly felt under-qualified to say much more than the few sentences that I managed to chirp.
  2. During the remainder of my time, I managed to more or less redo the CK blocks that I had completed during the past weekend. Rather than sandwiching tons of child components into other components, I’ve settled on having each component be their own self-contained units, excepting link group components which can piggy back on any other component.

What I Learned

  1. Tons and tons of thought go into the way Viget runs, which is highly reassuring.
  2. It has become clearer and clearer to me that good code is all of the following:
    • Dry
    • Modular
    • Simple
    • Readable
    • Maintanable
    • Efficient
    • Accurate
    • Testable
    • And much more…

I’ve got strive for my code to satisfy these standards more so in the future.

What I Still Don’t Understand

I don’t know enough about the different kinds of deployment environments that Viget utilizes when working for clients. Though I’m generally aware of the following three - integration, staging, and production, I certainly am not in the know regarding their specific purposes, setup process, and applications.



Share Tweet +1