You are here:

I love reading, I love books, and my friends say I have an overactive imagination. So it may not be terribly surprising that back in my teens one of my dreams was to one day become an author. A world famous author of course. Writing good old fashioned books. Which would be published with my name on them and which people would line up in book stores to buy. New books with that new book smell. I'd sign them and impress the ladies with my wit and prose.

Having trouble writing? It may be just that you are having trouble doing
two things at the same time:

decide what the prose should say (substance)

write the prose (form)

They are intimately interconnected. If you don't REALLY know what you
want to say, you are going to have a hell of a time saying it. And then
instead of actually writing sentences, you play with grammer and use
alot of syntatic sugar until your sentence seems to have filled a
respectable space (form over substance) and you can move on to the next
one.

A while back I decided it would be a good idea to combine a loose collection of related Git repositories into one big Git repository.

The rational for this was that I noticed that often the same logical change had to be broken up into multiple commits across these previously separate repositories in a way that made it difficult to track which changes were part of the same change. In other words it artificially fragmented the commits and made revisions harder to track.

Here's a super easy way to invalidate the disk cache, which is useful
for testing IO performance in the real world, where you can't rely on
all of your reads being served up from a super-fast RAM cache rather
than a vastly slower physical disk drive.

In a nutshell, Rules is a visual programming tool. Instead of writing
code as a block of text, you configure the desired behavior via a GUI
that guides you through the setup of "rule sets" which are basically
stored procedures that define conditionals and actions to execute, and
triggering those rulesets from various canned events.

Rules sets can can call each other immediately (watch out for infinite
loops), schedule each other (or themselves) to be called later, etc.

Not too long ago, a friend told me he was quiting his day job to try going out on his own as a freelance consultant/contractor and asked for some friendly advice regarding wages and billing practices.

I may not have been the ideal person to ask, as I had never worked in the exact market my friend was going into. On the other hand, in my twenties, a few years back I did work as a computer security consultant.