17.xhtml 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236
  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 © 2017 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/2017/06-June/17.xhtml" />
  27. <title>Chase is being difficult, but will get back to me in two days. &lt;https://y.st./en/weblog/2017/06-June/17.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/2017/06-June/17.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/2017/06-June/16.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2017/06-June/18.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>Chase is being difficult, but will get back to me in two days.</h1>
  67. <p>Day 00833: Saturday, 2017 June 17</p>
  68. </header>
  69. <section id="general">
  70. <h2>General news</h2>
  71. <p>
  72. <strong>*Chase Bank did not update the name on my account like they said they did.*</strong>
  73. I don&apos;t have time for this, school has started.
  74. I sent them a message instead of visiting them in person.
  75. Our conversation was as follows:
  76. </p>
  77. <blockquote>
  78. <p>
  79. I went into a branch to have the name on my account updated because I&apos;ve had a legal change of name, and I brought a certified copy of the court order along with my new DMV ID.
  80. I was told that I needed to have paperwork mailed to me, and that I needed to fill that out and bring it back along with my court order and ID again.
  81. When the letter from Chase arrived, there was no paperwork at all to fill out, and it just told me to bring my ID or the court order to Chase.
  82. I brought both back to a branch, and I was told my name would be updated this time.
  83. Now, I&apos;ve received a letter saying my name was already updated, so no further action was required by Chase at this time.
  84. After I finally managed to log into your website (your website is a major pain to log into and use), I found that the name on my account had not been updated at all.
  85. How do I get the name on my account updated?
  86. I have had a court-approved change of name and have no interest in using my birth name any further.
  87. Furthermore, there will come a point when my old DMV ID with my former name expires.
  88. I won&apos;t be able to manage my Chase account at that point if you haven&apos;t updated the name on my account.
  89. How do I get you to actually update the name on my account?
  90. </p>
  91. </blockquote>
  92. <blockquote>
  93. <p>
  94. Hello <span class="redacted">[REDACTED]</span>,
  95. </p>
  96. <p>
  97. Thank you for contacting Chase about updating the name on your account.
  98. </p>
  99. <p>
  100. To update your name on the account we will need some additional documentation.
  101. I am sending a form via US Mail to the address listed on your account.
  102. It should arrive by 7 to 10 business days.
  103. </p>
  104. <p>
  105. Please complete this form and fax it back with your documentation to the number provided.
  106. Once received, either myself or one of my colleagues will update your name in our records and send a replacement card.
  107. </p>
  108. <p>
  109. We appreciate your business and thank you for being a Chase customer.
  110. </p>
  111. <p>
  112. Thank you,<br/>
  113. <span class="redacted">[REDACTED]</span><br/>
  114. Chase Email Servicing<br/>
  115. 1-800-436-7927<br/>
  116. </p>
  117. </blockquote>
  118. <blockquote>
  119. <p>
  120. That&apos;s what you told me the first time, but then what you sent me wasn&apos;t actually paperwork to fill out. It was just paperwork that said to fill it out only if the change wasn&apos;t because of a court order, but it *is* because of a court order. Are you going to actually send me something to fill out this time? This is really getting old, and will be the third time I&apos;m waiting for something in the mail from you. This should be a very quick process, but you keep dragging it out.
  121. </p>
  122. <p>
  123. Additionally, I do not have a fax machine. May I just bring the paperwork in-branch?
  124. </p>
  125. </blockquote>
  126. <blockquote>
  127. <p>
  128. Hello <span class="redacted">[REDACTED]</span>,
  129. </p>
  130. <p>
  131. I appreciate your follow-up email about updating your legal name on the account.
  132. </p>
  133. <p>
  134. I&apos;ve forwarded your message to the appropriate department for review.
  135. You should receive a response within two business days.
  136. </p>
  137. <p>
  138. We appreciate your business with Chase.
  139. </p>
  140. <p>
  141. Thank you,<br/>
  142. <span class="redacted">[REDACTED]</span><br/>
  143. Chase Email Servicing<br/>
  144. 1-800-436-7927<br/>
  145. </p>
  146. </blockquote>
  147. <p>
  148. Needless to say, I&apos;m a bit annoyed; perhaps more than I should be.
  149. However, they&apos;re hitting me with two things I can&apos;t stand and one that&apos;s normally just obnoxious, plus I&apos;m a bit anxious about school.
  150. I feel like I&apos;m already a bit behind in my studies.
  151. Now they&apos;re keeping my account under my horrid birth name and assuming I have access to a fax machine, while making me wait for things to come through the slow postal system, things that just tell me that nothing has happened or that I didn&apos;t need to wait for them after all.
  152. I mean, c&apos;mon!
  153. Not everyone has a fax machine.
  154. In fact, unlike telephones, which also not everyone has but businesses assume we all do, I&apos;m fairly certain most private citizens don&apos;t have fax machines.
  155. Fax machines are an archaic business technology that businesses refuse to replace with something modern (say, scanned documents sent via email/<abbr title="Hypertext Transfer Protocol">HTTP</abbr> or something), and for some reason, several businesses thing all or most private citizens would have one in their living rooms or something.
  156. And mail?
  157. Just email me the document, or provide a link to it.
  158. At the very least, I can look at it and verify it&apos;s the exact same document they already sent me and that says I shouldn&apos;t actually fill it out.
  159. Let me move on in this process.
  160. </p>
  161. <p>
  162. Speaking of credit cards, I haven&apos;t heard from Discover in a while.
  163. I wonder if my documents have made it to them yet.
  164. Again, they wanted them via post, so it&apos;s taking more time than it honestly should, but unlike Chase, Discover hasn&apos;t sent me any annoying letters saying my name has already been updated in their system when it really hasn&apos;t.
  165. </p>
  166. <p>
  167. I forgot I had something in the oven, so not only did I not eat it in time to head out to work on time, I also burnt it.
  168. After eating it anyway (I&apos;m surprised it wasn&apos;t so much more unpalatable than it was), I left my apartment.
  169. On my way out, my downstairs neighbour caught me.
  170. Ugh!
  171. What rotten timing.
  172. Anyway, they offered me an old milk crate for storage, told me their birthday is tomorrow, and asked me to bring them bread sticks tonight.
  173. They offered to pay for them, but I declined; not because it&apos;s their birthday, as I don&apos;t really observe those, but just because I want to get along with my neighbours.
  174. I rushed to work, beginning the work day in a much sweatier state than I wanted to.
  175. When I got home though, I couldn&apos;t get them to come to the door.
  176. They said they&apos;d still be awake after asking when I&apos;d get off work, but they must&apos;ve gone to bed anyway.
  177. I left the bread sticks hanging on their door knob, but they won&apos;t be fresh in the morning.
  178. I&apos;ll probably bring more tomorrow, but the same problem is likely to occur.
  179. I found the old milk crate by my door when I went upstairs.
  180. I&apos;m not sure exactly what to put in it yet, but I can&apos;t help but feel a sturdier container than cardboard will be useful to have around.
  181. </p>
  182. <p>
  183. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  184. </p>
  185. </section>
  186. <section id="university">
  187. <h2>University life</h2>
  188. <p>
  189. I completed my <span title="Programming 2">CS 1103</span> reading for the week and wrote up my initial discussion post:
  190. </p>
  191. <blockquote>
  192. <p>
  193. Asking whether it&apos;s the computer or the program that should handle a given task is like asking if it&apos;s the brain or the mind that should.
  194. It&apos;s very difficult to separate the two.
  195. The program is the instructions given to a computer about how to perform a specific task.
  196. However, programs can&apos;t actually do anything.
  197. Instead, the computer performs all the tasks.
  198. </p>
  199. <p>
  200. The program should include instructions on how to catch and handle exceptions, though it&apos;s the computer that executes those instructions.
  201. The exceptions arising in a given piece of code are usually best understood by the programmer.
  202. For that reason, the programmer of a specific program is in the best position to understand the best way of dealing with those exceptions.
  203. Leaving exceptions to be dealt with outside the program is therefore not optimal, and in my opinion, is just lazy.
  204. Another option is to not handle the exception in the program that threw it, but to handle it elsewhere in the computer: the operating system.
  205. This is a terrible idea and should never be done.
  206. If your program is written in a language that automatically catches exceptions that haven&apos;t been caught in the program, such as Java or <abbr title="PHP: Hypertext Preprocessor">PHP</abbr>, it might be acceptable in some cases to leave it to the language and/or interpreter to cacth your exceptions for you.
  207. This should only be doen when you don&apos;t mind showing error messages and stack traces to the user.
  208. Usually though, you don&apos;t want to confuse your users with stack traces that they likely don&apos;t understand.
  209. If the language doesn&apos;t catch exceptions for you, the operating system may be hit with them if you don&apos;t catch them yourself in your code.
  210. This can lead to the computer crashing or locking up until restarted.
  211. This is never preferable, and should be avoided at all times.
  212. </p>
  213. </blockquote>
  214. </section>
  215. <hr/>
  216. <p>
  217. Copyright © 2017 Alex Yst;
  218. 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>.
  219. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  220. My address is in the source comments near the top of this document.
  221. This license also applies to embedded content such as images.
  222. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  223. </p>
  224. <p>
  225. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  226. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F06-June%2F17.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%2F2017%2F06-June%2F17.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  227. </p>
  228. </body>
  229. </html>