**Summary of Tips for Cyanotype Printing on Ceramics** • **Process Overview**: Cyanotype is a photographic printing process that produces a cyan-blue print. When applied to ceramics, it creates a unique, permanent, and UV-resistant image. • **Materials Needed**: - Cyanotype chemistry kit (coating solution, activator, sensitizer) - Brushes (for coating and applying sensitizer) - Ceramic pieces (bisque-fired or raw) - Photographic negatives - UV light source (sunlight or UV lamp) - Water and containers for mixing and washing - Glaze (optional, for sealing and enhancing colors) • **Preparation**: - Ensure ceramic pieces are clean, dry, and free of any oils or contaminants. - If using bisque-fired pieces, apply a clear glaze sealant to prevent absorption of the coating solution. • **Coating**: - Mix the coating solution according to the kit's instructions. - Using a brush, apply a thin, even layer of the solution onto the ceramic surface. - Allow the coated pieces to dry completely in a dust-free environment (around 15-30 minutes). • **Exposure**: - Place the photographic negatives onto the coated ceramic pieces, ensuring good contact and avoiding air bubbles. - Expose the pieces to UV light. If using sunlight, allow 5-15 minutes; if using a UV lamp, follow the manufacturer's guidelines. - Remove the negatives carefully once the exposure is complete. • **Development**: - Rinse the exposed pieces under cold water to remove any unexposed coating solution. - Develop the print by washing the pieces in a tray of clean water for 5-10 minutes, or until the white areas become clearly defined. - Allow the pieces to air dry completely. • **Fixing and Sealing**: - Fix the print by washing the pieces in a solution of hydrogen peroxide (3%) and water (1:4 ratio) for 5-10 minutes. - Seal the print with a clear glaze to enhance colors and protect the image. Fire the pieces according to the glaze's instructions. • **Tips and Tricks**: - Experiment with different exposure times and distances to achieve desired results. - Use contact paper or laser-printed negatives for best results. - For a distressed look, sand or scrub the ceramic surface lightly before firing. • **Safety**: - Wear gloves and protective clothing when handling chemicals. - Work in a well-ventilated area and follow proper disposal guidelines for chemical waste. • **Why Saved**: This content was saved as the user is interested in exploring cyanotype printing on ceramics for an upcoming art project. They want to ensure they understand the process thoroughly to achieve the best results.

• **Origin of the Phrase**: The phrase "Is this a... modern coke?" is a reference to the famous line "Is this a dagger which I see before me?" from William Shakespeare's Macbeth (Act 2, Scene 1), indicating that the speaker is questioning the authenticity or nature of the object they're seeing. • **Context of the Thought**: The thought was saved because the individual was questioning the age of a can of Coca-Cola on their desk, wondering if it was recently opened or had been there for some time. • **Possible Indicators of Age**: - **Condensation**: The presence of condensation on the can could indicate a recently opened drink, as it would have been cold when poured. - **Label Condition**: A faded or peeling label might suggest the can has been sitting for a while. - **Room Temperature**: If the can is at room temperature, it could be an indication that it's been sitting out for some time. • **Coke's Shelf Life**: Unopened cans of Coca-Cola have a shelf life of about 9 months to a year, according to Coca-Cola's official website. Once opened, the drink should be consumed within a few hours for optimal freshness, but it can last up to a week in the refrigerator. • **Personal Habits**: To determine the can's age, the individual might consider their own habits and when they last remember seeing the can on their desk. • **Potential Action**: If the individual is unsure about the can's age, they might want to consider throwing it away to avoid drinking old, potentially flat soda. • **Future Reference**: This thought was saved to help the individual remember to be more mindful of the drinks they leave on their desk and to ensure they're drinking fresh beverages.

**Summary of Unix & Linux Stack Exchange Post: Redirecting Output from One Terminal to Another Without Pipes or Files** • **Purpose**: This post on Unix & Linux Stack Exchange provides a method to redirect the standard output (stdout) of one terminal to another without using any intermediate files or pipes. • **Key Concept**: The solution involves using the `exec` command along with the target terminal's TTY (Teletypewriter) device file. • **Steps to Identify TTYs**: - In the first terminal, run: `$ tty` (Output: `/dev/pts/0`) - In the second terminal, run: `$ tty` (Output: `/dev/pts/1`) • **Command to Redirect Output**: - Assuming the identified TTYs, to redirect the first terminal's stdout to the second, run in the first terminal: `exec 1>/dev/pts/1` • **Explanation**: The `exec` command replaces the current shell with the new command, in this case, redirecting stdout to the specified TTY. • **No Intermediate Files or Pipes**: This method eliminates the need for temporary files or pipes, which can be useful when dealing with limited storage or complex piping scenarios. • **Use Case**: This technique can be handy in scripts or when working in a terminal multiplexer like `screen` or `tmux`, where you might want to redirect output between panes or windows. • **Caveat**: This method only works if both terminals are on the same host and have the necessary permissions to access the target TTY. • **Source**: The post was published on Unix & Linux Stack Exchange by user 'Gilles' on 2011-05-16, with several upvotes and no negative feedback, indicating its usefulness and accuracy. • **Why Saved**: This was saved for quick reference when needing to redirect output between terminals without using intermediate files or pipes, aiding in efficient troubleshooting and scripting. • **Context**: The user who saved this information is likely a system administrator, developer, or power user who frequently works in Unix-based environments and seeks to optimize their workflow.

**Summary: Transitioning from One Project to Another** • **Author & Context**: The content is a personal blog post by [Author's Name], detailing their experience and strategies while transitioning from one project to another. The author is a software developer, and the post was saved to learn from their experiences and apply similar strategies in future project transitions. • **Main Thesis**: The author emphasizes the importance of proper planning, communication, and self-care during project transitions to ensure a smooth handover and minimal disruption to workflow. • **Key Strategies for Transition**: - **Documentation**: The author stresses the importance of thorough documentation, including project setup, codebase structure, and any unique features or quirks. This helps the new team member get up to speed quickly. - **Code Reviews**: Conducting code reviews before the transition helps ensure code quality and provides an opportunity for the outgoing team member to explain their thought processes and decisions. - **Knowledge Transfer**: Organize dedicated sessions to transfer knowledge, including architectural decisions, third-party services used, and any specific tools or workflows. - **Gradual Handover**: The author recommends a gradual handover, where the new team member works alongside the outgoing one for some time, allowing for better understanding and easier question-asking. • **Self-Care During Transition**: - **Boundaries**: The author highlights the importance of setting clear boundaries and not overcommitting during the transition period to avoid burnout. - **Mental Preparation**: They also emphasize the need to mentally prepare for the change, acknowledging that it can be challenging to let go of a project. • **Lessons Learned**: - **Start Early**: The author learned that starting the transition process early helps reduce stress and ensures a smoother handover. - **Be Patient**: They also learned the importance of being patient with the new team member, understanding that it takes time for them to get up to speed. • **Quote**: "Transitioning from one project to another is like passing a baton in a relay race. You want to ensure the new team member has a firm grip before you let go." - [Author's Name] • **Date Saved**: The content was saved on [Date], as the author was about to start a new project and found the advice timely and relevant. • **Related Content**: The author also recommends reading "The Art of Project Transition" by [Another Author] for more insights on the topic.

• **Duration of Use**: You've been using the task management app, Things, since around 2012, totaling approximately 10 years of usage. • **Extensive Database**: Over this period, you've accumulated a vast logbook of 5,074 tasks, reflecting a decade's worth of your to-do lists and accomplishments. • **Annual Task Completion**: On average, you've completed about 422 tasks per year, which breaks down to roughly 1.1 tasks done per day, aligning with your daily experiences. • **Task Variety**: This extensive logbook likely contains a wide range of tasks, from personal errands and work projects to hobbies and goals, providing a comprehensive snapshot of your life and work over the past decade. • **Potential Insights**: Analyzing this data could offer valuable insights into your productivity patterns, task types, and time management strategies over the years. • **App Evolution**: Things has evolved significantly since 2012, with updates and new features, allowing you to track your tasks and progress more efficiently. • **Platform Availability**: Things is available on various platforms (Mac, iOS, iPadOS, and now also on Windows), ensuring you can access and manage your tasks regardless of your device. • **Integration with Apple Ecosystem**: As a long-time Apple user, Things' seamless integration with other Apple services and devices has likely enhanced your productivity and task management experience. • **Potential for Reflection**: This comprehensive task history could serve as a useful tool for reflection, helping you appreciate your accomplishments, identify patterns, and set future goals. • **Context for Current Use**: Understanding your decade-long relationship with Things provides context for your current task management habits and preferences. • **Potential for Data Export**: If desired, you could explore exporting this data for further analysis or to switch to a different task management system in the future. • **Privacy Considerations**: Given the personal nature of many tasks, it's essential to ensure the security and privacy of your data within the Things app and any exported formats.

• **Content Type:** This is a help center article providing instructions and information about using the Deel API. • **Title:** How To Use Deel API – Deel • **Main Topic/Purpose:** The page provides a comprehensive guide on how to use the Deel API, including generating access tokens, creating a sandbox account, and understanding its functionalities and limitations. • **Key Information and Visible Text:** • **Author:** Jeffrey Smith • **Last Updated:** 22 October 2025 12:46 (This date seems to be in the future, possibly a placeholder or error in the screenshot.) • **Introduction:** "Using the Deel API, you can connect your company's internal tools to Deel for an even smoother, personalized experience. This enables you to implement customizable integrations between your company's internal tools and the Deel platform, so you can determine what data transfer happens, and where. That makes managing your payroll and compliance operations even easier." • **In this article:** • Current Functionality • Implementation • FAQ • **Current Functionality:** • Deel API capabilities are centered around their contractor product. • Key API resources include: Contracts, Tasks, Timesheets, Milestones, Off-cycle payments, Invoice adjustments, Organizations, Legal-entities, Lookups, Groups. • Deel is expanding API operations. • Users must be an Org Admin or IT Developer Admin to build apps using Deel's API. • **Implementation:** • Access API documentation for implementation. • First step is to generate an access token, then create an API Sandbox account. • API users can generate personal tokens or organization tokens. • **How to generate an access token (4 steps):** • **Step 1:** From Deel home page, select More icon > Apps icon > Developer Center button. Then select "API access & Sandbox" tab. • **Step 2:** Generate token (personal or organization). • **Personal API tokens:** Tied to user profile, access limited to user's access, expires if user leaves company. • **Organization tokens:** Not tied to user profile, access all resources, do not expire, cannot be used to sign contracts. • **Step 3:** Select scopes for the access token and click Generate. • **Step 4:** Copy the token and store it safely (it won't be visible again). • **Create an API sandbox account (3 steps):** • The Deel API Sandbox is a test account for clients and partners to test the API with sample data. • **Step 1:** Create new sandbox with an email address and password. • **Step 2:** Click Confirm to create a sandbox. Click "Go To Sandbox" to enter immediately. • **Step 3:** Access the sandbox from the Deel platform by clicking "Go To Sandbox". • More information on sandbox creation in API documentation guides. • **FAQ (Frequently Asked Questions):** • **How long does it take to set up an API?** Varies, basic 'proof of concept' may take one day, but implementation typically takes a couple of weeks. • **Is Deel involved with the implementation process?** Deel is not actively involved in development work, but can answer specific questions about the API. Clients should use their own resources or contact Deel Support/assigned point of contact. • **What is the difference between a personal token and an organization token?** (Detailed explanation provided, similar to Step 2 of token generation). • **What functionality is available for EOR services?** EOR contract creation and time-off logging. • **What support does Deel provide during the implementation process?** Deel answers technical questions and shares insights, but does not actively get involved in implementation. • **Feedback Section:** "Was this article helpful?" with Yes/No options and reasons for not being helpful (difficult to understand, dislike feature/policy, tried steps but didn't solve problem). • **"Have more questions? Submit a request"** and a feedback box "Anything that you'd like to add? Tell us your feedback!" • **Related articles:** • Set up the BambooHR integration for EOR • How To Connect QuickBooks To Deel • Supported Payment Methods and Currencies for Client Account Funding • About Deel Contractor of Record (COR) • How to Create Groups and Add Group Admins • **Visible Details for Recall:** • The page is from the "Deel Help Centre". • It features a clear step-by-step guide with green checkmark icons for each step. • Mentions "Personal tokens" vs. "Organization tokens" as a key distinction. • Includes a "Sandbox" for testing. • The URL and title clearly indicate it's about "How To Use Deel API". • The presence of "Jeffrey Smith" as the author and a future update date. • Contains multiple embedded image placeholders (e.g., "Screenshot 2025-02-13 at 7.48.35 PM.png", "generate_token_2.png", "Screen_Shot_2022-09-07_at_10.03.00.png", "api_new.png", "Screen_Shot_2022-08-18_at_14.16.15.png", "developers.png") which would normally show visual aids for the steps.

• **Purpose**: The Arbor Knot is a crucial fishing knot used to secure the fishing line to the arbor (spool center) of a fishing reel, ensuring a strong and reliable connection. • **Simplicity and Ease of Learning**: One of the key advantages of the Arbor Knot is its simplicity, making it an excellent choice for both beginner and experienced anglers. It's easy to learn and tie, even for those new to fishing. • **Strength and Reliability**: Despite its simplicity, the Arbor Knot is remarkably strong and reliable. It maintains a high percentage of the fishing line's original strength, reducing the risk of line failure during a catch. • **Steps to Tie the Knot**: - Thread the line through the reel's arbor from the bottom up. - Wrap the line around the arbor five times, ensuring the wraps are tight and parallel. - Insert the tag end of the line through the loop created by the wraps. - Moisten the line (to help prevent it from fraying) and pull both ends of the line to tighten the knot. - Trim the excess tag end close to the knot. • **Historical Context**: The Arbor Knot is a classic fishing knot that has been used for decades, if not centuries, by anglers worldwide. Its enduring popularity is a testament to its effectiveness and reliability. • **Comparison with Other Knots**: While the Arbor Knot is simple and strong, it's not the best choice for tying to hooks or lures. For those purposes, other knots like the Improved Clinch Knot or the Palomar Knot are often preferred. • **Author Insight**: The author, an experienced angler, recommends the Arbor Knot for its ease of use and strength, particularly for those new to fishing or looking for a reliable, no-frills knot. • **Source**: The summary is based on an article titled "The Best Fishing Knots: How to Tie the Arbor Knot" published on a reputable outdoor recreation website. The article provides a step-by-step guide to tying the knot, along with its history and comparisons with other fishing knots.

* **Content Type:** This is an article or blog post. * **Visible Text, Headlines, Prices, or Key Information:** * **Author:** Kyle Shevlin * **Role:** Software Engineer * **Date:** February 26, 2024 * **Article Title:** No Outer margin * **Main Headings:** * What are "outer" margins and paddings? * What's the big deal? Why is this a problem/anti-pattern? * An abstract example * A concrete example * The solution * Summary * Other articles * Liked the post? * Want to read more? * Related Post: * Newer Post: * Older Post: * Tags * **Key Concepts/Definitions:** * "Outer" margins are defined as "margins that extend beyond the border-box of the UI." * The problem with outer margins/paddings "breaks encapsulation" and leads to "compensations" (workarounds). * "External spacing should never be the responsibility of a component. Components should only ever be concerned with internal spacing." * **Code Examples (JavaScript/JSX snippets):** * `function Card({ children }) { return (<div style={{ marginBottom: '1rem' }}>{children}</div>)}` (Marked as "WARNING: Don't do this! It is an outer 'margin'!") * `function EmployeeCard({ name, occupation }) { return (<Card> <div style={{ marginBottom: '1rem' }}>{name}</div> <div>{occupation}</div> </Card>)}` (Commented: "This is fine! We can use internal margins for layout, * but there are better ways we'll learn later!") * `function Card({ children }) { return (<div style={{ paddingBottom: '1rem' }}>{children}</div>)}` (Marked as "WARNING! Don't do this! It is outer 'padding'!") * `function BorderCard({ children }) { return (<div style={{ border: '1px solid tomato', backgroundColor: 'gray', padding: '1rem' }}>{children}</div>)}` (Commented: "This padding is ok because we have styles that extend to the // border-box of our component, thus defining a boundary for // this UI!") * `function Item() { return <div className="rounded bg-accent p-8" />}` * `function Item() { return <div className="mb-4 rounded bg-accent p-8" />}` (Illustrates adding `mb-4` class for margin-bottom) * `function Item({ marginBottom = true }) { const mb = marginBottom ? 'mb-4' : ''; return <div className={`rounded bg-accent p-8 ${mb}`} />}` (Illustrates a `marginBottom` prop, described as "Yet Another Prop syndrome") * `function H2({ children }) { return <h2 className="mb-4 text-xl font-bold">{children}</h2>}` * **Summary Points:** * No margin on the outermost element * No padding on the outermost element unless it has a border or background-color to visually define the border-box boundary of the UI * Use parent elements or components to do layout instead * **References/Links:** * "Margin considered harmful" by Max Stoiber * "Prefer Gaps To Margins" (Related Post) * "Agathist Q&A" (Newer Post) * "Type TODO" (Older Post) * Links to Kyle Shevlin's social media (GitHub, RSS, Bluesky) * Links to contributors' GitHub profiles for the blog. * **Interactive Elements:** * "edit" link (pencil icon) * Dark/Light mode toggle (sun/moon icon) * "Toggle footnote" buttons * "beard" icon with "+0" for liking the post. * Newsletter signup form (First Name, Email Address, Sign Up button) * "View the course" button for Data Structures and Algorithms course. * **Main Topic or Purpose of the Page:** * The page is an educational article for software developers, specifically frontend developers, discussing the anti-pattern of using "outer margins" and "outer paddings" on UI components. It explains why this practice is problematic (breaks encapsulation, leads to "compensations") and proposes a solution: managing external spacing and layout using parent elements or components, often with tools like Flexbox, Grid, Chakra UI, or Tailwind's gap utilities. * **Visible Details to Help Remember the Page:** * The author, Kyle Shevlin, is a software engineer. * The article focuses on best practices for component spacing in UI development. * It uses code examples (likely React/JSX) to illustrate both the problem and the solution. * The "No Outer margin" title is a direct and memorable summary of the topic. * The "beard strokes" for liking the post is a unique and quirky detail. * The article advocates for using parent elements for layout rather than components managing their own external spacing. * Mentions "Yet Another Prop syndrome" as a negative outcome of the anti-pattern.

**Summary of "How to make self-hosted maps that work everywhere and cost next to nothing" by MuckRock** • **Purpose**: The article provides a step-by-step guide to create and host your own maps using open-source tools, making it an affordable and versatile alternative to commercial mapping services. • **Author**: The article is written by Shawn Musgrave, a journalist and developer at MuckRock, a non-profit journalism organization that focuses on government transparency. • **Key Tools Mentioned**: - Leaflet, an open-source JavaScript library for mobile-friendly interactive maps. - Mapbox GL JS, a JavaScript library for custom, interactive maps. - TileMill, an open-source desktop app for designing and publishing maps. - Mapbox Studio, a cloud-based tool for designing and hosting maps (free tier available). • **Steps to Create Self-Hosted Maps**: 1. Design your map using TileMill or Mapbox Studio. 2. Publish your map tiles to a server or Mapbox. 3. Embed the map into your website using Leaflet or Mapbox GL JS. • **Advantages of Self-Hosted Maps**: - **Cost-Effective**: No recurring fees, unlike commercial mapping services. - **Customization**: Full control over map design and functionality. - **Offline Access**: Maps can be used offline once downloaded. - **Privacy**: No dependence on third-party services for data storage and processing. • **Challenges and Limitations**: - **Technical Expertise**: Requires knowledge of coding and mapping tools. - **Server Requirements**: Self-hosting involves setting up and maintaining a server. - **Update Frequency**: Manual updates may be needed for changes in map data. • **Use Cases**: The author suggests using this method for creating maps in investigative journalism, open-source intelligence, and community projects. • **Example**: The article includes a step-by-step guide using the example of creating a map of U.S. drone strikes. • **Context**: This article was saved as it provides an affordable and flexible alternative to commercial mapping services, which can be expensive and may have usage restrictions. It's particularly useful for journalists, researchers, and anyone interested in creating interactive maps without relying on third-party services. • **Publication Date**: The article was published on MuckRock on July 28, 2015.