Older blog entries for superuser (starting at number 49)

Devember 2016 – Day 7

Busy night, I had to help on call people in the middle of my coding, so
it delayed things. Still, I put in my hour. Later than I wanted, but
here it is. Started adding Router stuff. Learning about React in the
process. Yay!

Day 7 is here on GitHub.

Syndicated 2016-12-08 05:51:27 from JasonLotito

Devember 2016 – Day 6

So, adding in react after the fact was a pain. But it’s mostly working.
I still need to fix actually clicking on the links, but the basics of
React is up and running. Still a lot more work to be done, but still
making progress.

Syndicated 2016-12-07 05:08:35 from JasonLotito

Devember 2016 – Day 5

Another day has gone by.  Another video.  And more code. I learned that the recordings are difficult or impossible to see on screens smaller than an ultrawide, so this means they are mostly useless.  I need to come up with a solution to that if I mean to keep streaming.

From my commit:

So, didn't really think about it before, but decided to add
configuration injection into our commands.  This seems to have worked
out well and I'm happy with the results.  The command defines the
configuration and where it expects it, and the application provides the
external configuration in the appropriate location and it automatically
gets injected.

We also now can display route details.  This still needs more work, but
we are doing well and progressing.

Syndicated 2016-12-06 04:52:29 from JasonLotito

Devember 2016 – Day 4

Day four is done. Got the UI up today, though it’s very basic.  Decided that the API builder should, obviously, not worry about HTML output.  It should be focused on outputting results as if it’s an API, not acting as a template.  That being said, nothing prevents that from happening.  HTTP is, effectively, and API.  But the focus is on data in a format like JSON.

I streamed it once again so you can follow along with the thought process.

I think tomorrow I’ll continue with the UI, building out a system that allows you to compose commands together.

Syndicated 2016-12-05 01:03:42 from JasonLotito

Devember 2016 – Day 3

Day three is done. Not much done today.  Cleanup and work on the output functionality.  I streamed it once again so you can follow along with the thought process.

Added a TODO.md file, which I think is handy in terms of keeping track of my thoughts, on what has been done, and what needs to be done.  I think tomorrow I’m going to work a bit on a UI that is built using this system.  Still not sure of a name.  Still, three days down.  Let’s keep it going.

Syndicated 2016-12-03 22:53:56 from JasonLotito

Devember 2016 – Day 2

Day two is complete. Continued work on the stuff I was doing yesterday.  Streamed it live to no one. That’s fine.  Overall, I’m happy with the progress I’ve made tonight.  Handled outputs, both from defining the API along with the context of the request.

I think tomorrow I might want to tackle parallel commands.  So, if I wanted to fetch multiple pieces of data at once, I could do that.  Maybe I can do something more real tomorrow, such as have something that requests someones Twitter and GitHub feed at the same time.  I could do that.

Syndicated 2016-12-03 04:10:05 from JasonLotito

Devember 2016 – Day 1

Day one is complete. I’m working on something completely different, but it’s started.

I want to build a system where APIs can be built using Node.js in a way that allows you to piece together different methods.  I realize there are systems out there like this, but I couldn’t find anything that meets my goals.  Besides, I wanted to build it.  Today was a longer day.  More than an hour, mostly because I didn’t want to leave it in a half state.  I can continue tomorrow where I left off with a working system and clear next steps.

I live streamed the entire session using Twitch.  There was one point where I was dealing with an error that I could not figure out.  Here is the moment I discover the very simple error. At some level, it’s fairly embarrassing to have that live on video.  But things like that do happen.

Most of this is being designed as I go along.  I’m not so concerned about performance at the moment.  Mostly it’s about getting it working.

Syndicated 2016-12-02 04:29:51 from JasonLotito

Devember 2016

I, Jason Lotito, will participate to the next Devember. My Devember will be programming a game. I promise I will program for my Devember for at least an hour, every day of the next December. I will also write a daily public devlog and will make the produced code publicly available on the internet. No matter what, I will keep my promise.

My goal is simple.  I’m mostly following along with Handmade Hero and I’d like to continue on through the month.  I might do other things, and I’ll update that as I go along.  The goal is to get back in the habit of coding nightly and learn new things as I do it.

Syndicated 2016-11-29 02:19:34 from JasonLotito

Scripts in Confluence are an anti-pattern

Scripts in Confluence are an anti-pattern.

If you are going to take the time to document something out, then make an effort to take the time to script it out.  Even better, add it to something like Jenkins or Rundeck.  Maybe automate it.

This is true even if you have a list of steps in your documentation.  Run step 1, then step 2, then check for this, and if it’s true, do step 3, otherwise continue to step 4.  You are literally writing the program in English.

Scripts in Confluence are an anti-pattern. It’s not documented, it’s lazy.

Syndicated 2016-11-10 14:34:00 from JasonLotito

40 older entries...

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!