Snowy Sunday

With knowing it was going to be a snowy Sunday and nowhere to be. Besides my remote JavaScript Book Club at 5:00 PM, I didn’t set my alarm this morning or most Sundays.

Start of My Morning

I woke up at about 7:56 AM. laid in bed, and read until after 9:30 AM. Then I got out of bed to watch some cooking and farming videos on YouTube. I figured I could spend my lazy morning learning something.

Not Ready to Learn

I knew I wasn’t ready to learn JavaScript by watching my Wes Bos “JavaScript for Beginners’ videos. Maybe later this afternoon or this evening.

After watching videos, I cooked up a dozen breakfast sausages I had thawed out the last night. They had been in the freezer since the summer. I figure they would be getting a little freezer burn, etc., and they were.

Cooked Breakfast

While the sausages were cooking on medium-low heat, I washed dishes. Then I chopped the sausages into smaller bite-size pieces to make sure they’re cooked thoroughly. I then could use them in salads later, and with the four eggs, I was getting ready to scramble and cook for breakfast.

I toasted up some Wegman’s sliced garlic bread. Then I added strawberry preserves to one slice and apricot to the other. Once all that was done, I ate it while watching one more video.

Snow Shoveling

Then I got dressed to go out and shovel the sidewalk, walkways to each of the doors, and the back porch. With not having a car anymore, my shoveling is way down by many hours, depending on how much snow we get. I only had to make a path in the driveway.

Today was easy because we only got an inch and a half, maybe two inches at most.

Off for a Walk

After shoveling was done, I went for a 45-minute to an hour walk of over two and a half miles. I took my time to wander the neighborhood and see what was going on.

Home from Walk

Once I was back home, I cleaned up a few spots on the sidewalk and then went into the house. With being cold and a bit achy after shoveling I took a long hot shower. I know TMI.

Then I laid on my bed to read a bit on Twitter and see if I was ready for a nap, and I wasn’t.

Writing this Post

So I started writing this blog post after making a large bowl of popcorn on my stove with some oil and a little bacon fat. The bacon fat made for some tasty popcorn. I got myself a GT’s Gingerberry Kambucha and some water.

The next thing I do before a possible nap and book club is edit and post this blog post.

Then it’s outline/write a draft post about writing blog posts every day of January.

Possible Dinner Plans

Thinking dinner will be leftover curried coconut milk shrimp with elbow noodles, farro, corn, greens beans, and roasted Hatch Chili’s. Most likely, it will be a salad with greens that look to have seen better days.

More Lazy Weekends

So here’s to having more lazy Sundays or even weekends with not much to do but relax, read, nap, etc.

Check Your Draft Blog Posts First

Today when looking at my drafts to see if there was an old post, I could edit, update, etc., and then post. Because like others, I have old posts I got most of the way there and then never posted them or forgot about them.

When I got near the end of the list of drafts, I found a post about “Progress About ‘Places to Eat’ Web Application” (future posts). I already had old content about the 10K Apart contest and places to eat that I recommend. Along with starting a newsletter, etc., that I ended up writing called “Looking to Start a Newsletter of Places to Eat.” The old one had much more detail.

The old one needed a bit of finishing/updating and was almost 1,300 words. So I broke it into two posts for now that I can use later. Since I recently talked about these subjects. It will be better to post them after doing some research on starting a newsletter platform to use. Or at least which one to use when first starting.

Look at Your Old Posts First

So please look at all your drafts before starting a new blog post. You might even want to read some of them to see if the content is similar to what you wanted to talk about that day.

Here’s to finishing up old blog posts and getting them out in the world or deleting ones you don’t want anymore.

Your Website Needs Color and Contrast

NOTE – I found this old blog post in my drafts, so I did some time editing it, link checking, etc., and hit publish of an old draft.

To Read Your Content

To allow people to read your content, you need to make sure to have the color contrast as high as possible. So people can read what you have written. It shouldn’t be so high that it bothers people with low vision. Were too much contrast makes it difficult for them to read.

Putting light text on pastel or light backgrounds is not good for some people. You also have to think about the different types of color deficiencies (colorblindness). Meaning you don’t want to have red text on a green background, etc.

A Useful Tool

Below are a few different tools I use to check color contrast. The color contrast tool I use the most is Jonathan Snook’s web-based “Colour Contrast Tool”.  It’s the tool I use to check color contrast for the development team at work or if I have chosen will work.

W3C Recommendation for Color Contrast

Here’s the W3C recommended values from the WCAG 2.0 – 1.4.3 Contrast (Minimum) Level AA.

Following these guidelines ensures that foreground and background color combinations provide enough contrast. This pertains to those with color deficiencies. To pass your text and background need to have a color contrast ratio of at least 4.5:1 or higher to pass.

How High Should Your Color Contrast Be

You also have to think about how the web page or application is going to be used. Now, if it a heat index application that is likely going to be used outdoors. You have to consider most high heat index days will probably be in bright sunlight. So blaring sunny will not work well with a contrast ratio that passes b a little bit.

Color Deficiency or Colorblindness

Another tool is the “Color Oracle.” It’s used to simulate different types of colorblindness. They have Windows, Mac, and Linux versions created by Bernhard Jenny, Oregon State University (programming), Nathaniel Vaughn Kelso, and Stamen Design, San Francisco (ideas, testing, and icon).  The application places a color overlay for your entire main screen. You can set up different PF or function keys to turn on and off different types of colorblindness masks easily.

Doing this allows you to check against the three main types of color blindness. About 10% of the population is colorblind. Most of them are males. The three main types of color blindness are:

  • Deuteranopia or deuteranomaly (a form of red/green color deficit) – 7.5% of all males.
  • Protanopia or protanomaly (another form of red/green color deficit) – 2.5% of all males.
  • Tritanopia (a blue/yellow deficit- very rare) – Less than 0.3% of women and men.

More Tools

Next is the full list of tools I would you for building websites. Your choice will depend on how you work and what’s best for you.

I hope these tools are helpful to you in checking for color contrast issues.

Additional Reading

For a more detailed look at color contrast, you need to read Todd Libby’s color contrast article called “Contrasting Accessibility with Color Contrast“. You should also follow him on Twitter at @ToddLibby.

Any Recommendations

If you have any other tools that you use and think I should checkout, please leave a comment, and I will give them a look.

How I’m Using GitHub

I have had a GitHub account since March 6, 2013, but I never used it until much later in 2016.

I started working on a list of places to eat when I traveled and using GitHub to backup/store my code.

First GitHub Use

My first use of GitHub was on September 30, 2016, when I created my first repro for the place to eat project. At some point, I purchased the domain name GottaEatHere.com to put the information on. I bought a bunch more domains because I wasn’t sure what I wanted to call the application.

Reason for Using GitHub

The reason I started the project was for the An Event Apart and Microsoft 10K Apart contest. Besides, people had been asking me for recommendations of where to eat. So I figured I build a small web-based application to kills two birds with one stone. The contest was where people had to build an application in less than 10 kilobytes (KB) of code.

I spent some time upfront figuring out how best to do that. I wanted to learn PHP or at least get better at it, so that’s where I started.

Planning the Application

My first thoughts were I would need two or three Kb for CSS. Then another three Kb for my HTML template, and the remaining Kb for logic to render the pages content.

I decided to use JSON files because I wasn’t sure if a database would count against the total of 10 Kb. Which allowed me to learn something else new too.

I worked to get my PHP application to render a list of five or six cities, and I think five restaurants I loved going to. Each city had its know JSON file, and they were half Kb in size or something like that.

The 10 Kb or less version of the application had a lot less information per city and restaurant. I think it had a name, address, phone number, URL, and a short description. Now it has a bunch o other information.

A person chooses a city was from a drop-down list. Then the PHP would read the JSON file for the city that a person picked. Then render the restaurants for that city. Nothing fancy, but it got the job done. I didn’t expect to win anything, and I didn’t.

Of course, the whole time, I was making sure it was as accessible as possible.

Using GitHub Daily

On November 18, 2016, I started making more commits to add more places to eat along with more cities, along with information.

November 18th was the day I started making at least one commit or added an issue to GitHub every day. It might have been for new fields, cities, states, etc., to GitHub every day.

Over the last four and a half or so years, I have only missed doing something on GitHub about a dozen times. So that works out to three or four times a year. I’m okay with that and don’t lose sleep over it if I do. Some of the updates and issues were related to my slides, and others were for code examples for the slides.

My use of GitHub is still through their desktop application. It lets me create new repro’s, create issues for new features, cites, restaurants, etc.

With only me working on the projects, I have not had to worry about creating branches, merging others’ code, etc. At some point, I need to learn how to do that through the application or the command line.

Need to Learn More Git

So here’s to learning more Git. Be it through the GitHub application or, more importantly, through the command line.

Looking to Start a Newsletter of Places to Eat

I’m thinking of starting a newsletter about places to eat when people travel. That is when it’s safe to d so again. But I can give you an idea of restaurants to go to that I recommend.

I think it was over two years ago I set up a MailChimp newsletter related to places to eat when traveling. So I need to look for that information again and see if that is still valid. In the meantime, I need to start working on a few drafts of places to eat.

At some point, I need to check that the places I love to go to are still open after the pandemic.

I think I would send the newsletter out once every two weeks to start. They would have five or six places to eat in one city or state.

Ideas for Newsletters

Each newsletter would include a place to have breakfast, lunch, and dinner. They would also include somewhere to go in for a coffee, tea, etc., to get work done or relax. Along with a place for an afternoon snack or a beverage, and then a place for a late-night meal.

Some of the newsletters might have more of one type of place or another if I cannot decide which place to add.

For the larger cities, there might be many newsletters because I have found so many places to go in that city.

It won’t all be larger cities. There will be ones on places like Buffalo, Rochester, or Syracuse, NY, or Joshua Tree, CA, Akron or Columbus, OH, or Jackson, MS, Annapolis or Frederick or Grasonville, MD., etc.

Multiple Newsletters for Larger Cities

Some of those cities would be New York City, Washington, DC, Portland, OR, Seattle, Los Angles, San Diego, etc. I have so many places in those cities to suggest that I would recommend.

So for those cities, I would showcase places in a particular neighborhood. So that way you can walk to all the restaurants if you want and spend a day getting to know an area of that city.

Newsletter about a Given Food Type

Other newsletters might be on a specific topic. Such as places for Ramen, pizza, hamburgers, ice cream, Chinese food. Or maybe whole in the wall places, BBQ, vegetarian/vegan, etc.

Are You Interested?

Please leave a comment if you’re interested in signing up for an e-mail related to places I recommend. If so, I will notify you once you can sign up for the newsletter.

Or ones that might be in your home town that you suggest I go to at some point.