20.xhtml 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!--
  3. h t t :: / / t /
  4. h t t :: // // t //
  5. h ttttt ttttt ppppp sssss // // y y sssss ttttt //
  6. hhhh t t p p s // // y y s t //
  7. h hh t t ppppp sssss // // yyyyy sssss t //
  8. h h t t p s :: / / y .. s t .. /
  9. h h t t p sssss :: / / yyyyy .. sssss t .. /
  10. <https://y.st./>
  11. Copyright © 2016 Alex Yst <mailto:copyright@y.st>
  12. This program is free software: you can redistribute it and/or modify
  13. it under the terms of the GNU General Public License as published by
  14. the Free Software Foundation, either version 3 of the License, or
  15. (at your option) any later version.
  16. This program is distributed in the hope that it will be useful,
  17. but WITHOUT ANY WARRANTY; without even the implied warranty of
  18. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  19. GNU General Public License for more details.
  20. You should have received a copy of the GNU General Public License
  21. along with this program. If not, see <https://www.gnu.org./licenses/>.
  22. -->
  23. <!DOCTYPE html>
  24. <html xmlns="http://www.w3.org/1999/xhtml">
  25. <head>
  26. <base href="https://y.st./en/weblog/2016/11-November/20.xhtml" />
  27. <title>Eight days &lt;https://y.st./en/weblog/2016/11-November/20.xhtml&gt;</title>
  28. <link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
  29. <link rel="stylesheet" type="text/css" href="/link/basic.css" />
  30. <link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
  31. <script type="text/javascript" src="/script/javascript.js" />
  32. <meta name="viewport" content="width=device-width" />
  33. </head>
  34. <body>
  35. <nav>
  36. <p>
  37. <a href="/en/">Home</a> |
  38. <a href="/en/a/about.xhtml">About</a> |
  39. <a href="/en/a/contact.xhtml">Contact</a> |
  40. <a href="/a/canary.txt">Canary</a> |
  41. <a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
  42. <a href="/en/opinion/">Opinions</a> |
  43. <a href="/en/coursework/">Coursework</a> |
  44. <a href="/en/law/">Law</a> |
  45. <a href="/en/a/links.xhtml">Links</a> |
  46. <a href="/en/weblog/2016/11-November/20.xhtml.asc">{this page}.asc</a>
  47. </p>
  48. <hr/>
  49. <p>
  50. Weblog index:
  51. <a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
  52. <a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
  53. <a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
  54. </p>
  55. <hr/>
  56. <p>
  57. Jump to entry:
  58. <a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
  59. <a rel="prev" href="/en/weblog/2016/11-November/19.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/11-November/21.xhtml">Next&gt;</a>
  61. <a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
  62. </p>
  63. <hr/>
  64. </nav>
  65. <header>
  66. <h1>Eight days</h1>
  67. <p>Day 00624: Sunday, 2016 November 20</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/11/20.jpg" alt="A mariachi band playing outside someone&apos;s door" class="weblog-header-image" width="811" height="480" />
  70. <p>
  71. <strong>Current countdown:</strong> 8 days to find a place to live
  72. </p>
  73. <h2 id="general">General news</h2>
  74. <p>
  75. On my way to work, I saw and heard a mariachi band playing in front of someone&apos;s house! At first, I thought hat someone was playing a recording of them loudly, but as I neared the house, I actually got to see them playing.
  76. A couple of the band members even waved at me between songs! I&apos;m not sure why they were singing outside someone&apos;s house, but it was really cool to see it.
  77. </p>
  78. <p>
  79. The man-hour-to-profit ratio at work has been bad this week, so today, the shift leaders were trying to send employees home as soon as possible to improve that ratio.
  80. My hours started during the morning shift and ended during the evening shift.
  81. I was given a choice by the morning shift leaders: I could either go home very early, or they would call off one of the other employees scheduled to work during the night shift.
  82. I chose to stay.
  83. Apparently, that was the wrong decision.
  84. One of the night shift leaders got ticked off that one of their favorite and hardest-working employees had gotten called off.
  85. They later apologized to me, admitting that they don&apos;t know me or my work ethic.
  86. They also gave the morning shift leaders a list of people that they&apos;d rather see called off in the future if such a situation arises again.
  87. They cited reasons such as these people weren&apos;t able to handle simple tasks on their own or didn&apos;t work very hard.
  88. Ouch.
  89. I&apos;d hate to be on one of those sorts of lists.
  90. I ended up working a bit harder and faster than I normally do to try to prove to the night shift leader that having me around isn&apos;t so bad.
  91. </p>
  92. <p>
  93. Today, I picked up my first paycheck.
  94. It&apos;s not as high as I would have hoped, but I did come in partway through the pay period.
  95. Anything helps, and I hope to see several more paychecks before I leave this company again.
  96. </p>
  97. <p>
  98. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  99. </p>
  100. <h2 id="include.d">include.d</h2>
  101. <p>
  102. I shouldn&apos;t have, but I did a little work on <a href="https://git.volatile.ch./y.st./include.d/releases">include.d</a>.
  103. I added the <code>__set_state()</code> method to the exception classes.
  104. I plan to add this method to most of include.d&apos;s classes.
  105. The notable exception to this will be that wrapper classes won&apos;t have this method, as there&apos;s no clean way to implement the serialization of resource handles, especially without warning.
  106. If <code>\var_export()</code> would simply serialize objects using something similar to the <code>\serialize()</code> function, then wrap the serialized data in a call to <code>\unserialize()</code> instead of <code>self::__set_state()</code>, it might be more feasible to attempt to allow serialization.
  107. Exporting the object as an array without giving the class any way to clean up the data before doing so wasn&apos;t the best design decision on the part of the <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> developers.
  108. That said, the wrapper classes aren&apos;t really meant to be serialized in <strong>*any*</strong> way.
  109. They simply make calling functions on resource handles easier by grouping the resource handle and it&apos;s related functions into a single variable: an object.
  110. In reality, object such as these should have been used instead of resource handles, but I don&apos;t think that classes had been programmed into <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> yet at the time that the resource-handle-using functions were added.
  111. </p>
  112. <p>
  113. While i was writing some code, I came to a realization: the <code>__set_state()</code> method basically allows you to cast an array into an object of a given class, if the method is set up correctly! Is this useful? I argue that it isn&apos;t, but it&apos;s interesting to think about.
  114. Normally, when you cast any non-objects as objects, they become objects of the <code>\stdClass</code>.
  115. </p>
  116. <h2 id="university">University life</h2>
  117. <p>
  118. I don&apos;t remember where I found the link to the course textbook that I downloaded for <span title="Principles of Business Management">BUS 1101</span>, but I can&apos;t find it any more.
  119. Furthermore, I found two new links that I hadn&apos;t seen before.
  120. One offers the textbook in <strong>*basic <abbr title="Hypertext Markup Language">HTML</abbr>*</strong>, witch, if you don&apos;t take into account that good webpages are written in <abbr title="Extensible Hypertext Markup Language">XHTML</abbr>, not <abbr title="Hypertext Markup Language">HTML</abbr>, is the format that all online textbooks should be offered in.
  121. This version seems to be the right version for the course even, and has the required reading sections that weren&apos;t present in the other textbook that they offered me.
  122. Additionally, there&apos;s a <abbr title="Portable Document Format">PDF</abbr> textbook that I&apos;m going to assume is the correct one as well, but in another file format.
  123. This will be easier to work with on my mobile when reading at work, most likely.
  124. </p>
  125. <p>
  126. I also just found information that our initial discussion posts are due on Sunday.
  127. This information was <strong>*not*</strong> available in the syllabus.
  128. In any case, my initial discussion post last week was late.
  129. </p>
  130. <p>
  131. I graded the essays from last week that I was assigned this week, and the results were very disappointing.
  132. Nobody seems to have even read the assignment directions.
  133. We were supposed to review the definitions of leadership, entrepreneurship, and strategy.
  134. It wasn&apos;t stated clearly whether this review was supposed to be just us rereading the definitions or if we were supposed to write about them.
  135. Then, we were to find an example of each on the Internet, then compare and contrast our examples.
  136. The first two essays that I read didn&apos;t provide examples at all.
  137. The first of these then compared and contrasted the concepts themselves, though it didn&apos;t really compare strategy to anything.
  138. The second of these essays then went on to compare the definitions of these three concepts from the textbook to definitions of the same concepts found online.
  139. I can&apos;t even imagine what they must have been thinking.
  140. Not only that though, but their essay didn&apos;t meet the length requirements.
  141. Lastly, the final essay actually provided the three examples asked for! Sort of.
  142. Instead of finding examples online, the author instead gave generic examples: schoolteacher, inventor, and study plan.
  143. Still, that was better than the first two authors had done.
  144. That&apos;s where the good qualities of their essay ran out though, from a requirement-meeting perspective.
  145. Instead of comparing and contrasting the examples to one another, the author decided come up with three new examples, and compare and contrast to those instead.
  146. A leader was compared to a leader, an entrepreneur was compared to an entrepreneur, and a strategy was compared to a strategy.
  147. As much as I wanted to, I couldn&apos;t give anyone a decent grade on that assignment.
  148. </p>
  149. <p>
  150. Once I got home from work, I found that the textbook had been switched out on us.
  151. The reason that I found the new textbook today was because the textbook had been swapped on us! There had indeed been an error, but they found and corrected it.
  152. </p>
  153. <h2 id="apartment">Apartment hunting</h2>
  154. <p>
  155. I still have an account at Bank of the Cascades, and I&apos;m required to disclose all my financial account balances on my apartment application.
  156. I tried to log into the bank&apos;s website, only to find that I don&apos;t have login credentials in my KeePassX database.
  157. I never set up my online account! I tried to set up my account, but the stupid website is demanding that I verify the telephone number that they already have on file for me! I&apos;m not sure what number they have on file for me, but I was very clear with them when I set up the account that I didn&apos;t have telephone service.
  158. The number that they have on file ends in &quot;1212&quot;, which for some reason, makes me think that it&apos;s the number for one of the <a href="https://en.wikipedia.org./wiki/Directory_assistance#North_America">directory assistance</a> numbers; most likely, it&apos;s <a href="tel:+18005551212">+1 800 555 1212</a>.
  159. I have no way to clear this up but to go see them in person.
  160. I guess that that&apos;s how I&apos;m going to be spending my day tomorrow.
  161. </p>
  162. <hr/>
  163. <p>
  164. Copyright © 2016 Alex Yst;
  165. You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
  166. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  167. My address is in the source comments near the top of this document.
  168. This license also applies to embedded content such as images.
  169. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  170. </p>
  171. <p>
  172. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  173. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F11-November%2F20.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F11-November%2F20.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  174. </p>
  175. </body>
  176. </html>