In my post about using regular expressions to find matches in a text file, I promised to tell you about the two applications I used to help me write my regex. By the way, Regex is what the cool kids call Regular Expressions.
Let’s state the problem to be solved first. If you have a text file where you want to change something that’s repeated throughout the file, it’s pretty easy to do a search/change all. We do it all the time in text editors. But what if you have a text file that is repeatedly generated and always has the same thing wrong with it? Maybe it’s a date in the wrong format. Or maybe an online system hasn’t been updated with your new company name. Or what if instead of changing the text, you just need to know what the text actually says? Let’s say it’s a date in a document and you want to write a script to change the name of the document to include the date? All of these examples are a great place to try out regex.
We’re entering chapter 3 of my quest to provide chapter markers in the podcast. The original request was from Joe LaGreca but since I’ve started talking about it on the show, people have been coming out of the woodwork saying, “Yes, please!”
I have been working my little fingers and brain to the bone on this and I’ve figured out a really geeky solution. But first, let’s walk through what doesn’t work.
To review, I record the show in Hindenburg Journalist. I stop recording when I end each topic anyway, so it’s super easy to hit ⌘-control-enter to add a chapter and then type in the subject. The problem is that Hindenburg isn’t embedding those chapters on export. The dev and I have gone back and forth a few times and they seem to be saying that the chapters should be maintained, but they’re definitely not in the file.
In this episode of Programming By Stealth, Bart ties up the last of the loose ends related to web forms. He teaches us about form events, which are critical to making our web forms not only accessible to screen readers but to allow our users to tab around to the different fields and interact with them without using a mouse. We learn about the keypress event and learn what it means for 31 to be the space key.
This week Bart Busschots joins us to talk about HTML Form Validation. We’ll get back to our Cellular Automata next week. Bart has also decided that we’re going to get our feet a little bit yet by using GitHub where we’ll be getting the challenges and solutions from now on. You can see Bart’s awesome tutorial at bartbusschots.ie/…
We finally reached 500 episodes of Chit Chat Across the Pond (episode 499 will be next week) so who better to have on the show than Bart Busschots who started it all?
It was a lot of fun and I hope you enjoy this refresher episode as much as I did. Of course Bart’s fabulous written tutorial is available at bartbusschots.ie/…
I’ve been asking Bart a lot of questions in the back channel as I struggle to understand the documentation he has provided in our latest few sessions of homework assignments. He had an epiphany last week that he had never explained the documentation methods itself, which was certainly adding to my confusion.
He decided to take a step back and explain step by step using video. He created a video screencast of the entire process of creating documentation using JSDoc. Then during the audio recording you’ll hear in the podcast, he walked through it again while I asked him (lots of) questions. Hopefully it will be as eye opening to you as it was to me. He also demonstrates his favorite tools for the process.
Chit Chat Across the Pond this week is another episode of Programming By Stealth with Bart Busschots. I’m very proud of the fact that I completed my homework, writing a program from scratch that passed all of the tests written by Bart. It took me 12 hours, and nearly 4 hours of Dorothy’s time helping me do it, but I got ‘er done. In this installment, 36 of x, we learn some more HTML, specifically about all the cool things the input tag can do, like creating invisible forms which is just weird but also very cool. The challenge this week is a flip on last week. This week Bart has written the next bit of code for us and we have to create the tests. It’s as challenging as all the rest but it’s just as fun. And of course you can find Bart’s fabulous tutorial show notes at bartbusschots.ie/…
In this installment, Bart walks us through a little bit of how he wrote his Test Driven Development with QUnit for the Bartificer Link Toolkit. Bart even explains how it helped him find a couple of pretty major bugs in his own code, proving how important this is. Then we’ll move on to formatted sub-sets of text like numbers, email addresses and so on.
12 years ago, on May 13th, 2005, I decided to start the NosillaCast. Somewhere along the lines I met the wonderful Bart Busschots and he started to be a regular on the show, in a segment we affectionately called Chit Chat Across the Pond. Bart and I talked about photography and security and Macs and just about everything geeky that interested us.
Eventually we started doing Chit Chat Across the Pond together every other week and on the opposite weeks I’d have other tech guests on the show. Bart started his own shows, Let’s Talk Apple and Let’s Talk Photography.
In April of 2013, Bart decided to start a sub-series of Chit Chat Across the Pond called Taming the Terminal. This was the beginning of what we like to call our “propeller beanie” shows, where we get real geeky and learn how to conquer some of the harder tech topics.