On this week, I had the following readings that were very insightful:
Andrew Wilkinson speaks about a set of “Anti-Goals” he and his business partner set for their company. The idea is instead of seeking something good, to avoid something really bad.
“It is remarkable how much long-term advantage we have gotten by trying to be consistently not stupid, instead of trying to be very intelligent.”
Daniel Albuschat explains his two modes on writing code: Hacker mode and Clean mode. Put simply, he uses Hacker mode to get shit done fast and explore some library, for instance, that he doesn’t know. He requires from himself to write disposable code, which will be replaced by the code he writes on Clean mode. He also does very good statements on how to craft good documentation.
Sam Jarman tells about his experience on finding mentors. He puts that’s critical to keep casual and not ask for commitment. Simple coffee break and small talk about tech projects is enough to get invaluable advices from the people you admire. He also advices to pay back to the community, either helping the mentor with his marketing or work, or even mentoring junior developers along the way.
⭐️ Amazing post. This will give examples on how to market your product the right way. The idea behind the post is simple: People buy benefits, not features. They buy better versions of themselves.
When you’re trying to win customers, are you listing the attributes of the flower or describing how awesome it is to throw fireballs?
Rafal Cymerys will discuss about how bad chatbots are delivering value nowadays (if they are delivering something at all). He states that the problem with chatbots is that they are not (yet) good at either improvising a meaningful conversation with customers, neither presenting useful action items. They are, in the majority, just dumb robots that present lists as chat dialogs.
Regan Walsh will give three questions you should ask before taking on new work: does it motivates me? Does it speak to my values? And does I have a choice? By answering those questions, you can highlight reasons to accept or not new work.
Mo Bitar has an open-source named Standard Notes that has evolved to a mean of living for himself. He tells some good piece of advice about how to handle open-source communities and requests to enhance the library. He states that simplicity is key and will allow your product or project to evolve quickly and cheaply.
Nicer Studio owners will tell you it’s hard to ask people to pay for something you made. They have launched successfully two free products on ProductHunt, but their first paid one was the most challenging. But they got three ways to increase their success: generous free tier; special offer for product-hunters; and talk to as many customers as possible. Besides that, they understood their product was global and made it available in many different languages.
Beekey Cheung came to the conclusion that is not possible to learn everything. What he suggests instead is to focus on your area and play with some other technologies. You don’t have to master all of them, but you could benefit from getting one extra tool under your belt. Also, he advices on being rich on smart friends, have them playing with new technologies and then meeting to share results.
Featured image credit from here.