planning
The Thing-deadline calculus
The best-laid plans
But bulldozers move mountains
Good design is redesign
Obsessed with absolute numbers
A warning against the limitations of my own prescriptions
The plan must anticipate all that is needed
Many a corner office
Individuals matter
Driving engineers to an arbitrary date is a value destroying mistake
The value-destroying effect of arbitrary date pressure on code
An Article by Gandalf HudlowThe mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™!
What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™.
Hofstadter's Law
An Idea by Douglas HofstadterIt always takes longer than you expect, even when you take into account Hofstadter's Law.
Planning doesn't make for better software
A Fragment by Robin RendleMy own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it.
Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me.
After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64.
Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way.
Yagni
A Definition by Martin FowlerYagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from Extreme Programming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it".
Why Keep a Field Notebook?
Pick one thing
I recently started a field notebook assignment for my upper-level Ecology class at the University of Montana. I asked my students to pick one “thing” and observe it carefully over the entire semester.
In addition to their field notebooks, the students also had to suggest at least ten research questions inspired by their observations.
Lab notebooks
Most of my colleagues who conduct laboratory research not only keep extremely thorough and complete lab notebooks, but they teach their students how and why to keep data in them. Some labs even have friendly competitions in which prizes for the best-kept notebooks are awarded.
In stark contrast to the vibrant culture of keeping lab notebooks in molecular biology, my informal polling suggested a lack of interest in notebooks in field biology.
“I have a GPS for that.”
“My data are in a spreadsheet.”
“I write things down when I get home.”
“I have a computer.”The general consensus seemed to be that field notebooks are quaint, archaic, and obsolete in field biology.
Hybrid journals
The most useful and interesting notebooks of field biology are hybrids; as well as recording details and data of field research, they record the observations, thoughts, musings, and peregrinations of the author.
A fertile incubator
Another value of field notebooks is their ability to serve as an incredibly fertile incubator for your ideas and observations. By jotting down interesting observations, questions, and miscellaneous ideas, your field notebook can serve as a powerful catalyst for new experiments and projects.
Best practices
- Use a hardbound notebook.
- Keep your contact information in a prominent location.
- Write for yourself and for posterity.
- Write pertinent field information with every new entry. You should enter the date, time, and location at the top of every page.
- Add information on your location.
- Record your methods.
- Make backup copies.
- If you use abbreviations, make sure there is a key in your field notebook.
- Don’t leave home without it.
- Form a writing habit. Thomas Jefferson was such an inveterate chronicler of daily events in his notebooks that he even took the time to record the weather four times on the day he helped write the Declaration of Independence. So unless you have something far more pressing than writing the Declaration of Independence, you have no excuse for avoiding your field notebook!
- Set up a structure for your field notebook.
- Create an index.
- Treat your field notebook like a scrapbook. You should view your field notebook as a central clearinghouse for miscellaneous information that is relevant to your research project. If there are related bits of information that you will find useful later on, sketch them, write them down, photocopy them, and staple or tape them in your notebook.