Posts tagged “technical”
62 posts total. See Filtering and Navigation for tips on how to find the bits in which you're interested.
Subscribe to posts tagged "technical":
- 6 posts
- 1 post
- »
I've published another EngFlow blog post, but not about Bzlmod this time. I will, however, be talking live on the Internet about Bzlmod tomorrow.
- 1 post
- »
I've published my fourth EngFlow blog post, about accessing canonical repository names under Bzlmod in a portable way using macros or custom Make variables.
- 2 posts
- »
I've published my third EngFlow blog post, about the proper use of Bazel's rules_pkg and avoiding silent breakages.
- »
I've published my second EngFlow blog post, explaining the necessity of using runfiles libraries with Bzlmod. It also tries to fill a lot of runfiles documentation gaps in general.
- 1 post
- »
I ended my post-Apple sabbatical by joining EngFlow in March, which is at once a new start and a bit of a homecoming. I also just published my first EngFlow blog post, Migrating to Bazel Modules (a.k.a. Bzlmod).
- 1 post
- »
The "Making Software Quality Visible" series will resume shortly. Before that, I'm excited to share a new training project I've developed. I'm also about ready to start a business or find another job soon.
- 11 posts
- 3 posts
- »
Vital Signs are a collection of signals designed by a team to monitor project and process health and to resolve problems quickly. This is as opposed to so-called, performative "data-driven decision making."
- »
Contract and Collaboration tests are medium sized tests that validate how one's own code interacts with an external dependency. Internal APIs are adapters that insulate most of your code from changes in such dependencies.
- »
Test Doubles are lightweight, controllable objects that replace production dependencies in smaller tests. Adding seams in your logic to accommodate them enables much faster, more reliable, more thorough testing.
- 4 posts
- »
Michael Feathers's definition of "legacy code," his concept of "seams," and Scott Meyers's "most important design guideline" are profound insights. Perhaps my "electrical outlet" example will also prove useful.
- »
Developers (and those who work with them) are often misguided regarding the tradeoffs between quality, risk, and productivity. Here I take aim at two common bad habits and one common bad attitude.
- »
This is how I figured out how to import Keynote images into my blog as SVG images that scale to any size and are stylable.
- »
I learned much more about software quality and automated testing at Google—but more importantly, I began learning how to change culture.
- 2 posts
- »
My first exposure to software quality issues and automated testing happened by accident while working on navigation systems for US Coast Guard and Navy vessels.
- »
This is the first post in a long upcoming series to discuss and refine the Making Software Quality Visible presentation.
- 2 posts
- »
A serendipitous find demonstrates that, at a high level, systems are systems, and the Quality Mindset applies to them all.
- »
The unsubscribe link is at the very end of the email, if that's how you're reading this. I'll also explain what's going on, and what I've been up to.
- 8 posts
- 1 post
- »
I've released go-script-bash v1.7.0, which contains powerful new test helpers and file system modules, as well as project management improvements.
- 2 posts
- »
I've released go-script-bash v1.6.0, a small release featuring its first user-contributed feature!
- »
Some wheels were meant for reinventing—if sometimes only because we need to teach ourselves how they work!
- 1 post
- »
For most of this time, I've been working in Barcelona with my first paying client, started a new project, wrote a new talk, and have been touring across Europe.
- 1 post
- »
I've released go-script-bash v1.5.0, a relatively small release introducing the lib/prompt and lib/existence modules.
- 1 post
- »
I've released go-script-bash v1.4.0, another large update that includes massive test performance improvements, amongst other significant new features
- 1 post
- »
This blog now features a Let's Encrypt certificate with HPKP, and I hope to share insights and tooling that may be of use to others.
- 1 post
- »
I've just released go-script-bash v1.3.0, which is a massive update, especially for logging and automated testing features
- 6 posts
- 2 posts
- »
I've just released go-script-bash v1.1.0, which adds some major new features, two new builtin commands, and multiple bug fixes and internal improvements.
- »
Some background on the .about.yml project metadata format prompted by an unexpected inquiry from the TODO Group.
- 2 posts
- »
The video of the Surge 2016 version of "The Convergence of Wills", probably my favorite iteration of the talk so far, is now available. Plus a bonus go-script-bash lightning talk!
- »
Just posted a "Hello, World!" example for the new
ReactionMessagetype I added to thehubot-slacknpm.
- 1 post
- »
I've been obsessed with writing a framework for ./go scripts in Bash, and have just released v1.0.0.
- 1 post
- »
I've written a Slack bot in Node.js that files GitHub issues, and a unit testing tutorial in Node.js based on the bot.
- 4 posts
- 1 post
- »
Sometimes, when inspiration strikes, it isn't pretty; in fact, it can be downright painful and horrid. Please don't read this post.
- 3 posts
- »
After a bit of hunting and poking around, I got my Plan 9 virtual machine on the net, installed the Go programming language, and made good on a promise.
- »
I've finally gotten Plan 9 and its rio windowing system running successfully under VMware Fusion 7.1.1 on OS X 10.10.3 and feel like shouting about it.
- »
I've written a new 18F blog post describing my experience using Bitly's oauth2_proxy for the 18F Hub and contributing code changes back to it.
- 10 posts
- 1 post
- »
I've produced a report on the early, promising results of my OpenSSL makefile refactoring experiment, in which I was successful using GNU make.
- 3 posts
- »
I'm experimenting with refactoring OpenSSL's existing recursive Make structure into a top-Makefile-with-includes structure.
- »
To launch the effort to add unit/automated tests to OpenSSL, I've created OpenSSL wiki pages and created the openssl-testing Google Group
- »
While writing the tests for the "goto fail" and Heartbleed bugs, I stumbled upon an xUnit-like pattern for writing tests without a framework.
- 2 posts
- »
I've written a complete proof-of-concept unit and regression test for the Heartbleed bug, and am pretty happy with it
- »
I wrote a rough skeleton of a proof-of-concept unit test for the Heartbleed bug that I hope to polish and complete over the weekend
- 3 posts
- »
Wrote a new script to update the tags for the playingthechanges.com MP3 files before importing them into iTunes, and accepted a challenge from David Plass
- »
My programming skills still come into play at Berklee, as I wrote a Python script to download the MP3 files from the Playing the Changes website
- »
I've published a new article on AutoTest Central about the Testing Grouplet's Small, Medium, and Large test size schema, and more on the Apple bug.
- 1 post
- »
Apple's recent SSL security bug compelled me to write a blog post for AutoTest Central illustrating how unit testing could've helped prevent it
- 4 posts
- 1 post
- »
The recent Go 1.2 release contains genius test coverage features, but the announcement illustrating them contains an annoying flaw
- 1 post
- »
Extracting the album artwork for Jimi Hendrix's "People, Hell & Angels" from iTunes 11, using vim to change the binary ITC file format to JPEG
- 2 posts
- »
How to create a rechargeable 9V power supply for guitar effects pedals, based on advice from The Gear Page
- »
Modifying the MXR Micro Amp for True Bypass switching, requiring tricky circuit board surgery due to its original surface-mount DPDT switch
- 10 posts
- 1 post
- »
The specific tools the Testing Grouplet, Testing Tech, Build Tools and others developed to improve testing development and efficiency at Google
- 4 posts
- »
Comprehensive notes on maintaining a personal computer backup strategy, based on my Mac OS X experience
- »
The collection of processes Google uses for ensuring software quality, including automated developer testing as promoted by the Testing Grouplet
- »
The basics of how automated tests should--and should not--be written, as promoted by the Testing Grouplet at Google
- »
I learn that I'm still a programmer after writing tools in Ruby and Go to help publish my blog, which I've also now published on Google Code.
- 2 posts
- »
The fundamental object-oriented programming issues which produced Google's testing challenges and the solutions promoted by the Testing Grouplet
- »
The high-level cultural challenges to the adoption of automated developer testing at Google which the Testing Grouplet worked to overcome
- 2 posts
- »
Everything I've been saying and will say in this blog about the Testing Grouplet, Test Certified, and Fixits at Google, compressed
- »
A team of developers within Google dedicated to helping development teams participate in the Testing Grouplet's Test Certified program
- 1 post
- »
The homegrown continuous integration and test system that powered the Testing Grouplet's Test Certified program at Google before TAP
- 3 posts
- 1 post
- »
The before-and-after picture of the Testing Grouplet et. al.'s impact on Google Engineering
- 1 post
- »
The Testing Grouplet's terminology for getting Google engineers to think about the different scopes of automated tests
- 1 post
- »
The Testing Grouplet's program for promoting good automated developer testing practices throughout Google Engineering