Links & Learnings: Week #4

January 15, 2023


See ya Next Week

Well, that was a lie. The last few weeks had me swamped personally & professionally, so I've been a bit late to deliver these last few weeks of links & learnings. The good news is that (1) I'm much more free now in 2023 to report on the last few weeks of learnings, so I'll be publishing this backlog of links in the following days and (2) I've been organizing enough of my notes and thinking to start publishing more topical writing! Some things I plan to write about are query & command interfaces (ChatGPT3 - but also macOS Spotlight, and the command bar pattern), my (new!) homelab build project logs, and some opinions about engineering orgs. If any of that interests you, stay tuned!

🏎️ Building Fast & Resilient Web Applications

Building Fast & Resilient Web Applications

Ilya Grigorik delivered a talk about web application performance and resiliency at Google I/O 2016 and graciously summarized his key points (with timestamps!) on his blog. In his talk he busts common resiliency assumptions teams make when as they deliver their applications, using excellent sleuthing on real applicaiton metrics and network availability data. He expands further by pointing out different team mindsets that lead to sub-optimal performance posture, and also offers concise tactical solutions to solving some of the resiliency problems we have on the web today. While this is far from the first talk about web performance out there, it is one of the more concise and well-considered. I definitely suggest checking it out and watching the full video!

🕊️ ACM Code of Ethics and Professional Conduct

ACM Code of Ethics and Professional Conduct

Lack of professional standards, and accreditation, among others, is a common argument against software developers & professionals truly being "engineers". That's why I'm glad to discover that a code of ethics and professional conduct exists. It's general enough to apply itself to anyone that practices software, and it provides useful guiding principles for working on systems with software.

WorldWideWeb: Proposal for a HyperText Project

WorldWideWeb: Proposal for a HyperText Project

This is one of the original proposals that eventually gave birth to the web as we know it. In particular this introduces HyperText, which was sold as a single user interface to store and access disparate and varying forms of data at CERN (reports, notes, "data-bases", etc.). It introduces the navigation of having your client (a browser, or a terminal) read through pages, and follow the links you select to the next hypertext page. I won't summarize the rest of the document, because well, it's history and I encourage you to read it yourself but things that did jump out at me we're:

  1. The abstract starts off confronting the team headcount and resource needs (4 computer engineers, 1 programmer), each with their "state-of-the-art" workstation (80k USD in 1990 dollars, approximately 182k USD as of this posting).
  2. The authors include both an Objectives (TODO) and Non-Objectives (won't do). Cool to see a classic project management trick to manage scope and focus work employed here.
  3. Besides X and IBM mainframes, the authors focused on supporting Macintosh and NeXT software and machines.

👋 See ya Next Week!

I promise!

I write about engineering, technology, HCI and the future of computing. If you like what I have to say, feel free to buy me a coffee and/or subscribe below for updates.