ScaryRacoon

OP asks for moments, gets things people started doing with no description of the moment.

For me it is taking extensive notes. Over the past year I started pay attention to the mannerisms, behavior, and personalities of the people whose position I wanted to take in the near future. One commonality among almost all of them: they take notes during almost every conversation and write notes throughout the day as they think of things.

Where did you end up going?

Home construction and remodel services has always been a very strong indicator of how well or poor the economy is going.

I think a big point that wasn't touched on in the article (maybe her book does, I haven't read it) is that the increased debt load on students means they are delaying or forgoing buying other major purchases, such as homes and cars. Both of which are huge economic drivers. It isn't that people can't afford the loan payments, it is that the loan payments are reducing the disposable income of those students for quite some time.

Not at all. The housing administration had some discriminatory practices in the past that did much of what the original suggestion was. It was a disaster. You want a community to be as diverse as possible across any sort of metric (income, race, religion, etc).

I like how everyone now wants an echo chamber of their own ideas and are so uncomfortable with someone who challenges their opinions that they demand a service change the way it operates. I'm not saying the bashing/harassment is okay, it isn't.

I use it strictly to connect with other software engineers. Outside of that, I agree with you. I'm extremely careful about what I tweet or like or re-tweet. I don't think most folks would find Twitter that useful. I didn't really get it until I joined, and the only thing I've found it helpful for is to network with other engineers.

I recently move from a full-stack position into a more focused position. I felt like I was "jack of all, master of none" which really irked me. The time I was given for training was good, but it had to be split among all the different layers of the stack which meant I never really got an opportunity to get deep into any particular layer.

It isn't true. If you use your time wisely then you will be just fine. If your employer doesn't give you the time/budget for on-going education, then you need to look for a new employer.

What you're describing would result in large ghettos of low-income people. It would be a nightmare in the end.

Readable code > cleaver code

Why would anyone - individual or corporation - pay more taxes than they are legally obligated to pay?

Because they can't afford the accountants and lawyers required to pull of the funneling of funds through various bodies and countries to get said reduction in tax burden?

Failure is an opportunity to learn. If you don't fail once in a while, you're not pushing yourself. Failure is a normal part of life, to expect perfection in software development is insanity.

"List of cities"....3 states right off the bat. Wat?

In all seriousness, there won't be just one. Technology centers will continue to grow. Our economy is becoming even more centered around information and technology. If your city isn't positioning itself to attract business and talent, it's gonna be a rough future for you.

Just so we're clear: you're saying JavaScript isn't a useful language? Ooookay then.

I would argue that this should be the default behavior for a private tab.

The debate isn't just about the AR-15, but since the AR-15 is "America's Gun", it just happens to get the spotlight.

The debate is about all military-grade civilian issue long semi-automatic rifles. The debate is about if the potential damage such a weapon can cause in the wrong hands is enough to justify an outright ban (or severe restriction on sales).

It was a well written piece and very informative, but I think it missed what the on-going debate is really about.

Keys that I have seen: * Empathy, compassion, and passion * Ability to delegate work appropriately and fairly * Ability to communicate in a appropriate manner and at the appropriate times: * To the team * To management * To non-technical stakeholders * Ability to identify the "unknowns" and give a fairly accurate estimate that takes into account those unknowns * Know when to raise the red flag if something big will hinder the original estimate * Be humble (no work is "below" them)

That is fine. Talk about that. The point isn't to tell someone what is exciting, it is about making connections. Perhaps you read a research paper on a topic the other person has an interest in. Perhaps you contributed to a project they use in their spare time, or could use on a side project.