If you want to get started doing coding and you don’t know anything about coding, then do this tutorial: How To Build a Website with HTML | DigitalOcean
I say this for a few reasons:
- It’s a thorough step by step guide to building a website. You will learn quite a bit about HTML by the time you are done, but you shouldn’t feel overwhelmed or that you are missing things.
- This should be approachable by anyone from age 10 to 110. (Maybe 5 to 115…I don’t know. You get the idea.)
- You will also learn about developer tools, in this case, Visual Studio Code. A text editor is fine too, but learning new tools and how to effectively use them is better.
- If you go here, you will learn how to host it using Digital Ocean and Github. So not only will you build a website, but you can show it off to your family and friends, too 🙂
- Lots of good practices in here including in this tutorial. Always a plus.
Give it a try. Even if you already know a bit of HTML: you might find your skills much increased by the time you are done.
(Photo by Andrew Neel on Unsplash)
Sounds impossible, but if you go here and watch the enclosed video, you will feel confident you can watercolor too: How to watercolor: In under 3 mins.
That particular post comes from Danny Gregory , who has a great blog for all of us artists. (That’s you too). Well worth reading.
I used to be a big fan of about.me: they enabled me to create a personal home page far better than what I could do. Unfortunately they stripped out some of the things that made the page look great, and when they did that, I decided to make my own about.me page, using free hosting on Github.
First off, here is what my page looks like: http://blm849.github.io
Here’s the steps I took to make it.
Before you start, here’s what you will need if you want to follow my steps. You’ll need:
- a text editor. Notepad or Textpad or vi will all work fine.
- some knowledge of HTML. Not too much. If you just follow the steps below, you should be fine. If you want some quick knowledge of HTML, see this: HTML Tutorial
- some knowledge of git and github.com. Again, not too much. If you follow the steps below, you should not need any. If you want some quick knowledge of git and github, see this: How to learn github fairly easily | Smart People I Know
- Some words describing yourself that you want to have on the site.
- An image file of yourself that you would want to serve as the background of the site. The one I had was a simple photograph I took with my smartphone.
- A working file directory on your computer to hold your files.
Here are the steps:
- Set up your site on Github. To do this, follow the steps, here: GitHub Pages – Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live. Check it out. Use your working file directory to store the files. Once you complete the steps, and pointing your browser at http://username.github.io works, you are going to want to personalize the site. (Note: username = the name of your userid. e.g. my userid on github is blm849)
- Use a repository from someone else to make the job simpler. To create my site, http://blm849.github.io, I used a repository from here: https://github.com/weightshift/The-Personal-Page. It’s great. I simply downloaded the ZIP file, unzipped the files, and copied and replaced the files in the working file directory. In your case, I would recommend you take my repository and my files and modify them. I’ll explain in a bit. My repository and my files are here: https://github.com/blm849/blm849.github.io. Click on the “Clone or Download” button and then click “Download ZIP” to do this. Like I said, download the zip file, unzip the files, put them in your working file directory.
- Also, copy your background image (e.g. background.jpg) into the working file directory.
- Now edit the index.html file in the working file directory. Make the following changes and then file index.html:
- On line 5, change the text between <title> and </title>. This text will appear on the browser tab when someone opens your site.
- For lines 41-51, replace the lines I have in here with the words describing yourself. The only HTML I used here is:
- the <br> tag to add some blank lines before the line “My name is….”. I found it looked better when I did this.
- the <p></p> tag to format the words into paragraphs. Again, it makes it more presentable.
- the <b></b> tag to make my name bold. I wanted it to stand out. If you don’t, remove those tags.
- the <a></a>tag to have links to other web pages about me. If you don’t have links elsewhere, you can remove those.
- On line 58, replace “blm.jpg” with “background.jpg” (assuming that the file name of your background image is called background.jpg. If it is called something else, use that file name instead.)
- Once you have made the changes and saved index.html, open it with your favourite browser. (To do this, right click on the file and select “open with…” and pick your browser.) Check to see if the words are correct and the background image is correct and the formatting is correct. If not, you will have to go back and edit the file and fix your errors.
- Once you are happy with it, do the following:
- Delete any background image files in the working file directory that are not yours (blm.jpg and nh_bg.jpg)
- Enter: git add –all
- Enter: git commit -m “secondary commit with my own information”
Enter: git push -u origin master
- Point your browser at http://username.github.io and make sure it works.
One final note: I recommended using my repository and not the original one I worked on. I did that because I had some problems with displaying my page on my iPhone 6s plus. I added some files and tweaked the index.html file to get it to work. By using my package and my index.html file, there are less changes for you to make, I believe. That said, I am grateful for the code from the original repository and I am making sure I credit the owner of that repository (as should you).
Food52 has a number of good guides to making dishes and sauces without a strict recipe, including this one: How to Make Any Pesto in 5 Steps.
Once you do it once or twice, you will more or less be making it without a recipe.
I’d encourage you to skip basil and pine nuts and go with other greens and nuts, especially greens you may have in your fridge that are about to give up the ghost. I found that the combination of the oil and the greens give the pesto it’s sauce quality, while the nuts and cheese and garlic give it the flavour. So if you don’t like garlic (really?), drop it. Likewise if you have nut allergies. For additional flavour, add some wine vinegar, balsamic vinegar or lemon juice to taste at the end. And of course, add salt to taste.
Why you should make pesto is easy: once you have it, you can add it to food in all kinds of ways to make your food tastier. It is a very versatile sauce.
Once you have pesto, you can add it to roast meats or vegetables. I opened up a boneless pork roast, spread it on the inside, and closed it up. You could do the same with a boneless chicken breast. (Or add some to just cooked fish.) I tossed my roasted vegetables in a bowl with some pesto until they were lightly and evenly coated.
Another idea is to make a pasta sauce with 2 parts pesto to 1 part cream and warm them in a pot while you cook some pasta until it is al dente. Then drain the pasta and toss it with the sauce until the pasta is covered.
If you have some tomatoes, quarter them and lightly toss them with some pesto for an easy salad.
Or take 1 part mayo and 1 part pesto, combine, and use as a sandwich spread.
Lots of ways to use pesto. Enjoy!
(Image via a link to the Food52 post.)
Here’s a place you can start: Hadoop For Dummies.
. IBM (my employer) is providing it. Once you get through this, there are lots of places online and in bookstores to get more information. But this is a good place to start.
As one of my areas of skill development this year, I am teaching myself Python (the programming language). I had a number of different sites offering help with it, but I have found these three the most useful, so far. I have found each of them useful, but I have spent the most time on “medium”. If you are interested in learning Python, I recommend you check these out:
Fast: Tutorial – Learn Python in 10 minutes – Stavros’ Stuff. Great as a cheatsheet or a quick intro to Python or if you used to do work with Python but haven’t done it in awhile.
Medium:the Python Tutorial from python.org. If you know other programming languages, this is a good starting point.
Slow: Learn Python the Hard Way. Good if you don’t know much about programming and want to make Python the first language you know really well.
Posted in IT
Tagged IT, Linux, SSL, tutorial, VPN
I’ve been planning on making bread for…well, years. I made it decades ago, but for various reasons, I never got back into the habit of making it. The last time I tried was after I picked up the book “Artisan Bread in Five Minutes a Day” and hoped to jump on the no knead bandwagon. But the boule I made wasn’t very good and the book and my bread making went back on the shelf.
Two things happened to me recently to give it another go. First, I found a new copy of “The All New Purity Cook Book”. This book is the one I grew up with, and it is heavily oriented towards bread making. An old cook book, but a great one. Second, I wandered into a store and found a Black and Decker refurbished bread maker for a $29. I decided it was time to try making some bread again. You can see my results above. (And yes, the shapes are off, but hey, I am learning, just like you will be!)
Veteran bread makers won’t learn much from my notes below, but new bread makers might. Things I learned:
- Of the three approaches, the bread machine is the easiest. Not surprising. What I also learned is that the no knead and the traditional way are also not so hard. But the bread machine is still simplest. If you are feeling a bit courageous, skip buying the machine and try the other methods.
- I had fresh flour and fresh yeast: both are cheap, and if you aren’t sure how fresh yours are, I suggest you get some new stuff. Stale yeast and flour that is old and off will make it hard if not impossible to make good bread.
- I used to fret over water temperature and air temperature when I used to make bread, but this time I relaxed and just made sure the water was not hot and not cool, and didn’t worry if the temperature was 110F or some exact measure. It still worked. Likewise, for a warm place, I just stuck the bread in the microwave to rise. It was fine. I didn’t have to worry: the house wasn’t drafty or cool, but the microwave works well if it is drafty or cool in your place (or you have excessive AC, maybe?) Of course, don’t turn on the microwave while the dough is in there.
- My bread maker made a lot of noise at first and moved around a fair bit on the counter. Be careful not to have it too near the edge, and if all bread makers are as noisy as my refurb, don’t put it on before you go to bed.
- There’s not much to making bread maker bread, but follow the instructions. I made an exception for seasonings they wanted to add to the bread. I skipped those. But when it comes to water, oil, sugar and salt, flour and yeast, stick to the recipe.
- It didn’t call for it, but I brushed some butter on the bread after I took it out of the oven. It looks better in my opinion.
- As far a the five minute artisan bread, I messed it up the first time I tried it today. I tried it again, though. First, I halved the ingredients in the book for the master recipe. This was fine. Second, the trick to blending the flour into the water is to measure out the flour and slowly add it before you add more. The first time I more or less dumped it in and the dough was very difficult to work with. Also, the water ratio they use seems to be a bit slight. There’s always more flour then I can blend. I ran luke warm water, wet my hands, then mixed the loose flour in. It took me a few goes at this before I managed to incorporate all the loose flower into the dough. Without that extra water from my hands, I couldn’t get all the flour blended.
- The other benefit of halving the ingredients is that you have less bread in your fridge. It takes very little to mix up a new batch and my fridge is small and I don’t have room for all the dough they make with their recipe. If you are the same situation, chop the recipe quantities in half.
- The authors of the no knead bread recipe stress kosher salt: I used plain old table salt and it worked fine.
- Other than the things I mentioned, the no knead approach works great and the bagette I made was delicious: slightly chewy on the outside and nice a tender on the inside. I like the bread maker, but if you wanted easy bread, I highly recommend that book.
- Finally, I did the traditional approach and made the challah bread. There’s a few more steps, but it’s still really easy, right up to the part where you braid it. The braiding is not easy but the recipe itself is easy: you just need time.
- Rather than type in the recipe I used, I recommend this recipe because of the highly detailed description of how to braid the bread. My recipe had all the same ingredients and steps. Two exception: 1) in my recipe, after the dough has risen for 1.5 hours, I punched it down to deflate it and then formed six equal sized dough balls. And then I covered them and let them rest for 10 minutes. Then I started to braid. When the braid was formed, I brushed it with vegetable oil. 2) It also has more sugar than the recipe I made: mine only used 4 teaspoons of sugar for the whole recipe: this one uses more and the result should be a sweeter bread.
- This recipe will result in a whiter challah bread than others I have had. I suspect those recipes have more egg yolk added to the bread. It’s still delicious white.
Good luck making the bread. I am sure you will make nicer looking bread for sure.
If you just bought or are thinking of buying a Raspberry Pi, then two things:
- Read this: How To Set Up Your Raspberry Pi For The First Time – ReadWrite.
Not only will it help you get set up, but it also has a list of projects to get your started on doing something useful with it. As well, there’s some links to other resources.
There’s lots of material on Raspberry Pi’s on the Web, but if you haven’t found them yet, try this one at ReadWrite and get started.
It is easy to feel stupid if you are trying to learn how to use github and you are not a software developer. Many of the github tutorials are aimed at people who are software developers and who have used similar tools. What can seem obvious to them can seem bafflingly to you when you are trying to understand the workings of github. (e.g., if you are not used to source control, then getting your mind around what state your file can be in at any given time in the process can be confusing.)
Despite that, if you are committed to learn how to use Github and git (the basis for Github), I recommend you take the next four steps:
- Start with this two part tutorial: GitHub For Beginners: Don’t Get Scared, Get Started – ReadWrite (part 1) and GitHub For Beginners: Commit, Push And Go – ReadWrite. I really liked this series. It assumes that you aren’t a software developer and that you may have tried using github and gave up. I highly recommend you take an hour and walk through both parts of this tutorial. When you are done, you will have feel that you have a good start on being able to use git.
- If you still feel like you want some more practice and you want to try some new things with git in a safe environment, try this interactive tutorial: Code School – Try Git. It will also teach you some additional things that you will find useful that you didn’t learn in step 1.
- Now that you are more comfortable with git and github, this Git Reference site walks you some of the same material, but goes into detail and explains it more. By the time you go through this, you should be alot more confident about what you are doing with git and github.
- Lastly, I like this site: git – the simple guide – no deep s–t! (It’s where the graphic at the top of this post comes from). It’s a great summary of the things that you’ve learned, and it has an excellent cheat sheet on the top left of the page that you will want to keep handy.
Some additional thoughts: your use of git and github can be as simple or as complicated as you want it to be. You could have a simple repo on github with one or more files that only you use. Later, you could start cloning other people’s repos, making changes, and making them into your own repo. From there you could get into working with teams of people, branching and merging your files as you go. During that time, you are learning as you go. Don’t be afraid to a) make backups and then b) make mistakes. Eventually you will gain mastery of it and be able to use it to your full advantage. Better still, the material you share can be used by others, and that’s a great thing.
Posted in IT
Tagged git, github, IT, tutorial