- ✅ The right thing to do: What is the reason behind your actions? -
- ✅ Macro Workflow: Listing Topics that truly matter +
- ✅ Macro Workflow: Listing Projects that truly matter +
- ✅ Macro Time Management: Prioriting Projects and Calendar Scheduling
- ❌ Reflecting: How to use graphs to help Brainstorming ideas (draw.io)
- ❌ Micro Workflow: Todo Listing, Contextualizing, and Ordering Tasks
- ❌ Reflecting: Brainstorming Ideas while on the run diff --git a/productivity/macrotime/1.png b/productivity/macrotime/1.png new file mode 100644 index 0000000..acd545d Binary files /dev/null and b/productivity/macrotime/1.png differ diff --git a/productivity/macrotime/10.png b/productivity/macrotime/10.png new file mode 100644 index 0000000..94f1515 Binary files /dev/null and b/productivity/macrotime/10.png differ diff --git a/productivity/macrotime/11.png b/productivity/macrotime/11.png new file mode 100644 index 0000000..d358107 Binary files /dev/null and b/productivity/macrotime/11.png differ diff --git a/productivity/macrotime/12.png b/productivity/macrotime/12.png new file mode 100644 index 0000000..3f9957a Binary files /dev/null and b/productivity/macrotime/12.png differ diff --git a/productivity/macrotime/13.png b/productivity/macrotime/13.png new file mode 100644 index 0000000..c35760e Binary files /dev/null and b/productivity/macrotime/13.png differ diff --git a/productivity/macrotime/14.png b/productivity/macrotime/14.png new file mode 100644 index 0000000..05a2d51 Binary files /dev/null and b/productivity/macrotime/14.png differ diff --git a/productivity/macrotime/15.png b/productivity/macrotime/15.png new file mode 100644 index 0000000..0006209 Binary files /dev/null and b/productivity/macrotime/15.png differ diff --git a/productivity/macrotime/2.png b/productivity/macrotime/2.png new file mode 100644 index 0000000..e8d6bdc Binary files /dev/null and b/productivity/macrotime/2.png differ diff --git a/productivity/macrotime/3.png b/productivity/macrotime/3.png new file mode 100644 index 0000000..f61d32b Binary files /dev/null and b/productivity/macrotime/3.png differ diff --git a/productivity/macrotime/4.png b/productivity/macrotime/4.png new file mode 100644 index 0000000..26c059d Binary files /dev/null and b/productivity/macrotime/4.png differ diff --git a/productivity/macrotime/5.png b/productivity/macrotime/5.png new file mode 100644 index 0000000..6b04641 Binary files /dev/null and b/productivity/macrotime/5.png differ diff --git a/productivity/macrotime/6.png b/productivity/macrotime/6.png new file mode 100644 index 0000000..b3760b6 Binary files /dev/null and b/productivity/macrotime/6.png differ diff --git a/productivity/macrotime/7.png b/productivity/macrotime/7.png new file mode 100644 index 0000000..c6e0ca5 Binary files /dev/null and b/productivity/macrotime/7.png differ diff --git a/productivity/macrotime/8.png b/productivity/macrotime/8.png new file mode 100644 index 0000000..127db37 Binary files /dev/null and b/productivity/macrotime/8.png differ diff --git a/productivity/macrotime/9.png b/productivity/macrotime/9.png new file mode 100644 index 0000000..6233454 Binary files /dev/null and b/productivity/macrotime/9.png differ diff --git a/productivity/macrotime/index.html b/productivity/macrotime/index.html new file mode 100644 index 0000000..b454a9e --- /dev/null +++ b/productivity/macrotime/index.html @@ -0,0 +1,190 @@ + + + + + + + + + + +
+
+ Prioriting Projects
+Now that we have our list of projects, we have to allocate the time to work on each projects. It's a matter of finding the right balance, don't just allocate 100% of your free time to one project, and 100% of your work time to an other project. You need to split it correctly. Let's check out how i split my time for each project.
+
+For the world (1) (95% of Freetime)
+ -Blog (11)
+ -Project Opsec(111) (50% of Free time)
+ -Project Productivity (112) (25% of Free time)
+ -Fediverse (12) (5% of Free time)
+ -Privacy Front-ends(13) (5% of Free time)
+
+For yourself (2)
+ -Life (21) (5% of Freetime)
+ -Relationships (212) (4% of Free time)
+ -Apartment / House (211) (1% of Free time)
+
+ -Work (23) (100% of Work time)
+ -Work Project A (231) (50% of Work time)
+ -Work Project B (232) (50% of Work time)
+ -Work Project C (231 + 232 -> 233)
+
+Here as you can see, i have decided to reduce the my freetime to just 5% of the things i do for myself, the remaining 95% of things i do during my free time are for the world, as i know that these are going to be the most fulfilling things i can do. As we have explained previously, you need to priorise projects, based on which one matters most to you, and as i have ranked each project from most important (at the top) to least important (at the bottom) you can see how i allocated the time i spend for each accordingly.
+For Work, the priorisation of projects is different, as you're not supposed to prefer a project over another, here you just need to complete the projects in the correct order. As you can see Project Z depends on project X and Y to be started, therefore I split my work-time in 2, half the time is dedicated to project X, and the other half of the time is dedicated to project Y.
+The next week will have a different time allocation if projects X and Y are completed. Unless if there are more projects added to the list, then it will be project Z taking up 100% of the time afterward.
+Calendar Scheduling
+For calendars, to make it simple, i recommend using thunderbird:
+
+[ mainpc ] [ /dev/pts/13 ] [~/Nextcloud/blog]
+→ sudo apt install thunderbird -y
+
+[ mainpc ] [ /dev/pts/13 ] [~/Nextcloud/blog]
+→ thunderbird
+
+
+Now if you want to use a remote calendar, like the CalDAV calendar that comes preinstalled with Nextcloud, you can connect to it like so:
+
+
+
+
+
+Now from here, you can schedule your personal time events in the "Personal" calendar, just do "Ctrl+I" to schedule an event:
+
+In this case, we're doing a one-time event (going to the restaurant):
+
+But in the case where you have a recurrent event (like renewing your mullvad VPN subscription): you can schedule a recurring event like so:
+
+To schedule events on the work calendars you can simply switch the calendar when creating a new event:
+
+Then, as we also want to create "Default" tasks for entire weeks, we can just create an event that is an "All day event", starting from Monday, and ending on Sunday:
+
+And you can also do the same for your work calendar:
+
+So you now get the following result:
+
+For each week, you have a "default" work and personal project to work on whenever you have time (the cup is filled with water), and in it you have your one-time or recurrent events aswell (the marbles in your cup).
+
+Here as you can see on the week view, you have your default tasks on the top, and during the day you have your events.
+ +Nihilism
++ Until there is Nothing left.
Creative Commons Zero: No Rights Reserved
+
+
My Links
+
+
+ RSS Feed
SimpleX Chat
+
+
About nihilist
+Donate XMR: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAUqpZHLrX2VZLH71Jrd9k8
Contact: nihilist@contact.nowhere.moe (PGP)
+Macro Workflow: Listing Topics that truly matter
+Macro Workflow: Listing Projects that truly matter
To get yourself some ideas, just go around the world (physically or digitally) and look what you feel is missing. Over the course of the years on this blog i discovered many, many topics:
+To get yourself some ideas, just go around the world (physically or digitally) and look what you feel is missing. Over the course of the years on this blog i discovered many, many Projects:
-Hacking: Web, Binary, Physical, Hardware, Binexp, Bruteforcing, Privilege Escalations, MITM, AV evasions, etc.
-Sysadmin: Decentralisation, Self-hosting, Federation, Privacy front-ends, etc
@@ -91,8 +91,8 @@ To Transcend
My passion shifted from Hacking to Sysadmin, and from Sysadmin to Opsec over the years. The reasoning behind leaving hacking behind is that finding what developers forgot to take into account when designing their software or their infrastructure it isn't truly fulfilling for me, even though it has given me a very clear and diverse picture of what cybersecurity was. I learned the methodology to follow to start from an IP and arrive at the root user, and after applying it a few dozens of times it's gotten crystal clear and boring.
-Sysadmin wise, i felt like having tangible utility after each tutorial. You learn how to setup something for yourself, at the same time you show everyone how to do it, and in the end you can use the service for your own infrastructure at home. Here it starts to benefit the individuals and it was more fulfilling already. But upon looking at what was missing around the world, i came around the obvious governments attacking people's basic rights of privacy and anonymity. Hence the shift i made to Operational Security topics.
-The 2 main topics i cover currently are Opsec, and a secondary topic: Productivity. As this is also something i've seen that is missing in people, they all look either bored or are feeling completely lost in their lives. I'm firmly convinced that these 2 are currently essential and are 100% worth diving into.
+Sysadmin wise, i felt like having tangible utility after each tutorial. You learn how to setup something for yourself, at the same time you show everyone how to do it, and in the end you can use the service for your own infrastructure at home. Here it starts to benefit the individuals and it was more fulfilling already. But upon looking at what was missing around the world, i came around the obvious governments attacking people's basic rights of privacy and anonymity. Hence the shift i made to Operational Security Projects.
+The 2 main Projects i cover currently are Opsec, and a secondary Project: Productivity. As this is also something i've seen that is missing in people, they all look either bored or are feeling completely lost in their lives. I'm firmly convinced that these 2 are currently essential and are 100% worth diving into.