Interesting news I found on Friday– 5/25/2012 from going through my RSS and Twitter feeds (both current and historical)
- How to Measure Your Life
- Calendar Triage
- Protect the Basics
- Eliminate the non-essentials
- Reschedule what is important, but not now important
- We are successaholics not workaholics
- Care More to succeed
- Managing the load of requests for help in the digital age
The basic premise hear is make sure that a request from someone comes with some work on their part. Have them write an introduction for themselves or define what they want out of the request etc… That will alone streamline the number of help requests to those who are really serious about it.
- Buying Happiness
- The Science of Happiness
1. Buy experiences instead of things
2. Help others instead of yourself
3. Buy many small pleasures instead of few big ones
4. Buy less insurance
5. Pay now and consume later
6. Think about what you’re not thinking about
7. Beware of comparison shopping
8. Follow the herd instead of your head
Coding Horror presents his side of the Learn to Code, Don’t Learn to Code argument. He lands on the Don’t Learn to Code side. John Galloway argues the other side of the coin that a little coding knowledge in our technologically saturated world is a good thing. I agree with him as I think understanding how a computer works is becoming increasingly important as Software is eating the World. He makes the argument for my learning how a computer works is more useful and practical than much of what is taught in school. To his argument I would add that learning how a computer works (and how to code) is more important than cursive (why do we still teach that!).
That said for both coders and non-coders alike Coding Horror has some good advice. You should be learning to write as little code as possible. Ideally none. Amen. Code and especially novel code isn’t the goal, but sometimes we get that confused. Start with doing the simplest thing that works and go from there.
How many projects, projects with extremely aggressive schedules, have you been on, where everyone knows the project has been under “consideration” for months and months, if not years? Once the development team is appointed, the mantra becomes “hurry, hurry.” Where was all the hurry when management was “considering” the project?
- Attribute Based Routing in ASP.NET Web API
- A Better (Collaborative) Approach to BI
- Responsive Web Design
- GZip Compression in ASP.NET
Absolutely great advice for making decisions
- Use checklists for common routines.
- Set time limits.
- Limit your choices.
- Satisfice to find a good enough fit for now.
- Just decide.
- Right-size your decision making effort.
- Take a time out to recharge.
- Delegate more often and more frequently.
- Make it a group thing.
- Let things solve themselves.
- 6 Huge Hiring Mistakes
- Sharing Ideas with Authority Figures
- Encourage them to explain their ideas for solutions through pictures (it will help ease potential anxiety from talking to you)
- Embedding Data Discovery into your organization
- Leading Sales as the most challenging leadership position
- Model the way
- Inspire a shared vision
- Challenge the process
- Enable others to act
- Encourage the heart