needing

Proficient: Experience doing professional work on a project in a language without needing to come back up to speed.

Insert bad joke here about not needing a contest to have a obfuscated c++ competition.

Meaning, you can get live traffic data without needing to know where everyone is.

Then cursors were implemented to make it easier to pass around parts of your global state without having components needing to know everything.

Especially since the only crocodile you observed will not be needing another meal.

I really hate needing to validate this but I also have pretty great stats on sprint completion as well.

The instructions are pretty clear about it needing to be cold.

You can't do that if you have a family, (but if you do, that's on you for switching to programming while needing to support a family).

They're not fixing it and they're not working with it at a technical level, they're just using it without needing to know details of how it works.

I wonder how the rate of covering by snow compares with blown bulbs needing replaced, as both result in the lights not being visible.

I would often get an odd sense of needing to chew.

What about those of us who think the world is incredible and wonderful, and that there's more than enough magic for kids to spend a lifetime in love with without ever needing to be lied to in order to obtain it?

It reminds me (although I can't find any links, not sure how popular it really was) of the movement in the open source world for not needing the "private" keyword in Java if everything's open source anyway.

"== nil" is just as short as ".nil?" and isn't as wacky as intentionally calling methods of nil (and every other object needing to have this nil-specific interface).