\n Are You Solving the Right Problems? \n (via) My primary challenge is that I\n frequently work on the wrong things. I do that often enough I try not to invest a lot of time and energy \n into a path unless my teacher confirms it's the right one. \n

\n\n \n

\n This great article from Thomas Wedell-Wedellsborg explains how I can check I'm working on the right thing\n in a way that uses a reasonable amount of time. He emphasizes reasonable amount of time because many \n frameworks are so time-consuming they're only practical on the strategic level. The simpler frameworks \n tend to assume the first definition of the problem is the easiest and most effective to solve.\n

\n\n \n

\n I think a great way to explain the value of their approach is the slow elevator problem. In it you are the \n owner of an old building with a major problem. Several tenants are threatening to break their lease if you \n don't reduce the wait time and make the elevator faster. Most people would recommend replacing the motor or\n even the elevator. That type of suggestion is what's called the solution space. A solution space is a \n group of suggestions that share a common assumption about the problem. On the other hand if you ask a building \n manager, they recommend putting up a set of mirrors by the elevator. It solves the problem because \"people \n tend to lose track of time when given something utterly fascinating to look at—namely,\n themselves.\" \n

\n
\n The mirror solution is particularly interesting because in fact it is not a solution to the stated problem:\n It doesn’t make the elevator faster. Instead it proposes a different understanding of the problem.\n
\n
\n Note that the initial framing of the problem is not necessarily wrong. Installing a new lift would probably\n work. The point of reframing is not to find the “real” problem but, rather, to see if there is a better one\n to solve. In fact, the very idea that a single root problem exists may be misleading; problems are \n typically multicausal and can be addressed in many ways. The elevator issue, for example, could be \n reframed as a peak demand problem—too many people need the lift at the same time—leading to a solution that\n focuses on spreading out the demand, such as by staggering people’s lunch breaks.\n
\n

\n \n \n

\n I found their example about the number of dogs in shelters educational too.\n

\n\n

\n
\n Identifying a different aspect of the problem can sometimes deliver radical improvements—and even spark solutions \n to problems that have seemed intractable for decades. I recently saw this in action when studying an often \n overlooked problem in the pet industry: the number of dogs in shelters\n
\n
\n…\n
\n\n \n\n
\nLori Weise, the founder of Downtown Dog Rescue in Los Angeles, has demonstrated that adoption is not the only way to frame the problem. Weise is one of the pioneers of an approach that is currently spreading within the industry—the shelter intervention program. Rather than seek to get more dogs adopted, Weise tries to keep them with their original families so that they never enter shelters in the first place. It turns out that about 30% of the dogs that enter a shelter are “owner surrenders,” deliberately relinquished by their owners. In a volunteer-driven community united by a deep love of animals, those people have often been heavily criticized for heartlessly discarding their pets as if they were just another consumer good. To prevent dogs from ending up with such “bad” owners, many shelters, despite their chronic overpopulation, require potential adopters to undergo laborious background checks.\n
\n \n
\nWeise has a different take. “Owner surrenders are not a people problem,” she says. “By and large, they are a poverty problem. These families love their dogs as much as we do, but they are also exceptionally poor. We’re talking about people who in some cases aren’t entirely sure how they will feed their kids at the end of the month. So when a new landlord suddenly demands a deposit to house the dog, they simply have no way to get the money. In other cases, the dog needs a $10 rabies shot, but the family has no access to a vet, or may be afraid to approach any kind of authority. Handing over their pet to a shelter is often the last option they believe they have.”\n
\n\n
\nWeise started her program in April 2013, collaborating with a shelter in South Los Angeles. The idea is simple: Whenever a family comes in to hand over a pet, a staff member asks without judgment if the family would prefer to keep the pet. If the answer is yes, the staff member tries to help resolve the problem, drawing on his or her network and knowledge of the system.\n
\n\n
\nWithin the first year it was clear that the program was a remarkable success. In prior years Weise’s organization had spent an average of $85 per pet it helped. The new program brought that cost down to about $60 while keeping shelter space free for other animals in need. And, Weise told me, that was just the immediate impact: “The wider effect on the community is the real point. The program helps families learn problem solving, lets them know their rights and responsibilities, and teaches the community that help is available. It also shifted the industry’s perception of the pet owners: We found that when offered assistance, a full 75% of them actually wanted to keep their pets.”\n
\n

\n\n\n\n \n

\n I like Thomas identifies questions I didn't realize I needed to ask and answer them. For example I \n appreciate he explained there's no such thing as a single root cause. Instead there are \n generally multiple causes. Each of those individually could mitigate or even solve the problem.\n

\n\n \n

\n As someone with autism I really appreciate how clearly Thomas breaks down how to implement his process. \n His anecdotes help me visualize how the processes are implemented.\n

\n\n\n \n

\n The first part of the article is meant to explain the value of their process. The second part \n explains how you can use the process and the best way to.\n

Establishing legitimacy is how you convince people to give the process a try. (Intuitively this feels like it should be somewhere else but the article put it here)
Bringing outsiders into the discussion is beneficial because often the experts don't understand the problem \nnearly as well as the people experiencing it.
Geting people’s definitions in writing tells you about subtle differences like whether people think the problem is employees not being engaged enough to innovate or the customers not paying for innovation.
Asking what’s missing gives you the information you need to reframe the question.
Considering multiple categories can tell you if you're considering enough types of causes of problems and if \nnot which types you should.
Analyzing positive exceptions can raise morale and are often an easier way to solve the problem than figuring it out from first principles.
Questioning the objective is important because often the first way to solve a problem isn't the best way of \nachieving your goal.

\n\n \n

\n Thomas explained the best way to use his process depending on the time you have.\n

\n\n

\n
The practices I outline here can be used in one of two ways, depending on how much control you have over the situation. One way is to methodically apply all seven to the problem. That can be done in about 30 minutes, and it has the benefit of familiarizing everyone with the method.
\n
The other way is suitable when you don't control the situation and have to scale the method according to how much time is available. Perhaps a team member ambushes you in the hallway and you have only five minutes to help him or her rethink a problem. If so, simply select the one or two practices that seem most appropriate.
\n
Five minutes may sound like too little time to even describe a problem, much less reframe it. But surprisingly, I have found that such short interventions are often sufficient to kick-start new thinking—and once in a while they can trigger an aha moment and radically shift your view of a problem. Proximity to your own problems can make it easy to get lost in the weeds, endlessly ruminating about why a colleague, a spouse, or your children won't listen. Sometimes all you need is someone to suggest, \"Well, could the trouble be that you are bad at listening to them?\"
\n
Of course, not all problems are that simple. Often multiple rounds of reframing—interspersed with observation, conversation, and prototyping—are necessary. And in some cases reframing won't help at all. But you won't know which problems can benefit from being reframed until you try. Once you've mastered the five-minute version, you can apply reframing to pretty much any problem you face.
\n

\n\n \n

\n I wouldn't have realized that following a checklist tends to discourage productive thinking. I'd like to \n think I would've realized I needed to test things out in the real world too.\n

\n\n \n

\n I really liked the examples and anecdotes because it helped me understand how the process could be used and how useful it is.\n

\n \n \n`;\n\n return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", AreYouSolvingtheRightProblems);\nexport default app.fetch;\n\n{\n /*

; */\n}","deleted","label","children",[],[152],{"_103":173,"_95":174,"_153":175,"_155":-5,"_156":138,"_157":158,"_159":160,"_105":176,"_100":177,"_163":164,"_165":178,"_167":22,"_168":-5,"_169":179,"_98":180},"ccd6febe-2767-11f0-85cb-569c3dd06744","Bringing_My_OCD_Online","910f80cc-1ba0-11f0-aa2b-569c3dd06744",["D",1746198722010],4,"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Context, Hono } from \"npm:hono\";\n\nexport const Bringing_My_OCD_Online = (c: Context) => {\n return c.html(\n \n \n Bringing My OCD Online\n code{all:unset}blockquote{border:1px solid var(--slate10);color:var(--slate11);padding:2px 0 2px 20px;margin:0;font-style:italic}`,\n }}\n >\n \n \n \n Home{\" \"}About{\" \"}\n Twitter Github\n

Bringing My OCD Online: Userscripts for Immersive Forum Browsing

\n\n

\n Hi, I'm Will. I'm 24, autistic, and have OCD tendencies. I'm learning to code and this is my first public\n project. I’d really appreciate your feedback and encouragement!\n

\n This project lets me solve some of my OCD problems online. There are a couple of parts of the forums that I\n visit – Space Battles, Sufficient Velocity, and Questionable Questing – that I want to remove. Specifically, I\n hate seeing indicators of how much is left in a forum thread, because I keep thinking about how much content\n is left. It stops me from immersing myself in the story. It stressed me out. Before I learned to code, I'd use\n my hand to block the total chapter count so I could read the blurb and see the word count. I would do my best\n to ignore the page navigation bar except for the next page button, but I usually ended up failing. One of the\n reasons I always read in full-screen Safari is that I didn't have to see the tab name that always had the page\n number. I learned not to hover my cursor over the window because it would tell me the page number.\n

\n This project is a series of userscripts that hide those indicators. I coded the userscripts in JavaScript, and\n I used{\" \"}\n this system. Despite the fact I didn't know what a\n userscript was until I started coding them, AI assistance allowed me to code them with minimal help from my\n brother, Stevie. Khanmigo helped me plan, write, and debug code. ChatGPT taught me the theory. Part of the\n reason I coded a lot faster with the later userscripts is I knew enough to realize when AI was talking about\n something irrelevant and redirect it. One cool moment was when I correctly predicted I didn't need to code\n different userscripts for SpaceBattles and Sufficient Velocity because Sufficient Velocity used to be part of\n SpaceBattles.\n

\n I find it relaxing not to have to worry about accidentally seeing the chapter count or the final page number.\n Maybe they’ll help one of you!\n

\n \n ,\n );\n};\n\nconst app = new Hono();\napp.get(\"/\", Bringing_My_OCD_Online);\nexport default app.fetch;",[],[174],{"_103":182,"_95":183,"_153":184,"_155":-5,"_156":138,"_157":158,"_159":160,"_105":185,"_100":177,"_163":164,"_165":186,"_167":22,"_168":-5,"_169":187,"_98":188},"ccd6f90a-2767-11f0-85cb-569c3dd06744","Debugging_Guide","8185321e-1ba0-11f0-b496-569c3dd06744",["D",1746198722010],"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting Debugging_Guide val\", new Date().toISOString());\n\nexport const Debugging_Guide = (c: any) => {\n const html = `\n\n \n Debugging Guide\n \n \n \n \n

Debugging Checklist

The classic \"print-statement-debugging\" techniques may work for simpler cases, but quickly get unmanageable. The checklist below is an extremely effective way to find and fix bugs. Debugging is a learning process - you are about to learn more about your program's behavior and how to translate your ideas into code!

\n
Observe the bug
\n
\"What makes me think there is a problem?\"
\n
\n
Create a reproducible input
\n
\"How can I reliably reproduce this problem?\" You want the smallest, simplest test case possible that reproduces the bug. The smaller it is, the quicker you will be able to debug it.
\n
\n
Narrow the search space
\n
\"\"How can I narrow down to the code that could cause this problem?\" Tracing through the whole program is not feasible. Instead, consider:\n\n\n\n\n\nUsing your intuition as a starting point. Did you change a function recently? Are there any likely culprits?\n\n\n\nPut console.log at significant point of the program so I can see what’s happening. Ideally, I can spot the problematic code is from that. If not, put console.log at places like half way through the code to get closer to the bug.\n\n\n\nConsole logs being truncated. Check if I need everything in the log and maybe split the log into multiple parts.\"\n\nIf you're in GitHub you can use binary search to more easily find the last working version. The explanation is here.
\n
\n
Analyze
\n
\"What information can I gather from this identified code?\" Now use consoles.log so I can mentally follow along. Inspect the values of variables and flow of control, and draw pictures. Try externalizing by writing out what I think should be happening, what is happening, and why it's not happening.
\n
\n
Devise and run experiments
\n
Devise and run experiments. \"How can I check my hypotheses about the issue?\" Make inferences about the root cause and run experiments to validate your hypothesis. Iterate until you identify the root cause.
\n
\n
Modify code to squash the bug
\n
\"How can I fix the issue, and confirm that the fix works?\" The fix should be validated by your experiments and passing the original failed test case. You should be able explain the series of facts, tests, and deductions which match the observed symptom to the root cause and the corrected code.
\n

\n\n

Do not change your code haphazardly. As a scientist, you should change only one variable at a time while experimenting. This ensures you can fully understand the program behavior and causes at every step.
Good style means easier debugging. Anything that helps you navigate and understand your code is key to efficient debugging.\n\n.
Thorough testing helps uncover bugs. You can never reach step 1 if you are unaware of lurking issues!

\n View Source\n

\n \n \n`;\n\n return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", Debugging_Guide);\nexport default app.fetch;",[],[183],{"_103":190,"_95":191,"_153":192,"_155":-5,"_156":138,"_157":193,"_159":160,"_105":194,"_100":195,"_163":164,"_165":196,"_167":22,"_168":-5,"_169":197,"_98":198},"4add546a-26ce-11f0-b77b-569c3dd06744","HTTP101","4fea5438-26ad-11f0-a2f7-569c3dd06744",170,["D",1746132790949],11,"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting HTTP101 val\", new Date().toISOString());\n\nexport const HTTP101 = (c: any) => {\n const html = `\n\n \n HTTP 101\n \n \n \n

What is HTTP

HTTP is the movie-rental kiosk interface—how you browse, check out, and return movies.
Client is the customer at the kiosk; Server is the machine’s inventory database.
An HTTP Request is your on-screen selection:
Method → Action button (“GET” to view details, “PUT” to update return date, “POST” to add a new rental);
Path → Movie ID (“movie/1234”);
Version → API version (“v1.1”).
Request Headers are the extra options you set (“HD quality,” “Family-friendly,” “Two-day rental”).
The HTTP Response is the screen feedback and printed receipt:
Status Code → Result (“200 Success,” “404 Not Found,” “500 Out of Service”);
Response Headers → Receipt details (“Due date,” “Price”);
Response Body → Movie info and checkout confirmation.

\n\n\n

\n \n\n\n

Credit

I copied image 11. HTTP Headers \n& HTTP Status Codes which was written by Prabath Shalitha

\n\n \n \n

\n \n

\n\n \n \n`;\n\n return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", HTTP101);\nexport default app.fetch;",[],[191],{"_103":200,"_95":201,"_153":202,"_155":-5,"_156":138,"_157":158,"_159":160,"_105":203,"_100":204,"_163":164,"_165":205,"_167":22,"_168":-5,"_169":206,"_98":207},"ccd6f3a6-2767-11f0-85cb-569c3dd06744","ImOKTheBullIsDead","f7536daa-2116-11f0-96e0-569c3dd06744",["D",1746198722010],15,"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting ImOKTheBullIsDead val\", new Date().toISOString());\n\nexport const ImOKTheBullIsDead = (c: any) => {\n const html = `\n\n \n I’m OK; The Bull Is Dead\n \n \n \n \n

\n I’m OK; The Bull Is Dead. \n Gopal K. Kapur is the founder and president of the Center for Project Management. I liked his article\n because I struggle with conveying important information in an understandable way and I found his four step\n process enlightiening.\n

\n\n

\n \"I’m OK; The Bull Is Dead\"\n

\n\n

\n The quote is a great example of how to convey the core pieces of information in just a few words. Later\n the article explains the whole situation. I likely would've spent a few minutes trying to explain\n what happened. The article demonstrates how to do that in a few paragraphs in a more engaging way.\n

\n\n \n

\n Gopal explains his fourth step process to give concise interesting status reports.\n

\n\n

\n
1. Punch line: The facts; no adjectives, adverbs or modifiers. \"Milestone 4 wasn't hit on time, and we didn't start Task 8 as planned.\" Or, \"Received charter approval as planned.\"
\n
2. Current status: How the punch-line statement affects the project. \"Because of the missed milestone, the critical path has been delayed five days.\"
\n
3. Next steps: The solution, if any. \"I will be able to make up three days during the next two weeks but will still be behind by two days.\"
\n
4. Explanation: The reason behind the punch line. \"Two of the five days' delay is due to late discovery of a hardware interface problem, and the remaining three days' delay is due to being called to help the customer support staff for a production problem.\"
\n

\n \n

\n In journalism this is known as the inverted pyramid style. It begins with the conclusion, follows with the \n most important facts, and ends with the details. Gopal warns against using the academic style for status\n reports. The academic style is when you start with the problem, explain the background, discuss \n influencing factors, and finish with the conclusion. He says that in academic style by the time you get to \n the conclusion, most people have difficulty giving it the full attention, even though it's the most \n important part.\n

\n\n

\n \n

\n \n \n`;\n\n return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", ImOKTheBullIsDead);\nexport default app.fetch;\n\n{\n /*

; */\n}",[],[201],{"_103":209,"_95":210,"_153":211,"_155":-5,"_156":138,"_157":158,"_159":160,"_105":212,"_100":177,"_163":164,"_165":213,"_167":22,"_168":-5,"_169":214,"_98":215},"ccd6d77c-2767-11f0-85cb-569c3dd06744","Time_Blindness_Loud_Calendar_via_iOS_shortcuts","6f2aa7d4-1ba0-11f0-a43f-569c3dd06744",["D",1746198722010],"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Context, Hono } from \"npm:hono\";\n\n// Define the route handler function\nexport const Time_Blindness_Loud_Calendar_via_iOS_shortcuts = (c: Context) => {\n console.log(\"Route accessed: Time_Blindness_Loud_Calendar_via_iOS_shortcuts\");\n const htmlContent = `\n \n \n \n Time Blindness Loud Calendar via iOS Shortcuts\n \n \n \n \n

Time Blindness Loud Calendar via iOS Shortcuts

I have time blindness, a condition which makes it hard to notice the passing of time. I couldn't find a calendar app that had alerts loud enough that I'd notice.

The iOS Clock app is loud enough, though. So I created an iOS shortcut to schedule Clock alarms based on events in my calendar: Loud Calendar Alarm.

How it works

The first thing it does is delete the alarms it created from prior day by the label “Calendar Alarm”. Then it pulls all my calendar events for the next day, subtracts 15 minutes from the time, and creates an alarm. The shortcut is scheduled to run every night at midnight.

$\"Screen$

My shortcut is based on this one.

Installation Guide

1. Add the shortcut

On your iPhone, click Loud Calendar Alarms
Click the Open in the pop-up.
Click Add Shortcut.

2. Give permissions to the shortcut

Click the name of the shortcut.
Click Delete Always in the pop-up asking for permission.
Click Allow Always in the pop-up asking for permission to display notifications.
Click Always Allow in the pop-up asking for permission to share calendar events.

3. Schedule the shortcut

Click Automation at the bottom of the screen.
Click the +
Click Time of Day
Click the time under the blue check.
Change the time to when you want it to run (ie midnight)
Click Run Immediately
Click Notify When Run
Click Shortcut that sets alarms before calendar events, and delete them after use
The following day, confirm that you get a notification that the alarms were deleted and alarms were sent because sometimes you need to manually run the shortcut to re-give permission or even re-download the shortcut. Then it should work normally.
Enjoy!

\n \n `;\n return c.html(htmlContent);\n};\n\nconst app = new Hono();\napp.get(\"/\", Time_Blindness_Loud_Calendar_via_iOS_shortcuts);\nexport default app.fetch;",[],[210],{"_103":217,"_95":218,"_153":219,"_155":-5,"_156":138,"_157":220,"_159":160,"_105":221,"_100":222,"_163":164,"_165":223,"_167":22,"_168":-5,"_169":224,"_98":225},"c192009a-76e4-11f0-bb7e-0224a6c84d84","about","c3a7292c-1ba0-11f0-88f8-569c3dd06744",232,["D",1754938532053],46,"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting about val\", new Date().toISOString());\nexport const about = (c: any) => {\n const html = `\n\n \n about\n \n \n \n

Will Krouse

\n \n

\n Hi I'm Will, a 26-year-old autistic person in Florida. I love reading. I enjoy playing board games,\n tennis, and pickleball.\n

\n\n

\n I'm learning to code. My favorite part are the meta-skills. For example, the debugging mindset is always\n useful for fixing problems.\n

\n\n

\n I find the complexity of current events and politics really interesting. I enjoy articles that significantly\n change my understanding. I really like\n Tangle\n because it offers perspectives from all sides. I dislike when people assume the worst of their opponents and\n when I can't tell who's right because no one addresses the best arguments from their opponents.\n

\n I'm on the autism spectrum so I sometimes misunderstand people's tones and vibes or send the wrong ones.\n Your patience and feedback are appreciated!\n

\n\n

\n I built\n \n this site\n \n on Val Town.\n

\n\n

Credit

\n I copied the formatting from\n Valjean Clark\n and was inspired by his design.\n

\n \n `;\n return c.html(html);\n};\nconst app = new Hono();\n\napp.get(\"/\", about);\nexport default app.fetch;",[],[218],{"_103":227,"_95":228,"_153":229,"_155":-5,"_156":138,"_157":230,"_159":160,"_105":231,"_100":232,"_163":164,"_165":233,"_167":22,"_168":-5,"_169":234,"_98":235},"be7620b4-3e2f-11f0-b188-76b3cceeab13","asynchrousCode.tsx","e500ce90-3c05-11f0-84c6-9e149126039e",208,["D",1748703522818],5,"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting asynchrousCode file\", new Date().toISOString());\n\nexport const asynchrousCode = (c: any) => {\n const html = `\n\n \n Explaining promises, async, await, and the differences between them\n \n \n \n

\n Asynchronous code is code that has to wait to get responses from external sources. For example if the code\n makes a request for data via an API, the asynchronous part is when you wait for the response. A promise is an object representing the eventual Mission or failure of the asynchronous operation.\n

\n\n\n

Callback hell

\n It's common to need to do multiple asynchronous operations that need the result of the previous operation. That would lead to callback hell because of how hard that would be to read. I included an example of callback hell below.\n

\n\n

\ndoSomething(function (result) {\n  doSomethingElse(result, function (newResult) {\n    doThirdThing(newResult, function (finalResult) {\n      console.log(\\`Got the final result: \\${finalResult}\\`);\n    }, failureCallback);\n  }, failureCallback);\n}, failureCallback);\n\n          \n          I included examples of how you could do the exact same thing with promises below.\n          
\n\n          \n          const promise = doSomething();\n          const promise2 = promise.then(successCallback, failureCallback);\n          const promise3 = promise.then(successCallback, failureCallback);\n\n          \n          async function doSomething(function (result) {\n          const result = await doSomething(result);\n          const newResult = await doSomething(result);\n          const finalResult = await doSomething(newResult);\n          }\n\n\n          \n          Regarding the .then example, .then does two things. The first thing is that it handles the resolution of the asynchronous operation. The second thing is that depending on whether or not it succeeds or fails it causes a different function. \n          
\n\n Credit
\n\n    The majority of my code examples are from mdn.\n   
\n    \n`;\n\n  return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", HTTP101);\nexport default app.fetch;",[],[228],{"_103":237,"_95":238,"_153":239,"_155":-5,"_156":138,"_157":240,"_159":160,"_105":241,"_100":177,"_163":164,"_165":242,"_167":22,"_168":-5,"_169":243,"_98":244},"9c8620fa-22c1-11f0-9b08-569c3dd06744","blogCommentaryOutline","715703de-22b9-11f0-a112-569c3dd06744",134,["D",1745687539845]," link to article with a hyper text of the title and state the problem the article solves solves
\n        \n        Are You Solving the Right Problems?. \n        via My \n        
\n\n         give a high level explanation of why the article is different than the other one that tried to solve this problem. 
\n        \n        \n        
\n\n         give a low-level explanation of why the article is different then follow up with a quote that expands follow up with a quote that expands it 
\n        \n        \n        
\n\n        \n        \n\n        
\n        
\n\n         State small thing they do that you like for example introducing a new term 
\n        \n        \n        
\n\n         explain what is the thing that is the highlight of the article for you 
\n        \n        \n        
\n\n\n         explain the focus of the article and a short explanation of how it works 
\n        \n        \n        
\n\n\n         answer questions like when should you upgrade from a low-level cheap use to something more expensive that is more effective 
\n        \n        \n        
\n\n\n         include something you might not have thought of like needing to  
\n        \n        \n        
\n\n\n\n         include a warning about things people may not have participated like for example if possible you should try to avoid letting LLMs plan out their workflow by themselves 
\n        \n        \n        
\n\n\n         include a cool thing it has 
\n        \n        \n        
",[],[238],{"_103":246,"_95":247,"_153":248,"_155":-5,"_156":138,"_157":137,"_159":160,"_105":249,"_100":162,"_163":164,"_165":250,"_167":22,"_168":-5,"_169":251,"_98":252},"ea6b9a08-9ee4-11f0-9826-0224a6c84d84","homepage","b2324578-1ba0-11f0-a44b-569c3dd06744",["D",1759336647099],"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Context, Hono } from \"npm:hono\";\nimport { about } from \"./about\";\nimport { AreYouSolvingtheRightProblems } from \"./AreYouSolvingtheRightProblems\";\nimport { Bringing_My_OCD_Online } from \"./Bringing_My_OCD_Online\";\nimport { Debugging_Guide } from \"./Debugging_Guide\";\nimport { HTTP101 } from \"./HTTP101\";\nimport { ImOKTheBullIsDead } from \"./ImOKTheBullIsDead\";\nimport { statusGuide } from \"./statusGuide\";\nimport { Time_Blindness_Loud_Calendar_via_iOS_shortcuts } from \"./Time_Blindness_Loud_Calendar_via_iOS_shortcuts\";\n// import { lostMotivationChecklist } from \"./lostMotivationChecklist\";\n\nexport const homepage = (c: Context) => {\n  return c.html(\n    (\n      \n        \n          Blog\n          code{all:unset}blockquote{border:1px solid var(--slate10);color:var(--slate11);padding:2px 0 2px 20px;margin:0;font-style:italic}a[data-astro-cid-eimmu3lg]{display:inline-block;text-decoration:none}a[data-astro-cid-eimmu3lg].active{font-weight:600;text-decoration:underline}header[data-astro-cid-3ef6ksr2]{margin:0 0 2em}h2[data-astro-cid-3ef6ksr2]{margin:.5em 0}`,\n            }}\n          >\n          \n        \n        \n          Home{\"  \"}Twitter{\" \"}\n          Github{\"  \"}About\n          \n            Blog
\n            \n\n              {/* \n                10/1/2025 -{\" \"}\n                \n                  Lost Motivation Checklist\n                \n              
 */}\n              \n                5/1/2025 -{\" \"}\n                \n                  HTTP 101 guide\n                \n              
\n              \n                4/26/2025 -{\" \"}\n                \n                  Are You Solving the Right Problems?\n                \n              
\n              \n                4/18/2025 -{\" \"}\n                \n                  I’m OK; The Bull Is Dead\n                \n              
\n              \n                4/21/2025 -{\" \"}\n                \n                  Status Guide\n                \n              
\n              \n                11/19/2024 -{\" \"}\n                \n                  ChatGPT Text Definition Update\n                \n              
\n              \n                10/28/2024 -{\" \"}\n                \n                  Val Town Version Logger\n                \n              
\n              {\n                \n                  8/26/2024 -{\" \"}\n                  \n                    Debugging Guide\n                  \n                
\n              }\n              \n                8/20/2024 -{\" \"}\n                \n                  ChatGPT Text Definition\n                \n              
\n              \n                8/19/2024 -{\" \"}\n                \n                  Jumpchain Infosite\n                \n              
\n              \n                7/7/2024 -{\" \"}\n                \n                  Calculating Work Time\n                \n              
\n              \n                6/18/2024 -{\" \"}\n                \n                  Clarifying forum text and phrases\n                \n              
\n              \n                5/31/2024 -{\" \"}\n                \n                  Time Blindness Loud Calendar via iOS shortcuts\n                \n              
\n              \n                3/6/2024 -{\" \"}\n                \n                  Bringing My OCD Online: Userscripts for Immersive Forum Browsing\n                \n              
\n            
\n          
\n        \n      \n    ),\n  );\n};\n\nconst app = new Hono();\napp.get(\"/\", homepage);\napp.get(\"/Bringing_My_OCD_Online\", Bringing_My_OCD_Online);\napp.get(\"/Time_Blindness_Loud_Calendar_via_iOS_shortcuts\", Time_Blindness_Loud_Calendar_via_iOS_shortcuts);\napp.get(\"/Debugging_Guide\", Debugging_Guide);\napp.get(\"/statusGuide\", statusGuide);\napp.get(\"/HTTP101\", HTTP101);\napp.get(\"/about\", about);\napp.get(\"/AreYouSolvingtheRightProblems\", AreYouSolvingtheRightProblems);\napp.get(\"/ImOKTheBullIsDead\", ImOKTheBullIsDead);\n// app.get(\"/lostMotivationChecklist\", lostMotivationChecklist);\n\nexport default app.fetch;",[],[247],{"_103":254,"_95":99,"_153":255,"_155":-5,"_156":138,"_157":256,"_159":160,"_105":257,"_100":258,"_163":164,"_165":259,"_167":22,"_168":-5,"_169":260,"_98":261},"d09f4e62-9ee4-11f0-9acf-0224a6c84d84","fcfe3270-97d2-11f0-af8d-0224a6c84d84",243,["D",1759336603815],7,"// /** @jsxImportSource https://esm.sh/hono@latest/jsx **/\n// import { Hono } from \"https://esm.sh/hono@3.10.2\";\n// // last stable version is 61\n// console.log(\"[Init] Starting lostMotivationChecklist val\", new Date().toISOString());\n\n// export const lostMotivationChecklist = (c: any) => {\n//   const html = `\n// \n//     \n//         Lost Motivation Checklist\n//         \n//     \n//     \n//         \n//             Home \n//             About \n//             Twitter \n//             Github\n//         
\n\n      \n//         \n//         My challenge is that when I feel intense emotions, I react instead of think. Therefore, I'm making a checklist to \n//         remind myself of what I should do.\n//         
\n\n     \n//         \n//           1. Identify why I am having difficulty working. For example, is it because I'm feeling overwhelmed, anxiety, \n//           habit, or something else.\n          \n//           2a. If I'm feeling overwhelmed, try breaking the task down into small pieces and see how I feel.\n//           2b. If breaking the task into small pieces doesn't help, try setting a timer for a small period of time like \n//           10 or 30 minutes then see how much progress I made. Sometimes I think things will take a lot longer than they will.\n//           2c. If the project is just too big for me, I'll see how much I can cut while accomplishing the core goal. Later, \n//           I can add on as needed. That way I can publish something even if it's a lot less than planned.\n//           2d. \n\n\n\n//         
\n\n     \n//         \n        \n//         
\n\n        \n//     \n// `;\n\n//   return c.html(html);\n// };\n\n// const app = new Hono();\n// app.get(\"/\", lostMotivationChecklist);\n// export default app.fetch;",[],[99],{"_103":263,"_95":264,"_153":265,"_155":-5,"_156":138,"_157":266,"_159":160,"_105":267,"_100":268,"_163":269,"_165":270,"_167":22,"_168":-5,"_169":271,"_98":272},"dd7534b2-9ee4-11f0-b6f8-0224a6c84d84","personalWebsite","052de840-1ba1-11f0-87b0-569c3dd06744",244,["D",1759336625358],31,"http","/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"npm:hono@3\";\nimport { about } from \"./about\";\nimport { AreYouSolvingtheRightProblems } from \"./AreYouSolvingtheRightProblems\";\nimport { Bringing_My_OCD_Online } from \"./Bringing_My_OCD_Online\";\nimport { Debugging_Guide } from \"./Debugging_Guide\";\n// import { lostMotivationChecklist } from \"./lostMotivationChecklist\";\nimport { homepage } from \"./homepage\";\nimport { HTTP101 } from \"./HTTP101\";\nimport { ImOKTheBullIsDead } from \"./ImOKTheBullIsDead\";\nimport { statusGuide } from \"./statusGuide\";\nimport { Time_Blindness_Loud_Calendar_via_iOS_shortcuts } from \"./Time_Blindness_Loud_Calendar_via_iOS_shortcuts\";\nconst app = new Hono();\n\n// Add a middleware to include the viewport meta tag and additional CSS in all HTML responses\napp.use(\"*\", async (c, next) => {\n  await next();\n  if (c.res.headers.get(\"Content-Type\")?.includes(\"text/html\")) {\n    const html = await c.res.text();\n    const updatedHtml = html.replace(\n      \"\",\n      `\n      \n      \n    `,\n    );\n    c.res = new Response(updatedHtml, c.res);\n  }\n});\n\napp.get(\"/\", homepage);\napp.get(\"/Time_Blindness_Loud_Calendar_via_iOS_shortcuts\", Time_Blindness_Loud_Calendar_via_iOS_shortcuts);\n// app.get(\"/lostMotivationChecklist\", lostMotivationChecklist);\napp.get(\"/Bringing_My_OCD_Online\", Bringing_My_OCD_Online);\napp.get(\"/Debugging_Guide\", Debugging_Guide);\napp.get(\"/statusGuide\", statusGuide);\napp.get(\"/HTTP101\", HTTP101);\napp.get(\"/about\", about);\napp.get(\"/AreYouSolvingtheRightProblems\", AreYouSolvingtheRightProblems);\napp.get(\"/ImOKTheBullIsDead\", ImOKTheBullIsDead);\n\nexport default app.fetch;",[],[264],{"_103":274,"_95":275,"_153":276,"_155":-5,"_156":138,"_157":277,"_159":160,"_105":278,"_100":279,"_163":164,"_165":280,"_167":22,"_168":-5,"_169":281,"_98":282},"e6517fd4-55c2-11f0-8a61-f69ea79377d9","statusGuide","1b34f7fa-1c3c-11f0-84a8-569c3dd06744",221,["D",1751295602451],57,"/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting statusGuide val\", new Date().toISOString());\n\nexport const statusGuide = (c: any) => {\n  const html = `\n\n    \n        Status Guide\n        \n    \n    \n        \n            Home \n            About \n            Twitter \n            Github\n        
\n        What is a status report
\n        The point of a status report is to make sure you work on the right things. From personal experience \n        that's a lot harder than it seems. It's really easy to get into a rabbit hole without noticing. Also\n        I've wasted a lot of time because I worked on the intuitive right direction until my teacher\n        gave me feedback. At first I often needed to at the minimum recycle work if not restart from scratch\n        because my intuition was that wrong. The model prevents that problem because it requires you to find an \n        exising example of the right direction you'll take heavy inspiration from. \n\n        \n        
Sample good sample report
\n• Project Name: Learn HTTP 101\n
• Motivation: \"I want a well paying job indoors that doesn't require physical activity or prioritize social skills.\"\n
• Goal:  \"Learn HTTP 101 by writing guides to it in Val Town I would've liked to have when learning.\"\n
• Model: Your first form.\n
• Status now: I completed half of the blog post\n
• Status last week: I completed seven out of the ten parts of the outline and thoroughly proofread each part.\n
• Progress since last week: I finished the outline. I learned how to teach pratical code with active learning by reading link.\n
• Activity that didn't move status forward: I tried to get advice on writing by searching for blog post guides. I didn't find anything applicable when I googled how to write a blog post, guide to blog post, and blog post writing 101.\n
• Next Steps: My plan is to finish my first draft and ask for feedback.\n
• Open Questions: Could you please check my first draft? I'm not worried about minor problems since it's just a first draft. I'm concerned I'm being unclear or rambling a lot again. What do you think?
\n\n        How to write a quality status report?
\n        I'll walk you through what you need to do to write a great status report step-by-step. 
\n\n         Project Name
\n          You want a name that is  very clear and reasonably short. Otherwise you'll find yourself working\n          on things that are generally related and not what you should be working on.
\nExamples:
\n\n❌ Bad: \"Learn programming.\"
\n\nI don't know what type of programming the project covers.
\nThere is no way to know when you finish the project because you could literally spend decades studying\nprogramming and there would still be a lot left to learn.
\n\n
\n✅ Good:  \"Learn HTTP 101\"
\n\nHTTP 101 is a small enough knowledge base that it's reasonable to master completely.
\nHTTP 101 is a specific and concrete goal so it's easy to measure my progress.
\n\nMotivation
\nMotivation is the reason you're pursuing the goal. Often I find what's needed to complete a \nproject is very different than what I expected. I need to check my motivation then to make sure\nI'm still working on the most effective way to achieve it.
\n\n Examples:
\n\n  ❌ Bad: \"I want to have a good career skill.\"
\n\n The problem is that you're not answering the question why is programming the right career skill.
\n          \n
   \n ✅ Good: \"I want a well paying job indoors that doesn't require physical activity or prioritize social skills.\"
\n\nThat's a good motivation because it's describing a very specific set of the desires.
\n          \n  ❌ Bad: \"I want to make my parents happy.\"
\n          \n The problem is that you didn't specified how it'll make your parents happy. How do you know that's the most effective way to make them happy?
\n          \n
   \n ✅ Good: I want to improve my relationship with my parents by getting rid of long lasting friction by showing that I have a concrete plan to get marketable skills.
\n\n  This is a better motivation for two reasons. The first is that improving a relationship is more specific \nthan making someone happy. The second is that you specify how you're improving the relationship.
\n          Goal
\n          The goal is how you achieve your motivation.
\n\n          Examples:\n\n        
  ❌ Bad: \"Learn HTTP 101\"\n\n       
   The problem with the goal is that it doesn't say how you're going to learn HTTP.\n\n          
   
 ✅ Good: \"Learn HTTP 101 by writing guides to it in Val Town I would've liked to have when learning.\"\n\n         
  This is a good goal because I can clearly see if I'm learning because if I can write a guide to a \n         concept I learned it.\n         
 Additionally I can measure my progress by seeing how much of HTTP 101 I covered.\n          \n\n         
  ❌ Bad: \"I want a programming job.\"\n\n         
  The problem with the goal is that a job in a startup is very different than an established tech \n         company. Similarly there's a big difference between working in a tech company and working in a \n         company that is technologically behind.\n\n          \n          
   
 ✅ Good: \"I want a job at a low tech company where I can modernize the company.\"\n\n          
 This is a good goal because I'm aiming for a specific type of job and can predict what the \n          relevant skills I need to learn are.\n  \n          
Model
\n          The point of a model is to find a pre-existing example of something similar to what you're trying\n          to achieve so you focus your effort on the right things.
\n\n           Examples:\n           ❌ Bad: \"How the Web Works, HTTP Request/Response Cycle.\"\n\n         
  The problem with using that as a model is that it's only a good model for teaching theory so I \n         had to guess what I should do for the active learning. It turned out that I was completely wrong on how to \n         teach active learning.\n\n\n          \n          
   
 ✅ Good: \"Your first form.\"\n\n         
  This is a good model because it teaches theory, practical knowledge, and uses active learning.\n  \n          
Status now
\n          The point of the Status now is to make sure you know how close you are to your goal.
\n\n           Examples:\n         
  ❌ Bad: \"Finished the outline and completed half of the blog post.\"\n\n        
   The problem is that finishing the outline goes in the progress section not in the Status now. After all\n          the Status now is meant to show how close you are to the goal and the fact you started the blog post\n          obviously means you finished the outline.\n\n          \n          
   
 ✅ Good: \"I completed half of the blog post.\"\n\n         
  This is a good Status now because it's only focused on the task you're working on at the moment.\n        \n\n  \n  \n          
Status last week
\n          The point of the status after the last check in is to make it easy to compare to the Status now so \n          you can easily tell the progress you're making.
\n\n           Examples:\n         
  ❌ Bad: \"Wrote part of an outline.\"\n\n          
  The problem is that it's unclear how much of the outline was written. \n          \n          
   
 ✅ Good: \"I completed seven out of the ten parts of the outline and thoroughly proofread each part.\"\n\n         
  This is a good Status last week because you know exactly how much of the outline is \n         completed, how much is left, and that the three parts are polished.\n\n          
Progress since last week
\n          Progress since the last check in is covering the change and/or delta since the last check-in.
\n\n           Examples:\n         
  ❌ Bad: \"I read five articles on outline writing. The links are …. I also finished the outline.\n\n         
  The problem is that I don't know why any of those articles are relevant.\n          \n          
   
 ✅ Good: \"I finished the outline.\"\n\n        
   This is a good Progress since last week because it's listing a concrete accomplishment that \n        moved you forward.\n\n          
   
 ✅ Good: \"I learned how to teach pratical code with active learning by reading link.\"\n\n         
  This is a good Progress since last week because it's saying what you learned through reading \n         the article and giving the link to the article.\n\n          
Activity that didn’t move status forward
\n          Activity that didn’t move status forward is where you put things you tried that didn't move you \n          closer to the goal. The point of recording it is that otherwise you could work very hard on\n          trying plausible paths forward but look like you did nothing because none of those plausible \n          paths worked. Additionally if you're asking for help, it's good form to say what the dead ends are.\n\n         
  Examples:\n         
  ❌ Bad: \"I spent a half hour looking for a model on how to write HTTP guides.\n\n        
   The problem is that it's specific in the wrong place. The length of time spent looking doesn't help\n          anyone find a good model.\n \n          
   
 ✅ Good: \"I didn't find a model on how to write HTTP guides when I tried searching HTTP guide, \n          HTTP lesson, and HTTP course on both Twitter and Hackernews.\"\n\n        
 This is a good activity that didn’t move status forward because it's specifying the search terms that \n          didn't work and where you searched.\n\n         
  ❌ Bad: \"I read five HTTP guides. The links are ….\n\n         
  The problem is that I don't know why reading those articles didn't move me closer to accomplishing the goal.\n \n          
   
 ✅ Good: \"I read five  HTTP guides. They weren't helpful because they were focused \n          on programming environments that use npm and that's too different from my programming environment of Val\n          Town. The links are ….\n\n         
  This is a good activity that didn’t move status forward because I specified why they weren't helpful \n         and what needed to change to make sure they are helpful.\n\n  \n          
Next Steps
\n           The point of the next steps are to make a plan on what to do next. That's valuable because I found \n          deciding what I need to work on beforehand can be the difference between smoothly starting work and \n          struggling to.
\n\n          Examples:
\n           ❌ Bad: \"My plan is to finish the blog post.
\n\n           The problem is that it's unclear what is needed to finish. A first draft needs a lot less polishing than a \n          final one. I also don't know if the reason there's no plan to ask for feedback is because there's no need\n          or if it's considered an obvious thing to do.
\n \n          
    ✅ Good: \"My plan is to finish my first draft and ask for feedback.
\n\n           This is a good next step because I'm specifying the amount of polishing and plan to ask for feedback.\n\n          
Open Questions
\n          The point of the open questions is to ask for help from a teacher, boss, or someone else.
\n\n          Examples:\n           ❌ Bad: \"Could you please check my first draft?\n\n        
   The problem is that I'm not being clear about why I'm asking for help. I'm asking the other person\n          to guess what the problem is. While the other person is better than me at the task, it's extra work\n          for them to guess what the problem is. Additionally you might not notice a problem that they do that is so obvious and\n          problematic they only advise you on one problem instead of all of them.\n\n          
   
 ✅ Good: \"Could you please check my first draft? I'm not worried about minor problems since it's just \n          a first draft. I'm concerned I'm being unclear or rambling a lot again. What do you think?\n\n        
   This is a good open question because I tell them what they shouldn't worry about and what are the two \n          problems I'm concerned about.\n\n        
Template to copy
\n\n  Project Name: 
\n  Motivation: 
\n  Goal: 
\n  Model: 
\n  Status now: 
\n  Status last week: 
\n  Progress since last week: 
\n  Activity that didn't move status forward: 
\n  Next Steps: 
\n  Open Questions: 
\n
\n        \n    \n`;\n\n  return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", statusGuide);\nexport default app.fetch;",[],[275],{"_103":284,"_95":285,"_153":286,"_155":-5,"_156":138,"_157":287,"_159":160,"_105":288,"_100":289,"_163":269,"_165":290,"_167":22,"_168":-5,"_169":291,"_98":292},"3c2d232e-1b9c-11f0-9155-569c3dd06744","testWbsite","38d7fa96-1b9c-11f0-bb49-569c3dd06744",2,["D",1744901828680],1,"/** @jsxImportSource https://esm.sh/react */\nimport { renderToString } from \"npm:react-dom/server\";\n\nexport const testWebsite = (request: Request) => {\n  // convert to Response\n  return new Response(\n    renderToString(\n      \n        \n          Page Title\n        \n        \n          H e{\" \"}\n          l l{\" \"}\n          o\n        \n      ,\n    ),\n    {\n      headers: { \"Content-Type\": \"text/html\" },\n    },\n  );\n};",[],[285],"files",[150,172,181,189,199,208,216,226,236,245,253,262,273,283],"counts",{"_297":32,"_298":289,"_299":289,"_300":301},"pulls","branches","forks","envVars",{"_302":32,"_303":32},"count","emptyCount","contents",[],"file",{"_103":254,"_95":99,"_153":255,"_155":-5,"_156":138,"_157":256,"_159":160,"_105":308,"_100":258,"_163":164,"_165":259,"_167":22,"_168":-5,"_98":309},["D",1759336603815],[99],"upstreamProject","upstreamBranch","emptyEnvVars","isNew","flags",[],"routes/_app.x.$handle.$name.branch.$branch.history_.$",{"_93":94,"_95":96,"_97":43,"_98":99,"_101":318,"_306":323,"_326":327,"_366":367,"_377":-7,"_378":32,"_379":22},{"_103":104,"_95":96,"_105":319,"_107":-5,"_108":22,"_109":110,"_111":-5,"_112":-5,"_14":113,"_114":-5,"_115":22,"_116":117,"_118":32,"_16":119,"_120":121,"_122":121,"_123":124,"_125":124,"_126":124,"_127":121,"_128":121,"_23":320,"_132":321,"_135":322,"_147":22},["D",1744900563378],{"_93":94,"_130":131},{"_93":94,"_134":131},{"_100":137,"_95":43,"_103":138,"_139":104,"_140":-5,"_141":-5,"_142":-5,"_143":-5,"_144":-5,"_145":96,"_146":94},{"_103":254,"_95":99,"_153":255,"_155":-5,"_156":138,"_157":256,"_159":160,"_105":324,"_100":258,"_163":164,"_165":259,"_167":22,"_168":-5,"_98":325},["D",1759336603815],[99],"history",[328,330,336,341,346,352,357,361],{"_103":254,"_156":138,"_153":255,"_95":99,"_165":259,"_163":164,"_100":258,"_155":-5,"_105":329,"_157":256,"_168":-5},["D",1759336603815],{"_103":331,"_156":138,"_153":255,"_95":99,"_165":332,"_163":164,"_100":333,"_155":-5,"_105":334,"_157":335,"_168":-5},"828893dc-9ee4-11f0-ac5c-0224a6c84d84","/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting lostMotivationChecklist val\", new Date().toISOString());\n\nexport const lostMotivationChecklist = (c: any) => {\n  const html = `\n\n    \n        Lost Motivation Checklist\n        \n    \n    \n        \n            Home \n            About \n            Twitter \n            Github\n        
\n\n      \n        \n        My challenge is that when I feel intense emotions, I react instead of think. Therefore, I'm making a checklist to \n        remind myself of what I should do.\n        
\n\n     \n        \n          1. Identify why I am having difficulty working. For example, is it because I'm feeling overwhelmed, anxiety, \n          habit, or something else.\n          \n          2a. If I'm feeling overwhelmed, try breaking the task down into small pieces and see how I feel.\n          2b. If breaking the task into small pieces doesn't help, try setting a timer for a small period of time like \n          10 or 30 minutes then see how much progress I made. Sometimes I think things will take a lot longer than they will.\n          2c. If the project is just too big for me, I'll see how much I can cut while accomplishing the core goal. Later, \n          I can add on as needed. That way I can publish something even if it's a lot less than planned.\n          2d. \n\n\n\n        
\n\n     \n        \n        \n        
\n\n        \n    \n`;\n\n  return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", lostMotivationChecklist);\nexport default app.fetch;",6,["D",1759336472809],242,{"_103":337,"_156":138,"_153":255,"_95":99,"_165":338,"_163":164,"_100":232,"_155":-5,"_105":339,"_157":340,"_168":-5},"9d8e8918-9ee2-11f0-bbc1-0224a6c84d84","/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting lostMotivationChecklist val\", new Date().toISOString());\n\nexport const lostMotivationChecklist = (c: any) => {\n  const html = `\n\n    \n        Lost Motivation Checklist\n        \n    \n    \n        \n            Home \n            About \n            Twitter \n            Github\n        
\n\n      \n        \n        My challenge is that when I feel intense emotions, I react instead of think. Therefore, I'm making a checklist to \n        remind myself of what I should do.\n        
\n\n     \n        \n          1. Identify why I am having difficulty working. For example, is it because I'm feeling overwhelmed, anxiety, \n          habit, or something else.\n          \n          2a. If I'm feeling overwhelmed, try breaking the task down into small pieces and see how I feel.\n          2b. If breaking the task into small pieces doesn't help, try setting a timer for a small period of time like \n          10 or 30 minutes then see how much progress I made. Sometimes I think things will take a lot longer than they will.\n          2c. If the project is just too big for me, I'll see how much I can cut while accomplishing the core goal. Later, \n          I can add on as needed. That way I can publish something even if it's a lot less than planned.\n          2d. \n\n\n\n        
\n\n     \n        \n        \n        
\n\n        \n    \n`;\n\n  return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", lostMotivationChecklist);\nexport default app.fetch;\n\n{\n  /* \n
; */\n}",["D",1759335659152],241,{"_103":342,"_156":138,"_153":255,"_95":99,"_165":343,"_163":164,"_100":177,"_155":-5,"_105":344,"_157":345,"_168":-5},"f389547a-9ee1-11f0-8d00-0224a6c84d84","/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting lostMotivationChecklist val\", new Date().toISOString());\n\nexport const lostMotivationChecklist = (c: any) => {\n  const html = `\n\n    \n        Lost Motivation Checklist\n        \n    \n    \n        \n            Home \n            About \n            Twitter \n            Github\n        
\n\n      \n        \n        My challenge is that when I feel intense emotions, I react instead of think. Therefore, I'm making a checklist to \n        remind myself of what I should do.\n        
\n\n     \n        \n          1. Identify why I am having difficulty working. For example, is it because I'm feeling overwhelmed, anxiety, \n          habit, or something else.\n          \n          2a. If I'm feeling overwhelmed, try breaking the task down into small pieces and see how I feel.\n          2b. If breaking the task into small pieces doesn't help, try setting a timer for a small period of time like \n          10 or 30 minutes then see how much progress I made. Sometimes I think things will take a lot longer than they will.\n          2c. If the project is just too big for me, I'll see how much I can cut while accomplishing the core goal. Later, \n          I can add on as needed. That way I can publish something even if it's a lot less than planned.\n          2d. \n\n\n\n        
\n\n     \n        \n        \n        
\n\n        \n    \n`;\n\n  return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", AreYouSolvingtheRightProblems);\nexport default app.fetch;\n\n{\n  /* \n
; */\n}",["D",1759335373905],237,{"_103":347,"_156":138,"_153":255,"_95":99,"_165":348,"_163":164,"_100":349,"_155":-5,"_105":350,"_157":351,"_168":-5},"b2793f5c-9ed9-11f0-b645-0224a6c84d84","/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting lostMotivationChecklist val\", new Date().toISOString());\n\nexport const lostMotivationChecklist = (c: any) => {\n  const html = `\n\n    \n        Lost Motivation Checklist\n        \n    \n    \n        \n            Home \n            About \n            Twitter \n            Github\n        
\n\n      \n        \n        My challenge is that when I feel intense emotions, I react instead of think. Therefore, I'm making a checklist to remind myself of what I should do.\n        
\n\n     \n        \nStevie pointed out that if I'm concerned about possible consequences, changing the scope can mitigate or even remove the problem. For example, if I only apply to one position at Apple, there's no pattern they can see for a red flag of me supplying for practice. Stevie also said it's way too cautious to worry about an automated system to detect anomalies. I could send him an email to apologize. I could choose a different company to apply to in the future.\n\nStevie said it's hard to be motivated when you're living with your parents and instead of going to an office for everyone else is working. Stevie says I didn't think about like I'm forcing myself. I should be doing it for five minutes with the mind of all check in and see how I feel. Think of myself as a child I'm trying to get excited about hopefully making myself excited.\n\nStevie said it feels like we keep on taking projects and I get not interested so we keep switching. I said the part of the reasoning of why I didn’t start a new project when I lost interest in the survival guide is because I didn't want to keep switching from one partially started protect to another.\n\nStevie said one thing I should try is just cutting the scope to the minimum then publishing. Later I can come back to it and say oh actually I wanted to add to it. I realized that the nice thing about publishing publicly might be that I could get a lot of lots of feedback that motivates me Stevie points out. Alternatively, I can get negative feedback or silence and be happy. I don't waste time on something no one likes.\n\nI said a challenge of mine is that when I have intense emotion, I react, and instead of thinking. For example, all the times I just react to not want something by switching to something else and see if they hang out why is it too vague and unspecific. Stevie recommends I should try journaling about it, talking to myself with a recording, that type of thing to keep a record about what how I feel and why. For example, where do I feel that anxiety in my body, what emotions do I feel, where do I feel it in my body? I should make checklist of what to do in. Stevie suggested printing them out and taping them on my wall so I can go to my physical wall in my room since he's concerned, I'll forget I have the checklists. I should have a loss move for project checklist, feel like I need to ask for permission too much, and maybe some others. Stevie said I need to put in canonical places. I think that means places where I won't easily forget about. For example, my website. I like the idea of putting it on my website and publishing on Twitter because other people might find it useful.\n\nI\n        
\n\n     \n        \n        \n        
\n\n        \n    \n`;\n\n  return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", AreYouSolvingtheRightProblems);\nexport default app.fetch;\n\n{\n  /* \n
; */\n}",3,["D",1759331828771],236,{"_103":353,"_156":138,"_153":255,"_95":99,"_165":354,"_163":164,"_100":287,"_155":-5,"_105":355,"_157":356,"_168":-5},"24480f5a-9d40-11f0-8319-0224a6c84d84","/** @jsxImportSource https://esm.sh/hono@latest/jsx **/\nimport { Hono } from \"https://esm.sh/hono@3.10.2\";\n// last stable version is 61\nconsole.log(\"[Init] Starting lostMotivationChecklist val\", new Date().toISOString());\n\nexport const lostMotivationChecklist = (c: any) => {\n  const html = `\n\n    \n        Lost Motivation Checklist\n        \n    \n    \n        \n            Home \n            About \n            Twitter \n            Github\n        
\n\n      \n        \n        My challenge is that when I feel intense emotions, I react instead of think. Therefore, I'm making a checklist to remind myself of what I should do.\n        
\n\n     \n        \n        This great article from Thomas Wedell-Wedellsborg explains how I can check I'm working on the right thing\n        in a way that uses a reasonable amount of time. He emphasizes reasonable amount of time because many \n        frameworks are so time-consuming they're only practical on the strategic level. The simpler frameworks \n        tend to assume the first definition of the problem is the easiest and most effective to solve.\n        
\n\n     \n        \n        I think a great way to explain the value of their approach is the slow elevator problem. In it you are the \n        owner of an old building with a major problem. Several tenants are threatening to break their lease if you \n        don't reduce the wait time and make the elevator faster. Most people would recommend replacing the motor or\n        even the elevator. That type of suggestion is what's called the solution space. A solution space is a \n        group of suggestions that share a common assumption about the problem. On the other hand if you ask a building \n        manager, they recommend putting up a set of mirrors by the elevator. It solves the problem because \"people \n        tend to lose track of time when given something utterly fascinating to look at—namely,\n        themselves.\" \n        
\n\n        \n        The mirror solution is particularly interesting because in fact it is not a solution to the stated problem:\n        It doesn’t make the elevator faster. Instead it proposes a different understanding of the problem.\n
\n        \n        Note that the initial framing of the problem is not necessarily wrong. Installing a new lift would probably\n        work. The point of reframing is not to find the “real” problem but, rather, to see if there is a better one\n        to solve. In fact, the very idea that a single root problem exists may be misleading; problems are \n        typically multicausal and can be addressed in many ways. The elevator issue, for example, could be \n        reframed as a peak demand problem—too many people need the lift at the same time—leading to a solution that\n        focuses on spreading out the demand, such as by staggering people’s lunch breaks.\n        
\n        
\n        \n        \n        \n        I found their example about the number of dogs in shelters educational too.\n        
\n\n        \n        \n        Identifying a different aspect of the problem can sometimes deliver radical improvements—and even spark solutions \n        to problems that have seemed intractable for decades. I recently saw this in action when studying an often \n        overlooked problem in the pet industry: the number of dogs in shelters\n        
\n        \n…\n        
\n\n      \n\n        \nLori Weise, the founder of Downtown Dog Rescue in Los Angeles, has demonstrated that adoption is not the only way to frame the problem. Weise is one of the pioneers of an approach that is currently spreading within the industry—the shelter intervention program. Rather than seek to get more dogs adopted, Weise tries to keep them with their original families so that they never enter shelters in the first place. It turns out that about 30% of the dogs that enter a shelter are “owner surrenders,” deliberately relinquished by their owners. In a volunteer-driven community united by a deep love of animals, those people have often been heavily criticized for heartlessly discarding their pets as if they were just another consumer good. To prevent dogs from ending up with such “bad” owners, many shelters, despite their chronic overpopulation, require potential adopters to undergo laborious background checks.\n        
\n        \n        \nWeise has a different take. “Owner surrenders are not a people problem,” she says. “By and large, they are a poverty problem. These families love their dogs as much as we do, but they are also exceptionally poor. We’re talking about people who in some cases aren’t entirely sure how they will feed their kids at the end of the month. So when a new landlord suddenly demands a deposit to house the dog, they simply have no way to get the money. In other cases, the dog needs a $10 rabies shot, but the family has no access to a vet, or may be afraid to approach any kind of authority. Handing over their pet to a shelter is often the last option they believe they have.”\n        
\n\n        \nWeise started her program in April 2013, collaborating with a shelter in South Los Angeles. The idea is simple: Whenever a family comes in to hand over a pet, a staff member asks without judgment if the family would prefer to keep the pet. If the answer is yes, the staff member tries to help resolve the problem, drawing on his or her network and knowledge of the system.\n        
\n\n        \nWithin the first year it was clear that the program was a remarkable success. In prior years Weise’s organization had spent an average of $85 per pet it helped. The new program brought that cost down to about $60 while keeping shelter space free for other animals in need. And, Weise told me, that was just the immediate impact: “The wider effect on the community is the real point. The program helps families learn problem solving, lets them know their rights and responsibilities, and teaches the community that help is available. It also shifted the industry’s perception of the pet owners: We found that when offered assistance, a full 75% of them actually wanted to keep their pets.”\n        
\n        
\n\n\n\n     \n        \n        I like Thomas identifies questions I didn't realize I needed to ask and answer them. For example I \n        appreciate he explained there's no such thing as a single root cause. Instead there are \n        generally multiple causes. Each of those individually could mitigate or even solve the problem.\n        
\n\n     \n        \n        As someone with autism I really appreciate how clearly Thomas breaks down how to implement his process. \n        His anecdotes help me visualize how the processes are implemented.\n        
\n\n\n     \n        \n        The first part of the article is meant to explain the value of their process. The second part \n        explains how you can use the process and the best way to.\n        
\n\nEstablishing legitimacy is how you convince people to give the process a try. (Intuitively this feels like it should be somewhere else but the article put it here)
\nBringing outsiders into the discussion is beneficial because often the experts don't understand the problem \nnearly as well as the people experiencing it. 
\nGeting people’s definitions in writing tells you about subtle differences like whether people think the problem is employees not being engaged enough to innovate or the customers not paying for innovation.
\nAsking what’s missing gives you the information you need to reframe the question.
\nConsidering multiple categories can tell you if you're considering enough types of causes of problems and if \nnot which types you should.
\nAnalyzing positive exceptions can raise morale and are often an easier way to solve the problem than figuring it out from first principles.
\nQuestioning the objective is important because often the first way to solve a problem isn't the best way of \nachieving your goal.
\n\n
\n\n      \n        \n        Thomas explained the best way to use his process depending on the time you have.\n        
\n\n        \n       The practices I outline here can be used in one of two ways, depending on how much control you have over the situation. One way is to methodically apply all seven to the problem. That can be done in about 30 minutes, and it has the benefit of familiarizing everyone with the method.
\nThe other way is suitable when you don't control the situation and have to scale the method according to how much time is available. Perhaps a team member ambushes you in the hallway and you have only five minutes to help him or her rethink a problem. If so, simply select the one or two practices that seem most appropriate.
\nFive minutes may sound like too little time to even describe a problem, much less reframe it. But surprisingly, I have found that such short interventions are often sufficient to kick-start new thinking—and once in a while they can trigger an aha moment and radically shift your view of a problem. Proximity to your own problems can make it easy to get lost in the weeds, endlessly ruminating about why a colleague, a spouse, or your children won't listen. Sometimes all you need is someone to suggest, \"Well, could the trouble be that you are bad at listening to them?\"
\nOf course, not all problems are that simple. Often multiple rounds of reframing—interspersed with observation, conversation, and prototyping—are necessary. And in some cases reframing won't help at all. But you won't know which problems can benefit from being reframed until you try. Once you've mastered the five-minute version, you can apply reframing to pretty much any problem you face.
\n
\n\n      \n        \n        I wouldn't have realized that following a checklist tends to discourage productive thinking. I'd like to \n        think I would've realized I needed to test things out in the real world too.\n        
\n\n      \n        \n        I really liked the examples and anecdotes because it helped me understand how the process could be used and how useful it is.\n        
\n        \n    \n`;\n\n  return c.html(html);\n};\n\nconst app = new Hono();\napp.get(\"/\", AreYouSolvingtheRightProblems);\nexport default app.fetch;\n\n{\n  /* \n; */\n}",["D",1759155926050],235,{"_103":358,"_156":138,"_153":255,"_95":99,"_165":72,"_163":164,"_100":289,"_155":-5,"_105":359,"_157":360,"_168":-5},"0dc8d326-97d3-11f0-ad15-0224a6c84d84",["D",1758559317347],234,{"_103":362,"_156":138,"_153":255,"_95":363,"_165":72,"_163":164,"_100":32,"_155":-5,"_105":364,"_157":365,"_168":-5},"fcfe31b2-97d2-11f0-af8d-0224a6c84d84","new-file-392.ts",["D",1758559289181],233,"versions",[368,370,371,372,373,374,375,376],{"_306":328,"_369":330},"previous",{"_306":330,"_369":336},{"_306":336,"_369":341},{"_306":341,"_369":346},{"_306":346,"_369":352},{"_306":352,"_369":357},{"_306":357,"_369":361},{"_306":361,"_369":-5},"versionNumber","page","hasNext","actionData","errors"]

Bringing My OCD Online: Userscripts for Immersive Forum Browsing

Debugging Checklist

Observe the bug

Create a reproducible input

Narrow the search space

Analyze

Devise and run experiments

Modify code to squash the bug

What is HTTP

Credit

Time Blindness Loud Calendar via iOS Shortcuts

How it works

Installation Guide

1. Add the shortcut

2. Give permissions to the shortcut

3. Schedule the shortcut

Will Krouse

Credit

Callback hell

Credit

link to article with a hyper text of the title and state the problem the article solves solves

give a high level explanation of why the article is different than the other one that tried to solve this problem.

give a low-level explanation of why the article is different then follow up with a quote that expands follow up with a quote that expands it

State small thing they do that you like for example introducing a new term

explain what is the thing that is the highlight of the article for you

explain the focus of the article and a short explanation of how it works

answer questions like when should you upgrade from a low-level cheap use to something more expensive that is more effective

include something you might not have thought of like needing to

include a warning about things people may not have participated like for example if possible you should try to avoid letting LLMs plan out their workflow by themselves

include a cool thing it has

Blog

What is a status report

Sample good sample report

How to write a quality status report?

Project Name

Motivation

Goal

Model

Status now

Status last week

Progress since last week

Activity that didn’t move status forward

Next Steps

Open Questions

Template to copy

willthereader

WillpersonalWebsite

History for lostMotivationChecklist.ts