note

· · to read

I’m participating in the Ultimate Blog Challenge for personal and professional reasons. The personal reasons are partly documented here, and I’ll document my professional reasons on this site.

Content creation is hard work, and I need to get back into the swing of it. I have several lengthy tutorials sitting in my drafts, and I need to finish them, and I think the only real way to get back into the swing of content creation is to practice. So I’ve decided to take up this blogging challenge so that I can do that, as well as find new content to read and absorb. There are a lot of things floating around my brain regarding business, the tech landscape, and the web development landscape specifically, and I’d like to start getting those things out of my brain and onto my website where I can flesh them out better. My plan is to not turn over all my thoughts to social media platforms and instead document them on my own site, linking to them in larger posts where appropriate, and of course changing them when appropriate. Plus this will be a really great way to share what I learn by sharing my notes on the books I’m reading, (there are several professional development as well as technical books on my anticipated reading list for 2019), as well as the articles written by others, especially experts in particular fields like accessibility. I’m looking forward to this, and I think it will be a lot of fun. If you want to sign up, I believe there’s still time left to join. No pressure or anything, but it’s a great way to start owning your own content if you haven’t started doing that already.

Until next time.

note

· · to read

I spent some time today putting a system in place to track the unbillable time I spend on contributions to free software, and when I say contribution I’m being pretty liberal about what counts as contribution: Advocacy, not just code, for example. I believe in the mission of free software, but the fact is free software isn’t without cost, and sometimes that cost can get pretty high. I’m also working out how to document my contributions in my portfolio, including the free accessibility advocacy that I do. This is going to take a little more work and some more research, but I feel it needs to be done. I need to be able to keep track of this stuff so I can limit it when necessary. Right now I’m thinking of setting the limit at ten percent of free time outside of shabbat and festivals, because those are times when no work of any kind is done, as a general rule. I’m not going to get into the exceptions around festivals because it’s a lengthy topic, but to say no work of any kind can be done on festivals would be technically inaccurate. I think ten percent is a reasonable amount of time. It’s not a ton, but it places an upper limit on the time I have available to do this kind of work. I will also document the time spent, although I haven’t decided whether I will publish a weekly or monthly or yearly report. This is going to be an interesting project.

read

· · to read
Tech Ethics New Year’s Resolution: Don’t Build Software You Will Regret by Jennifer Riggins
we should be working not just to pay the bills, but to make sure we don’t create software that we will one day regret.

In the web accessibility space, we talk a lot about how everyone has a role to play when it comes to accessibility. We’ve been talking about this for a very long time, and I’m glad to see the idea that when it comes to cross-disciplinary things like ethics, it’s not just one person’s responsibility. Accessibility, at its core, is an ethics issue, and I think that, just as accessibility as a part needs a good business case to support it, tech ethics as a whole will need that too. Right now we’re still in the beginning stages of considering tech ethics as a whole, so we’re not to the part yet where the business case for it, or even the general idea of a business case, is being considered. But I suspect we’ll get there soon enough.

read

· · to read
GitHub Free users now get unlimited private repositories
If you’re a GitHub user, but you don’t pay, this is a good week. Historically, GitHub always offered free accounts but the caveat was that your code had to be public. To get private repositories, you had to pay. Starting tomorrow, that limitation is gone. Free GitHub users now get unlimited private repositories.

I think this is over all a good thing, although I’m hesitant to take this as some sort of goodwill sign from Microsoft. I find that it’s easier to deal with the disappointment that inevitably arises when platforms remove or limit features if one keeps in mind that these are business decisions and nothing more. Plus, honestly, I still don’t trust Microsoft when it comes to free/open source software. Their newfound love for open source hasn’t been around long enough to erase their very long history of having an anti-open-source stance. This article opines that most developers have come to terms with Microsoft’s Github acquisition. Well of course we have. Most of us use Github either for our own projects or for projects we contribute to, and it’s easier to just come to terms than it is to spin up decentralized operations and move everything over to those. Decentralized is the better approach, although I think managing the social aspects of software contribution is still a hurtle. I need to look into this more.