chore: add files from master-wiki repo

2024-11-20 20:00:35 -03:00 · 2024-11-20 20:00:35 -03:00 · 1847f6bf28
commit 1847f6bf28
parent f99a9ae2ac
315 changed files with 1047341 additions and 0 deletions
--- a/_master_wiki/void/Readwise/10
+++ b/_master_wiki/void/Readwise/10
@ -0,0 +1,64 @@
+# 10 Practical Time Management Tips for When Everything Is a Priority
+
+![rw-book-cover](https://rebelsguidetopm.com/wp-content/uploads/2016/04/GGtPM-Pin-5.png)
+
+## Metadata
+- Author: [[Elizabeth Harrin]]
+- Full Title: 10 Practical Time Management Tips for When Everything Is a Priority
+- Category: #articles
+- URL: https://rebelsguidetopm.com/time-management-tips/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=10%20Practical%20Time%20Management%20Tips%20for%20When%20Everything%20Is%20a%20Priority
+
+> [!note]
+> **Background:** I aim to enhance my personal organization within my projects to manage tasks more effectively and make better use of my time.
+> **Top 3 Important Takeaways:**
+> 🗂️ **Establish Clear Priorities:** Understand the distinction between urgent and important tasks. Use tools like the Eisenhower Matrix to identify and focus on high urgency and high importance tasks, ensuring that you also allocate time for important but less urgent tasks to avoid last-minute stress.
+> 📅 **Create a Structured Schedule:** Develop a detailed weekly plan that includes your priorities, meetings, and commitments. Dedicate specific time blocks each day to work on tasks that align with your goals, helping you stay organized and productive throughout the week.
+> ✉️ **Implement an Email Management Strategy:** Design a system to manage your emails effectively, reducing inbox clutter and stress. This will allow you to quickly find important messages and maintain organization, especially when dealing with multiple priorities.
+> [!tldr]
+> This article offers practical time management tips for increasing productivity when everything feels like a priority. The tips include scheduling your time, understanding the difference between urgent and important tasks, and knowing when you are most productive. By following these tips, you can better prioritize tasks and manage your workload effectively.
+
+## Highlights
+I am most productive and get the most out of my time when my time is planned. [View Highlight](https://read.readwise.io/read/01j98zjaq5c6j0kah92r2s5pwf))
+
+This is how I schedule my time:
+• I work out my priorities for the week.
+• I look at what meetings and other commitments I have.
+• I split my priorities across the week, blocking out time each day to do something that gets me closer to having achieved my goals by Friday. [View Highlight](https://read.readwise.io/read/01j98zkq45h9f9e2hw0afrc21y))
+
+Not everything that is urgent is important.
+And not everything that is important is urgent. ... Important means something that:
+• has high significance
+• other people believe is a good use of your time
+• will help you or the organization reach your goals. ... Urgent tasks are things that have to happen now.
+
+Tasks that are high urgency and high importance should take most of your time in the day.
+However, ideally, you’ll also be spending time on the highly important but less urgent tasks too. Plan these in your calendar for the coming weeks so they don’t become a source of panic. [View Highlight](https://read.readwise.io/read/01j98ztb77ncd7d5zw6v15m6s4))
+> [!note]
+> The Eisenhower Matrix of TickTick was usefull for this
+
+Task priority can change over time [View Highlight](https://read.readwise.io/read/01j990cbt2hveke2849wjwqnst))
+
+You can only block out time on your calendar if you know what your priorities are. Understanding what is urgent and important will help you spot priority tasks. [View Highlight](https://read.readwise.io/read/01j990h9rp0c19yamjw766kw6j))
+
+**the answer is never: everything is a priority.**
+That’s just lazy thinking. Some things will be more priority than others. [View Highlight](https://read.readwise.io/read/01j990jd7zq69xc6fgkeskrtxg))
+
+A great time management tip for teams is to [delegate](https://rebelsguidetopm.com/how-to-delegate-tasks-with-more-confidence-and-less-stress/) to each other. [View Highlight](https://read.readwise.io/read/01j99197wtqzqvx6fbsfvbppsw))
+
+Don’t forget that “managing” also takes time. [View Highlight](https://read.readwise.io/read/01j9918rgtz371s7h6j9shv54t))
+
+Have different To Do lists. Know what you need to achieve this year, quarter, month, week and day. [View Highlight](https://read.readwise.io/read/01j9919h30698gxszd9733vcp1))
+
+Learn when you are at your most productive and use that to your advantage. Schedule your frogs for the time when you are sharpest. [View Highlight](https://read.readwise.io/read/01j991bs54wa52q66hp3kf12k8))
+
+Remember to build some slack into your calendar as well. You can’t work every evening and still function at full capacity during the day. Have some downtime, whatever that looks like for you! [View Highlight](https://read.readwise.io/read/01j991e4nzd98gzr6yee0yger9))
+
+Having a strategy for dealing with email is important because when everything is a priority you have to be able to find messages and stay organized. For me, having thousands of mails in my inbox is a source of stress. [View Highlight](https://read.readwise.io/read/01j991gt8fq6bvjbw40zbpcdvp))
+
+Integrating your schedules will help you see all the key milestones at once. ... At its simplest, make a milestone planner and use that to see which months are going to be your busy times.
+
+Keep talking to your stakeholders and clients about their expectations, and keep communication channels open with your team as well. Managing expectations on all sides goes a long way to keeping the peace. [View Highlight](https://read.readwise.io/read/01j991pdc0apq5bn06k3w9b3hs))
+
+Try to be flexible and adapt to what’s required this week (or today). And let your positive attitude rub off on your team. [View Highlight](https://read.readwise.io/read/01j991rcc7xk5rqgw10e32f3ws))
+
--- a/_master_wiki/void/Readwise/11
+++ b/_master_wiki/void/Readwise/11
@ -0,0 +1,41 @@
+# 11 Life-Changing Journaling Tips for Beginners
+
+![rw-book-cover](https://www.simplyfiercely.com/wp-content/uploads/2021/05/11-Life-Changing-Journaling-Tips-For-Beginners-Feature-Image.jpg)
+
+## Metadata
+- Author: [[Jennifer]]
+- Full Title: 11 Life-Changing Journaling Tips for Beginners
+- Category: #articles
+- URL: https://www.simplyfiercely.com/journaling-tips/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=11%20Life-Changing%20Journaling%20Tips%20for%20Beginners
+> [!tldr]
+> Journaling is a powerful tool for self-discovery and personal growth. To help beginners get started, the author shares 11 tips, like using prompts and writing honestly. The key is to enjoy the process and make journaling a regular habit.
+
+## Highlights
+1. Keep a list of go-to prompts ... They can be very helpful if you’re just starting because they give you a place to begin.
+
+write as though you’re talking to someone else.
+You can write to:
+• Your future self
+• Your younger self
+• To someone who is no longer with us
+• To someone who has hurt your feelings
+• To someone you admire
+• To someone who needs your help [View Highlight](https://read.readwise.io/read/01j862h864h4mhyv3vqy6xvve3))
+
+If you’re working from a list of journaling prompts, using a guided journal, or experimenting with a new journaling method, and something doesn’t feel right for you—then it’s OK to stop. [View Highlight](https://read.readwise.io/read/01j862kcsaxk8909cdb69f3dpe)) ^05df43
+
+Remember that the point of a prompt is to get your thoughts flowing freely, not necessarily to answer or address that specific question or statement. [View Highlight](https://read.readwise.io/read/01j862kvny6qx7bt3eykq0z8zm)) ^ce92d8
+
+But here’s the thing: too much inspiration can often lead to paralysis. [View Highlight](https://read.readwise.io/read/01j862ppxd79psqff22tjz21z1))
+
+cover the first page with a big scribble! A friend of mine recommends doing this as a way to break the ice [View Highlight](https://read.readwise.io/read/01j862r1djv5s1px2z8f233efa))
+
+Freewriting is a form of journaling where you write everything down without stopping, editing or even correcting grammar until your mind feels empty. [View Highlight](https://read.readwise.io/read/01j862t96pgsrqk03vdvpcj643)) ^ffddd6
+
+Keep this in mind at the start of your journey as you may feel pressure to journal the “right way”. When it comes to journaling, there is no right way. It’s your space to explore how you see fit. Don’t overthink it—just keep writing! [View Highlight](https://read.readwise.io/read/01j862vd6rrf591ccavj9s1f5b))
+
+To get the full benefits of journaling, you have to be honest. Open up and be vulnerable—it’s one of the few genuinely private spaces you have (unless you choose to share your journal with someone). The more honest you are, the closer you’ll get to your truth. [View Highlight](https://read.readwise.io/read/01j862vy4n84vzqznh9t62t0qx)) ^4d6f9f
+
+Whenever you have a thought or feel strong emotions, write them down. [View Highlight](https://read.readwise.io/read/01j862ww1v0j1ebb9rfkd1ww7e))
+
--- a/_master_wiki/void/Readwise/17-Year-Old
+++ b/_master_wiki/void/Readwise/17-Year-Old
@ -0,0 +1,19 @@
+# 17-Year-Old Student Exposes Germany's 'Secret' Pirate Site Blocklist
+
+![rw-book-cover](https://news.ycombinator.com/favicon.ico)
+
+## Metadata
+- Author: [[isaacfrond]]
+- Full Title: 17-Year-Old Student Exposes Germany's 'Secret' Pirate Site Blocklist
+- Category: #articles
+- URL: https://torrentfreak.com/17-year-old-student-exposes-germanys-secret-pirate-site-blocklist-240822/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=17-Year-Old%20Student%20Exposes%20Germany%27s%20%27Secret%27%20Pirate%20Site%20Blocklist
+> [!tldr]
+> A 17-year-old student in Germany has created a website to reveal the blocked pirate sites that major internet providers do not disclose. This initiative aims to increase transparency and address concerns about censorship related to copyright enforcement. The site, CUIIliste.de, lists 275 blocked domains, allowing users to see which sites are restricted.
+
+## Highlights
+watchdog [View Highlight](https://read.readwise.io/read/01j64wj1fy8b0dyhcdsjgv4vta))
+> [!note]
+> Watchdog: A term used to describe an individual or organization that monitors and oversees the actions of others, often to ensure accountability, transparency, and adherence to laws or regulations. Watchdogs play a critical role in various fields, including journalism, government, and environmental protection, by investigating misconduct, exposing corruption, and advocating for the public interest. Their function is essential in promoting ethical standards and fostering public trust in institutions.
+> In the context of Isaac Frond's article, the term "watchdog" refers to individuals or organizations that monitor and ensure accountability regarding governmental or institutional actions, particularly in relation to transparency and rights. The lack of public knowledge about the blocked pirate sites in Germany has led to frustration among journalists and advocates, highlighting the need for oversight. The 17-year-old student, along with his friends, embodies this watchdog role by exposing the secretive blocklist, thereby promoting transparency and challenging potential overreach in copyright enforcement.
+
--- a/_master_wiki/void/Readwise/3
+++ b/_master_wiki/void/Readwise/3
@ -0,0 +1,30 @@
+# 3 Simple Hacks to Stay Up-to-Date as a Developer
+
+![rw-book-cover](https://i.ytimg.com/vi/AIUw82G-jKE/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Bran van der Meer]]
+- Full Title: 3 Simple Hacks to Stay Up-to-Date as a Developer
+- Category: #articles
+- Document Tags: [[star]] 
+- URL: https://www.youtube.com/watch?v=AIUw82G-jKE
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=3%20Simple%20Hacks%20to%20Stay%20Up-to-Date%20as%20a%20Developer
+
+## Highlights
+there's just too much you have to filter somehow you have to find the right news aggregators for your topic [View Highlight](https://read.readwise.io/read/01j6ye17qj6mqt3hvcv776vd0t))
+
+social media is it's itself an
+aggregator of content of course and you can even argue that daily doev which I just showed is social media I recommend to follow specific creators that you like and if you don't have anybody you like yet then you can try and find those people from now on whenever you go to conferences you can pay attention who the speaker is whenever you're reading books or reading articles look up the author see if they have a Blog see if they publish other things [View Highlight](https://read.readwise.io/read/01j6ye8bktbvyjv1763jf4333z))
+
+try and go to at least one conference a year [View Highlight](https://read.readwise.io/read/01j6yebe0q7bq1gdgmf4zzw6xa))
+
+I like conferences because they have a
+tendency to burst your filter bubble [View Highlight](https://read.readwise.io/read/01j6yeckqdxp8na7meb3m1fz14))
+
+you're looking for a job a Meetup is often a chance to meet a company that's very local that's very close to where you live and you get a chance to meet them outside of the normal hiring process which can also be an advantage [View Highlight](https://read.readwise.io/read/01j6yees1azkpzgsabf3r546av))
+
+calm any fear you may have fear fear of becoming
+irrelevant [View Highlight](https://read.readwise.io/read/01j6yefnrc19pj2f04dq6p6h7g))
+
+what I do is once a year I read a lot of vacancies I don't think about applying for another job I'm not actually applying for another job I am just purely looking at what companies are looking for [View Highlight](https://read.readwise.io/read/01j6yeg5yy6m8g2tpgd4xj5gv6))
+
--- a/_master_wiki/void/Readwise/5
+++ b/_master_wiki/void/Readwise/5
@ -0,0 +1,8 @@
+---
+
+New highlights added at 2024-09-15 3:42 PM
+People are highly visual but can get overwhelmed by too many graphics. Liferay takes a direct approach to educating users by using images only when it matters, such as in screenshots of actual elements. By limiting the unnecessary items in your design system documentation, you can ensure the important things get communicated. [View Highlight](https://read.readwise.io/read/01j7tw12yxcgpsp883nsvscf1t))
+
+IBM shows that if you want to ensure that everyone can use your product, you need to start that process with your design system.
+And when you do, don’t just state your intent. Educate your team on the accessibility challenges different people face and teach them proven best practices that can make a noticeable difference for millions of people worldwide. [View Highlight](https://read.readwise.io/read/01j7twa6wgtnehe050h7br44r7))
+
--- a/_master_wiki/void/Readwise/6
+++ b/_master_wiki/void/Readwise/6
@ -0,0 +1,69 @@
+# 6 Morning Journal Prompts That Will Transform Your Day
+
+![rw-book-cover](https://www.simplyfiercely.com/wp-content/uploads/2021/06/6-Morning-Journal-Prompts-That-Will-Transform-Your-Day-Feature-Image.jpg)
+
+## Metadata
+- Author: [[Jennifer]]
+- Full Title: 6 Morning Journal Prompts That Will Transform Your Day
+- Category: #articles
+- Document Tags: [[journaling]] [[notetaking]] 
+- URL: https://www.simplyfiercely.com/morning-journal-prompts/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=6%20Morning%20Journal%20Prompts%20That%20Will%20Transform%20Your%20Day
+> [!tldr]
+> Morning journaling can help you start your day with clarity and purpose by processing your thoughts and emotions. Using specific prompts can guide your reflections and help you feel more focused and less overwhelmed. Establishing a morning journaling routine can make your mornings more enjoyable and productive.
+
+## Highlights
+1. How do I want to feel when I go to bed tonight?
+**Use when: You feel stuck, unsure, or even a bit lost.** [View Highlight](https://read.readwise.io/read/01j8588c42w7v68v76cjzak02x)) [[journaling/prompt]]  ^80fb8d
+
+To do this, start by imagining that you’re in bed at the end of the day and you’re about to close your eyes. Take a deep breath and then exhale. How do you want to feel at that moment? [View Highlight](https://read.readwise.io/read/01j858a7fzcsje3ptx8evpnh7g))
+
+instead of saying *happy,* you could write down that you want to feel *accomplished* or *connected*. [View Highlight](https://read.readwise.io/read/01j858ajbqht1382hc75spg314))
+
+take things a step further by brainstorming simple actions that will support you. [View Highlight](https://read.readwise.io/read/01j858b7frqbr2kpzck52rsvdr))
+
+2. What season of life am I in?
+**Use when: You’re feeling overwhelmed by your to-do list.** [View Highlight](https://read.readwise.io/read/01j858cvvbjkzh75jvzbet09xa)) ^44f8db
+
+think about your own life and ask yourself, “What season am I in?”
+• Are you in a season of caring for others?
+• A season of resting while you heal from physical or emotional trauma?
+• A season of growth in your career or professional life? [View Highlight](https://read.readwise.io/read/01j858g53d4y95edq9ca2265kx))
+
+Living a balanced life means knowing when to drop some things and when to pick up others *depending on what season you’re in right now*. It gives you permission to focus on what you need most and clarity to choose a few [things to let go of](https://www.simplyfiercely.com/things-to-let-go-of/) (for a while, at least). [View Highlight](https://read.readwise.io/read/01j858j3yzdcjpmrd72zrssfrj))
+
+Acknowledging life’s seasonality and where you are in that rhythm can, with practice, release you from the guilt that comes with wanting to do it all. [View Highlight](https://read.readwise.io/read/01j858kpwq5d6xnb80721zj64z))
+
+**Journaling Tip:** When working through this journal prompt, ask yourself if you need rest, if you need to work, if you need to spend time with family or friends, or if you need to be alone right now. [View Highlight](https://read.readwise.io/read/01j858m1vvj4nfkwn9g433he6d))
+
+3. Today I am excited to…
+**Use when: You need a pick-me-up.** [View Highlight](https://read.readwise.io/read/01j858mgv14bedfggjwgza7exg)) [[journaling/prompt]]  ^656f82
+
+you’re generally feeling a little low [View Highlight](https://read.readwise.io/read/01j858sve44psj3r6zvyahhekb))
+
+We are hard-wired to focus more on the negative things in life than the positive things. So how can we overcome this?
+By putting extra attention on the positive in the morning and throughout the day as well. [View Highlight](https://read.readwise.io/read/01j858thnp6y7cam9rbg2098zf))
+
+**Journaling Tip:** If you’re struggling to feel excited, try getting your senses involved. Imagine a warm cup of coffee pressed between your palms, the sound of the birds on your way to work, the sun shining on your skin—and see if it doesn’t change the way you feel. [View Highlight](https://read.readwise.io/read/01j858s0zxdjg1jfa6yhqf5j4c))
+
+4. Today I get to…
+**Use when: You’re feeling burdened or resentful.** [View Highlight](https://read.readwise.io/read/01j858y4e0kv537bhhck4vs0em)) [[journaling/prompt]]  ^e92888
+
+think about things that you have to do today … and see if you can reframe your thoughts about the situation. [View Highlight](https://read.readwise.io/read/01j8591gse70tyvt73pah1aaw1))
+
+**Journaling Tip:** Don’t forget to acknowledge if you are currently living out a past goal or dream! [View Highlight](https://read.readwise.io/read/01j8594bw1hq0kssgpszr0wqxq))
+
+5. I am challenged by…
+**Use when: You’re struggling.** [View Highlight](https://read.readwise.io/read/01j85c3n5raa1jpnkww72tg06n)) [[journaling/prompt]]  ^44a1a6
+
+By making your challenges the focus of your morning journal prompt, you’re ‘eating the frog’ but in a more mindful way. When you write about what challenges you, it is helpful to explore why and how you will overcome the challenge—but you should also write out what it will mean to you or your life. [View Highlight](https://read.readwise.io/read/01j85c8z3kjz86gjm4t6sybshm))
+
+If those words don’t ring true to your situation, you may need to re-evaluate whether the challenge fits with your values and goals. [View Highlight](https://read.readwise.io/read/01j85cngfe6j4f1bp4cy1q88nh))
+
+6. Write it all out
+**Use When: You don’t know what to do next.** [View Highlight](https://read.readwise.io/read/01j85dnb9vnavm92sfq8cvjfds)) [[journaling/prompt]]  ^b6b0bd
+
+The idea behind free-writing is just as it sounds—you simply write out all of your thoughts without editing until there is nothing left. [View Highlight](https://read.readwise.io/read/01j85dpk39fpze0r24wkwas9kt))
+
+I find that it’s powerful because it allows your brain to unload without expectations. It’s a bit like ranting to a friend after a long day—sometimes you just need to get things off your chest, and then you can move on. [View Highlight](https://read.readwise.io/read/01j85dqa7hcqt5k4h4pc161dwc))
+
--- a/_master_wiki/void/Readwise/7
+++ b/_master_wiki/void/Readwise/7
@ -0,0 +1,59 @@
+# 7 Intentional Questions To Ask Yourself Every Day
+
+![rw-book-cover](https://www.simplyfiercely.com/wp-content/uploads/2018/02/Questions-to-Ask-Yourself-Feature-Image.jpg)
+
+## Metadata
+- Author: [[Jennifer]]
+- Full Title: 7 Intentional Questions To Ask Yourself Every Day
+- Category: #articles
+- Document Tags: [[journaling]] 
+- URL: https://www.simplyfiercely.com/7-questions-to-inspire-intentional-living/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=7%20Intentional%20Questions%20To%20Ask%20Yourself%20Every%20Day
+> [!tldr]
+> Regular self-reflection is essential for living a meaningful and purposeful life. Asking yourself seven intentional questions each day can help clarify your priorities and decisions. By taking time to reflect, you can ensure your actions align with what truly matters to you.
+
+## Highlights
+I thought I was too busy for something as trivial as “self-reflection” but now I know it’s one of the most valuable things I can do with my time, and for you as well. [View Highlight](https://read.readwise.io/read/01j85trb36ydy64sbw670rqy75)) ^029f29
+
+1. Why am I doing this?
+This is a deceptively simple yet very powerful question to ask yourself. I think too often we assume we know why we do what we do, but when we carve out time to sit and reflect, the truth can surprise us. [View Highlight](https://read.readwise.io/read/01j85ttaxs6xp6dyt426kv53re)) [[journaling/prompt]]  ^78caa2
+
+It might save you ten minutes on a Monday morning, or ten years spent chasing a goal you don’t even really want. [View Highlight](https://read.readwise.io/read/01j85txf1x20mpd5dtfsex667w))
+
+2. Who am I doing this for? [View Highlight](https://read.readwise.io/read/01j85x45h66bevcpas8kb7jn36)) [[journaling/prompt]]  ^0ea258
+
+This is a good question to ask yourself regularly when you feel your priorities are out of alignment. It can help shine a light on where you need stronger [personal boundaries](https://www.simplyfiercely.com/personal-boundaries/). [View Highlight](https://read.readwise.io/read/01j85x6nevt1a156g7tvrkar7w))
+
+But I should also point out that self-reflection isn’t about judging yourself or others. Instead, it’s about honesty; knowing why you do what you do and who you do things for, so you can [make intentional decisions about how to invest your time, money and energy](https://www.simplyfiercely.com/intentional-time-money-energy/). [View Highlight](https://read.readwise.io/read/01j85x70r7rxh41qz1tcm196qs))
+
+3. Is there a simpler way? [View Highlight](https://read.readwise.io/read/01j85xafyt9wnwf26pf711mjd2)) [[journaling/prompt]]  ^3b92eb
+
+Taking just five minutes to ask the question and look for a simpler way has saved me countless hours throughout my life. (And I’ll also admit that sometimes it happens in reverse —I’d spend hours doing something and then realise I made it harder than need be!) [View Highlight](https://read.readwise.io/read/01j85xe88z59xav5x5n16yee9k))
+
+4. How does this add value to my life? [View Highlight](https://read.readwise.io/read/01j85xqetvfmrkt17gwaxx8ssh)) [[journaling/prompt]]  ^de9f88
+
+We trade away our precious lives in little moments ... we often spend our *lives* on things that give us little value in return.
+
+if you can’t quickly explain in very specific terms how something is adding value to your life, then odds are it isn’t. [View Highlight](https://read.readwise.io/read/01j85xtzjn34ra2xt29zyevsw4))
+
+5. What am I giving up? [View Highlight](https://read.readwise.io/read/01j85y3wdwgy2mbpkh1pygyevt)) [[journaling/prompt]]  ^8419b3
+
+you put a name to the tradeoffs associated with any decision [View Highlight](https://read.readwise.io/read/01j85y5pfvpjm9mzm49bgc4kya))
+
+Whenever you decide to do or buy something, make sure you think about what you’re giving up to make it happen. [View Highlight](https://read.readwise.io/read/01j85y6bt9wgrec4r2520b5ja7))
+
+6. How does this make me feel? [View Highlight](https://read.readwise.io/read/01j85y8kck7ckzazkgdaphdfjm)) [[journaling/prompt]] 
+
+If you’re doing something that makes you feel sad, anxious, or angry it’s important to understand why. Are you doing something that goes against your core values? Or do you need more rest and support? [View Highlight](https://read.readwise.io/read/01j85ya9vvam560p585n9eyhn6))
+
+Or when you feel more positive emotions—why? What can you learn from your feelings and how can you apply what you learn in your everyday life? How can you be intentional about creating the life you want? [View Highlight](https://read.readwise.io/read/01j85yak4qe3qzhdqnnp65nr74))
+
+7. Am I being honest with myself? [View Highlight](https://read.readwise.io/read/01j85yapckfm2deazf2qfdadx8)) [[journaling/prompt]]  ^b44977
+
+Finally, it’s important to check that you’re being honest with yourself, because if you’re not, none of your other answers really matter. [View Highlight](https://read.readwise.io/read/01j85ye7w6zca1hjwcaqxmp2zt))
+
+---
+
+New highlights added at 2024-10-13 4:11 PM
+Everything in life has a tradeoff. [View Highlight](https://read.readwise.io/read/01j8j1xm6rfcw66sjf6nz1xf47))
+
--- a/_master_wiki/void/Readwise/7
+++ b/_master_wiki/void/Readwise/7
@ -0,0 +1,88 @@
+# 7 Mindful Journaling Prompts to Calm an Anxious Mind
+
+![rw-book-cover](https://www.simplyfiercely.com/wp-content/uploads/2020/12/7-Mindful-Journaling-Prompts-to-Calm-An-Anxious-Mind-Feature-Image.jpg)
+
+## Metadata
+- Author: [[Jennifer Burger]]
+- Full Title: 7 Mindful Journaling Prompts to Calm an Anxious Mind
+- Category: #articles
+- URL: https://www.simplyfiercely.com/mindful-journal-prompts/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=7%20Mindful%20Journaling%20Prompts%20to%20Calm%20an%20Anxious%20Mind
+> [!tldr]
+> Journaling can help calm an anxious mind by bringing awareness to the present and allowing you to explore your feelings without judgment. Mindful journaling prompts provide a structured way to reflect on your thoughts and fears, making it easier to cope with anxiety. Whether you're new to journaling or have experience, these prompts can help you find peace and clarity in stressful times.
+
+## Highlights
+mindful journaling is intended to bring more of your awareness to the present moment. Simply put, it’s the act of conscious writing. It can be particularly helpful for anyone that struggles with meditation because you go to the extra step of taking the thoughts from your mind and making them tangible by writing them down. [View Highlight](https://read.readwise.io/read/01j83kfe31tcya0gkqbfcfw71c))
+
+Mindful journaling can help to ease anxiety by allowing you to uncover the root cause of your stress. After all, one of the [benefits of journaling](https://www.simplyfiercely.com/benefits-of-journaling/) is that it’s a reflective process. It helps you organise your thoughts, and because they’re written down, you have the chance to reflect on them too. [View Highlight](https://read.readwise.io/read/01j83kjtp3t9x64bmgtwkter90))
+
+In the words of Eckhart Tolle, “As soon as you honour the present moment, all unhappiness and struggle dissolve, and life begins to flow with joy and ease.” [View Highlight](https://read.readwise.io/read/01j83m70htvhxtfjfvhb68qsvx))
+
+If you’re new to journaling, you might be hit with ‘writer’s block’. Remember, any new behaviour or practice can take getting used to. [View Highlight](https://read.readwise.io/read/01j83m8kymfctpxjqyw29vq3wh))
+
+[Be intentional](https://www.simplyfiercely.com/be-intentional/) about creating time to write your feelings out. Turn it into a ritual by making yourself a warm drink, lighting a candle, or choosing a nice spot to write in. This might help you create a [daily routine](https://www.simplyfiercely.com/daily-routines/) in the future. [View Highlight](https://read.readwise.io/read/01j83m93tv468vmfpmrafmfg5j))
+
+Prompt: What Am I Feeling Right Now?
+**Use when: You feel like you need to empty a racing brain.** [View Highlight](https://read.readwise.io/read/01j83ncpgpa765e7ma2yk8264x)) [[journaling/prompt]]  ^69db00
+
+Once you start writing, don’t stop until you feel there is nothing else to write. This means you should write *everything* down, even if you begin to veer away from the prompt. Don’t pay any mind to spelling mistakes, your handwriting and don’t edit what ends up on the page. Just write it all out. [View Highlight](https://read.readwise.io/read/01j83nhv221bsrfd0r2fyv08vj))
+
+Prompt: What Am I Afraid Of?
+**Use when: You are overcome with worry.** [View Highlight](https://read.readwise.io/read/01j83njt22m4rmjdrv55g4c356)) [[journaling/prompt]]  ^beb82a
+
+To journal through your fears, start by writing them out one at a time. Ask yourself what are the worse case scenarios, how they might affect you, and what you would do. Ask yourself how likely it is to happen, why you think it might happen, whether its occurrence would be positive or negative and why. [View Highlight](https://read.readwise.io/read/01j83qra9bkp4fzk2vrzhm0erf))
+
+The anticipation of something is usually much worse than when it actually occurs. This is because before something happens, we can’t do anything about it. By journaling through our fears, we’re doing something proactive and preemptive, which can help us work through our fears rather than letting them fester. [View Highlight](https://read.readwise.io/read/01j83sq982ymg9stz6mxbf4776))
+
+Prompt: Write A Letter That You’ll Never Send
+**Use when: The thought of someone is making you anxious.** [View Highlight](https://read.readwise.io/read/01j83sqq9zcr1aahr612jqkh2x)) [[journaling/prompt]]  ^c261c4
+
+Address the letter to the person you need or want to talk to and say everything you want to say. This prompt will help you organise your thoughts and feelings about this person. You can also be as honest as you need because you’re never going to send the letter. [View Highlight](https://read.readwise.io/read/01j83sspweq1e87w1cgb2r1dzd))
+
+If you enjoy letter writing, you could also try a love letter. Write to your younger self (*or your future self!*) and practice being your own best friend. After all, self-love and compassion are also powerful tools for combating chronic anxiety. [View Highlight](https://read.readwise.io/read/01j83stt71p8h0kjdmf24mhpat)) [[journaling/prompt]] 
+
+Prompt: Where Am I Right Now?
+**Use when: You need to feel grounded.** [View Highlight](https://read.readwise.io/read/01j83svpn19zb9t7k0rch206pr)) [[journaling/prompt]]  ^27b8e0
+
+The 5-4-3-2-1 coping technique for anxiety attacks is all about bringing your attention back to the now. ... In your journal, write the following:
+• Five things that you see 
+• Four things that you can touch 
+• Three things that you can hear 
+• Two things that you can smell 
+• One thing that you can taste
+
+Prompt: Why Do I Feel Unwell?
+**Use when: You’re feeling agitated, stressed or anxious for no apparent reason.** [View Highlight](https://read.readwise.io/read/01j83syhvp6jy0mvk0q32qhx8a)) [[journaling/prompt]]  ^3608de
+
+When I’m [so overwhelmed that I can’t think](https://www.simplyfiercely.com/overwhelmed-by-life/) about how to care for myself, I turn to my journal. I start with the line *‘I feel unwell because…’* and let my thoughts flow. Answering this question leads me to discover what I need (whether it be rest, connection, or creative expression). By delving into why I feel unwell, I learn what I can do about it, which improves how I care for myself. [View Highlight](https://read.readwise.io/read/01j83t1ryr94dwp6syd3c051ga))
+
+Prompt: How Can This Moment Inform My Future
+**Use when: You feel like you’ve made a mistake.** [View Highlight](https://read.readwise.io/read/01j83t2c2z79vpc1r0kfpmxz6k)) [[journaling/prompt]]  ^a59479
+
+Taking time to acknowledge our mistakes, understand why they occurred, and think about how we can make better choices in the future is healthy. [View Highlight](https://read.readwise.io/read/01j83t889905a6az7md4d70z3x))
+
+Mistakes are inevitable and mindfully working through them helps us accept them as part of life and let go of perfectionism. [View Highlight](https://read.readwise.io/read/01j83t97qhrr5fxj9nttkbke0n))
+
+Prompt: I Am Lucky To…
+**Use when: You are feeling negative.** [View Highlight](https://read.readwise.io/read/01j83t9evy5zxg8m3qf6r5gkw1)) [[journaling/prompt]]  ^fc98ae
+
+Gratitude is one of the healthiest emotions to sit with. It has the power to shift your mindset from scarcity to abundance, which can be helpful when you’re feeling stressed or just plain having a bad day. [View Highlight](https://read.readwise.io/read/01j83xxb6jwrvvdrg4a7wmvb5n))
+
+try reflecting on:
+• a favourite memory
+• your own strengths
+• song lyrics or a list of favourite songs
+• your greatest lessons
+• your biggest supporter
+• how you overcame a negative experience in the past [View Highlight](https://read.readwise.io/read/01j83xvwfvcc5tjc4an2a92671))
+
+---
+
+New highlights added at 2024-09-23 7:15 PM
+The 5-4-3-2-1 coping technique for anxiety attacks is all about bringing your attention back to the now. ... In your journal, write the following:
+• Five things that you see 
+• Four things that you can touch 
+• Three things that you can hear 
+• Two things that you can smell 
+• One thing that you can taste
+
--- a/_master_wiki/void/Readwise/8
+++ b/_master_wiki/void/Readwise/8
@ -0,0 +1,34 @@
+# 8 Principles for a Secure Cloud Environment
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article4.6bc1851654a0.png)
+
+## Metadata
+- Author: [[omerxx@gmail.com]]
+- Full Title: 8 Principles for a Secure Cloud Environment
+- Category: #articles
+- URL: https://omnivore.app/aleidk/8-principles-for-a-secure-cloud-environment-18f1fa5c54d
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=8%20Principles%20for%20a%20Secure%20Cloud%20Environment
+> [!tldr]
+> On July 15th, 2019, I messed up bad. Real bad. I wanted to finish a project quickly, and show a quick POC to a customer I was working with. To make a long story short, I pushed a container, to a public repo, containing admin credentials to an AWS account.
+
+## Highlights
+CISO BS. [View Highlight](https://read.readwise.io/read/01j58cb911jv15qjeccffqxbv1))
+> [!note]
+> In "8 Principles For a Secure Cloud Environment," the term "CISO" refers to the Chief Information Security Officer, a role responsible for overseeing and ensuring the security of an organization's information and systems. The author implies that some principles may be perceived as excessive or overly cautious, often dismissed as "CISO BS," yet emphasizes their importance based on personal experiences with security incidents. Ultimately, the mention of CISO highlights the necessity of adopting robust security practices to mitigate risks in cloud environments, regardless of differing opinions on their complexity.
+
+Key resources should only be placed in private subnets, effectively isolating them from direct internet access and reducing vulnerability. [View Highlight](https://read.readwise.io/read/01j58ch8xmresvx0x8mty8h37s))
+
+The sharing of SSH keys is a common security pitfall. [View Highlight](https://read.readwise.io/read/01j58ckd7mgrh2b6f6dzmzstz9))
+
+Utilize a dedicated secret manager to securely store and handle access to these sensitive elements, ensuring they’re encrypted and accessible only to those who truly need them. [View Highlight](https://read.readwise.io/read/01j58cm13bxanfd7bxg5th88j4))
+
+Implement a routine where every merge commit is scanned for secret leaks and vulnerabilities using tools like [gitleaks](https://click.convertkit-mail2.com/xmuvr2v7d6h6hr6eg6pc5h03owzllbn/dpheh0h0dwroe6hm/aHR0cHM6Ly9naXRodWIuY29tL2dpdGxlYWtzL2dpdGxlYWtz). Establish strict policies to halt deployments if issues are found in the codebase or in the container images during CI. Don’t have a CI in place yet? 1. Do it! 2. Run these locally before EVERY push. [View Highlight](https://read.readwise.io/read/01j58cn5zg2y5dkd0m9emzevtw))
+
+Move away from traditional firewall-based security for accessing internal systems remotely. Instead, adopt a VPN or, ideally, a Zero Trust framework [View Highlight](https://read.readwise.io/read/01j58cq5q1j7w0xcm19cynt6j7))
+
+Regularly reviewing your cloud bills can help you identify unused or forgotten resources and even expose potential security threats. [View Highlight](https://read.readwise.io/read/01j58dr7eagpfs41b1g7cp42fr))
+
+Deploying a WAF can provide a critical defense layer against numerous web-based threats. The default set of rules can cover 80% of randomly sent malicious query attempts which you can then tweak over time to block additional potentially harmful requests. [View Highlight](https://read.readwise.io/read/01j58drvb7t9633re0pfwc567x))
+
+consider deploying containers that lack any form of shell environment. Building your containers with containers starting with `FROM: scratch` ensures that only the essential application binaries are running, thereby hardening your containers against simple intrusion attempts. [View Highlight](https://read.readwise.io/read/01j58dsmfdt50cgke4skb9d4vf))
+
--- a/_master_wiki/void/Readwise/A
+++ b/_master_wiki/void/Readwise/A
@ -0,0 +1,17 @@
+# A Cyberspace Inquisition #2: Impressions
+
+![rw-book-cover](https://www.adamsdesk.com/assets/img/posts/cyberspace-wormhole.webp)
+
+## Metadata
+- Author: [[Adam Douglas]]
+- Full Title: A Cyberspace Inquisition #2: Impressions
+- Category: #articles
+- URL: https://www.adamsdesk.com/posts/a-cyberspace-inquisition-2/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=A%20Cyberspace%20Inquisition%20%232%3A%20Impressions
+> [!tldr]
+> Navigate cyberspace with me and discover unique content that leave you with impressions and trigger your own inner curiosity to explore and innovate.
+
+## Highlights
+(https://sudhir.io/the-big-little-guide-to-message-queues/)
+If you have every [View Highlight](https://read.readwise.io/read/01j59rfbd66tv18q7vdpc0brt3))
+
--- a/_master_wiki/void/Readwise/A
+++ b/_master_wiki/void/Readwise/A
@ -0,0 +1,35 @@
+# A Successful Git Branching Model
+
+![rw-book-cover](http://nvie.com/img/git-model@2x.png)
+
+## Metadata
+- Author: [[Vincent Driessen]]
+- Full Title: A Successful Git Branching Model
+- Category: #articles
+- URL: https://nvie.com/posts/a-successful-git-branching-model/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=A%20Successful%20Git%20Branching%20Model
+> [!tldr]
+> The Git branching model, git-flow, is widely used but can be seen as overly rigid by some teams. It is beneficial for versioned software and managing multiple versions. Git has revolutionized how developers handle branching and merging in version control.
+
+## Highlights
+If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like [GitHub flow](https://guides.github.com/introduction/flow/)) instead of trying to shoehorn git-flow into your team.
+If, however, you are building software that is explicitly versioned, or if you need to support multiple versions of your software in the wild, then git-flow may still be as good of a fit to your team as it has been to people in the last 10 years. [View Highlight](https://read.readwise.io/read/01j548q3y82vb6tgpcxkff732r))
+
+We consider `origin/master` to be the main branch where the source code of `HEAD` always reflects a *production-ready* state. [View Highlight](https://read.readwise.io/read/01j548s6wn5tww0q86agt4mc3b))
+
+We consider `origin/develop` to be the main branch where the source code of `HEAD` always reflects a state with the latest delivered development changes for the next release. Some would call this the “integration branch”. This is where any automatic nightly builds are built from. [View Highlight](https://read.readwise.io/read/01j548sbx0chxzjqhbdxbfkd34))
+
+Next to the main branches `master` and `develop`, our development model uses a variety of supporting branches to aid parallel development between team members, ease tracking of features, prepare for production releases and to assist in quickly fixing live production problems. Unlike the main branches, these branches always have a limited life time, since they will be removed eventually.
+The different types of branches we may use are:
+• Feature branches
+• Release branches
+• Hotfix branches [View Highlight](https://read.readwise.io/read/01j548v29py8ken2hnj4kqn7d4))
+
+Feature branches (or sometimes called topic branches) are used to develop new features for the upcoming or a distant future release. When starting development of a feature, the target release in which this feature will be incorporated may well be unknown at that point. The essence of a feature branch is that it exists as long as the feature is in development, but will eventually be merged back into `develop` (to definitely add the new feature to the upcoming release) or discarded (in case of a disappointing experiment). [View Highlight](https://read.readwise.io/read/01j548xe9jrd2c98pd2kch582r))
+
+The `--no-ff` flag causes the merge to always create a new commit object, even if the merge could be performed with a fast-forward. This avoids losing information about the historical existence of a feature branch and groups together all commits that together added the feature. Compare: [View Highlight](https://read.readwise.io/read/01j548z6jfdzegbyxqcbw9qzg8))
+
+Release branches support preparation of a new production release. __They allow for last-minute dotting of i’s and crossing t’s. Furthermore, they allow for minor bug fixes and preparing meta-data for a release__ (version number, build dates, etc.). By doing all of this work on a release branch, the `develop` branch is cleared to receive features for the next big release. [View Highlight](https://read.readwise.io/read/01j54919d0891s3web647x0zkt))
+
+Hotfix branches are very much like release branches in that they are also meant to prepare for a new production release, albeit unplanned. __They arise from the necessity to act immediately upon an undesired state of a live production version__. When a critical bug in a production version must be resolved immediately, a hotfix branch may be branched off from the corresponding tag on the master branch that marks the production version. [View Highlight](https://read.readwise.io/read/01j5498mt0tq7m5y0gk06rst3t))
+
--- a/_master_wiki/void/Readwise/A
+++ b/_master_wiki/void/Readwise/A
@ -0,0 +1,35 @@
+# A guide to design tokens
+
+![rw-book-cover](https://s3.amazonaws.com/www-inside-design/uploads/2021/06/design-tokens-7-1-810x810.png)
+
+## Metadata
+- Author: [[invisionapp.com]]
+- Full Title: A guide to design tokens
+- Category: #articles
+- Document Tags: [[design]] [[dev]] 
+- URL: https://www.invisionapp.com/inside-design/design-tokens/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=A%20guide%20to%20design%20tokens
+> [!tldr]
+> Design tokens help ensure consistency across different platforms by managing design properties from a single source. They are defined pairs of code and visual properties, like colors and spacing, that can be easily deployed. By using design tokens, teams can streamline updates and maintain a cohesive brand identity without confusion.
+
+## Highlights
+if you established a new data layer on top of your existing design elements ... and managed them from a single place, you could use a system to consistently scale it to all platforms.
+
+Essentially, a design token is a design decision: a pairing of the same code and visual properties—design elements you use over and over again in your products—packaged in a format that’s deployable across all platforms. [View Highlight](https://read.readwise.io/read/01j7gb6cqqmf343z3g33y56jkb))
+
+Each token will be given **a name** that corresponds to a certain design decision/option and the defined **value.** [View Highlight](https://read.readwise.io/read/01j7gbesf4pcyz7va8f288kq2j))
+
+are an abstraction layer that makes them **platform-agnostic**. [View Highlight](https://read.readwise.io/read/01j7gbf531ycxc49212f6p6f1r))
+
+Before any coding is implemented in DSM or your SSoT, designers and developers must agree on:
+• What should be a token
+• How those tokens will be used
+• How those tokens will be named [View Highlight](https://read.readwise.io/read/01j7gbjas3kb8h0szhxkkj6rss))
+
+For ease of use, it’s recommended to use Category/Type/Item (CTI) naming conventions to define tokens in a hierarchical tree structure of options and decisions. [View Highlight](https://read.readwise.io/read/01j7gbmfh2rzgrx74f36r0f8s6))
+> [!note]
+> This seems like a good way to categorize pretty much anything
+
+Alias tokens create a hierarchy of options and decisions to control the scope, or intent, of changes. So let’s say you wanted to just change the background color on the buttons. You can create an alias token that reads as an inheritance from the global token as such:
+Using the earlier alias example – color.background.button.primary – the ‘category’ would be ‘color’. Moving down the tree the ‘type’ would be ‘background,’ followed by ‘button’ as the ‘item.’ [View Highlight](https://read.readwise.io/read/01j7gbshpy8mqhasnve88440mw))
+
--- a/_master_wiki/void/Readwise/ACID
+++ b/_master_wiki/void/Readwise/ACID
@ -0,0 +1,24 @@
+# ACID Databases – Atomicity, Consistency, Isolation & Durability Explained
+
+![rw-book-cover](https://www.freecodecamp.org/news/content/images/2024/01/cover-fcc.png)
+
+## Metadata
+- Author: [[Daniel Adetunji]]
+- Full Title: ACID Databases – Atomicity, Consistency, Isolation & Durability Explained
+- Category: #articles
+- URL: https://www.freecodecamp.org/news/acid-databases-explained/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=ACID%20Databases%20%E2%80%93%20Atomicity%2C%20Consistency%2C%20Isolation%20%26%20Durability%20Explained
+> [!tldr]
+> ACID (Atomicity, Consistency, Isolation, and Durability) is a set of guarantees provided by database management systems (DBMS). While most popular DBMS offer ACID guarantees, the implementation can vary. Atomicity ensures that all parts of a transaction are completed or none at all. Consistency, or referential integrity, ensures data accuracy and reliability. Isolation guarantees that concurrent transactions do not interfere with each other. Durability ensures that changes made by committed transactions are not lost. These properties are important for maintaining data integrity and fault tolerance in a DBMS.
+
+## Highlights
+Consistency in the context of ACID means *consistency in data*, which is defined by the creator of the database. The technical term for consistency in data is called referential integrity. __Referential integrity is a method of ensuring that relationships between tables remain consistent__. It's usually enforced through the use of **foreign keys**. [View Highlight](https://read.readwise.io/read/01j549yzv6a3s4x73cc7qj06rg))
+
+Isolation is a guarantee that concurrently running transactions should not interfere with each other. Concurrency here refers to two or more transactions trying to modify or read the same database record(s) at the same time. [View Highlight](https://read.readwise.io/read/01j54a1g3dka9smm3v4ct09v4d))
+
+In this example, read committed isolation ensures that Marie is not prematurely excluded from buying the burger just because someone else said they wanted it. __Only committed transactions can be read__. Therefore, the burger is available to be ordered as long as no one has paid for it. [View Highlight](https://read.readwise.io/read/01j54a6t2df5kjvy8q4tyhkwas))
+
+A repeatable read guarantees that if a transaction reads a row of data, any subsequent reads of that same row of data within the same transaction will yield the same result, regardless of changes made by other transactions. This consistency is maintained throughout the duration of the transaction. [View Highlight](https://read.readwise.io/read/01j54a7baf7scbgptfwf5a5hgf))
+
+Durability is a guarantee that changes made by a committed transaction must not be lost. All committed transactions must be persisted on durable, non-volatile storage, that is on disk. This ensures that any committed transactions are protected even if the database crashes. [View Highlight](https://read.readwise.io/read/01j54aa01whthekb1jegqsx42w))
+
--- a/_master_wiki/void/Readwise/APCA
+++ b/_master_wiki/void/Readwise/APCA
@ -0,0 +1,25 @@
+# APCA in a Nutshell
+
+![rw-book-cover](https://git.myndex.com/images/APCAresourcesTheWorldIsReading.png)
+
+## Metadata
+- Author: [[APCA]]
+- Full Title: APCA in a Nutshell
+- Category: #articles
+- Document Tags: [[design]] 
+- URL: https://git.apcacontrast.com/documentation/APCA_in_a_Nutshell#use-case--size-ranges
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=APCA%20in%20a%20Nutshell
+> [!tldr]
+> The Accessible Perceptual Contrast Algorithm (APCA) is a new method for measuring color contrast and improving readability on screens. It provides a more accurate way to assess contrast than the existing WCAG guidelines, focusing on user needs and different text sizes. APCA includes various levels of contrast to help designers create more accessible content, especially for body text and large elements.
+
+## Highlights
+Use-Case & Size Ranges
+These general levels are appropriate for use by themselves, without the need to reference a lookup table. APCA reports contrast as an Lc value (lightness contrast) from **Lc 0** to **Lc 105+**. For accessibility, consider Lc 15 the point of invisibility for many users, and Lc 90 as preferred for body text.
+• **Lc 90** • Preferred level for fluent text and columns of body text with a font no smaller than 18px/weight 300 or 14px/weight 400 (normal), or non-body text with a font no smaller than 12px/400. Also a recommended minimum for extremely thin fonts with a minimum of 24px at weight 200. Lc 90 is a *suggested maximum* for **very large and bold fonts** (greater than 36px bold), and large areas of color. Small fonts do not have a maximum.
+• **Lc 75** • The *minimum* level for columns of body text with a font no smaller than 24px/300 weight, 18px/400, 16px/500 and 14px/700. This level may be used with non-body text with a font no smaller than 15px/400. Also, Lc 75 should be considered a minimum for larger for any larger text where readability is important.
+• **Lc 60** • The *minimum* level recommended for content text that is not body, column, or block text. In other words, text you want people to read. The minimums: no smaller than 48px/200, 36px/300, 24px normal weight (400), 21px/500, 18px/600, 16px/700 (bold). These values based on the reference font Helvetica. To use these sizes as body text, add Lc 15.
+• **Lc 45** • The *minimum* for larger, heavier text (36px normal weight or 24px bold) such as headlines, and large text that should be fluently readable but is not body text. This is also the minimum for pictograms with fine details, or smaller outline icons.
+• **Lc 30** • The *absolute minimum* for any text not listed above, including text considered as “spot readable”. This includes placeholder text and disabled element text, and some non-content like a copyright bug. This is also the minimum for large/solid semantic & understandable non-text elements such as “mostly solid” icons or pictograms. Generally no less than 5.5px solid in its smallest dimension.
+• **Lc 15** • The *absolute minimum* for any non-semantic non-text that needs to be *discernible*, and is no less than 5px (solid) in its smallest dimension. This may include dividers, and in *some* cases large buttons or thick focus-visible outlines, but does *not* include fine details which have a higher minimum. **Designers should treat anything below this level as invisible**, as it will not be visible for many users. This minimum level should be avoided for any items important to the use, understanding, or interaction of the site.
+These define the basic minimum levels, what you might think of as AA in the old WCAG 2. For the equivelent to AAA, simply increase the contrast values by Lc 15. [View Highlight](https://read.readwise.io/read/01j80shgn3ccehc3qxw0at9gsz))
+
--- a/_master_wiki/void/Readwise/All
+++ b/_master_wiki/void/Readwise/All
@ -0,0 +1,32 @@
+# All You Need Is Data and Functions
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article1.be68295a7e40.png)
+
+## Metadata
+- Author: [[mckayla.blog]]
+- Full Title: All You Need Is Data and Functions
+- Category: #articles
+- Document Tags: [[dev]] [[star]] 
+- URL: https://mckayla.blog/posts/all-you-need-is-data-and-functions.html
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=All%20You%20Need%20Is%20Data%20and%20Functions
+
+> [!note]
+> **Background:** I would like to implement the ideas from "All you need is data and functions" by mckayla.blog in my programming project.
+> ### Key Takeaways:
+> 🛠️ **Emphasize Type Over Traits:** Instead of relying on traits, create a data-type that encapsulates the desired behavior. Then, implement a conversion function to transform your data-type into the trait-type when needed.
+> 🔄 **Utilize Implicit Conversions:** Understand that trait-types allow for implicit conversions, which can simplify your code. This means the language can handle the transformation from your data-type to the trait-type automatically, reducing boilerplate and improving readability.
+> 📜 **Represent Traits with Types:** Recognize that traits can be viewed as types themselves. For example, a Display trait can be represented by a String type alongside a function that converts your original type into a String, enabling clearer and more direct handling of type-specific logic.
+> ---
+> 1. How does the omission of traits in Gleam influence the way developers approach generic programming compared to languages like Rust?
+> 2. In what ways might the simplicity of Gleam's design, focusing on data and functions, lead to both advantages and disadvantages in software development?
+> 3. How does Gleam's approach to immutability and function-based programming compare with the mutable state and trait systems commonly found in other languages?
+> [!tldr]
+> The document explores the concept of traits in programming languages, using the example of the Gleam language. Traits are compared to types and functions, emphasizing how traits can be represented and achieved through types and functions. The discussion covers examples from Rust and Gleam to illustrate how traits can be replaced by types and functions in a language like Gleam, where simplicity and low concept count are valued. The document concludes that data and functions can effectively replace the need for traits, particularly in languages like Gleam.
+
+## Highlights
+**traits are just types**. Our `Display` trait in this example, can be represented by the `String` type, and a function which converts from our original type to a `String`. [View Highlight](https://read.readwise.io/read/01j6axgxbj76x7jbz4zsc45tdv))
+
+The biggest difference between most trait/interface systems and trait-types is that the language is essentially doing implicit conversions for you, from your data-type to the trait-type. [View Highlight](https://read.readwise.io/read/01j6ccvpskph772e8r479esbq4))
+
+Instead of a trait, just make a type that implements the generic behavior you want, and then write a function to convert your data-type into your trait-type. If you need some data-type specific logic, then pass around functions as necessary (usually from your conversion function). [View Highlight](https://read.readwise.io/read/01j6ccz00s0t2aydshas3xw962))
+
--- a/_master_wiki/void/Readwise/Best
+++ b/_master_wiki/void/Readwise/Best
@ -0,0 +1,41 @@
+# Best Practices for Maintainers
+
+![rw-book-cover](https://opensource.guide/assets/images/cards/best-practices.png)
+
+## Metadata
+- Author: [[Open Source Guides]]
+- Full Title: Best Practices for Maintainers
+- Category: #articles
+- Document Tags: [[dev]] 
+- URL: https://opensource.guide/best-practices/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Best%20Practices%20for%20Maintainers
+> [!tldr]
+> Maintaining a popular open source project involves more than just coding; it requires effective communication and managing contributions. It's important to set clear expectations for your time and the types of contributions you accept, while also being kind and responsive to contributors. Taking breaks and prioritizing your own happiness is essential for the long-term success of the project.
+
+## Highlights
+Written and enforced fairly, however, good rules empower maintainers. They prevent you from getting dragged into doing things you don’t want to do. [View Highlight](https://read.readwise.io/read/01j59endsw1rpkb9tf8m8qawvj))
+
+Don’t forget to document your interactions, too. Wherever you can, keep communication about your project public. If somebody tries to contact you privately to discuss a feature request or support need, politely direct them to a public communication channel, such as a mailing list or issue tracker. [View Highlight](https://read.readwise.io/read/01j59eq13dn3wga93d01tnfqmy))
+
+Having everything written down, however, helps depersonalize situations when you do need to enforce your rules.
+Saying no isn’t fun, but *“Your contribution doesn’t match this project’s criteria”* feels less personal than *“I don’t like your contribution”*. [View Highlight](https://read.readwise.io/read/01j59eskv2qw7f8cfrkz5g3rvt))
+
+The key to handling support for large-scale open source projects is to keep issues moving. Try to avoid having issues stall. If you’re an iOS developer you know how frustrating it can be to submit radars. You might hear back 2 years later, and are told to try again with the latest version of iOS. [View Highlight](https://read.readwise.io/read/01j59ezaxynf5z61amr95w7x7m))
+
+I cater to the 80% use case. If you are one of the unicorns, please fork my work. I won’t get offended! My public projects are almost always meant to solve the most common problems; I try to make it easy to go deeper by either forking my work or extending it. [View Highlight](https://read.readwise.io/read/01j59ftzzkh4m5fkbbgse1qs8y))
+
+It’s almost inevitable that once a project becomes big, maintainers have to become a lot more conservative about how they introduce new code. You become good at saying “no”, but a lot of people have legitimate needs. So, instead you end up converting your tool into a platform. [View Highlight](https://read.readwise.io/read/01j59fw4nd6sjdfxwtxgbn89zy))
+
+I believe that tests are necessary for all code that people work on. If the code was fully and perfectly correct, it wouldn’t need changes – we only write code when something is wrong, whether that’s “It crashes” or “It lacks such-and-such a feature”. And regardless of the changes you’re making, tests are essential for catching any regressions you might accidentally introduce. [View Highlight](https://read.readwise.io/read/01j59fyszkgtfzj58msft420j5))
+
+There are a [variety of tools available](https://github.com/showcases/tools-for-open-source) to help automate some aspects of maintenance work. A few examples:
+• [semantic-release](https://github.com/semantic-release/semantic-release) automates your releases
+• [mention-bot](https://github.com/facebook/mention-bot) mentions potential reviewers for pull requests
+• [Danger](https://github.com/danger/danger) helps automate code review
+• [no-response](https://github.com/probot/no-response) closes issues where the author hasn’t responded to a request for more information
+• [dependabot](https://github.com/dependabot) checks your dependency files every day for outdated requirements and opens individual pull requests for any it finds [View Highlight](https://read.readwise.io/read/01j59g05hnrn42hj1ey8s0cjhe))
+
+Burnout is a real and pervasive issue in open source work, especially among maintainers. As a maintainer, your happiness is a non-negotiable requirement for the survival of any open source project. [View Highlight](https://read.readwise.io/read/01j59g44y47gfp6bexny1cf077))
+
+In maintaining WP-CLI, I’ve discovered I need to make myself happy first, and set clear boundaries on my involvement. The best balance I’ve found is 2-5 hours per week, as a part of my normal work schedule. This keeps my involvement a passion, and from feeling too much like work. Because I prioritize the issues I’m working on, I can make regular progress on what I think is most important. [View Highlight](https://read.readwise.io/read/01j59g63w7h9j6krg5wpjh40ap))
+
--- a/_master_wiki/void/Readwise/Building
+++ b/_master_wiki/void/Readwise/Building
@ -0,0 +1,39 @@
+# Building a Second Brain - Tags
+
+![rw-book-cover](https://m.media-amazon.com/images/I/71jhK9zsKEL.jpg)
+
+## Metadata
+- Author: [[Tiago Forte]]
+- Full Title: Building a Second Brain - Tags
+- Category: #articles
+- Document Tags: [[notetaking]] [[productivity]] 
+- URL: https://readwise.io/reader/document_raw_content/2217137
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Building%20a%20Second%20Brain%20-%20Tags
+> [!tldr]
+> Creating a universal tagging system for notes is impractical and can lead to frustration. Instead, tags should be used to track the progress and purpose of notes, focusing on actionable use cases. Start small with simple organization methods and apply tags retroactively as needed to maintain clarity and motivation.
+
+## Highlights
+The goal of all these endeavors was to create a system of classification – known as a “taxonomy” – that every piece of knowledge could be placed into. [View Highlight](https://read.readwise.io/read/01j6hh4c8747s1xrb59f93826q))
+
+Like Pandora’s Box, once we begin to apply tags it can be incredibly tempting to start labeling each and every note ... Building a Second Brain: Chapter 11 | buildingasecondbrain.com understand what we are trying to use our notes to accomplish to avoid the trap of “tagging for the sake of tagging.”
+
+There are three practical approaches to tagging you can use as your Second Brain grows and matures. Each one follows the principle of actionability and answers an important question about the purpose of a given note: 1. Create personalized tags for your use cases. (How will my notes be used?) 2. Use tags to track the progress of notes. (How are my notes currently being used?) 3. Tag notes retroactively and only as needed. (How have my notes been used?) [View Highlight](https://read.readwise.io/read/01j6hhjytn42dbdcgskyjrr74q))
+
+if you already know how your notes are likely to be used – such as for citations in a paper [Source], as evidence in a trial [Evidence], or as slides in a presentation [Slides] – it can be helpful to tag your notes according to those use cases. [View Highlight](https://read.readwise.io/read/01j6hhp4pghcnk2r4z4r95n287))
+
+Ask yourself, “What are the most common use cases for the content I capture?” Here are a couple common examples: • Tagging according to the final product a note will be used in: [Presentation], [Essay], [Report], [Website], [Project plan], [Meeting agenda], or [Budget]
+• Tagging according to the kind of information a note contains: [Arguments], [Theories], [Frameworks], [Evidence], [Claim], [Counterpoint], or [Question] [View Highlight](https://read.readwise.io/read/01j6hhwgwga3a4t0bm9p3t12y6))
+
+tags to track the progress of their notes: • Tagging according to its role in a project: [Meeting notes], [Timeline], [Budget], [Decision], [Action], [Idea], or [Objective]
+• Tagging according to the current stage of their workflow: [Planned], [In process], [Waiting for approval], [Reviewed], [Approved], [On hold], or [Finished] [View Highlight](https://read.readwise.io/read/01j6hj21kk7kmc7c4f40hg3004))
+
+These kinds of tags aren’t about the contents of a note. They are about its context – specifically, the context in which it is being used. Since [View Highlight](https://read.readwise.io/read/01j6hj2t79v8mg6rey564bm350))
+
+We didn’t want to move her existing notes from their respective PARA folders, but we did want to be able to see all the notes related to “writing job descriptions” or “reviewing applications” in one place with a quick search. This is the perfect situation for tags: when you want a different way of “viewing” your notes, without having to [View Highlight](https://read.readwise.io/read/01j6hj859j9vyq735n7t634791))
+
+Building a Second Brain: Chapter 11 | buildingasecondbrain.com undertake a massive reorganization of your entire system. [View Highlight](https://read.readwise.io/read/01j6hj84vq0hfy5rtaxw7nk0wa))
+
+Instead of applying tags when you first capture content, I recommend applying them when it’s time to use it. Often, the ideal moment is when you are getting ready to start a new project. When you apply tags with a specific use case in mind, the tags you come up with will be far more concrete and actionable. And you will have the motivation to do the work of adding them because of the immediate needs of the project you are taking on. [View Highlight](https://read.readwise.io/read/01j6hjb00pwcgt92e9ek7ad2p7))
+
+using tags in this way means it’s perfectly fine to skip adding tags altogether if you don’t feel like it. ... This eliminates the frustrating experience of trying to force yourself to think of a tag for a note, even when nothing comes to mind, because you fear that otherwise it will be lost forever. Even if no tags are applied, the note will always be right in the folder where you left it.
+
--- a/_master_wiki/void/Readwise/Caching
+++ b/_master_wiki/void/Readwise/Caching
@ -0,0 +1,38 @@
+# Caching vs Content Delivery Networks – What's the Difference?
+
+![rw-book-cover](https://www.freecodecamp.org/news/content/images/2024/02/Conducting-Research-Projects-Educational-Presentation-in-Pink-and-Yellow-Colorful-Line-Style-1.jpg)
+
+## Metadata
+- Author: [[anamika.ahmed.792]]
+- Full Title: Caching vs Content Delivery Networks – What's the Difference?
+- Category: #articles
+- URL: https://www.freecodecamp.org/news/caching-vs-content-delivery-network/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Caching%20vs%20Content%20Delivery%20Networks%20%E2%80%93%20What%27s%20the%20Difference%3F
+> [!tldr]
+> In the world of network optimization, Content Delivery Networks (CDNs) and caching are essential for enhancing website performance and user experience. Caching involves temporarily storing frequently accessed data to reduce response times, while CDNs use a network of servers to deliver web content more efficiently. Both methods aim to improve performance, optimize resource utilization, and enhance user experience. Caching is ideal for frequently accessed static content, while CDNs excel at delivering content globally, especially dynamic content and media. Combining caching and CDNs can offer optimal results, particularly for websites with a mix of static and dynamic content.
+
+## Highlights
+Caching is a technique used to store copies of frequently accessed data temporarily. The cached data can be anything from web pages and images to database query results. When a user requests cached content, the server retrieves it from the cache instead of generating it anew, significantly reducing response times. [View Highlight](https://read.readwise.io/read/01j5rvjkrkd34kjh984axnab87))
+
+What to Consider When Implementing a Cache SystemDecide When to Use a Cache:
+• A cache is best for frequently read but infrequently modified data.
+• Cache servers are not suitable for storing critical data as they use volatile memory.
+• Important data should be stored in persistent data stores to prevent loss in case of cache server restarts. [View Highlight](https://read.readwise.io/read/01j5rvj1mdcbaqnj0e9n2vnw3v))
+
+In technical terms, a CDN is a network of servers distributed across various locations globally. Its primary purpose is to deliver web content, such as images, videos, scripts, and stylesheets to users more efficiently by reducing the physical distance between the server and the user. [View Highlight](https://read.readwise.io/read/01j5rvrwx5kh2fpqwfpnvxeqd9))
+
+What to Consider When Implementing a CDN
+• **Cost Management**: CDNs charge for data transfers. It’s wise to cache frequently accessed content, but not everything.
+• **Cache Expiry**: Set appropriate cache expiry times. Too long, and content might be stale. Too short, and it strains origin servers.
+• **CDN Fallback**: Plan for CDN failures. Ensure your website can switch to fetching resources directly from the origin if needed.
+• **Invalidating Files**: You can remove files from the CDN before they expire using various methods provided by CDN vendors. [View Highlight](https://read.readwise.io/read/01j5rvvgawfs37758cbyyz9g69))
+
+In fact, studies show that CDNs can ****reduce video startup time by up to 50%****, making a significant difference in user satisfaction. [View Highlight](https://read.readwise.io/read/01j5rvxqm29rk1kwr36j6m9nmp))
+
+Caching is ideal for frequently accessed content that doesn't change frequently. This includes static assets like images, CSS files, and JavaScript libraries.
+It's particularly effective for websites with a substantial user base accessing similar content, such as news websites, blogs, and e-commerce platforms. [View Highlight](https://read.readwise.io/read/01j5rw4q49kh725b3er30axw9q)) [[dev]] [[favorite]] 
+
+CDNs are invaluable for delivering content to a global audience, especially when geographical distance between users and origin servers leads to latency issues.
+They are well-suited for serving dynamic content, streaming media, and handling sudden spikes in traffic.
+CDNs also excel in scenarios where content needs to be delivered reliably and consistently across diverse geographic regions, ensuring optimal user experience regardless of location. [View Highlight](https://read.readwise.io/read/01j5rw5x54n9bs6qg1mygc0vd9))
+
--- a/_master_wiki/void/Readwise/Code-Splitting
+++ b/_master_wiki/void/Readwise/Code-Splitting
@ -0,0 +1,37 @@
+# Code-Splitting for Libraries—bundling for NPM With Rollup 1.0
+
+![rw-book-cover](https://miro.medium.com/v2/resize:fit:1200/1*BZ4p60HENosEjyZfQgjsRQ.jpeg)
+
+## Metadata
+- Author: [[Lukas Taegert]]
+- Full Title: Code-Splitting for Libraries—bundling for NPM With Rollup 1.0
+- Category: #articles
+- Document Tags: [[dev]] [[dev/javascript]] 
+- URL: https://levelup.gitconnected.com/code-splitting-for-libraries-bundling-for-npm-with-rollup-1-0-2522c7437697
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Code-Splitting%20for%20Libraries%E2%80%94bundling%20for%20NPM%20With%20Rollup%201.0
+> [!tldr]
+> Rollup 1.0 introduces code-splitting as a key feature for bundling JavaScript libraries. The article explains how to create an efficient library called "fancy-case" that allows users to import specific utility functions while offering multiple formats for different environments. It highlights the benefits of using ES modules and provides guidance on configuring Rollup for optimal performance.
+
+## Highlights
+CommonJS module for Node
+This is probably the most important target. This allows Node users and legacy bundlers to import your library as a [CommonJS module](http://wiki.commonjs.org/wiki/Modules/1.1.1) via [View Highlight](https://read.readwise.io/read/01j864mhazhr25k1zh6ngzn2x8))
+
+Single bundle to be used in a script tag
+The “traditional way” of distributing JavaScript may still be interesting for small, hand-crafted sites with minimal setup. The bundle creates a global variable via which its exports can be accessed. [View Highlight](https://read.readwise.io/read/01j864mcsdtwp63pehyqf3cex6))
+
+AMD module to be used with an AMD loader
+There are still quite a few [AMD/RequireJS](https://requirejs.org/) based projects out there. We can distribute a file that can itself be used as a dependency of an AMD module. [View Highlight](https://read.readwise.io/read/01j864mvbta1gpk2n5rptm0m5z))
+
+ES module for modern bundlers
+[ECMAScript modules](http://exploringjs.com/es6/ch_modules.html) are now the official, standardized JavaScript module format. [View Highlight](https://read.readwise.io/read/01j864n23372ch1nkz5xrxwqp2))
+
+Direct imports for CJS or ESM consumers
+An emerging new pattern especially for libraries with many independent utility functions is to allow users to import independent parts of the library from separate files. Node users could write
+const upper = require(**'fancy-case/cjs/upper'**); 
+console.log(upper('some Text'));
+while ESM consumers could write
+import upper from **'fancy-case/esm/upper'**; 
+console.log(upper('some Text')); [View Highlight](https://read.readwise.io/read/01j864p33y06v43pdzwxrgksxg))
+
+Rollup supports a special output format called a [“Universal Module Definition”](https://github.com/umdjs/umd), which simultaneously supports the CJS, script tag, and ESM use cases. To create it, add a new file called `rollup.config.js` to the root of your project [View Highlight](https://read.readwise.io/read/01j864rhxg10v4kb7fnf2a869x))
+
--- a/_master_wiki/void/Readwise/Coding
+++ b/_master_wiki/void/Readwise/Coding
@ -0,0 +1,21 @@
+# Coding and ADHD - ADHD Brains
+
+![rw-book-cover](https://res.cloudinary.com/practicaldev/image/fetch/s--BliSrKEI--/c_imagga_scale,f_auto,fl_progressive,h_500,q_auto,w_1000/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ri1ahc6zfstekngl1ejg.png)
+
+## Metadata
+- Author: [[DEV Community 👩‍💻👨‍💻]]
+- Full Title: Coding and ADHD - ADHD Brains
+- Category: #articles
+- URL: https://dev.to/abbeyperini/coding-and-adhd-adhd-brains-im1
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Coding%20and%20ADHD%20-%20ADHD%20Brains
+> [!tldr]
+> The author shares their experience of having ADHD and how it affects their coding abilities. They describe struggles with focus and attention but also highlight the excitement and stimulation coding provides. The piece will explore strategies for managing ADHD challenges in programming while acknowledging the potential benefits of ADHD in a development role.
+
+## Highlights
+Rather than "Attention-Deficit," it should be called something like "Attention-Regulation" or "Executive Function" / Hyperactivity Disorder. [View Highlight](https://read.readwise.io/read/01j9ynfj6cn6zz3nf53v9t6g6z))
+
+novelty [View Highlight](https://read.readwise.io/read/01j9ynk79n34t53r0qkb6de9w1))
+> [!note]
+> Novelty: The quality of being new, original, or unusual, often evoking interest or excitement. In psychology and marketing, novelty is associated with the human desire for variety and stimulation, influencing behavior and preferences. Novelty can enhance experiences, making them more memorable and enjoyable, as well as motivating individuals to seek out new products, ideas, or experiences. In various contexts, such as art, technology, and consumer goods, novelty plays a key role in innovation and cultural trends.
+> In the context of "Coding and ADHD - ADHD Brains," the term "novelty" refers to the appeal of new and interesting challenges that stimulate the brains of individuals with ADHD. This drive for novelty helps such individuals engage deeply with coding, as they are often drawn to the constant learning and problem-solving that comes with tackling new tasks. The pursuit of novel experiences can lead to significant achievements, but it also contributes to a tendency to start many projects without finishing them.
+
--- a/_master_wiki/void/Readwise/Currying
+++ b/_master_wiki/void/Readwise/Currying
@ -0,0 +1,20 @@
+# Currying - Writing Sophisticated Functional Code
+
+![rw-book-cover](https://i.ytimg.com/vi/Q01LEKKrTmA/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Coding with Yalco]]
+- Full Title: Currying - Writing Sophisticated Functional Code
+- Category: #articles
+- URL: https://www.youtube.com/watch?v=Q01LEKKrTmA
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Currying%20-%20Writing%20Sophisticated%20Functional%20Code
+> [!tldr]
+> #FunctionalProgramming #Coding #Programming
+
+In this video, we look at one of the representative techniques of functional programming, currying. Currying is a coding method that breaks down tasks that should be performed at once into multiple stages. To explain this, we use a function that makes a sandwich as an example, where a traditional function handles the three ingredients (bread, meat, vegetables) of a sandwich all at once, but Currying divides this process into each ingredient, or argument. This allows for the execution of functions in divided stages. By doing this, one advantage is that the original process can be diversely branched into multiple stages and branches for each ingredient. This video provides a detailed code example and explanation of this. In the next video, we're going to look at monads, one of the most challenging topics in functional programming.
+
+## Highlights
+Currying is a coding method that  allows you to break down tasks that   used to be done at once into multiple steps [View Highlight](https://read.readwise.io/read/01j9rca7zb81g8vzbx7n2xj22e))
+
+A function created with  Currying executes like this.  As you can see, it gets executed  individually as many times as the number   of arguments the original function had. [View Highlight](https://read.readwise.io/read/01j9rcc05k5d11mf16szvrs8y3))
+
--- a/_master_wiki/void/Readwise/Dependency
+++ b/_master_wiki/void/Readwise/Dependency
@ -0,0 +1,22 @@
+# Dependency Injection, the Best Pattern
+
+![rw-book-cover](https://i.ytimg.com/vi/J1f5b4vcxCQ/maxresdefault.jpg)
+
+## Metadata
+- Author: [[CodeAesthetic]]
+- Full Title: Dependency Injection, the Best Pattern
+- Category: #articles
+- URL: https://www.youtube.com/watch?v=J1f5b4vcxCQ
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Dependency%20Injection%2C%20the%20Best%20Pattern
+> [!tldr]
+> The text explains how to use dependency injection to build an attachment service that uploads files. By creating an interface for storage and injecting it into the request handler, the code becomes simpler and less error-prone. This approach also allows for easy testing with mock implementations.
+
+## Highlights
+have a piece of code which uses another piece of code, and instead of using that code directly, it's passed in instead. [View Highlight](https://read.readwise.io/read/01j8b4fbn7xc4day63pshpds1t))
+
+Injection basically just lets us pick and choose from our compatible puzzle pieces and then slot them in when we need them. [View Highlight](https://read.readwise.io/read/01j8b51ysp8pj6g1sk4cc94qzp))
+
+We can use injection to inject fake or mock implementations instead, which basically means we can slice and dice up our architecture to isolate sections of code during testing. [View Highlight](https://read.readwise.io/read/01j8b54d9xcz7p57m37apc92xm))
+
+A natural side effect of having nice code is that it's easy to test without needing to hack around the code structure. If you find yourself asking, how can I test a private method? Or I need to set some internal variable in order to test. That's a signal that you maybe need to pull some stuff out, that you need to isolate some part of it by separating it and injecting it instead. [View Highlight](https://read.readwise.io/read/01j8b57129cky28vhfsq2fd38y))
+
--- a/_master_wiki/void/Readwise/Design
+++ b/_master_wiki/void/Readwise/Design
@ -0,0 +1,31 @@
+# Design Systems 101: What Is a Design System?
+
+![rw-book-cover](https://cdn.sanity.io/images/599r6htc/localized/f88e32e02cb892585c56edd61a160822fd134a5e-1200x630.png?w=1200&q=70&fit=max&auto=format)
+
+## Metadata
+- Author: [[Figma]]
+- Full Title: Design Systems 101: What Is a Design System?
+- Category: #articles
+- Document Tags: [[design]] 
+- URL: https://www.figma.com/blog/design-systems-101-what-is-a-design-system/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Design%20Systems%20101%3A%20What%20Is%20a%20Design%20System%3F
+> [!tldr]
+> A design system is a collection of standards and components that ensures consistency and efficiency in digital products. It helps designers work faster by providing reusable elements, allowing them to focus on more complex challenges. Implementing a design system can improve collaboration and streamline workflows across teams, making the design process smoother.
+
+## Highlights
+a design system is a set of building blocks and standards that help keep the look and feel of products and experiences consistent. [View Highlight](https://read.readwise.io/read/01j7gbyb49nhm0t495h8wwakph))
+
+While both are integral to design systems, component libraries focus on UI elements like buttons and input fields, whereas pattern libraries address broader design solutions like navigation flows or data display. [View Highlight](https://read.readwise.io/read/01j7gc0j368sfxwsseakv52kky))
+
+While often used interchangeably, design systems are more holistic, including coding standards and usability, while a style guide is a subset focusing primarily on visual elements like colors, typography, and imagery. [View Highlight](https://read.readwise.io/read/01j7gc2ge1rj1tzkkmz150837e))
+> [!note]
+> Holistic: An approach that considers the entirety of a system or concept rather than focusing on individual components in isolation. In various fields, including medicine, education, and design, holistic perspectives emphasize the interconnectedness and interdependence of elements, advocating for comprehensive solutions that address the whole rather than just parts. This methodology often leads to more effective and sustainable outcomes by recognizing how components influence one another within a larger context.
+> ---
+> Styles guides focus only on visuals meanwhile design systems care about usability as a whole
+
+Design systems support designers by solving for repeatable patterns and freeing them up to solve other challenges. [View Highlight](https://read.readwise.io/read/01j7gd50z8w8q8x5qc40hmx2yk))
+
+![](https://cdn.sanity.io/images/599r6htc/regionalized/876225f41a3f420c161b8b2dc62aa018f88fb73a-1080x864.png?w=390&q=75&fit=max&auto=format&dpr=2) [View Highlight](https://read.readwise.io/read/01j7gdbmnzscxkqtkbjndqecaa))
+
+![](https://cdn.sanity.io/images/599r6htc/regionalized/8843a69171ad6e0d84aa973d3505d6d5045e2b1c-2063x1419.png?w=804&q=75&fit=max&auto=format&dpr=2) [View Highlight](https://read.readwise.io/read/01j7gdbt1d0mvvc58jfhg57t03))
+
--- a/_master_wiki/void/Readwise/Developer
+++ b/_master_wiki/void/Readwise/Developer
@ -0,0 +1,22 @@
+# Developer With ADHD? You’re Not Alone.
+
+![rw-book-cover](https://stackoverflow.blog/wp-content/uploads/2017/03/cropped-SO_Logo_glyph-use-this-one-smaller-32x32.jpg)
+
+## Metadata
+- Author: [[Eira May]]
+- Full Title: Developer With ADHD? You’re Not Alone.
+- Category: #articles
+- URL: https://stackoverflow.blog/2023/12/26/developer-with-adhd-youre-not-alone/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Developer%20With%20ADHD%3F%20You%E2%80%99re%20Not%20Alone.
+> [!tldr]
+> There is a connection between programming and ADHD, as many developers with ADHD feel that their job is a perfect fit for how they think and approach problems. Coding provides the kind of stimulation that ADHD brains crave, and it rewards a state of hyperfocus, which is a symptom of ADHD. However, ADHD can also present challenges such as inattentive mistakes and missed deadlines. It is important to have an open dialogue about ADHD and other forms of neurodiversity in order to combat stigma and create psychologically safe environments in the tech industry.
+
+## Highlights
+Many developers with ADHD feel their job is a perfect fit for how they think and approach problems. “Coding can give ADHD brains exactly the kind of stimulation they crave,” [explains](https://dev.to/abbeyperini/coding-and-adhd-adhd-brains-im1) full-stack developer Abbey Perini. “Not only is coding a creative endeavor that involves constantly learning new things, but also once one problem is solved, there’s always a brand new one to try.” [View Highlight](https://read.readwise.io/read/01j6pxdgk8q9zpq1a1dmjf050g))
+
+coding can reward and encourage a state of [hyperfocus](https://health.clevelandclinic.org/hyperfocus-and-adhd/): a frequently cited symptom of ADHD that developer [Neil Peterson](https://adapthd.com/topics/coping-strategies/programming-with-adhd-the-good-the-bad-and-the-hyperfocus/) calls “a state of laser-like concentration in which distractions and even a sense of passing time seem to fade away.” It’s easy to draw parallels between hyperfocus and the [flow state](https://stackoverflow.blog/2022/09/14/what-science-says-about-flow-state/), a distraction-free groove in which programmers, writers, musicians, artists, and other creators produce their best work (occasionally while forgetting to eat). [View Highlight](https://read.readwise.io/read/01j6pxkb2v38syn1hs3tw6exyk))
+
+ADHD can make people more vulnerable to inattentive mistakes, missed deadlines, or unfinished projects. A perennial question on Reddit is [some variation](https://www.reddit.com/r/learnprogramming/comments/kftc4g/any_programmers_with_adhd/) of “Programmers with ADHD, how do you stay on track?” [View Highlight](https://read.readwise.io/read/01j6pxt1ppawyk5bfb7yqbb4cs))
+> [!note]
+> Inattentive mistakes: Errors that occur when an individual fails to fully focus on a task, often resulting in oversights or miscalculations. These mistakes can stem from distractions, fatigue, or cognitive overload, and are frequently associated with conditions such as Attention Deficit Hyperactivity Disorder (ADHD). Inattentive mistakes may manifest as missed deadlines, incomplete work, or simple errors in judgment, highlighting the importance of attention and concentration in effective task management.
+
--- a/_master_wiki/void/Readwise/Embedded
+++ b/_master_wiki/void/Readwise/Embedded
@ -0,0 +1,17 @@
+# Embedded Rust Setup Explained
+
+![rw-book-cover](https://i.ytimg.com/vi/TOAynddiu5M/maxresdefault.jpg)
+
+## Metadata
+- Author: [[The Rusty Bits]]
+- Full Title: Embedded Rust Setup Explained
+- Category: #articles
+- URL: https://www.youtube.com/watch?v=TOAynddiu5M
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Embedded%20Rust%20Setup%20Explained
+> [!tldr]
+> The video explains how to set up an environment for embedded software development using Rust. It covers installing the Rust toolchain, configuring VS Code, and compiling code for microcontrollers. The tutorial also discusses debugging techniques and tools needed for embedded Rust projects.
+
+## Highlights
+to specify a different Target in Rust C is through a Target triple this is composed of a core and sub architecture an
+optional vendor and or operating system and an environment or AB [View Highlight](https://read.readwise.io/read/01j7qyvme91v6h3mqqva4s9nm6))
+
--- a/_master_wiki/void/Readwise/Five
+++ b/_master_wiki/void/Readwise/Five
@ -0,0 +1,23 @@
+# Five Terminal Applications I Can't Live Without
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article1.be68295a7e40.png)
+
+## Metadata
+- Author: [[DevOps Toolbox]]
+- Full Title: Five Terminal Applications I Can't Live Without
+- Category: #articles
+- Document Tags: [[cli-tools]] 
+- URL: https://omnivore.app/aleidk/five-terminal-applications-i-can-t-live-without-19137768dab
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Five%20Terminal%20Applications%20I%20Can%27t%20Live%20Without
+> [!tldr]
+> We all love the terminal. But what if I told you that some of the most powerful security tools are slo available, right at your fingertips, within your familiar terminal?
+
+## Highlights
+[age](https://click.convertkit-mail2.com/5qulodl26mb7hv6oe4vf6h94xo444tn/qvh8h7hrpoermrbl/aHR0cHM6Ly9naXRodWIuY29tL0ZpbG9Tb3R0aWxlL2FnZQ==) is a simple, modern file encryption tool that’s perfect for quickly securing sensitive data. Whether you’re using keys or passwords, age makes file encryption a breeze. [View Highlight](https://read.readwise.io/read/01j544wrjfxa9s9bfvp3nww6hh)) [[cli-tools]] 
+
+[sshs](https://click.convertkit-mail2.com/5qulodl26mb7hv6oe4vf6h94xo444tn/g3hnh5h3w6g38mhr/aHR0cHM6Ly9naXRodWIuY29tL3F1YW50dW1zaGVlcC9zc2hz) is a terminal user interface for SSH that takes the pain out of managing multiple server connections. It picks up your SSH config and presents your servers in a neat, easy-to-navigate list. [View Highlight](https://read.readwise.io/read/01j544yqsb0j8442d97546tgyy)) [[cli-tools]] 
+
+[atac](https://click.convertkit-mail2.com/5qulodl26mb7hv6oe4vf6h94xo444tn/9qhzhnhprz4pvzc9/aHR0cHM6Ly9naXRodWIuY29tL0p1bGllbi1jcHNuL0FUQUM=) (Arguably a terminal API client) brings the power of Postman to your command line. It’s perfect for testing and debugging API endpoints without leaving your terminal. [View Highlight](https://read.readwise.io/read/01j544zs5250tst193evsrth2c)) [[cli-tools]] 
+
+[portal](https://click.convertkit-mail2.com/5qulodl26mb7hv6oe4vf6h94xo444tn/48hvhehr86wrdwtx/aHR0cHM6Ly9naXRodWIuY29tL1NwYXRpdW1Qb3J0YWUvcG9ydGFs) is a sleek file transfer utility that works in your terminal. It makes sending files between computers secure and straightforward. [View Highlight](https://read.readwise.io/read/01j5450tnt3tjstzyn3tzs4xyx)) [[cli-tools]] 
+
--- a/_master_wiki/void/Readwise/GitHub
+++ b/_master_wiki/void/Readwise/GitHub
@ -0,0 +1,69 @@
+# GitHub - SanderMertens/ecs-faq: Frequently asked questions about Entity Component Systems
+
+![rw-book-cover](https://opengraph.githubassets.com/9f38bac900ccebd3e7025142dc959fe140bdc3ea93f156cb20fc5c1cf7f5b193/SanderMertens/ecs-faq)
+
+## Metadata
+- Author: [[https://github.com/SanderMertens/]]
+- Full Title: GitHub - SanderMertens/ecs-faq: Frequently asked questions about Entity Component Systems
+- Category: #articles
+- Document Tags: [[dev]] [[dev/design-patterns]] 
+- URL: https://github.com/SanderMertens/ecs-faq
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=GitHub%20-%20SanderMertens/ecs-faq%3A%20Frequently%20asked%20questions%20about%20Entity%20Component%20Systems
+> [!tldr]
+> ECS promotes code reusability by separating data from behavior through entities, components, and systems. ECS is a design pattern that can be implemented in various ways with different tradeoffs. Reading existing ECS resources and experimenting with different approaches can help understand and implement ECS applications effectively.
+
+## Highlights
+EC frameworks, as typically found in game engines, are similar to ECS in that they allow for the creation of entities and the composition of components. However, in an EC framework, components are classes that contain both data and behavior, and behavior is executed directly on the component. [View Highlight](https://read.readwise.io/read/01j91jpa60m0gseet7h0ve558p))
+
+users have reported that once ECS "clicked", it made it easier to write, reuse and scale code. [View Highlight](https://read.readwise.io/read/01j91jreb2rx3n0s4kjegsf23p))
+
+Because of its small set of concepts and rules, building a functional ECS is not hard. There are many benefits to building your own, like the freedom to add new features, and only building features that you really need. [View Highlight](https://read.readwise.io/read/01j91jvvay1c66e7124rbpvff6))
+
+Things that ECS implementations are generally good at are querying and iterating sets of entities linearly, or dynamically changing components at runtime. Things that ECS implementations are generally not good at are queries or operations that require highly specialized data structures, such as binary trees or spatial structures. [View Highlight](https://read.readwise.io/read/01j91jx0jh2wn8xrhmzvycyf1w))
+
+The reason for this is that behavior in an ECS is matched with a set of components, vs. for example being tightly coupled with a class in OOP. [View Highlight](https://read.readwise.io/read/01j91jzyev2345b36sy6aphze1))
+
+new systems can be introduced at any stage of development, and will automatically get matched with any existing and new entities that have the right components. [View Highlight](https://read.readwise.io/read/01j91k0jc5vdz6zfysrwvfqezc))
+
+This promotes a design where systems are developed as single-responsibility, small units of functionality that can be easily deployed across different projects. [View Highlight](https://read.readwise.io/read/01j91k0ypypatnzt77n85sdrer))
+
+Designing an ECS application starts with creating the components (data structures) that contain the game data. Important things to take into account are:
+• How many instances of the data will exist
+• How often is data accessed
+• How often is the data mutated
+• When does data need to be accessed/mutated
+• Which data is accessed/mutated together
+• What is the cardinality of the data [View Highlight](https://read.readwise.io/read/01j91k30n38vyb492he5vej8b2))
+
+It is good practice to design components and systems to have a single responsibility. This makes them easier to reuse across projects, and makes it easier to refactor code. [View Highlight](https://read.readwise.io/read/01j91k34bzgxsycjdsfxfj4jm1))
+
+An archetype ECS stores entities in tables, where components are columns and entities are rows. Archetype implementations are fast to query and iterate. [View Highlight](https://read.readwise.io/read/01j91k41g8wnx5ahhg34x2jkn5))
+
+A sparse set based ECS stores each component in its own sparse set which is has the entity id as key. Sparse set implementations allow for fast add/remove operations. [View Highlight](https://read.readwise.io/read/01j91k4e2nj4wk4x8qm0rcw1ea))
+
+A bitset-based ECS stores components in arrays where the entity id is used as index, and uses a bitset to indicate if an entity has a specific component. [View Highlight](https://read.readwise.io/read/01j91k5v49vx19nff799nzy3ty))
+
+A reactive ECS uses signals resulting from entity mutations to keep track of which entities match systems/queries. [View Highlight](https://read.readwise.io/read/01j91k649x535px14rzf4r5a85))
+
+ECS ("Entity Component System") describes a design approach which promotes code reusability by separating data from behavior. [View Highlight](https://read.readwise.io/read/01j91htdgbpsyzgr1b0ddfa0ac))
+
+ECS has the following characteristics:
+• It has entities, which are unique identifiers
+• It has components, which are plain datatypes without behavior
+• Entities can contain zero or more components
+• Entities can change components dynamically
+• It has systems, which are functions matched with entities that have a certain set of components. [View Highlight](https://read.readwise.io/read/01j91hvjdef0xbq6p44wgq4jrj))
+
+A framework that lets you add "things" to entities, with a way to query for entities that have some things but not other things, is generally considered to be an ECS. [View Highlight](https://read.readwise.io/read/01j91hx4zdbfka8v3x211xs198))
+
+• ECS can typically support larger numbers of game objects
+• ECS code tends to be more reusable
+• ECS code is easier to extend with new features
+• ECS allows for a more dynamic coding style [View Highlight](https://read.readwise.io/read/01j91hxszmzjc3mtrcwrg3m53x))
+
+While ECS and OOP overlap, there are differences that impact how applications are designed:
+• Inheritance is a 1st class citizen in OOP, composition is a 1st class citizen in ECS.
+• OOP encourages encapsulation of data, ECS encourages exposed POD (plain old data) objects.
+• OOP colocates data with behavior, ECS separates data from behavior.
+• OOP Object instances are of a single static type, ECS entities can have multiple, dynamically changing components [View Highlight](https://read.readwise.io/read/01j91hzkqsfw0qdfg2e282zp3v))
+
--- a/_master_wiki/void/Readwise/HTMX
+++ b/_master_wiki/void/Readwise/HTMX
@ -0,0 +1,16 @@
+# HTMX: 3 IRL Use Cases
+
+![rw-book-cover](https://i.ytimg.com/vi/sTzF57GE4-k/maxresdefault.jpg)
+
+## Metadata
+- Author: [[ThePrimeTime]]
+- Full Title: HTMX: 3 IRL Use Cases
+- Category: #articles
+- URL: https://www.youtube.com/watch?v=sTzF57GE4-k
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=HTMX%3A%203%20IRL%20Use%20Cases
+> [!tldr]
+> HTMX is a simple tool that can make web development easier by keeping things straightforward. It allows developers to build dynamic web applications without relying heavily on JavaScript frameworks. Many tasks can be achieved with just a few lines of code, making it a valuable addition to a developer's toolkit.
+
+## Highlights
+if you started web dev after 2015 it is hard to see how to do a site without anything other than client-side Frameworks [View Highlight](https://read.readwise.io/read/01j5tc1j7ke8vs2vmcs34c07kn))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,26 @@
+# How Do You Program for 8h in a Row?
+
+![rw-book-cover](https://substackcdn.com/image/fetch/w_1200,h_600,c_fill,f_jpg,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa68add58-ed53-40af-972e-222f936aa4bd_512x312.png)
+
+## Metadata
+- Author: [[Bite Code!]]
+- Full Title: How Do You Program for 8h in a Row?
+- Category: #articles
+- Document Tags: [[dev]] [[productivity]] 
+- URL: https://www.bitecode.dev/p/how-do-you-program-for-8h-in-a-row
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20Do%20You%20Program%20for%208h%20in%20a%20Row%3F
+> [!tldr]
+> Most programmers can't work for 8 hours straight every day without feeling burnt out. It's important to focus on your own coding goals and productivity rather than comparing yourself to others. Finding a balance that works for you will lead to a happier and more sustainable coding experience.
+
+## Highlights
+Unless you are going to deny John von Neumann and Usain Bolt have existed, you have to accept the idea some individuals are able to produce results you can’t. [View Highlight](https://read.readwise.io/read/01j5ve0w5gwghcgzxsyvvhmwqt))
+
+Here I am with the damn spectrum again. But it’s a curve, y’all, of course, it’s a spectrum. You don’t have 10x and 1x, you have 0.3x, 5x, 1.479878x (and -2x because aggressive imbeciles are also part of our reality)... [View Highlight](https://read.readwise.io/read/01j5ve777bthcmj83k6k7cec5f))
+> [!note]
+> Aquí estoy de nuevo con el maldito espectro. Pero es una curva, amigos, por supuesto, es un espectro. No tienes 10x y 1x, tienes 0.3x, 5x, 1.479878x (y -2x porque los imbéciles agresivos también son parte de nuestra realidad)...
+> lol xd
+
+you will have to adapt your rhythm, and the size of the task you are going for, plus manage expectations, yours and others, to be a happy coder [View Highlight](https://read.readwise.io/read/01j5veddky3z4g488sy5bcd4a2)) [[favorite]] 
+
+Figure out what you can do, and find the load that fits you. If you like it, you may attempt to outgrow this by giving yourself more challenges or even putting yourself in an extremely hard situation. However, remember that life, often in the form of customers, bosses and DDOS, will bring that to you anyway. [View Highlight](https://read.readwise.io/read/01j5vee0j5h4jqxfyarnvpxnkt))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,22 @@
+# How I Remember Everything I Read With Readwise
+
+![rw-book-cover](https://i.ytimg.com/vi/OlWomVta4DU/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Tiago Forte]]
+- Full Title: How I Remember Everything I Read With Readwise
+- Category: #articles
+- Document Tags: [[notetaking]] [[productivity]] 
+- URL: https://youtube.com/watch?v=OlWomVta4DU&si=9kSzbiC8eY_Bncgq
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20I%20Remember%20Everything%20I%20Read%20With%20Readwise
+> [!tldr]
+> Readwise is a platform that helps you remember everything you read by collecting highlights from books, articles, and other content. It can export these highlights to various note-taking apps, making it easy to organize your thoughts. This way, you can revisit important information whenever you need it without the hassle of copying and pasting.
+
+## Highlights
+that kind of focused aware reading where you're not just reading a tweet or an Instagram caption you're actually taking the time and space to sit down and really think about something really take an idea seriously that is a rare and precious experience [View Highlight](https://read.readwise.io/read/01j69ty4jsa8qyqrm76cb82e1c))
+
+most of the internet if you think about it especially social media is not designed for calm deep purposeful reflection it's exactly the opposite [View Highlight](https://read.readwise.io/read/01j69v3539zhtvg4z09r0mhj0c))
+
+what I find is I end up deleting never even looking at maybe half of the stuff that is saving my relater app and it's the half that is most click-baity most sensationalistic most pointless most full of hype that's the stuff that I don't even want to be filling my mind
+anyway [View Highlight](https://read.readwise.io/read/01j69v79j1jfc2ptn55y886ee5))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,65 @@
+# How Japanese Minimalism Changed My Life: 5 Principles to Declutter Your Life
+
+![rw-book-cover](https://i.ytimg.com/vi/Sa7cgPILItQ/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Zach Highley]]
+- Full Title: How Japanese Minimalism Changed My Life: 5 Principles to Declutter Your Life
+- Category: #articles
+- Document Tags: [[productivity]] 
+- URL: https://www.youtube.com/watch?v=Sa7cgPILItQ
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20Japanese%20Minimalism%20Changed%20My%20Life%3A%205%20Principles%20to%20Declutter%20Your%20Life
+
+> [!note]
+> **Background:** I will soon be moving out of my parents' house and into a small apartment to live independently. I want to use this transition as an opportunity to embrace a minimalist lifestyle.
+> ---
+> ### Top 3 Most Important Takeaways:
+> 🗑️ **Create Space by Decluttering** 
+> Start by evaluating your physical possessions and ask yourself if each item brings you joy. Embrace the concept of having ample physical space around you, and organize your belongings purposefully. Assign a designated place for every item to prevent clutter from accumulating again.
+> 🧘 **Eliminate Choices to Free Up Mental Space** 
+> Reduce decision fatigue by minimizing choices in your daily life, such as wearing the same outfit or eating the same meals. Simplifying these decisions will free up mental space and time, allowing you to focus on what truly matters.
+> 🌿 **Embrace Imperfection and Transience** 
+> Adopt the principle of Wabi-sabi, which encourages finding beauty in imperfection. Understand that nothing is perfect and that everything is transient. This mindset will help you appreciate the simplicity and clarity that comes with minimalism.
+> [!tldr]
+> When there is too much clutter, you can't think. When you can't think, you can't create. When you can't create, your world slows down. What if we only filled our lives with things that had real value and removed everything else.
+
+📜 Write Up - https://zhighley.com/japanese-minimalism-five-principles-to-declutter-your-life/
+📸 Instagram - https://www.instagram.com/zachhighley/ 
+🐧 Twitter - https://twitter.com/zachhighley 
+💌 Newsletter - https://zhighley.com/newsletter/ 
+
+——————————————————————————————————————————————————
+Who am I:
+
+My name is Zach. I’m a Resident Physician in Boston. I make videos about medical school, studying, and growth. I love trying new things and often mess up. However, every time I screw up, I usually learn something. Whatever I learn, I post it either on YouTube or on my website 🌐  (https://zhighley.com/).
+
+I write a weekly newsletter 💌 (https://zhighley.com/newsletter/) linking the best things I read, watched, and listened to that week. Join the 4,000+ that read it every other Sunday...
+
+## Highlights
+When there's too much stuff around us, our minds can't think straight. When your mind can't think straight, you can't create. When you can't create, when you can't contribute to the world, the world slows down a little bit. [View Highlight](https://read.readwise.io/read/01j7105sy62k477j7we49j3vng))
+
+tip number one is create space. [View Highlight](https://read.readwise.io/read/01j710802fzkm0xb0jfvpe6zj0))
+
+Marie Kondo says, "When people revert to clutter no matter how much they tidy, it is not their room or their belongings, but their way of thinking that is at fault." [View Highlight](https://read.readwise.io/read/01j71087j6npx5etywvmh93dq4))
+
+Tip number two is embrace space. Embrace this newfound clearness you have. [View Highlight](https://read.readwise.io/read/01j71097tmgwwthqw40kqjm70e))
+
+Seneca says, "It's not the man who has too little, but the man who craves more who is poor." [View Highlight](https://read.readwise.io/read/01j710ans5zjy9p4e10chdkk7b))
+
+Tip number three is to be purposeful with your space fillers. [View Highlight](https://read.readwise.io/read/01j710eehmhsxrv02rbrkfxzp3))
+
+"The reason every item must have a designated place is because the existence of an item without a home multiplies the chances that your space will become cluttered again. [View Highlight](https://read.readwise.io/read/01j710fafawb9z9265r7r036pv))
+
+Tip number four is to eliminate choices. [View Highlight](https://read.readwise.io/read/01j710k01a20dk494w8yf8vq3w))
+
+When you eliminate decisions, you create more time. Confucius said that, "Life is really simple. We insist on making it complicated." [View Highlight](https://read.readwise.io/read/01j710mjajf9x11sk2gy3h4tbm))
+
+Eliminate decision fatigue, eliminate choices, free up mental space, free up time to focus on things that have a real impact. [View Highlight](https://read.readwise.io/read/01j710nn39sxpz7md9mhd4cx3q))
+
+this comes to the important principle of Japanese minimalism of Wabi-sabi or kinda loving imperfection. [View Highlight](https://read.readwise.io/read/01j710xzs42s3dj7czt7py85qc))
+
+Tip number six is to think beyond stuff. [View Highlight](https://read.readwise.io/read/01j710zgdawxb9bzxj4w5g67p8))
+
+Create space by decluttering your physical possessions.
+Does this item give me joy? Embrace space by having as much physical space around you wherever you live. Organize all the things in your life purposely. What is this drawer for? What is this cabinet for? Eliminate choices. Maybe you wear the same outfit every day maybe you eat the same breakfast every day. Maybe you only drink water. Next, everything is transient. Nothing is perfect, and that's okay. And finally, can we apply the idea of simple living to not only our stuff, but our thoughts and our actions. [View Highlight](https://read.readwise.io/read/01j7117z1262k0pwpp24knqea4))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,21 @@
+# How a Collaborative Zettelkasten Might Work: A Modest Proposal for a New Kind of Collective Creativity
+
+![rw-book-cover](https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSBHZPD3JWcWaVg_AFb1m5du55SCFgj2hbE1Ek60-RFG4I3W8kvc35rFvniOx-G0NcNnwg&usqp=CAU)
+
+## Metadata
+- Author: [[hidden (bobdoto)]]
+- Full Title: How a Collaborative Zettelkasten Might Work: A Modest Proposal for a New Kind of Collective Creativity
+- Category: #articles
+- URL: https://writing.bobdoto.computer/how-a-collaborative-zettelkasten-might-work-a-modest-proposal/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20a%20Collaborative%20Zettelkasten%20Might%20Work%3A%20A%20Modest%20Proposal%20for%20a%20New%20Kind%20of%20Collective%20Creativity
+> [!tldr]
+> This article gives a preliminary framework for people wanting to experiment with a collaborative zettelkasten. Keep in mind, these are mere suggestions, since I've not yet experimented with this type of slip box. As to whether the suggestions are valid, this will be determined by anyone who attempts to put them into practice. Note: While this article was written in the context of a Luhmann-style zettelkasten, people using similar, adjacent models, should feel free to work with what's presented in ways that fit their system.
+What's a Collaborative Zettelkasten?A collaborative zettelkasten is maintained by multiple people, one in which all the participants add main notes, establish connections between ideas, and freely pull from the network of notes for their own projects / projects worked on as a collective. The contents of the zettelkasten may or may not be aligned with a single, agreed upon subject. Participants may or may not have a common output, goal, or project in mind when they start. The only requirements...
+
+## Highlights
+A collaborative zettelkasten is maintained by multiple people, one in which all the participants add main notes, establish connections between ideas, and freely pull from the network of notes for their own projects / projects worked on as a collective. The contents of the zettelkasten may or may not be aligned with a single, agreed upon subject. Participants may or may not have a common output, goal, or project in mind when they start. [View Highlight](https://read.readwise.io/read/01j5xzksta891sj1jfpexpb9vs))
+
+"[Luhmann's] main concern was not to develop an idea to maximum sophistication; rather, he operated on the assumption that a decision on the usefulness of a note could only be made in relating it to the other notes."[2](https://writing.bobdoto.computer/how-a-collaborative-zettelkasten-might-work-a-modest-proposal/#fn-2) [View Highlight](https://read.readwise.io/read/01j5xzxhwd0d5cgcvstt6y57z4))
+
+As Luhmann states in his own notes, let the zettelkasten function as a "septic tank."[3](https://writing.bobdoto.computer/how-a-collaborative-zettelkasten-might-work-a-modest-proposal/#fn-3) Allow the relationships between ideas to determine their value. [View Highlight](https://read.readwise.io/read/01j5xzz8xhq5r1tde4vkhr0fhp))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,28 @@
+# How the Index Card Method Improves Your Knowledge Gathering
+
+![rw-book-cover](http://cdn.shopify.com/s/files/1/0064/3665/1072/articles/how-the-index-card-method-improves-your-knowledge-gathering-963916_600x.jpg?v=1675232920)
+
+## Metadata
+- Author: [[THINKERS Notebook]]
+- Full Title: How the Index Card Method Improves Your Knowledge Gathering
+- Category: #articles
+- Document Tags: [[notetaking]] [[productivity]] 
+- URL: https://thinkersnotebook.com/blogs/news/how-the-index-card-method-improves-your-knowledge-gathering
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20the%20Index%20Card%20Method%20Improves%20Your%20Knowledge%20Gathering
+> [!tldr]
+> The index card method is a simple and effective way to organize and connect information for writing, research, and projects. It allows you to summarize ideas on cards, linking them to main themes for easy reference. You can even adapt this method to digital formats for better organization and searchability.
+
+## Highlights
+The key components of an effective index card method are:
+• The information on the card is summarized or simplified.
+• Each card is linked back to a main thread or theme of information via a number, a tag, or a title (or a mix of all three). [View Highlight](https://read.readwise.io/read/01j80drzv3a1w0wppg4syztwc3))
+
+There are other ways you can use this method in a notebook, to help order and structure your projects and ideas:
+• Organize your thoughts and findings around a particular topic you’re researching.
+• Scope your long-form article, thesis or book, summarizing each section or chapter.
+• Store important research data for key business metrics.
+• Create reference cards for your business presentation.
+• Track specific habits and goals for a week or month.
+• Keep note of specific birthdays and recurring events by month.
+• The key to using an index card method effectively lies in how you connect the separate ideas and information that you’re listing. [View Highlight](https://read.readwise.io/read/01j80e0c34a7kbvxsy3cbbkf25))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,25 @@
+# How to Actually Use What You Read With Readwise: Part 2
+
+![rw-book-cover](https://s3.amazonaws.com/readwiseio/2018/03/kindle-highlights.png)
+
+## Metadata
+- Author: [[Daniel Doyon]]
+- Full Title: How to Actually Use What You Read With Readwise: Part 2
+- Category: #articles
+- Document Tags: [[notetaking]] 
+- URL: https://blog.readwise.io/reading-workflow-part-2/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Actually%20Use%20What%20You%20Read%20With%20Readwise%3A%20Part%202
+> [!tldr]
+> In Part 2 of the Readwise series, we learn to enhance our reading workflow by actively engaging with what we read. This includes capturing highlights and notes, which help create a two-sided conversation with the text. The article emphasizes the importance of reviewing these materials through the Readwise web app for a more interactive experience.
+
+## Highlights
+you'll find yourself asking as you read: Do I actually want to see this passage again? Is this passage actually highlight-worthy? Will my future self be able to make sense of what I've highlighted? And so on. [View Highlight](https://read.readwise.io/read/01j6mqyk29xd598f62nayabzfj))
+
+The internal dialog is actually a sign that you're *actively* — rather than passively — reading. [View Highlight](https://read.readwise.io/read/01j6mqzsxe83y8t342knm6y82h))
+
+"If your aim in reading is to profit from it — to grow somehow in mind or spirit — you have to keep awake. That means reading as actively as possible. It means making an effort — an effort for which you expect to be repaid." [View Highlight](https://read.readwise.io/read/01j6mrf2e1tg6jz2209brj24yk))
+
+Once you grow accustomed to actually revisiting what you've captured, however, you'll likely discover that you also want to review more than just the original passages. You'll also want to review your original reaction *to* those passages. You can capture these reactions, of course, by taking notes. [View Highlight](https://read.readwise.io/read/01j6mtvq8kd9c0cxcjmwp5bfpq))
+
+The objective is simply to start a conversation rather than just silently highlighting. Maybe you strongly agree with something the author has written. Even better, maybe you strongly disagree. Note why. Maybe a section confuses you. Maybe a section could be helpful to something you're working on. [View Highlight](https://read.readwise.io/read/01j6mtym0q2qhrbap1r1tby8cn))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,37 @@
+# How to Actually Use What You Read With Readwise: Part 3
+
+![rw-book-cover](https://s3.amazonaws.com/readwiseio/2018/03/kindle-highlights.png)
+
+## Metadata
+- Author: [[Daniel Doyon]]
+- Full Title: How to Actually Use What You Read With Readwise: Part 3
+- Category: #articles
+- Document Tags: [[notetaking]] 
+- URL: https://blog.readwise.io/reading-workflow-part-3/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Actually%20Use%20What%20You%20Read%20With%20Readwise%3A%20Part%203
+> [!tldr]
+> In Part 3 of the Readwise series, the author explains how to use advanced workflows for two types of reading: practical and theoretical. Practical reading aims for action, while theoretical reading focuses on gaining knowledge, and Readwise helps users capture and review key insights for both. By utilizing features like Inline Tagging and spaced repetition, readers can turn their reading into meaningful actions and lasting insights.
+
+## Highlights
+"Theoretical books teach you that something is the case. Practical books teach you how to do something you want to do or think you should do." [View Highlight](https://read.readwise.io/read/01j6mxk0qxsc1ge4ebcrabg7n8))
+
+When you read something practical, you are seeking some sort of action — to *do*. When you read something theoretical, you are seeking some sort of knowledge — to *know*. [View Highlight](https://read.readwise.io/read/01j6mxkgms2x7rkwt6qqaaq144))
+
+serendipitous [View Highlight](https://read.readwise.io/read/01j6mxnpq872bx9q40h1ez0hp3))
+> [!note]
+> serendipitous (adjective): occurring by chance in a happy or beneficial way; unexpected and fortunate 🌟🍀
+
+For example, we might make it so highlights tagged `.i` for inbox, like above, are accelerated into your daily reviews until you do something about them. [View Highlight](https://read.readwise.io/read/01j6my11vve93ecp1hwdrd5n9n))
+> [!note]
+> tags highlights for actionability, something that I can filter later to search stuff I want to do or apply
+
+to meaningfully understand a new concept, you need to ponder it repeatedly — in different moods and in different contexts, and from different perspectives. [View Highlight](https://read.readwise.io/read/01j6my5fjqcss9a8zb68vqerw4))
+
+[spaced repetition](https://en.wikipedia.org/wiki/Spaced_repetition), [View Highlight](https://read.readwise.io/read/01j6my96k3avt6s37knqkehh9s))
+> [!note]
+> Spaced repetition: A learning technique that involves increasing intervals of review for information to enhance long-term retention and mastery. By leveraging the psychological spacing effect, spaced repetition optimizes the timing of study sessions based on how well the learner knows the material, promoting efficient memory consolidation and reducing the forgetting curve. This method is commonly used in educational software and flashcard systems to facilitate language learning, exam preparation, and skill acquisition.
+
+[active recall](https://en.wikipedia.org/wiki/Active_recall), [View Highlight](https://read.readwise.io/read/01j6my8p2zekrx849jj5c4yj06))
+> [!note]
+> Active recall: A learning technique that involves actively stimulating memory during the learning process, typically by testing oneself on the material to be remembered. This method contrasts with passive review strategies, such as rereading or highlighting, by emphasizing retrieval practice, which has been shown to enhance long-term retention and understanding. Active recall can take various forms, including flashcards, quizzes, and self-questioning, and is widely used in educational settings to improve learning outcomes.
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,29 @@
+# How to Actually Use What You Read With Readwise
+
+![rw-book-cover](https://s3.amazonaws.com/readwiseio/2018/03/kindle-highlights.png)
+
+## Metadata
+- Author: [[Daniel Doyon]]
+- Full Title: How to Actually Use What You Read With Readwise
+- Category: #articles
+- Document Tags: [[notetaking]] 
+- URL: https://blog.readwise.io/reading-workflow-part-1/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Actually%20Use%20What%20You%20Read%20With%20Readwise
+> [!tldr]
+> Readwise is a tool that helps you remember and use the important ideas you find while reading. It offers a simple workflow with three steps: Capture your highlights, Review them regularly, and Integrate those insights into your life. By using Readwise, you can turn your reading into meaningful actions and lasting knowledge.
+
+## Highlights
+We read in order to learn how to do something or we read to understand some new concept. For example, we might read a book to learn how to negotiate or we might read a book to understand behavioral economics. We call these motives meaningful action and lasting insight, respectively, and a reading workflow will help you get more of both.[](https://blog.readwise.io/reading-workflow-part-1#fn1) [View Highlight](https://read.readwise.io/read/01j58ez9vkh68ptwbnt951wkg9))
+
+*capture* any and all the things that might be meaningful to you — today or tomorrow, small or large — in a reliable system outside your mind so you can make use of those things later [View Highlight](https://read.readwise.io/read/01j58f1740ca5k7akyjp7enmkx))
+
+Now that you're capturing all the things that might be meaningful to you, the next step is to actually go back and *review* those things. Otherwise, what was the point of capturing in the first place? [View Highlight](https://read.readwise.io/read/01j58f3zcas4ewpxjf861kzfy6)) [[favorite]] 
+
+Integrate might mean **improved retention** (or compression) of new concepts thanks to a lightweight form of [spaced repetition](https://en.wikipedia.org/wiki/Spaced_repetition). [View Highlight](https://read.readwise.io/read/01j58f5aqe8f69a4rvvypb3r1n))
+
+Integrate might also mean **enhanced creativity** resulting from the serendipitous juxtaposition of seemingly unrelated ideas. [View Highlight](https://read.readwise.io/read/01j58f679pcp1vtd3ne64cxke9))
+> [!note]
+> This relates to BASB
+
+Integrate might also mean **sudden inspiration** to act on something you've read due to a well-timed reminder in a daily review. [View Highlight](https://read.readwise.io/read/01j58f8fa57a88b7647bwyaxp4))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,33 @@
+# How to Build New Habits by Taking Advantage of Old Ones
+
+![rw-book-cover](https://jamesclear.com/wp-content/uploads/2014/07/Habit-stacking-01-1086x1200.png)
+
+## Metadata
+- Author: [[James Clear]]
+- Full Title: How to Build New Habits by Taking Advantage of Old Ones
+- Category: #articles
+- Document Tags: [[productivity]] 
+- URL: https://jamesclear.com/habit-stacking
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Build%20New%20Habits%20by%20Taking%20Advantage%20of%20Old%20Ones
+> [!tldr]
+> James Clear explains how to build new habits by linking them to existing ones, a technique called habit stacking. By pairing a new behavior with a current daily habit, you make it easier to remember and stick to the new action. This method utilizes the brain's natural ability to strengthen connections between frequently used neurons, enhancing skill development over time.
+
+## Highlights
+One of the best ways to build a new habit is to identify a current habit you already do each day and then stack your new behavior on top. This is called habit stacking. [View Highlight](https://read.readwise.io/read/01j9ptg4p5nm7em2n2azb1e7vg))
+
+The habit stacking formula is:
+> After/Before [CURRENT HABIT], I will [NEW HABIT]. [View Highlight](https://read.readwise.io/read/01j9pth51kbn08v4p8q8pb6s8g))
+
+![](https://jamesclear.com/wp-content/uploads/2014/07/Habit-stacking-01-1086x1200.png)
+Habit stacking increases the likelihood that you’ll stick with a habit by stacking your new behavior on top of an old one. This process can be repeated to chain numerous habits together, each one acting as the cue for the next. [View Highlight](https://read.readwise.io/read/01j9ptmf01qgk91cvkdcd7kyqs))
+
+No matter how you use this strategy, the secret to creating a successful habit stack is selecting the right cue to kick things off. [View Highlight](https://read.readwise.io/read/01j9ptqdz0614xq8g6apgh3kf2))
+
+One way to find the right trigger for your habit stack is by brainstorming a list of your current habits. [View Highlight](https://read.readwise.io/read/01j9pts3gjkah6w1dm32xzdnnz))
+
+, you can create a list with two columns. In the first column, write down the habits you do each day without fail. ... In the second column, write down all of the things that happen to you each day without fail. ... Armed with these two lists, you can begin searching for the best place to layer your new habit into your lifestyle.
+
+Habit stacking works best when the cue is highly specific and immediately actionable. Many people select cues that are too vague. [View Highlight](https://read.readwise.io/read/01j9ptvtp0hv80yjc2cvt41esx))
+
+Habits like “read more” or “eat better” are worthy causes but far too vague. These goals do not provide instruction on how and when to act. Be specific and clear: After I close the door. After I brush my teeth. After I sit down at the table. [View Highlight](https://read.readwise.io/read/01j9pty5517662hdae5jqcmpwj))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,28 @@
+# How to Not Write Like an Asshole
+
+![rw-book-cover](https://thehustle.co/wp-content/uploads/2015/09/copywork2_og_image.jpg)
+
+## Metadata
+- Author: [[The Hustle]]
+- Full Title: How to Not Write Like an Asshole
+- Category: #articles
+- Document Tags: [[notetaking]] 
+- URL: https://thehustle.co/how-to-not-write-like-an-asshole
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Not%20Write%20Like%20an%20Asshole
+> [!tldr]
+> Most people write poorly, using confusing sentences and unnecessary words. A simple way to improve writing is through copywork, where you hand-copy great writing to learn from it. By practicing this method for just a few minutes each day, anyone can become a better writer.
+
+## Highlights
+The easiest way to become a better writer is to copy great writers. It’s that simple. [View Highlight](https://read.readwise.io/read/01j6py7hp221k6fzx7mza6b3k1))
+
+When I say you should copy great writers, I mean you should literally copy their best work, word-for-word, and preferably by hand.
+This process is called copywork and it’s mind-numbingly simple. You barely have to think. All you have to do is sit down with your favorite book, article, or blog post and copy it. [View Highlight](https://read.readwise.io/read/01j6py9pbrq5epw3sxgy5a9wv2))
+
+**Step 1: Pick a writer who you want to be like** ... To start with copywork, pick an author you love. Copywork is hard work, and you’ll spend a lot of time with whomever you decide to copy, so you need to love their work.
+
+**Step 2: Buy a ton of legal notebooks** 
+[Studies have shown](https://lifehacker.com/5738093/why-you-learn-more-effectively-by-writing-than-typing) that people learn better when they write by hand versus typing. So, for copywork it’s best to do all the copying by hand. I prefer using yellow legal notepads as they’re easy to read and cheap. [View Highlight](https://read.readwise.io/read/01j6pzrch7rq9ct4xr5f58nxhc))
+
+**Step 3: Start writing** 
+I suggest copying your favorite author for 10 minutes each day. It’s that simple. [View Highlight](https://read.readwise.io/read/01j6pzs8wpx24wawjxq7fypj7f))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,54 @@
+# How to Organize a Notebook for Work
+
+![rw-book-cover](https://rebelsguidetopm.com/wp-content/uploads/2021/12/GPM-Featured-Image-11.jpg)
+
+## Metadata
+- Author: [[Elizabeth Harrin]]
+- Full Title: How to Organize a Notebook for Work
+- Category: #articles
+- Document Tags: [[notetaking]] [[productivity]] 
+- URL: https://rebelsguidetopm.com/how-to-organize-a-notebook-for-work/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Organize%20a%20Notebook%20for%20Work
+> [!tldr]
+> This text provides tips on organizing a notebook for work, emphasizing the importance of personalizing the system to suit individual needs. It suggests practical strategies like cutting corners to locate pages easily and using sections to categorize notes effectively. The author shares insights on maximizing a notebook's potential as a productivity tool within a larger task management system.
+
+## Highlights
+2. Put the To Do list at the back [View Highlight](https://read.readwise.io/read/01j80bnsjvv4jdnga09mjrajqx))
+
+3. Put important information on the inside front cover ... • Cost codes, timesheet codes or project codes
+• Important telephone numbers
+• Instructions on how to change your voicemail (can you tell that’s a real example from inside my book?!)
+
+You’ll get through a lot of work notebooks in time, so put the start date on the front cover or one of the first inside pages so you know what time period this book covers. [View Highlight](https://read.readwise.io/read/01j80bpqqt6fhjntgx30tkvnmn))
+
+5. Organize the inside ... I don’t use page numbers in my books because they are free-flow for my notes and tend to be a chronological representation of what I was working on at the time. ... • Leave a page at the front for the table of contents or keep a page at the back for the index
+• Add page numbers to each page
+• Mark where things are in the notebook as you go.
+
+I don’t section my work because as a project manager, I find much of my work overlaps. [View Highlight](https://read.readwise.io/read/01j80bs5d5q3vp2ccdpq97j1fp))
+
+If you don’t want to number and structure, an alternative option is to have a different notebook for each project or to use sections. [View Highlight](https://read.readwise.io/read/01j80bsg6hnpaqwjvyjnszmsxy))
+
+6. Use sections ... • Weekly goals and objectives (or monthly/annual goals)
+• Trackers for habits e.g. drinking water, gratitude
+• Lists e.g. team birthdays. ... Use sticky notes or sticky tabs to section off the book and make it easier to find the right page when you need it.
+
+in circles to help them stand out in the notes:
+A: Action – for specific tasks to be done
+D: Decision – normally to be transferred to a decision log or confirmed on email so no one can forget that we made it.
+R: Risk – to be transferred to the project risk log and something done about it.
+I: Issue – to be transferred to the issue log and flagged with whomever is going to be able to do something about it.
+Star – something important. Normally something that has to be done today. [View Highlight](https://read.readwise.io/read/01j80am80gt459xt3n5hkv1mr5))
+
+I make time to rewrite the important lists in my book (the actions) on a regular basis. It isn’t strictly necessary, but it helps me clear my mind and focus on what is still to do. [View Highlight](https://read.readwise.io/read/01j80aq18td7pq8hk3ty7fh0pg))
+
+However you use your notebook, I would recommend allocating some time on a regular basis to go through it and tidy it up. Mark tasks as complete, transfer notes to other tools, re-write lists. Just refresh yourself on what is in there and check it is still working for you. [View Highlight](https://read.readwise.io/read/01j80ar15h0jat05dtvevj5362))
+
+Your notebook should be part of a whole productivity and task management system. It should fit alongside your online tools. [View Highlight](https://read.readwise.io/read/01j80ayzgm5px6mvxbvbnpxr8m))
+
+Your system should work in the round. No one in your team should be waiting to be told what to do because you wrote it down in the wrong place. [View Highlight](https://read.readwise.io/read/01j80b1xq3h5rpdrrwmnbvkgqg))
+
+Notebook organization should be simple. If you create a system that is too difficult to stick to, then you won’t stick to it. [View Highlight](https://read.readwise.io/read/01j80b2b9t15za4kfvtmv0ytpr))
+
+Remember, the way you organize your work notebook can evolve over time. Switch up how you use your notebook as your needs change. [View Highlight](https://read.readwise.io/read/01j80bbpykp4yqskxt4g5m1aaz))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,39 @@
+# How to Rebuild Your Routines When Everything Changes | Rewind
+
+![rw-book-cover](https://i.ytimg.com/vi/-c1HY-vrmIQ/maxresdefault.jpg)
+
+## Metadata
+- Author: [[How to ADHD]]
+- Full Title: How to Rebuild Your Routines When Everything Changes | Rewind
+- Category: #articles
+- URL: https://youtube.com/watch?v=-c1HY-vrmIQ&si=7ximCdZha4zJg-LR
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Rebuild%20Your%20Routines%20When%20Everything%20Changes%20%7C%20Rewind
+> [!tldr]
+> The video discusses how to rebuild routines after significant changes, especially for those with ADHD. It offers eight practical tips, such as keeping what works, allowing time for transitions, and managing stress. The key message is to be patient with yourself and acknowledge your achievements while adjusting to new routines.
+
+## Highlights
+keep what you know works it can be tempting to start with a blank slate but the less you change the quicker you'll adjust to those changes so anything you liked from your old
+routine that would still work with the new one consider keeping [View Highlight](https://read.readwise.io/read/01j8b6stmxqkv0rx1yq54y0fpb))
+
+design the rest with you in mind hang on current you not future you [View Highlight](https://read.readwise.io/read/01j8b6x2we07a50fpdy60tx1xf))
+
+give yourself plenty of white space in your schedule remember transitions will probably take longer at first because you're not used to your new routines [View Highlight](https://read.readwise.io/read/01j8b6z2dx0wnx94kde9a96xre))
+
+can speed up the process of setting those new routines and reduce the transition time between them by mentally walking through your new routines a few times before you need to start using them [View Highlight](https://read.readwise.io/read/01j8b71t112qtedbcbxbyfd2q8))
+
+write the new routines down ... put it in your schedule create a habit tracker sticker chart use an app
+
+there's a surprising amount that will suddenly not be automatic when you go through Big Life Changes again speaking from experience once you're used to your routines your brain will usually remind you what's next until then you'll probably need some help so you need to
+have a way of keeping yourself on track [View Highlight](https://read.readwise.io/read/01j8b776eyyvx1aq905tatr726))
+
+if at all humanly possible wait until you're used to your new routine before adding in stuff that you've never done before [View Highlight](https://read.readwise.io/read/01j8b7be7rkvdf5z68nva3fkx5))
+
+manage your stress levels change even good change is stressful expect small unexpected changes to affect you more than usual right now because they're not
+really small changes they're Peaks on a mountain of giant changes [View Highlight](https://read.readwise.io/read/01j8b7efp3k1eb92dakzhy2m6z))
+
+acknowledge your achievements it can be really easy when you're adjusting to a new routine to only see the stuff you didn't get to check out all the stuff you did even little things like getting to work on time that you might otherwise take for granted are a huge
+Victory when you did it with a new routine [View Highlight](https://read.readwise.io/read/01j8b7jk8wq2xtpscy1fdbhesg))
+
+tweak as necessary if anyone gets all of their routines right on their first try I'm going to very annoyed impressed but
+annoyed it's totally normal for it to take some trial and error to figure out what works for you so expect that things will go wrong and you will need to make adjustments doesn't mean you're doing something wrong it's part of the process [View Highlight](https://read.readwise.io/read/01j8b7ntbt4jbsb7ma3axe4z3b))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,30 @@
+# How to Start Journaling
+
+![rw-book-cover](https://www.simplyfiercely.com/wp-content/uploads/2021/08/How-to-Start-Journaling-Feature-Image.jpg)
+
+## Metadata
+- Author: [[Jennifer]]
+- Full Title: How to Start Journaling
+- Category: #articles
+- URL: https://www.simplyfiercely.com/start-journaling/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Start%20Journaling
+> [!tldr]
+> Journaling is a powerful habit that promotes self-awareness and helps you make intentional choices in life. To start, just relax and begin writing about your thoughts and feelings, using prompts if needed. Sticking with journaling daily can lead to greater clarity and personal growth.
+
+## Highlights
+Journaling helps combat this short-sightedness by encouraging us to step back and consider the big picture. [View Highlight](https://read.readwise.io/read/01j83ye06dw8vkysgntnavndb8))
+
+First and foremost, relax and let go of any ideas about doing it the “right” way— because when it comes to journaling, there’s no such thing! Your journal is a personal space for you to use however you see fit. [View Highlight](https://read.readwise.io/read/01j83yn2d1qgem2pycxrsth3gj)) ^363cd8
+
+After that, the best way to start journaling is to just begin. [View Highlight](https://read.readwise.io/read/01j83yp4c2axwtzy3k87e98ajt))
+
+If you don’t know what to write about, a great place to begin is by **[asking questions](https://www.simplyfiercely.com/7-questions-to-inspire-intentional-living/).** My favourites include:
+• *How do you feel right now?*
+• *Why do you feel that way?*
+• *How do you want to feel?*
+• *What can you do to feel that way?* [View Highlight](https://read.readwise.io/read/01j83yqf5g8j5h964d735bfexe)) [[journaling/prompt]] 
+
+If you don’t feel comfortable writing long, in-depth entries in your journal then find something that works for you. Again, there are no right or wrong ways to journal as long as you’re exploring your thoughts and feelings. [View Highlight](https://read.readwise.io/read/01j84amwhygt3bsycq85eptcs4))
+
+**Make journaling a special ritual.** Try and do it at the same time every day and treat it as a special event, not a chore! Light a candle, make a hot drink, burn incense—whatever makes the experience special for you. [View Highlight](https://read.readwise.io/read/01j84anevvcn0ydv0287v7yjff))
+
--- a/_master_wiki/void/Readwise/How
+++ b/_master_wiki/void/Readwise/How
@ -0,0 +1,52 @@
+# How to Think in Writing
+
+![rw-book-cover](https://substackcdn.com/image/fetch/w_1200,h_600,c_fill,f_jpg,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd8bec767-3242-4428-a281-0cdc3182ff75_750x587.png)
+
+## Metadata
+- Author: [[Henrik Karlsson]]
+- Full Title: How to Think in Writing
+- Category: #articles
+- Document Tags: [[star]] 
+- URL: https://substack.com/home/post/p-143987982
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=How%20to%20Think%20in%20Writing
+
+> [!note]
+> Este articulo habla sobre cómo utilizar la escritura como un medio para realizar un análisis crítico de nuestros propios pensamientos e ideas y obtener su completo potencial.
+> ---
+> Utiliza un metodo kinda like Phoenix Wright cross examination:
+> - hacer nuestros pensamientos solidos y especificos al escribirlos
+> - Decantarlos hasta poder obtener una conclusión, una conjetura o una hipótesis
+> - Desafiar esta conclusion intentando probarla verdadera o falsa, buscando sus fallas y grietas. Con _"pressionar"_ (follow up questions)
+> - Esto nos proveerá más información, más pensamientos y más ideas que pueden re-definir nuestra conclusión 
+> [!tldr]
+> Writing helps refine thinking by making ideas more precise and complete. Without writing, one may not fully form or realize the limitations of their ideas. By unfolding and probing claims through writing, one can discover flaws, refine understanding, and reach deeper insights.
+
+## Highlights
+Ideas can feel complete. It's only when you try to put them into words that you discover they're not. So if you never subject your ideas to that test, you'll not only never have fully formed ideas, but also never realize it. [View Highlight](https://read.readwise.io/read/01j8b867hqxmxzdkn3q3pjqbm4))
+
+Good thinking is about pushing past your current understanding and reaching the thought behind the thought. [View Highlight](https://read.readwise.io/read/01j8b8cww40tqsnbaw3k42mgvn))
+
+When I write, I get to observe the transition from this fluid mode of thinking to the rigid. As I type, I’m often in a fluid mode—writing at the speed of thought. I feel confident about what I’m saying. But as soon as I stop, the thoughts solidify, rigid on the page, and, as I read what I’ve written, I see cracks spreading through my ideas. What seemed right in my head fell to pieces on the page. [View Highlight](https://read.readwise.io/read/01j8b8ezy6ywq99f4dkz8r3ymd))
+
+a conjecture,” a qualified guess based on limited information. A hypothesis. [View Highlight](https://read.readwise.io/read/01j8b8hry74ry71zk4ffareecj))
+
+Forcing the diffuse ideas and impressions in your head into a definite statement is an art form. You have to grab hold of what is floating and make it rigid and sharp. It can feel almost embarrassing–revealing your ignorance with as much vulnerability as possible. [View Highlight](https://read.readwise.io/read/01j8b8ksn5s7t4bn3wwefxeqwr))
+
+By unfolding I mean “interrogating the conclusion to come up with an explanation of why it *could* be true.” What premises and reasoning chains leads to this conclusion? The explanation isn’t meant to prove that your conclusion was right. It is just a way of unpacking it. [View Highlight](https://read.readwise.io/read/01j8b8nc9p2ywzsmztc4d6zjyk))
+
+Since the goal is to find flaws in our guesses (so that we can change our minds, refine our mental models and our language, and be more right) unfolding a claim through an explanation is progress. Even if the explanation is wrong. [View Highlight](https://read.readwise.io/read/01j8b8q53msmbr9kbr9dzhew55))
+
+Once I unfold my understanding in writing, I often see holes right away. I start correcting myself and discarding ideas already while typing. I cut ideas that are obviously flawed. I rewrite what feels ambiguous to make it sharper–more precise, concrete, unhedged, and true to my understanding. [View Highlight](https://read.readwise.io/read/01j8b8v6s8028792yvcwgy19n0))
+
+I tend to go through my list of premises and assumptions and ask follow-up questions to myself, to further unfold my conclusion. [View Highlight](https://read.readwise.io/read/01j8b8y1z5wbjfjkjpjcwkwj4b))
+
+Now that I have spelled out my position and fixed the obvious flaws, I start probing myself more seriously to see if I can get the argument to break down. [View Highlight](https://read.readwise.io/read/01j8b9fcg5r389f7pzvsfad82m))
+
+If one of the premises I have unfolded is a factual claim, I’ll spend a few minutes skimming research in the area to see how well my position holds up. [View Highlight](https://read.readwise.io/read/01j8b9g5d16dwc6dqe3b6x7hag))
+
+But often the type of problem I like to think about is too personal and messy and qualitative to be resolved cleanly through a statistically significant study. What I do in these situations instead is to consider *counterexamples*. ... I like to visualize concrete situations when I make an argument ... When I have a concrete situation in mind, I can ask myself, “What is a situation where the opposite happened? Why was that?” I can list the characteristics of the situation that inform my conclusion and then systematically look for cases that have other characteristics.
+
+Counterexamples are useful in two ways. Either you find a counterexample that a) proves one of the premises wrong but b) does not change your mind about the conclusion. Lakatos calls this a local (and non-global) counterexample. This means there is something wrong with your unfolding. ... Local counterexamples help you improve your explanation and get a better understanding.
+
+Other times, the counterexample you find undermines the whole idea—a *global counterexample*. You unfold your conclusion and discover that one of the premises does not hold up, and there is no way to patch it. The fracture spreads right up to the conclusion. Now—this is what we have been longing for—there is a big hole of confusion where before there was a mental model. It is time to replace it with something more subtle and deep that incorporates the critique. [View Highlight](https://read.readwise.io/read/01j8b9vyrraya2jxw8ygqhb7nz))
+
--- a/_master_wiki/void/Readwise/I
+++ b/_master_wiki/void/Readwise/I
@ -0,0 +1,25 @@
+# I Like Makefiles
+
+![rw-book-cover](https://news.ycombinator.com/favicon.ico)
+
+## Metadata
+- Author: [[thunderbong]]
+- Full Title: I Like Makefiles
+- Category: #articles
+- URL: https://switowski.com/blog/i-like-makefiles/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=I%20Like%20Makefiles
+> [!tldr]
+> The author, Sebastian Witowski, enjoys using makefiles because they provide a consistent way to automate project setups and commands. He finds makefiles simple to write and effective for managing various projects, regardless of the technologies used. While he appreciates other build tools, he prefers to use makefiles for their familiarity and ease of use.
+
+## Highlights
+they often follow an unwritten convention of implementing the same set of commands to get you up and running. [View Highlight](https://read.readwise.io/read/01j8tjgaevhxxyf0b2nf9gnbkd))
+
+Even if I use tools like Docker or gulp in my project, I still use makefiles to orchestrate those tools. [View Highlight](https://read.readwise.io/read/01j8tjjdw6w421n8jk5vvj6cs5))
+
+Some common tasks that most of my personal projects[[1]](https://switowski.com/blog/i-like-makefiles/#fn1) contain include:
+• `dev` to start the development server
+• `build` to build the project (if a build step is necessary)
+• `deploy` to deploy/publish the project [View Highlight](https://read.readwise.io/read/01j8tjknbwkzycf3ft7bka78ym))
+
+Make is simple and doesn't require as many additional dependencies as some other build tools. This can be useful if you need a tool that will work in a restricted environment where installing additional packages is difficult or impossible for security reasons. [View Highlight](https://read.readwise.io/read/01j8tjpnwyppr4k1jf6ctx5js0))
+
--- a/_master_wiki/void/Readwise/I've
+++ b/_master_wiki/void/Readwise/I've
@ -0,0 +1,24 @@
+# I've built my first successful side project, and I hate it
+
+![rw-book-cover](https://switowski.com/posts/2024/i-have-built-my-first-successful-side-project-and-i-hate-it/cover.jpg)
+
+## Metadata
+- Author: [[switowski]]
+- Full Title: I've built my first successful side project, and I hate it
+- Category: #articles
+- URL: https://switowski.com/blog/i-have-built-my-first-successful-side-project-and-i-hate-it/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=I%27ve%20built%20my%20first%20successful%20side%20project%2C%20and%20I%20hate%20it
+> [!tldr]
+> Sebastian Witowski created a stock trading script that initially excited him, but he soon faced challenges with customer support and feature requests. Despite some sales, he experienced burnout from managing the project while juggling a full-time job. Ultimately, he learned that selling a product is just the beginning, and it requires ongoing effort and support.
+
+## Highlights
+I'm an engineer, goddamit! We're not meant to click buttons in the browser or send the same email over and over again! [View Highlight](https://read.readwise.io/read/01j5y28d3ftfhss7wegbnkdwea)) [[favorite]] 
+
+Did disconnecting from my project affect my sanity? Oh, hell yes! The project went on autopilot, and it no longer felt like a dreaded chore when I was checking my emails or logging in to my TradingView account. It lost a lot of traction because I stopped updating it, so people think it's not useful anymore (even though it does its job as well as it did a few years ago). Its revenue declined in the past years. But I don't care. I'm happy again. [View Highlight](https://read.readwise.io/read/01j5y2yn2enf1aqz6y9akfmpxa))
+
+The dreaded truth that most programmers learn the hard way is that releasing a product is just the beginning. Once it's out there, you have to maintain it: fix bugs, implement new features, deal with disputes or frauds, and answer a LOT of emails (often from curious window shoppers who never convert to paying customers). [View Highlight](https://read.readwise.io/read/01j5y2gg4qd0p65b97g6xjgxy1))
+
+If your side project is not a source of genuine joy and you have other priorities, it's important to set some boundaries. [View Highlight](https://read.readwise.io/read/01j5y323gv3dwa4y15qzwpycg3))
+
+If you're planning to sell products globally, consider using a "merchant of record" like Gumroad or Paddle. This way, you won't have to figure out how much tax to charge for each country (basically, you only sell to Gumroad, and they resell your product to the final customer). [View Highlight](https://read.readwise.io/read/01j5y32rm97xwbjg1tv9hr65g6))
+
--- a/_master_wiki/void/Readwise/Implementing
+++ b/_master_wiki/void/Readwise/Implementing
@ -0,0 +1,23 @@
+# Implementing an Actor Model in Golang
+
+![rw-book-cover](https://miro.medium.com/v2/da:true/resize:fit:1200/0*smZOmMQjuS_5l1Af)
+
+## Metadata
+- Author: [[Gaurav Sharma]]
+- Full Title: Implementing an Actor Model in Golang
+- Category: #articles
+- Document Tags: [[dev]] [[dev/design-patterns]] [[dev/go]] 
+- URL: https://betterprogramming.pub/implementing-the-actor-model-in-golang-3579c2227b5e
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Implementing%20an%20Actor%20Model%20in%20Golang
+> [!tldr]
+> The article explains how to implement an actor model in Golang to handle concurrent tasks efficiently. It describes the roles of actors, task assigners, and the actor system, highlighting their interactions and task processing. The author also shares insights from a simulated web server benchmark that demonstrates how the system adapts to varying task latencies.
+
+## Highlights
+The actor model is one such programming construct that models a large number of independent jobs, being processed in any order with no need for a lock synchronisation. [View Highlight](https://read.readwise.io/read/01j96c65ze39pyrcsvp8fpg6xp))
+
+An actor has a task queue and goroutine that listens to the task queue and execute task. [View Highlight](https://read.readwise.io/read/01j96c7xjz9y9snbaawa8qa6hn))
+
+The task is executed in an actor. It is an implementation of a given interface with *Execute method*. Anything which can be executed by making Execute call. Task is a business implementation of the work we need to do. [View Highlight](https://read.readwise.io/read/01j96c958cxjr5855jy9qcshx1))
+
+![](https://miro.medium.com/v2/resize:fit:700/1*YGV-7SgbyBUKIUnruMI5Sg.png) ... `Task`s are submitted to `ActorSystem` using the `SubmitTask` method. A `taskAssigner` assigns each of the task to one of the `Actor`s. Each `Actor` also has a small queue, in which it buffers the tasks and executes one by one.
+
--- a/_master_wiki/void/Readwise/In
+++ b/_master_wiki/void/Readwise/In
@ -0,0 +1,56 @@
+# In Search of Code Purity
+
+![rw-book-cover](https://i.ytimg.com/vi/voRBS0r4EyI/maxresdefault.jpg?v=65aa862f)
+
+## Metadata
+- Author: [[No Boilerplate]]
+- Full Title: In Search of Code Purity
+- Category: #articles
+- Document Tags: [[dev]] [[dev/rust]] 
+- URL: https://www.youtube.com/watch?v=voRBS0r4EyI
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=In%20Search%20of%20Code%20Purity
+
+> [!note]
+> Goal: The intention is to leverage the principles of functional programming purity in a project, utilizing Rust or other programming languages, to enhance code readability, maintainability, and reliability. This to-do list will help achieve that by outlining actionable steps for implementation.
+> - [ ] 🦀 **Familiarize with Rust's const functions** to understand how they execute at both compile time and runtime, ensuring the utilization of pure functions.
+> - [ ] ⚙️ **Implement pure functions** in the codebase, ensuring they do not produce side effects and maintain referential transparency for predictable behavior.
+> - [ ] 🔍 **Establish a system for tagging functions** as pure in the codebase, allowing both developers and the compiler to reason about function behavior effectively.
+> - [ ] 📜 **Utilize Rust macros wisely** to enable compile-time evaluations effectively, while understanding their limitations compared to const functions.
+> - [ ] 📝 **Incorporate error handling** strategies focused on return types and assertions for better debugging of const functions.
+> - [ ] 🧪 **Experiment with caching techniques** that leverage the predictability of pure functions to optimize performance in the application.
+> [!tldr]
+> Alternate title: Rust's Hidden Purity System
+I was taught formal methods at university but these ultra-safe development techniques are expensive, require using unusual external verification languages, and most damning for web and application developers, they slow down iteration.
+After graduating and getting a webdev job, I despaired that the safety and guarantees of the formal systems that I had been introduced to weren't available to me as a web developer.
+I was going to have to act if I wanted to live in a different world.
+
+❤️ If you would like to support what I do, I have set up a Patreon here: https://www.patreon.com/noboilerplate - Thank you!
+
+📄 All my videos are built in compile-checked markdown, transcript source code available here https://github.com/0atman/noboilerplate this is also where you'll find links to everything mentioned. 
+
+🖊️ Corrections are in the pinned ERRATA comment.
+
+🦀 Start your Rust journey here: https://www.youtube.com/watch?v=2hXNd6x9sZs
+
+👕 Bad shirts available here https://www.teepub...
+
+## Highlights
+first function here factorial is a pure function a function that doesn't cause or rely upon side effects we know this without reading the function body because it doesn't have IO in the signature the second function main prints to the screen and so must have I/O this is a fantastic way to keep side effects managed and covers half of the nightmare errors I've seen throughout my career [View Highlight](https://read.readwise.io/read/01j6ez3db15q2wagxxh4fxpagw))
+
+if your language has a way of separating or tagging functions that are pure and then can hold you to that contract both you and the compiler can reason about your code in useful new ways [View Highlight](https://read.readwise.io/read/01j6ezg1548mj8f5ntkwrhxh86))
+
+If a pure function is called twice with the same inputs the result is guaranteed to be the same every time this is called referential transparency or idance or determinism this enables perfect predictable caching of return values which your compiler might automatically and easier debugging [View Highlight](https://read.readwise.io/read/01j6ezh53e7hcszmxxd91aze3r))
+
+const functions are functions that can be executed at compile time as well as runtime they differ from rust macros which can only run at compile time and can do anything by being much more limited [View Highlight](https://read.readwise.io/read/01j6ezpb7jgqybcmhz38r5sdxk))
+
+when debugging the only way to get information out of a const function is by its return type or Hal in compilation
+with a panic or a failed assertion [View Highlight](https://read.readwise.io/read/01j6f15drv4ypknhpcqz8jh9dc))
+
+macros execute arbitrary code at compile time and then can insert the
+results of that processing as potentially const values [View Highlight](https://read.readwise.io/read/01j6f1arc85y5twtf781mgy5tz))
+
+rust's const functions are only pure once you get to runtime [View Highlight](https://read.readwise.io/read/01j6f1a5g0yddv78empzwmh1xp))
+
+rust
+is as pure as possible but no purer [View Highlight](https://read.readwise.io/read/01j6f1env98rtskyvf5sp1eygp)) [[dev/rust]] [[dev]] 
+
--- a/_master_wiki/void/Readwise/Journaling
+++ b/_master_wiki/void/Readwise/Journaling
@ -0,0 +1,69 @@
+# Journaling for Personal Development: Stress Management
+
+![rw-book-cover](https://priscillapalmer.com/wp-content/uploads/2023/09/journaling.jpg)
+
+## Metadata
+- Author: [[Barbara H. Pugh]]
+- Full Title: Journaling for Personal Development: Stress Management
+- Category: #articles
+- Document Tags: [[notetaking]] 
+- URL: https://priscillapalmer.com/journaling/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Journaling%20for%20Personal%20Development%3A%20Stress%20Management
+> [!tldr]
+> Journaling is a helpful tool for managing stress and promoting personal growth by allowing individuals to reflect on their thoughts and emotions. It can lead to increased self-awareness, emotional release, and clarity about stressors. By regularly writing in a journal, people can develop strategies to cope with challenges and improve their overall well-being.
+
+## Highlights
+Research suggests that engaging in regular journaling can have numerous benefits when it comes to stress reduction and personal development. Firstly, by writing down one’s thoughts and feelings related to stressful events or situations, individuals are able to gain clarity and perspective on their internal state. This process enables them to identify patterns or triggers that contribute to their stress levels, thereby empowering them with the knowledge needed to make positive changes in their lives. Additionally, journaling provides a safe outlet for expressing emotions that may be difficult to articulate verbally. Through this cathartic release of pent-up feelings, individuals can experience relief from emotional distress while gaining a sense of emotional release and catharsis. [View Highlight](https://read.readwise.io/read/01j82r0yf8r0wfj54mg92wx0rv))
+
+Moreover, journaling can also serve as a means of problem-solving and decision-making. When faced with stressors or challenges, writing about them allows individuals to explore different perspectives and potential solutions. This process of self-reflection and brainstorming can lead to increased insight and clarity, helping individuals develop effective strategies for managing their stressors. [View Highlight](https://read.readwise.io/read/01j82r1qjbd8pykyn658ae279f))
+
+Furthermore, the act of journaling itself can be a calming and grounding practice. Taking the time to sit down, focus on one’s thoughts, and put them into words can create a sense of mindfulness and present-moment awareness. This mindfulness aspect of journaling has been shown to promote relaxation, reduce anxiety levels, and improve overall mental well-being. [View Highlight](https://read.readwise.io/read/01j82r23yyw2bs77zw57sdm8mk))
+
+There are no strict rules for journaling; Sarah can write freely without worrying about grammar or structure – the goal is simply to allow her thoughts and emotions to flow onto the pages. [View Highlight](https://read.readwise.io/read/01j82r51a1ef5bnr6mhk69e8q6))
+
+Here are some key benefits of journaling for stress reduction:
+• **Emotional release:** Writing down our thoughts and feelings allows us to acknowledge and process them more effectively. It provides a safe space to express raw emotions without judgment or consequences.
+• **Perspective gain:** Through journaling, we gain perspective on our problems and challenges. This shift in viewpoint enables us to approach difficulties with greater clarity and objectivity.
+• **Problem-solving:** Journaling facilitates problem-solving by allowing us to explore different solutions and evaluate their pros and cons. It helps break down complex issues into manageable parts.
+• **Gratitude cultivation:** Writing about the things we are grateful for fosters positivity and shifts our focus away from stressors. This practice encourages mindfulness and promotes a sense of contentment. [View Highlight](https://read.readwise.io/read/01j82rdzjqkbhtddtevdwsb6ct))
+
+Set aside dedicated time: Find a quiet space where you can focus solely on your writing without distractions. Allocating even just 10-15 minutes each day can make a significant difference in managing stress. [View Highlight](https://read.readwise.io/read/01j83g3ykzypexdx6yg264s24a))
+
+Choose a format that suits you: Whether it’s pen and paper or digital platforms, select a medium that feels comfortable for you. Experiment with different styles such as free-writing or structured prompts until you find what resonates best. [View Highlight](https://read.readwise.io/read/01j83g47r6y96fpxd11gq003hg))
+
+Be non-judgmental: Remember that your journal is a safe space for self-expression; there are no right or wrong answers. Allow yourself to freely explore your thoughts and feelings without censoring or criticizing them. [View Highlight](https://read.readwise.io/read/01j83g4f15c6h136m28f6ccymb))
+
+Incorporate gratitude practices: Cultivating gratitude has been shown to reduce stress levels significantly. Consider including a regular gratitude reflection in your journal entries by listing things you’re grateful for each day. [View Highlight](https://read.readwise.io/read/01j83g4t6htbb3g9av0q4czz0x))
+
+Emotional release: The act of putting pen to paper allows individuals to express suppressed emotions effectively, leading to emotional catharsis. [View Highlight](https://read.readwise.io/read/01j83g8at9az6qxc9mbvvkrzma))
+
+Stress reduction: Journaling offers an outlet for processing stressful experiences and reducing psychological distress. [View Highlight](https://read.readwise.io/read/01j83g8qgcdemre6wj8jz8hp27))
+
+Problem-solving: By writing down challenges and brainstorming potential solutions, individuals can develop a clearer perspective on problems they face. [View Highlight](https://read.readwise.io/read/01j83g94f5gj99fz91kke20f1x))
+
+Self-discovery: Regular journaling promotes self-awareness and facilitates personal growth by uncovering deeper layers of oneself. [View Highlight](https://read.readwise.io/read/01j83g98fa6s5kwmepwea2jh0x))
+
+Reflect on Daily Experiences: Allocate dedicated time each day to record significant events or encounters that affected your mood positively or negatively. [View Highlight](https://read.readwise.io/read/01j83gcn96tpdded0ydrqb6052))
+
+Identify Emotional Responses: Pay attention to how you feel throughout the day by checking in with yourself regularly. Describe these emotions accurately using specific terms such as frustration, excitement, sadness, or contentment. [View Highlight](https://read.readwise.io/read/01j83gcy7trhxp8ccs2kecxz2s))
+
+Explore Underlying Causes: Dig deeper into your reactions by questioning why certain situations evoke particular emotional responses within you. [View Highlight](https://read.readwise.io/read/01j83gdgv4dd5z122knj7yyb8v))
+
+Monitor Physical Sensations: Observe any physical sensations associated with different emotions—such as increased heart rate during moments of anger or tension—to develop an awareness of your body’s response. [View Highlight](https://read.readwise.io/read/01j83ge9xk9phtja3tpg8mcw1c))
+
+**Identify coping mechanisms**: Reflect on past entries where you successfully managed stressful situations. Note down those techniques and activities that helped alleviate your stress levels. [View Highlight](https://read.readwise.io/read/01j83ghndtsnn7x0d678pgmtbz))
+
+**Set realistic goals**: Break down larger tasks into smaller, achievable goals. This will provide a sense of progress and accomplishment while reducing overwhelm. [View Highlight](https://read.readwise.io/read/01j83ghwt10bc8h4d5wmteebb2))
+
+**Practice self-care**: Prioritize activities that promote relaxation and well-being, such as exercise, meditation, or spending time in nature. [View Highlight](https://read.readwise.io/read/01j83gj5e39ctg3sj16zs2wpyw))
+
+**Seek support**: Reach out to trusted friends or family members who can offer guidance and encouragement during challenging times. [View Highlight](https://read.readwise.io/read/01j83gj9v2zbm0ggre2zrgk54a))
+
+Enhanced self-reflection: Practicing mindfulness allows individuals like Sarah to observe their thoughts and emotions without judgment, fostering greater understanding of their inner experiences. [View Highlight](https://read.readwise.io/read/01j83gmxxazma1tt6rb144p8xs))
+
+Improved emotional regulation: By cultivating awareness of their emotions through mindful journaling, individuals can develop strategies for managing challenging feelings effectively. [View Highlight](https://read.readwise.io/read/01j83gneyj2gmpr6zp51vybmjp))
+
+Increased clarity and perspective: Engaging in mindful reflection while journaling enables individuals to gain fresh insights and new perspectives on stressful situations. [View Highlight](https://read.readwise.io/read/01j83gnhg39rqb94yept0sk884))
+
+Strengthened resilience: Regularly practicing mindfulness in conjunction with journaling equips individuals with tools to navigate adversity more skillfully. [View Highlight](https://read.readwise.io/read/01j83gp7c9ekx44ypp3sgrc4hz))
+
--- a/_master_wiki/void/Readwise/Learn
+++ b/_master_wiki/void/Readwise/Learn
@ -0,0 +1,22 @@
+# Learn vLANs, Subnets, and NAT to Improve Your Network Security
+
+![rw-book-cover](https://i.ytimg.com/vi/gk_kHgNhJVo/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Jim's Garage]]
+- Full Title: Learn vLANs, Subnets, and NAT to Improve Your Network Security
+- Category: #articles
+- Document Tags: [[homelab]] 
+- URL: https://www.youtube.com/watch?v=gk_kHgNhJVo
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Learn%20vLANs%2C%20Subnets%2C%20and%20NAT%20to%20Improve%20Your%20Network%20Security
+> [!tldr]
+> This text explains how to set up a static IP address, configure subnets, and use VLANs and NAT for better network security. It emphasizes the importance of organizing your network into different subnets and assigning VLAN tags for improved traffic management. The author also highlights the role of firewalls in controlling access to various devices on the network.
+
+## Highlights
+that's pretty much how op works it would know that your tablet is making an internet request even though it's coming from that same ISP IP address therefore we're able to break down One external IP address into multiple
+internal addresses [View Highlight](https://read.readwise.io/read/01j54cajqj3xyfj1eemhcmsvqw))
+> [!note]
+> NAT in a nutshell
+
+what it does is it takes a single wire and it splits it up into lots of little wires now if you do that right through proper subnetting and VLAN tagging you can introduce security but it's dependent on making sure that you put the right devices in the right subnets and you control or access those protocols those IP addresses with strict firewall rules [View Highlight](https://read.readwise.io/read/01j54hz2c5z7kpt964rxs33095))
+
--- a/_master_wiki/void/Readwise/Looking
+++ b/_master_wiki/void/Readwise/Looking
@ -0,0 +1,154 @@
+# Looking After Your Autistic Self
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article4.6bc1851654a0.png)
+
+## Metadata
+- Author: [[Niamh Garvey]]
+- Full Title: Looking After Your Autistic Self
+- Category: #books
+> [!tldr]
+> Autistic people often feel overwhelmed by sensory stress and emotional changes in their daily lives. Recognizing their triggers can help them manage these feelings and create a sense of safety. Using sensory tools and strategies allows them to participate in activities without becoming overwhelmed.
+
+## Highlights
+In my experience, there is a misconception that autistic children grow into ‘less autistic’ adults. I believe this stems from our ability, as autistic adults, to adapt our behaviour to ‘stand out’ less, and to ‘fit in’ more. We learn how to hide our differences and hide our overwhelm. But this takes its toll on us, and can actually increase our levels of stress. [View Highlight](https://read.readwise.io/read/01j6ta5tywrynbek3nwrk4ztpf))
+
+Autistic people can react differently to stress than non-autistic people. Research has found that autistic children release higher amounts of the stress hormone cortisol than non-autistic children. Additionally, the levels of cortisol last longer in their bodies, even after the thing that caused the stress has gone (Spratt et al. 2012). [View Highlight](https://read.readwise.io/read/01j6tb32z54r5n39rmednd9p0d))
+
+What Skills Are Involved in Executive Function?
+• Planning: Recognising that a task needs to be done, and planning how to do it.
+• Organising: Getting ready for a task: Recognising what tools or skills you will need.
+• Initiation: Starting a task.
+• Flexible thinking: Seeing a task through and not giving up when faced with problems.
+• Time management: Being able to divide your time appropriately to complete all the steps of a task.
+• Finishing a task: Not giving up on a task, keeping focused and motivated until the end.
+• Evaluation: Looking back at how you did a task, evaluating how you did it, and learning from it.
+• Emotional regulation: Managing emotions throughout a task so that the task can be completed. [View Highlight](https://read.readwise.io/read/01j6tbdfg6e1wfrs92988vk3mb))
+
+A study published in 2015 (Bishop-Fitzpatrick et al. 2015) found that autistic adults without intellectual disability experienced substantially higher levels of stress than non-autistic adults. Not only that, but when stress levels increased, autistic adults’ social functioning went down significantly. [View Highlight](https://read.readwise.io/read/01j6tb2h8a03x46nqxsatrwcs2))
+
+Research has found that autistic adults have significantly more challenges with executive function skills than non-autistic adults, with one study finding that 20–30% of autistic adults had difficulty with planning, while 20% had difficulty with flexible thinking (Johnston et al. 2019). This study also found that having a higher IQ did not equate to having better executive function skills. Only 35% of autistic adults were found to have no impairment in executive function skills. [View Highlight](https://read.readwise.io/read/01j6tbg0wvc6rrxs57pnpbqpqn))
+
+A trigger is something that sets off your stress response. There are endless types of things that may trigger your stress response. For autistic people, a trigger could be a type of environment (e.g. a busy crowded room), a social difficulty, a sensory experience (e.g. a loud noise), a communication challenge, a demand on your organisation skills, a change in routine etc. [View Highlight](https://read.readwise.io/read/01j6tb3tpnc9cs5f76gkkm8b8b))
+
+There might be no real danger, but our brains and bodies acts like there is. When we are stressed, our bodies experience changes that may include dizziness, a racing heartbeat, high blood pressure, breathing fast, and sweating (World Health Organization 2008). [View Highlight](https://read.readwise.io/read/01j6tb4xc2qpbh3z0gvpt8958g))
+
+Triggers can cause you to feel anxious or overwhelmed, angry or frightened, unsafe or under attack. Sometimes individual triggers may not cause an immediate stress response, but a build-up of triggers, or too many triggers at once, can lead to fight, flight, or freeze mode, and you might experience anxiety, overwhelm, shutdown, or meltdown (see [Chapter 11](private://read/01j68en5pg3ysg1jcbwjsjmy61/#chap_11) for information on meltdowns and shutdowns). [View Highlight](https://read.readwise.io/read/01j6tb631tgjc6dyzvs1yw22kp))
+
+Learning what triggers your stress response is not just important to reduce the psychological impact of stress, but it also improves the physical health of your body. Putting strategies in place to deal with your triggers will help reduce the damaging effect of chronic stress on your body. Over-exposure to the stress hormone cortisol from chronic stress can increase the risk of anxiety, depression, headaches, muscle pain, problems with digestion, heart disease, sleep disturbance, difficulty maintaining a healthy weight, and impaired memory and concentration (Mayo Clinic 2021). [View Highlight](https://read.readwise.io/read/01j6tb9cyhtard039hqes709t7))
+
+The Five Steps to Managing Triggers
+1. The Detective Habit: Identifying your triggers.
+2. Coping Strategies: Learn to manage your triggers.
+3. Rationing: Spread out your triggers.
+4. Recovery: Plan your recovery time between triggers, and after triggers.
+5. Quick Calm Strategies: These are strategies to help you calm down quickly. As developing immediate calming strategies is a huge topic, this will be dealt with in the next chapter. [View Highlight](https://read.readwise.io/read/01j6tbn89zmyj8vdd2tvcqq327))
+
+Executive function is the ability to get things done. It is the ability to organise yourself, and carry tasks through from beginning to end. Our daily lives are full of tasks, and thus we rely on our executive function skills to do everything from getting dressed to leaving the house on time, from working to preparing meals etc. [View Highlight](https://read.readwise.io/read/01j6tbar3qva0233pbzz8xpgv2))
+
+In order to start identifying what my triggers are, I began to develop my ‘detective habit’. This is a habit of reflecting on how I felt and behaved in a scenario, so I could learn to identify my triggers. [View Highlight](https://read.readwise.io/read/01j6tbp0fjq1fvf5hxd3z6p5g1))
+
+The detective habit is about looking back at a scenario that I found hard, analysing it with non-judgemental eyes, and giving thought and consideration to what could have caused the stress. Once I identify the triggers, I then make plans to support myself when exposed to the identified triggers. [View Highlight](https://read.readwise.io/read/01j6tbq246p82d1yr80dj96dwx))
+
+How to Use the Detective Habit ... What happened?
+• What did I feel? Did I feel stressed, scared, out of control, angry etc.?
+• Was there anything in the environment that could have been a trigger? Was there a sensory stressor? ... Did the environment mean there was too much information to take in at once? Did the environment create challenges for any of my executive function skills? ... • At what point did I start to feel a stress response? Was it when someone started talking to me? Was it when someone tried to get eye contact? Was it when I walked into a shop? Was it when the environment changed? Was it at the point of transitioning from one task to another? ... Were my basic needs met before I encountered the trigger? By basic needs, I mean hunger, thirst, sleep, body temperature, and physical comfort. ... • What were my strengths in the situation, i.e. what did I manage well? Which of my strengths could I use in similar scenarios in future?
+• What would have helped me to feel more comfortable, or avoid becoming stressed and/or overwhelmed?
+• What coping strategies could I use if that situation happens again, or if I’m exposed to the same trigger or triggers?
+
+The DSM-5 (Diagnostic and Statistical Manual, 5th edition) is the American Psychiatric Association’s guide to mental illness and disorders, including diagnosing autistic people. It suggests that autistic people have rigid thinking, insist on sameness, are inflexible, and are overly ritualised. ... What the DSM-5 doesn’t explain properly, in my opinion, is that many of these diagnostic traits come out when we are stressed, but may improve when we are calm and happy.
+
+Every time I came up with a coping strategy, I asked myself what strength I was using to develop that strategy. [View Highlight](https://read.readwise.io/read/01j6tca09mxawkj3xcah30yy47))
+
+Interestingly, an autistic friend of mine lately told me about her strategy for getting the staff to turn down the music in restaurants. She taps her ear and says to the staff, ‘My hearing aid is buzzing from the music being so loud, could you please turn it down?’ It works every time. I expressed my discomfort with this as it’s a blatant lie (she has no hearing aid), and she said, ‘No, it’s not a lie, my ear is a hearing aid, in a way, and my ear hears the loud music as a horrible buzzing’. [View Highlight](https://read.readwise.io/read/01j6tcjsnfvnr1kz1906cpz5mz))
+
+Sometimes I’m not aware of my own triggers, or autistic differences, until someone else points them out to me. ... Validating the feelings of an autistic person is one of the best things someone else can do to support that autistic person, especially in times of stress. ... if you plan to ask others about your own triggers and traits, be prepared for some surprises, and be aware that you may find some observations upsetting.
+
+When I first began to identify my triggers, my first thought was ‘Now I know what to avoid’. But I soon realised that I would become agoraphobic if I tried to live a life avoiding all my triggers. I also wouldn’t be able to experience so many things that bring me joy. [View Highlight](https://read.readwise.io/read/01j6wyjkm7shc41zxzk5c6xzev))
+
+I therefore realised that I cannot shut all triggers out of my life; instead I need to learn to deal with them. Taking control of my triggers means taking care of myself while still living a full life. This involves planning and preparing myself to cope with triggers. [View Highlight](https://read.readwise.io/read/01j6wyprn8vttk71kp619rt10n))
+
+One of the ways I take control of my triggers is by rationing them out. This means being careful that I don’t plan too many triggering events or activities close together. By spreading triggers out, I give myself time to recover after each one, and time to prepare and plan for the next one. [View Highlight](https://read.readwise.io/read/01j6wyr4pg3m4n08ysqth3tgz7))
+
+The world is full of triggers, and dealing with them takes energy, mental planning, and work. I don’t have infinite energy to cope with triggers; I need time to rest and refuel my energy levels. I therefore pre-emptively plan time for myself to rest or decompress during and after social situations, or any situation that I know will require a lot of my coping strategies. [View Highlight](https://read.readwise.io/read/01j6wz0zc2hkz1z4417922tkks))
+
+KEY POINTS
+◊ Triggers are things that set off a stress response in our brains, and make our body feel the need to fight, flight, or freeze.
+◊ Autistic people can get overwhelmed or stressed from exposure to their triggers.
+◊ Every autistic person has different triggers, so it’s important to get to know your own.
+◊ The detective habit is a method of reflection that can help identify one’s triggers, and then create strength-based coping strategies.
+◊ Other people can be helpful in identifying your triggers, but take caution that the person you ask is sensitive and uncritical.
+◊ Autistic people can react differently to triggers at different times. If your basic needs are not met, or if you are stressed, you are more likely to react strongly to a trigger.
+◊ Rationing out your triggers helps avoid triggers building up and becoming overwhelming.
+◊ Planning time to rest after a build-up of triggers is really important, as is having a few techniques to calm yourself when out and about. [View Highlight](https://read.readwise.io/read/01j6wz69za3httx5ksj1zz0hnq))
+
+---
+
+New highlights added at 2024-09-23 6:48 PM
+A Quick Calm Plan is a series of strategies or tools that you can use to calm down, refuel your energy, and to reduce the feeling of being overwhelmed. When I am overwhelmed and have either shut down (see [Chapter 11](private://read/01j68en5pg3ysg1jcbwjsjmy61/#chap_11) for more on shutdown) or am about to shut down, I cannot think flexibly, and therefore it’s very important to have a Quick Calm Plan made before I become overwhelmed. [View Highlight](https://read.readwise.io/read/01j8g84a4z0dxke72pje3wp9f4))
+
+• Realising I’m doing repetitive body movements such as rubbing my index finger against my thumb, or twitching my eye or head very slightly. [View Highlight](https://read.readwise.io/read/01j8g89vr2rf03z0v2jr6k5yta))
+
+• A strong desire not to talk to anyone. [View Highlight](https://read.readwise.io/read/01j8g8ak0vpa3chwn2q16nwsq7))
+
+• Exhaustion. [View Highlight](https://read.readwise.io/read/01j8g8cmw6qbcq8w1sxcz4q9t8))
+
+• Feeling like I will scream if one more demand is put on me. [View Highlight](https://read.readwise.io/read/01j8g8cpdn84p3nmvcyv50ybtr))
+
+• Feeling like I might burst into uncontrollable crying. [View Highlight](https://read.readwise.io/read/01j8g8cray1hcekkqjm5rtsj27))
+
+• Feeling like everything is just too much and I cannot cope. [View Highlight](https://read.readwise.io/read/01j8g8cwmqtmqeg0xydgywme9j))
+
+Remove yourself from the stressful situation, if possible. [View Highlight](https://read.readwise.io/read/01j8g8egz63debcmjcrhjktda3))
+
+Ask yourself are your basic needs met? [View Highlight](https://read.readwise.io/read/01j8g8etm4gkgpsys8k11nmq1a))
+
+When you feel stressed or anxious, you may feel an urge to breathe faster or deeper, as if you are hungry for more oxygen. But when you are hyperventilating, you actually need to breathe less, not more. This is because you need to bring up the amount of carbon dioxide in your body (i.e. stop blowing out so much air). You can do this by taking smaller breaths and holding your breath after you inhale for the count of four, and again holding your breath after you exhale for the count of four (NHS Borders 2005). [View Highlight](https://read.readwise.io/read/01j8g8kqt48za0cg0m9pc4pv9r))
+
+Take a drink. [View Highlight](https://read.readwise.io/read/01j8g8n8zh4rs2v31hsdfsxpp5))
+
+Find somewhere you can be alone. [View Highlight](https://read.readwise.io/read/01j8g8ngzvq0srdq7rw75a2rs4))
+
+Go home and go to bed for a while, [View Highlight](https://read.readwise.io/read/01j8g8pqabw067rt9jnbdr4er7))
+
+Hold a hot water bottle, heated pad, or warm mug just under your chest bone. [View Highlight](https://read.readwise.io/read/01j8g8q3nk4z3nmjkdk7xka7d1))
+
+Lie under a weighted blanket. [View Highlight](https://read.readwise.io/read/01j8g8qmdfsk0g4zgmsn0fvqjw))
+
+Put something heavy on your lap. [View Highlight](https://read.readwise.io/read/01j8g8rdcsrj07yj0bf0bgwnfb))
+
+Smell something lovely [View Highlight](https://read.readwise.io/read/01j8g8sv21bny6sxhqkr0p3sxs))
+
+Splash cold water on your face, the back of your neck, and on your palms and inner wrists. [View Highlight](https://read.readwise.io/read/01j8g8tgtasn1nbvbkezc3qr71))
+
+Get fresh air. [View Highlight](https://read.readwise.io/read/01j8g8tnmezvhkkazky6pfd47v))
+
+Avoid people putting demands on you if possible. [View Highlight](https://read.readwise.io/read/01j8g8v3a27x4e9n13fdpwvjn1))
+
+Listen to music or an audiobook. [View Highlight](https://read.readwise.io/read/01j8g8veva1a3kymtv71mt8p14))
+
+Darken the room. [View Highlight](https://read.readwise.io/read/01j8g8vqcrkejsy0s9jp1ary4k))
+
+Reduce visual stimulation. [View Highlight](https://read.readwise.io/read/01j8g8w54nzt72bn56w1qmt5rv))
+
+Take a shower or bath. [View Highlight](https://read.readwise.io/read/01j8g8wsnxw2njt5q037a5k9xs))
+
+Singing is a lovely way to control your breathing and expand your chest, [View Highlight](https://read.readwise.io/read/01j8g8xjm5pkzcn9g4r1nx1r2e))
+
+Go into nature, whether that’s a garden or a park, or maybe it’s just looking at nature on your phone. [View Highlight](https://read.readwise.io/read/01j8g8xx6fen4gz5x05ryjmfk8))
+
+Have a warm drink [View Highlight](https://read.readwise.io/read/01j8g8y1gt5frvjb7tfbqwkxdy))
+
+Turn off the internet on your phone, or turn off the phone so you can disconnect from people, if the overwhelm is caused by social stress. [View Highlight](https://read.readwise.io/read/01j8g8yks2t50qkn6s594re2ps))
+
+Say how you feel. I often find that even just saying how I feel out loud to someone helps ease the feelings. [View Highlight](https://read.readwise.io/read/01j8g8ys4ymwr3xnfmhm8c7wv8))
+
+Ask for help. [View Highlight](https://read.readwise.io/read/01j8g8zbp27ks99fn15zn0x6b6))
+
+Exercise. I used to go for a jog when I felt shaky with stress or anxiety, which is an activity that combines fresh air, time alone, and deep pressure into the joints, which is calming to the proprioceptive sensory system [View Highlight](https://read.readwise.io/read/01j8g8zy14e8xpxyaxtshp4d0f))
+
+Having a visual version of your Quick Calm Plan will help you to carry out the strategies and remember to use your calming tools, even when you are overwhelmed or stressed. [View Highlight](https://read.readwise.io/read/01j8g917881cdzmf5pj0znhqqk))
+
+Stimming, also known as self-stimulatory behaviour, is a repetitive, often rhythmic behaviour. ... There are many ways to stim, including using body movements, sounds, thought patterns, and more.
+
+If an autistic person is stimming, it may suggest they are feeling the need to release their overwhelm, distress, over-stimulation, anger, joy, excitement, or any intense emotion. This feeling of release is why stimming is a coping strategy. [View Highlight](https://read.readwise.io/read/01j8g9f8r6td0nfwc1n3w047t5))
+
--- a/_master_wiki/void/Readwise/Making
+++ b/_master_wiki/void/Readwise/Making
@ -0,0 +1,16 @@
+# Making a Blog With Rust
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png)
+
+## Metadata
+- Author: [[mckayla.blog]]
+- Full Title: Making a Blog With Rust
+- Category: #articles
+- URL: https://mckayla.blog/posts/making-a-blog-with-rust.html
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Making%20a%20Blog%20With%20Rust
+> [!tldr]
+> The author created a personal blog using Rust, aiming for an easy writing experience and control over the site’s generation. They chose Rust for its simplicity and productivity, despite its reputation for being complex. The blog's framework, called Pocky, allows publishing posts easily through Markdown and Git without extra fuss.
+
+## Highlights
+I'm a hacker to my core. I love to poke at things, tear things apart, and shuffle around the parts as I put them back together. [View Highlight](https://read.readwise.io/read/01j6ax5r2tem9q9dx3ctw86mj1))
+
--- a/_master_wiki/void/Readwise/Mi
+++ b/_master_wiki/void/Readwise/Mi
@ -0,0 +1,23 @@
+# Mi Paso a Paso Para Desarrollar Proyectos De Software
+
+![rw-book-cover](https://i.ytimg.com/vi/uCq7XP9CNag/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Fazt]]
+- Full Title: Mi Paso a Paso Para Desarrollar Proyectos De Software
+- Category: #articles
+- URL: https://www.youtube.com/watch?v=uCq7XP9CNag
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Mi%20Paso%20a%20Paso%20Para%20Desarrollar%20Proyectos%20De%20Software
+> [!tldr]
+> El video de Fazt explica el proceso de desarrollo de proyectos de software como desarrollador independiente. Se enfoca en las herramientas y técnicas que utiliza para organizar su trabajo y comunicarse con los clientes. Además, menciona la importancia de recibir feedback y hacer ajustes durante el desarrollo del proyecto.
+
+## Highlights
+yo utilizo una herramienta bastante sencilla llamada d diagram.io esta te permite poder diseñar dentro de la web una especie de tablas a medida de que escribes un lenguaje y esas te permiten crear relaciones y esto incluso luego se pueden convertir en sq huele [View Highlight](https://read.readwise.io/read/01j8nppp54gq5czx8dzghw9w7b))
+> [!note]
+> db diagram.io
+
+la plataforma supabase también ha creado una web llamada postgress neww en donde utilizando un pront puedes ir generando un diagrama Rd e incluso te da el código de postgress en caso utilicen
+esta base de datos [View Highlight](https://read.readwise.io/read/01j8nps2a1bz3xgkamzvsd60m7))
+> [!note]
+> postgres.new
+
--- a/_master_wiki/void/Readwise/Monad
+++ b/_master_wiki/void/Readwise/Monad
@ -0,0 +1,42 @@
+# Monad Is Actually Easy
+
+![rw-book-cover](https://i.ytimg.com/vi/8hYUthfmSRM/maxresdefault.jpg)
+
+## Metadata
+
+- Author: [[Coding with Yalco]]
+- Full Title: Monad Is Actually Easy.
+- Category: #articles
+- Document Tags: [[dev]] [[dev/design-patterns]]
+- URL: <https://www.youtube.com/watch?v=8hYUthfmSRM>
+- Archive: <https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Monad%20Is%20Actually%20Easy>.
+
+> [!tldr]
+> #Functional #Programming #Coding
+
+This video explains one of the concepts of functional programming, Monad. A monad can be understood as a box that creates a new box filled with values by applying a function to a value. The basic functions of a monad include Unit, Map, and FlatMap. The unit is a function that wraps a given value in a monad, Map is a function that sends out the result of the executed function back into the box, and FlatMap is a function that processes values already contained in the box. Thanks to these functions, monads make it convenient to process values in programming and help simplify difficult problems. Therefore, understanding and being able to use it is a great help in improving programming skills. Through this video, I hope you have helped understand the basic concepts and operating principles of Monad, and understand Monad through a simple example.
+
+## Highlights
+
+'Maybe' is like Schrödinger's box.  In other words, it is used to hold a value that  may or may not exist, just like the types called   Option, Optional, Nullable in other languages. Such monads allow for the safe and convenient  
+handling of operations when a  valid value has not been returned [View Highlight](https://read.readwise.io/read/01j9xkp05a5hvjysk36jj8qt2x)) [[resources]]
+> [!note]
+> This example can be usefull to replicate the behavior of Option<T> of Rust in other languages
+
+There are these three essentials in  a monad. Unit, map, and flat map. [View Highlight](https://read.readwise.io/read/01j9xks9yx76p1gnsrxh1kz6qn))
+
+In other words, this 'Maybe' monad can make   a box with a value with 'just',  or an empty box with 'nothing' [View Highlight](https://read.readwise.io/read/01j9xktwhss9pwc2y7yt09t6x2))
+
+the 'Functor' function,  commonly referred to as the 'map' method.  It carries out the given function and  then puts the result back into a box. [View Highlight](https://read.readwise.io/read/01j9xkw0a68fr05fytfenqczj3))
+
+the flat map,   also known as 'bind'. It's the same as the above map,   but you can see that it doesn't wrap  the value in a box when sending it out. [View Highlight](https://read.readwise.io/read/01j9xkwy1tgn917kczbarkdxcr))
+
+we can summarize monads like this:  
+They are magic boxes that have the  ability to hold a given value and   later process the subsequent functions given  by map or flat map, returning other boxes. [View Highlight](https://read.readwise.io/read/01j9xk4qrbj6bft0t9vwx8pgk0))
+
+the Left Unit Law. When there's a certain value and a function,  the rule is that the result of wrapping this  value in a monad and applying a function,  should be the same as simply  giving that value to the function. [View Highlight](https://read.readwise.io/read/01j9xk6jbj6rjagtgqvfzp4kjs))
+
+the Right  Unit Law which stipulates that,  the result of applying a function that  simply returns the same value to the monad  should be identical to the original monad. [View Highlight](https://read.readwise.io/read/01j9xk7rpfgzvd8ba29cx9qj44))
+
+he law of associativity.
+When applying two functions  'f' and 'g' to a certain monad,  Applying 'g' to the result of first applying 'f', Should yield the same result as applying a single   function that is a combination  of 'f' and 'g' sequentially. [View Highlight](https://read.readwise.io/read/01j9xk96vz0xb9wm1vkmke4ser))
--- a/_master_wiki/void/Readwise/NeurodiversityWhitePaperFINAL.md
+++ b/_master_wiki/void/Readwise/NeurodiversityWhitePaperFINAL.md
@ -0,0 +1,43 @@
+# NeurodiversityWhitePaperFINAL
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/media/reader/parsed_document_assets/217097737/R5UR4y6xDYgXS7GQrVIXqqEfxTK7onAwuxIThk45JEw-cove_tLj7cMv.png)
+
+## Metadata
+- Author: [[cdsreg.com]]
+- Full Title: NeurodiversityWhitePaperFINAL
+- Category: #articles
+- Document Tags: [[design]] [[dev/accesibility]] 
+- URL: https://www.cdsreg.com/assets/NeurodiversityWhitePaperFINAL.pdf
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=NeurodiversityWhitePaperFINAL
+
+## Highlights
+A structured and predictable layout helps all attendees find what they need. Keep headings, colors, and spacing consistent throughout your event web page and forms to create a familiar visual pattern for neurodiverse users. [View Highlight](https://read.readwise.io/read/01j80z4vtd50rd6mx389xj245v))
+
+Choose legible fonts and appropriate font sizes to enhance readability. [View Highlight](https://read.readwise.io/read/01j80z5jjrtnjhrzz45151hedj))
+
+neurodiverse audiences have a preference toward muted, pastel hues and neutral tones. Consider using a matte black background with two or three pastel hues to depict data, or a neutral tan, gray, or white background to prevent colors from overwhelming the reader. [View Highlight](https://read.readwise.io/read/01j80zay83cd3zs5mr5cv8f5bj))
+
+r [View Highlight](https://read.readwise.io/read/01j80zbt6qxbf3qnkdw3z8qee1))
+
+Simplify your event web page and forms by reducing unnecessary animations and busy backgrounds. A clean design minimizes sensory overload, allowing neurodiverse users to focus on essential content. [View Highlight](https://read.readwise.io/read/01j80zeq2075rv1rej44a7k0mk))
+
+o [View Highlight](https://read.readwise.io/read/01j80zezsd7tf9tmtrw0nbqgp3))
+
+Use clear headings, subheadings, and visual cues to establish a hierarchy of information. Neurodiverse users benefit from a structured content layout that helps them quickly grasp the importance and organization of information. [View Highlight](https://read.readwise.io/read/01j80zgp155t1g2japh3sm2jm3))
+
+Craft straightforward language and concise sentences to facilitate comprehension. Clear content helps neurodiverse individuals process information more easily and reduces the risk of misinterpretation. [View Highlight](https://read.readwise.io/read/01j80zhpdq1k0knybfacq7d8xz))
+
+Include descriptive image alternative text (also known as alt text or alt tags) for images and diagrams. This ensures that neurodiverse attendees who rely on screen readers or have difficulty interpreting visuals can access and understand the content. [View Highlight](https://read.readwise.io/read/01j80zn0r0zsw75xejf3gpam0t))
+
+Incorporate sufficient spacing between elements and paragraphs. White space enhances content digestion, prevents crowding, and enables neurodiverse users to focus on individual pieces of information. [View Highlight](https://read.readwise.io/read/01j80znjnftwn94d83yj7ejzkk))
+
+Provide the ability to adjust font sizes, color themes, and reading modes. Customizable options empower neurodiverse attendees to tailor the online experience to their preferences, enhancing their engagement. [View Highlight](https://read.readwise.io/read/01j80zq3newv6vp3g8qbhf9bda))
+
+Offer a straightforward navigation menu with clear labels. Neurodiverse individuals may rely on structured browsing paths such as breadcrumb navigation, and intuitive navigation ensures everyone can easily find and explore relevant content. [View Highlight](https://read.readwise.io/read/01j80zr6nsdb9nwndf5ydhqsmv))
+
+Incorporate text-to-speech features to accommodate auditory learners and those with reading challenges. Enabling this functionality allows neurodiverse users to absorb content through their preferred sensory channel. [View Highlight](https://read.readwise.io/read/01j80zscatb4sypv22d48c09y3))
+
+When using videos or audio, provide transcripts and captions. This supports attendees who may struggle with auditory or visual processing, ensuring they can access and comprehend information effectively. [View Highlight](https://read.readwise.io/read/01j80zszx3pkx6xhb3xrz1v49m))
+
+Ensure forms follow a logical flow and offer clear instructions, and that there are visual cues like highlighted inputs to help readers know where they are in the form. A step-by-step approach minimizes confusion and frustration for neurodiverse users during data input. [View Highlight](https://read.readwise.io/read/01j80ztdpbr8m2kbjc7pyss1ac))
+
--- a/_master_wiki/void/Readwise/On
+++ b/_master_wiki/void/Readwise/On
@ -0,0 +1,33 @@
+# On finishing things
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article1.be68295a7e40.png)
+
+## Metadata
+- Author: [[alexreichert.com]]
+- Full Title: On finishing things
+- Category: #articles
+- URL: https://www.alexreichert.com/blog/finishing
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=On%20finishing%20things
+
+> [!note]
+> **Background:** The intent is to develop the ability to consistently complete projects in a timely manner while overcoming obstacles related to accountability, clarity of goals, and the fear of sharing work.
+> - [ ] 📝 **Create a project specification document for each new project to clarify goals and outline necessary tasks.**
+> - [ ] ⏳ **Set a deadline for project completion, ideally within 2 to 4 weeks, to establish a concrete finish line.**
+> - [ ] 🌐 Develop a public projects page to share specs, demos, and retrospectives, including unfinished projects, to foster a sense of accountability.
+> - [ ] 🎯 Regularly review and adjust project goals to ensure they are clear and measurable, reducing procrastination.
+> - [ ] 🔄 Share work with peers or a community for feedback to overcome the fear of sharing and validate project usefulness.
+> [!tldr]
+> Finishing projects can be really challenging, as it's often unclear when something is truly complete. Sharing work publicly can help overcome this difficulty and offer personal growth, accountability, and potential connections. To improve, setting clear goals and deadlines can make it easier to push through to the finish line.
+
+## Highlights
+This begs the question: why is it important to share your work with the world?
+First, because there's practically no downside, and very, very high potential upside. [View Highlight](https://read.readwise.io/read/01j68aj6hyksvsfzm62xr7y5k7)) [[favorite]] 
+
+because it's weirdly therapeutic. In the same way that journaling can alleviate anxiety by externalizing it, writing publicly encourages you to process your thoughts more rigorously, and launching an app forces you to find out if your idea has legs or not. [View Highlight](https://read.readwise.io/read/01j68akfqnw95egtaczyadh2z8)) [[productivity]] 
+
+First of all, more often than not, the end goal is neither clear nor concrete. It's not obvious where the "finish line" even is. When this is the case, it's easy to procrastinate by nitpicking the design, adding little flourishes, or using "perfectionism" as an excuse. [View Highlight](https://read.readwise.io/read/01j68anqkv399fr50q8qhehvgm)) [[favorite]] [[productivity]] 
+
+I think there are two strategies that would help a lot: 1) writing a spec (i.e. a plan) upfront, and 2) timeboxing the project by giving myself a deadline. [View Highlight](https://read.readwise.io/read/01j68aq1fbhqx79hp9mnvn39n1)) [[productivity]] [[favorite]] 
+
+I've started setting up a [projects page](https://www.alexreichert.com/projects), where I plan to share the specs, demos, and retrospectives of my personal projects. Even for the "unfinished" ones, sharing them here gives me a small sense of closure. [View Highlight](https://read.readwise.io/read/01j68ath2r2az2v2hwzc6y7jxt))
+
--- a/_master_wiki/void/Readwise/Own
+++ b/_master_wiki/void/Readwise/Own
@ -0,0 +1,17 @@
+# Own Your Content on Social Media Using the IndieWeb
+
+![rw-book-cover](https://i.ytimg.com/vi/X3SrZuH00GQ/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Jamstack TV]]
+- Full Title: Own Your Content on Social Media Using the IndieWeb
+- Category: #articles
+- Document Tags: [[dev]] [[indie-web]] [[selfhosted]] 
+- URL: https://www.youtube.com/watch?v=X3SrZuH00GQ
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Own%20Your%20Content%20on%20Social%20Media%20Using%20the%20IndieWeb
+> [!tldr]
+> The video discusses how to take control of your content on social media by using your own website. It emphasizes the importance of owning your data so you can manage it on your own terms, rather than relying solely on social media platforms. By creating personal sites, you can archive and share your content while maintaining ownership and creative control.
+
+## Highlights
+here a couple of my favorite ones that include some indie web stuff max bulk Mattias OTT Jeremy Keith Charlie Owen Erin Pirozhki and Paul Paul Robert Lloyd I've really done a nice job with their sites [View Highlight](https://read.readwise.io/read/01j55sdfykg3xfaj3ehnwj2rf4)) [[design]] 
+
--- a/_master_wiki/void/Readwise/PARA
+++ b/_master_wiki/void/Readwise/PARA
@ -0,0 +1,27 @@
+# PARA Method and Zettelkasten: What’s The Difference?
+
+![rw-book-cover](https://rdl.ink/render/https%3A%2F%2Fmattgiaro.com%2Fpara-method-and-zettelkasten%2F)
+
+## Metadata
+- Author: [[mattgiaro]]
+- Full Title: PARA Method and Zettelkasten: What’s The Difference?
+- Category: #articles
+- Document Tags: [[notetaking]] [[productivity]] 
+- URL: https://mattgiaro.com/para-method-and-zettelkasten/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=PARA%20Method%20and%20Zettelkasten%3A%20What%E2%80%99s%20The%20Difference%3F
+> [!tldr]
+> The PARA method organizes digital information into Projects, Areas, Resources, and Archive, focusing on actionability. In contrast, Zettelkasten is a note-taking method that emphasizes linking ideas without a strict structure to foster new insights. While both methods can be used together, they serve different purposes and should not be confused.
+
+## Highlights
+PARA is an acronym for Projects, Areas, Resources, and Archive. 
+It’s a way of organizing all digital information. 
+Re-read this sentence again. [View Highlight](https://read.readwise.io/read/01j6mjrgpc2gnjjwzpzyr7ndgc))
+
+the Zettelkasten is a note-taking method. it focuses on links between notes and how to think in associations.
+When dissecting and studying the Zettelkasten method, you see that all notes are contained within ONE slip box, and are linked between them.
+There is absolutely no structure. [View Highlight](https://read.readwise.io/read/01j6mjs40nymdj2zsnjk4rwm42))
+
+**Zettelkasten is a note-taking method designed to spart new insights. PARA is not. It’s a way of organizing files and information for a specific project.** [View Highlight](https://read.readwise.io/read/01j6mjsp1f97yprmm81h7c6nn7))
+
+So people who look to implement the zettelkasten methodology using PARA didn’t get the point of both methodologies. [View Highlight](https://read.readwise.io/read/01j6mjxkq0a5z7m3w967zj3xxz))
+
--- a/_master_wiki/void/Readwise/Practical
+++ b/_master_wiki/void/Readwise/Practical
@ -0,0 +1,17 @@
+# Practical Concurrency in Go - GoRoutines, Mutexes, Channels and More
+
+![rw-book-cover](https://i.ytimg.com/vi/X24qXb4uWms/maxresdefault.jpg)
+
+## Metadata
+- Author: [[eldr-io]]
+- Full Title: Practical Concurrency in Go - GoRoutines, Mutexes, Channels and More
+- Category: #articles
+- Document Tags: [[dev]] [[dev/go]] 
+- URL: https://youtube.com/watch?v=X24qXb4uWms&si=rsxeM5e_FgY5RCIg
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Practical%20Concurrency%20in%20Go%20-%20GoRoutines%2C%20Mutexes%2C%20Channels%20and%20More
+> [!tldr]
+> The video tutorial demonstrates how to create a concurrent currency exchange API using Go. It explains how to fetch currency rates simultaneously by utilizing goroutines and channels. The goal is to efficiently manage multiple API calls to retrieve currency data.
+
+## Highlights
+We don't really want to spin up a  thousand threads just to do API calls. What we   want instead is we want a worker pool of threads  that can basically, whenever they're available,   pick up work, and then they can do the work and  then return a result, and then they can pick up   the next work until there's no more work to be  done. And this is a great pattern called a worker   pattern or worker pool pattern. [View Highlight](https://read.readwise.io/read/01j7ngcdm7y0mhae1x7a524k9q))
+
--- a/_master_wiki/void/Readwise/Project
+++ b/_master_wiki/void/Readwise/Project
@ -0,0 +1,63 @@
+# Project People vs. Area People: Are You Running a Sprint Or a Marathon?
+
+![rw-book-cover](https://i0.wp.com/fortelabs.com/wp-content/uploads/2020/02/cropped-cropped-Icon_Red-1.png?fit=192%2C192&ssl=1)
+
+## Metadata
+- Author: [[Tiago Forte]]
+- Full Title: Project People vs. Area People: Are You Running a Sprint Or a Marathon?
+- Category: #articles
+- Document Tags: [[productivity]] 
+- URL: https://fortelabs.com/blog/project-people-vs-area-people-are-you-running-a-sprint-or-a-marathon/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Project%20People%20vs.%20Area%20People%3A%20Are%20You%20Running%20a%20Sprint%20Or%20a%20Marathon%3F
+
+> [!note]
+> Goal: The intent is to enhance productivity by effectively organizing tasks into projects and areas of responsibility, enabling better focus and balance in work and life.
+> - [ ] 🗓️ **Establish a daily routine** to create structure and consistency in work and personal life.
+> - [ ] 🎯 **Set specific deadlines** for tasks to promote urgency and focus on achieving desired outcomes.
+> - [ ] 🌳 Take regular breaks and engage in nature to recharge and maintain mental clarity.
+> - [ ] 📝 **Maintain a journal** to reflect on thoughts and anxieties, aiding in self-awareness and emotional balance.
+> - [ ] 🌟 **Evaluate the balance** between project-focused work and ongoing areas of responsibility to ensure sustainable productivity.
+> - [ ] 🚀 **Break larger projects into smaller tasks** with milestones to track progress and maintain motivation. 
+> - [ ] 🧘‍♂️ Integrate a mindful practice, such as meditation, to cultivate awareness and reduce stress.
+> [!tldr]
+> The author, Tiago Forte, suggests organizing work into two categories: projects, which are short-term tasks with specific outcomes, and areas of responsibility, which are ongoing aspects of life that require maintenance. He emphasizes the importance of balancing both, as projects provide excitement and achievement, while areas foster peace and fulfillment. By understanding and managing these categories effectively, individuals can improve their productivity and well-being.
+
+## Highlights
+A **project** is any endeavor that has:
+1) A desired *outcome* that will enable you to mark it “complete”
+2) A *deadline* or timeframe by which you’d like it done. [View Highlight](https://read.readwise.io/read/01j5p8akz4t1csffcf6ps9rj56))
+
+An **area of responsibility** has 1) a *standard* to be maintained that 2) is continuous over time. [View Highlight](https://read.readwise.io/read/01j5p8aqhhnkykx9aw3f5jk4an))
+
+Areas are crucial to your wellbeing, security, fulfillment, and peace of mind. Whereas projects have outcomes, areas have *standards* *of performance* that you want to maintain. [View Highlight](https://read.readwise.io/read/01j5p8ex5f82m4zjkzte47n5f1))
+
+Once you view your life through the lens of discrete projects and continuous areas, it becomes clear that both of these structures are essential. Projects bring you excitement, achievement, and recognition, whereas areas bring you balance, peace, and meaning. [View Highlight](https://read.readwise.io/read/01j5p8h36864xvfwed8kx1wbv3))
+
+Every project requires a “heavy lift” to some degree, but those heavy lifts are far more powerful and effective (and brief) when you’ve already been collecting material in a “slow burn.” __It is only when heavy lifts become a chronic, default way of approaching everything that they lead to burnout and exhaustion__. [View Highlight](https://read.readwise.io/read/01j5p8mmxvbt84hm0zh4ecky0p))
+
+“Project people” are good at sprints. Give them a clear goal and a path to get there, and they will ferociously chase after it with everything they have. [View Highlight](https://read.readwise.io/read/01j5p8nq7mx2gcg1bkbebk7jb7))
+
+But the weakness of sprinters is that once they’ve reached their goal, they will often have trouble keeping it going. They will often change direction and run after the next goal, leaving their past achievements to wither. Sprinters are prone to starting many things and getting obsessed for a short time, before moving abruptly to something else. [View Highlight](https://read.readwise.io/read/01j5p8ph0pee8fazkr6jcn9e52))
+
+“Area people” excel at marathons. Send them on a long journey with some supplies and they will doggedly keep at it for as long as it takes. [View Highlight](https://read.readwise.io/read/01j5p8pnmq54457hb2a9fwkyby))
+
+The weakness of marathoners is that they often have trouble generating a lot of power on short notice. When an opportunity opens up that requires quick, decisive action, they’ll have difficulty changing direction and drawing down their reserves to chase it down [View Highlight](https://read.readwise.io/read/01j5p8q8wmf4j78vppmcst8fe4))
+
+Projects require you to be **laser-focused,** to ferociously drive toward an outcome, **to overcome or circumvent obstacles**, and to **ignore distractions along the way**. Areas, on the other hand, require **mindfulness, balance, and reflection**. This is the realm of **habits, rituals, and intentional communities**. Whereas projects tend to be more black and white, areas require more introspection and self-awareness because it takes more nuance to decide if you are meeting your standard in a given area. [View Highlight](https://read.readwise.io/read/01j5p8zgbrdb2x0dc8v9aba3pc))
+
+If you are a “Project person” and want to improve your ability to sustain your areas, here are some techniques you can try:
+• Adopt a morning or evening routine
+• Set limits to your working hours
+• Take regular breaks and walks in nature
+• Journal and write out your internal anxieties and thoughts
+• Create a meditation habit (or other mindful habit)
+• Set your intentions each day, week, month, or year
+• Evaluate your schedule for a balance of intense work and healthy, mindful activities [View Highlight](https://read.readwise.io/read/01j5p94wamdw1k24avskcd8vd2)) [[review/plan]] [[favorite]] 
+> [!note]
+> Implement
+
+We all know the importance of work-life balance and healthy boundaries, but once in a while we have to let all that go and focus every ounce of energy we have on a singular outcome. This is, by definition, unsustainable. But that is why it’s so important to move fast and break through barriers as quickly as possible: __the faster you reach your objective, the sooner you can stop to rest and recover__. [View Highlight](https://read.readwise.io/read/01j5p9bh2gd06bbgmgyp9tn7ef))
+
+Some seasons of our lives are all about the journey, but others are more like sprints.
+*Source: [The Universe Will Now Explode for Your Pleasure](https://us1.campaign-archive.com/?u=78cbbb7f2882629a5157fa593&id=c4f01c7ab5) by Venkatesh Rao* [View Highlight](https://read.readwise.io/read/01j5p9fyk6bjw8gg0v5n09q5yx))
+
--- a/_master_wiki/void/Readwise/Psychological
+++ b/_master_wiki/void/Readwise/Psychological
@ -0,0 +1,33 @@
+# Psychological Safety Is Critical for High-Performing Teams
+
+![rw-book-cover](https://cdn.stackoverflow.co/images/jo7n4k8s/production/7aebe88c0b5d91d2b212b405326d45070ea6f928-2400x1260.jpg?w=1200&fm=png&auto=format)
+
+## Metadata
+- Author: [[Stack Overflow Blog]]
+- Full Title: Psychological Safety Is Critical for High-Performing Teams
+- Category: #articles
+- Document Tags: [[mental-health]] [[productivity]] [[work]] 
+- URL: https://stackoverflow.blog/2022/01/27/psychological-safety-is-critical-for-high-performing-teams/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Psychological%20Safety%20Is%20Critical%20for%20High-Performing%20Teams
+> [!tldr]
+> Psychological safety is crucial for high-performing teams. It refers to creating a work environment where employees feel safe to speak up, share ideas, and discuss failures without fear of punishment or humiliation. When teams feel psychologically safe, they are more willing to take risks, collaborate, and put in discretionary effort. Evaluating the level of psychological safety in an organization can be done by assessing factors such as tolerance for mistakes, micro-moments of learning, space for reflection and review, encouragement of risk-taking, and diversity of thought. Creating a psychologically safe workplace requires ongoing effort and a combination of factors including company values, leadership qualities, and supportive technology.
+
+## Highlights
+According to [Amy Edmondson](https://www.hbs.edu/faculty/Pages/profile.aspx?facId=6451), “psychological safety in the workplace is the belief that the environment is safe for interpersonal risk-taking. It is a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.” [View Highlight](https://read.readwise.io/read/01j93vhyxhk5j2b15nwatff18r))
+
+When employees feel psychologically safe, they’re willing to take more risks, share ideas, and speak their truth. There is an unspoken agreement that employees will not feel punished or embarrassed when speaking up, whether it’s exposing one’s ignorance by asking questions or offering a new solution or idea to a problem. Trust is created through interpersonal connections and reinforced through an open and transparent environment. [View Highlight](https://read.readwise.io/read/01j93vk913rzjpbgwkzkfsv4pb))
+
+By having a psychologically safe environment, employees perceive risk as a good thing, and there is an understanding that employees won’t be seen as ignorant, incompetent, or invalid. [View Highlight](https://read.readwise.io/read/01j93vpnspqs7wcbqp8rv2q64h))
+
+Risk-taking and learning from mistakes so the team doesn’t repeat them again are behaviors of high-performing teams. [View Highlight](https://read.readwise.io/read/01j93vp6hf2wnjgzjecqrqbd1t))
+
+There is a tolerance for mistakes [View Highlight](https://read.readwise.io/read/01j93vthzdva8gc9yhaajf5bv5))
+
+Micro-moments of learning occur regularly [View Highlight](https://read.readwise.io/read/01j93vtre343brwez6m6rft2d9))
+
+Space is created for reflection and review [View Highlight](https://read.readwise.io/read/01j93vx25zbxmr5xf4rw12mhyh))
+
+Risk-taking is encouraged [View Highlight](https://read.readwise.io/read/01j93vybefn6z629f6q03y7f4z))
+
+There is a diversity of thought [View Highlight](https://read.readwise.io/read/01j93wdk43srd38dar2f08afwb))
+
--- a/_master_wiki/void/Readwise/Reader
+++ b/_master_wiki/void/Readwise/Reader
@ -0,0 +1,16 @@
+# Reader: Frequently Asked Questions
+
+![rw-book-cover](https://s3.amazonaws.com/readwiseio/2022/12/reader-logo.jpg)
+
+## Metadata
+- Author: [[Daniel Doyon]]
+- Full Title: Reader: Frequently Asked Questions
+- Category: #articles
+- URL: https://blog.readwise.io/p/f8c0f71c-fe5f-4025-af57-f9f65c53fed7/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Reader%3A%20Frequently%20Asked%20Questions
+> [!tldr]
+> You can save articles to Reader using the browser extension or the mobile app, and highlights sync with Readwise. Reader allows you to highlight text and images while reading on the web, and all highlights are accessible in the app and synced to your note-taking apps. To manage your articles, you can move them to your Library and create custom views based on your preferences.
+
+## Highlights
+![](https://readwise-community.ghost.io/content/images/2024/01/CleanShot-2024-01-27-at-16.50.32@2x.png) [View Highlight](https://read.readwise.io/read/01j53426gkd6xdb1bkxftyezfd))
+
--- a/_master_wiki/void/Readwise/Remember
+++ b/_master_wiki/void/Readwise/Remember
@ -0,0 +1,28 @@
+# Remember Everything With This Pocket Notebook System
+
+![rw-book-cover](https://i.ytimg.com/vi/swC4MAryYRw/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Eric Pfohl]]
+- Full Title: Remember Everything With This Pocket Notebook System
+- Category: #articles
+- Document Tags: [[notetaking]] 
+- URL: https://www.youtube.com/watch?v=swC4MAryYRw
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Remember%20Everything%20With%20This%20Pocket%20Notebook%20System
+> [!tldr]
+> A Commonplace Notebook is a helpful tool for collecting and organizing ideas, quotes, and details from various sources like books and podcasts. It allows you to document wisdom in one place, making it easier to reference later. Using pen and paper for this process can enhance your memory and creativity.
+
+## Highlights
+a Commonplace Notebook is a way to collect details around you that are relevant to you in some way rather than writing things down introspectively like a diary or Journal would be a Commonplace Notebook is a way to document things only from external sources [View Highlight](https://read.readwise.io/read/01j70zaykjztys0bef0xp5ef4e))
+
+they allow you to document and collect any ideas in a singular place that you can refer back to at any time [View Highlight](https://read.readwise.io/read/01j70zcrej9xvmp5905czk027r))
+
+if you're somebody like me who likes organization the thought of just a bunch of random ideas on the pages seems a little bit overwhelming and messy but honestly the organization of your Commonplace Notebook is nothing to worry about our thoughts ideas and minds are constantly going in a million different directions and realistically your Commonplace Notebook is going to be an extension of
+that [View Highlight](https://read.readwise.io/read/01j70zkh7h2rtdjrptg01f854g))
+
+one way to do this is to leave the first page or two of your notebook blank so that way when you fill the notebook you can put an index on those blank pages [View Highlight](https://read.readwise.io/read/01j70znccjr4srj337fdjqmw79))
+
+you can highlight certain categories in specific colors or you can even write in different colored inks depending on the topic [View Highlight](https://read.readwise.io/read/01j70zp3p890b8kdqx21w2gqm8))
+
+with a Commonplace Notebook I do think is a great idea to collect your observed details and expand upon them further through writing [View Highlight](https://read.readwise.io/read/01j70zrzc6s2g9x9768b2596qa))
+
--- a/_master_wiki/void/Readwise/SIMPLIFY
+++ b/_master_wiki/void/Readwise/SIMPLIFY
@ -0,0 +1,17 @@
+# SIMPLIFY Your Python Code With the Facade Pattern
+
+![rw-book-cover](https://i.ytimg.com/vi/tCzmda1VCUQ/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Isaac Harris-Holt]]
+- Full Title: SIMPLIFY Your Python Code With the Facade Pattern
+- Category: #articles
+- Document Tags: [[dev]] [[dev/design-patterns]] 
+- URL: https://www.youtube.com/watch?v=tCzmda1VCUQ
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=SIMPLIFY%20Your%20Python%20Code%20With%20the%20Facade%20Pattern
+> [!tldr]
+> The facade pattern is a design approach that simplifies complex code by providing a user-friendly interface. It helps developers hide underlying complexities, making it easier to work with libraries and frameworks. By using this pattern, you can create cleaner and more efficient Python code.
+
+## Highlights
+You could think of the facade pattern almost like a wrapper around one or many complex subsystems making them **easier to interact with**. [View Highlight](https://read.readwise.io/read/01j5qry2jq70c28ebz4zdeqe8z)) [[dev]] 
+
--- a/_master_wiki/void/Readwise/SQLite
+++ b/_master_wiki/void/Readwise/SQLite
@ -0,0 +1,62 @@
+# SQLite is not a toy database
+
+![rw-book-cover](https://antonz.org/assets/2021/sqlite-is-not-a-toy-database.png)
+
+## Metadata
+- Author: [[Anton Zhiyanov]]
+- Full Title: SQLite is not a toy database
+- Category: #articles
+- Document Tags: [[dev]] [[dev/sql]] 
+- URL: https://antonz.org/sqlite-is-not-a-toy-database/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=SQLite%20is%20not%20a%20toy%20database
+
+> [!note]
+> **Background:** Utilize SQLite for a wider array of applications beyond merely functioning as a basic data storage solution.
+> ### Key Takeaways:
+> 📊 **Leverage Advanced Indexing Capabilities:** 
+> SQLite supports partial indexes and indexes on expressions, enabling the creation of efficient indexes on generated columns. This functionality allows users to transform SQLite into a document database by storing raw JSON and indexing on extracted JSON fields.
+> 📝 **Utilize Built-in Statistical Functions:** 
+> SQLite makes it easy to perform descriptive statistics, such as calculating mean, median, and percentiles, with minimal setup. By loading the sqlite3-stats extension, users can execute complex statistical queries in a straightforward manner, enhancing data analysis capabilities.
+> 📁 **Seamless JSON Data Handling:** 
+> SQLite excels at analyzing and transforming JSON data, allowing users to directly query JSON files as if they were regular tables. This feature simplifies data manipulation, making it convenient for users to extract and analyze JSON information efficiently.
+> [!tldr]
+> SQLite is highlighted as a versatile tool suitable for developers, data analysts, and various professionals due to its widespread use, serverless nature, and ease of integration. The database console feature is particularly praised for its data analysis capabilities and simplicity, offering powerful functions like CSV import, SQL query support, and various export options. Additionally, SQLite's compatibility with data exploration tools and its efficiency in processing large datasets make it a robust choice for those working with JSON, Common Table Expressions, set operations, generated columns, and mathematical statistics. The document also touches on SQLite's performance capabilities, handling hundreds of millions of records efficiently, with insert speeds improving when connecting CSV files as virtual tables.
+
+## Highlights
+The console is a killer SQLite feature for data analysis: more powerful than Excel and more simple than `pandas`. One can import CSV data with a single command, the table is created automatically:
+> .import --csv city.csv city
+> select count(*) from city;
+1117 [View Highlight](https://read.readwise.io/read/01j6hehc1ap6yxya4135j8z7d1))
+
+Data could be exported as SQL, CSV, JSON, even Markdown and HTML. Takes just a couple of commands:
+.mode json
+.output city.json
+select city, foundation_year, timezone from city limit 10;
+.shell cat city.json [View Highlight](https://read.readwise.io/read/01j6hekgzt1yg4dse4xt6kqec4))
+
+There is nothing more convenient than SQLite for analyzing and transforming JSON. You can select data directly from a file as if it were a regular table. Or import data into the table and select from there.
+select
+json_extract(value, '$.iso.code') as code,
+json_extract(value, '$.iso.number') as num,
+json_extract(value, '$.name') as name,
+json_extract(value, '$.units.major.name') as unit
+from
+json_each(readfile('currency.sample.json'))
+; [View Highlight](https://read.readwise.io/read/01j6henb91d2vd1d43x4yj6e5w))
+
+Descriptive statistics? Easy: mean, median, percentiles, standard deviation, you name it. You’ll have to load an extension, but it’s also a single command (and a single file).
+.load sqlite3-stats
+select
+count(*) as book_count,
+cast(avg(num_pages) as integer) as mean,
+cast(median(num_pages) as integer) as median,
+mode(num_pages) as mode,
+percentile_90(num_pages) as p90,
+percentile_95(num_pages) as p95,
+percentile_99(num_pages) as p99
+from books; [View Highlight](https://read.readwise.io/read/01j6hev7qj7qyszxhwft53r1w9))
+
+There is a popular opinion among developers that SQLite is not suitable for the web, because it doesn’t support concurrent access. ... the write-ahead log mode ... there can be as many concurrent readers as you want. There can be only one concurrent writer, but often one is enough.
+
+SQLite supports partial indexes and indexes on expressions, as ‘big’ DBMSs do. You can build indexes on generated columns and even turn SQLite into a document database. Just store raw JSON and build indexes on `json_extract()`-ed columns [View Highlight](https://read.readwise.io/read/01j6hf4c5250yyf6871sphxenm))
+
--- a/_master_wiki/void/Readwise/Sharing
+++ b/_master_wiki/void/Readwise/Sharing
@ -0,0 +1,27 @@
+# Sharing Code Between Projects: Lessons Learned in the Trenches
+
+![rw-book-cover](https://archive.smashing.media/assets/344dbf88-fdf9-42bb-adb4-46f01eedd629/adc3be2f-343a-4bee-8ee8-2cec63967354/01-sharing-code-between-projects-800w.png)
+
+## Metadata
+- Author: [[Smashing Magazine]]
+- Full Title: Sharing Code Between Projects: Lessons Learned in the Trenches
+- Category: #articles
+- URL: https://www.smashingmagazine.com/2018/04/sharing-code-between-projects/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Sharing%20Code%20Between%20Projects%3A%20Lessons%20Learned%20in%20the%20Trenches
+> [!tldr]
+> Jonathan Saring discusses the challenges of sharing code between projects and the lessons learned by his team. They found that code duplication was widespread and sought a better way to share components without the complexities of multiple repositories or libraries. This led to the creation of Bit, a tool that simplifies code sharing and collaboration across projects.
+
+## Highlights
+Trying to publish a few files from our project to NPM forced us to split our repository and create new ones just to share this code. When dealing with hundreds of components, **this meant having to maintain and make changes across hundreds of repositories**. [View Highlight](https://read.readwise.io/read/01j7c7r70prgze7nhnwf9mrvyb))
+
+Even then, we had now a simple way to organize these packages and make them easily [discoverable](https://medium.com/@Rich_Harris/small-modules-it-s-not-quite-that-simple-3ca532d65de4#.88d5anyhv) to our entire team. Another major problem was the coupling between the packages and the owners of their origin repositories, which made it nearly impossible for other people to quickly make updates to the packages while working on their own projects. [View Highlight](https://read.readwise.io/read/01j7c7snv6bz7w24x6v99zar37))
+
+Choosing this option meant we would still have to effectively keep multiple packages with multiple `package.json` files, multiple build and test environments and a complicated dependency tree to handle between them. Updating these packages must also go through the main repository, still making it hard to modify these package from other projects when working with a few separate monorepos. [View Highlight](https://read.readwise.io/read/01j7c7tyqzf8z4ns8sr35gstvb))
+
+This option was quickly dropped, too. In a lot of way, it resembles using a CD-ROMs instead of an iTunes playlist. First, it made no sense to force an entire library of React components and an entire utility library and so on on each of our projects.
+Secondly, every project using it would be tightly coupled to the development of this library, making it impossible to adjust its components for each project. This becomes most painful when sharing common Node.js code between our microservices, which would now be coupled to the library.
+Thirdly, discoverability within the library is bound to be poor and would involve a lot of work with its documentation and usage in different edge cases. [View Highlight](https://read.readwise.io/read/01j7c7x4br1vpa6peckn8f04x1))
+
+You there. You're thinking about using a Git submodule. DON'T. Just don't. It's not worth it, ever.
+— Jeremy Kahn (@jeremyckahn) [December 16, 2012](https://twitter.com/jeremyckahn/status/280406794583539712?ref_src=twsrc%5Etfw) [View Highlight](https://read.readwise.io/read/01j7c7zhs027w5jac3mg71v905))
+
--- a/_master_wiki/void/Readwise/Site
+++ b/_master_wiki/void/Readwise/Site
@ -0,0 +1,35 @@
+# Site Design Standards
+
+![rw-book-cover](https://seirdy.one/favicon512.63ee1da7ff5f42b764febf0cf7a793b5.png)
+
+## Metadata
+- Author: [[Rohan Kumar]]
+- Full Title: Site Design Standards
+- Category: #articles
+- Document Tags: [[dev]] [[indie-web]] 
+- URL: https://seirdy.one/meta/site-design/#static-indieweb
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Site%20Design%20Standards
+> [!tldr]
+> The website seirdy.one focuses on high accessibility standards, adhering to most Web Content Accessibility Guidelines (WCAG) while continuously improving link purpose clarity. It is compatible with various browsers, including older ones, and uses semantic, well-structured markup to enhance content accessibility. The site also incorporates IndieWeb features, allowing interactions like Webmentions, while planning future enhancements.
+
+## Highlights
+I only set custom colors in response to the `prefers-color-scheme: dark` media query. These custom colors have an Advanced Perceptual Contrast Algorithm (APCA) lightness contrast close to the ideal value of 90. I use autism- and overstimulation-friendly colors: the yellow links have low saturation to reduce harshness. [View Highlight](https://read.readwise.io/read/01j6q0y08pr5az55kbqx1za16z)) [[design]] 
+> [!note]
+> Be carefull with over stimulation design
+
+I run axe-core, the IBM Equal Access Accessibility Checker, the Nu HTML Checker (local build, latest commit), and webhint on every page in my sitemap. After filtering out false-positives (and reporting them upstream), I receive no errors. I repeat this run with every change to my Hugo templates and stylesheets. [View Highlight](https://read.readwise.io/read/01j6q1k4ha86p96pnhz2m9szcp)) [[dev/accesibility]] 
+
+This website conforms to Web standards. Each build runs `xmllint` to catch syntax errors. Every few commits, I run a local build of [the Nu HTML Checker](https://github.com/validator/validator) and [html proofer](https://github.com/gjtorikian/html-proofer), and see no errors. I do [filter out false Nu positives](https://git.sr.ht/~seirdy/seirdy.one/tree/master/item/linter-configs/vnu_filter.jq), and I [report and fix false-positives](https://github.com/w3c/css-validator/issues?q=author%3ASeirdy) when possible. [View Highlight](https://read.readwise.io/read/01j6q1vgnhs9b2rqh77xxw9y5v)) [[dev/web-dev]] 
+
+[The IndieMark page](https://indieweb.org/IndieMark) lists all the ways you can “IndieWeb-ify” your site. [View Highlight](https://read.readwise.io/read/01j6q2cs5dpg7dc3qb130600n8)) [[indie-web]] 
+
+IndieWeb features implemented
+I’ve implemented several features from IndieMark:
+• IndieAuth compatibility, using the external [IndieLogin.com service](https://indielogin.com/).
+• Microformats: representative `h-card`, in-text `h-card` and `h-cite` when referencing works, `h-feed`.
+• Sending and receiving Webmentions. I receive Webmentions with [webmentiond](https://github.com/zerok/webmentiond), and send them from my own computer using [Pushl](https://github.com/PlaidWeb/Pushl/).
+• Displaying Webmentions: I render backlinks, IndieWeb “likes” (not silo likes), and comments below posts. I model their appearance after Tumblr’s display of interactions.
+• Backfeeding content from silos: I’m only interested in backfilled content containing discussion, not “reactions” or “likes”. Powered by [Bridgy](https://brid.gy/). [View Highlight](https://read.readwise.io/read/01j6q2a4dcrmq9eegvrsgz1hja)) [[indie-web]] 
+
+IndieWeb sites need not implement *every* IndieWeb standard. Progressive enhancement and graceful degradation let me implement interesting features, and skip less interesting ones. Skipped features include: [View Highlight](https://read.readwise.io/read/01j6q2j1gyftbdbr59hsggy34t))
+
--- a/_master_wiki/void/Readwise/Software
+++ b/_master_wiki/void/Readwise/Software
@ -0,0 +1,29 @@
+# Software Deployment Models – Explained for Beginners
+
+![rw-book-cover](https://www.freecodecamp.org/news/content/images/2024/01/pexels-joshua-135018--1-.jpg)
+
+## Metadata
+- Author: [[freeCodeCamp.org]]
+- Full Title: Software Deployment Models – Explained for Beginners
+- Category: #articles
+- Document Tags: [[dev]] 
+- URL: https://www.freecodecamp.org/news/software-deployment-models/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Software%20Deployment%20Models%20%E2%80%93%20Explained%20for%20Beginners
+> [!tldr]
+> Software deployment models refer to the different ways in which software code can be deployed. This article explores various deployment models, including client/server computing, thin and fat client architectures, microservices, and Application Programming Interfaces (APIs). Client/server computing involves splitting computing tasks between clients and servers, with clients making requests and servers providing services or resources. Thin client architectures place most of the processing on the server side, while fat client architectures handle both the presentation layer and application logic on the client machine. Microservices involve dividing applications into smaller, independent services that communicate over a network, while APIs enable communication and integration between different software applications. The article also briefly touches on web applications, single page applications (SPAs), and different types of APIs, such as open APIs and REST APIs.
+
+## Highlights
+Client/server computing architectures are a type of distributed computing architecture in which computing tasks are split between two types of machines: clients and servers. [View Highlight](https://read.readwise.io/read/01j59dqe78wf56va1yz6gb3df0))
+
+The client/server architecture provides several advantages, including:
+• Scalability, meaning that servers can be added or removed from the network as demand changes. This allows the system to scale up or down as needed without having to make changes on the clients.
+• Centralization, which means that by centralizing resources on servers, it is easier to manage and control access to those resources, and to enforce security policies. [View Highlight](https://read.readwise.io/read/01j59dqwmj1saw3r59nt5qy2v8))
+
+In a *thin* client architecture, the client machine is responsible for only the presentation layer, while the application logic and data processing are handled on the server side. __Thin clients typically have limited processing power and memory, and rely heavily on network connectivity to function__. [View Highlight](https://read.readwise.io/read/01j59drt66pd1rvgzhqdk6jvae))
+
+On the other hand, in a *fat* client architecture, the client machine is responsible for both the presentation layer and the application logic. The client machine typically has more processing power and memory, and can execute code and process data locally. [View Highlight](https://read.readwise.io/read/01j59dtzv6kms42sp02x7p6rz6))
+
+Now, should you design your software as a microservices or monolith architecture? In a *monolith* architecture, the entire application is built as a single, self-contained unit. All functionality, from data access to user interface, is bundled together in one codebase and deployed as a single unit. [View Highlight](https://read.readwise.io/read/01j59dx0jgkzhxpcsrbvhmb8p5))
+
+Web applications are software applications that are accessed through a web browser over a network such as the Internet. The purpose of web applications is to provide users with a convenient and accessible way to perform various tasks and access services over the web. [View Highlight](https://read.readwise.io/read/01j59dzd3j41bgbampr7rqjsxd))
+
--- a/_master_wiki/void/Readwise/Stateful
+++ b/_master_wiki/void/Readwise/Stateful
@ -0,0 +1,18 @@
+# Stateful vs. Stateless Applications — Differences, Pros & Cons, Use Cases
+
+![rw-book-cover](https://miro.medium.com/v2/resize:fit:1060/1*4FjP5a8XoDB7LnIhJWlWQA.jpeg)
+
+## Metadata
+- Author: [[Neal Davis]]
+- Full Title: Stateful vs. Stateless Applications — Differences, Pros & Cons, Use Cases
+- Category: #articles
+- URL: https://neal-davis.medium.com/stateful-vs-stateless-applications-differences-pros-cons-use-cases-ad4b434576b8
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Stateful%20vs.%20Stateless%20Applications%20%E2%80%94%20Differences%2C%20Pros%20%26%20Cons%2C%20Use%20Cases
+> [!tldr]
+> Stateful applications remember user interactions and store data between sessions, while stateless applications do not retain any user information. This choice affects how applications are designed, their scalability, and the resources they require. Developers must weigh the pros and cons of each type to meet their project needs effectively.
+
+## Highlights
+Stateful applications save info about the user’s “state” by keeping track of what they do. [View Highlight](https://read.readwise.io/read/01j7pd95t5qyvwt98kv86bmcbf))
+
+Stateless software applications are those applications that do not save information about previous interactions, user sessions, or events. These applications do not preserve context or state between requests in a stateless design. [View Highlight](https://read.readwise.io/read/01j7pdbyyxz2g1ems20te5d6ez))
+
--- a/_master_wiki/void/Readwise/THE
+++ b/_master_wiki/void/Readwise/THE
@ -0,0 +1,32 @@
+# THE ZETTELKASTEN MANIFESTO | What is a Zettelkasten?
+
+![rw-book-cover](https://zettlr.com/storage/app/media/img/social_media_img.png)
+
+## Metadata
+- Author: [[Zettlr]]
+- Full Title: THE ZETTELKASTEN MANIFESTO | What is a Zettelkasten?
+- Category: #articles
+- Document Tags: [[notetaking]] 
+- URL: https://www.zettlr.com/post/what-is-a-zettelkasten
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=THE%20ZETTELKASTEN%20MANIFESTO%20%7C%20What%20is%20a%20Zettelkasten%3F
+
+> [!note]
+> This is the definitive explanation of a Zettlelkasten
+> [!tldr]
+> Website traffic analytics show high interest in the Zettelkasten method, which is a knowledge management system. Users seek simple answers to complex problems of managing knowledge effectively. Structuring notes and self-reflection are key components of creating a personalized Zettelkasten system.
+
+## Highlights
+We live in a society that likes a dead-simple approach to problems; one solution each. But a Zettelkasten evades this 21st-century mindset. A Zettelkasten is a multitude of different approaches to a common problem — the problem of knowledge management. [View Highlight](https://read.readwise.io/read/01j60nacy93812ptm2c0fh226q))
+
+there is not *the* Zettelkasten approach — but one for every human being living on this planet. [View Highlight](https://read.readwise.io/read/01j62awnqp75y0p29mgp8werra)) [[notetaking]] 
+
+It does not help to copy a workflow by a different person, because a Zettelkasten must at all costs reflect the working habits of the person using it. [View Highlight](https://read.readwise.io/read/01j62b22nehaew7g0y0g2cw3fg))
+
+The first thing you must respect when beginning to structure your knowledge is exactly that: a certain structure. This is what people like us can explain to you and help you with. But the second thing is where you are completely on your own: self reflection. __To manage your knowledge, you have to know how you work__. [View Highlight](https://read.readwise.io/read/01j62b418gmqzv0j2ng9wg4pw6)) [[favorite]] 
+
+The structure of a Zettelkasten is fairly easy described: It's a database. It is simply a place where you file your knowledge in a semi-structured way. [View Highlight](https://read.readwise.io/read/01j62hpbfbv82tkf6kq9b3ddef))
+
+The more important part of a Zettelkasten therefore is self reflection. You need to be constantly on the watch for how *you* work. [View Highlight](https://read.readwise.io/read/01j62hsdeyxwtxf429t43ve5rb))
+
+Do not listen too much to too specific advises on how to start a Zettelkasten. Just start and use the structure *you* need. And stop reading tutorials on Zettelkästen. [View Highlight](https://read.readwise.io/read/01j62hvprnrb55xhvd525v03ww))
+
--- a/_master_wiki/void/Readwise/The
+++ b/_master_wiki/void/Readwise/The
@ -0,0 +1,39 @@
+# The Actor Model in 10 Minutes
+
+![rw-book-cover](https://www.brianstorti.com/assets/images/profile-small.png)
+
+## Metadata
+- Author: [[brianstorti.com]]
+- Full Title: The Actor Model in 10 Minutes
+- Category: #articles
+- URL: https://www.brianstorti.com/the-actor-model/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=The%20Actor%20Model%20in%2010%20Minutes
+> [!tldr]
+> The actor model is a conceptual model for concurrent computation that uses actors as the primitive unit of computation. Actors receive messages and perform computation based on them, similar to objects in object-oriented languages. Actors are isolated from each other and maintain a private state. Messages are sent asynchronously and stored in an actor's mailbox until processed. Actors can create more actors, send messages to other actors, and designate how to handle the next message. The actor model also allows for fault tolerance and distribution across multiple machines.
+
+## Highlights
+An actor is the primitive unit of computation. It’s the *thing* that receives a message and does some kind of computation based on it. [View Highlight](https://read.readwise.io/read/01j918hcacc07w4axvgt59x8zq))
+
+actors are completely isolated from each other and they will never share memory. It’s also worth noting that an actor can maintain a private state that can never be changed directly by another actor. [View Highlight](https://read.readwise.io/read/01j918j9h6jqm35fdy1vqcfpvd))
+
+In the actor model everything is an actor and they need to have addresses so one actor can send a message to another. [View Highlight](https://read.readwise.io/read/01j918ke4asb17p1z7nt58d46v))
+
+multiple actors can run at the same time, an actor will process a given message sequentially. [View Highlight](https://read.readwise.io/read/01j918nf2daeb5my4gfz7vq4vy))
+
+Messages are sent asynchronously to an actor, that needs to store them somewhere while it’s processing another message. The mailbox is the place where these messages are stored. [View Highlight](https://read.readwise.io/read/01j918p5c4xp37ry1q48rk46p7))
+
+![](https://www.brianstorti.com/assets/images/actors.png) [View Highlight](https://read.readwise.io/read/01j918m33wqavsptrvx0tt7pen))
+
+When an actor receives a message, it can do one of these 3 things:
+• Create more actors
+• Send messages to other actors
+• Designate what to do with the next message [View Highlight](https://read.readwise.io/read/01j918qs9pm600m7ywrjcwjwmb))
+
+“Designating what to do with the next message” basically means defining how this state will look like for the next message it receives. Or, more clearly, it’s how actors mutate state. [View Highlight](https://read.readwise.io/read/01j918r1sd8f8ajq9n0b44atyr))
+
+What `Erlang` does is simply letting it crash, but make this critical code be supervised by someone whose only responsibility is to know what to do when this crash happens (like resetting this unit of code to a stable state), and what makes it all possible is the actor model. [View Highlight](https://read.readwise.io/read/01j918v4a749ra9wqtaag6xrt4))
+
+This makes it possible to create systems that “self heal”, meaning that if an actor gets to an exceptional state and crashes, by whatever reason, a supervisor can do something about it to try to put it in a consistent state again [View Highlight](https://read.readwise.io/read/01j918xtyxjak1pwdav830pd8a))
+
+Another interesting aspect of the actor model is that it doesn’t matter if the actor that I’m sending a message to is running locally or in another node. [View Highlight](https://read.readwise.io/read/01j9192dk4wf5rj9ccpzhpfb29))
+
--- a/_master_wiki/void/Readwise/The
+++ b/_master_wiki/void/Readwise/The
@ -0,0 +1,34 @@
+# The Art of Finishing
+
+![rw-book-cover](https://www.bytedrum.com/assets/art-of-finishing/og.png)
+
+## Metadata
+- Author: [[emmorts]]
+- Full Title: The Art of Finishing
+- Category: #articles
+- URL: https://www.bytedrum.com/posts/art-of-finishing/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=The%20Art%20of%20Finishing
+> [!tldr]
+> The author discusses the challenge of finishing projects, highlighting the temptation to start new ones instead. They outline strategies to overcome procrastination, such as defining what "done" means and setting deadlines. Ultimately, the goal is to build the habit of completing projects to experience the satisfaction and growth that comes from finishing.
+
+## Highlights
+It’s the Hydra Project Effect: no matter how much progress I make, new challenges always seem to sprout in their place. [View Highlight](https://read.readwise.io/read/01j9rmxn4ng2c8zys41hfkqdq2))
+
+When a project is ongoing, it can be anything. It’s Schrödinger’s[1](https://www.bytedrum.com/posts/art-of-finishing/#user-content-fn-schrodinger) project—simultaneously perfect and flawed until you actually finish it and put it out into the world. [View Highlight](https://read.readwise.io/read/01j9rn0cnw6xcrfv3236ekfy1k))
+
+Before diving into a project, I’ll clearly define what “finished” looks like. What are the core features that constitute a complete project? I’ll write them down and resist the urge to expand this list as I go. [View Highlight](https://read.readwise.io/read/01j9tz2kvb3g5ytpbdkkjd88sy))
+
+**Embrace MVP**: Instead of aiming for perfection, I’ll aim for “good enough.” I’ll get a basic version working and out into the world. I can always iterate and improve later. [View Highlight](https://read.readwise.io/read/01j9tz46f5mr2wf3d6nzn7hgq0))
+
+**-Box My Projects**: I’ll give myself a deadline. It doesn’t have to be short, but it should be finite. Having an end date creates urgency and helps me prevent endless feature creep. [View Highlight](https://read.readwise.io/read/01j9tz4wxc2jhwk7npbhp9km0z))
+
+I’ll build my “finishing muscle” by completing small projects or tasks regularly. I recognize that the skill of finishing is like any other—it improves with practice. This could be as simple as finishing a blog post or completing a small coding challenge each week. [View Highlight](https://read.readwise.io/read/01j9tz6d7dmmmnhpmcq5w97hgz))
+
+When new features or project ideas pop up during implementation, I’ll jot them down for future consideration instead of immediately acting on them. This helps maintain focus on the current project while still capturing potentially valuable ideas. [View Highlight](https://read.readwise.io/read/01j9tz748wp0dznk73afv1chm7))
+
+I’ll celebrate when I complete a project, no matter how small. This positive reinforcement can help shift my mindset towards completion. [View Highlight](https://read.readwise.io/read/01j9tz8xdbyvk47smjy3nkghqs))
+
+External accountability adds motivation and support to the often solitary journey of personal projects.[3](https://www.bytedrum.com/posts/art-of-finishing/#user-content-fn-accountability-study) [View Highlight](https://read.readwise.io/read/01j9tza1jjcf360gr4z6gaka63))
+
+This phenomenon is closely related to [Parkinson’s Law](https://en.wikipedia.org/wiki/Parkinson%27s_law#First_meaning), which states that “work expands so as to fill the time available for its completion.” In personal projects, the available time is often infinite, leading to endless expansion. [↩](https://www.bytedrum.com/posts/art-of-finishing/#user-content-fnref-parkinson-law) [View Highlight](https://read.readwise.io/read/01j9tzeefxcvyb8yx4499ndgev)) [[quotes]] 
+
--- a/_master_wiki/void/Readwise/The
+++ b/_master_wiki/void/Readwise/The
@ -0,0 +1,53 @@
+# The Composition Over Inheritance Principle¶
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article1.be68295a7e40.png)
+
+## Metadata
+- Author: [[python-patterns.guide]]
+- Full Title: The Composition Over Inheritance Principle¶
+- Category: #articles
+- URL: https://python-patterns.guide/gang-of-four/composition-over-inheritance/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=The%20Composition%20Over%20Inheritance%20Principle%C2%B6
+> [!tldr]
+> The Composition Over Inheritance principle emphasizes that using composition (combining classes) is often more effective than inheritance (subclassing) for managing complexity in code. By employing design patterns like Adapter, Bridge, and Decorator, developers can create flexible logging systems that separate filtering from logging behavior. This approach allows for easier maintenance and the ability to mix and match different filters and handlers at runtime without creating a large number of subclasses.
+
+## Highlights
+Favor object composition over class inheritance. [View Highlight](https://read.readwise.io/read/01j8bahv00beg9tchtr4b8hkem))
+
+A crucial weakness of inheritance as a design strategy is that a class often needs to be specialized along several different design axes at once, leading to what the Gang of Four call “a proliferation of classes” in their Bridge chapter and “an explosion of subclasses to support every combination” in their Decorator chapter. [View Highlight](https://read.readwise.io/read/01j8bakccctxe895jka6vmvdyw))
+
+The total number of classes will increase geometrically if *m* and *n* both continue to grow. This is the “proliferation of classes” and “explosion of subclasses” that the Gang of Four want to avoid. [View Highlight](https://read.readwise.io/read/01j8baqph5c3v99rgn0p32tj70))
+
+The solution is to recognize that a class responsible for both filtering messages and logging messages is too complicated. In modern Object Oriented practice, it would be accused of violating the “Single Responsibility Principle.” [View Highlight](https://read.readwise.io/read/01j8bar8r89tdkkqwg09cy61bk))
+
+One solution is the Adapter Pattern: to decide that the original logger class doesn’t need to be improved, because any mechanism for outputting messages can be wrapped up to look like the file object that the logger is expecting. [View Highlight](https://read.readwise.io/read/01j8bat4m4e3sttcc3x9x8nbtw))
+
+Python encourages duck typing [View Highlight](https://read.readwise.io/read/01j8bav8whbf9z87ssg40m23kz))
+> [!note]
+> Duck typing: A programming concept primarily associated with the Python language, duck typing emphasizes an object's behavior (methods and properties) over its explicit type. The term is derived from the saying, "If it looks like a duck and quacks like a duck, it must be a duck," indicating that the suitability of an object is determined by the presence of certain methods and attributes rather than its inheritance or class. This approach allows for greater flexibility and adaptability in coding, as it encourages developers to focus on what an object can do rather than what it is, facilitating the creation of lightweight adapters and promoting code reuse.
+
+And so the subclass explosion is avoided! Logger objects and adapter objects can be freely mixed and matched at runtime without the need to create any further classes: [View Highlight](https://read.readwise.io/read/01j8baynydfgxctvwbdw0rca62))
+
+The Bridge Pattern splits a class’s behavior between an outer “abstraction” object that the caller sees and an “implementation” object that’s wrapped inside. We can apply the Bridge Pattern to our logging example if we make the (perhaps slightly arbitrary) decision that filtering belongs out in the “abstraction” class while output belongs in the “implementation” class. [View Highlight](https://read.readwise.io/read/01j8bb0dxxf1dewfg0jyv6w8tn))
+
+---
+
+New highlights added at 2024-10-13 4:11 PM
+Instead of file output being native to the `Logger` but non-file output requiring an additional class, a functioning logger is now always built by composing an abstraction with an implementation. [View Highlight](https://read.readwise.io/read/01j8mcakzs1dpqmst4sgsxby1k))
+
+The reason we cannot stack two filters is that there’s an asymmetry between the interface they offer and the interface they wrap: they offer a `log()` method but call their handler’s `emit()` method. Wrapping one filter in another would result in an `AttributeError` when the outer filter tried to call the inner filter’s `emit()`.
+If we instead pivot our filters and handlers to offering the same interface, so that they all alike offer a `log()` method, then we have arrived at the Decorator Pattern [View Highlight](https://read.readwise.io/read/01j8r6kf6c1dp9y5sbaxss465r))
+
+Python logging module implements its own Composition Over Inheritance pattern.
+1. The `Logger` class that callers interact with doesn’t itself implement either filtering or output. Instead, it maintains a list of filters and a list of handlers.
+2. For each log message, the logger calls each of its filters. The message is discarded if any filter rejects it.
+3. For each log message that’s accepted by all the filters, the logger loops over its output handlers and asks every one of them to `emit()` the message. [View Highlight](https://read.readwise.io/read/01j8r76se8wen2j1m7g91bgp89))
+
+a logger’s messages might deserve both multiple filters *and* multiple outputs — to decouple filter classes and handler classes entirely [View Highlight](https://read.readwise.io/read/01j8r77jrx6spm326k65g9w54d))
+
+design principles like Composition Over Inheritance are, in the end, more important than individual patterns like the Adapter or Decorator. Always follow the principle. But don’t always feel constrained to choose a pattern from an official list. [View Highlight](https://read.readwise.io/read/01j8sgr5es60teb6y127ycdjnw))
+
+Sometimes, yes, you will find an existing Design Pattern that’s a perfect fit for your problem — but if not, your design might be stronger if you move beyond them. [View Highlight](https://read.readwise.io/read/01j8sgsc3731bd5qq2fxm6ww5e))
+
+I suggest that the apparent simplicity of the `if` statement forest is, from the point of view of software design, largely an illusion. [View Highlight](https://read.readwise.io/read/01j8sh7a9e0mf63x6r2fqpemh5))
+
--- a/_master_wiki/void/Readwise/The
+++ b/_master_wiki/void/Readwise/The
@ -0,0 +1,19 @@
+# The Definitive Guide to Docker Swarm
+
+![rw-book-cover](https://gabrieltanner.org/blog/the-definitive-guide-to-docker-swarm.png)
+
+## Metadata
+- Author: [[Gabriel Tanner]]
+- Full Title: The Definitive Guide to Docker Swarm
+- Category: #articles
+- URL: https://gabrieltanner.org/blog/docker-swarm/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=The%20Definitive%20Guide%20to%20Docker%20Swarm
+> [!tldr]
+> This text is a guide to Docker Swarm, a tool to scale and manage Docker projects easily. Docker Swarm helps in load balancing, cluster management, and service deployment within a cluster of Docker hosts. It provides features like replicated and global services, scaling, and rolling updates for efficient container management.
+
+## Highlights
+After the registry is running we can continue with pushing the local image to the registry using the **push** command.
+docker-compose push [View Highlight](https://read.readwise.io/read/01j5js3hxamp3s08ebhf5ka502))
+> [!note]
+> Se puede subir una imagen desde un compose.yml file
+
--- a/_master_wiki/void/Readwise/The
+++ b/_master_wiki/void/Readwise/The
@ -0,0 +1,56 @@
+# The Easy Intro to the APCA Contrast Method
+
+![rw-book-cover](https://git.myndex.com/images/APCAresourcesTheWorldIsReading.png)
+
+## Metadata
+- Author: [[APCA]]
+- Full Title: The Easy Intro to the APCA Contrast Method
+- Category: #articles
+- Document Tags: [[design]] [[dev]] 
+- URL: https://git.apcacontrast.com/documentation/APCAeasyIntro.html
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=The%20Easy%20Intro%20to%20the%20APCA%20Contrast%20Method
+> [!tldr]
+> The APCA Contrast Method is a new way to measure readability contrast, improving upon outdated WCAG 2.x guidelines. It focuses on lightness contrast, ensuring consistent visual perception across various colors and contexts. This method helps designers create more accessible web content, especially for users with different visual impairments.
+
+## Highlights
+**Visual Acuity (VA)**. VA refers to the ability to focus the eyes on a small item, to a sharp clear image. An acuity impairment limits how small an item we can focus on. An eye doctor can prescribe glasses or contacts, or perform surgery, to improve acuity. One way we can help accommodate acuity problems is to make things bigger. [View Highlight](https://read.readwise.io/read/01j80q19atq7kcj9e3xhjv3m6j))
+
+**Contrast Sensitivity (CS)**. CS is our ability to detect edges, lines, & letters against a background. CS is separate from acuity, and we can have good acuity with poor contrast sensitivity. We can improve our contrast perception by increasing the light on the subject. On a computer screen, we can increase the difference between a darker and a lighter color. [View Highlight](https://read.readwise.io/read/01j80q35df9x2a0t34ts8r7vyj))
+
+**Color Vision Deficiency (CVD)**. CVD is a reduced ability to distinguish different hues of color. (Sometimes called “colorblind”). Those with CVD have as good or better vision and contrast sensitivity, as standard vision. Thus, CVD does not impact readability per se. But CVD affects visual tasks such as reading a map or charts (dataviz), due to the need to discriminate colors (hue). [View Highlight](https://read.readwise.io/read/01j80q4ftg8t1nw6etbpna3xhf))
+
+contrast between two colors is sensitive to context. This means the other items around it affects how you see it. The “spatial characteristics” of line thickness or text weight & size, govern our contrast sensitivity. [View Highlight](https://read.readwise.io/read/01j80q6p2903s73a752yvtaj83))
+
+For readability, we need ample lightness-contrast, disregarding color as in hue. Color contrast, meaning hue/saturation, does not play a major role in readability. But ample lightness/darkness contrast enables fluent readability at best speed and comprehension. This is especially true for small body text, such as in columns or blocks. [View Highlight](https://read.readwise.io/read/01j80q83bh27pagnrreeqfeze8))
+
+• **The contrast sensitivity threshold** **(CS)** is the point of “just noticeable differences” (JND). That is, the point between visible and invisible.
+• Fluent readability refers to critical contrast. This is the smallest amount needed for best reading speed and comprehension. Peer-reviewed science tells us¹ contrast should be at least ten times the JND. The preferred contrast reserve is twenty times threshold for best fluent reading.
+• Spot readability means readable without significant effort. Spot reading is the lowest readable level, where the contrast needs to be three times the JND. This low level is useful for disabled controls, copyright bugs, and other non-content. [View Highlight](https://read.readwise.io/read/01j80qcm3haxxzbq87k5070v11))
+
+T [View Highlight](https://read.readwise.io/read/01j80qg1xsekbn8qen3c2b12ew))
+
+he following chart demonstrates the spatial nature of human contrast sensitivity. The text samples connect the abstract science of the CS curve to practical reality.
+![This is a chart of the human contrast sensitivity curve. A blue line curves down to the right where the Y axis is contrast sensitivity, and the X access is spatial frequency, increasing toward the right. An increase in spatial frequency means elements are smaller and thinner. On the right of this info graphic are samples of text from very large and bold to very thin and small, with red lead lines indicating approximately where those samples fall on the contrast sensitivity curve. All of the text samples are at the exact same CSS color of #c7c7c7, the top very large and bold headline is legible but as the fonts become thinner and smaller they literally fade out as if becoming lighter gray, even though they are all at the exact same color.](https://git.apcacontrast.com/images/contrastSensitivityGraph5sameColor.png) [View Highlight](https://read.readwise.io/read/01j80qftmhwxycjeeb699tq6cr))
+
+Lightness contrast (Lc) [View Highlight](https://read.readwise.io/read/01j80qn4r2akhdg9bqz128fehm))
+
+APCA generates a lightness contrast value for a minimum font weight, size, and color pair. This value is uniform to lightness/darkness perception. Regardless of how light or dark the two colors are, a given contrast value is visually consistent. Thus, ***Lc 60*** represents the same perceived contrast, for the range of available colors. [View Highlight](https://read.readwise.io/read/01j80qmyq1185m5xfy298yj5vt))
+
+The APCA Readability Criteria has a basic set of levels, related to use cases. For instance, ***Lc 90*** is preferred and ***Lc 75*** is the minimum for body text. This makes it easy to use APCA, very much like WCAG guideline 1.4.3 for ease of use. [View Highlight](https://read.readwise.io/read/01j80qqdpsrb9rk2ejpzwkfy49))
+
+The values below based on the reference font Helvetica or Arial.
+• **Lc 90** - Preferred level for fluent text and columns of body text with a font no smaller than 14px/weight 400 (normal).
+• **Lc 75** - The minimum level for columns of body text with a font no smaller than 18px/400. Consider Lc 75 as a minimum for text where readability is important.
+• **Lc 60** - The minimum level recommended for content text that is not body, column, or block text. In other words, text you want people to read. The minimums: 24px normal weight (400) or 16px/700 (bold).
+• **Lc 45** - The minimum for larger, heavier text (36px normal weight or 24px bold) such as headlines. This is also the minimum for pictograms with fine details.
+• **Lc 30** - The absolute minimum for any text not listed above. This includes placeholder text and disabled element text. This is also the minimum for large/solid semantic & understandable non-text elements.
+• **Lc 15** - The absolute minimum for any non-text that needs to be discernible and differentiable, and is no less than 5px in its smallest dimension. This may include disabled large buttons. Designers should treat anything below this level as invisible. Less than Lc15 will not be visible for many users. Avoid less than Lc30 for anything important for the use, understanding, or interaction of the site. [View Highlight](https://read.readwise.io/read/01j80qwns8z71advxzqxtd91x8))
+
+The demonstrator tool provides real-time updates of minimum font size & weight vs ***Lc*** lightness-contrast. [**apcacontrast.com**](https://apcacontrast.com/) The tool has several ways to enter a color. Click on the color patches to bring up a color-picker, enter a hex value or an RGB value, or use the sliders. The text color supports alpha. A negative ***Lc*** value, such as ***Lc -60*** means the text is lighter than the background. A positive value ***Lc 60*** means the text is darker than the background (light mode). [View Highlight](https://read.readwise.io/read/01j80r1cmq4sx7cfxpy38ntfek))
+
+• **Spatial or spatially:** relating to size, weight, or thickness.
+• **Hue:** the uniqueness of a given color vs other colors, i.e. blue vs red.
+• **Chroma/saturation:** the intensity or purity of a color vs no color.
+• **Luminance:** a physical measure of light, disregarding hue.
+• **Lightness:** the human perception of a given luminance. Also darkness and brightness. [View Highlight](https://read.readwise.io/read/01j80r1p31g0yk305pv0zjq7zz))
+
--- a/_master_wiki/void/Readwise/The
+++ b/_master_wiki/void/Readwise/The
@ -0,0 +1,48 @@
+# The Purest Coding Style, Where Bugs Are Near Impossible
+
+![rw-book-cover](https://i.ytimg.com/vi/HlgG395PQWw/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Coderized]]
+- Full Title: The Purest Coding Style, Where Bugs Are Near Impossible
+- Category: #articles
+- Document Tags: [[dev]] [[dev/design-patterns]] 
+- URL: https://www.youtube.com/watch?v=HlgG395PQWw
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=The%20Purest%20Coding%20Style%2C%20Where%20Bugs%20Are%20Near%20Impossible
+> [!tldr]
+> Functional programming is a coding style that emphasizes using functions and avoiding side effects to create more reliable and maintainable code. It promotes concepts like immutability and closures, which help keep data and functions organized. While it can be complex, learning functional programming can enhance your coding skills, regardless of your background.
+
+## Highlights
+we have imperative, or the paradigm of giving explicit instructions.
+Basically, the "how." And declarative, or the paradigm of describing our goals. Basically, the "what." [View Highlight](https://read.readwise.io/read/01j7qxkzfnjbsj5k63874xp5cm)) [[dev/design-patterns]] [[dev]] 
+
+At the core of the functional paradigm, we have functions, obviously. And these functions need to be usable in a fairly unrestricted way ... we can pass them to other functions and return them from other functions,
+as well as hold references to them for later use. ... We also need to be able to create closures, which are functions that can access and remember the scope around them.
+
+"A closure is a poor man's object... ...and an object is a poor man's closure." [View Highlight](https://read.readwise.io/read/01j7qxw02q306dmkqttpc9phze))
+
+higher-order functions, which are functions that work with other functions to perform an action. Think filter(), sort(), map(), and so on. These help us create reusable and isolated modules [View Highlight](https://read.readwise.io/read/01j7qxwvqq86xrr3rvagas3mb2))
+
+we have immutability, where we aim to avoid something called side effects. Side effects happen when we allow unpredictable state from outside the scope of a function to affect it in some way, or when we allow a function to make changes outside of its scope. By getting rid of potential side effects, our functions become pure, in that if the same data goes into a function, we can always guarantee the same result coming out, without affecting anything else. [View Highlight](https://read.readwise.io/read/01j7qxz3ra928rvfavgendb12z)) [[c1]] 
+
+Currying brings multiple arguments of a function into their own function calls that we then chain together.
+It achieves this using the memory scope ability of closures, where each argument stays in memory until the chain completes, and we get our result. In a similar way, we can use closures to create something resembling an object. The first function in the chain acts as a kind of object constructor, and is where we define most of our internal data. [View Highlight](https://read.readwise.io/read/01j7qy48epfjav6h7rtv8a3nxa))
+
+Currying brings multiple arguments of a function into their own function calls that we then chain together.
+It achieves this using the memory scope ability of closures, where each argument stays in memory until the chain completes, and we get our result. In a similar way, we can use closures to create something resembling an object. The first function in the chain acts as a kind of object constructor, and is where we define most of our internal data. [View Highlight](https://read.readwise.io/read/01j7qy688qvfwj8asj84mzz9t6))
+
+Currying brings multiple arguments of a function into their own function calls that we then chain together.
+It achieves this using the memory scope ability of closures, where each argument stays in memory until the chain completes, and we get our result. [View Highlight](https://read.readwise.io/read/01j7qy6nkgytf7x78h6mq3jqts))
+
+we can use closures to create something resembling an object. The first function in the chain acts as a kind of object constructor, and is where we define most of our internal data.
+This data is privately scoped to the constructor function and is therefore encapsulated by it. We can then return a closure to provide external access to this private data. ... we can go as far as returning multiple named closures to access and manipulate the internal data in more complex ways, further solidifying its object-like behaviors.
+
+In the purely functional paradigm, we work primarily with types and expressions, where the following rules apply: Code is generally evaluated rather than executed, which gives us some interesting new optimization capabilities, such as lazy evaluation and automatic parallelization. Immutability is enforced everywhere, meaning that when we want to make changes to our data,
+We do so by computing a new constant based on an existing constant. And to keep functions pure, the mere thought of a side effect is punishable by the most horrific torture imaginable. Having to learn... MONADS! [View Highlight](https://read.readwise.io/read/01j7qyccaq27vqjn4wqabpsdd5))
+
+The immutability of the functional paradigm forces us to think more strictly about how we pass data around, helping to ensure that changes don’t happen unexpectedly. [View Highlight](https://read.readwise.io/read/01j7qyec9pb8pmxcegkbrnj5d2))
+
+guides us in forming readable code that is highly modular and therefore maintainable. [View Highlight](https://read.readwise.io/read/01j7qyeqqgmbv2v8wk6m1a0fz1))
+
+It does come at the cost of potentially being a bit harder to optimize [View Highlight](https://read.readwise.io/read/01j7qyf3kdvtrsnvdfnm7hf6fq))
+
--- a/_master_wiki/void/Readwise/The
+++ b/_master_wiki/void/Readwise/The
@ -0,0 +1,37 @@
+# The Strategy Pattern Will Make Your Python Code CLEANER
+
+![rw-book-cover](https://i.ytimg.com/vi/hVLb3-OE3pM/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Isaac Harris-Holt]]
+- Full Title: The Strategy Pattern Will Make Your Python Code CLEANER
+- Category: #articles
+- Document Tags: [[dev]] [[dev/design-patterns]] 
+- URL: https://www.youtube.com/watch?v=hVLb3-OE3pM
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=The%20Strategy%20Pattern%20Will%20Make%20Your%20Python%20Code%20CLEANER
+> [!tldr]
+> The strategy pattern is a design method that helps organize code by separating different algorithms into distinct classes. This makes code cleaner, more modular, and easier to maintain, allowing for easy changes at runtime without extensive conditional statements. By using this pattern, developers can enhance their code's flexibility while keeping it readable and manageable.
+
+## Highlights
+the strategy pattern is a design pattern that allows you to cleanly separate different algorithms and behaviors into separate classes.
+__Each algorithm implements a common interface__ so you can easily switch between them at runtime without having to modify your core code. [View Highlight](https://read.readwise.io/read/01j5qs5ace2bghpggy8trfaz6r))
+> [!note]
+> Is this kinda the same as the factory class?
+
+we're going to use Python's protocol typeint protocol is like an interface in other languages it allows you to define the methods an object
+should have without knowing the implementation details up front [View Highlight](https://read.readwise.io/read/01j5qsbjkgnknchvq55mj1eec6))
+
+you may be wondering why you might pick Python's protocol over using an abstract base
+class or ABC unlike ABC's Protocols are duct typed meaning you don't have to explicitly inherit from them in order to implement them [View Highlight](https://read.readwise.io/read/01j5qsjaf9qdk5a5d46drkv43e))
+
+Protocols are duct typed [View Highlight](https://read.readwise.io/read/01j5qsr9779888tpa2mp6w0438))
+> [!note]
+> In "The Strategy Pattern Will Make Your Python Code CLEANER," Isaac Harris-Holt uses the term "Protocols are duct typed" to describe how Python's protocol mechanism allows objects to be used interchangeably based solely on their method signatures, rather than requiring explicit inheritance from a protocol. This flexibility enables developers to integrate external libraries or new classes into their code without needing to modify existing structures, as long as the new objects conform to the expected method definitions. Essentially, duct typing promotes a more modular and adaptable coding style, where compliance with an interface is determined by the presence of specified methods rather than formal inheritance.
+
+the power of the single method interface it allows you to write modular extensible and
+flexible code it's easily testable and very readable [View Highlight](https://read.readwise.io/read/01j5qsr0gh3pvf1w3j0jtqm0ez))
+
+you'll see this pattern used a lot particularly in languages like go where the standard library has single method interfaces like io.writer and io.reader the truly powerful thing here is that these interfaces are used by the standard Library so if you implement a read method on your struct you can use it in standard Library functions without having to do any manual type conversions [View Highlight](https://read.readwise.io/read/01j5qswey6zs8mdgxjnv71v4gy))
+> [!note]
+> Usages
+
--- a/_master_wiki/void/Readwise/The
+++ b/_master_wiki/void/Readwise/The
@ -0,0 +1,16 @@
+# The Waiting Time Paradox, or, Why Is My Bus Always Late?
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article4.6bc1851654a0.png)
+
+## Metadata
+- Author: [[jakevdp.github.io]]
+- Full Title: The Waiting Time Paradox, or, Why Is My Bus Always Late?
+- Category: #articles
+- URL: https://jakevdp.github.io/blog/2018/09/13/waiting-time-paradox/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=The%20Waiting%20Time%20Paradox%2C%20or%2C%20Why%20Is%20My%20Bus%20Always%20Late%3F
+> [!tldr]
+> The text discusses the waiting time paradox in the context of bus arrivals. It explains that while one might expect the average wait time for a bus that arrives every 10 minutes to be 5 minutes, under certain assumptions, the average waiting time can actually be 10 minutes. The text explores this paradox through simulations and probabilistic arguments, showing that the average waiting time aligns with the average interval between bus arrivals. It also discusses the use of Poisson processes to model bus arrival times and concludes that the waiting time paradox assumption may not hold true in real-world scenarios where bus arrival intervals are not exponentially distributed.
+
+## Highlights
+Briefly, the inspection paradox arises whenever the probability of observing a quantity is related to the quantity being observed. Allen gives one example of surveying university students about the average size of their classes. Though the school may truthfully advertise an average of 30 students per class, the average class size *as experienced by students* can be (and generally will be) much larger. The reason is that there are (of course) more students in the larger classes, and so you oversample large classes when computing the average experience of students. [View Highlight](https://read.readwise.io/read/01j5vf1r4qjgrnqa3dq94f19e5))
+
--- a/_master_wiki/void/Readwise/This
+++ b/_master_wiki/void/Readwise/This
@ -0,0 +1,16 @@
+# This Week in Self-Hosted
+
+![rw-book-cover](https://selfh.st/favicon.png)
+
+## Metadata
+- Author: [[Ethan Sholly]]
+- Full Title: This Week in Self-Hosted
+- Category: #articles
+- URL: https://selfh.st/newsletter/2024-08-23/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=This%20Week%20in%20Self-Hosted
+> [!tldr]
+> Self-hosted news, updates, launches, and a spotlight on Pocket ID - a self-hosted OIDC authentication provider
+
+## Highlights
+![](https://github.githubassets.com/assets/pinned-octocat-093da3e6fa40.svg) [View Highlight](https://read.readwise.io/read/01j6vrq67ew0b2bq6vy9efws1q))
+
--- a/_master_wiki/void/Readwise/Time
+++ b/_master_wiki/void/Readwise/Time
@ -0,0 +1,49 @@
+# Time Blocking: The Ultimate Guide
+
+![rw-book-cover](https://blog.superhuman.com/content/images/size/w1200/2022/03/00_Hero---Everything-you-need-to-know-about-calendar-blocking.jpg)
+
+## Metadata
+- Author: [[Jenna Scaglione]]
+- Full Title: Time Blocking: The Ultimate Guide
+- Category: #articles
+- Document Tags: [[productivity]] 
+- URL: https://blog.superhuman.com/time-blocking/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Time%20Blocking%3A%20The%20Ultimate%20Guide
+
+> [!note]
+> **Background:** How can I effectively utilize calendar blocking to enhance my productivity and manage my tasks more efficiently?
+> Here are the top three most important takeaways or to-dos that stood out to you regarding your intent:
+> 🗓️ **Define Theme Days:** Consider assigning specific themes to each day of the week, such as dedicating Wednesdays to meetings and Thursdays to creative tasks. This can help streamline your focus and make your week more structured.
+> ⏳ **Schedule Breaks and Reactive Time:** Incorporate 15-30 minute breaks throughout your day to recharge, and allow for 1-2 hours of reactive time each week to accommodate unexpected tasks. This will help maintain your energy and flexibility in your schedule.
+> ✅ **Prioritize and Map Out Tasks:** Before scheduling, categorize your tasks into meaningful work, "me" time, high priority, and low priority. Then, start mapping out your week by assigning specific blocks of time for each task, ensuring a balanced and focused approach to your workload.
+> [!tldr]
+> Time blocking, also known as calendar blocking, is a method that can help individuals accomplish important tasks, feel more in control of their day, and dedicate time to activities that enrich their lives. By designating blocks of time in their calendar for specific tasks, individuals can avoid distractions and stay focused. The process involves creating weekly and daily goals, prioritizing tasks, and assigning calendar blocks for each task. Additional tips include scheduling reactive time, breaks, and tasks with productivity in mind. It's important to remain flexible and experiment with different strategies to find what works best for each individual.
+
+## Highlights
+Committing to a daily to-do list is a significant accomplishment. It provides structure and direction for personal or workday time management, and helps us avoid randomly completing tasks. It can also feel liberating to transfer your to-do items from your head to paper or an app. [View Highlight](https://read.readwise.io/read/01j9rcxb6bdxq1m7ykh6573qwg))
+
+Calendar blocking involves designating blocks of time during your day to essential tasks and scheduling them into your calendar. By assigning tasks to time blocks, you can easily avoid distractions and stay more focused. [View Highlight](https://read.readwise.io/read/01j9rcz2wktsfweqh3kcdf0t43))
+
+Create weekly and daily tasks/goals
+What are your goals for the week ahead? What would you like to accomplish? [View Highlight](https://read.readwise.io/read/01j9rh1f2e92jbv0s6j3tb15y9))
+
+Prioritize your tasks
+Next, divide your tasks into four categories: (1) meaningful work, (2) "me" time, (3) high priority, and (4) low priority. [View Highlight](https://read.readwise.io/read/01j9rh28qw4faekc503axpzx93))
+
+Define your calendar blocks ... Start mapping out your week and assigning calendar blocks of time for each task you wrote down.
+
+Scheduling in a little reactive time (around 1-2 hours a week depending on your profession) will give you some wiggle room in your schedule should unexpected situations arise. [View Highlight](https://read.readwise.io/read/01j9rhb4qmt7yh3ph64xy6yp2n))
+
+Schedule 15-30 minute breaks throughout the day to recharge, use the bathroom, drink water, etc. [View Highlight](https://read.readwise.io/read/01j9rhjxrm3f4dyxxch1xqt3pw))
+
+Schedule tasks with productivity in mind [View Highlight](https://read.readwise.io/read/01j9rhsjknppx61zz2tbsnw9f3))
+
+Don't schedule more than 90 minutes for each task — the science says so! ... our body rhythms play out in 90 minutes of activity, followed by 20 minutes of rest.
+
+**Are you trying to accomplish more than what is humanly possible in one week?** Instead of cramming tasks or removing "me" time, consider what you can push off until next week. [View Highlight](https://read.readwise.io/read/01j9rj2nffa0g1b7jgb8x22kff))
+
+Are those priority items really a priority for this week? ... When we're stressed, we can sometimes see tasks as more urgent than they really are.
+
+**Try defining theme days** 
+Maybe Wednesdays will be meeting days, and Thursdays will be dedicated to creative endeavors. [View Highlight](https://read.readwise.io/read/01j9rj4rasqpqhp893dqddng04))
+
--- a/_master_wiki/void/Readwise/TypeScript
+++ b/_master_wiki/void/Readwise/TypeScript
@ -0,0 +1,46 @@
+# TypeScript the Right Way
+
+![rw-book-cover](https://i.ytimg.com/vi/UMEp6eFU16k/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Awesome]]
+- Full Title: TypeScript the Right Way
+- Category: #articles
+- Document Tags: [[dev]] [[dev/javascript]] 
+- URL: https://youtube.com/watch?v=UMEp6eFU16k&si=5FrI-L7etAUGFl1K
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=TypeScript%20the%20Right%20Way
+
+> [!note]
+> **Background:** I want to incorporate TypeScript in my projects to enhance code quality, readability, and maintainability while ensuring type safety.
+> ### Top 3 Important Takeaways or To-Dos:
+> 🛠️ **Keep Types Simple:** Avoid using nested types, complex unions, and intersections. Overcomplicated types can lead to confusion and higher maintenance costs, so aim to maintain simplicity in your type definitions. 
+> 🔍 **Utilize Type Guards:** Implement type guards to check for null or undefined values before using variables. This practice enhances code safety and reliability by ensuring that variables are properly validated. 
+> 🚫 **Avoid Using "Any":** Steer clear of the "any" type, as it defeats the purpose of type safety in TypeScript. Instead, use union types, type guards, or the unknown type to handle uncertain variable types effectively.
+> [!tldr]
+> TypeScript has become popular for modern web development because it improves upon JavaScript's weaknesses. It adds static type checking, helping developers catch errors before their code runs. Following best practices in TypeScript, such as avoiding overly complex types, ensures safer and more maintainable code.
+
+## Highlights
+Let’s say you have a basic function that adds up  two numbers in a main.js file. In pure JavaScript   there isn’t anything stopping you from passing  strings or any other type of object as a parameter   to this function. To avoid this, we need that  extra layer of validation provided by TypeScript. [View Highlight](https://read.readwise.io/read/01j7r04ptybp6b904wk49qar0a))
+
+the first rule should be pretty obvious -  avoid using the “any” type at all costs. [View Highlight](https://read.readwise.io/read/01j7r07sqy58gkbmcg2n0kg1tv))
+
+there will be those corner case scenarios where  you don’t really know the shape of an object ... In such scenarios don’t hesitate to use union  types and type guards to make your code safer. If you are truly unsure of a variable's type,  you could use the unknown type instead of any or   leave out the type reference to allow TypeScript  to infer it.
+
+remember to avoid overly verbose type  annotations when they are unnecessary. [View Highlight](https://read.readwise.io/read/01j7r0c9r7ws816nrtcmbksehf))
+
+TypeScript offers a strict mode compiler  option that enforces more rigorous type   checking and constraints to enhance code  quality and to catch potential issues during   development. You can enable this by setting  the strict flag to true in the TS config file. [View Highlight](https://read.readwise.io/read/01j7r0dn8e90zkxvdj370t22tw))
+
+JavaScript’s strict mode was  introduced in ES 5 and you should always use   it as well. This will allow you to opt in to a  restricted variant of JavaScript where silent   errors are changed to throw errors, some mistakes  that make it difficult for the engine to perform   optimizations are fixed, and syntax likely to  be defined in future versions is prohibited. [View Highlight](https://read.readwise.io/read/01j7r0f8r2nskx1jagx6sn7hsf))
+
+A type alias creates a new name for a type.  This can be a primitive, union, intersection,   tuple or any other type. In other words  it can represent complex structures and   give you flexibility in defining types  that go beyond simple object shapes. On the other hand, interfaces are  primarily used to define the structure   or shape of an object or class. Interfaces  in TypeScript are more focused on describing   the properties and methods  that an object should have,  
+and they provide a powerful way to enforce  the structure of objects across your codebase. [View Highlight](https://read.readwise.io/read/01j7r0hfyz8nps371dqga3bmmh))
+
+you should use interfaces for object  shapes and class contracts, use types for complex   and flexible structures and use a combination  of both to create powerful type definitions. [View Highlight](https://read.readwise.io/read/01j7r0jedxp5gd3h5qpkr428v0))
+
+Non-Nullable assertions are Another big source of   potential problems since they can lead  to runtime errors if used incorrectly. ... you should use type guards  to ensure that variables are properly checked   for null or undefined values before use. This  approach leads to safer and more reliable code.
+
+keep things simple.
+Overcomplicated types are a common pitfall  in TypeScript projects, and although complex   types may occasionally be needed, making them  overly complicated can result in confusion,   reduced readability, and higher maintenance costs. [View Highlight](https://read.readwise.io/read/01j7r0pctvv439x5ev9w1ccz74))
+
+Avoid nested types since they are hard  to read and maintain, avoid complex union   and intersection types since they can lead to  convoluted and difficult-to-understand types,   and don’t overuse mapped and conditional types  since they can easily get over complicated. [View Highlight](https://read.readwise.io/read/01j7r0rw8djwydvfy9jdx0e8wj))
+
--- a/_master_wiki/void/Readwise/Understanding
+++ b/_master_wiki/void/Readwise/Understanding
@ -0,0 +1,27 @@
+# Understanding Composition in Software Development
+
+![rw-book-cover](https://miro.medium.com/v2/da:true/resize:fit:1200/0*2px3-S5mOYJWlt1q)
+
+## Metadata
+- Author: [[Hamida Meknassi]]
+- Full Title: Understanding Composition in Software Development
+- Category: #articles
+- Document Tags: [[dev]] [[dev/design-patterns]] 
+- URL: https://medium.com/@hamida.meknassi/understanding-composition-in-software-development-74f84ab984ce
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Understanding%20Composition%20in%20Software%20Development
+> [!tldr]
+> Composition is a software development principle that emphasizes building complex systems by combining smaller, independent components rather than using inheritance. This approach offers flexibility, reusability, and easier maintenance, making it a popular choice among developers. By favoring composition, developers can create more adaptable and manageable systems.
+
+## Highlights
+At its core, composition is about constructing complex systems by piecing together smaller, distinct objects. In object-oriented programming lingo, we often describe it as a “has-a” relationship rather than the “is-a” relationship that comes with inheritance. [View Highlight](https://read.readwise.io/read/01j7jxtrsfs087rbx45dgh9skx))
+
+Flexibility : As requirements change, it’s easier to swap or upgrade individual components without disrupting the entire system.
+Reusability : Crafted correctly, components can be used across various parts of a project or even in entirely different projects.
+Maintainability : Focused and modular components are easier to understand, test, debug, and enhance.
+Reduced Side Effect : Unlike inheritance, where modifying the base can have widespread consequences, composition limits the ripple effect of changes. [View Highlight](https://read.readwise.io/read/01j7jxvsqhk5j1bzjarjrwymhr))
+
+When facing a complex problem, ask:
+- Which components make up this system?
+- How can I break this down into smaller, more manageable pieces?
+- Can I reuse existing components? [View Highlight](https://read.readwise.io/read/01j7jxxp9dp3sqncv2d9rewnqs))
+
--- a/_master_wiki/void/Readwise/Use
+++ b/_master_wiki/void/Readwise/Use
@ -0,0 +1,23 @@
+# Use a Work Journal to Recover Focus Faster and Clarify Your Thoughts
+
+![rw-book-cover](https://news.ycombinator.com/favicon.ico)
+
+## Metadata
+- Author: [[Charles Féval]]
+- Full Title: Use a Work Journal to Recover Focus Faster and Clarify Your Thoughts
+- Category: #articles
+- Document Tags: [[journaling]] [[notetaking]] [[productivity]] 
+- URL: https://fev.al/posts/work-journal/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Use%20a%20Work%20Journal%20to%20Recover%20Focus%20Faster%20and%20Clarify%20Your%20Thoughts
+> [!tldr]
+> The author shares the benefits of using a work journal to improve focus and clarify thoughts while dealing with interruptions and distractions. By writing down tasks, thoughts, and plans, the author found it easier to recover focus and continue work more efficiently. Keeping track of progress and ideas in a journal helped the author stay organized and regain momentum when switching between tasks.
+
+## Highlights
+![](https://fev.al/img/2024/focus.png) [View Highlight](https://read.readwise.io/read/01j93tyz3xadwbjh1jf1y96phr))
+
+I started listing all the commands I was running, and their results. Writing down my train of thoughts, the things I was doing and what I wanted to do next. And I have been doing that for the past 3-4 months. I feel like I invented something new. It helps me think more clearly, and restore the context so, so much faster when I switch between things. [View Highlight](https://read.readwise.io/read/01j93v4f4yq4ycdpcy2sysn9mg))
+
+Write notes of what you’re doing and what you’re thinking. When you drop the pen and get back at it, read the last bit. That’s it. [View Highlight](https://read.readwise.io/read/01j93v5t0hfpz3knh2425ne5ep)) [[productivity]] [[notetaking]] 
+
+After all, I’m writing pages of text, of which I will never read more than a fraction. But that’s not the point. The point is structure, and the point is caching. [View Highlight](https://read.readwise.io/read/01j93v72kryd88jmrpdj4mqxce)) [[notetaking]] [[productivity]] 
+
--- a/_master_wiki/void/Readwise/Why
+++ b/_master_wiki/void/Readwise/Why
@ -0,0 +1,53 @@
+# Why Composition Is Often Better Than Inheritance
+
+![rw-book-cover](https://lh6.googleusercontent.com/proxy/3FDJd1lWoiuZCxfz7C2GRuBjhEQ9Es3OPvuUzs7_qAmYsdPEAiRFKrH9QBOGubPOZOa1I7q6WfEnXHce89uFMceSXhAhs4QbuWmuzw6aeM2G32M3Li8Gr8jwjbSbyaafYID1uQd9hzojASmGiMAp8H1kMjii4g=w1200-h630-p-k-no-nu)
+
+## Metadata
+- Author: [[Joost van Dongen]]
+- Full Title: Why Composition Is Often Better Than Inheritance
+- Category: #articles
+- Document Tags: [[dev]] [[dev/design-patterns]] 
+- URL: https://joostdevblog.blogspot.com/2014/07/why-composition-is-often-better-than.html
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Why%20Composition%20Is%20Often%20Better%20Than%20Inheritance
+
+> [!note]
+> Por lo que entiendo de momento:
+> - Usar composition by default unless you have a reason to use inheritance
+> - Permite crear código más reutilizable y más _"loosly coupled"_, en donde es más dificil que cambios en una parte del código afecten a otra
+> - Composition puede estar relacionado con [[dependency injection]] pero no estoy del todo seguro
+> - Razones para usar herencia pueden ser:
+> - [[polymorphism]], para crear variantes con una interfaz común
+> - Ciertos patrones de diseño como [[factory]] y [[listener]]
+> [!tldr]
+> The article argues that using composition is often better than inheritance in code structure. While inheritance can seem more natural, composition offers greater flexibility, readability, and reduces the risk of bugs. The author suggests that developers should be cautious with inheritance and consider composition for many situations.
+
+## Highlights
+the famous *diamond problem*. What happens when a class A inherits from two classes B and C that both inherit from a single parent D? A now has a D twice and chaos ensues. [View Highlight](https://read.readwise.io/read/01j7k02e4exj8srkx4242fpxkj))
+
+The problem is that when it does, it can often be very difficult to come up with a good solution for how to get rid of it without doing a lot of refactoring. [View Highlight](https://read.readwise.io/read/01j7k01q1m9fafymhnjn692hgk))
+
+Inheritance is very useful for a lot things, for example in polymorphism and in design patters like listeners and factories. [View Highlight](https://read.readwise.io/read/01j7k03r10m6ncdmpn301yc0ns))
+
+An important question in code structure is whether to make classes work together through composition or inheritance. The "has a" relationship versus the "is a" relationship. [View Highlight](https://read.readwise.io/read/01j7jy5adbxd6hqanwamxwyr34))
+
+In my experience intuition often favours inheritance, but it gives so many problems that in many cases composition is better. [View Highlight](https://read.readwise.io/read/01j7jy705wznt9rph7nxb66r4n))
+
+As you can see in this code, CharacterInheritance is shorter. It also feels more natural, since we don't have to write these extra accessor functions for *applyKnockback* and *getPosition*. However, after years of creating both of these kinds of structures I have learned that in a situation like this, using composition is actually more flexible, less sensitive to bugs and even more understandable than using inheritance. [View Highlight](https://read.readwise.io/read/01j7jyaz1nx8p671tzccsgqx29))
+
+Game designers constantly come up with game mechanics that are exceptions to what you already programmed. Saying no to these just because your code structure cannot handle them will seriously damage your game quality [View Highlight](https://read.readwise.io/read/01j7jzcahqza5zye0dxa3yxvdx))
+
+An important goal in game programming is flexibility: making your code in such a way that it is relatively easy to add whatever weird whim the game designers come up with today. In most cases composition is much more flexible than inheritance. [View Highlight](https://read.readwise.io/read/01j7jzdzcr2kv4qtdp378h2chd))
+
+"Readability" is always accomponied by "sensitivity to bugs", since if a programmer does not really understand how something works, then he will likely break it when working on it. [View Highlight](https://read.readwise.io/read/01j7jzem4sqbhqgzj1z7cqm7vx))
+
+*virtual* and *protected* functions. [View Highlight](https://read.readwise.io/read/01j7jzm6wg5dwhd71cmtv7ehzb))
+> [!note]
+> **Virtual and Protected Functions**: In object-oriented programming, *virtual functions* are member functions in a base class that can be overridden in derived classes. They enable polymorphism, allowing the correct function to be called based on the object's runtime type rather than the type of reference or pointer. This is crucial for implementing dynamic behavior in applications.
+> *Protected functions*, on the other hand, are member functions that can be accessed within their own class and by derived classes, but not by outside classes. This access control mechanism helps encapsulate the functionality of a class while still allowing derived classes to utilize or extend that functionality. Together, virtual and protected functions facilitate code reuse and maintainability in complex software systems.
+
+inherited classes work together to create complex behaviour and intertwine more and more over time. [View Highlight](https://read.readwise.io/read/01j7jzh52x8t0pgefbgzdktpay))
+
+this is just too much code to really grasp it all at once without starting to mix things up. The result is that readability decreases and the programmer becomes more likely to introduce bugs because she overlooked something. [View Highlight](https://read.readwise.io/read/01j7jzkaftyev2f34t5x6k5n43))
+
+This keeps the classes from intertwining over time and makes it easier to keep them truly separate. [View Highlight](https://read.readwise.io/read/01j7jzr2x12ncezqhzp3r1qr3h))
+
--- a/_master_wiki/void/Readwise/Why
+++ b/_master_wiki/void/Readwise/Why
@ -0,0 +1,16 @@
+# Why Gumroad Didn't Choose htmx
+
+![rw-book-cover](https://htmx.org/img/gumroad-red.jpeg)
+
+## Metadata
+- Author: [[Sahil Lavingia]]
+- Full Title: Why Gumroad Didn't Choose htmx
+- Category: #articles
+- URL: https://htmx.org/essays/why-gumroad-didnt-choose-htmx/
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Why%20Gumroad%20Didn%27t%20Choose%20htmx
+> [!tldr]
+> Gumroad initially considered using htmx for their new project, Helper, but found it didn't meet their needs as they grew. They switched to React and Next.js, which provided a better user experience and easier development. This experience highlighted the importance of choosing technologies that align with project complexity and long-term goals.
+
+## Highlights
+“HTMX is (officially) a meme to make fun of how overly complicated the JS landscape has gotten - much like tailwind is just a different syntax for inline CSS, HTMX is a different syntax for inline JS.” [View Highlight](https://read.readwise.io/read/01j9k9tx30e5kw6zm07drhw8gv))
+
--- a/_master_wiki/void/Readwise/Writing
+++ b/_master_wiki/void/Readwise/Writing
@ -0,0 +1,44 @@
+# Writing Is Magic. It Can Change Your Life
+
+![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article0.00998d930354.png)
+
+## Metadata
+- Author: [[omerxx@gmail.com]]
+- Full Title: Writing Is Magic. It Can Change Your Life
+- Category: #articles
+- Document Tags: [[star]] 
+- URL: https://omnivore.app/aleidk/writing-is-magic-it-can-change-your-life-18dfa8bdd0b
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Writing%20Is%20Magic.%20It%20Can%20Change%20Your%20Life
+> [!tldr]
+> Today, I want to share a powerful skill with you. If you choose to embrace it—and there are countless ways to do so—you’ll see growth in every aspect of your life. Yes, it’s that impactful.
+
+## Highlights
+“Begin with the end in mind”: Effective writing evokes emotion. Consider the feeling you want to create - excitement, amazement, or anger - and aim to engage your readers. 
+ [View Highlight](https://read.readwise.io/read/01j547jfjajaa9k41dtnpxsxge)) [[blog]] 
+
+Good stories have an **intention** and an **obstacle**. That’s it. You want something; there’s a problem; what do you do? (shock, frustration, deep thinking). Find a solution! Let’s fix the issue. 
+ [View Highlight](https://read.readwise.io/read/01j547jwm5swdx523nhy2n0w2z)) [[notetaking]] 
+
+Use “low-level” writing. Studies show that The New York Times uses 12th-grade level language. 
+Warren Buffett changed his writing style over 40 years. 
+He simplified it from a 16th-grade to a 10th-grade level. Now, he explains things more clearly. 
+If they can, you should too. Use simple language, AI tools like GPT, and apps like [Hemingway](https://click.convertkit-mail2.com/4zu4mx47q9ieh5lx3lguxh3drwv77/7qh7h8hoz8kxolfz/aHR0cHM6Ly9oZW1pbmd3YXlhcHAuY29tLw==) to help. 
+ [View Highlight](https://read.readwise.io/read/01j547kb2be2txj046yrh9a3pg))
+
+[Rhythm in writing](https://click.convertkit-mail2.com/4zu4mx47q9ieh5lx3lguxh3drwv77/owhkhqhronk0rduv/aHR0cHM6Ly93d3cuYmJjbWFlc3Ryby5jb20vYmxvZy9yaHl0aG0taW4td3JpdGluZw==). Words can be music. Sentences can have a flow. 
+Replace commas with periods. Control the tone. 
+Make the readers feel their heart beats, their emotion, their... soul. 
+Did it work? **Make them** ***listen*** **while they read**. 
+ [View Highlight](https://read.readwise.io/read/01j547m5raqmgazwydfrwfpef9)) [[blog]] [[favorite]] 
+
+Start by warming up. Yes, really. Take 10 minutes, pick a piece you like, and write it down, **word by word**. 
+Warm up your brain and body for writing! 
+ [View Highlight](https://read.readwise.io/read/01j547mrzvshcwd1jmdh92gg28))
+
+**Don’t perfect it**. Start with a ROUGH first draft. Then take a break. Then hard edit. 
+ [View Highlight](https://read.readwise.io/read/01j547n5d9btvs9q9xrzz1xvva))
+
+**Publish**! Whether it’s once a week or once a month, it doesn’t matter. 
+The more you practice, the better you become; the more you publish, the better you get at sharing ideas. 
+Practice storytelling. [View Highlight](https://read.readwise.io/read/01j547nethjk4bbf0prnncdsk4))
+
--- a/_master_wiki/void/Readwise/Writing
+++ b/_master_wiki/void/Readwise/Writing
@ -0,0 +1,45 @@
+# Writing Over Infinite Scrolling | Journal Like a Scientist
+
+![rw-book-cover](https://i.ytimg.com/vi/0LhmdYa5vvA/maxresdefault.jpg)
+
+## Metadata
+- Author: [[Charlotte Fraza]]
+- Full Title: Writing Over Infinite Scrolling | Journal Like a Scientist
+- Category: #articles
+- Document Tags: [[Education]] [[notetaking]] 
+- URL: https://www.youtube.com/watch?v=0LhmdYa5vvA
+- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Writing%20Over%20Infinite%20Scrolling%20%7C%20Journal%20Like%20a%20Scientist
+
+> [!note]
+> **Background:** I want to start journaling about my projects, focusing primarily on software development but also incorporating any other interests or activities I engage in.
+> ---
+> ### Key Takeaways and To-Dos:
+> 📝 **Experiment Logging:** For each project or experiment, document the hypothesis, methods, results, and conclusions. This structured approach will help in tracking progress and learning outcomes effectively.
+> 🔍 **Continuous Logging:** Maintain a habit of continuously logging thoughts and observations throughout the project. This ongoing documentation can capture insights as they arise and provide clarity during the development process.
+> 🤝 **Weekly Reflection:** Set aside time for weekly reflections to review all notes taken throughout the week. This will help consolidate ideas, identify valuable insights, and create a coherent framework for understanding your progress.
+> [!tldr]
+> Charlotte Fraza discusses the importance of note-taking and journaling in the scientific process. She emphasizes that logging experiments and reflecting on failures can enhance learning and problem-solving skills. By capturing ideas and documenting resources, individuals can improve their understanding and share knowledge with others.
+
+## Highlights
+experiment logging So within science what you do is
+you record all your experiments successful or not and all the questions that you pose and the answers that you seek and then you note down what you learned from each of these experiments [View Highlight](https://read.readwise.io/read/01j536cg9k591ndzmjdyn3acx0))
+
+experiment logging the idea what you do is for each experiment that you make is you write down these sections so you write down the hypothesis methods results and conclusions [View Highlight](https://read.readwise.io/read/01j536ety7c80mnxr62zpjdxzp))
+
+he second part of experiment logging is the brain dump so this is also something that I really learned to do during my PhD and this is whenever you sit down for a full work day or at the end of a work day you kind of dump all the information that you have in your brain about the experiment [View Highlight](https://read.readwise.io/read/01j536hwghwa7h71cfjs4mhw3f))
+
+the idea of resource documentation or research logging is that throughout any learning process you __log or take a record of all the resources that you use__, and this is mainly because at the end of learning something you usually forget what you've used to get there. [View Highlight](https://read.readwise.io/read/01j536q30j8nqkpcd7dqgrh2ar)) [[favorite]] [[notetaking]] 
+
+the idea of continuous logging is that you keep writing down the thoughts you have about that experiment as you are conducting it. [View Highlight](https://read.readwise.io/read/01j536tb8h218sb5f4jzbh4c4e)) [[notetaking]] 
+
+having reflection moments or weekly reflection in my case and that's really to come back to all the notes you've taken throughout the week and to combine them into one coherent framework and also to pick out the ideas that you really like [View Highlight](https://read.readwise.io/read/01j5373tkcxah1j67yk861wjpp))
+
+don't cross out any of the previous ideas that you have that you currently don't like cuz I find often that as you change yourself throughout time if you go back to some really old notebooks it's actually really nice to see some of the thoughts you were having and sometimes these thoughts are actually more valuable at this moment than you estimated them to be at the previous moments [View Highlight](https://read.readwise.io/read/01j5377gqcfcwfzmwe0mtb9w32))
+
+sharing and reflecting together with another person is actually really nice [View Highlight](https://read.readwise.io/read/01j537948pfqmqcdrfpj1dth6v))
+
+you would write down your hypothesis to how you think this would go what you think you would learn what you think you would gain from this skill acis
+you would write down your methods how you think you're going to learn as much as possible about the brain in 30 days and you would write down your results but then in the end you would also write down your conclusions [View Highlight](https://read.readwise.io/read/01j6s8wm539b8fne7spch2qqnp))
+
+these are usually to-dos that I think I need to do doubts I have about the experiment that I'm going to do what I think throughout that day I will learn or kind of what I have to consider and also a lot of times I write down what I think can go wrong [View Highlight](https://read.readwise.io/read/01j6s90vvygxh31fm58cp5xj11))
+