Lifestream

One diagram. One purpose. Or you already lost the argument.

The syndication microservice is working! Now to write up a blog post explaining it all.

It has taken longer than I first thought. But I can see the end in sight for the re-architecturing phase in my #indieweb redesign. I landed on a microservices approach and so far it feels much nicer to work with and maintain. Just the syndication service to go!

A complex user flow can be a good indicator of messy business process being palmed off to the user as their issue. Similarly if it is overly simplistic there is a good chance you are missing something in your research.

Wondering if I could work out a method for a complexity rating at each stage over a given process. It would be a way to ensure at no point during a service things get to complex for a user and they abandon it. Or it could be used as an analysis tool to identify problems

the blog has been quiet for a while but work is continuing when I can during lockdown. I have been refactoring and tidying up my indieweb server. I have also been experimenting with Netlify functions, which are not fun to use at all. Lots learned, but not a lot to show right now

Just implemented @Netlify Large Media. It was super simple to setup. one Minor niggle, it did not play well with Node 12, downgrading to 10.13 solved the issue.

Starting to feel like I am only a few weeks away from getting my port from Jekyll to Eleventy done. I definitely think I need to write up a blog post. Lots of learning to document

808DotPop on hard repeat.