Archive for the 'Technology' category

Dell XPS 13, one year later

Oct 06 2017 Published by under Technology

I don’t want this to be a rant, but I feel like I need to document this experience. I’ll try to stick to the facts.

TLDR; hardware issues, poor support.

The Good

It was just about a year ago that I got a Dell XPS 13 9360 Developer Edition. This laptop is designed to run Linux well and comes with Dell’s own version of Ubuntu with updated hardware drivers. They also push any changes they make upstream, which is nice. I’d read that Linus Torvalds uses one of the Dell XPS machines. He prefers a desktop, but if he’s on the road, he uses a Dell.

Design-wise, the laptop is pretty nice looking. It’s thin. It’s light. It’s attractive. Virtually no bezel – it’s all screen. Much smaller footprint than my Yoga 2 Pro, but the exact same screen real estate. The keyboard is standard chicklet that you get on pretty much every laptop these days. Nothing to write home about, but not horrible (except for the space bar, which I’ll get to shortly). Track pad is decent enough. Sound is fine for a laptop. It’s got 2 full size USB ports and a USB C. No complaints about the battery. The screen itself is nice, though a bit too high res for me. 3200×1800, again same as the Yoga. As this resolution generally causes more problems than it’s worth to my eyes, I usually set it to 1600×900, which works just fine and looks good enough to me. The palm rest is carbon fiber, which is pretty cool. Intel Graphics are meh, but it’s not a gaming machine, so that’s fine.

The Bad

So let’s start on the problems. The first thing I noticed was the aforementioned space bar. It had two issues. One, when I tapped it with my left thumb, it often would not register anything. And two, it would constantly add multiple spaces as I typed. I guess this might have been happening with my right thumb. This was a well known and documented issue. There are articles and Youtube videos explaining exactly why it happens and how to fix it. Unfortunately, these involve taking the computer apart, which I wasn’t going to do to my brand new still-under-warranty device. I decided to try and live with it, but it was pretty damn annoying having to constantly correct myself.

The next thing I noticed was a physical defect on the palm rest. I first noticed it as a small bump and when I rubbed it, the bump came off revealing a small pit in the palm rest. At first I thought maybe this was something I had done. But I wasn’t using anything near that computer that I believe could eat its way into carbon fiber. Still, I wasn’t 100% sure I hadn’t caused it somehow and it was pretty tiny, so I decided to try and live with that too.

Other than those two things, the computer seemed fine for many months. Then in July of this year – about 9-10 months into owning it, the display started going weird. It was just black, even on a new boot. Obvious first thought is some kind of video driver issue. Especially being on Linux, these things can crop up. Oddly, it worked fine on an external monitor. So I wasn’t really sure if it was a hardware issue or driver or what. It happened several times just before I went out of the country on vacation, so I decided to take my Yoga with me instead and deal with the Dell when I got back – reinstall Linux and if that didn’t fix it, I still had a couple of months of warranty left to get it fixed. But when I got back home, it was working fine. And never had the display issue again.

Then, one day a few weeks back, I went to reboot it, and it could not find any bootable media. I’m no stranger to UEFI/BIOS stuff, but nothing I did could get it to boot. No big deal, I thought, I’ll just reinstall Linux. But the machine could not even recognize a bootable USB drive. Note that I had already installed a few versions of Linux in the time I’d had the computer – just because I like to try different distros now and then. All through bootable USB drives, so I kind of know what I’m doing here. Time to call in the warranty.

Initially, Dell support was very helpful. They did due diligence to rule out user error, and then sent me a box to mail the pc in for repairs. While I was at it, I mentioned the space bar and display issues I’d been having. Up to this point, I was totally fine with how things were going. Computers have hardware issues. This is why we have warranties. I sent it in and expected things would get resolved.

The Ugly

After a couple of days, I got an email saying that there was evidence of spillage in the computer and this was not covered by the warranty. I would have to pay around $250 for repairs. Now, I knew, absolutely that I had not spilled any liquid into the computer. I suspect they might have been referring to the pitted spot on the palm rest. But this was one tiny spot right in the very center of the left palm rest, as far as you could get from any opening on the keyboard. Even if this was something I had caused, it was not the cause of the hard drive controller failure. I asked what the exact evidence of spillage was that they had found. The tech said that he would request photos of said evidence and send them to me.

That’s the last I heard about spillage. The next email was from a different tech saying that they had replaced the logic board and other components and they needed to reinstall the OS and needed my OK to do so, as it would wipe out anything I had on the hard drive. I said that was fine, I had backups. The next day I was told the repairs were done and the pc was on its way back to me.

This whole exchange seemed pretty sketchy to me. Like, “Let’s try to get the customer to pay… Nope, they didn’t fall for it, just fix the computer.” I never even argued about the spillage. I just asked for details and it disappeared.

The Uglier

So the computer arrived back. I cheerfully unboxed it, plugged in the power and pressed the power button. And… it could not find any bootable media. And it could not find a bootable USB drive. In fact, the behavior it was showing was identical to the behavior I sent it in with. A letter in the box said what they had supposedly done: replaced the hard drive, lcd panel, palmrest, keyboard, main logic board. And my earlier conversation with a tech had indicated that they had reinstalled the OS. In fact, the computer came back with a card containing a Windows license number.

I could not understand how they could replace that much hardware and the computer behaves no differently. I could not understand how they could have installed an operating system on a computer that would not boot. I could not understand why they would ask my permission to reinstall an OS over my existing hard drive but also replaced the hard drive. I could not understand how they replaced the palm rest and the palm rest had the exact same pitted spot that my old palm rest had.

The only things that made sense to me is that someone there was very confused or someone there was outright lying. I don’t think they did anything other than clean up my computer and send it back.

So, back in touch with tech support. They had me try various BIOS settings and repair images, but nothing could get the thing to boot or see a USB drive. In fact, I talked to different techs and they had given me totally conflicting instructions on BIOS settings. But I tried everything anyway. Finally, they said they were going to send someone to my house to replace the motherboard. At this point, I was fed up and said this was unacceptable. Either send me a new computer, or give me my money back.

The End

To my surprise, they responded right away saying they were sending a new computer. And it arrived. And… so far, it’s pretty good. It boots, no screen problems, no palm rest defects, and the space bar seems to work just fine. So, it all turned out well. But the whole experience left me with a bad feeling about Dell tech support.

To reiterate – hardware can have flaws. You produce millions of computers, you’re going to get the occasional dud. That’s not going to upset me as long as the company takes care of it. Sadly, the tech support experience left me with the feeling that they are either utterly incompetent, dishonest, or both. In spite of it being a nice computer, this experience has me doubting that I would buy another Dell product again.

4 responses so far

BIT-101 Lab Visual Index

Jan 04 2017 Published by under JavaScript, Lab, Technology

Screen Shot 2017-01-04 at 9.28.46 AM

I just ticked off another feature on the BIT-101 Lab list. A visual index.

Back in the old Flash Lab the only way to find a specific experiment you wanted to look at again was to click through, one by one, trying to remember the approximate date and targeting items around that. I wanted to avoid that pain. The first thing I did was to add tags and the ability to search by tags. This should help a lot. But I think this visual index will help even more. You can just scroll until you see something that looks like the thing you want to check out, and click away. It will also be good for discovery, I think.

At any rate, I think it looks pretty cool. I test-populated it with about 15 future experiments and it really starts to look great when there are lots of images in the list. I can’t wait to see it grow.

Comments are off for this post

Back to Basics

Jan 01 2017 Published by under General, JavaScript, Lab, Technology

TL;DR: Go here:

Long time readers of this blog may recall what existed here before “blogging” was a thing – the BIT-101 Lab.

Back in the late 90’s / early 2000’s there were a bunch of people running Flash “experiment” sites. Basically, each day they would post some kind of visual, animated and/or interactive Flash piece, often open sourced. Josh Davis’s Praystation, Jared Tarbell’s Levitated, Robert Hodgin’s Flight 404 were some of my favorites. In August 2001 I decided to blatantly copy them… I mean… jump on that bandwagon. My site at the time was called “KP Web Design”. Sigh. I started doing some experiments and decided I needed a better domain, so I came up with bit-101 and moved all the experimental stuff over there. It went live on September 11, 2001. Yes, THAT September 11th. So nobody really noticed it for a while. But over the next four years I posted just shy of 700 open source Flash experiments that explored all kinds of neat techniques. The site won an award (FlashForward 2003 – Best Experimental Site) and really pretty much launched my career.

In 2003 I started this blog. And by 2005 the lab was retired. I blogged heavily for several years, but in the last few years, not so much. I’ve had other interesting projects over the years, but nothing was quite as exciting as those lab days. Recently Zach Lieberman posted about his 2016 project of posting a sketch each day (sketch/experiment, same concept). It inspired me to get back to basics.

Of course, I would not be doing Flash anymore. I haven’t opened that program on my own volition in several years. (I did need to use it to examine or fix a few things for work a few times.) My weapon of choice these days is HTML5 Canvas and JavaScript.

I’ve spent the last week or so creating a site and a workflow. All the source will be posted on github at And the site uses github pages – So literally, the site IS the source IS the site.

I have template files and a script to create a new daily sketch / experiment based on the templates. This goes into a dev folder where I can work on it. When I’m ready to release it, I move it to the dailies folder, update the index.json file, add, commit and push. This updates the source and publishes the new file to the site. Because the site IS the source… etc.

One thing you’ll see in there is the use of a couple of libraries, bitlib and QuickSettings. You might be familiar with the latter. But the bitlib library is something I’ve been working on quietly for a while. It’s really just for my own use. It’s not something that I want to promote and convince other people to use and then have to wind up supporting. It’s just a compilation of the functions that I wind up using over and over. It’ll grow and change over time. Feel free to use it as much as you want – at your own risk. I make no claims for it’s production-readiness.

The site code is pretty rough. Again, I banged it all out over the last week in my spare time. But I’m quite proud of the calendar UI I created from scratch. And the tag searching and indexing. It’s even responsive and stuff. I have plans to take a screen shot of each experiment and present a visual index as well. And I’m thinking about ways to automate that index / tag generation portion. But it all seems pretty good right now for starters.

Anyway, I’m pretty excited about this. I know that on day one, there’s not a whole lot to be excited about from your end, but hopefully as the calendar fills up, it will become a fun place to visit and play with and learn from.

10 responses so far

Back to GNU/Linux

Sep 17 2016 Published by under General, Technology

My computing platform history in a nutshell.

1984 – First significant interaction with a computer. A Commodore 128 I inherited at work.

1989 – Bought my own Commodore Amiga.

Early 90’s – Was given a pc built from spare parts by a programmer friend. This was upgraded and evolved piece by piece, sometimes completely replaced throughout the 90’s / early 00’s. Eventually jumped over to laptops. This saw me through Windows 3.0, 3.1, 95, 98, 2000, NT, XP.

2007 – Got a Mac Book Pro. Fully switched away from Windows over to the Apple world.

2010 – After 3 years, while overall happy with the software and hardware experience on Mac, I was growing increasingly annoyed by Apple’s ever tightening grip over its users and developers. I moved back to Windows.

2010/11 – I then spent almost two years immersed in the GNU/Linux world. It was my daily OS. Loved it probably more than anything else.

2012 – Intrigued by Windows 8, I jumped back over to the MS platform to see what that was all about. I wound up staying longer than I had intended. Note that even while I was back on Windows as my daily OS, I always maintained a Linux tower PC that I used as a file server, media server, etc.

2016 – No major complaints with Windows 10. But it was time to get back to my favorite over the years. GNU/Linux.

Actually, I had tried to jump back about a year or so ago, trying a couple of different distros – probably Ubuntu and Mint – on my Yoga 2 Pro. I ran into a couple of major hurdles.

One was the high dpi screen on the Yoga. 3200×1800. Even when I initially got the Yoga, Windows didn’t handle it too well. And even to this day, a lot of Windows programs just don’t handle high dpi screens well. You wind up with tiny text, tiny icons or controls that get chopped off. Ubuntu was just getting to the point of addressing it, but it needed some work.

The other issue was video production. I make videos for Coding Math, Egghead, and occasionally other customers. I need software that does decent audio recording and editing, full screen capture and decent video editing.

For audio, I use Audacity, so I was covered there. Screen capture generally worked well, but I couldn’t find a decent editor. Every one I tried either didn’t have the (fairly basic) set of features I needed, or – more commonly – just crashed about every two minutes. There were a couple of others that didn’t crash but the workflow was way too complex and the performance was abysmal. I gave up and went back to Camtasia on Windows.

But recently I’d heard some positive words about video editing on Linux and decided to give it another shot. Starting out on my tower pc, I tried OpenShot. Last year it was crashing constantly. It seemed relatively stable and has a nice workflow. I was excited.

I took the plunge and installed Ubuntu on my Yoga again. I was really impressed. 99% of everything worked perfectly out of the box. I did need to tweak the trackpad a bit. The high dpi support was great, but in the end, I wound up lowering my resolution to 50% – 1600×900 anyway. It looks just as good to my eyes, you get much better performance, and any lingering issues are totally handled. It felt dirty to misuse all those pixels like that, but after a day, I never thought about it again.

Did some screen recording, fired up OpenShot and started cutting up clips and … crash. Not as bad as last year, but often enough to make it not worth using. Discouraged. Well, let’s see what else is out there. Another top contender was Kdenlive. Crossed my fingers, and tried it out.

I liked it. Used it some more… liked it a LOT. Is it crash free? mmm…. I can’t say that. But I can get through a full video editing session with 0 to 1… maybe 2 crashes, which I can live with. And so far, every time I’ve had a crash, I reopen the file and it auto recovers it to the exact point where I left off. So it’s a minor 20 second annoyance rather than something that destroys work.

There was one issue I ran into with screen recording. The solution to this issue led to some really cool discoveries that I’ll go over in another post.

One response so far

Chrome OS / Chromebooks

Jul 16 2016 Published by under Technology

I’ve been curious about Chrome OS and Chromebooks for a while now. A couple of months ago I replaced my daughter’s dead laptop with a cheap Chromebook and she loves it. The only thing she really misses is Minecraft.

Then, the other week, I got interested in the idea of running Android apps on Chrome OS. This is a recent development that only works on a few specific devices as of this writing, but will be pushed out to a lot more in the coming months. I decided to dive in and get a Asus Chromebook Flip, as it’s one of the devices that do support Android apps out of the box at this time. It’s also got decent specs at a decent price. $260-$280 with 4GB RAM and 16GB storage, plus and SD card slot for more storage. It’s also got the Lenovo-Yoga-type-flip-around thing going on, which means you can use it as a tablet or other configurations. I never use my Yoga like that, but with the smaller size of the Asus, it’s actually workable.

First of all, I’ll say I’ve had pretty bad luck with hardware on this adventure. My first flip would not accept an SD card. It just wouldn’t click in. Popped right out. I really wanted the extra storage, so I got a replacement. Second one, card reader was fine, but the touch screen was not. Phantom touches all over the place. Amazon admitted they were having issues with their current inventory and suggested I get a refund and order from another supplier. So I returned that and reordered another one direct from Google. Hoping third time is a charm. I looked at a bunch of other models and the Flip is really what I want, and beyond the stuff that was broken, I really liked the device.

I won’t try to sell you on why you should get a Chromebook, because none of these arguments worked on me. I don’t think they are for everyone. But you won’t really know whether or not you like it until you experience it. What I really liked about it was:

A. The size. Small, lightweight. Like a tablet, but with a real keyboard.
B. Great battery life. Really amazing battery life.
C. Instant on. Even if you need to reboot, it’s seconds.
D. Virtually maintenance free. Nothing to install. I can grab any Chromebook anywhere, sign into Chrome, sign into LastPass, and it’s totally my computer with all my apps there. Sign out, remove the account, and it’s like I was never there.

As far as the Android apps side of things, this turned out to be a bit of a letdown for me. Not because they didn’t work, but because once I had all my apps set up and went into the Play Store to look for apps, I couldn’t think of any that I really needed. All my web apps and Chrome apps had me pretty much covered. I tried a few anyway and for the most part they were fine. One of the more intensive games I tried crashed a couple of times. Other than that, no issues, just not as much of a need as I thought there would be. Time will tell.

So what do I use this for? Mostly for web, email, youtube. Actually watched some Netflix and Amazon Prime shows on it, no problem. For web entertainment stuff, great. General productivity stuff, also great. Google docs, etc. works nice. If I were going to do more serious typing, I’d use an external keyboard and maybe a monitor. The Flip’s keyboard is a bit small, but feels pretty decent otherwise.

Of course, a lot of people would ask about coding on the device. For me, I’m not quite sure yet. Obviously, you’re not going to run Android Studio or any large web dev ide, Visual Studio or XCode on it. But there are several Chrome based coding IDEs which are half decent.

There’s the Chrome Dev Editor which is surprisingly nice. It actually creates a localhost server to test your in-dev app, has git integration, templates, projects, publishing capabilities, etc. The github page for the project says it’s no longer in active development, but the lastest update in the Chrome store says March of this year. This editor is especially useful if you are developing Chrome Apps or Extensions. That’s really what it’s made for, although it can do regular web apps as well.

Caret is another very popular and capable editor. It’s modeled after Sublime Text, so there’s a lot there you’ll find familiar. Very extensible.

Of course, if you need to work on more complex projects, that include specialized build systems, etc. You’re going to need to jump into cloud dev. Cloud9, Koding, are some worth checking out. These all set up your projects on a server somewhere and give you a graphical IDE to edit and run that code on the server.

There’s also the possibility of running a different OS on the Chromebook itself. There is a way to get a special Linux build on there, which makes it capable of doing a lot more. Can’t speak for that myself yet, as I haven’t tried it. Here are some links on Chromebook dev:

Comments are off for this post

I made a Chrome Extension

Jul 16 2016 Published by under General, JavaScript, Technology

The other week I got a new Chromebook. Mainly just to see what the user experience was, but I surprised myself by liking it a lot more than I expected I would. But that’s another story.

I started being more interested in Chrome Apps, which work in Chrome on a regular PC or Mac as well, and started looking into the development process of Chrome Apps and Extensions. Pretty cool stuff. So here is my first extension, Chrome Apps Shortcut.

It barely does anything. Literally a one liner in terms of code. But I made it as a solution to an actual problem I had. Your Chrome Apps are displayed in a special page in the Chrome. If you use the bookmarks bar, you can add a shortcut to that location there. Or, if you use the default new tab page, there’s a shortcut there. I don’t use either of those things. I use a custom new tab page. So the only way to open the Chrome Apps page was to type in “chrome://apps” in the url field. Furthermore, because this is a custom url scheme, most methods of creating a shortcut to a web page do not work with that. At least none of the methods that I usually use. I looked for an extension that would do what I wanted, and there wasn’t one, so I made this.

All it does is put an icon up in the extensions area at the top of Chrome. You click it, it opens the Apps page in a new tab. The Code to do this is here:

[code language=”javascript”]chrome.browserAction.onClicked.addListener(function(tab) {
code: chrome.tabs.create({url:”chrome://apps”})

And even most of that is boiler plate. I just added the chrome.tabs.create({url:"chrome://apps"}) part.

There’s also the manifest, and all the icon files…

[code language=”javascript”]{
“manifest_version”: 2,
“name”: “Chrome Apps Shortcut”,
“short_name”: “Chrome Apps Shortcut”,
“description”: “Opens the Chrome Apps tab.”,
“version”: “0.0.1”,
“minimum_chrome_version”: “38”,

“icons”: {
“16”: “icon_16.png”,
“48”: “icon_48.png”,
“128”: “icon_128.png”
“browser_action”: {
“default_icon”: “icon_48.png”
“background”: {
“scripts”: [“background.js”],
“persistent”: false
“permissions”: [

And then in order to publish, you have to set up your Chrome Developer Account ($5 one time fee) and create screenshots, descriptions, blah blah blah.

All told though, from concept, to published in store, was maybe 2-3 hours. Most of that was looking up how to do stuff.

I want do dive more into packaged apps next. There are some great possibilities there. Learn more here:

Comments are off for this post

Quicksettings.js 1.3

Jul 15 2016 Published by under Components, JavaScript, Technology

Did a bit of work on Quicksettings.js recently. Mostly based on some features suggested in issues and pull requests. A quick summary:

1. A few new controls:

  •  addNumber. Basically the same as addRange, but displayed as a numeric text field with up and down buttons. Actual render may differ per browser / platform.
  •  addDate. Where supported, will show a date field with a button to click that shows some kind of date picker. In Chrome you get an actual calendar. In some implementations, it’s just a text field. Input and output are both strings in the form “YYYY-MM-DD”.
  •  addTime. Like date, but for time. String format “HH:MM” or “HH:MM:SS”. 24 hour time.
  •  addPassword. Basically, addText, but text is hidden as asterisks, dots, or whatever the platform does with it.

All of those have corresponding bind, set and get methods as well.

2. Method chaining. Great suggestion. Now, all methods that do not actively return some value will return a reference to the panel itself. So you can do stuff like:

var panel = QuickSettings.create(10, 10, "Panel")
.addRange("x", 0, 100, 50, 1)
.addRange("y", 0, 100, 50, 1)
.addRange("w", 0, 100, 50, 1)
.addRange("h", 0, 100, 50, 1)

That makes me really happy.

Here’s a master demo showing all the controls:

And all the code that creates that demo:

When you figure that almost a quarter of that code is for making a canvas and drawing a circle in it, and the rest creates everything else on the page, that’s not bad.

You can check it out, download it from here, or just use the cdn links:

Don’t forget to add one of the styles:

Comments are off for this post

Sublime Text Comment and Next Line Shortcut

Dec 10 2015 Published by under Technology

Just a quick tip. I’ve been using Android Studio extensively, daily, for the last year and a half. One minor editing feature I’ve grown to love is the way it handles commenting lines. You have your keyboard shortcut, Ctrl-/ or Cmd-/. This toggles the comment on the current line and then moves to the next line. So if you want to comment, or uncomment a bunch of lines, you can just hit that shortcut a few times and it will move through the lines and do its thing.

When I started doing a lot more personal JS work and dove back into Sublime Text, I really missed this feature. So I figured out how to re-create it.

First, you have to make a macro. Just put your cursor at the start of a line, and choose Tools -> Record Macro. Then hit your comment shortcut. Then hit down arrow. Then go to Tools -> Stop Recording Macro and then Tools -> Save Macro.

Now you just need to hook that up to your comment toggle keyboard shortcut. Go to Preferences -> Key Bindings – User and add this line:

{ "keys": ["ctrl+/"], "command": "run_macro_file", "args": {"file": "Packages/User/comment_next_line.sublime-macro"} }

Obviously, “ctrl” is for Windows / Linux. You’ll probably want “cmd” “command” for Mac. And the “file” argument is the path to where you saved the macro you just recorded.

5 responses so far

Two Pixels

Dec 09 2015 Published by under Technology

Say you are a designer tasked with creating an image. The only specs you have are that the size of the image needs to be one pixel high and two pixels wide. Seems pretty simple, right?

Just considering RGB colors, that gives you 16,777,216 color choices for the leftmost pixel. And another 16,777,216 for the rightmost pixel. Combined, that means that for that 1×2 pixel image, there are over 281 trillion different images you can create. 281,474,976,710,656 to be exact.

If you were to generate every possible image and lay them out in a grid, it would be large enough to fill over 271 million iPhone 6 Plus screens. Or almost 68 million 4K TV screens.

Two pixels.


RGB is 16,777,216 colors per pixel. Two pixels means 16 million per pixel, multiply them to get 281,474,976,710,656 different images.

Each image is composed of two pixels, so a grid of all possible images would take up 562,949,953,421,312 pixels.

An iPhone 6 Plus resolutions is 1920×1080, or 2,073,600 pixels. Divide the grid size by that, you get 271,484,352 (and a half) iPhone 6 Plus screens to display all the images.

4K resolution is 3480×2160, or 8,294,400 pixels. So 67,871,088 (and change) 4K screens to display the grid.

One response so far

Coding Math Application Series

Feb 10 2014 Published by under General, JavaScript, Technology

Last week I kicked off a new series on the Coding Math Channel. It’s the Application series.

I was thinking that it’s nice to present new concepts in each video, but there is a limited amount that I can do with them. I try to make the main episodes be 10-15 minutes long. I can explain a concept, do a few drawings, show some math, write some code, see it in action, and maybe iterate on that once or twice. And then, that’s it for that topic. Hopefully the brief example was good enough, because I’m moving on to something else now.

So my thought was to start another series where I actually build some simple app or game, or at least the barest outline of such. With some real world applications of the principles that are covered in the other videos. Each video will be in the five minute range, adding just one or two small features to the current app or game. Each feature may make use of one or more of the concepts from the other videos.

The first game is something I call Ballistics. It’s just a simple idea where you aim a gun and it shoots a cannonball that you try to hit a target. Like the old QBasic game, Gorillas.


In the first episode, we use a bit of trigonometry, including arctangent, to aim the gun using the mouse. In this week’s upcoming episode, we’ll actually get a cannonball firing, so that will use the particle class, with velocity and gravity, and lots more real world application of trigonometry. But each one is a bite sized piece of an application. We might hit the same concept over and over in different parts of the same app, or in different apps. But that’s the whole idea, to see many different ways you can use these concepts.

So now, we have the main episode each Monday, a Mini episode – shorter 5-minute simple concept – on Wednesday, and these Application episodes on Friday.

I want to thank all of you who have supported me on It really makes doing these videos more justifiable in terms of the time I spend on them. And if you are a supporter, know that only the main Monday episodes are Patreon sponsored episodes. The Minis and Applications are on the house.

Comments are off for this post

Older posts »