I have always liked lists over paragraphs of text in web design, but I have always struggled with capitalization, punctuation and detail level which should be included in the list and when to use an ordered list and an unordered list. Someone from my past recommended something like “only use a ordered list when the person should do things in a particular order” which made perfect sense and I remember it to this day, but I like this article that I noticed recently because goes into much more detail about all of the aspects of lists and gives many examples of what to do and what not to do.
Authoritative data source (also referred to as System of Record) is an interesting concept I learned about a while ago and began using immediately. It’s the idea that any piece if data (a person’s name, email address, phone number, etc.) ideally should be stored in only one place, and if it needs to be duplicated, typically for improved performance, one of the locations should be considered the correct, or authoritative, one.
If stored in more than one location, any workflow which changes that information should update it in the authoritative location and then update it in any secondary locations. Alternatively the workflow could update the authoritative data and then a batch process could update any secondary locations.
As the graphic suggests, this concept helps address item 3, accuracy, of data.
I originally learned to code many years ago in C when I was in college. Back then everything was functions where you had a “main” and which called several functions in the desired order. Since then Object Oriented Programming has emerged and, after several attempts to wrap my head around it, after reading several articles like this one, I get the concepts, but I have never been able to really be comfortable with it. Maybe I need to use it on a project to really allow it to sink in.
Edit – In re-reading the article I recall the largest issue I had, using the object oriented approach many different types of objects can be created and manipulated, but I never figured out how to save an object’s data to the database.
A long time ago when I was working with Web Services I got turned onto the idea of resume content in XML format and having a variety of DTD displays, some more serious and others more creative. At the time I found a open source framework which does this and, more recently, a web based application, but looking back I realize that:
- This can/should be done using more modern standards such as html and CSS, which the web application may use
- Although it’s cute to have a variety of looks for a resume, having one professional format is all that is needed
- For each job application the content of the resume should be tweaked
If I didn’t have my own domain and web site (this one) on which to post my resume, I would probably use that web application to store my base resume and modify for each job application.
Ed Note: Speaking of resumes, I recently found an interesting article defining the goal of a resume, the different audiences who may read your resume and providing advice on how many bullet points each job description should have, what verbiage to use which may be good, etc. As always, don’t believe everything you read online and use your best judgement when hearing anyone’s advice.
Before going to sleep instead of reading a book, I catch up on my news feeds using feedly on my phone. Although many people say reading your phone before going to sleep is bad but for me it helps me relax and puts me to sleep, sometimes even waking me up from my early slumber because my phone fell onto my chest. Sometimes you shouldn’t take other’s people advice too seriously and just do what works for you.
Anyway, the reason I mention this is because when I come across an interesting article I have the Pocket app on my phone and, with one click, I can save the interesting article to pocket, I’ve collected quite a few articles, some of them still pertinent and others out of date. I mentioned this habit to a friend of mine who reads my blog and suggested I post these articles to here, partially to share with the world, but also to consolidate; now that was some good advice.
So my next group of posts will be information which were previously saved and transferred here. I’ll try to only post articles that are timeless, but some may be a from older articles.