csh
/
y.st.
派生自 y.st./y.st.


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301
							<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2017 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2017/06-June/21.xhtml" />
		<title>No sick day... &lt;https://y.st./en/weblog/2017/06-June/21.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
		<link rel="stylesheet" type="text/css" href="/link/basic.css" />
		<link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
		<script type="text/javascript" src="/script/javascript.js" />
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<nav>
			<p>
				<a href="/en/">Home</a> |
				<a href="/en/a/about.xhtml">About</a> |
				<a href="/en/a/contact.xhtml">Contact</a> |
				<a href="/a/canary.txt">Canary</a> |
				<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
				<a href="/en/opinion/">Opinions</a> |
				<a href="/en/coursework/">Coursework</a> |
				<a href="/en/law/">Law</a> |
				<a href="/en/a/links.xhtml">Links</a> |
				<a href="/en/weblog/2017/06-June/21.xhtml.asc">{this page}.asc</a>
			</p>
			<hr/>
			<p>
				Weblog index:
				<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
				<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
				<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
			</p>
			<hr/>
			<p>
				Jump to entry:
				<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
				<a rel="prev" href="/en/weblog/2017/06-June/20.xhtml">&lt;Previous</a>
				<a rel="next" href="/en/weblog/2017/06-June/22.xhtml">Next&gt;</a>
				<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
		</nav>
		<header>
			<h1>No sick day...</h1>
			<p>Day 00837: Wednesday, 2017 June 21</p>
		</header>
<section id="to-do">
	<h2>To-do list</h2>
	<ul>
		<li>
			Acquire stuff for my new home:
			<ul>
				<li>
					A bed
				</li>
				<li>
					A dustpan
				</li>
				<li>
					A carpet broom
				</li>
			</ul>
		</li>
		<li>
			Inform people that I&apos;ve moved
			<ul>
				<li>
					Relevant online accounts
				</li>
				<li>
					<del>My boss</del>
				</li>
			</ul>
		</li>
		<li>
			Finish stabilizing <a href="https://git.volatile.ch./y.st./include.d/releases">include.d</a> and put out another release (low priority)
		</li>
	</ul>
</section>
<section id="general">
	<h2>General news</h2>
	<p>
		I feel terrible.
		I did not get enough sleep last night.
		The worst part is that even with the shift I reluctantly picked up taking a day from me, there was enough time not to need that all-nighter, had I finished my coursework before cleaning house.
		After getting my due-today coursework done though, I couldn&apos;t resist cleaning up a bit more instead of getting some rest.
		I guess I tried to get some rest first, but I couldn&apos;t sleep for long.
		My coworker still hasn&apos;t gotten back to me about that mould spray.
		I give up.
		I&apos;m tired of being afraid to sleep in my own bedroom and I&apos;m not going to continually pester my coworker.
		I also need a study place that&apos;s well-lit at night.
		My bedroom has a light fixture, but the living room I&apos;ve been sleeping and studying in does not.
		I&apos;ve cleaned up the mould with just bleach and a rag.
		It&apos;s not completely gone, but it&apos;s not like I have money or options.
		Hopefully this is good enough.
		If it doesn&apos;t stay away, I&apos;ll just clean it up again.
		I&apos;ve moved my mattresses that I use and desk into the bedroom and the mattress I don&apos;t use out.
		I don&apos;t know if I mentioned it before, but I found a box spring someone put out by a dumpster, so I rescued it.
		Now, I started to set it up, but I found it has a broken cross-board.
		Lovely.
		I guess I can&apos;t use this thing after all.
		I put it back by the dumpster after work.
		Sock-sorting and file-sorting are the the two highest-priority items on my cleaning agenda.
		A large bin full of mixed socks and a collection of files scattered around the apartment represent the items that are most in the way, yet can be taken care of without first cleaning up something else.
	</p>
	<p>
		My mother wrote to me this morning asking how to download an entire email inbox.
		I explained that it depends on your email client, then explained how to do it in Thunderbird.
		Honestly though, I don&apos;t think that&apos;s the answer they&apos;re looking for.
		I think they don&apos;t even use a real client, but instead use their provider&apos;s Web-based client.
		The short answer on how you download your inbox on a Web-based client is that you don&apos;t.
		It&apos;s possible that the provider would offer a way to download all your emails in a ZIP file, but that&apos;s unlikely, and even if it&apos;s an option, it&apos;s going to be very provider-specific.
		I don&apos;t stand a chance at guessing where that option would be located.
	</p>
	<p>
		A while after cleaning up, I was hit pretty hard and fairly suddenly.
		My head was spinning, I was very nauseous, and I threw up a couple times.
		That couldn&apos;t be from the lack of sleep, could it?
		Then maybe ... was it the mould that hit me?
		Was this its way of fighting back?
		I&apos;d planned to pick up a face mask when I picked up the mould spray, but as my coworker never got back to me about the spray, I ended up going about this the stupid way and not preparing whatsoever.
		Or ... could this be from the fumes of the bleach!?
		Research when I got back home made this seem unlikely.
		I think I either just caught a virus with very strange timing or, more likely, I took a blow from the mould because I didn&apos;t wear a face mask when I cleaned it up.
		As horrid as I felt though, I had no choice; I had to go to work.
		I had a closing shift.
	</p>
	<p>
		As a side note, even while not feeling well, I still made some observations about my condition.
		Head spinning is very strange.
		It screws with your brain&apos;s ability to properly track things with your eyes.
		Either that, or it&apos;s <strong>*caused*</strong> by a temporary inability to track things with your eyes.
		The room appears to move only because your actual eyes are running in a straight line towards the edge of their range.
		When I rested my forehead on something hard, it also felt like my brain was moving around in circles within my skull.
		It wasn&apos;t like it was spinning; but like it was, while keeping its orientation parallel at all times, having its front-most tip rubbed on the inside of my skull.
		It was very strange, and altogether unpleasant.
	</p>
	<p>
		I bought less underwear than I threw out the other day, but I did get two packs.
		One was just standard underwear, nothing fancy; a ten-pack.
		The other was only a two-pack, but was supposed to help with the chafing I deal with at work.
		We have flame-powered ovens always blazing and I&apos;m fat, so my legs get sweaty and rub together.
		These underwear covered my legs and were tight-fitting, and my hope was that they&apos;d prevent that.
		They ... sort of helped.
		At first, I thought they were working.
		After sweating in them, they were unpleasantly damp and itchy, but I noticed a complete lack of chafing on my thighs.
		Once I got off work though, I noticed the chafing hadn&apos;t been prevented, but moved.
		Instead of chafing my thighs, I&apos;d now chafed my genitals.
		Ouch.
		Overall though, I guess I have less pain, so that&apos;s good.
		I&apos;m going to try wearing them a bit further down though next time, and see if that resolves the issue.
		Truth be told, I&apos;ve never worn underwear that long before, and I&apos;m not sure I had them on right.
		If that doesn&apos;t help, I&apos;ll try wearing two pairs of underwear; the long, outer paid to protect my thighs from each other and an inner pair to protect my groin from my outer pair.
	</p>
	<p>
		I got a chance to see my pay cheque today.
		My name has been updated, so it&apos;s now safe to update my account with First Tech Federal Credit Union.
		However, my boss didn&apos;t update my address, despite the fact that they had me fill out a form specifying my new name and new address.
		Oh well.
		I told they where I live, so I&apos;ve done my job.
	</p>
	<p>
		I discovered a new way to exercise at work on my breaks.
		I&apos;ve been trying to do sit-ups daily at home, but there&apos;s not a whole lot I can accomplish exercise-wise at work.
		However, I found I can flex my abs.
		Why didn&apos;t I think of that before?
		I pretty much spent most of one of my breaks rapidly doing that, and now my abs are a bit sore.
		I think that&apos;s a good thing though, it should mean I&apos;ve given them a challenge.
	</p>
	<p>
		Like I said before, I went to work in a terrible state.
		It was, quite predictably, a terrible idea.
		However, I have reason to believe that attempting to get sick pay would be fruitless without a doctor&apos;s note just because the store owner is illegally trying to keep it secret that we even have access to state-mandated sick pay.
		I think any excuse to avoid paying would be used.
		Normally, I try not to talk about the terrible working conditions here because it&apos;s not my place, but if you make me come to work in this state out of greed, yeah, I&apos;m not going to avoid commenting on it in my public journal if it becomes relevant.
		Anyway, in my impaired state, I messed up an order pretty badly.
		A customer ordered two pizzas, and that&apos;s both what I charged them for and what i gave them.
		However, that&apos;s not what I punched into the register.
		Before I hit the &quot;2&quot; button, I must&apos;ve hit the &quot;9&quot; button, because the receipt I handed them was for ninety-two pizzas!
		Thankfully, they&apos;d paid by credit card, checked their receipt, and thought I&apos;d charged them for all that.
		They alerted me to the problem, I printed a copy of the card machine receipt for them (our card machines are separate from our registers) to prove they hadn&apos;t been over-charged, and I took their incorrect receipt so I could show the manager what had happened and they could correct it in the paperwork.
		I didn&apos;t even notice though, and most customers don&apos;t seem to even look at their receipts before either crumpling them or putting them away somewhere.
		I got lucky.
	</p>
	<p>
		One of my coworkers was worried about me walking home in the dark.
		Alone.
		In an impaired state.
		I&apos;d left my bike at home, fearing I was in no state to ride safely.
		By the time I got to work, I was doing a bit better and was okay to ride, but at that point, it was too late.
		My coworker gave me mace though in case something came up.
		Apparently, they keep multiple containers of it on hand, and it sounds like they have more at home.
		That was nice of them!
		I&apos;ve added it to my lanyard with my keys, so I should have it on me any time I&apos;m out and about.
	</p>
	<p>
		My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
	</p>
</section>
<section id="university">
	<h2>University life</h2>
	<p>
		I finished up my discussion posts for the week before heading to work:
	</p>
	<blockquote>
		<p>
			You make an excellent point about the correctness of the output.
			If the program is relying on something outside the program to handle its exceptions, the program won&apos;t be as likely to know there&apos;s a problem and could produce incorrect output.
			It&apos;s very important that if we throw an exception or we call a method that does, we catch the exception and handle it properly.
		</p>
	</blockquote>
	<blockquote>
		<p>
			Memory dumps can be ugly and hard to interpret, but many languages these days output a stack trace for uncaught exceptions.
			Those are far from difficult to decipher by the people that actually need to.
			They&apos;re not very pretty to show to regular users though, so for externally-facing applications, catching the exception and showing a less-helpful but less-ugly message is a good idea.
			Like you said too, it may be possible to continue execution after catching the exception.
			Even if we can&apos;t perform the specific task the user asked us to, there might be other tasks the user needs our software to complete before shutting down.
		</p>
		<p>
			Imagine if we wrote a plain text editor.
			When we fail to save a file, an exception is thrown.
			One option is to let the program crash.
			In this case, the user tries to save the file and instead loses all their hard work!
			A better option would be to catch the exception, tell the user we failed, then let the user continue.
			They can then either try to save the file elsewhere in the file system, or at the very least, copy the contents of their file to the system clipboard and save it using some other application.
		</p>
	</blockquote>
	<blockquote>
		<p>
			I agree that it&apos;s the program itself that should catch and handle exceptions.
		</p>
		<p>
			However, you mention that the Java Virtual Machine runs on several platforms, so relying on the underlying computer to deal with exceptions would be ... well, unreliable.
			The logic behind this is that different systems would handle errors and exceptions differently, making it difficult to have any sort of expected, predictable behaviour in case of error if the exceptions aren&apos;t specifically handled by the program.
			This is very sound logic except that it leaves out one key detail, which pretty much reverses the argument.
			The Java Virtual Machine is a virtual machine; an emulated system.
		</p>
		<p>
			Java programs don&apos;t run on a multitude of systems, but only this one virtual one.
			The virtual system can be emulated on a multitude of platforms, but as far as what computer will be hit by uncaught exceptions, it isn&apos;t your physical one.
			There is only one (virtual) system that runs Java programs, so the behaviour of system-handling of exceptions would be extremely predictable and reliable.
		</p>
	</blockquote>
	<p>
		My <span title="Programming 2">CS 1103</span> discussion posts, shown above, were easy enough to write.
		My <span title="Databases 1">CS 2203</span> discussion posts, instead stored in my learning journal, were another matter.
		The <span title="Programming 2">CS 1103</span> discussion topic facilitated an actual discussion.
		We discussed who should catch and handle exceptions, which allowed for different thoughts and points of view.
		On the other hand, in <span title="Databases 1">CS 2203</span>, the discussion assignment was to rattle off definitions.
		This provided nothing reasonable for us to substantially respond to.
	</p>
	<p>
		I really wasn&apos;t feeling up to it, but I took the ungraded quizzes as well.
		I actually did pretty well on them, only missing one question between the two of them.
	</p>
</section>
		<hr/>
		<p>
			Copyright © 2017 Alex Yst;
			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>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F06-June%2F21.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%2F21.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>