This new book is smaller, has fewer projects, requires the purchase of fewer components, is an accordingly less expensive book, and perhaps most important for some people, requires no solder!
The projects consist of a steady-hand game, a touch enabled light, an alarm you can put on your cookie jar or similar container, a night light that detects when it is dark, various sorts of blinking or party lights, a musical instrument, and of course, an LED Marquee. You need just over 20 components to build all the projects, which mainly use breadboards. The book suggests which parts to buy from Jameco, and many of the parts come in one or a couple of Jameco kits. (Jameco company sells individual electronic parts, like the old Radio Shack, and also, kits you can use to make cool stuff like an Infrared Escape Robot or a Dual-Output Adjustable Linear Regulated Power Supply.)
All the instructions are clear, the illustrations are excellent, and the projects are fun, if a bit basic. This is well within the range of a seven to ten year old kid with adult supervision, and without the adults for ten and up. Depends on the kid, of course.
What I like about this book is that there are traditional circuit diagrams accompanied with descriptions of how the electronics work at a basic level. For many of the projects, you are expected to use the breadboard to assemble the parts using the traditional diagram. This is a much better way to learn the way circuits work than many other guides or books, which hold your hand through assembly at the cost of holding your hands through understanding. In many cases, there are photographs of the assembled project with sufficient detail and clarity to get you past any ambiguity. But, the key is this: The circuits are both interesting and simple, so nothing can go wrong.
There are also sections for many of the projects that help you past when something goes wrong.
The number of satellite circling the Earth right now is approaching 5,000. The number that are not broken, and are being actually used, is just over 1,000. However, Space X, Elon Musk’s megacompany, is approved to launch well over 10,000 satellites over the next several years, to serve a single purpose: Give broadband internet to every human on Earth no matter where they are.
Unless it is cloudy, I guess. I mean, Satellite TV does not work when the weather is bad.
Not to be a curmudgeon about this, but I wonder if this increases the likelihood of a Kessler event?
There are important details. Most of these satellites will be in low orbit, and a large number will be in even lower orbit. I assume this means that of the several thousand satellites circling the Earth at 1,000 to 1,400 km, there will be a regular replacement cycle, because don’t low orbit satellites’ orbits wear down?
You know all those projects where you wire up some electronic circuitry and then hook it all to a bunch of LEDs, then you have fancy or fun lighting? Like a Halloween costume, or a Griswald house, or some nice mood lighting in your home?
It is harder than it looks, though doable if you have a soldering iron and some basic electronic knowledge. The RocketLife project, which is starting a kickstarter any day now, claims to make this much easier.
From the press release:
Light by RocketLife is an easy-to-use hardware and software system that adds dynamic lighting to almost anything. Unlike conventional systems that are limited to one color at a time or preset patterns, Light allows anyone to create multi-layered effects that blend and move with rich color transitions, sparkles, and natural motion effects that tell a story.
Light provides creative home and business lighting that’s perfect for animated signs, retail displays, holiday lighting, club and DJ lighting, sparkling DIY crafts, mobile bling for bikes and cars, flashing wearables for nightclubs and parties, creative costumes, PC mods, and dramatic works of art. Light’s integrated Bluetooth LE lets you control it all from your iOS or Android device with the included LightMobile app.
Create a Mood, Enhance an Occasion, or Just Have Fun — Plug & Play Easy for Everyone to Use
Light by RocketLife is plug-and-play easy for everyone to use. Beginning users can simply connect the compact LightBox Bluetooth device to the included LED strip and choose a lighting effect on their phone for instant atmosphere. Or anyone can load a photo into the included Light Effects Designer Software, draw virtual lights on top, and quickly light up a home or other project. For more advanced users, designers, audio/video enthusiasts, lighting pros, makers, and other creative people, the Light hardware and software also include numerous options to add Light to interactive art, games, and other electronic projects.
Here’s the movie:
I am reviewing the hardware and software, and I’ll let you know if it is a good investment for your holiday lighting or summer time biking! Stay tuned (review likely out in early December).
Meanwhile, you can sign up for the advanced kickstarter launch notice HERE. That link will get you to the project’s website where you can find out more.
The LEGO Boost Creative Toolbox is a humanoid robot that is also a guitar, a dogbot, and an industrial fabrication machine. Which of these things it is depends on which set of instructions you follow. A scratch-like programming language lets you control the boost from a phone or tablet, via blue tooth. It is not cheap, but it is an amazing and excellent toy.
It does take absolutely forever to build any of these projects, but there are stages along the way where you can stop and play with what you’ve got so far.
And, if you are clever, you can combine the Lego Boost parts that come with the kit with other Lego objects and make more different things. For example, if you happen to have the LEGO City Arctic Scout Truck (60194) , which is in and of itself a fun LEGO kit, you can combine some of the Boost parts with this kit to make something special. Like this:
But, the problem with that project, and several like it, is that even on the LEGO boost site, there is relatively little information on how to do it. Not that you necessarily want step by step instructions. You really want to learn how to hack the LEGOs with the Boost and have fun creating. But I think it is helpful to get a bit more guidance, to get farther with the first few stages of this sort of project.
And that is why Yoshihito Isogawa wrote The LEGO BOOST Idea Book: 95 Simple Robots and Hints for Making More!. This excellent book has, as it says in the name, 95 specific ideas that come in the form of typical LEGO non-verbal visual instructions (but nicer looking than actual LEGO instructions) to do very specific things, like how to make a sliding door, how to launch rockets, that sort of thing. Each project comes with the code blocks specified to make it work.
In a way, deploying many of the ideas in this book, and using them as part of an overall LEGO build you’ve otherwise got going, may be more fun than the Robot itself, especially after you’ve messed around with the robot for a few weeks.
For example, we have a large and complex LEGO Angry Birds Kit, which includes an angry bird launcher that uses basic finger power like a lever. Not any more! We are going to build an actual rocket launcher that launches the angry birds, you betcha!
Now, I want to be clear about something. All of the parts that the The LEGO BOOST Idea Book uses in its descriptions are part of the LEGO Boost kit itself (#17101). But the principles laid out and the design ideas could easily use other bricks from your general collection. This give you the best of both worlds: Total functionality using the book itself as an add on to your Boost, adding significant value to that expensive kit for only a few bucks more AND a way to leverage all those other books, because you can extend the projects pretty easily with your own imagination.
I guess I would say that if you get a LEGO Boost Kit, you really should get this book along with it. Great gift for a kid this holiday season. Best ready to build robot on the market (possibly) with a truly meaningful extension.
That was the amateur geek electronics project of the 1950s and 1960s.
For younger kids, there is also the more recently developed Snap Circuits, which are pretty good and fun until you are about 8.
But today, with inexpensive microcontrollers like the Arduino and small computers like the Raspberry Pi,and significant advancements in LED technology, the game has been upped, and with the mere ability to follow instructions, you can make a plethora of projects that blink, whirr, and amaze your neighbors.
DIY 10 LED Projects for Geeks: Build Light-Up Costumes, Sci-Fi Gadgets, and Other Clever Inventions by Jon Baichtal (ed) provides instructions to get you up to speed with LEDs, to make a UFO, a dice roller, a music visualizer, an automated infrared remote control, an optical screwdriver, an LED costume, and numerous other things. Since you will want to solder many of these things (though you could get away with not for several of them) there is even a chapter on soldering.
This is not the most basic electronics book. Watch this space for a review of a recent and excellent volume that serves that niche. These projects are challenging, but they are also very adaptable. Though these are LED projects and thus light up, LEDs also admit infrared, so you learn to handle that technology as well. All project books have a couple of LED projects. This brilliant book focuses on the bright lights themselves.
The instructions are clear and VERY well illustrated. Each project comes with a very clear set of parts you’ll need. Many projects use Arduino controllers.
You will learn about available electronic components you may not have known about but will suddenly need. For example, there is a tiny card that goes on the end of a USB cable and allows serial output directly to an infrared stream. How cool is that? You can take over the world, with that!!!
I’m going to use the technology from one of these projects for a lamp for my bathroom, and I’m going to build a version of the digital dice roller. Had I gotten this book a few weeks earlier, Huxley would have gone out Trick or Treating as a light up flashing ghost in stead of a plain old ghost.
Just so you know, here is the list of contributors and their brief bios:
John Baichtal has written or edited over a dozen books, including the award-winning Cult of Lego (2011 No Starch Press), LEGO hacker bible Make: LEGO and Arduino Projects (2012 Maker Media) with Adam Wolf and Matthew Beckler, as well as Robot Builder (Que 2013), and Hacking Your LEGO Mindstorms EV3 Kit (Que 2015). He’s hard at work on his latest project, a compilation of Minecraft projects for Maker Media. John lives in Minneapolis with his wife and three children.
Contributors to 10 LED Projects for Geeks:
Kaas Baichtal became interested in computers and electronics around age 12, taking every available electronics class. As a technician Kaas worked mostly in the entertainment industry, doing equipment repairs and travelling system installs for theatrical dimmer manufacturers AVAB America and Electronic Theatre Controls (ETC) as well as multimedia integrator BBI Engineering. Kaas has run her own servers at home since 1998 and specializes in writing custom code to solve real life problems.
Matthew Beckler is a computer engineer who lives in Minneapolis with his wife and two cats. His day job usually consists of writing firmware for fancy microcontrollers, and he is a co-founder and engineer of a fun side-hustle called Wayne and Layne, where he and Adam Wolf design and sell electronic kits and help create interactive museum and art exhibits.
Kristina Durivage is an independent software developer by day and a hardware hacker by night—specializing in data visualization and making the world a brighter place with LEDs. Her work is collected at portfolio.gelicia.com and her opinions and cat pictures can be found on Twitter, @gelicia.
Lenore M. Edman is a co-founder of Evil Mad Scientist Laboratories, a family run company that designs, produces, and sells hobby electronics kits, drawing machines, and retrotechnological objects. She writes for the accompanying project blog on the topics of electronics, crafts, cooking, science, robotics, and anything else that catches her fancy. Many of the blog’s projects have been featured at science and art museums and in Make, Wired, and Popular Science magazines. She holds a B.A. in Interdisciplinary Studies; English and Greek.
Mike Hord has been working at SparkFun Electronics designing products and projects for makers for six years. His making skills run the gamut from metalworking, woodworking, and 3d printing to coding and circuit design. When not creating his next Big Hack, he’s raising two small children to question the veracity of everything except the need for toothbrushing.
James Floyd Kelly is a full-time technology writer in Atlanta, Georgia. He has written over 25 books on a mix of topics that includes Open Source software, LEGO Robotics, basic electronics, Arduino programming, and more. He and his wife have two young boys who are showing the early signs of Maker-ness.
Michael Krumpus has a master’s degree in computer science and 25 years of experience as a software engineer. He discovered a passion for electronics design later in life and formed a small electronics company, nootropic design, where he designs and manufactures innovative electronics for hobbyists, designers, educators and industry. Michael is based in Minneapolis, MN.
Windell H. Oskay is the co-founder of Evil Mad Scientist Laboratories, a Silicon Valley company that has designed and produced specialized electronics and robotics kits since 2007. Evil Mad Scientist Laboratories also runs a popular DIY project blog, and many of its projects have been featured at science and art museums and in Make, Wired, and Popular Science magazines. Windell was also a founding board member of OSHWA, the Open Source Hardware Association. Previously, Windell has worked as a hardware design engineer at Stanford Research Systems and as a research physicist in the Time and Frequency Division of the National Institute of Standards and Technology. He holds a B.A. in Physics and Mathematics from Lake Forest College and a Ph.D. in Physics from the University of Texas at Austin.
Adam Wolf is a cofounder of and engineer at Wayne and Layne, where he designs DIY electronics kits and interactive exhibits. He also does computer engineering and embedded systems work at an engineering design services firm in Minneapolis, MN. When he isn’t making things blink or helping computers talk to each other, he’s spending time with his wife and sons.
First, lets get one thing straight about Phython. If you (or, maybe, your kid) is going to learn to code, you’ve got to learn Python. It isn’t the only coding language out there, and depending on what you do with coding, Python might be something you do all the time or almost never. But it is a good bet that the arbitrary future coder will be coding in Python in the future.
Python is both simple and complex, easy and hard. I think it is probably easier for people who have never previously coded to learn than for old timers who cut their teeth on structured languages. Python actually is structured, but it is also object oriented. If you don’t know the difference between the two, don’t worry. Suffice it to say that the following works:
This is using a command interpreter, demonstrating that Python is sort of like a command line language if you want it to be. I entered Python statements and got instant results. That is not how Python is usually run, but it can be helpful.
Notice that I created a “list” which is an object that includes a list of things. I cleverly made the list, in its original form, a sentence of sorts. I then printed it so you could see that the list indeed has stuff in it. What I did there could be done in a similar form in virtually any language, though the concept of a “list” in Python (as opposed to the very similar “array” or “matrix” in other languages) is much more powerful than demonstrated here.
Then, I did the object-oriented thing. I called up the list (“aList”) but with a dot followed by a thing that made that list change. It became sorted. I then printed it.
Anyway, enough messing around. Python is a great and powerful Oz of a language, and it is very widely used, which means that there are a LOT of powerful libraries that can be drawn on to do a lot of things.
If you, or your kid, plays around with a Raspberry Pi, then you’ll want to learn Python because that is the handiest way to program it.
So, back to the Python Flash Cards. There are helpful and just plain fun. As you learn concepts, you can go through the cards and use them exactly like flash cards (because they are actual flash cards) to both review and backfill gaps in your knowledge.
The topics on the cards range from “what is a string” to how to loop through lists (yes, you can loop through a list) to how to define classes and methods (that’s object-oriented stuff, where you make your own object oriented mojo like the “sort” thingie we used above).
The flash cards are not available yet but will be out in a few days. You can pre-order. They will come in time for the holidays, and they are, in fact, a great holiday gift for your 11 year old future programmer.
The Manga guides are Manga art graphic non-fiction books that cover a wide range of topics. This new guide covers, obviously, cryptography.
As with all of these guides, there is a story centered on someone motivated to learn stuff. In this cae, Inspector Jun Meguro seeks to bust an art thief who uses ciphers to ply that trade. Meguro learns about the history and origins of cryptography and code making, what the different kinds of encoding are, and the basics of modern methods including public keys. There is math, but it is all doable. It is a fun reading for manga fans of any age, or people who just want to spend a few evenings learning the basics without with very manageable descriptions. It is not a watered down version of cryptography, just a very accessible one. Not the be all and end all, but an excellent jumping off point.
Authors: Masaaki Mitani is a professor at Tokyo Denki University’s School of Engineering specializing in digital signal processing, communication, and educational engineering.
Shinichi Satou is an assistant professor at Tokyo Denki University’s School of Engineering specializing in signal processing and educational engineering.
You can actually download the Python code and have the game without learning anything beyond how to download then run a Python program. You can not download anything, and follow the book through all the stages of development, making the occasional and learning from your mistake. Or, you can download the code, and do a combination of entering it yourself, cutting and pasting, and slowly building up the program, for a less frustrating (frustrations caused by your typos) yet very educational experience.
(Also, the game uses sounds that you can download from the same source as the source code.)
The code is actually remarkably short given the complexity of the game. As the reader develops the game, they are guided through the process of understanding what the various code blocks do. Someone who goes through the book pretty carefully, and works with the code though most of it, will get a basic understanding of how to use Python to write other programs.
The book sues Pygam Zero, which is a graphics and sound library.
Since this is Python, it works on all the usual platforms.
Here is a video of the game:
This is a fun book, and though I’ve not completed the process of making the game, I have worked through quite a bit of it. This is a good way to learn Python, in my opinion. Might make a great holiday gift for a gifted younun’ looking to up their game in coding games.
This is not a book that fully explores the alliance and overlap between war and makers of war on one hand and science and scientists on the other. Authors Neil deGrasse Tyson and Avis Lang focus on one part of that relationship, the link between astrophysics and related disciplines (really, astronomy at large) and the military.
Back when I was working in or near the Peabody Museum, in Cambridge, the museum’s assistant director, Barbara Isaac, hired me to work with the NAGPRA database. NAGPRA was the North American Graves Protection and Repatriation Act. Ultimately, large swaths of the Peabody Museum’s collection would be turned over, or some other thing done to it, as per the wishes of the various Native American groups associated with that material. Most of the work had already been done. But, Barbara is a meticulous person and wanted to make sure the dotting of each i and crossing of each t was double checked. So, I was one of two people charged with going over the printouts, on that old green and less green striped paper, bound in large blue cardboard books. Each line (or two) was an item or collection of items, with notes, and an indication of what was going to happen to the material. There were just a few options, but the basic idea was this: An item listed was either going to be returned to a tribal group, or not. My job was mainly to look at stuff that was not going to be returned and, given my ongoing scan of what was going to be returned, and my knowledge of North American prehistory, ethnography, and archaeology, to earmark things that said “do not return” but where maybe we should be returning it. So, for example, after noting that a particular South Dakota Lakota tribe would have this, and that, and this other, soapstone tobacco pipe returned to them, when I saw that the ninth pipe on the list, several lines down and all by itself, is labeled to not be returned, I’d earmark that. Nearly 100% of the time, that ninth pipe was just something that nobody wanted, or it didn’t really exist (not all museum databases are exactly accurate). But, it would be earmarked.
Many items on the list had information as to how the item had originally gotten to the museum.
Many, many items, especially items taken from Native Americans living in what was the frontier between about 1840 and 1900, were taken by medical doctors who, as we all know, also stood in for naturalists, or some kind of traveling scientist, on military and quasi military expeditions (Like Darwin).
And many of those items were taken for use as medical specimens.
We initially learned that Native Americans have a particular blood type because, in part, of studies done on blood stains on shirts of slain warriors, collected after various battles with the US Army units accompanied by such scientists. There are a few famous cases of Native American bodily remains, mostly but not all skeletal remains, sitting in the anatomy teaching rooms of this or that college. But a lot more, a lot not noticed by either historians or even the all seeing all knowing Wikipedia, are or were sitting in museums around the world. Collected, by scientists wearing military uniforms, on military ventures, with a scientific twist.
So the science-military link is not exclusive to astronomy and astrophysics.
I wrote elsewhere about the person I met who was taking Pentagon funding to build an object that would help cure cancer. An example of a scientist subverting the military funding process. And so on.
OK, my complaint.
The authors have two long chapters (and references elsewhere) covering the early history of human endeavor in general (not limited to military) and the evolution of astronomy, mainly as it related, over a very long period of time, to navigation. One chapter covers land, the other the sea.
Staring somewhere along the way in each chapter, we get a very nice, well done, and pretty full description of the process of humans learning about the stars, about the earth and how to find one’s way, etc. But prior to that, the authors do what so many authors do and I so much dislike. I’ve written about this before. We get a version of human prehistory, and indeed, current human variation (or at least, ethnographically recent), that is bogus. For example, the authors speak of the first modern humans wandering around in the Rift Valley of Africa. There is no evidence that modern humans evolved there. Using just the archaeology, southern Africa is a more likely origin, and the physical anthropology record is simply incomplete. There are early fossils there, but that is because the rift valley is and was a big hole that made fossils. The entire rest of the continent is big, and the evolution probably happened there, not in the rift.
Similarly, ethnographic variation we see in the present and recent times is stripped out. For example, most rain forest dwelling foragers are not known to have a sky oriented cosmology, or to use the sky for much information about seasonal change in ecology, or navigation. And, there have always been a lot of rain forest dwelling foragers.
MIT Technology review has a fascinating writeup on efforts to build electric planes. In my view, these efforts are at the same time shooting too low (the result would be the equivalent of flying short buses, at most) and possibly doable (which is good).
Have you ever noticed how much electricity weighs? Here is an experiment you can do. Get two identical alkaline batteries (small ones, like AA size), one totally discharged and the other fully charged.
Now, hold one in each hand and see if you can tell which one is heavier. Is the charged up one heavier?
No, of course not. Electricity stored as potential energy in a battery actually weighs nothing. This is an interesting idea. Airplane fuel does weigh something, but electricity itself does not. If only we could create a battery that weights almost nothing to carry all that weight-free electricity!
OK, now, while you are still holding the batteries, try something else. Do this quickly, because you don’t want anyone asking you “why are you holding these batteries” right now, because you’d have to say, “I’m trying to see how much electricity weighs,” and that is kind of a stupid question.
Hold the batteries over a hard surface that you don’t mind dropping a battery on. Maybe ten inches to a foot above the surface. Hold them upright. Now, drop them on the surface and see how they act.
The “full” battery, the one with the charge, will normally bounce better than the “empty” one.
After reading this, I had this thought: Have a relatively small battery i an aircraft that does not use the same exact technology as the long distance battery, and is good at ONLY rapid output of a lot of power, and is replaced and recycled after every flight. Ideally, the plane would actually drop the battery once it is done using it. Neighbors of airports may object.
How to erase specific autosuggested URLs from Google Chrome?
You know the problem. You are accustom to swooping into the URL entry space on your browser and typing the first three or four letters of a website you commonly visit, hitting enter, and getting where you need to be. But Google Chrome, it an undying effort to be as helpful as possible, starts suggesting subpages of that site you visited once before, and are unlikely to visit again, ever.
For example, you want to look for something on Amazon. So you type in “Amaz” and suddenly the correct URL comes up, you hit ENTER and there you are. That is how it used to be. But now, you type “Amaz” and hit enter and you are now looking at an entry for a specific light switch you searched for last week. Forever. From now on, all of your searching on Amazon will start with this one light switch.
How do you stop this madness?
Simple: Once the URL you don’t like is visible in the search bar, use the down arrow key to put the focus on that very same URL down on the list that will also appear below the search bar. Then, use Shift-DELETE to eliminate that URL forever. Or any others.
Shift-DELETE simply removes that URL from your search history. Don’t worry, it will not delete that actual web site or anything. Totally safe.
Some of the earliest LEGO sets were for buildings or some sort of structure, and to this day architecture forms a core part of the LEGO panoply. If you build an architecture project from a kit, you’ll see that they are highly engineered. In order to make a LEGO project look like something other than a concoction of random bricks made by some kids having fun (which is, of course, just fine), serious planning has to have happened.
Most of the LEGO books I’ve seen are pure idea books. If you wanted to build a project based on what you see in the books, you have to either have a huge collection of LEGO parts very well organized, or you have to be prepared to order several specific bricks that are called for in the books.
But that is the wrong way to play with LEGOs. The books demonstrate concepts, give you ideas, guide you to become a better LEGOer.
How does this work? Let me give you an example. Say you want to build a building with nice columns. There are many different kinds of columns out there in architecture land, and you can imagine that there are different ways to build each one, and which method you use depends, in turn, on the scale you are working on. Say you want to build columns that would go with a building that would work well with the assumption that the building will be used by minifigs (the small LEGO people that come with many kits). Finch gives you sixteen pages of ideas for columns, starting out with these two:
The wizzard behind the book, Alice Finch, is one of the top LEGO builders in the world, famous for her extensive renditions of Harry Potter’s world and other major projects (see below). This is a great book for the aspiring LEGO builder, and an excellent choice as a holiday gift for your LEGO-loving offspring.
First, let’s get this one thing out of the way. How do you pronounce “SQL.”
Donald Chamberlin, the co-developer of SQL, pronounces it by saying the letter out louse. Ess Cue Ell. However, many computer science teachers prefer “sequel” and in at least one poll, the latte won out. One of the most common implementations of the database language is mySQL, and that piece of software is officially pronounced “My Ess Cue Ell” and not “Mysequel.”
I myself have never once uttered the word “sequel” when referring to this database system. I have also never once uttered either the term “Jiff” or “Giff” in relation to *.gif files. They are, to me, “Gee Eye Eff” files. I admit, however, to calling *.jpg files “Jay pegs” even when they are not *.jpeg.
But I digress. We are here to talk about a new book, on SQL.
The book provides what you need to know to create databases and set up relationships. But don’t get excited, this is not a dating book.
See, a “database” isn’t really a thing, but a collection of things. Normally, at the root of a database is a set of tables, which look like squared off sections of spreadsheets, or highly organized lists, if you lay them out. But then, the different fields (columns) of the tables are related to each other. This is important. Let’s say you have a table of individuals in your club, and each individual has a set of skills they bring to the table. It is a model railroad club, so you’ve got engineers, artificial vegetation experts, landscape sculptors, background and sky painters, and so on. Also, each club member has a known set of days of the week and hours that they are available to meet or to manage some event you are having. Plus, they each have lunch food and drinks preferences for when you order out. Three of the members drive wheelchairs. And so on.
You have a table of dates and times that will be when your club will meet over the next year. You have a list of venues you will meet in. Each venue is associated with a different deli where you order out. Some of the venues are not wheelchair friendly, while some are.
Imagine putting together a big chart that shows all the events, who is going to them, what everyone will eat, what everyone will do, and special needs requirements, for the next ten years.
If that was one single giant structured table, each time a given member was included on a sublist because he or she, there would also be all the information about the person’s address, phone number, email, food preference, skill, etc. etc.
So you don’t do that. Instead, the database is taught to associate the name of each member with that member’s personal file, including all that personal information, in a way that lets you selective ignore or include that information. Then, the database lets you construct new, novel, virtual tables that combine the information in a clever way.
For instance, for an upcoming event, you can have a to-do list that includes which materials to order for a build of a new model, and whether or not the person who helps Joe with the wheelchair thing should be sent a note to remind him to definitely come, and a precise list to send to the corner deli, as well as the phone number of the deli, for lunch, and so on.
Tables, linked together with relationships, which are then mined to make these novel tables which are called queries.
You may need to import data, export data, clean up errors, you may be using a GIS system, creating automatic emails or mail merge documents, and at some point you might even want to analyze the data.
The book assumes you are using PostgreSQL, which is free (and there are instructions to get it) but all SQL systems are very similar, so that really doesn’t matter too much.
Everybody who works with data should know some SQL. All desktop operating systems (Linux, MacOS, Windows) use this sort of software and it runs about the same way on all of them. Just so you know, you are using SQL now reading this blog, because SQL or something like it lies at the base of pretty much every common way of serving up web pages. Prior to you clicking on the link, these very words were in a database file, along with the name of the post, a link to the graphic used, etc. etc. A bit of PHP code accessed the data from the SQL database and rendered it into HTML, which was then fed to your browser. SQL is one of those things that lies at the root of how we communicate on line, and the basics of how it works and what you can do with it have not changed in a long time. The first relational models go back to 1970. Remember “dbase”? That was an early version, deployed in the early 1980s. By the mid 1980s, everything you can do with modern SQL, to speak of, was implemented.
A huge amount of energy is spent going to the store. The grocery store, the hardware store, all the stores. The amount of energy spent to get an object to the store for you to buy is big, but this process is on average highly efficient. A train can hold a lot of objects, and pushing a train down the tracks is highly efficient. Also, we will hopefully eventually be running trains entirely on a combination of electricity delivered to the train indirectly, batteries, and bio-fueled generators on board. Delivering object for you to buy at the store is already efficient, but it will become more efficient with a relatively small number of (big) step.
But then everybody leaves their home and drives various distances to various stores. When I was a kid, there were two grocery stores in our neighborhood. One had no parking lot, the other had room for about five or six cars, but nobody drove to either one. We used those two wheel carts you drag along to the store (or laundromat). When you get to the grocery store, you fold the cart up and hook it to a push car, then, when you pack up your groceries, they go in that two wheeler and you drag it home. Everybody did that all the time. It was strange to drive your car to the grocery store.
I remember when my parents started to drive to get groceries. Instead of going to the store on foot (or more likely, sending one of the offspring to the store with a list), they would drive out to the edge of town to a large warehouse discount store that had sprung up, like a Cosco. Oddly, large suburban style grocery stores emerged, in my world, after these edge-of-town discount store. My parents would drive the station wagon out there, spend all day, come back and and fill the freezer and cupboards. Maybe once every six weeks. In between times, for milk and other perishables that you can’t freeze, it would be walking to the A&P. So that was all pretty efficient.
But today, tens of millions of Americans get in a car and drive a few miles to pick up some object or bunch of objects at the stores. The energy spent to do that is large. The total amount of energy we spend going to the store to get objects is probably less than the total amount of energy spent to get objects from producers (via warehouses) to stores, but not by as much as you might think.
One way to solve this is to not go to the store in a car and by an object. Order it on line. The delivery will be more efficient. Or, in some cases, go to the store on foot, bike, or public transit, get your your stuff in a big pile, and then have the store deliver it to your house. And, have all the delivery done by electric vehicles charged with energy produced without fossil carbon.
I envision a future in which we abandon mail boxes and replace them with small rooms with an indoor and outdoor access, some insulation and modest climate control, a place to put frozen stuff, refrigerator stuff, other stuff. That’s where the grocery store delivery service drops your stuff.
Or, if you are in need of new flat packed furniture, Ikea:
In a couple of years, if you buy a Malm bed at Ikea in Brooklyn and opt for delivery, Ikea will probably drop it off in an electric truck. The company is transitioning to zero-emissions delivery in New York, Los Angeles, Amsterdam, Paris, and Shanghai by 2020. By 2025, Ikea aims to do the same for every store worldwide.
“Climate change is no longer just a threat, but it’s a reality,” says Jesper Brodin, CEO of Ikea Group. “We see how that impacts our business, our customers, and our coworkers more or less everyday . . . We want to be a leader, and take action, and speed up our plans.”
The company had announced earlier this year that it would shift to zero-emissions delivery by 2025, but now plans to work more quickly in key cities.
But where do you get one of those nice delivery receiving futuristic mail boxes with the climate control?