1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 | <rss version='2.0'> <channel><title>mcksp.com</title><link>https://mcksp.com</link><description>mcksp.com</description> <item> <guid>https://mcksp.com/tech/gituwa.html</guid> <title>gituwa: static git web frontend generator</title> <link>https://mcksp.com/tech/gituwa.html</link> <description><h1>gituwa: static git web frontend generator</h1> <p> <b><code>gituwa</code></b> is static git web frontend generator. You can find it self-hosted <a href='https://git.mcksp.com/gituwa'>here</a>. </p> <p> It lets you browse file tree, display file content, and also prepare nice repo main page with file tree, photo of your project and README. </p> Usage of gituwa: <p><code>gituwa [repo_path] [output_path] [repository_description]</code></p> <p> where <code>repo_path</code> can be a path to <code>bare</code> repository, and <code>repository description</code> is a short text that will be displayed next to name of the repository. </p> <p> To update files automatically on <code>git push</code> I recommend updating <code>post-receive</code> hook of repositories to include call of <code>gituwa</code>. </p> <p> I was looking for something like that for my site, and I found <a href='https://git.codemadness.org/stagit/files.html'>stagit</a>, which is great software, but I decided to implement something simpler by myself. So in terms of features <code>gituwa</code> is definitely a subset of <code>stagit</code> except directory structure in file tree and added image on the main page of repository. </p> <p> I think that image makes a lot of difference when looking at repositories of strangers on the internet, as it removes barrier of cloning and compiling a thing to see what it is really about </p> <img class='center' src='/assets/tech/gituwa/gituwa.png'> </description> <pubDate>Wed, 23 Aug 2023 12:00:00 +0000</pubDate> </item><item> <guid>https://mcksp.com/blog/choose_direction.html</guid> <title>Productivity is for choosing direction</title> <link>https://mcksp.com/blog/choose_direction.html</link> <description><h1>Productivity is for choosing direction</h1> <p> I'm getting bombarded with productivity tips from everywhere. To be honest, sometimes it's me who is searching for some productivity porn. </p> <p> It seems that productivity is pervasive theme of our lives. With all these techniques, habits, and strategies is easy to lose sight of the "why" behind our pursuit of productivity. <i>Getting more done</i> is the obvious one, nevertheless shouldn't be the only one, as your to-do list probably will never be emptied. </p> <p> I believe that one of the biggest gains of being productive is that finally, after completing all necessary daily hustle occupying your mind, you can pause to think about <i>where</i> you want to direct your productivity, what are your goals. </p> <p> Maybe even it's not about being productive, but peace of mind, escaping constant sense of urgency. And for me, this feeling often comes from completing a task. And when I am productive it's often also the time packed with reflections on directions of my actions and goals. </p> </description> <pubDate>Tue, 15 Aug 2023 12:00:00 +0000</pubDate> </item><item> <guid>https://mcksp.com/blog/gardens.html</guid> <title>Digital gardens</title> <link>https://mcksp.com/blog/gardens.html</link> <description><h1>Digital gardens</h1> <p> Recently I came across the term <i>digital gardens</i>. It encapsulates a concept that has long been present on the web but was coined only recently. </p> <p> In my words, <i>digital garden</i> is a way to play with and grow your ideas, organized as an interconnected set of evergreen notes. Unlike chronological/hierarchical organizational systems popular today it emphasise non-linear nature of thinking. It's often closely tied with <i>thinking</i> in public, sharing your ideas, <a href='https://notes.andymatuschak.org/zCMhncA1iSE74MKKYQS5PBZ'>working with garage door up</a>. </p> <p> In short, it's probably your CS professor's website. Or a wiki with backlinks. </p> Here are some blog posts that explore this topic far better than I do: <ul> <li><a href='https://tomcritchlow.com/2019/02/17/building-digital-garden/'>https://tomcritchlow.com/2019/02/17/building-digital-garden/</a></li> <li><a href='https://jzhao.xyz/posts/networked-thought'>https://jzhao.xyz/posts/networked-thought</a></li> </ul> And more examples of <i>digital gardens</i>: <ul> <li><a href='https://gwern.net'>https://gwern.net</a></li> <li><a href='https://notes.andymatuschak.org'>https://notes.andymatuschak.org</a></li> </ul> <p> I don't run my digital garden yet, but it feels like it can be a good way to <i>think</i>. Taking care of your garden sounds like it can translate better to taking care of your mind than taking care of generating new entries in your feed. But of course, either way, you still have to put in hard work to get quality output. </p> <p> It's a shame that I find myself so hyped about this way of running my blog just after I finish developing my own static site generator :D Don't want to be one of these blogs, where posts revolve more around new tools used to run a blog than the actual content. But I believe that where digital gardens shine is blogs with an extensive collection of articles, mostly <i>researching</i> new topics, While I may have some time before reaching that stage, I plan to incorporate some ideas of digital gardening already. </p> </description> <pubDate>Wed, 19 Jul 2023 12:00:00 +0000</pubDate> </item><item> <guid>https://mcksp.com/blog/elden.html</guid> <title>Elden Ring is really good</title> <link>https://mcksp.com/blog/elden.html</link> <description><h1>Elden Ring is really good</h1> <p> I will be just a short note, but I have so much joy playing <i>Elden Ring</i>. I love the atmosphere and subtle way of leading the story. Combat is satisfying, monster design is top-notch. I often stop to just watch how beautiful the world in this game is. </p> <p> Open world is awesome, but also you will find linear, carefully designed levels similar to those in <i>Dark Souls</i>. </p> <p> And after around 50 hours I still didn't finish the game, cause there is so much to explore (I hope this review will be valid after beating the game too). </p> <p> My only remark will be that in my opinion upgrade system is not ideal. There are so many weapons, spells and other gear in this game, and almost nothing stops you from using it and experimenting (you can even respec your character midgame many times). But in the end, you have to upgrade your gear to fight with harder enemies, and upgrades are very resource hungry, you can't aford to upgrade multiple weapons. Which leads to less experimentation and less fun. </p> <p> It kinda forces you to check wiki for optimal builds (which I refuse to do), because you can't afford to make mistakes, and this is something that sucks. I believe that in gaming generally using wikis takes half the fun away, but it's a topic for a different time. </p> <p> But even with this flaw this game is a masterpiece and I recommend it to everyone. </p> <img class='center' src='/assets/blog/elden/elden.jpg'> </description> <pubDate>Wed, 28 Jun 2023 12:00:00 +0000</pubDate> </item><item> <guid>https://mcksp.com/blog/start_doing.html</guid> <title>You thought about it enough, start doing</title> <link>https://mcksp.com/blog/start_doing.html</link> <description> <h1>You thought about it enough, start doing</h1> <p> I believe most people spend too much time on theoretical exploration rather than executing on their ideas. Of course, some areas need big theoretical background, and there is some virtue in coming "prepared" for the task. But often times when it comes to starting new hobby or that little project you have in mind, I would recomend getting your hands dirty fast. </p> <p> For long time I was always dreaming about making my own music, something around house / hip hop beats. I have watched a ton of youtube videos, read about stories of musicians I listen too, but never actually tried to create something. My firends sometimes share with me really exiting ideas, however, more often than not, when we met again after few months, those ideas are still only ideas. It's hard to say what is the cause of that, maybe analysis paralysis, maybe fear of failure or perfectionism. </p> <p> But I believe that there is also some kind of inertia - the longer we stay in the theoretical realm, the harder it becomes to start executing. </p> <p> One evening I bought music sampler (for too much money), and suddenly all the things I read about making music before make more sense. Things become a lot clearer, and finally I could start actually <i>progressing</i> in a way that can only happen from <i>practise</i>. </p> </description> <pubDate>Tue, 23 May 2023 12:00:00 +0000</pubDate> </item></channel></rss> |