For example, I recently discovered this site https://bomwiki.com/ which attempts to make a giant dependency graph of all the parts used to make large machines. This would not be possible without it being a wiki.

The problem with ebikes is any unlicensed driver can get one, and go 40mph on a sidewalk without any practical way to hold them accountable.

I live near one of the busiest biking + walking trails in the country, and the egregious disrespect and recklessness of ebike's and scooters is insane to me. Even on the parts of the trail that are split into two or three sections (walking, running, and biking sections) I see people going 20-30mph weaving in and out of walkers. What's crazy is it would be safer if they were operating gas motorcycles, because atleast you could hear them coming.

Other commentors have made good points that these guardrails are counter productive for well intentioned cyber security, because I can't use it to test and harden my own software.

I really appreciate this perspective as It helps fill in gaps in my mental model of where our economy has gone wrong the last 50 years. Unrelated but - I've read an interesting paper on how allowing private banks to create money has led to the infinite profit growth goose chase...

At work I have a great brain dump + TODO list tracker via custom API + MCP into confluence, using confluence pages as the app state. The website is so bloated it takes like 20 seconds to go from "idea" to getting it written down. Im now able to avoid all of that and make ~ MY ~ perfect UX while still being a good corporate employee.

The difference here is just one word in the prompt, but serves as an example of how just a little but of deliberate thought in one's prompt can yield massive efficiency in outcome.

Whats wild to see both online and at work, non engineers given vibe code like tools will quickly show their ignorance to the importance of deliberate design and need for specific instructions one learns via coding. The "missing semi colon" meme is an example of the intuition we all developed early in our coding careers.

Many people are hoping AI can build and design for them, when in reality the deliberate design choices up front are as important if not more so than before AI.

The example I was thinking of would be a vibe coder having it "read my emails every hour" only for claude to read the same 1000 emails over and over...

One example - was giving several agents different sub problems to solve in a complex ML / forecasting problem. Each agent would write + run + read a jupyter notebook. This worked ok, the notebooks would be verbose but it was fine... until one of them wrote out hundreds of thousands of rows to a cell output, creating a 500MB ipynb file. Claude tried several times to read it and it used my entire context limit.

The solution was to prescribe a better structure of doing the world (via CLI analysis scripts + folders to save research results to). But this required some planning, thought, and design work by me the operator.

When I see people spending $10k a month in tokens, I can only assume they are taking lazy hands off approaches to solving problems with the expensive hammer that is claude code. EX: have claude read all your emails every day... the lazy solution is to simply do that, but a smarter solution is to first filter the email body HTML to remove the noise.

The better solution is developers and designers taking a sense of pride and craftmanship in this sort of thing. So many of my least favorite interfaces are presumably designed and implemented in an environment with a gigabit connection to their apps backend so they never catch it.

A few years ago I saw some very interesting custom ergonomic setups optimized for traveling + flying.

One person with a thinkpad is able to get the monitor to be 180 degrees flat w/ the keyboard, and can hang it off the seat. He also brings a split ergo keyboard with a lap mount.

Another person did something similar with a M1 laptop, but needs an Ipad to act as the external monitor (laptop stays in bag) with a built and designed from scratch split ergo keyboard.

My other grandpa, controversially used a big chunk of their wedding money on a good camera. They traveled the world and lived abroad for several years right before and after my mom and aunt were born. Because of this, we are all able to see such a fascinating and meticulous glimpse into their lives. Each photo tells a story even if the story is boring, but I really appreciated the small details. Even random pictures of cars that my Grandpa thought were cool. Or the mean guard dog they had in Taiwan while it was still a puppy. Or my mom on the Trans Siberian Railroad in the middle of the Cold War.

These stories and my own appreciation of photography have made me realize how valuable every photo I have is, and I'm willing to put in effort to save them. When I'm old and dying of dementia, I'll be able to look back at my life in incredible detail one last time. Even the dumb meme's I decided to save will tell a story.

I still have a deep appreciation for living in the moment and knowing not everything should be captured, but we live in an era where I have a really good camera in my pocket at all times, and the ability to store all those photos forever cheaply.

I also have a 14TB RAID 5 NAS at home. And my Desktop PC has 6TB of RAID 5 (had that first, mostly used for video games these days).

But the closest answer I can give you (without detailed examples of work projects) is I can prototype things faster than my team of 5 devs + 1 BA + 1 Manager before AI / Covid. The speed isn't just the faster code generation, but a fundamental paradigm shift from the commonly accepted project management philosophies. Agile and scrum are (in my experience) meant to protect developers from "wasted work" or "throwaway code" and also placate this non technical stakeholder fantasy that they know the best about product and can micromanage their way into a predictable timeline.

I have effectively been working as a team of 1 and I have been able to prototype things in days or weeks that would of taken months before. 95% of the code generated by claude is throwaway but the goal is to discover the real requirements faster. In the old model every step and possible risk needs to survive 3 meetings. If the story points are arbitrarily high then we have to split the tasks into more tasks.

Ironically, the obsession of quantifying productivity is what killed the productivity. People that live through spreadsheets would rather have 10 units of measurable productivity vs 50 units of unmeasurable productivity.

Every time I've created my own backup script I realized knowing what to delete and when is not easy. IMO the practical solution to this is to just pay for more storage (within reason).