You can download them at http://www.goddessguidebook.com/free-poster-key-zen-habits/
Showing posts with label productivity. Show all posts
Showing posts with label productivity. Show all posts
2012-02-24
2012-02-22
Top 10 Productivity Hacks
Top 10 Productivity Hacks
Source: zenhabits.net
Also in poster version.
# 1: Do something you’re passionate about
# 2: Work off-line as much as possible
# 3: Do the tough tasks first
# 4: Avoid unnecessary work
# 5: Avoid meetings; when you must meet, make it effective
# 6: Get to work early; work fewer hours
# 7: Declutter your workspace; work on one thing at a time
# 8: Simplify information streams, crank through blogs & email
# 9: Wake up early
#10: Take care of your Most Important Things first
Source: zenhabits.net
Also in poster version.
2011-12-16
7 things highly productive people do
7 things highly productive people do
By Ilya Pozin
1 - Work backwards from goals to milestones to tasks.
2 - Stop multi-tasking
3 - Be militant about eliminating distractions.
4 - Schedule your email.
5 - Use the phone.
6 - Work on your own agenda.
7 - Work in 60 to 90 minute intervals.
By Ilya Pozin
1 - Work backwards from goals to milestones to tasks.
2 - Stop multi-tasking
3 - Be militant about eliminating distractions.
4 - Schedule your email.
5 - Use the phone.
6 - Work on your own agenda.
7 - Work in 60 to 90 minute intervals.
2010-03-24
My developer workbench
A very dear friend is having a hard time getting back into 'developer shape', so I decided to blog about how I organize my developer work files:
/dev
This is where I keep the current projects I am working on.
It is important to me to keep this folder as clean as possible.
If I have a project that is inactive, I just create a ZIP archive and delete it.
/dev/examples
This is where I keep code examples, historically called the 'grrreat tests' :-) (Miguel and João, you know why)
The idea is to keep small projects, each with a single purpose. It is the best way to test libraries before using them in larger projects.
I get snippets from here all the time. If you don't know, snippets are fragments of code that can be copy-pasted and easily reused.
/devlib
This is a collection of libraries. You can save a lot of time reusing existing code and learning from it.
The collection is organized in 3 sections: dist, doc, and source; for binaries, documentation, and source code, respectively.
I keep multiple versions of libraries, each in a separate subfolder, because sometimes it is useful to compare changes, using a tool like WinMerge.
If you only take away one thing, remember that single-purpose code examples are the way to write quality code, fast!
Feel free to share comments about your development practices. I'm always looking for ways to improve!
/dev
This is where I keep the current projects I am working on.
It is important to me to keep this folder as clean as possible.
If I have a project that is inactive, I just create a ZIP archive and delete it.
/dev/examples
This is where I keep code examples, historically called the 'grrreat tests' :-) (Miguel and João, you know why)
The idea is to keep small projects, each with a single purpose. It is the best way to test libraries before using them in larger projects.
I get snippets from here all the time. If you don't know, snippets are fragments of code that can be copy-pasted and easily reused.
/devlib
This is a collection of libraries. You can save a lot of time reusing existing code and learning from it.
The collection is organized in 3 sections: dist, doc, and source; for binaries, documentation, and source code, respectively.
I keep multiple versions of libraries, each in a separate subfolder, because sometimes it is useful to compare changes, using a tool like WinMerge.
If you only take away one thing, remember that single-purpose code examples are the way to write quality code, fast!
Feel free to share comments about your development practices. I'm always looking for ways to improve!
Subscribe to:
Posts (Atom)