I’ve been dedicating my spare time to three development projects lately, some of which are continuations of past work, while others are new ventures. Allow me to elaborate on them.
Firstly, there’s Tin (using the chemical symbol Sn), the software that powers this website. I’m quite pleased with Tin’s progress, as it now boasts numerous features I’ve long wanted to implement. In fact, it has made creating and posting new content significantly more effortless. I recently added pagination functionality, enabling users to navigate between pages and allowing Google to index all 3,000+ posts on the blog. Additionally, I re-enabled the search feature, which has been performing well. As I continue developing Tin, I plan to enhance the interactive front-end for post composition, streamlining the process of writing and publishing content directly on the site.
I’ve been reading many posts on Reddit about “daily scrum” meetings, and I’ve got to say, there are some really strange practices out there. I don’t understand how people are ending up with the processes they do. I wanted to write down a few basics to get them out of my head and be able to share them with others, so I’m drafting this post. This post will be about the team daily touchbase meeting format that I’ve been using for the last three years, known in for-fee framework circles as “the daily scrum” and also as “daily standup”.
People seem to talk a bunch about “big-A Agile”. I don’t know that I like labels too much. I am working more from base principles here than from a Scrum foundations textbook or the Agile Manifesto. But it does seem reasonable to review some Agile basics.
You see portfolio sites all over the web from web designers showcasing the sites that they've designed. And now and then you see web developers posting a portfolio including a few sites they've managed the HTML coding for. But you never see a portfolio of a developer showing the site architecture that they've rocked.
Here's a weird paradox: I want to showcase the work I've done for clients. The work I do is primarily writing site-specific code to enable a certain unique feature on a site, or assembling the parts to produce that feature. But often I can't realistically use a screenshot of the site to characterize that work, since the screenshot is of the graphic design, which is something I had nothing to do with.
