20 random bookmarks
stuff me collect
stuff me collect
Shipping is really hard and you have to make it your main priority
Shipping doesn’t mean deploying code, it means making your leadership team happy
You need your leadership team to trust you in order to ship
Most of the essential technical work is in anticipating problems and creating fallback plans
Scale back your implementation work as you approach launch so you’re free to jump on last-minute problems
You should constantly ask yourself “can I ship right this second?”
Generate an RSS feed from Telegram chats. You digital minimalism friend. - aigoncharov/telegram-to-rss
A - The task requirements and goals might not be clear enough. If you are trying to get yourself to “plan for a project” or “write a book” then it’s hard to identify the next actionable items. Put some time aside to figure out what physical things you can do to move the project forward. Try break down the larger tasks into the smallest pieces possible. The goal of the project might need identifying, or the requirements fleshed out from a supervisor.
B - The task might exceed your current competency. Sometimes we know what we have to do, but don’t know how to do it, and then we become avoidant rather than admitting this. In this case, it’s worth figuring out what you do know how to do and what you don’t know how to do, and be honest with that. Then slowly ask for help or read up on the things you don’t know.
C - The tasks might really not be worth it. Sometimes you are assigned tasks that don’t actually help you achieve your long-term goals, and so your brain demotivate you from doing them. Maybe the payoff is low, maybe you don’t learn anything new from them, or maybe a colleague you don’t like will gain credit for the tasks, or maybe you just wont be rewarded or appreciated for getting the tasks done.
Баунс читает Кафку.
Would you love me if I became a worm?, somebody could ask. I would respond that no, I don't in fact love you, for you are a worm.
Indeed I find humans more valuable.
Don't leave openings in which you are going to insert code at some future date when the problem changes because inevitably the problem will change in a way that you didn't anticipate. Whatever the cost it's wasted. Don't anticipate, solve the problem you've got.
Development Platform for building event-driven and distributed systems. Move faster with purpose-built local dev tools and DevOps automation for AWS/GCP.
The emerging golden age of home-cooked software, barefoot developers, and why the local-first community should help build it
Your brain does not process information, retrieve knowledge or store memories. In short: your brain is not a computer
Completely open source DIY gaming mouse, including hardware (PCB, shell) design files - wareya/DIY-Gaming-Mouse
WTF Notebook gives me a place to park the impulse to fix it now, damn it! until I have more context for deciding what to work on first. Instead, for two weeks, I just write things down.
Classic MacOS & GS/OS widget library for linux (and other?) - buserror/libmui
Instead of asking over and over again if she is working tomorrow. I just consult her very organised calendar — and when she wants to check if I'm free she looks at my very empty calendar.
Прекрасная статья о выборе человечества - покинуть планету с её проблемами или остаться и решать их? Обратиться к корням - природе, ручному труду или отвергнуть прошлое и адаптироваться к жестокому космосу?
Как сказал Курт Воннегут: "What makes you think you’re going anywhere?"
Подобные Дайсонам, в моей душе борются отец и сын, правда скорее поменявшись ролями. Тянуться к недостижимому космосу, к неизведанным и от того прекрасным технологиям с их бесконечными проблемами? Или обратить внимание на верную спутницу человека - прекрасную Землю и, возможно, обрести покой в отказе от амбиций?
TL;DR В статье рассказывается о том, как мне удалось перевести чтение лент в ВКонтакте, Telegram, Facebook, Instagram, Reddit и почтовых рассылок в единый сервис InoReader. Причем почти без написания своих велосипедов