25 lines
1.9 KiB
HTML
25 lines
1.9 KiB
HTML
<!doctype html>
|
|
<html>
|
|
<head>
|
|
<title>Zk | [no subject]</title>
|
|
<link rel="stylesheet" type="text/css" href="/style.css" />
|
|
<meta name="viewport" content="width=device-width" />
|
|
<meta charset="utf-8" />
|
|
</head>
|
|
<body>
|
|
<main>
|
|
<header>
|
|
<h1>Zk | [no subject]</h1>
|
|
</header>
|
|
<article class="content">
|
|
<p><span class="tag">diary</span> <span class="tag">livejournal</span> <span class="tag">fossils</span></p>
|
|
<p>After spending the day fighting with creating a new image for the D630s we got at the library, I've decided that, nice as he was, my previous supervisor really did not like his job. NONE of his code is commented at all, and the code that previous students have written is clumsy and comments usually apply to code that my previous supervisor commented out and rewrote. The guy who used to do all the imaging is graduating, and, having worked primarily with my previous supervisor, picked up the habit and didn't comment any of his code, nor document the rather involved process of image making at the library. I've decided that, once I get the D630s and Optiplex 330s out, I'm going to make it my task to not only relearn VBScript and possibly rewrite all these code tools, but to document the entire process of both making an image and imaging a computer.</p>
|
|
<p>I was looking into formats to do this in, as I'm sick of my workplace's reliance on Word - any ideas? Both LaTeX and Compiled HTML Help have been suggested - I would prefer the former, but don't think anyone would even want to touch it after I graduated, and while I dislike the latter, it would certainly be easier to update and more commonly used</p>
|
|
</article>
|
|
<footer>
|
|
<p>Page generated on 2008-01-11 00:49:31</p>
|
|
</footer>
|
|
</main>
|
|
</body>
|
|
</html>
|