• Home
  • Blog
  • Projects
  • Bookshelf
  • About
← Back to all posts

Start Small, Accept Change

Published ....
Last modified ....

Share this post on BlueskySee discussion on Bluesky


As I have grown into a more experienced web developer, I have been thinking a lot more about this tweet by Joel Hooks:

Twitter

There’s a tendency to jump straight to step 32 of the “new thing” vs focusing on steps 1 and 2.


“what’s the next smallest step that we can do?”
Skipping to the end can often lead to failure and hard feelings when you’ve put in a lot of work and it gets a 👎 Baby steps. 🐣 — Joel 🌧 (@jhooks)

July 4, 2018

I could spend the better part of a weekend just enumerating all the times that I jumped to a solution for a problem I was working on at the time.[1]Jump to footnote Skipping past the the important groundwork of framing the problem space, and evaluating, as well as reevaluating, the problem.

Its difficult as an engineer, to have the patience to step back and reevaluate a problem before jumping to a solution. It takes a lot of critical thinking to determine what the actual ask is for a new feature, or what the cause of a bug might be.

The first thing I would generally suggest to new or junior developers is to take a step back from the problem before diving into it with a concept for a solution.

That can either take the form of getting up to go for a walk, grabbing a cup of coffee or tea, or even just sleeping on it to approach from a clear headed state.

In general, I think there are two constants in software engineering (especial web development):

  1. Everything changes
  2. Most difficult technology problems are actually people problems at the root[2]Jump to footnote

As with most advice however, the key takeaway here is that things change, specifically code will change. Don't feel like you need to write the correct solution the first time you attempt to solve a problem.

Frequently, on your way to that 32nd step in developing your feature or application, you will encounter steps 5, 18, and 27 where you throw out all your current work and rewrite it from the ground up because you discovered another pattern or stumbled across some other insight into your work.

Its ok to accept these rewrites, because if you skipped them and jumped to step 32, you might have missed out on those opportunities to learn more about what you were building.

As I was chipping away at the concepts behind this blog post, I was reminded of the many long summers growing up around the house as a kid helping my dad on some of his small construction projects. These projects varied, and including building out a new back deck, building out a new front deck, redoing our siding, or the multitude of other projects. The part I remembered the most was a saying that my dad taught me:

"Measure twice, cut once"

It didn't really resonate with me too much when I was a little kid, I thought it only applied to construction, however I have now realized that it applies to a lot of things in life as well.

I do think though, that there were a few parts missing from this wisdom, and I would generally expand it to be:

"Measure twice, cut once. Always prepare to buy more lumber."


Footnotes:

↩Back to reference

A part of me would like to think that I have gotten better at the skill of not skipping that groundwork, but I know I still do make the same mistakes.

↩Back to reference I should really write up a post all on its own on this point


Tags:

Web DevelopmentSide Projects

Loading...

Related Posts

Web Development

Website Redesign v11

....

I've once again updated my personal website, this time powered by my own RSC framework and a custom CMS solution as well!

Onboarding Your New AI Teammate

....

Are we reinventing the wheel when it comes to onboarding new AI agents to a codebase, when we already have primitives available for onboarding humans?

Quick Tip - Theme Aware Images

....

Have you ever found the need to change the image you render on a web page based on the current preferred color scheme of your theme?

Async Class Creation In JavaScript

....

Have you ever wanted to create a class in JavaScript or TypeScript but also have the initialization be async? Here's a quick tip on a pattern that I've used in the past!

Website Redesign v10

....

I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!

Server Side Rendering Compatible CSS Theming

....

A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!

Podcasting By Hand

....

A brief overview on how we launched The Bikeshed Podcast, including a deep dive in our recording and distribution workflows!

Quick Tip - Specific Local Module Declarations

....

A quick tip outlining how to provide specific TypeScript type definitions for a local module!

On File-System Routing Conventions

....

Some rough thoughts on building a file-system routing based web application

You're Building Software Wrong

....

Slicing software: why vertical is better than horizontal.

Single File Web Apps

....

What if you could author an entire web application in a single file?

Resetting Controlled Components in Forms

....

A quick way to handle resetting internal state in components when a parent form is submitted!

A Quick Look at Import Maps

....

A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!

Recommended Tech Talks

....

A collection of tech talks that I regularly re-watch and also recommend to everyone!

Request for a (minimal) RSC Framework

....

Some features and functionality that I'd like within a React Server Component compatible framework.

Bluesky Tips and Tools

....

A (running) collection of Bluesky tips, tools, packages, and other misc things!

The Bookkeeping Pattern

....

A quick look at a small but powerful pattern I've been leveraging as of late!

TSLite

....

A proposal for a minimal variant of TypeScript!

Monorepo Tips and Tricks

....

Sharing a few core recommendations when working within monorepos to make your life easier!

Next.js with Deno v2

....

This is a quick post noting that Next.js should now work with Deno v2!

Don't Break the Implicit Prop Contract

....

React components have a fundamental contract that is often unstated in their implementation, and you should know about it!

A Better useSSR Implementation

....

Replace that old useState and useEffect combo for a new and better option!

My Current Dev Setup

....

A quick look at the applications and tools that I (generally) use day to day for web development!

Abstract Your API

....

Proposing a solution for sharing core "business" logic across services!

Tip: Request and Response Headers

....

There's a common gotcha when creating Web Request and Response instances with Headers!

Using Feature Toggles to De-risk Refactors

....

Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors

Hohoro

....

A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!

Custom Favicon Recipes

....

Two neat tricks for enhancing your site's favicon!

Corporate Sponsored OSS

....

The various risks and pitfalls of open source software run by corporations.

The Library-Docs Monorepo Template

....

A monorepo template for managing a library and documentation together.

Building Better Beacon

....

How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.

Project Deep Dive: Tails

....

A(nother) deep dive into one of my recent side projects; tails - a plain and simple cocktail recipe app.

Churn Anxiety

....

When did semver major changes become so scary?

Service Monitors and Observability

....

Leveraging service monitors properly to improve service observability.

On Adopting CSS-in-JS

....

A brief recap of how Wayfair changed it's CSS approach not once but twice in the span of 5 years!

Project Deep Dive: Microfibre

....

A deep dive into one of my recent side projects; microfibre - a minimal text posting application

Pair Programming

....

Pair programming can be good sometimes - but not all the time

Suspense Plus GraphQL

....

A few thoughts on using Suspense with GraphQL to optimize application data loading

You've Launched, Now What?

....

A few thoughts on what to do after you launch a new project

Taking a Break

....

A few quick thoughts on burn out and taking a break

Managing Complex UI Component State

....

A few thoughts on managing complex UI component state within React

Understanding React 16.3 Updates

....

A quick overview of the new lifecycle methods introduced in React 16.3

CSS in JS

....

A few thoughts and patterns for using styled-jsx or other CSS-in-JS solutions

Redesign v6

....

A few thoughts on the redesign of my personal site, adopting Next.js and deploying via Now

JavaScript Weirdness

....

A few weird things about JavaScript

Calendar

....

Building a calendar web application