Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

absolute paths #57

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/content/posts/2023-07-10-lessons-in-naming-minecraft.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,13 @@ If you had to guess what it means, what would you say?

When Minecraft developers were coming up with a way to generate terrain for new worlds, they wanted enough randomness to be unique and interesting, but enough predictability so they could simulate features of real world geography. They chose Perlin noise, a special type of randomness that introduces smoothing for a more organic look and returns consistent results using the same seed.

![Sample Noise: Simplex vs. Perlin](/assets/i/post-noise-types.png)
![Sample Noise: Simplex vs. Perlin](https://practicaldesignsystems.com/assets/i/post-noise-types.png)

Hang with me on this…

Developers modified the noise output in different ways and created a library of noise maps with different characteristics. Then — and this is the important bit — they used names to convey the mental metaphor for each map: continentalness, erosion, peaks & valleys, temperature, humidity, etc.

![Sample Noise Maps: Continentalness and Erosion](/assets/i/post-noise-continentalness.png)
![Sample Noise Maps: Continentalness and Erosion](https://practicaldesignsystems.com/assets/i/post-noise-continentalness.png)

One of the Minecraft developers who works on terrain generation explains in [a recent talk on the topic](https://www.youtube.com/watch?v=ob3VwY4JyzE):

Expand All @@ -30,4 +30,4 @@ I’ve talked about [useful naming conventions for design systems in a previous

And for the curious, *continentalness* defines the relationship between ocean terrain and inland terrain. In other words, it’s used to shape continents. It's amazing what you can get when you combine all of this randomness together in intentional and meaningful ways, isn't it?

![Merging noise maps to create full biomes](/assets/i/post-noise-biomes.png)
![Merging noise maps to create full biomes](https://practicaldesignsystems.com/assets/i/post-noise-biomes.png)
25 changes: 25 additions & 0 deletions src/content/posts/2023-07-11-fake-news-score.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
title: The fake news score
description: Discovering the real value of what you're building.
date: 2023-07-11
tags:
- value
- mvp
- over-optimize
---

Years ago, I worked on a platform that billed itself as a newsroom in a box. For significantly less than it would cost to develop all the design and functionality required for a robust newsroom product — design, development, paywall integration, analytics, newsletter integration, ad management, user accounts, AP feeds, etc. — this platform would be turnkey.

One of the selling points was an easy-to-read score on your site’s dashboard that graded the overall health of your site and setup based on a number of key business intelligence measurements and characteristics. Each day, you would log in and, at a glance, get a sense of how your site was performing.

Here’s the crazy part: the score wasn’t real.

Or more accurately, it wasn’t **automated**.

Each day, someone would gather data from the key measurements for each site on the platform and manually enter them into a spreadsheet. The score was then calculated and displayed on each site’s dashboard. Most people assumed it was some kind of real-time measurement, but it was just someone manually crunching numbers every day.

For weeks, we had discussed ways to automate this process, but many of the things we wanted to measure didn’t have an API or any other easy way to get at the data. So we decided to do it manually, at least to start.

The breakthrough moment was when we realized that the value of the score wasn’t real-time automation, it was insight. The people involved in the project were legends in the news industry, so their insights were highly sought after. That was the real value.

There’s a danger, especially when building systems, to lose sight of what is genuinely valuable in favor of increased automation. [Don’t optimize too early!](https://practicaldesignsystems.com/daily/beware-premature-optimization/)