Artificial Intelligence in Nature


When you think of Artificial Intelligence, what comes to mind? Is it Spielberg's 2001 movie? Is it the Matrix? Is it your computer beating you at Chess? Or the characters within a video game who clearly have no form of intelligence, as they continuously fire at the walls? However which way you think of artificial intelligence, there's pretty much one commonality - electronics. Computers are thought to be a series of wires and connections, all made working through the magic of electricity. And there's no reason for you to think otherwise, because after all that's how it's always been.

Take a look at your computer... consider: if we had a really good artificial program available, and it was running on your computer, where would the consciousness lie? Somewhere inside the inner workings of that box, no doubt. And because that box looks somewhat utilitarian (unless you have a shiny, glossy Mac), because that box can remind you in some ways of HAL, you may feel a little fearful of this thinking box. Again, if you have a Mac, you're probably not fearful as it reminds you more of something like Hello Kitty instead of HAL So imagine yourself asking this thinking computer a question, what would it say? And how scared would you be, as you thought about how this thinking box made of wires and chips, is a conscious being...

Those who may know a thing or two about computers know that computers work on this thing called binary. What exactly is binary? The short answer is it's a shorter name for binary system - a system of two states. An on/off switch. Computers are composed of many many on/off switches, rapidly turning off and on. Music, movies, photographs have all been turned into binary instructions - turn the switch off here, turn it on here, on again, on, and off here - voila! But media is a far more extreme version of binary instructions - that's why the file sizes are so huge. The most basic form of binary is the number system, in which you can immediately see how powerful binary can be.

As an example, how high can you count with your fingers? 10? Maybe 20, if you're creative. How high can you count with binary? With a single hand you can count to 31. With two hands, you can count to 1023. How? By thinking of your fingers as switches.

For simplicity's sake, I'll explain one hand. Assigning 1 to your thumb, 2 to your index, 4 to your middle finger, 8 to your ring finger, and 16 to your pinky, you can represent all the numbers from 0-21. 0 would be a closed fist. 1 would be extending your thumb. 2 would be extending only your index. 3 would be extending your thumb and your index. 4 would be extending only your middle (beware not to count 4 while looking angrily at someone...), 5 would be thumb and middle... And hopefully you can see the pattern.

Hopefully from that, you see the power of binary - the ability to cover a wide range with as few switches as possible. As an aside, there are trinary systems and quantum systems which are currently being worked on which will be eons more efficient than binary, but that's not why I'm writing this.

Another thing you hopefully picked up on is the fact that your hand, when counting binary, is a computer. That is, it has a series of switches (5), which can be turned on and off. But, wait! No electricity!

The fact is, the reason why computers use electricity is because electricity is ridiculously fast. So fast you can only appreciate it's speed by ridiculing it. It's the fastest method to flip those tiny switches on and off, and that's why computers are made of wires. By making those switches ever-so-tiny, electricty can rapidly fly aroudn the circuit board, and we can build faster and faster computers, allowing for more and more computational power. But there are non-electric computers out there - the problem is they're a lot bigger, and are more prone to damage. They also can't compute a whole lot - but if you have a lot of tinker toys laying around you can program your own tic-tac-toe game, with built in AI.

Electricity, and particularly the fact that all the wires and circuit boards are locked up and out of sight, allows us to be very removed from the computer. We don't see the little switches rapidly turn on or off, and most of the time, we don't even think of it as happening. We look at the monitor and accept that as the physical manifestation of our data - reason why some people attack their monitors and not their towers when something goes wrong. And because we're so removed from the computer, AI becomes this mysterious thing that makes for a great movie. The wires inside a box remind us of a brain - and we're far too removed to know what's going on inside there. There's a lot of mystery within that little box.

But here's an interesting note: I've already established that computers don't need electricity, they just need a bunch of switches, and some sort of flow to turn the switches on and off. So let's get imaginative - what if we had a really big mountain. A huge mountain. One where a river flowed rapidly from top to bottom. And along this river we put a bunch of logs that could be rotated to one of two positions that we designate as on or off. And then we managed to feed in instructions into this massive mountain of a computer (massive computer of a mountain?) In short, instead of a small black box with an HP/Dell/IBM logo on it (or a white box with a Mac logo on it, and a built-in monitor), we had a massive mountain, with water as our electricy. For the sake of argument, let's say this mountain-computer could process at the same rate, or faster, than electrical computers. Imagine now, if we ran an AI program on our mountain computer. We would have a thinking mountain.

Now, we have no mysterious HAL-esque box. We don't have wires and tiny electrical circuits. We have a big mountain with massive logs, a flowing river, and probably a very loud computer, as those logs are rotated to on/off positions. Go ahead and ask it a question... and while you do, let me ask you a question... Where does the consciousness lie on our thinking mountain-computer?

Popular

Let's Clear Up The Ambiguity!

Image
Job seeking is hard - especially when you factor the ambiguity around expectations, the lack of transparency and consistency around process. It's frustrating dealing with the sheer subjectivity of everyone's opinions. Just think of even the basics: How long should your resume really be? Traditional black and white, or modern? Should you include a headshot? Oh - and cover letters - are those needed? Is anyone actually reading the cover letter? What are they looking for? Is there a bias for people with a more traditional background? Worst of all: The dreaded typo  that you catch only after applying to your dream job.  Are typos really going to cost you the opportunity??? To help bring some clarity to the process, I surveyed a bunch of hiring managers. The results were really interesting, and very illuminating.     If you're on the job hunt, I hope this information helps out! One final note: My recent post,  7 Steps to Writing an Amazing Resume , factors a lot of this feedba
Read more

Work Experience vs Professional Experience

Image
In reviewing a bunch of resumes this week, I noticed quite a lot of resumes with a  "Work Experience"  section. In each of those resumes, people had de-valuing some very valuable  experience - and I write that with no exaggeration. The problem is people were looking at their experience purely through the "Job Title/Relevancy" lens and had reduced their experience down to a list of discrete, random, disconnected jobs. No interconnectedness, no narrative thread weaving through it all. As much as you may feel some jobs have no way of being connected, the reality is  you   are always the connection . To not connect them on your resume is to lose all that growth, knowledge, skills, impact, value, and trajectory. In other words - you lose the " You " in the resume. I recommended they start with a small change. Reword "Work Experience" to "Professional Experience" because, ultimately, every single job they had was in service of building their
Read more

FAQs for a Software Engineering Hiring Manager

Image
Technical Interviews have evolved a lot since the early I transitioned from being a Software Engineer to an Engineering Manager. Particularly in the post-Covid era, there's been a greater emphasis on the person, which I think is an important and welcome change. Over the decade of interviewing hundreds of coders, I've also had the pleasure of working with various bootcamps, colleges, and hundreds of individual job seekers on LinkedIn. Across all the changes over the past years, across the various locations and mediums, something remained consistent throughout: The questions I get asked.  With that in mind, I thought - why not make a FAQ from my perspective as a hiring manager? While this is my perspective, it's based off years of observation and supporting data. But that being said, advice is not fact. You may disagree with certain points, and that's OK. Opinions we disagree with allow us to better understand our own views. At best, I hope these responses help you
Read more

7 Steps to Writing an Amazing Resume

Image
  Since sharing my resume template  I've received plenty of feedback from job seekers, HR and hiring managers - all of whom value its purpose. Two (now former!) jobseekers even shared that as soon as they used my template, they were getting calls. Something about this template works, and given the traction it's getting others, I wanted to share - in more detail - why  this approach works so well.  Before continuing, let me give an important disclaimer: This resume isn't a miracle cure that's going to land anyone their dream job. Unless they're filled with lies, resumes are only as good as the candidate themselves. But they can also be a whole lot worse. This template and approach are all about maximizing the potential candidates have by highlighting and summarizing key areas.  Last point before beginning: If you don't know me, it's worth stating this advice comes from more than a decade of having hiring a broad range of coders: straight out of college, high
Read more

7 Steps to Building your Portfolio MVP

Image
Often when I suggest to coders that they build a portfolio, I'll hear back: "I don't need one..." "With all the effort it takes to apply, where will I find the time?" Simply put, having a portfolio's never going to hurt your chances at landing a job - it can only help. That second question is where a lot of struggle - because applying to jobs can be time consuming. Especially if you're wrapping up a bootcamp, or having to manually type in your resume info after uploading your resume. That's why I made these 7 steps which, when done correctly, can really help you stand out with a hiring manager. And, the best part is, it should only take you 2 days. Being the Agile-Obsessive that I am, it's all about maximizing value while minimizing effort. Fix links to your Resume, GitHub, LinkedIn, etc. at the top where they're always accessible. Link to everything here - and then remove all other links on your Resume except your Portfolio link . It sa
Read more