diff --git a/src/content/blog/2023-02-13-the-exceptions-are-more-interesting.md b/src/content/blog/2023-02-13-the-exceptions-are-more-interesting.md new file mode 100644 index 0000000..408fd3a --- /dev/null +++ b/src/content/blog/2023-02-13-the-exceptions-are-more-interesting.md @@ -0,0 +1,43 @@ +--- +title: The exceptions are more interesting +date: 2023-02-13T22:29:48.797Z +slug: 2023-02-13-the-exceptions-are-more-interesting +author: Thomas Wilson + +--- +I'm going to open with three buzzwords and a bland sentiment: + +Theories, policies, and frameworks are useful. + +Things like \"do the uncertain things first\" or \"automate the process\" are snappy little things that help us conquer problems by dividing, or sorting, or some other action. + +Left alone, people will pretty much always make a theory expand. They'll only do uncertain things, and automate all the once-a-quarter tasks they can find. + +Frameworks that do more, probably don't do it as well. Theories get fuzzier when they try to explain more. You cannot be specific and generic at the same time. Every \"clarifying\" *but only when* or *otherwise you should* shrinks the on-the-ground usefulness of a policy. + +Always be honest... except with children about some things. + +Judge people by their actions not their words... unless their words are hateful. + +You'll collect a lot of frameworks on your journey through apprentice to master. Keep them like every other tool: in a belt with their friends. + +Earlier in my career I loved the rules. I loved the certainty of knowing what to do, and when. + +Later in my career, my ears perk when I hear about exceptions to rules. Then I'll spend some time talking about them. + +I used to think this makes every framework or theory useless. I don't think that's true now. It's no more true than how money and laws and language are all made up. They all seem pretty useful. + +When something becomes an exception, you might have found the limit of your approach. You've found something you haven't accounted for, or something you cannot do. + +What you should not do, with this fresh exception, is ignore or massage or change it. That would be putting the solution before the problem. + +Say your proof-reading checklist works well for blog posts, but not an academic essay. Or your data analysis won't work on a sample size below 50. You've found a new problem. + +Everything has a limit to what it can help you with. + +Everything has a long tail of exceptions. Taken alone, these exceptions will feel like a one off. Taken together, they make up the majority. + +And left alone, a lot of people will simplify, and try to make a theory expand. + +But otherwise *all* we have is One Off Exceptions. I reckon we could group some of them into similar buckets, and stop re-inventing the wheel... +" diff --git a/src/routes/blog/[slug]/+page.svelte b/src/routes/blog/[slug]/+page.svelte index c4cfae7..18fc27b 100644 --- a/src/routes/blog/[slug]/+page.svelte +++ b/src/routes/blog/[slug]/+page.svelte @@ -35,19 +35,34 @@

{intlFormat(date)}

-
+
{@html post.content} See other articles
- diff --git a/src/routes/engineering-principles/+page.svelte b/src/routes/engineering-principles/+page.svelte index 8acce33..405640b 100644 --- a/src/routes/engineering-principles/+page.svelte +++ b/src/routes/engineering-principles/+page.svelte @@ -1,47 +1,70 @@
-
-

Software Engineering Principles

-

This is a collection of things I've learned about, and while, building software.
- They are best guesses.
- I reserve the right to be completely wrong about all of them.

-
- -
- -
+
+

Software Engineering Principles

+

+ This is a collection of things I've learned about, and while, building + software.
+ They are best guesses.
+ I reserve the right to be completely wrong about all of them. +

+
+
+ +