Things You Should Never Do
An oldie but a goody. I sure wish there was a part 2, but at least we've got part 1.
About Me
Helping my Friendgineers whenever possible
Latest Articles
-
Indirection Vs. Abstraction
Abstractions may be indirections, but indirections are NOT abstractions. Confuse them at your own peril. -
Testing Is More Than Preventing Breakage
If you think about tests as the last thing you do you're missing out on some of the biggest benefits of testing. You can learn a lot about what your code SHOULD do by thinking about your tests first. -
Stuttering
Sometimes we are our own worst enemy. Here's a story of my spending WAY too much time trying to figure out why one of the core functions of one of my core tools was broken. Even though it wasn't. It can happen, but that's probably not the most likely thing to be wrong. -
Optimization
You can find lessons in the strangest things if you let yourself. There are even lessons to be learned from the holes in a bar of soap. -
Writing Legacy Code
One of the hardest things for a person to admit, to themselves or others, is that some painm they're feeling is self-inflicted. But it's also one of the things that has the highest return on investment. Or to put it another way, the code we write is hard to work on because we wrote it that way. So it's up to US to do something about it. -
Who Do You Love?
When you love the right thing you know what to do and how to move forward. When you focus on the wrong thing then the path forward isn't nearly as clear. -
Practice Makes Perfect?
Practice, practice, practice. Do that enough and you'll become an expert. That's all you need to do and all you need to know, right? Not quite. It's important, even critical, but it's NOT enough -
Power Dynamics
You always need to be careful what you say, because you can't be sure how people will here it. Add in a power differential and things can easily go off the rails. -
Exsqueeze Me?
There are lots of good reasons to remove tests. There are even more reasons to keep them. Or, if there's a problem, FIX them. -
The Messy Middle
It's hard to be stuck in the middle. But if you pay attention and know that important things can happen in the middle you can turn the messy middle into an advantage.
Categories
it-depends
(70)
context
(62)
agile
(37)
cognitive-load
(34)
tdd
(33)
learning
(32)
systems-thinking
(32)
code-quality
(28)
code-for-the-maintainer
(23)
career
(22)
refactoring
(21)
planning
(20)
best-practices
(18)
martin-fowler
(18)
kent-beck
(17)
testing
(17)
domain-driven-design
(16)
engineering-excellence
(16)
devops
(15)
mmmss
(15)
ownership
(15)
trying-to-do
(15)
decisions
(14)
software-engineering
(14)
code-review
(12)
development
(12)
wip
(12)
architecture
(11)
assumptions
(11)
yagni
(10)
bounded-context
(9)
non-functional-requirements
(9)
scope
(9)
tech-debt
(9)
unix-way
(9)
book-review
(8)
code-smell
(8)
documentation
(8)
naming
(8)
productivity
(8)
geepaw
(7)
hyrums-law
(7)
isq
(7)
tim-ottinger
(7)
tyranny-of-or
(7)
api
(6)
biases
(6)
chestertons-fence
(6)
design
(6)
eisenhower
(6)
flow
(6)
life
(6)
storytelling
(6)
tuckman
(6)
big-ball-of-mud
(5)
comments
(5)
debugging
(5)
feedback
(5)
time
(5)
tools
(5)
change
(4)
done
(4)
goals
(4)
observability
(4)
purpose
(4)
unit-test
(4)
user-stories
(4)
value
(4)
autonomy
(3)
broken-window-theory
(3)
drive
(3)
hillel-wayne
(3)
models
(3)
working-backward
(3)
constraints
(2)
continuous-learning
(2)
customers
(2)
dan-north
(2)
date
(2)
deming
(2)
distributed-systems
(2)
domains
(2)
drucker
(2)
dry
(2)
engineers
(2)
errors
(2)
legibility
(2)
measurement
(2)
mobbing
(2)
noestimates
(2)
object-oriented-programming
(2)
ooda
(2)
opinions
(2)
optimization
(2)
optionality
(2)
partners
(2)
platform
(2)
pm
(2)
priority
(2)
prs
(2)
rca
(2)
readability
(2)
rubber-duck
(2)
simple
(2)
teams
(2)
tradition
(2)
virtues
(2)
wat
(2)
winnie-the-pooh
(2)