summaryrefslogtreecommitdiff
path: root/blog
diff options
context:
space:
mode:
authorSiri Reiter <siri@jones.dk>2016-08-06 13:16:56 +0200
committerSiri Reiter <siri@jones.dk>2016-08-06 13:16:56 +0200
commit781a2307f428d198ed9d5103a3cdb32098be9c1f (patch)
treeed0e5a6df8e7f322ce40fe8560804da416f3a4b1 /blog
parent7305b9da6bdaf455aff00c24ab09507a428e3527 (diff)
Blog entry saturday.
Diffstat (limited to 'blog')
-rw-r--r--blog/entry/160806_en.mdwn63
1 files changed, 63 insertions, 0 deletions
diff --git a/blog/entry/160806_en.mdwn b/blog/entry/160806_en.mdwn
new file mode 100644
index 0000000..dc7e58d
--- /dev/null
+++ b/blog/entry/160806_en.mdwn
@@ -0,0 +1,63 @@
+# Cleaning day
+
+Saturday is cleaning day. Day for tying loose ends. Sort, toss, tidy.
+
+The week has been about dealing with an intern as well as a pile of
+due print jobs, a few still pending, needing to get done before monday morning.
+
+I've also said yes to read and correct spelling and markup mistakes in blog
+entries for a client, possibly providing him with graphics (already did the
+creative part of that). The actual work might be postponed untill tomorrow,
+but it's better to do it today, to take out stress of dealing with eventual
+failures and mistakes. It's never fun to do that last minute before - or even
+after the newsletter is sent out. Visit the blog [Vejviseren](http://byvandring.nu/vejviseren/]
+this [Byvandring.nu](http://byvandring.nu/) Monday at noon (in Danish).
+
+I'd like to begin a new habit of backing up and updating my computer on Saturdays
+today.
+
+If I can squeeze it in, I would think it nice to spend some time in the garden,
+it needs tending. But it's probably better to postpone that for tomorrow, or use those tasks
+for a productive break from screen time. Compost, strawberry plants and the usual
+removal of a hundred out of thousands of small trees.
+
+## Touching issues
+
+Following a conversation with my partner about it, pointing towards CouchDesign,
+here are some of the subjects I've been touching with my client work this week,
+each somehow related to [our pending's list](http://couchdesign.dk/):
+
+ * layered pdf with pdf inclusion
+ * color management (for press and for print)
+ * bar code generation
+ * process documentation
+ * archive structure
+ * key signing with caff
+ * design management
+ * licensing
+ * slippy maps
+ * scss
+ * vector drawing optimization
+ * documenting work, tracking
+
+## Demerits
+
+I sent an advent calendar to the printers' shop without the date numbers.
+I somehow tied the design of that part to the producer, subconsciously presuming
+they came with the diecut drawing. I never even gave it a thought, and was
+reminded by the client asking.
+
+I struggled more, however, with dealing with a reported color failure on another
+job. It's been a while since I've had issues with that, and it took me by surprise.
+It was an office printer job. Jonas had yet another long read to deepen his already
+rather extensive knowledge on color management and to brush up on what to take
+into consideration. I've successfully taken care of it from his hints, and
+now I/we are going to document what I did.
+
+## Documenting manifesto of today
+
+Documenting a routine is not the same as improving it, even if it needs it.
+Confronted with an unfinished or dormant project, issue or bug, it is not the
+right time to deal with it. Simply document it.
+
+[[!tag daily blog couchdesign saturday english]]