28.xhtml 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149
  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/03-March/28.xhtml" />
  27. <title>To lie to medical professionals &lt;https://y.st./en/weblog/2016/03-March/28.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/03-March/28.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/03-March/27.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/03-March/29.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>To lie to medical professionals</h1>
  67. <p>Day 00387: Monday, 2016 March 28</p>
  68. </header>
  69. <p>
  70. I received a letter from one of my credit unions today saying that if I got an automobile insurgence quote, they would ship me a gratis umbrella.
  71. In the fine print, they said that the offer is only valid if I get the quote over the telephone.
  72. That&apos;s just moronic.
  73. There&apos;s no valid reason to require that a quote be obtained over the telephone.
  74. </p>
  75. <p>
  76. I want to speak with the people at the dental office, and I think I may have somehow looked up the wrong dental office yesterday.
  77. I swear that the address I saw was on Virginia avenue, but the only dental offices there are with other providers.
  78. Luckily, a local office was available, and perhaps it was even slightly closer than the office that I thought was the right one; it was just about half a block off Virginia Avenue, on Broadway.
  79. They said that it was in fact possible for me to set up an appointment at the local office instead of the distant one.
  80. But while emergency appointments are available for people with a pain of at least a six, ostensibly on a scale of zero to ten, as far as regular appointments, the soonest that they can see me is May 23.
  81. I&apos;m wasn&apos;t even sure that I&apos;ll be in the city anymore in May, so I didn&apos;t set up the appointment.
  82. I later spoke with my mother about this, and she told me to lie about the pain, saying that it was of level nine and that the pain is nearly unbearable.
  83. This seems like a very bad idea.
  84. Even ignoring the fact that this would be lying, it misinforms the medical professionals that are performing work on my body.
  85. If they think that things are worse than they are, yes, they&apos;ll see me sooner, but they will also take more drastic action or potentially even the wrong action.
  86. Lying to medical professionals just isn&apos;t safe.
  87. I suppose I&apos;ll walk to the distant office tomorrow and try to make an appointment there to see if I can get a sooner appointment.
  88. If I can get a sooner appointment, even if it&apos;s at the more distant office, maybe that will appease my mother.
  89. If a sooner appointment isn&apos;t available at the other office, maybe I&apos;ll suck it up and tell her about my fears with lying to the dental people.
  90. Alternatively, maybe I&apos;ll just schedule the May 23 appointment if I can&apos;t get a sooner one at the other office.
  91. If I have to cancel it, I have to cancel it.
  92. </p>
  93. <p>
  94. I worked on <a href="https://git.vola7ileiax4ueow.onion/y.st./include.d">include.d</a> a bit, but I quickly hit a snag: <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> traits can&apos;t define class constants.
  95. This throws a wrench in my usual method of setting exception codes.
  96. For the built-in exception classes, exception codes are integers.
  97. To make such numeric information meaningful, I set up class constants to compare the exception codes to.
  98. That means to see if an exception was caused by a particular exception-throwing case, you can compare the exception code to the relevant constant.
  99. This doesn&apos;t help if you don&apos;t have any guesses as to where the exception came from, but you usually do have a pretty good idea of what could do the throwing based on what code you wrote and/or interfaced with, and this is the closest that I can get to meaningful exception codes in the default exception classes.
  100. Now I&apos;m faced with several options, assuming that i can&apos;t come up with any better ones.
  101. I could have the class that uses the trait define the constants, but that would mean that each class that implements the trait would have its own set of constants to check against.
  102. You wouldn&apos;t have a generic way to check to see if the exception was thrown by a particular method; instead, you&apos;d be checking to see if it was thrown by the combination of the method itself and the class that used the trait.
  103. I could set this up as static functions that return the values that would have otherwise been constant values, but that seems hacky.
  104. I could define a constant array outside of a class that is used strictly to hold the constant values that would otherwise be stored in trait constants, but that presents a couple issues.
  105. First, it doesn&apos;t take care of the constants used to provide access to the value that the <code>__FILE__</code> keyword references from within the trait&apos;s file.
  106. Second, it causes all exception-throwing cases in which this external constant is referenced to be fatal if the exception&apos;s file has not been <code>require</code>d.
  107. Then again, this may be fine.
  108. Code that isn&apos;t ready to deal with these potential exception cases by including the constant is probably not wrapped in a <code>try</code> block.
  109. Exceptions should be fatal when unexpected.
  110. Still, it seems messy, as you may try to catch anything that can possibly be thrown, only to have the undefined constant error kill your code.
  111. Perhaps I just shouldn&apos;t use an exception code or should use a code that&apos;s arbitrary but easy to calculate.
  112. I did some experimenting and found that I can cram six characters into a thirty-two bit integer if I use a forty-character alphabet.
  113. It&apos;s also worth noting that I still can only cram six character into the integer if I use a twenty-six character alphabet.
  114. In fact, in order to cram in a seventh character, I have to drop to a twenty-three character alphabet.
  115. If I go with this method, which is more helpful, one extra character in length or seventeen extra characters in the character set?
  116. </p>
  117. <p>
  118. My mother was looking at something that she wanted online today, and it was sold out.
  119. It got me thinking.
  120. Things that she wants are often either sold out or expensive.
  121. She herself even says that she has expensive tastes.
  122. The problem is that her tastes are so popular, that people are able to charge more, and if they don&apos;t, none of the object in question are left for her to buy.
  123. Maybe this is just a symptom of how extreme of a conformist she is though.
  124. She is against rocking the boat or doing anything that could be remotely perceived as strange.
  125. Maybe she is exceeding generic at her core.
  126. I suppose there&apos;s nothing inherently wrong with being generic, as long as you aren&apos;t trying to pressure everyone else into being generic with you, as she does.
  127. </p>
  128. <hr/>
  129. <p>
  130. Copyright © 2016 Alex Yst;
  131. 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>.
  132. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  133. My address is in the source comments near the top of this document.
  134. This license also applies to embedded content such as images.
  135. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  136. </p>
  137. <p>
  138. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  139. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F03-March%2F28.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%2F03-March%2F28.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  140. </p>
  141. </body>
  142. </html>