devmorgan.com

I can’t quite come up with a good name. Dave’s Cheesy Garlic Bread is a little too generic, and Devmorgan’s Cheesy Garlic Bread is a little weird sounding.. so, I’ll go with My Cheesy Garlic Bread (by Dave Morgan).

No, this isn’t particularly geeky, and has nothing to do with technology or computers - but it’s my favorite thing to cook for people if I want to pretend to look like I can cook.

Start to Finish: About 45-50 mins

So, first things first.. Ingredients (makes about 8 pieces)

• 1 loaf of pane Italian bread
• 1.5 sticks of butter (or 2 if you want even LESS healthy. or 1 if you want more healthy)*
• Grated mozzarella cheese (I usually get away with the 16oz bag - can grate yourself though)
• 2 tablespoons of minced garlic (do it yourself, or buy the little glass jar at the store)

* = I make no claim that this is healthy no matter how much butter you do or don’t use.

Now, for the directions. Some variances can apply, I will note them. Also, some steps can be done concurrently, I bet you’re smart enough to figure out you can melt butter and slice bread at the same time ;).

1. Pre-heat your oven to 375 degrees.
2. Slice your bread
   

   Slice about 8 slices out (1-1.5 inches thick).

3. Melt Your butter. I tend to melt half a stick first, put a tablespoon of garlic in, then melt the rest, and put the other tablespoon in. I used to do this in the microwave - now I actually do it in a sauce pan. I think the butter seems to get more of the garlic’s flavor this way. I could be wrong. Results may vary.
   

   Mix this all together until it melts completely and let it simmer a min or two.

4. Place your sliced bread on a cookie sheet (I wrap it with tin-foil to save on clean-up later).
   

   Better to have them closer rather than farther apart, but not touching.

5. Now, use a spoon to scoop out the garlic from the pan and evenly distribute it onto the bread slices (I sometimes make one half of the tray more garlic heavy if some people don’t like garlic as much).  Scoop all the loose garlic out first.
   

   Don't worry - we use the butter soon enough. Just garlic for now though.

6. Now pour the butter onto the bread. Pour slowly and let it soak into the bread. Use all the butter. It’s okay if some runs off the bread.
   

   Yes. This is artery clogging goodness.

   

   The bread should be saturated with the butter.

7. Place the bread in the over for about 15 mins (this will start to make it a little more like toast).
8. Pull the bread out and now place your cheese on the bread… liberally. Mound the cheese on each slice of bread. No, more than that. Even more.. Little more.. Alright, thats good.
   

   The more cheese the more delicious.

   

   I tend to pour it over, and a lot gets lost to the tray. Thats ok. Just make sure the bread has lots of cheese on it.

9. Bake for another 15-20 mins. Pull the bread out when the cheese starts to brown on the edges and a little on the top.
   

   This is how it should look, more or less. It's what delicious looks like.

I tend to serve this with spaghetti or sometimes steak. It’s not healthy, but it is DELICIOUS. Plus, it’s ok if you make too much - it tastes pretty delicious out of the fridge the next day.

dave food

So, this past week has been one of painting - not so much of coding like usual…

Lots of painting.

I would like to thank Jess’ parents for coming up and helping us by painting our family room, office, and nursery. Having the help made getting so much work done possible.

This post however, is less about that particular bit of painting, but more about the amazing work that my sister Michelle was able to do when she came up this weekend. Now, my sister is artistic - but I never imagined how nicely our Dr. Seuss nursery would turn out.

First things first, we had to start with a blank canvas.

Now, this beautiful blue base was painted by Jess’ parents, and it came out great… but it doesn’t look much like a Dr. Seuss themed room, does it?

Read more…

dave house, life, technology

So, I’ve been gone for a little longer than I would like to admit. What it really comes down to is being busy. Of course. I have a real excuse though! I’m going to be getting married. I’m going to be a dad. I just bought a house. I just started a new job. Things are moving fast and I haven’t had time to write.

Now, I have more pictures - but they are on my camera, and well, I haven’t had any time since we closed to really do anything except work at U of R, travel, and work on the house. So, I can only share the ones that are on my phone.

I have gone from programmer to “house guy” lately, so I promise to update when I get some time. Maybe I’ll post details of some of my projects here.. hmm..

dave house, life

Time Warner Cable announced the other day that they are going to be placing low usage based caps on usage in select markets, one of which being Rochester, NY.

Hey, the twitterverse is already pissed. I’m pissed. But lets think about this for a moment.

Media-on-demand providers should be pissed. Their service requires that end users have expendable bandwidth. High Definition movies are over several gigs a piece.

Families and Roommates should be pissed. Every computer you have on the net will be consuming that bandwidth. I live with 2 friends, and yes we’re techies, but we each have a computer. We have an xbox media center (for watching movies and such), a wii (which we utilize the internet for games such as mario kart), and we all have iPod touches that we use day to day for various reasons. All of these go through our pipe. Just imagine if we played online games! My World of Warcraft addiction would start to cost me more than the monthly fee.

People with a home office should be pissed. It’s highly doubtful you have a business line into your home, especially if you do less than 50% of your work at home, so you will be affected. Sure, it depends on what you do in your office… but if you use services like Skype (for conference calls), or are involved transfering documents, all that data is counted as well.

Friends that come over with their laptops should be pissed. What happens when Steve your buddy from freshman year comes by to say hi and you have to tell him “Sorry dude, I can’t let you connect to my wifi… I’m at my limit.”  or “sure, can you give me a buck or two to cover for your bandwidth?” Even worse, what happens when someone leeches your wifi?

Well, lets address some of the issues…

In Rochester, there is no real competition to Time Warner for broadband service. Frontier doesn’t have the infrastructure, and other services are just reselling Time Warner infrastructure.

Of course, ’shit ain’t free’, I agree, and I totally understand. However, a strange thing happens when companies become the only really shop in town… they charge more then they need to. Numbers that I have read vary, from 3 cents to 5 cents, but that is the approximate cost for Time Warner to have a gigabyte of data pass over their network. The means, at the high end of those numbers, it costs Time Warner two dollars for 40GB of data. Then, they are going to charge me a dollar for every gigabyte I go over? Does that seem fair to you? Ok Ok… Support costs? Fine. You know what though? The average person who will constantly go over, doesn’t use support… unless Time Warner screws up their network.

Should someone that barely uses the internet have to pay the same as me? No. I agree again. You know what? Offer people the choice. Usage based consumption, or all inclusive. Usage based should be cheaper, and it should be FAIR. You wanna set up low limits? Fine. But charge reasonable overages. Still worried about the “all inclusive” plan being abused by people who transfer truely massive amounts of data? Fine. Limit them. Write it in their contracts that consistantly going over 1TB of data transfer will cause their service to be discontinued - but let it be a truely masive amount, and only if it’s really a problem should it be addressed.  There are better ways.

Really, the crux of the matter is this… You may not use all that bandwidth yet. You may even think one dollar of overages aren’t that bad. What needs to be realized though, is that our world is becoming a truely connected world. Data transfer is what is making much of this possible. Limiting access to this data will stifle our economy more, and will cause a decline in the utilization of the internet for all of its purposes… and believe it or not, thats a BAD thing.

Just remember, even reading this brings you a little bit closer to your cap. Don’t worry though, to be considerate I decided not to include any images that might needless cost you more.

dave rambling, technology

I wasn’t able to get this post up yesterday, but I wanted to make sure I got it up today. Sorry for the interruption of the DyDL stuff. It’ll come out more soon.

This year we had another successful April Fools. Zack and I were able to pull off 2 fairly successful pranks. The two pranks this year were new course offering and course cancellation posters and implementation of upside-down-ternet.

So, lets start off with the simple one, the posters:

Each one of the posters by themselves were mildly amusing, but when taken together, it provided for some hilarity. One thing that was requested last year was a list of all of the name tags we made, so this year I am providing a list of all the posters and where they were located (to the best of my reccolection).

Course Offerings:

Introduction to Hygiene (Men’s Bathroom Door)
(4002-039-01)
Course Description:
Learn about hygiene and why it affects you as a professional. Course is restricted to Computer Science majors until 4/13.

Advanced Googling (Posting Board)
(4002-501-04)
Course Description:
Students in this course will familiarize themselves with the advanced search functionality of google. Prerequisites: Introduction to Googling (4002-005) and Introduction to the Internet (4002-006)

Introduction to DOS gaming (Posting Board)
(4080-001-01)
Course Description:
An introduction to developing games for the new DOS platform. Topics include Virtual Memory management and writing BASIC

Introduction to the Internet (Posting Board)
(4002-006-01)
Course Description:
This course will discuss usage of applications such as Web Browsers and Chat Clients, and topics such as pr0n, games, and LOLcats.

Inventing Incomprehensible Jargon (Posting Board)
(4002-009-01)
Course Description:
BC IDK, WTF. People L2Talk. LOL Internets.

Gold Farming (Gaming Lab Door)
(4080-003-10)
Course Description:
Develop an understanding of the economics behind gold farming, as well as nurture skills in gold farming. Students must be taking less than 12 credit hours to take this course.

Introduction to ASCII porn (Posting Board)
(4002-002-69)
Course Description:
Topics include subjective determination of ASCII characters to their genitalia similarity, arranging multiple characters for genitalia, and using characters to describe sexual events.

Daemon Summoning (Airgapped Security Lab Door)
(4002-009-01)
Course Description:
Call on the powers of Rut and Baash to control first your machines, and then the world!  A working knowledge of Linux and lesser daemons like the Oracle is helpful but not a prerequisite.

CAT5 Basket Weaving (Posting Board outside of Networking’s Main office)
(4002-007-01)
Course Description:
This trade skill course will train students in the fine art of basket weaving using only CAT5 cables.

Fundamentals of Notepad (Posting Board in Lobby area)
(4002-004-01)
Course Description:
Topics include: Creating a new file, Opening an existing file, Saving a file you just opened, Saving a file you just opened as another file, and Printing.

Advanced Topics in Notepad (Posting Board in Lobby area)
(4002-200-01)
Course Description:
Topics include: Copying text, Pasting text, Cutting text, Printing to a non-default printer, Word-wrap, Changing font, and using the Find command.

Designing VCR Programming Controls (Posting Board)
(4002-008-01)
Course Description:
Make VCRs not suck. Because you’re tired of your parents calling for help.

Course Cancellations:

Advanced Molecular Computing and Informatics (Medium Database Lab Door)
(4002-023-01)
Professor Thireos has been talking to someone for the past hour, and we don’t think he’ll make it to class on time.

Advanced Programming for New Media Kids (Media Lab near Bridge Door)
(4002-018-01)
Not enough interest.

“Alternative Medicines” to help Coding. (Lecture Room Door South Hallway)
(4002-021-01)
Professor Sonstein’s class will not be held until more snacks are available.

Cooking in a Digital Age (Lecture Room Door South Hallway)
(4002-017-01)
Professor Perry’s class has been canceled because there is not enough interest. Most students only eat fast food, pizza, and drink jolt or mountain dew anyway.

Being Big and Tough (Media Lab near Bridge Door)
(4002-016-01)
Professor Bogaard’s class has been canceled because his minivan broke down and he fainted and broke his chin.

Somber Programming (IMM Lab Door)
(4002-053-01)
Professor Jacobs is still sad he didn’t have a name tag last year, so in that memory, class will be postponed until tomorrow.

Flash Physics at the University Level (New Media Lab Door)
(4002-057-01)
Professor Kurtz was busy determining the rate at which a falling body falls. He should be out of the cast next Monday.

How to attract the opposite sex for INFOTECH (Lecture Room East Hallway)
(4002-100-10)
Has been canceled because no professors with course knowledge are available.

Fighting Shortness (IMM Lab Door)
(4002-023-01)
Professor Lawley and Oyzon’s team taught class will not be held today. Class will recommence  when platform shoes become fashionable again.

Using Documentation for Programming (Big Database Lab Door)
(4002-067-01)
Professor Kang is out sick today. Apparently his friend, the javadoc, had the flu.

Drinking for Programmers (Medium Database Lab Door)
(4002-050-01)
Professors Whittington and Zilora have already decided that it’s 5 o’clock somewhere.

The second prank was much more involved. We implemeneted Upside-Down-Ternet in all three of the database labs. This prank took us late in to the night to try to figure out how to do it. We used a combination of ARP poisoning and DNS spoofing to make it happen.

We ran into a few problems - that really show us how caring of pranksters we are. We had to modify the scripts we were using to allow for the students to continue to connect to class resources without disruption. It took us a while, and we had a few bugs, but we pulled it off.

We had it running on and off for most of the day. During peak hours, having everyone redirected through our server bogged down the internet - so we had to turn it off, but we were able to turn it back on later. Towards the end of the day, Zack turned it into a Burleson-Net (a famous Oracle blogger) to make some of the database classes laugh.

Overall, a great day. I was able to see many student laughing, and many professors laughing as well.

dave life

So, before I sit back and talk about all of the actual methods on the MagicDB object, we need to talk about a problem that is specific to PHP and the mysqli extension.

Now, the basic idea I had was to build something that could generate prepared statements dynamically. This will (if done correctly) help protect against SQL injection, and ideally help speed up a few frequently run queries (as long as the SQL structure is always consistent). We need to select mysqli because it has the mysqli_stmt::prepare ( string $query ) function.

Ok, so, now we come to the binding parts of the process… and here is where it gets sticky. We are presented with these two methods:

mysqli_stmt::bind_param ( string $types , mixed &$var1 [, mixed &$... ] )
mysqli_stmt::bind_result ( mixed &$var1 [, mixed &$... ] )

This presents us with a problem. Notice how both methods (which are required for prepared statements) allow for multiple parameters. This is handy — wait.. really.. it’s never handy. I really don’t know why they designed it this way. In fact.. Damn those PHP people. OK.. so maybe I do know why,  but it gets in to reference/value discussion.. so.. lets move on and just figure out a way to fix it.

In an ideal world, for being dynamic, the functions should be designed something more like this:

mysqli_stmt::bind_param ( string $types ,  array &$params )
mysqli_stmt::bind_result (  array &$results )

Instantly this becomes a lot better. Since the parameters/results are stored as an array, they can be dynamically generated and of any length.  To address this concern, we need to tackle both functions a little bit differently. First off, the bind_param function:

I wrote a simple private function that is included in MagicDB that will accept a mysqli_stmt object, and a list of parameters. From it, the function will call the bind_param method with the proper values and return the statement object.

Now, lets discuss the major concern with this code. The data types of the parameter array that is passed in are used for truth. So, as a developer you need to be careful. This will not cause any security risks, but it may reject your parameter if the wrong data type is used. This is a known concern, but one that I am not worried about since I know to pass an int when I need an int. The beauty of this code is in the last couple lines. I use the php variable-variable-name functionality to generate a dynamic variable reference. I call each variable $bind#, and then assign the parameter to it. I then can use the & symbol to add the variable by reference to the array. Using  the PHP function call_user_func_array, we can get around the multiple parameter problem by simple passing an object reference, a method name, and an array of parameters.

Now for the binding of the result. This code isn’t stored in a function, although it could be. It’s stored in my “get” method on the MagicDB object. Some variables are out of scope, but here is the snip.

So here, without getting into too much detail about how the get() function works, we want to return an object of the type that $object is.  The object should have all the values populated with the results of the database. We bind the variables in the same manner that we bound the parameters in the previous function.  Where it gets fancy is in the use of reflection. We get the type of the object, and pass it into what is called a ReflectionClass.

This will generate a generic class of the type we specify. We must then instantiate the object by calling newInstanceArgs() method. This allows us to pass an array with the parameters for the constructor. This is why the constructor is required in all of the data objects. We do this for each iteration of the fetch, and return the array of objects.

Sexy eh?

Next up we talk about the API and how the MagicDB functions actually work.

dave coding, data, technology

MagicDB is the codename for the Dynamic Data Layer that I built to help me with my much larger project, my fabled “Capstone” for my Masters of Science Degree. First a couple technical details:

• MagicDB currently runs on PHP 5.x.
• MagicDB currently only interfaces with MySQL.
• MagicDB is built using an Object-Oriented paradigm.
• MagicDB uses PHP’s mysqli engine.

Understanding the technical bits will explain why some decisions have to be made. PHP is used pragmatically for myself, since that is the language I used to build my capstone with. It’s free. That helps. MySQL is also free, and one of the most common companions with PHP. The mysqli engine is used primarily because it provides the support for prepared statements. Using a prepared statement allows us to curb SQL injection attacks, which addresses one of our main concerns with security.

MagicDB has only a couple rules that need to be followed.

1. Data Objects (PHP) must follow specific naming requirements.
2. Data Objects (PHP) and Data Tables (MySQL) must follow specific structural requirements.

Naming Requirements are actually pretty simple. All data objects used with MagicDB need to follow the pattern [Prefix]TableName. The prefix can be whatever the developer wants. For my capstone project (codename: TWiG), I used the prefix “TWiGdb_”. This means for a table in my database named “Entry”, I have a corresponding data object with the class name of TWiGdb_Entry.

Structural Requirements are a little more in-depth. Originally, the structures were required to be identical. This meant that for every column in the database, the data object should have a column for that as well. I improved upon this by adding a column to every database table (but not the data object) called “exist”. This column is a flag to show if the row was removed from the database, it has a default value of true. This allows us to “remove” data, without deleting it (although functionality is built to actually DELETE data), in case we require that data later.

Another structural requirement is that the first column in the data object MUST be the primary key for the table. In the table, the first column must be the primary key as well. This allows us to issue UPDATE commands easily. A constructor with all the attributes as parameters is also required. Order of the parameters and attributes must also match across the board.

The final requirement is that each attribute of the data object MUST be using the same exact name as the corresponding column in the table.

For example the table User would be described like this:

The corresponding data object would look like this:
Once we can build the structure of the database, and the corresponding data objects, we can begin to discuss how the DyDL works. MagicDB itself really has a simple interface to use.

In the next few posts we’ll discuss each of these methods, and talk about some of the private methods that power the implementation.

dave coding, data, technology

So, I figure it’s about time I actually talk a little bit about code. I know many of my readers aren’t programmers, so my apologies. For my capstone work I have been playing around a lot with data, and I want to share my experiences.

So, first things first. Lets talk about Dynamic Database Layers. We want to build a database layer that is as dynamic as possible and flexible, but provides understandable structure and expected results. We want something that is secure, but also usable. So lets break it down:

What are the goals?

1. Ease of use.
2. Low learning curve.
3. Clear and understandable “rules”
4. Secure
5. Solves routine problems naturally.
6. Allows non-routine problems to be solved easily.

Ease of use. The first and foremost goal we have for our DyDL is that its easily usable. Ideally, it should make accessing the data simple and trivial. If you need to write lines upon lines of code just to invoke simple calls, developers won’t use it. Make easy things easy. If a developer needs to do something more complicated, try to make it easy - but they’ll be willing to do more work to accomplish it.

Low learning curve. One of the most difficult tasks as a programmer is to adapt to new technology. Understanding the lingo, the structure, and the benefits is required to be efficient. Don’t make it difficult to use. Use common paradigms to make entry into use easy. This leads us into the next requirement..

Clear and understandable “rules”. Make how the software layer works straight forward and simple. Don’t build an application that has situations where if you want to do one thing, you have to do it differently than another thing. Make it clear to the developer what each function is actually doing. If all data objects require certain structure, make it clear. Giving meaningful messages and documentation for the layer.

Secure. This is straight forward. Make your best attempt to make the code secure. If you can prevent SQL injections, do so. Build as much structure to the framework such that you can limit the ways to exploit it. Don’t trust unknown data.

Solves routine problems naturally. Make simple stuff simple. If you need to do a simple access of data based on a few parameters, make it so that is one simple call. Try to abstract your calls so the developer doesn’t need to know the SQL that is being run underneath. Allow simple complexity by allowing the developer to do so, but don’t require them to.

Allows non-routine problems to be solved easily. Always allow the developer to decide if their way is better. Provide a simple interface such that a developer can still use your engine to do things that you haven’t accounted for. If you can, try to make it easier. If you can’t, don’t stand in their way.

For a portion of my capstone, I have implemented what I believe is an excellent start of a DyDL, codenamed MagicDB.  I will be writing about this project more in the coming weeks, and will be showing bits of code, and explaining decisions made. Hope I don’t bore anyone.

dave coding, data, technology

I have heard this word a lot lately. It partially explains why my writing has been more sporatic lately. So, for that, my apologies.

So. A few big things have happened in my life, some of which geekier than others. First things first: I’m engaged! This is very exciting, and well, pretty much awesome. For the record, I didn’t do anything too fancy, but I did do the one knee thing.

Now on to the geeky things! I have been working on a research project for about a year now, involving Data Mining and Data Warehousing. Dr. Jai Kang, his son, and I have written a paper based on the research, and it was accepted to a conference! In Italy! So, come May, I will be heading out to Milan to present the paper with Dr. Kang. Very exciting time indeed. I will likely make a copy of the paper available here after it is presented.

I am also working on my capstone. I am staying pretty quiet about it online right now, but I can tell you it will be really cool. It will involve a visualization, and will be available as a web application, and of course, I will allow access it from here.

I also have had several interviews, hopefully I’ll be getting a nice development job in the coming months.

I guess the long and the short of it is, I will be posting more soon I hope. I just need to catch up with everything that is going on in my life. So, until then, adios.

dave life, relationships, travel

Another call from the parents, wanting to get something working correctly on their computer.

You’d think we’d be past this… but we aren’t. That’s the problem with technology today. We are SO close to having things “just work”. In fact, I’ll admit, Apple is closer. The problem is, we aren’t there yet, even for the mac.

My parents are smart people. They don’t understand computers, but they are smart people. In fact, my father is one of the most intelligent people I know. He has a mechanical mind like none other. Once we start talking how to use the computer though, things get increasingly difficult. I wish I didn’t have such a short fuse, but I get frustrated easily with technical questions. Sorry guys. The problem still remains, when things get plugged in, and installed… they don’t always just work.

The reality is, will we ever get there? Sure, things are more and more user friendly, but sometimes the learning curve is just going to be difficult. Trying to explain how to get video conferencing is hard when the person who is being told is miles away and doesn’t understand why the computer needs to reboot to recognize the drivers, or where the unmute settings are.

This isn’t meant to be a rant - wait - I guess it is, but as software developers we always need to strive to make things “just work”. A lot of times, this isn’t the focus. Sometimes hardware is the limitation. Sometimes software is.  Sometimes the focus is quick development, and not quick learning curve. Sometimes we just specify a “requirement” on the system to avoid something that will cause the program to break. Although, every day we get closer!

What I worry about is that more and more, I need to explain to many of my students that things are “magic” and it just works. This is great - but it’s also scary. We need to be able to develop things that “just work”, but at the same time have a very clear and logical paradigm that is associated with them, so they can be understood. I don’t know how to solve this problem. Hell, I can barely think of examples. But, it’s been a month since I’ve written and I figured I’d say something.

Perhaps a few more days in the oven and this thought will be a little more cooked.

dave coding, technology