Grow, Like a Tree Not a Cancer

 As ever, Mandy Brown casually drops a blog post that makes you examine the everyday meaning of words:

One of the imperatives in contemporary, professional work culture is to “grow.” There is often a sense of height or largeness with that imperative, as if growth must be measured in your distance up the ladder, your territory across the way. In The Soul’s Code, James Hillman implores us to think rather of growing down, of growth not of branch but root, of becoming more grounded, sturdier, less able to be pushed around by the whims of others.

I love this idea of “growing down”, becoming more rooted and sturdy.

It got me thinking about the word “growth”.

Contemporary usage of the word in business often communicates human intervention and imposition against an otherwise natural outworking.

“Growth” in a forest is different than “growth” in business.

In business, we talk about “growth hacking” as if the natural cadence of growth isn’t sufficient. It requires modification because we deem it insufficiently slow.

We “engineer” growth instead of tending it.

Personally, when I say I want to grow, I mean like a tree. Not like a cancer.

Tree growth responds to its environment and integrates with its ecosystem. Growth is sustainable, balancing expansion and repair. It scales in harmony with its context.

Cancer growth is selfish, consuming resources at the expense of its host. Growth is uncontrolled until the system that supports it collapses. It scales through extraction until failure.

When we talk about the growth of technology in the 21st century, which kind of growth do you think best describes it?

“Hey, {social media | AI} grew so big, we all sat together under its canopy and enjoyed the shade.”

Said no one.

More likely: “Hey, {social media | AI} grew so big, it metastasized beyond what society could bear and now look at the mess we’re in.”


Reply via: Email · Mastodon · Bluesky

Jim Nielsen's Blog

02 Dec 2025 at 19:00

Malicious Traffic and Static Sites

 I wrote about the 404s I serve for robots.txt. Now it’s time to look at some of the other common 404s I serve across my static sites (as reported by Netlify’s analytics):

  • /wp-login.php
  • /wp-admin
  • /news/wp-includes/wlwmanifest.xml
  • /login/
  • /wp-includes/wlwmanifest.xml
  • /news/wp-includes/wlwmanifest.xml
  • /website/wp-includes/wlwmanifest.xml
  • /info.php

I don’t run WordPress, but as you can see I still get a lot of requests for wp-* resources.

All of my websites are basically just static files on disk, meaning only GET requests are handled (no POST, PUT, PATCH, etc.). And there’s no authentication anywhere.

So when I see these requests, I think: “Sure is nice to have a static site where I don’t have to worry about server maintenance and security patches for all those resources.”

Of course, that doesn’t mean running a static site protects me from being exploited by malicious, vulnerability-seeking traffic.

Here are a few more common requests I’m serving a 404 to:

  • /.env
  • /.env.production
  • /.env.local
  • /.env.dev
  • /.git/config
  • /data.sql
  • /database.sql.gz
  • /mysql.sql
  • /db.sql.gz
  • /backup.sql.gz
  • /database.sql

With all the magic building and bundling we do as an industry, I can see how easy it would be to have some sensitive data in your source repo (like the ones above) end up in your build output. No wonder there are bots scanning the web for these common files!

So be careful out there. Just because you’ve got a static site doesn’t mean you’ve got no security concerns. Fewer, perhaps, but not none.


Reply via: Email · Mastodon · Bluesky

Jim Nielsen's Blog

30 Nov 2025 at 19:00



Refresh complete

ReloadX
Home
(83) All feeds

Last 24 hours
Download OPML
Annie
Articles – Dan Q
*
Baty.net posts
*
bgfay
*
Bix Dot Blog
*
Brandon's Journal
Chris McLeod's blog
*
Colin Devroe
*
Colin Walker – Daily Feed
Content on Kwon.nyc
Crazy Stupid Tech
*
daverupert.com
Dealgorithmed
Human Stuff from Lisa Olivera
*
jabel
James Van Dyne
*
Jim Nielsen's Blog
Jo's Blog
*
Kev Quirk
*
Manton Reece
*
Manu's Feed
*
Notes – Dan Q
On my Om
*
QC RSS
*
rebecca toh's untitled project
*
Rhoneisms
*
Robert Birming
*
Scripting News for email
*
Simon Collison | Articles & Stream
strandlines
*
The Torment Nexus
*
thejaymo

About Reader


Reader is a public/private RSS & Atom feed reader.


The page is publicly available but all admin and post actions are gated behind login checks. Anyone is welcome to come and have a look at what feeds are listed — the posts visible will be everything within the last week and be unaffected by my read/unread status.


Reader currently updates every six hours.


Close

Search




x
Colin Walker Colin Walker colin@colinwalker.blog