How to build a writing habit
A wonderful essay by Peter Suhm
Read more [writinghabit.com]
A wonderful essay by Peter Suhm
Read more [writinghabit.com]
– medium.com - submitted by Mazen Touati
A set of practical and straightforward tips for enhancing productivity as a developer.
Read more [medium.com]
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
"Freek’s newsletter is one of the best ways to stay updated with the Laravel and PHP ecosystem. It consistently highlights useful packages, tools, and ideas from the community, especially the amazing work coming from Spatie. As a Laravel developer building SaaS and web platforms, I find it extremely helpful to discover practical tools and insights that improve my development workflow."
– medium.com - submitted by Mazen Touati
A set of practical and straightforward tips for enhancing productivity as a developer.
Read more [medium.com]
Personally, when I want to work on something I just turn off all notification on my Mac.
Probably reached for the phone. Turned off the alarm. Glanced at the time. Scrolled through the Slack notifications. Went through the emails. You will likely continue doing it throughout the day, approximately 2,617 more times, according to some studies. We all do it, and despite all the virtues of digital minimalism, completely giving up those habits is extreme and, arguably, unnecessary. Yet we live in a culture obsessed with productivity and these harmless distractions are wreaking havoc on it.
Read more [blog.nuclino.com]
I present you with the taxonomy of terrible software developers, the ecosystem of software critters and creatures who add a whole new meaning to the concept of “defensive programming.”http://www.aaronstannard.com/the-taxonomy-of-terrible-programmers/At one point or another, every programmer exists as at least one of these archetypes – the good ones see these bad habits in themselves and work to fix them over time. The bad ones… simply are.
Programmers work at night because it doesn’t impose a time limit on when you have to stop working, which gives you a more relaxed approach, your brain doesn’t keep looking for distractions and a bright screen keeps you awake.http://en.codeceo.com/why-programmers-work-at-night.html
Though I keep working at night to a minimum it sounds very familiar. It seems a bit strange but not having a deadline is great for productivity for some types of tasks.