From ef62be357d9d9934652148072e906e53420e171a Mon Sep 17 00:00:00 2001 From: Stephen Enders Date: Sun, 17 Feb 2019 22:33:20 -0500 Subject: Updated intro and closing, and homepage --- www/blog/2019-02-17/index.html | 10 +++++++++- www/index.html | 23 ++++++++++++++++++----- 2 files changed, 27 insertions(+), 6 deletions(-) (limited to 'www') diff --git a/www/blog/2019-02-17/index.html b/www/blog/2019-02-17/index.html index 48f5f4c..5c4b040 100644 --- a/www/blog/2019-02-17/index.html +++ b/www/blog/2019-02-17/index.html @@ -42,6 +42,11 @@ would monitor for reminder notifications I would send via a CLI. It queue them up based on some time set to send the notification. I ended up writing both the CLI and the daemon in this past week, both in C.

+

The Beginning

+

+ This project started with an outline (as a README) which I think was the reason this ended up as an actually successful project. + I had been thinking about this for a long time, and had begun using a calendar to keep track of long term reminders/dates etc. First, I outlined the architecture "how would I actually do want to send myself remidners". Since half my day is spent infront of a computer, with a terminal open or at least two keystrokes away, a CLI would do the trick. Then how do I actually send myself notifications... writing them down. So I can use the CLI to write to a file and have a daemon pick up the changes and notify me once it hits the desired time posted. +

The CLI

The CLI remindme took in messages and appened them to a file. This file would be monitored by the daemon later on. Each reminder @@ -140,9 +145,12 @@

Overall, this was an extremely fun first week of engineering. I look forward to what I am able to do syncing and sending notifications on android.

+

+ For the zero people reading, grab a beer and outline your project. Full through. Think about the how, then write it down. Don't worry about getting in the weeds of how to write a manfile, thats what is fun about programming. I thought I botched my debian/sid environment uninstalling and reinstalling a notification daemon. Infact I think its caused me to take a stance on the whole systemd thing. Either way, start a private repo (they're free now) write a README and a LICENSE file and iterate on the README until you realize "oh shit this is something I can do". Then do it. This project still needs some work, but for an MVP, its actually done. And now I can dive in the deep end of trying to actually make it easy to setup on a fresh PC. Or dive into modern android development and server syncing... +

diff --git a/www/index.html b/www/index.html index 1471b9a..5f4f663 100644 --- a/www/index.html +++ b/www/index.html @@ -23,11 +23,24 @@

Recent Post - 2019-02-17

Venturing back into C

-

After working in C++ for home projects that never go anywhere I - decided to get back to basics and write a utility that I have been - needing in plain ol' C.

-

reminder.d is - a cli and daemon (so far) that manage reminders throughout your day.

+

For the past two weeks or so I have been diving back into C + programming. I've found it to be a very fun and refreshing experience + coming off of a slog of Java 11 updates at work. I've found comfort + in its simplicity and frustrations in my "I can do this without an + IDE" mindset.

+

I started C programming in College during a 8 AM course of which all I + can remember is that it was at 8 AM. I loved programming in C, dealing + with memory, pointers, no strings, structs, no strings, linking, no + strings. It was a really interesting difference from the web and Java + programming I had done previously. Obviously the lack of the + "string" type made things interesting and initially a challenge + for me back then. In my most recent endevour I found char * to be perfectly suitable for every case I came + across. It was usually a separate library that was failing me, not a + fixed char array. This was mostly due to the types of programs I was + writting in college were text adventures where all of what I did was + using strings. And my lack of understanding of what was actually + happening in C was really what was causing all the issues.

-- cgit v1.2.3-54-g00ecf