2018-12-28 (F) Weekly Summary

I am a bit of a sucker when it comes to alternative computer interfaces so when this article about forearm vibrators translating dialog to the wearer, I wanted to know about it and tell others.

Most of the time I would say that I put function before form but these speakers, which are based on the tapering spiral of shells, were too pretty to ignore. The halves were printed on a consumer-grade printer, and the sand texture does a phenomenal job covering the print layers and hiding imperfections. That is a good hack.

Every contemporary hacker knows what a Pi and Arduino are and many have connected them with a USB cable. It is a logical way to make these powerful, yet inexpensive pieces of hardware talk to one another. One person made an interface board which gives the two boards a place to communicate where their voltage level differences don't matter and software so they can speak the same language.

This was in the Hackaday tip line, and it was roughly six months old, so every other writer there had a chance to see it. It was a diamond that had been passed over because there was no link, it was merely a couple of images someone had posted in a hackaday.io chat. Regardless of the coverage, this was a brilliant solution, and it caught the eye of Hackaday's editor-in-chief, who put his own touches on the article.

I personally enjoy wordplay a great deal. This hack involved tying some unrelated systems together to create a service which would answer single-word text messages with portmanteaus of that word and others which shared the first letters with the last letters. To have some fun, I wrote the article as though it were very important, I mean world-changing, creation..

The rest of the summary posts have been arranged by date.

First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.