This has been super fun. I have really enjoyed playing along with Kathy’s Brave, Bold Blogger Challenge. I’ve been pretty slack on it as we’ve been winding down so today, I’ll just whip out the final four installments.
- How you make a living
- Selfie, captured specifically for your post
- Childhood photo
- The first song that comes into your head and why
Here we go…
Checksums are handy. According to Wikipedia:
A checksum or hash sum is a small-size datum from a block of digital data for the purpose of detecting errors which may have been introduced during its transmission or storage.
We find ourselves using checksums to verify that the file a developer has created is the same as what has been deployed.
I just wrote the stupidest program ever. It is inefficient by design. If anyone did this thinking “hey… this is great code” they should be fired.
Anyway… generally speaking, using try/catch blocks is not a great idea. There are a myriad of reasons but it’s usually something along the lines of:
If you truly have an unexpected error it’s better to let the program crash and then fix the bug.
If you do have to use the try/catch exception handling block, you should only catch explicit exceptions. For example catch a file access exception or a database invalid primary key exception. Just catching the generic exception is poor practice.
There’s another reason to avoid try/catch though… it is a performance hog.
I’m not entirely sure what to blog about with the topic of Spice. I know that spices are valuable and useful. I know wars have been fought over them. That’s kinda silly though.
Hey… my soup tastes like garbage. Let’s go kill those guys.
That doesn’t make much sense.
I am enjoying the BBBC thing. But I feel like todays topic was designed to make me look bad. LOL!
In the search for better and better performance, there are many techniques developers can use. A technique used early on by some entry level or “still learning” developers is to build inline SQL. That looks something like this:
string name = "Mark";
string query = "SELECT * FROM users WHERE FirstName='" + name + "'";
OleDbCommand cmd = new OleDbCommand(query);
OleDbDataReader reader = cmd.ExecuteReader();
There are steps missing… this is just example code
This is something more seasoned developers learn to avoid almost immediately. There’s a variety of reasons why inline SQL is bad. The most important reason is security.
However, there’s another reason to avoid it. Performance.
Ummmm…. Today is a little like the shoes post. Hopefully the meaning of my blog name is:
I am a fan of trying to make my kids be able to change a tire before they’re allowed to drive. They may never need to do it, but if they have to, it’s an important skill.
Same with maps and GPS and navigation systems. If you find yourself in a place where the GPS signal is not available, you better be able to read a map.
That being said, I don’t even carry paper maps with me when I travel.
This is an interesting and timely topic. As I daydream and fantasize about taking longer and longer trips on the motorcycle, I start to think of the time between saddle time. The time when I am not actually riding. Sometimes in my daydreams I’m camping, other times I’m in a hotel… but not a big chain hotel; a little bed and breakfast.
Either way, when I’m watching the scene play out, I am reading a book. I might be reading around a firepit or in a chair in the room or maybe just taking a break reading under a tree.
But what is the book I’m reading?
As ToadMama rightly points out, having just one best friend is a little weird. Perhaps when I was little and didn’t know very many people I would have said “Brett is my best friend” and meant it. But now-a-days, I know so many more people. I don’t like any one of them to the exclusion of the others.
That being said, there are a few that I do consider to be “among my very best friends”.