Good to Great: Why Some Companies Make the Leap and Others Don't

Author: Jim Collins
This Year Hacker News 2
This Month Hacker News 1


by austincheney   2020-07-28
I learned so much about structure and organization from

I learned the value of utility from Nicomachean Ethics in that it establishes a value hierarchy starting from the fragment: that which exists for its own sake.

I liked this book for establishing ethics as the basis for rapid growth in business:

A lot of people struggle with CSS. It’s not hard but it take some solid practice to master. This is the best book:

Honesty is important. Brutal honesty forces changes to culture and everybody wins. It forces you to act with ethics for the welfare of the group:

Fear of innovation is a form of hecklers veto, more so when popularity or a majority is threatened. Originality, even when wrong, is always more important: On Liberty.

by austincheney   2019-12-08
My favorites are Good to Great and Principles



by anonymous   2018-01-14

I'm using Amazon AWSECommerceService to help the user find and add Amazon item to resources in applications DB. I have an input field with some JS code - when a user types some text it will grab it and search for items using AWSECommerceService. On my local machine, I'm getting correct date whit good DetailPageURL for items. But when the app is deployed to customers test server Amazon service returns weird URL.


This is the URL is returned to my localhost:

And this is a URL returned for the same item on customers server:

This NULL value is returned instead of parameters. I am still unable to find the solution to this issue - the same code works differently in two environments.

by wheelerwj   2017-08-19
This is an interesting question, because it signals that you are most likely very new to hiring, and maybe ill-equipped to handle managing people in general. Although, at least you're asking questions.

First, very rarely does a manager regret a hire even though it's very common for a hire not to work out. Hiring and interviewing are in terrible shape right now, and more often then not lead to terrible hiring/job acceptance choices.

Second, you regret hiring PEOPLE, not developers because regrettable hires aren't specific to developers. When they are, it's because an engineer was given too much access to something they should not have been and a theft/breach occurs.

Examples of these concepts in play: The NSA probably regrets hiring Edward Snowden. I don't regret hiring the last JS dev I hired even though it didn't work out and he moved to a different company.

Lack of technical expertise is a problem sometimes, but it can be nurtured. Lack of personal skills is a huge problem in an office environment, and is much, much harder to nurture. But neither of these are regrettable in-and-of themselves.

The thing to remember is that you have to weigh the urgency of hiring against the long term impacts of hiring the wrong person. In other words, be careful and set up controls, but don't allow decision paralysis.

Good luck with your project, keep your head up, and expect failure. Great employees are rare, so just keep at it.

post mobile edit:

Go read:

Good To Great:

How to Win Friends and Influence People:

Emotional Intelligence: