Developer Rules of Thumb

 https://ae01.alicdn.com/kf/HTB1eBcJd7fb_uJjSsrbq6z6bVXa0/10pcs-American-Thumb-Tip-Large-Size-Magician-Trick-Magic-Gimmick.jpg

  1. K.I.S.S. - Keep It Simple Silly
  2. "A Place for Everything and Everything in its place"
    1. Eliminate Redundancy aka Orthogonalization
      1. In human process design
      2. In system, process, and database design
      3. In code
      4. In communication - Speak Concisely
    2. Eliminate Waste/Noise
      1. In human process design - toil
      2. In system, process, and database design
        1. Unused features
        2. Levels of indirection
      3. In code
        1. Unnecessary code
        2. Unreachable code
      4. In communication
        1. Digression & change of topic
        2. Pedantry
        3. Filler words
  3. Minimize Cognitive Load
  4. Always be working yourself out of a job
    1. Identify and formalize/eliminate repeating manual work
    2. Automate/eliminate formalized manual processes with software
    3. Design, write, document software so that an uninitiated, junior developer can quickly own it
    4. Train team to replace you
  5. Foster a Personal Sense of Urgency
    1. Engineers are seldom if ever the ones holding the purse strings.  Throughout your career, you'll likely be beholden to someone who isn't technical.  They hire you to solve a problem they have.
    2. There's an assumed (or explicit) return on investment for solving that problem.  If you take too long, the cost of solving the problem may exceed the benefit.
    3. You need to solve the problem in such a way that the future cost to maintain, support, or expand the solution doesn't hamstring your employer.  The business often won't fully appreciate this.  The incentives of the employment market run contrary to it.
    4. Speed and Quality are necessarily at conflict.  To improve, you must simultaneously push on both fronts.

Comments

Post a Comment

Popular posts from this blog

Engineering Truisms

This is a brief collection of quotes, laws, and truisms that I've gathered over the years.  I've kept those that have consistently proved themselves across organizations and projects during my career.
Read more

The Telescoping Constructor (Anti-Pattern)

Image
The Telescoping Constructor Looks like this: Widget(varA) {...} Widget(varA, varB) {...} Widget(varA, varB, varC) {...} or Widget widget = new Widget(x); widget.setVarA(...) widget.setVarB(...) widget.setVarC(...) There are both shared and specific problems for each variety.  Let's talk about both. The 1st case, supernumerary constructors. What's wrong with this? Well, the good news is you provide  quiet consumption since there's a bespoke constructor for every use case.  Rather than have noisy construction, where the consumer must fill in a bunch of nulls, you move the noise into the implementation.  We shouldn't make assumptions on how many times the class will be used, so keeping the complexity to ourselves is generous and will lead to a more maintainable macro system. However, one problem here is that the end consumer is not restricted in their choice of constructors.  Like shopping at the super market, somet
Read more

A Strategic Approach to Precision Process Automation

Image
The global tech labor arbitrage trade has matured since its start in the Clinton era.  We've witnessed real estate in places like Mumbai and Singapore appreciate to levels rivaling NY and London.  The rising tide lifts all boats.  As global tech labor costs have flattened somewhat, software has gotten more expensive to produce and maintain.  The market is betting that AI will largely alleviate this by supplanting much of software engineering as a practice.  However, until this plays out, being judicious about when and how to use software is more important than ever.   While it's constructive to build software systems as "black boxes," it's folly to view them as crystal balls.  Increasingly, software is operations .  That engineer who knows the code like the back of his hand is your foreman.  Code is not static, it's constantly evolving to meet business demands and improve efficiency.  "Software Engineering is programming integrated over time."  Th
Read more