Weeknotes – 012
Just a week after officially declaring that I will stop posting on my dev blog and instead publish software developments posts on this journal, I am starting to see a problem with this setup. The problem mainly revolves around retrieving software development content.
I actually use my dev blog to store answers to problems I've encountered before. And every once in a while, I use it to retrieve scripts or pieces of code that I need to re-use. That's easy to do with a dedicated software development blog. It's not so easy to do with this journal. And that's because these bits and pieces of software development content, are buried inside one big Weeknotes post. And that makes it hard for me to quickly get to the information I need. It is inefficient as far as searching for information goes.
For instance, to retrieve the notes I had about the basics of using Git from a command line. I have to sift through the content of Weeknotes-011.
So now I'm trying to think of ways to get around this. After posting the Weeknotes post, I'm thinking I could move out some of the software development content into their own stand alone post. But then that means readers will receive notifications of a new post, for a post whose content they've already read before. So I don't really like that solution.
Another possible solution is instead of including software development content in a Weeknotes post, I should just publish them in their own stand alone posts. This one is the logical solution. The only reason I'm not pursuing this, is because I want to avoid publishing multiple posts during the week. I'm trying to avoid another burn out from over-posting.
Another possible solution is to copy the software development content and publish them to my old dev blog, in my spare time. Then I'll update the Weeknotes post with a link to the stand alone post. I think this one is a valid solution. It's a little embarrassing to be going back so quickly, but if that's what I have to do, then that's what I have to do.
The last solution I thought of, is to create a micro notes blog or atomic notes blog. I've been thinking about this for awhile now and have mentioned it in my previous Weeknotes post.
An idea: Instead of creating a “microblog” to house micro/short posts, or creating one as a social media replacement, how about creating one to hold micro thoughts (or atomic notes) on a specific topic? I'm thinking more of a digital garden here versus a Twitter replacement.
This new micro or atomic notes blog, would basically be a cross between a digital garden and a collection of notes from my posts on this journal. Posts from this new blog will not be published to the read.write.as feed and email subscription will not be enabled. It will basically function like a public notebook. At least, that's the idea. I'm still not sure if I'm going to go through with it.
Also, it sounds like the same thing that I did on my Are.na account — where I started moving notes and excerpts from my journal entries into specific buckets. Yeah, it is similar. Except Are.na has the same problem when it comes to searching for information I want. Having a dedicated blog containing a collection of notes, like a public notebook, sounds like what I'm looking for right now.
Another blogging related idea: Instead of creating a new blog to contain posts for a specific topic (like a dedicated dev or gaming blog), what about creating just one post that contains all posts on a specific topic? This single post would then be a living document that gets updated as new thoughts and ideas on the topic come up. It will most likely end up being huge. But it will be a one stop shop for everything on a specific topic.
By chasing audience we lose the ability to be ourselves. By writing for everyone we write for no one.
– Tom Critchlow
Link: Small b blogging
This week I ran into this quote again. This explains so much of my dilemma with blogging. Should I write for myself? Yes, yes I want to. But doing so makes my posts seem only applicable to me.
For instance, my Weeknotes post, or my discontinued journal entries. They are/were this one big post with so many different topics all mixed in together. This is/was me being myself, writing for myself. However, I can't help but wonder if I should break down that big post into smaller chunks, so that readers can get to the topics they are interested in. Now that is me trying to write for everyone.
This debate that regularly goes on in my brain, is one of the things that tires me out when it comes to blogging.
Unsubscribed from the Aeon newsletter and a couple of other ones as well, because I'm having a hard time keeping up with all my subscriptions.
If you wanted to create some live polls during say an online presentation, you can use PollEv.
Why doesn't anyone create a camera/device that can take pictures as good as the latest iPhone, but not make it a smartphone? I'm thinking more in terms of avoiding distractions with everything that a smartphone brings. I just want a camera that takes great pictures, but is only as big as say an iPhone 12 Pro.
I guess in some ways it doesn't make sense from a business standpoint. An iPhone that can only take pictures and do nothing else, would probably not sell. At least, compared to an iPhone that can do everything else in addition to taking great pictures.
And you can always turn off notifications, uninstall apps, turn on screen time and dumb down your smartphone. So, why bother right? Except doing all that requires willpower and mental stamina. So, why not just give me a great camera, that's the size of a phone, without all the distractions?
Was doing research on what the best rifle was in Fallout 4. Ran into a post showing a Damage per Second stat. This stat is not something you will find in the game. So, that led me to try and figure out what the Fire Rate stat in Fallout 4 really means.
Based on this post, Fire Rate is the number of shots a weapon can make in a 10 second window (without reloading). So, if a rifle has a Fire Rate of 5, that means that weapon can fire 5 shots in the span of 10 seconds.
Using the info above, you can figure out the damage per second stat of any weapon in the game. The formula then would be
(Fire Rate / 10) x Weapon Damage = Damage Per Second.
Re-activated my micro.blog subscription to try out a photo-blog alternative.
That was precisely the reaction that Jesus wanted. For God is like this crazy farmer, sowing the seed of his word and his love—not only on receptive soil, not only to those who will respond, but also on the path, on the rocks, and among the thorns, lavishly pouring out his love on those who are least likely to respond. God’s love is irrational, extravagant, embarrassing, unreasonable, completely over the top.
~ Daily Gospel Reflection by Bishop Barron
Just because you don't believe doesn't mean you can't be saved. God is reaching out to everyone, even to those who are currently not listening. All you need to do is give Him a chance and listen.
How does God tend to work? From the very small to the very great—and by a slow, gradual process. God tends to operate under the radar, on the edges of things, quietly, clandestinely, not drawing attention to himself.
C.S. Lewis speaks to this principle. How, he asks, did God enter history? Quietly, in a forgotten corner of the Roman Empire, sneaking behind enemy lines. How was European Christianity established? Through the handful of people that listened to St. Paul in Philippi and Athens. How did the mighty Franciscan movement come to be? One odd, mystical kid who heard a voice coming from a crucifix: “Francis, rebuild my Church, which is falling into ruin.” A handful of followers joined him in his quixotic project, then dozens, then hundreds, then thousands.
So don’t be afraid to do small things at the prompting of God! Plant the seed, make the move, take the risk—take even the smallest step, and don’t worry about who notices or how much attention you’re getting. Sow the seed and leave the rest to the mercy and providence of God.
~ Daily Gospel Reflection by Bishop Barron
Baby steps. All I need to take are baby steps. As long as I keep moving forward, I can leave the rest to God.
Content moved to... SQL Database Project Publish Dialog Box Showing Up On Virtual Desktop
Between news at work and stuff at home, last Friday ended being eventful and to an extent stressful. I'll end this post with what I wrote down on my journal that night:
I'm tired. I need a break.