markjgsmith

2020/01/17 #

• cat << EOF > New Linkblog feature: rss, atom and json feeds

  The latest linkblog feature is feeds. These are a versions of your linkblog that are easily readable by a computer. This makes it easier for people to read your linkblog but also enables you to do neat things like auto post your links to social media such as Twitter and Facebook. Each time a day finishes where you posted links, the hash link of that day gets added to your feed.

  

  To access your feed, right click on the icon in the toolbar (it looks a bit like the Wifi symbol rotated by 45 degrees) and select copy link address. This should copy the url of your feed to your computer's clipboard.

  If you then paste it into some form of text editor you will see what the feed url looks like. Here are my feeds for my regular linkblog and for my custom domain linkblog:

  https://linkblog.io/users/mark/feeds/daily/rss https://links.markjgsmith.com/feeds/daily/rss

  The advantge of using your custom domain url is that theorectically if you ever needed to move your linkblog to another provider, then as long as you still own the custom domain, that could be done without the people already using your feed having to update to a new url.

  If you try to load these pages in a browser you'll see lots of strange looking text with HTML tags, but you will also notice that your daily posts are within <item> elements. Computers can read these feeds easily. The vaste majority of the time though you never need to read the actual feed, you only really have to copy and paste the urls of the feed.

  The most common type of feed is RSS so that's what is used in your navbar. Atom and JSON versions of the feed are also available by replacing 'rss' in the url with 'atom' or 'json'.

  A very typical thing people do with feeds is add them to their feed reader, which makes it possible to read many sites from 1 place rather than have to remember to visit all the sites individually. Seen like this, feeds are very similar to the follow feature in many social media sites, they have the advantage of working across many different sites, though they are a bit more complicated.

  Feeds also make it possible to do things automatically with your posts, like posting them to sites like Twitter or Facebook. For example I have setup my linkblog so days are posted to my Twitter account @markjgsmith. There are lots of 3rd party online sites that offer rss-to-[insert favorite social media site] type services.

  For a more detailed description about feeds check out the You Need Feeds site. Also useful is this list of rss feeds for social media sites which might give you some ideas about what is possible.

  If you want to try out running a linkblog then signup for the 14 day free trial, after the trial it's just a few dollars per year.

  EOF

• cat << EOF > Setting up as a freelance web developer

  There are lots of reasons for doing freelance work, whether it's for what people refer to as a side hustle or whether it's more of a full time freelancing goal, but in all cases it's necessary to have a minimal infrastructure setup. You fine tune this over time and adjust according to the direction of the projects. Broadly speaking the essentials are payments, contracts and some form of marketing.

  I got some of the details from this article from an audio on soundcloud called Web dev freelancing high level overview basic setup. The author makes some good points and is worth the listen.

  Payments

  Freelancers need a way to receive payments. There are a lot of online services that specialise in providing services for freelancers. Freshbooks seems to be a favorite for a lot of web developer freelancers. I hear it mentioned a lot on podcasts. Whichever service you choose, you will need to create an account, connect it to Paypal, and connect it to your checking account. It's a good idea to setup a seperate checking account for your freelancing work than your personal banking account. Then it's a good idea to test out the setup by sending a $1 invoice from Freshbooks, pay and ensure that the money reaches your paypal and then bank account.

  Another possibility here is to use a partly self hosted solution. You will need some web development skills, but you could use the Freelancer project (One of my projects) to host a payment site that uses Stripe as the backend payment provider. You can host the code on a public Github repo, so customers can inspect the code if they want.

  Joan from Toptal contacted me after reading this post to inform me that they have just released a freelance calculator tool that could be useful to easily figure out your hourly rate and yearly income. Thanks Joan!

  Contracts

  You will need some basic freelancer contracts that will clearly set out the project goals and responsibilities, and a way to send these contracts back and forth securly. Docusign has been recommended a lot, but there are other similar services available online, easily findable via Google search.

  As far as the contract google search 'standard exchange of services contract' or 'web development contract' and use one of these as the basis for your contract. Make sure that the contract contains at least the following:

  • State that you will build website, describe the website, pages, api etc
  • State the price for building the website
  • Client will pay 1/3 before, 1/3 midway, 1/3 at the end
  • After contract finishes, will leave project
  • Hourly rate applicable for maintenance after contract finishes, should be arranged as a seperate engagment

  Also worth checking out is this article that has lots of details about freelance contracts.

  Marketing

  Some way to promote your services, this doesn't need to be too envolved initially.

  A basic website with a logo, contact details, short description of the services offered. Something you can add to the footer of your emails, it will be useful for referals too, a way for other to point people towards you. You might want to setup a blog at some stage, but initially a basic 1 page website should be enough.

  How to deliver

  General advice is to deliver a working website using new accounts for hosting and give these to customer as a deliverable. Hosting your customers website is not advised.

  Now you have the basic infrastructure to make proposals, draft contracts, and receive payments.

  Related posts:

  List of freelance web development websites and marketplaces

  List of remote friendly web development job board websites

  EOF

Today’s links:

• Microsoft will be carbon negative by 2030 - In this piece they outline a very extensive plan that will hopefully result in them being carbon ‘net zero’ by 2050, it’s good to see them lead in this area, it would be even better if other companies around the world followed in their footstepsblogs.microsoft.com #

• Daily Overview photography of the Australia Bushfires -It looks terrifyingwww.getrevue.co #

• What happens when words don't translate between languages - Something that is probably quite topical for programmers, naming things is difficult, it’s interesting to see the variations in how other cultures and languages approach this aspect of communicationwww.bbc.com #

• Throw Me a Lifebuoy - Debugging Node.js in Production with Diagnostic Reports - Useful debugging tools and techniques for issues that fall outside of the space of easily debugable bugsm.youtube.com #

• New Post: New Linkblog feature: rss, atom and json feedsblog.markjgsmith.com #

• New Post: Setting up as a freelance web developermarkjgsmith.com #

• What are you self hosting? (2020)lobste.rs #